How to recover via recovery mode

My Opensuse 12.1 hangs during boot shortly before the login screen after i have asked Yast to update Firefox.
I can boot into recovery mode. But how can i get my setup fixed so i can boot normal again ?

Many thanks for your advice.

I doubt that’s directly caused by updating Firefox.
But where did you update Firefox from? There are no updates for 12.1 any more.

Since recovery mode works, it’s probably a graphics driver issue.
So please start by telling what graphics card you use and what driver.

What do you mean with “hang”?
Can you get to text mode and login, if you press ESC or Ctrl+Alt+F1?

Please do a normal boot, then reboot to recovery mode and post the file /var/log/Xorg.0.log.old (upload to some pasting/sharing site like http://susepaste.org and post a link).

And please post your repo list. If the update really triggered the problem, it’s likely that some packages from other than the standard repos got installed/updated as well, breaking your system.

zypper lr -d

And a final note: 12.1 is out of support and end-of life for over 1.5 years already. You probably should consider upgrading to a supported version.
https://en.opensuse.org/Lifetime

On 2014-10-27 11:56, donseppo wrote:
>
> My Opensuse 12.1 hangs during boot shortly before the login screen after
> i have asked Yast to update Firefox.

12.1 is obsolete and non maintained. Current version is 13.1

> I can boot into recovery mode. But how can i get my setup fixed so i can
> boot normal again ?

Depends on what messages it prints about what problem dumps it to
recovery mode…


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

You seem to confuse “recovery mode” with “emergency mode” again… :wink:

If I didn’t completely misunderstand the OP, the system boots fine when he chooses to boot “Recovery Mode” in grub2’s “Advanced Options”, i.e. what the “failsafe mode” entry in grub1 did.
But it hangs (without going to emergency mode) when booting the standard boot menu entry.

On 2014-10-27 20:06, wolfi323 wrote:
>
> robin_listas;2671410 Wrote:

>> Depends on what messages it prints about what problem dumps it to
>> recovery mode…
>>
> You seem to confuse “recovery mode” with “emergency mode” again… :wink:

Yes, possibly… Aparently I can’t remember the name of each mode O:-)

Ah, you forget “rescue mode” :stuck_out_tongue:

> If I didn’t completely misunderstand the OP, the system boots fine when
> he chooses to boot “Recovery Mode” in grub2’s “Advanced Options”, i.e.
> what the “failsafe mode” entry in grub1 did.
> But it hangs (without going to emergency mode) when booting the standard
> boot menu entry.

Failsafe, rescue, emergency, recovery… and you want me to remember all
that? :stuck_out_tongue:


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

… I cannot remember what I had for breakfast.

Or, wait … did I have breakfast yet? lol!

Thanks for your advices, however i can´t get it to textmode neither via ESC nor ctrl-Alt-F1.
from xorg0.log.old i can see it is a radeon HD 5450.

 6.779] (II) fglrx(0): Eyefinity capable adapter detected.
 6.779] (II) fglrx(0): Adapter ATI Radeon HD 5450      has 3 configurable heads and 2 displays connected.
 6.779] (==) fglrx(0):  PseudoColor visuals disabled
 6.779] (II) Loading sub module "ramdac"
 6.779] (II) LoadModule: "ramdac"
 6.779] (II) Module "ramdac" already built-in
 6.779] (==) fglrx(0): NoDRI = NO
 6.779] (==) fglrx(0): Capabilities: 0x00000000
 6.779] (==) fglrx(0): CapabilitiesEx: 0x00000000
 6.779] (==) fglrx(0): OpenGL ClientDriverName: "fglrx_dri.so"
 6.779] (==) fglrx(0): UseFastTLS=0
 6.779] (II) fglrx(0): Shadow Primary option: ShadowPrimary is enabled
 6.780] (--) Depth 24 pixmap format is 32 bpp
 6.780] (EE) fglrx(0): atiddxDriScreenInit failed. Probably kernel module missing or incompatible. 
 6.780] (WW) fglrx(0): ***********************************************************
 6.780] (WW) fglrx(0): * DRI initialization failed                               *
 6.780] (WW) fglrx(0): * kernel module (fglrx.ko) may be missing or incompatible *
 6.780] (WW) fglrx(0): * 2D and 3D acceleration disabled                         *
 6.780] (WW) fglrx(0): ***********************************************************
 6.780] (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x10000000

Meanwhile i removed firefox, however, as suspected it still hangs.
I see the textbox, where it says loading ramdisk, then the green screen with the chameleon pops up, the white balls circle around , but shortly before the reach the center of the chameleon, as they usually did, the screen freezes and even ctrl-alt-del has no more effect. Only hard poweroff-poweron will bring it back to life.

Would it make sense to install 13.1 over the existing 12.1 ?

regards,

donseppo

On 2014-11-01 10:56, donseppo wrote:

> 6.780] (EE) fglrx(0): atiddxDriScreenInit failed. Probably kernel
> module missing or incompatible.

This may be the root trouble. Probably something related to the kernel,
or to your video driver, got updated together with your FF update.

> Would it make sense to install 13.1 over the existing 12.1 ?

IMHO, yes.

Or upgrade it, using the DVD upgrade method. That’s what I would try first.

Even if your 12.1 can be repaired, few people may try to correlate to
your problem here, as we use more modern versions.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

Did upgrade to 13.1, but the issue remains.
i can switch to text with ctrl-alt-f1 and it stops after loading name service ?!?
I tested my graficsdriver with glxgears and all looks fine

Does selecting failsafe/recovery mode in the boot menu still help? (in “Advanced Options” if using grub2)

Have you tried to uninstall fglrx?
Do that and try to rename/remove /etc/X11/xorg.conf if still there to use the “radeon” driver.

If you install the driver again afterwards, it should work probably.
I would recommend the packages from the repo:
https://en.opensuse.org/SDB:AMD_fglrx

How did you install the driver originally? Which version?
An older version might not work on openSUSE 13.1.

On 2014-11-01 21:36, donseppo wrote:
>
> Did upgrade to 13.1, but the issue remains.
> i can switch to text with ctrl-alt-f1 and it stops after loading name
> service ?!?
> I tested my graficsdriver with glxgears and all looks fine

I don’t understand. You do reach graphics mode, as you can test with
glxgears. What are the exact symptoms now? Please describe in more detail.


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)