This bug report was marked as Incomplete and has not had any updated
comments for quite some time. As a result this bug is being closed.
Please reopen if this is still an issue in the current Ubuntu release
http://www.ubuntu.com/getubuntu/download . Also, please be sure to
provide any requested
I've removed the regression tag since this is likely a hardware issue
and not kernel related.
** Tags removed: regression-update
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: regression-update
** Tags removed: regression-potential
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
When you see the black screen does attempting to switch VT to VT-7 help
any? It sounds a bit like the plymouth race condition. You could try
booting without 'splash' on the kernel command line to see if that
helps.
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You
Andy ... I'm afraid the only VT I know is the green mountain state. It
is too short a term to feed to the borg for assistance, too.
(however, see my last comment, re. disk corruption)
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification
Okay: I spent some time reviewing syslogs and it seems that I have some
major disk corruption going on (tons of null characters followed by a
dump of some random config file in the syslog, for instance). Which
would be consistent with the 2.6.31.x kernels borking since (this is
where it gets a
Thanks Leann. It took me a bit to get to this. Answers:
I'm not getting any errors. Just a cursor at the top left corner of the
black screen. Nothing else. The last thing I see before it switches
over to the blank screen is Starting AppArmor profiles -- it runs
through a bunch of stuff and then
It also might not hurt to try the even newer 2.6.31-17.54 kernel update.
Thanks.
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Amanda,
Can you boot the 2.6.31-16 kernel but remove the quiet and splash
boot options:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Bootloader
Are there any errors printed to the screen prior to the hang? If so you
paste the messages here (maybe take a digital photo of your
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Tags added: regression-potential
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Pepe,
Yes, 2.6.31-15 worked normally as far as I could tell.
Thanks,
Amanda
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi Amanda,
Please, can you confirm that 2.6.31-15 kernel worked normally?
Thanks in advance.
** Tags added: karmic
** Changed in: linux (Ubuntu)
Status: New = Incomplete
--
Cannot boot in 2.6.31.16 kernel
https://bugs.launchpad.net/bugs/499569
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This bug did not have a package associated with it, which
is important for ensuring that it gets looked at by the proper
developers. You can learn more about finding the right package at
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 499569
This will help us to find and resolve the problem. Bear in mind that you
may need
14 matches
Mail list logo
