[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-03 Thread Launchpad Bug Tracker
** Branch linked: lp:~vorlon/console-setup/lp.864466 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864466 Title: break=foo boot option incompatible with gfxpayload=keep To manage notifications

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Steve Langasek
** Patch added: prospective patch for kbd to add totextmode https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/864466/+attachment/2497398/+files/kbd-864466.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Steve Langasek
** Patch removed: prospective patch for kbd to add totextmode https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/864466/+attachment/2497398/+files/kbd-864466.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Steve Langasek
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/864466 Title: break=foo boot option incompatible with gfxpayload=keep To manage notifications about this bug go to:

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Steve Langasek
Fixed patch to get totextmode really into the package. Doesn't work though; I'm still left with the graphical splash when using break=top. Needs more investigation. ** Patch added: updated kbd patch (totextmode in /bin so it can be used reliably by friendly-recovery)

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Ubuntu QA's Bug Bot
The attachment updated kbd patch (totextmode in /bin so it can be used reliably by friendly-recovery) 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

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-02 Thread Steve Langasek
Further testing shows that totextmode is both insufficient and unnecessary. - If a framebuffer module is loaded so that the kernel has an fbcon, 'chvt 1' is sufficient to get a text console, and the panic() function already does this. - If no framebuffer module is loaded, the kernel seemingly

[Bug 864466] Re: break=foo boot option incompatible with gfxpayload=keep

2011-10-01 Thread Steve Langasek
** Changed in: console-setup (Ubuntu) Status: New = Triaged ** Changed in: console-setup (Ubuntu) Importance: Undecided = Medium ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) = Steve Langasek (vorlon) ** Also affects: kbd (Ubuntu) Importance: Undecided