** Tags removed: quantal regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To manage notifications about
Making some changes to this bug due to issues with kernel hot team
report.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New = Invalid
** Tags added: kernel-key
--
You received this bug notification because you are a
** Changed in: grub2 (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To manage
** Changed in: grub2 (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To
I got the opportunity to show Colin the behavior in person, and he had a
key insight. He asked whether the freeze happens on the reboot after a
shutdown, as opposed to an explicit reboot command (e.g. choosing Reboot
from the greeter menu).
In my very limited testing so far, it seems to be true
Colin, I must have missed your comment #24; I'll try that. In the
meantime, note that if I let rEFIt boot to OS X, it will *always* boot
successfully to Ubuntu the next time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Setting debug=all doesn't provide anything useful. When it freezes, it
still freezes before there's any output. When it doesn't freeze, I get
all the expected debugging output to the console.
About the only other bit of information I can provide is that when it
does freeze, the keyboard stays
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To manage notifications about this bug go to:
It may be worth putting 'set debug=all' at the top of grub.cfg and
seeing how far it gets. (Warning: this can potentially take a *long*
time to boot. In extremis you might even need to boot from a live CD or
similar to remove it.)
** Package changed: grub (Ubuntu) = grub2 (Ubuntu)
--
You
I do think the works half the time behavior of grub safe boot is
coming into play. It's not exactly half the time but whenever I get a
hang, I definitely get the grub screen afterward. Occasionally I get
the grub screen more than once in a row though.
I downgraded libplymouth2 plymouth
Hi Barry - when it hangs, does pressing Escape show anything? Also, I've
updated the Plymouth wiki page so it would be interesting to know if
Plymouth is runnable via the initramfs and the live system:
https://wiki.ubuntu.com/Plymouth#Checking_Plymouth_Can_Run_in_the_Initramfs
Might also be useful to get a plymouth debug log (along with syslog,
etc) even with quiet splash removed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet
Since downgrading plymouth to the precise version doesn't fix it, it
doesn't sound like plymouth itself is the culprit here. Reassigning to
the kernel.
Barry, have you checked whether setting GRUB_GFXPAYLOAD_LINUX=text makes
the boot reliable?
** Package changed: plymouth (Ubuntu) = linux
Barry,
Can you test the latest mainline kernel[0], to see if this bug is
already fixed upsteram?
Also, does the issue go away if you boot back into the Precise kernel?
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/
** Tags added: quantal regression-release
** Tags added:
On Jun 27, 2012, at 05:11 PM, Steve Langasek wrote:
Barry, have you checked whether setting GRUB_GFXPAYLOAD_LINUX=text makes
the boot reliable?
It does not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Jun 27, 2012, at 04:19 PM, James Hunt wrote:
Hi Barry - when it hangs, does pressing Escape show anything?
Hi James. Nothing happens if I press esc (or really, anything) during the
hang.
Also, I've updated the Plymouth wiki page so it would be interesting to know
if Plymouth is runnable via
On Jun 27, 2012, at 04:19 PM, James Hunt wrote:
Hi Barry - when it hangs, does pressing Escape show anything?
Hi James. Nothing happens if I press esc (or really, anything) during the
hang.
Also, I've updated the Plymouth wiki page so it would be interesting to know
if Plymouth is runnable via
On Jun 27, 2012, at 06:08 PM, Joseph Salisbury wrote:
Hi Joseph.
Can you test the latest mainline kernel[0], to see if this bug is
already fixed upsteram?
Also, does the issue go away if you boot back into the Precise kernel?
So, I set GRUB_DEFAULT=saved then chose the 3.2.0-25-generic kernel
So this bug still exists if you boot the Precise kernel on Quantal, but
it did not exist at all booting the precise kernel on Precise?
An interesting test would be to boot the Quantal kernel on this machine
with Precise installed. Is this a test machine? Do you have the
option to re-install
On Wed, Jun 27, 2012 at 07:26:33PM -, Joseph Salisbury wrote:
So this bug still exists if you boot the Precise kernel on Quantal, but
it did not exist at all booting the precise kernel on Precise?
An interesting test would be to boot the Quantal kernel on this machine
with Precise
On Jun 27, 2012, at 07:26 PM, Joseph Salisbury wrote:
So this bug still exists if you boot the Precise kernel on Quantal, but
it did not exist at all booting the precise kernel on Precise?
Correct.
An interesting test would be to boot the Quantal kernel on this machine
with Precise installed.
Barry, there are some additional things that can be done to gather further
debug information. Details can be found at:
https://wiki.ubuntu.com/DebuggingKernelBoot
It looks like you already tried setting GRUB_GFXPAYLOAD_LINUX=text
I'm going to add this bug to the kernel team hotlist to get some
On Jun 27, 2012, at 08:22 PM, Joseph Salisbury wrote:
Barry, there are some additional things that can be done to gather further
debug information. Details can be found at:
https://wiki.ubuntu.com/DebuggingKernelBoot
It seems like the problem is in the handoff from refit to grub, since I cannot
On Wed, Jun 27, 2012 at 09:23:39PM -, Barry Warsaw wrote:
On Jun 27, 2012, at 08:22 PM, Joseph Salisbury wrote:
Barry, there are some additional things that can be done to gather further
debug information. Details can be found at:
https://wiki.ubuntu.com/DebuggingKernelBoot
It seems
Barry: Can you modify /etc/defaults/grub to remove quiet splash and
set GRUB_GFXPAYLOAD_LINUX=text, then run update-grub, and see if you
still get a hang? If so, what do you get on the screen?
I think forcing the boot menu to always be shown is a good idea as well,
to give another point of
On Jun 27, 2012, at 09:42 PM, Steve Langasek wrote:
You can force the grub menu to always be shown, with or without a previous
failure and with or without a shift key, by setting GRUB_TIMEOUT=-1 (I
think).
According to `info grub` -1 waits indefinitely, 0 boots immediately. However,
even
One of the things I'm interested in knowing is if you force the grub
menu to displayed every time you boot (so any non-zero value of
GRUB_TIMEOUT) does the hang happen before the boot menu is displayed. If
so then it's pretty conclusive that it's happening in grub. Based on
your comments I'm
On Jun 27, 2012, at 10:32 PM, Seth Forshee wrote:
One of the things I'm interested in knowing is if you force the grub
menu to displayed every time you boot (so any non-zero value of
GRUB_TIMEOUT) does the hang happen before the boot menu is displayed. If
so then it's pretty conclusive that it's
** Package changed: linux (Ubuntu) = grub (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To manage notifications
Can you check whether downgrading to the 12.04 version of the plymouth
packages fixes this issue? There are a lot of moving parts here, it
could just as well be a kernel regression as a plymouth one.
** Changed in: plymouth (Ubuntu)
Status: New = Incomplete
--
You received this bug
On Jun 21, 2012, at 06:18 PM, Steve Langasek wrote:
Can you check whether downgrading to the 12.04 version of the plymouth
packages fixes this issue? There are a lot of moving parts here, it
could just as well be a kernel regression as a plymouth one.
I'll give it a try. I should note too that
More data points:
* arch is i386
* at least half the time I don't even get to the grub screen
* I think removing quiet or splash is a red herring - if I get to grub the
machine boots regardless of whether I edit the boot line, leave it alone, or
just let grub timeout, etc. obviously if I don't
** Changed in: plymouth (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1016170
Title:
No login screen unless quiet splash removed from boot line
To manage
33 matches
Mail list logo
