I absolutely confirm this bug. I posted some infos about this bug here: https://bugs.freedesktop.org/show_bug.cgi?id=11617
But I was probably wrong about "xorg starts correctly" as it doesn't start and it behaves like Timo described (100% CPU).
So I correct my previous statement and re-post my infos (as attachments seem corrupted in the other bug).
Computer:
Toshiba 1800-100 and Trident Ai1 (for
more info see the attached X org log and dmesg).
Not-working Distributions tested:
- Ubuntu 7.10 - Xorg 7.2
- Debian unstable - Xorg 7.3
- Fedora 7 - Xorg 7.2
Working distros:
- Debian 4.0 - Xorg 7.1
- a lot of other distros with Xorg <= 7.1
Working combinations of xorg.conf:
driver trident + option noddc
Not working combinations:
driver trident without option noddc
driver vesa + option noddc
I absolutely confirm this bug. I posted some infos about this bug here: /bugs.freedeskt op.org/ show_bug. cgi?id= 11617
https:/
But I was probably wrong about "xorg starts correctly" as it doesn't start and it behaves like Timo described (100% CPU).
So I correct my previous statement and re-post my infos (as attachments seem corrupted in the other bug).
Computer:
Toshiba 1800-100 and Trident Ai1 (for
more info see the attached X org log and dmesg).
Not-working Distributions tested:
- Ubuntu 7.10 - Xorg 7.2
- Debian unstable - Xorg 7.3
- Fedora 7 - Xorg 7.2
Working distros:
- Debian 4.0 - Xorg 7.1
- a lot of other distros with Xorg <= 7.1
Other reports: /bugs.launchpad .net/ubuntu/ +source/ xserver- xorg-video- trident/ +bug/154069 ubuntuforums. org/showthread. php?t=587668
https:/
http://
Workaround:
Add Option "NoDDC" in the "Device" section of xorg.conf
Bugs probably related (or duplicates): /bugs.freedeskt op.org/ show_bug. cgi?id= 3946
https:/
Working combinations of xorg.conf:
driver trident + option noddc
Not working combinations:
driver trident without option noddc
driver vesa + option noddc
Going to attach some logs.