Hi Steve, sorry for my late reply (I was at a sprint). I agree with your
conclusions but I'd like to partially revert your changes.
You removed a feature which allowed packagers to blacklist single card
ids to prevent them from using the boot splash in case of nasty
interactions with the NVIDIA
** Changed in: fglrx-installer (Ubuntu)
Status: Triaged = Fix Released
** Changed in: fglrx-installer-updates (Ubuntu)
Status: Triaged = Fix Released
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: Triaged = Fix Released
** Changed in:
This bug was fixed in the package nvidia-graphics-drivers -
280.13-0ubuntu5
---
nvidia-graphics-drivers (280.13-0ubuntu5) oneiric; urgency=low
* Drop /usr/share/grub-gfxpayload-lists/blacklist handling; there's
nothing about binary drivers in particular that requires
Alberto, please revert these blacklists. Blacklisting the cards in grub
causes a significant regression to the user experience when NOT booting
in recovery mode - systems that had a perfectly working flicker-free
boot from grub to plymouth even when using the binary nvidia drivers now
have a text
Also, note that this issue is NOT specific to binary drivers! I can
reproduce the problem on a system with an intel video card when
gfxpayload=keep. The issue is that during a normal boot, plymouth
handles the transition from graphics mode to text mode for the VT
(plymouth show-splash /
** Branch linked: lp:~ubuntu-core-dev/ubuntu/oneiric/grub2/oneiric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about this bug
I committed this before noticing that Steve had assigned the bug to
himself :-)
** Changed in: grub2 (Ubuntu)
Status: Triaged = Fix Committed
** Changed in: grub2 (Ubuntu)
Assignee: Steve Langasek (vorlon) = Colin Watson (cjwatson)
--
You received this bug notification because you
This bug was fixed in the package grub2 - 1.99-12ubuntu5
---
grub2 (1.99-12ubuntu5) oneiric; urgency=low
* Never use 'set gfxpayload=keep' in recovery mode (LP: #854967).
-- Colin Watson cjwat...@ubuntu.com Sat, 01 Oct 2011 10:30:39 +0100
** Changed in: grub2 (Ubuntu)
** Branch linked: lp:ubuntu/grub2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about this bug go to:
** Patch added: patch for bugs 864149 and 854967
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2494190/+files/nvidia-graphics-864149%2C854967.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The attachment patch for bugs 864149 and 854967 of this bug report has
been identified as being a patch in the form of a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. In the event that this is in
fact not a
** Also affects: fglrx-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: fglrx-installer-updates (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fglrx-installer (Ubuntu)
Status: New = In Progress
** Changed in: fglrx-installer-updates
This bug was fixed in the package nvidia-graphics-drivers-96-updates -
96.43.20-0ubuntu4
---
nvidia-graphics-drivers-96-updates (96.43.20-0ubuntu4) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of
This bug was fixed in the package nvidia-graphics-drivers-173 -
173.14.30-0ubuntu7
---
nvidia-graphics-drivers-173 (173.14.30-0ubuntu7) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of hyphens (LP:
This bug was fixed in the package nvidia-graphics-drivers-173-updates -
173.14.30-0ubuntu4
---
nvidia-graphics-drivers-173-updates (173.14.30-0ubuntu4) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of
This bug was fixed in the package nvidia-graphics-drivers-updates -
280.13-0ubuntu4
---
nvidia-graphics-drivers-updates (280.13-0ubuntu4) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of hyphens (LP:
This bug was fixed in the package fglrx-installer-updates -
2:8.881-0ubuntu5
---
fglrx-installer-updates (2:8.881-0ubuntu5) oneiric; urgency=low
* debian/rules, debian/modaliases/fglrx_supported:
- Make sure that the module alias is always correct and
uses underscores
This bug was fixed in the package fglrx-installer - 2:8.881-0ubuntu3
---
fglrx-installer (2:8.881-0ubuntu3) oneiric; urgency=low
* debian/rules, debian/modaliases/fglrx_supported:
- Make sure that the module alias is always correct and
uses underscores instead of hyphens
This bug was fixed in the package nvidia-graphics-drivers -
280.13-0ubuntu4
---
nvidia-graphics-drivers (280.13-0ubuntu4) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of hyphens (LP: #855396).
-
This bug was fixed in the package nvidia-graphics-drivers-96 -
96.43.20-0ubuntu5
---
nvidia-graphics-drivers-96 (96.43.20-0ubuntu5) oneiric; urgency=low
* debian/rules:
- Make sure that the module alias is always correct and
uses underscores instead of hyphens (LP:
** Tags added: kubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about this bug go to:
** Changed in: nvidia-graphics-drivers-173-updates (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: (unassigned) = Alberto Milone (albertomilone)
** Changed in: nvidia-graphics-drivers-96-updates (Ubuntu)
I testing Kubuntu, Xubuntu and Ubuntu alternate 64bit cd with the same
result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications
I can confirm this on my GeForce 9300 netbook. With nouveau, the
recovery menu shows as expected. With nvidia-current, the framebuffer
is the empty purple left over from grub until the X driver kicks in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
josef: You need to select Remount first as netroot requires write
access to your system. Netroot is also pretty limited at the moment,
there's another bug report specifically for that which I'll work on for
12.04 (don't feel like rewritting netroot entirely 2 weeks before
release).
--
You
Marking the bug as invalid on friendly-recovery's side as it's not
something I can fix in friendly-recovery itself.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode
Adding a task for each of the nvidia binary source packages. I'd suggest
the gfxpayload blacklist shipped in each of these be updated to
blacklist the nvidia chipsets (the blacklist currently shipped in these
packages is empty).
** Also affects: nvidia-graphics-drivers (Ubuntu)
Importance:
** Changed in: nvidia-graphics-drivers-173-updates (Ubuntu)
Status: New = Triaged
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Status: New = Triaged
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: New = Triaged
** Changed in:
here rescue mode also is broken after installing kde-desktop (installed
kubuntu boot logo) on an amd64 installation with ati hd 3200 graphics.
I must admit that i did not use rescue mode for a while, maybe rescue
mode was broken before but i suspect kubuntu :-; due to many other
problems with kdm
Thanks worked now with set gfxpayload=text in grub.cfg. But in recovery mode
is only
Resume
Fsck
Remount
Root
but no find NET root for wowk with APT.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes I have nvidia GF 7600GT . Fsarchive version from 14 september is ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about
I test/mistake now archive with lock update. When is lock only grub-
common v 1.99-12 ubuntu2 and grub-pc-bin v 1.99-12 ubuntu2 rescue mode
booting. When is update this fies to ubuntu4 rescue boot is with
affects.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
At Colin Watson's suggestion, changing the gfxpayload call in grub to
set gfxpayload=text fixes it here. Would have to check for potential
side effects of doing that for everyone.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reproduced the issue on nvidia hardware here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about this bug go to:
Do you have nvidia graphics on all affected machines?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To manage notifications about this bug go to:
This bug affects me too. Both on an old en new PC. The bug had also
affected my Lenovo R61i laptop. But was fixed by friendly-recovery i386
0.2.17. This update did not fixes de bug for the old en new PC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I testing only amd64 from Alternate cd. But friendly-recovery amd64
0.2.17 no fixed this problem. Archive Kubuntu 64bit from fsarchiver with
version friendly-recovery 0.2.12 worked ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New dpkg -l
** Attachment added: dpkg-l
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2447145/+files/dpkg-l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
cmdline
** Attachment added: cmdline
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2447146/+files/cmdline
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi
the same result with clear new installation of Kubuntu alternate CD beta 2.
Blue screen with:
Loading Linux 3.0.0-11
Inital Loading ramdisk
Now Kubuntu stoped. Must pressing enter and follow normal login screen.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Ah, ok, so the fact that you need to press enter before the boot
sequence resumes actually tells me that friendly-recovery started
properly.
The first option in friendly-recovery is resume, so pressing enter
selected it and the boot continued.
Now the problem is why don't you actually see the
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2447809/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
** Attachment added: lspci
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2447807/+files/lspci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
** Changed in: friendly-recovery (Ubuntu)
Assignee: (unassigned) = Stéphane Graber (stgraber)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
boot to rescue mode in Oneiric
To
Hi!
Can you give me a bit more details on your setup?
I'm mostly interested in the output of dpkg -l and /boot/grub/grub.cfg
Thanks
** Changed in: friendly-recovery (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: grub.cfg
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2442393/+files/grub.cfg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
** Attachment added: dpkg-l
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/854967/+attachment/2442394/+files/dpkg-l
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/854967
Title:
your dpkg -l got cut off, almost half of it seems missing.
Your grub.cfg looks good and contains what should be needed to trigger
the recovery mode.
Would be good to have your full dpkg -l and the result of cat
/proc/cmdline when booting in rescue mode.
Thanks
--
You received this bug
48 matches
Mail list logo
