|
Bugzilla – Full Text Bug Listing |
| Summary: | X does not start after installation | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Richard Bos <richard.bos> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | VERIFIED FIXED | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Normal | ||
| Priority: | P2 - High | ||
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Beta-Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
xorg configuration file
X11 log file xfdebug log file after running 20 minutes Xorg log with "noaccel" option, right after boot. Altered xorg.conf file with noaccel |
||
|
Description
Richard Bos
2005-08-13 21:28:42 UTC
Created attachment 45978 [details]
xorg configuration file
Created attachment 45979 [details]
X11 log file
Please call xf86debug and attach the logfile. Stefan, xf86debug has been running for 10 minutes without quiting... The log cotains the usual X startup message, no debugging. All this time the X window (<ctrl)F7) shows the standard X gray background with a cross as pointer. Attaching the log file /tmp/xf86debug..... anyway. Created attachment 45980 [details]
xfdebug log file after running 20 minutes
Hmm ... then the Xserver doesn't crash immediately, but after some interaction with some Xclient. Ok. Please try adding Option "noaccel" to 'Section "Device"' of your /etc/X11/xorg.conf and attach logfile. No difference :( The diff to xorg.conf is: --- xorg.conf.old 2005-08-14 14:29:32.000000000 +0200 +++ xorg.conf 2005-08-14 11:36:31.000000000 +0200 @@ -205,6 +205,7 @@ Section "Device" Driver "mga" Identifier "Device[0]" VendorName "Matrox" + Option "noaccel" EndSection X is staying at the gray back ground with a cross as pointer. Of course after disabling acceleration support the Xserver does not crash immediately. Please forget xf86debug for now for testing. I would like to see the logfile when using this option. Created attachment 45981 [details]
Xorg log with "noaccel" option, right after boot.
Xorg log with "noaccel" option, right after boot.
I couldn't verify that you set noaccel by reading the logfile. To make sure please attach new xorg.conf. Created attachment 45998 [details]
Altered xorg.conf file with noaccel
config file looks correct. Hmm ... Looks like the xaa module is never loaded - no matter whether noaccel is set or not. Strange. BTW, does the Xserver work now when noaccel is set? The Xserver does not work. There is not difference on VT07 when init 5 or init 3 are used. I'll give it a try with our G200. Unfortunately our G200 no longer works. :-( I'll try to reproduce this problem (at least the unresolved symbol issue) with a G450 now. Hmm ... I cannot reproduce neither the "unresolved symbol" issue nor the crashing Xserver. The "xaa" module is loaded as well. The last hope would be to try Option "NoHal" Around the time you made the last update, I started my holiday! It's unfortenate that you did not make the suggestion a day earlier, as it just works!!! It's just booting into kde :)) Now all I have to do, is to download suse10b4 and try it again. Is there something that can be done, during installation, that this setting (NoHal) is included in the xorg.conf automatically? FYI: I removed the noaccel option. So now I have a xorg.conf with NoHal and without noaccel. Added this option now to our database. Will be fixed for RC1. For Beta4 after installation reboot into runlevel 3 and edit your /etc/X11/xorg.conf. Stefan, :)) RC1 installed without (unexpected) manually intervention. |