Can only use opensuse in GUI rescue mode?? Was working fine for months

The only way I can no use my computer is to select the Advanced options from grub2 and select rescue mode.
This boots me right to my normal desktop but the graphics driver is disabled, but it works.

The normal boot option starts plymouth (green gecko on right of screen) then some lines of text fly by ending with the network startup at top of screen.
Then I am sitting at a text based login console.

So far I have checked the dmesg logs and everything looks normal. The /var/log/messages looks normal too although it is 35000 lines long?? I also checked /var/log/zypp/history and there were no updates recently that should have screwed anything up.

It is almost like kdm is not starting, if that is possible.

One thing I do remember is accidentally turning the power off while it was asleep, I though I was turning it on but it was only asleep and I powered it off by accident.

What should I check next or do next?

This is opensuse 13.1 with KDE and latest updates.

What video and driver?

Press esc as boot starts so you can see the startup text

Thanks for the reply,

AMD proprietary driver, there are no failures on the esc boot messages.

In my op I inaccurately stated I am booting in rescue mode but it is recovery mode.

The kernel was updated to version 3.11.10 on 6 February. Have you installed the proprietary driver since then? If not, and your kernel has been updated, you will need to.

The box was working fine on 4/20 and broken when started on 4/21, there were no updates except for some vlc stuff from pacman repo.

I have been running the 3.11.10 kernel since it came out and at that time I updated the AMD drivers. Just for giggles I just re-installed the AMD drivers and I have the same issue.

I just boot into a console session unless I choose recovery mode. Its like KDM is not getting triggered to start or something.

There are no errors on boot that I can see, everything works in console mode as well.

Could there be some setting that is now telling plymouth to start in console mode for the default user?

I am at a loss, maybe I will create a new user?

You should fall back to the login screen if something was wrong with your user account.
And the vlc update should not cause something like this either.

Please do a normal boot, and after it fails reboot to recovery mode and post /var/log/Xorg.0.log.old.

I think you may be on to something

This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See for git access instructions.
X.Org X Server (1.14.4 RC 1)
Release Date: 2013-10-26
     5.420] X Protocol Version 11, Revision 0
     5.420] Build Operating System: openSUSE SUSE LINUX
     5.420] Current Operating System: Linux linux-aa3c 3.11.10-7-desktop #1 SMP PREEMPT Mon Feb 3 09:41:24 UTC 2014 (750023e) x86_64
     5.420] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.11.10-7-desktop root=UUID=3c81491e-7da8-45f7-bc8d-1d0f7843d28b splash=silent quiet showopts
     5.420] Build Date: 19 December 2013  01:42:00PM
     5.420] Current version of pixman: 0.30.2
     5.420]     Before reporting problems, check
    to make sure that you have the latest version.
     5.420] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
     5.420] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Apr 22 11:31:22 2014
     5.420] (==) Using config file: "/etc/X11/xorg.conf"
     5.420] (==) Using config directory: "/etc/X11/xorg.conf.d"
     5.420] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
     5.421] (==) ServerLayout "aticonfig Layout"
     5.421] (**) |-->Screen "aticonfig-Screen[0]-0" (0)
     5.421] (**) |   |-->Monitor "aticonfig-Monitor[0]-0"
     5.421] (**) |   |-->Device "aticonfig-Device[0]-0"
     5.421] (==) Automatically adding devices
     5.421] (==) Automatically enabling devices
     5.421] (==) Automatically adding GPU devices
     5.421] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist.
     5.421]     Entry deleted from font path.
     5.421] (==) FontPath set to:
     5.421] (==) ModulePath set to "/usr/lib64/xorg/modules/updates,/usr/lib64/xorg/modules"
     5.421] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
     5.421] (II) Loader magic: 0x803c20
     5.421] (II) Module ABI versions:
     5.421]     X.Org ANSI C Emulation: 0.4
     5.421]     X.Org Video Driver: 14.1
     5.421]     X.Org XInput driver : 19.1
     5.421]     X.Org Server Extension : 7.0
     5.421] (II) xfree86: Adding drm device (/dev/dri/card0)
     5.422] (--) PCI: (0:0:2:0) 8086:0162:1849:0162 rev 9, Mem @ 0xf7800000/4194304, 0xd0000000/268435456, I/O @ 0x0000f000/64
     5.422] (--) PCI:*(0:1:0:0) 1002:6758:174b:e194 rev 0, Mem @ 0xe0000000/268435456, 0xf7e20000/131072, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
     5.422] Initializing built-in extension Generic Event Extension
     5.422] Initializing built-in extension SHAPE
     5.422] Initializing built-in extension MIT-SHM
     5.422] Initializing built-in extension XInputExtension
     5.422] Initializing built-in extension XTEST
     5.422] Initializing built-in extension BIG-REQUESTS
     5.422] Initializing built-in extension SYNC
     5.422] Initializing built-in extension XKEYBOARD
     5.422] Initializing built-in extension XC-MISC
     5.422] Initializing built-in extension SECURITY
     5.422] Initializing built-in extension XINERAMA
     5.422] Initializing built-in extension XFIXES
     5.422] Initializing built-in extension RENDER
     5.422] Initializing built-in extension RANDR
     5.422] Initializing built-in extension COMPOSITE
     5.422] Initializing built-in extension DAMAGE
     5.422] Initializing built-in extension MIT-SCREEN-SAVER
     5.422] Initializing built-in extension DOUBLE-BUFFER
     5.422] Initializing built-in extension RECORD
     5.422] Initializing built-in extension DPMS
     5.422] Initializing built-in extension X-Resource
     5.422] Initializing built-in extension XVideo
     5.422] Initializing built-in extension XVideo-MotionCompensation
     5.422] Initializing built-in extension XFree86-VidModeExtension
     5.422] Initializing built-in extension XFree86-DGA
     5.422] Initializing built-in extension XFree86-DRI
     5.422] Initializing built-in extension DRI2
     5.422] (II) "glx" will be loaded by default.
     5.422] (II) LoadModule: "glx"
     5.424] (II) Loading /usr/lib64/xorg/modules/updates/extensions/
     5.424] (II) Module glx: vendor="Advanced Micro Devices, Inc."
     5.424]     compiled for 6.9.0, module version = 1.0.0
     5.424] Loading extension GLX
     5.424] (II) LoadModule: "fglrx"
     5.429] (II) Loading /usr/lib64/xorg/modules/drivers/
     5.496] (II) Module fglrx: vendor="FireGL - AMD Technologies Inc."
     5.496]     compiled for, module version = 13.25.5
     5.496]     Module class: X.Org Video Driver
     5.497] (II) Loading sub module "fglrxdrm"
     5.497] (II) LoadModule: "fglrxdrm"
     5.497] (II) Loading /usr/lib64/xorg/modules/linux/
     5.499] (II) Module fglrxdrm: vendor="FireGL - AMD Technologies Inc."
     5.499]     compiled for, module version = 13.25.5
     5.499] (II) AMD Proprietary Linux Driver Version Identifier:13.25.5
     5.499] (II) AMD Proprietary Linux Driver Release Identifier: 13.251                               
     5.499] (II) AMD Proprietary Linux Driver Build Date: Dec  6 2013 15:19:03
     5.499] (++) using VT number 7

     5.500] (WW) Falling back to old probe method for fglrx
     5.510] (EE) 
     5.510] (EE) Backtrace:
     5.515] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x3d) [0x585aad]
     5.515] (EE) 1: /usr/bin/Xorg (0x400000+0x189819) [0x589819]
     5.515] (EE) 2: /lib64/ (0x7faadfe62000+0xf9f0) [0x7faadfe719f0]
     5.515] (EE) 3: /lib64/ (0x7faadecb4000+0x94d07) [0x7faaded48d07]
     5.515] (EE) 4: /usr/lib64/xorg/modules/drivers/ (amdPcsEngine_CreateKey+0x32) [0x7faadd19fd72]
     5.516] (EE) 5: /usr/lib64/xorg/modules/drivers/ (0x7faadc8e0000+0x8c0a08) [0x7faadd1a0a08]
     5.516] (EE) 6: /usr/lib64/xorg/modules/drivers/ (amdPcsFile_PopulateDatabase+0x28) [0x7faadd1a0288]
     5.516] (EE) 7: /usr/lib64/xorg/modules/drivers/ (amdPcsEngine_InitDatabase+0x24) [0x7faadd19f564]
     5.516] (EE) 8: /usr/lib64/xorg/modules/drivers/ (0x7faadc8e0000+0x8bf3c9) [0x7faadd19f3c9]
     5.516] (EE) 9: /usr/lib64/xorg/modules/drivers/ (0x7faadc8e0000+0x8beb12) [0x7faadd19eb12]
     5.516] (EE) 10: /usr/lib64/xorg/modules/drivers/ (xdl_xs114_atiddxProbe+0x1a2) [0x7faadce35162]
     5.516] (EE) 11: /usr/lib64/xorg/modules/drivers/ (atiddxProbe+0xd) [0x7faadcc9cbcd]
     5.516] (EE) 12: /usr/bin/Xorg (xf86BusConfig+0x46) [0x46fda6]
     5.516] (EE) 13: /usr/bin/Xorg (InitOutput+0x8ae) [0x47da3e]
     5.516] (EE) 14: /usr/bin/Xorg (0x400000+0x2bfcb) [0x42bfcb]
     5.516] (EE) 15: /lib64/ (__libc_start_main+0xf5) [0x7faadecd5be5]
     5.516] (EE) 16: /usr/bin/Xorg (0x400000+0x2c501) [0x42c501]
     5.516] (EE) 
     5.516] (EE) Segmentation fault at address 0x0
     5.516] (EE) 
Fatal server error:
     5.516] (EE) Caught signal 11 (Segmentation fault). Server aborting
     5.516] (EE) 
     5.516] (EE) 
Please consult the The X.Org Foundation support 
 for help. 
     5.516] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
     5.516] (EE) 

Hmmm, what to do?

Formatting in the code tags looks bad but I just copy from Kate?? Hopefully you can read it.

Hmmm, what to do?

The segfault could just possibly be memory/register corruption on the graphics card. On the basis of trying the easy remedy before thinking too hard, try powering the machine off, and disconnecting it from the mains supply (Switch it off at the wall). If it is a laptop, remove the battery. Wait a minute or two for any large capacitors to drain (have a coffee/tea or something). Then reconnect and power on. See what happens.
Note. On most modern machines switching off without physically disconnecting leaves the motherboard powered and the graphics, network subsystems etc. do not get a hard reset.

Ok, I was thinking the same sort of thing. I took the machine offline took it to the workbench and proceeded to clean out all the dust and crud (there was a bunch in there) and then started again, same problem.
It is starting to make me think it is some kind of hardware issue.

Would recovery work good if the graphics card was going bad?

I just re-installed the AMD drivers from Sebastian’s script and still have the same errors in Xorg.

I hate to flail about with out any direction but this is my work box and I am kinda stuck till I get it fixed.

I am going to wait for some feedback but my next thought is to take the card out and try and run on the intel graphics but I am not sure how successful that would be.
I wish I had another AMD card to swap in the slot but I do not.

TO go back to Intel make sure that any /etc/X11/xorg.conf file is renamed Also may check the files in /etc/X11/xorg.conf.d to be sure no driver is specified there

Great advise thank you, I just switched the MB over to boot Intel (as I discovered the mei module was being loaded anyway) but it did fail because Xorg is still looking for flgrx.

I will try your suggestions and see what happens.

Rebooting now, after renaming xorg.conf.

Ok, I am back to full resolution finally. :good: The Intel graphics and now my pc seem to be working normally again. Thanks to all that took the time to help. :slight_smile:

So what does this mean, is my AMD card broken?


I had a NVIDIA card go bottom up on me a few weeks ago.

Did you get a new card yet, what was it?

Off topic now but wow do the fonts look different under Intel graphics card, not sure how to describe it. Maybe the fonts get changed when Xorg changes, its like the fonts went on a huge diet.

Had an older NVIDIA laying about and used that. The card that went was a newer very cheap NVIDIA the older 5+ years card as about the same specs LOL. I prefer NVIDIA but to each his own.

I have NVIDIA in another box and like it. It is crazy what the differences are between graphics cards though. For example, I just started VirtualBox to see how it would work under Intel and when I passed my mouse over the main settings they were highlighted, that never happened under my AMD card, weird.

What I will look for in this machine is a silent card with loads of memory, what ever manufacture provides those specs will get my money.

Same here, I have a definite preference for the nVidia cards.


I wanted to follow up on this thread in case it helps someone else.

It turns out the conclusions about a dead video card were not warranted and the video card is working fine.

I found a good way to test the card was to boot an openSUSE live dvd and check out the desktop effects in KDE to see if they are working and running in openGL. This helped me figure out the hardware was working fine.
I would then suggest using a something like to check your memory, harddrives etc…
All the hardware in my system checked out fine and so I came to the conclusion that it was some software glitch.

Story follows:
To add to the oddity of the OS booting problems in my OP I ended up with a completely non-bootable system. This happened after I pulled out a memory stick to write down the specs ( I was going to buy more memory at the same time I was going to purchase a new video card, this never happened).
So after I pulled the memory to look at it there was a boot loop after the system hit plymouth, the gecko would appear for a split second and then a reboot. I re-seated the memory chip and various other things but still boot loop.
I finally started up with the live DVD and everything worked good and hence my conclusion that it was some software glitch.

After some long consideration, I decided to move to a new linux distro that will hopefully not fall down as much as openSUSE did for me. As I reflected back I realized that I had already re-built my system several (3) over the last 1.5 years all for the same reason, booting problems. This is just too much work and so I am trying some other KDE based linux with the hopes it will work out better.