When I first boot Windows XP and then Knoppix 5.2 Live (which was attached to the c't magazine no. 7/2007) everything 3d works fine. But when I DIRECTLY boot Linux, my screen gets black when trying to init the GUI. It won't even work when beryl is disabled. To fix this, I commented out the lines # Load "dri" # Load "glx" in my /etc/X11/xorg.conf. This gives me a complete 2d working station. Changing Section "Device" Identifier "ATI Technologies, Inc. RV280 [Radeon 9200 PRO]" Driver "ati" BusID "PCI:1:0:0" EndSection to Section "Device" Identifier "ATI Technologies, Inc. RV280 [Radeon 9200 PRO]" Driver "radeon" BusID "PCI:1:0:0" EndSection results in an error, which in my oppinion is caused due to the same reasons (whoch I don't know).
Please attach (as opposed to paste) X log files for all cases.
Created attachment 9429 [details] /var/log files after rebooting WindowsXP
Created attachment 9430 [details] /var/log files after booting Knoppix 5.2 directly
The Xorg.0.log after direct boot appears truncated; can you log into the machine remotely after this happens, or is the machine at least pingable? Can you get at the X server's stderr output and/or the kernel output?
Created attachment 9470 [details] Xorg.0.log which is (hopefully) not truncated. I copied the log file with sshfs when the computer was running.
(In reply to comment #5) > Created an attachment (id=9470) [details] > Xorg.0.log which is (hopefully) not truncated > I am sorry, this is the wrong file. Please IGNORE my previous reply! I'll submit the right one soon...
This is a long shot, but I remember on my old laptop I sometimes had issues with DRI. It seemed like some form of initialization error, the first time I would start glxgears or glxinfo, it would fail, but when I tried again it all worked perfectly, perhaps this issue is still lurking around. Unfortunately I can't provide any debug info since I switched laptop since then, but it was an old radeon card using the open source radeon driver.
Created attachment 9521 [details] Xorg.0.log when booted directly
> The Xorg.0.log after direct boot appears truncated; can you log into the > machine remotely after this happens, or is the machine at least pingable? Can > you get at the X server's stderr output and/or the kernel output? Sorry for the delayed answer. Here's another Xorg.0.log, but I think it is truncated again. How can I get the complete file? Yes, the machine is pingable after the screen is gone black, but I can't establish a ssl or ftp connection to the machine. How can I get X server's stderr output or kernel output?
(In reply to comment #9) > Sorry for the delayed answer. Here's another Xorg.0.log, but I think it is > truncated again. How can I get the complete file? Maybe I should add how I came to the (truncated) Xorg.0.log file: I booted with the parameter "knoppix 2" which starts the system in runlevel 2. Then I entered "X -probeonly" which generates the log file and returns to the console from where I can copy the file. I chose runlevel 2 because I didn't see another possibility to get the log file; When I boot with "knoppix 3d" I can't do anything after the screen goes black: no CTRL+ALT+BACKSPACE nor CTRL+ALT+F1/F2 to switch to the console.
Bugzilla Upgrade Mass Bug Change NEEDSINFO state was removed in Bugzilla 3.x, reopening any bugs previously listed as NEEDSINFO. - benjsc fd.o Wrangler
Closing for inactivity, please reopen if you still have issue with recent xorg, kernel and x86-video-ati.
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.