This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on
the current status under the
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
hooray, -14 kernels just released fix the problem (for me). I hope it does so
for everyone else too.
Thanks!
--
Can't boot kernel 2.6.20-13.21-generic
https://bugs.launchpad.net/bugs/96262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for U
s/asram/asrock/ sorry.
--
Can't boot kernel 2.6.20-13.21-generic
https://bugs.launchpad.net/bugs/96262
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
FWIW, this does not work for me. I haven't been able to boot to my SATA
drive since kernel -11. I have a asram 939dualsata2 (I think) with one
of those problematic SATA chipsets. My machine doesn't even show the
/dev/sd* devices on these newer kernels.
--
Can't boot kernel 2.6.20-13.21-generic
I think I have fixed it.
It looks like my partition UUID's got mucked up. For kernels 2.6.20.11 and
after I added the /dev/sd-- number instead after the 'root=' on the boot line
and in /etc/fstab and it now works fine, so far.
I read a thread on the ubuntu forums, I think, that had someone else w
Not quite overnight but further than I got before.
It now comes out to the prompt:
--
BusyBox v1.1.3 (Debian 1:1.1.3-3ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands
/bin/sh: can't acces
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) => Ubuntu Kernel Team
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Thanks for the comment Ben. I'll try an overnight tonight and see what happens.
I'd gotten as far as five minutes but given up.ndra
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
I see the same behavior. If I wait long enough (several minutes) it
will get past the hang but will boot to the emergency console.
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailma
** Changed in: linux-source-2.6.20 (Ubuntu)
Status: Unconfirmed => Confirmed
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Changed in: linux-source-2.6.20 (Ubuntu)
Sourcepackagename: None => linux-source-2.6.20
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
lspci listing
** Attachment added: "lspci listing"
http://librarian.launchpad.net/6936130/lspci.txt
--
Can't boot kernel 2.6.20-13.21-generic
https://launchpad.net/bugs/96262
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Attachment added: "lsusb listing"
http://librarian.launchpad.net/6936233/lsusb.txt
** Tags added: image kernel
** Description changed:
Cannot boot into this image 2.6.20-13-generic nor the previous
2.6.20-12-generic.
System gets as far as "Waiting for root filesystem" on splash boot
14 matches
Mail list logo
