Recovery mode in lucid fails to load recovery menu

[Doug McMahon]

Binary package hint: grub2

Booting to recovery mode in updated lucid (03/21), hangs at black screen instead of loading the recovery menu
(the initial text based recovery 'seems' to work as normal

ProblemType: Bug
Architecture: i386
Date: Sun Mar 21 13:30:00 2010
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100211.1)
Package: grub2 (not installed)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: grub2
Uname: Linux 2.6.32-16-generic i686

[Doug McMahon (mc3man)]

Dual boot with 2 parallel installs, one with nouveau/plymouth, one with nvidia-current/no plymouth - only occurs on the nouveau/plymouth install

[GuyR (guy-rouger)]

Occurs on ACer Aspire T650 (radeon xpress 200).
No more blue screen to select which type of recovery.

[Doug McMahon (mc3man)]

restored plymouth to nvidia-current install (it now works fine) and recovery menu comes up, - so it only fails to load with nouveau.

The binary hint of grub2 may be incorrect

[Colin Watson (cjwatson)]

plymouth may not be the right package either, but I think it's closer than grub2.

[Scott James Remnant (Canonical) (canonical-scott)]

Can't see any reason that this would be a plymouth issue; since recovery mode doesn't have "splash" in its arguments, Plymouth should never show a splash screen

[GuyR (guy-rouger)]

I confirm, when uninstalling:
- libdrm-nouveau1
- plymouth
- plymouth-X11

All is working well, back to standard blue screen for recovery mode.

[Doug McMahon (mc3man)]

While probably not that helpful an 'unfriendly recovery' also fails at same point and way, while the same does work with nvidia-current
(......., runs a fsck, reloads screen, root shell prompt

[Doug McMahon (mc3man)]

You can scratch the above - it takes 2 attempts at recovery mode with friendly-recovery removed, then it works as expected, so I only see the issue with the combo of nouveau and friendly-recovery

[emarkay (mrk)]

Marked my bug a dupe:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/543673

[Doug McMahon (mc3man)]

if it was just me i'd chalk it up to a local glitch, but anyway recovery mode with the recovery menu is now working fine with nouveau.
Why don't know - basically just removed friendly-recovery, rebooted a couple of times (normal and recovery), removed plymouth and rebooted a few times, re-installed friendly-recovery, rebooted, re-installed plymouth, tested and works fine thru several attempts. Then re-installed plymouth-x11 and still is good

[papukaija (papukaija)]

For me it hangs with an error message saying something like this: "could not write to pipe".

[papukaija (papukaija)]

I disabled the nouveau driver and now I get to the recovery mode if I switch to an other virtual console (propably tty2). However the menu entries do nothing.

[Michael Vogt (mvo)]

It seems there are (at least) two issues:
 - the recovery menu is on the wrong tty
 - ENTER is no longer working

[Michael Vogt (mvo)]

Oddly enough removing friendly-recovery fixes the tty and ENTER problem. Then sulogin is run. But all that does is really a setsid() AFAICS and doing that for friendly-recovery does not help with the bug.

[papukaija (papukaija)]

This bus seems to be fixed in ibdrm-nouveau1 (2.4.18-1ubuntu3) and libdrm2 (2.4.18-1ubuntu3). Please confirm.

[papukaija (papukaija)]

Fixed in ibdrm-nouveau1 (2.4.18-1ubuntu3) and libdrm2 (2.4.18-1ubuntu3). Please reopen if you can reproduce this bug.

[papukaija (papukaija)]

*libdrm

[Marcelo Ruiz (marcelo-javier-ruiz-yahoo)]

this still happens in the Toshiba Satellite M640. Would this be related to the fact that this computer has an hybrid (Intel/Nvidia) graphics card?

[David Robert Lewis (afrodeity)]

I have a similar problem in oneiric. Recovery-mode boots into a simple root prompt, with no friendly-recovery menu.