[Bug 394316] New: X.org doesn't start in failsave mode
https://bugzilla.novell.com/show_bug.cgi?id=394316 Summary: X.org doesn't start in failsave mode Product: openSUSE 11.0 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: X.Org AssignedTo: sndirsch@novell.com ReportedBy: suse-beta@cboltz.de QAContact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Created an attachment (id=217967) --> (https://bugzilla.novell.com/attachment.cgi?id=217967) Xorg.0.log Because of the broken kernel in Factory (post-beta3), I had to boot in failsave mode. Bad side effect of this: X.org doesn't start anymore, probably because of (WW) Open ACPI failed (/var/run/acpid.socket) (Connection refused) The full Xorg.0.log is attached. I tried with several xorg.conf files (dualhead and only one screen), and always got the same result. Workaround: boot with the "normal" boot entry + acpi=off works. "normal" boot entry cmdline: kernel /boot/vmlinuz-2.6.25.4-2-default root=/dev/disk/by-id/scsi-SATA_ST94011A_3KW2C49P-part5 resume=/dev/sda2 splash=silent showopts vga=0x342 (+ acpi=off) failsave boot entry cmdline: kernel /boot/vmlinuz-2.6.25.4-2-default root=/dev/disk/by-id/scsi-SATA_ST94011A_3KW2C49P-part5 showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off x11failsafe vga=0x342 (I just wonder what x11failsave should do...) I'll keep the broken kernel for some days in case you need something tested. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c1
Stefan Dirsch
(I just wonder what x11failsave should do...) If x11failsafe is set; then if /etc/X11/xorg.conf.install exists ; then X is started with the settings from installation (usually fbdev driver) else X is not started at all
Your logfile uses (++) Using config file: "/tmp/sax2-4440/xorg.conf" This means that it is a logfile from some SaX2 installation and not from failsafe boot at all. Please attach the correct logfile. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=394316
User suse-beta@cboltz.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c2
Christian Boltz
if /etc/X11/xorg.conf.install exists ; then X is started with the settings from installation (usually fbdev driver) else X is not started at all
Ah, then we have already found the reason: I did some cleanup in /etc/X11/ (I have always several config files around because of the dualhead setup I'm using) and also moved away xorg.conf.install. Therefore it's not surprising that X doesn't start in failsave mode ;-) I'd like to propose a small patch to /etc/init.d/xdm: --- /etc/init.d/xdm.orig 2008-05-25 12:01:31.000000000 +0200 +++ /etc/init.d/xdm 2008-05-25 12:02:13.000000000 +0200 @@ -166,6 +166,7 @@ case "$1" in if [ -f /etc/X11/xorg.conf.install ]; then export XORGCONFIG=xorg.conf.install else + echo "/etc/X11/xorg.conf.install does not exist!" >&2 rc_status -u rc_exit fi Simply print an error message _why_ it fails ;-)
This means that it is a logfile from some SaX2 installation and not from failsafe boot at all. Please attach the correct logfile.
Oops, sorry. However I think attaching the logfile is obsolete now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c3
--- Comment #3 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c4
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=394316
User suse-beta@cboltz.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c5
Christian Boltz
And what's the use of this error message? When xorg.conf.install is gone, it cannot be restored without reinstalling the system.
The use of this error message is: A more experienced user sees _why_ X doesn't start. (Newbies are irrelevant here IMHO - they won't delete xorg.conf.install ;-) I know that xorg.conf.install can't be restored automatically (and don't even expect it) - but giving the user a hint why something fails is always a good thing.
So this error message would only confuse the customer. The graphical failsafe mode is new since openSUSE 11.0, so most people expect text mode anyway.
I think the current behaviour (fail silently) causes more confusion ;-) Agreed, most people expect text mode. But they also expect that "rcxdm start" starts X... Now compare the two possibilities on "rcxdm start": a) current behaviour: "unused - hmm, what's wrong?! X always worked, even with failsave boot parameters. Does X.org require ACPI now??? Or ...???" b) with the proposed error message: "Ah, they even made failsave mode using a failsave X config. Nice. I'll move xorg.conf.install back to its original location." (Or: "Silly me, I deleted xorg.conf.install :-(" - but you won't get a bugreport on the issue.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c6
Stefan Dirsch
But they also expect that "rcxdm start" starts X...
Thanks. I now finally understood your bugreport. :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=394316
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=394316
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c7
--- Comment #7 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=394316
User sndirsch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=394316#c8
Stefan Dirsch
participants (1)
-
bugzilla_noreply@novell.com