I'm running Lucid and Maverick now and neither have boot issues. I'm
changing the status.
** Changed in: linux (Ubuntu)
Status: Incomplete = Invalid
--
Karmic wont boot with 2.6.30 kernel
https://bugs.launchpad.net/bugs/377925
You received this bug notification because you are a member
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and
your problem may have been
After a restart I can't get into Karimic 2.6.30-5. I log in, the welcome
sounds and then I'm returned to the login screen. I'm using my main
partition in Jaunty to write this.
Between restarts I installed lib-gksu, which may be the culprit. How do
I remove it via the terminal, which is the only
Thanks for your cooperation so far. Could you please --attach in a .txt
file-- (not posted as a message like above) the output from the commands
after a failed boot:
1.dmesg
2. lspci -vv
3. lspci -vvn
These are required for the assignment of the bug to the appropriate
team.
--
Karmic wont
I don't have anything that uses bluetooth.
--
Karmic wont boot with 2.6.30 kernel
https://bugs.launchpad.net/bugs/377925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you for reporting the bug. In order to find the issue and properly
report/fix it we require further information. Do you know when it hangs?
At boot, when GRUB is displayed use e to edit the kernel line, removing
splash vga=xxx.
It would also be useful to know which release candidate of
I am running 2.6.30-5-generic, however I ran some updates today and now
I can boot into that kernel.
--
Karmic wont boot with 2.6.30 kernel
https://bugs.launchpad.net/bugs/377925
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I've isolated a part of the log (a boot with the 2.6.30-5-generic kernel) where
the error occurs.
Do you have a usb bluetooth dongle attached? If so, have you tried booting
without it attached?
** Attachment added: kernel log for 2.6.30-5-generic failed boot from Mike
Hurst
It seems the previous attached log is from a failed resume following
this successful boot. Does this happen when you're not resuming from
sleep/hibernation?
** Attachment added: kernel log for 2.6.30-5-generic boot before kern.log.txt
from Mike Hurst
