Summary: | doesn't actually work on Tseng ET4000/W32p | ||
---|---|---|---|
Product: | xorg | Reporter: | Michael Shigorin <mike> |
Component: | Driver/Tseng Labs | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | major | ||
Priority: | medium | CC: | balaton, libv |
Version: | git | Keywords: | regression |
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
Michael Shigorin
2012-03-08 06:55:29 UTC
Created attachment 58187 [details]
8f41e5d8bb40d6bb184b4806b701a3e11caf43c3 (WAIT_ACL)
Created attachment 58188 [details]
8f41e5d8bb40d6bb184b4806b701a3e11caf43c3 ("Unable to probe RAMDAC" w/palette snoop)
Hi there. I a Gigabyte MoBo with five (5) Tseng ET4000/W32p cards. Plan is to build a video wall (six monitors in total) for a full environment administration. Evidently I cannot do it because I am having the same problem. Is there anything I can do to help fix this problem? (In reply to comment #3) > Is there anything I can do to help fix this problem? You might end up with drivers from xorg-server 1.3/1.4 age, I recall those as rather working with a range of old videocards. Degradations started ca. 2009. The "modern hardware" way might be to find a dual-pipe motherboard (with e.g. DVI and HDMI capable to work simultaneously) and two dual-pipe videocards (I've used a dual Nvidia Quadro setup with three 42" panels at a HPC site once upon a time). My stand was situated in Kiev and is not available anymore "thanks" to neocon greed and USA aggression against Ukraine (read Russia)... -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-tseng/issues/1. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.