*** This bug is a duplicate of bug 73090 ***
Same problem for me with 2.6.19-7 with lilo.
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 73090 ***
I'm also having this problem with a fully updated system,
2.6.17-10-generic boots but 2.6.19 doesn't boot. I have root on a md
(raid5) over 3 sata disks on a nforce4 mb. I think the problem is that
the sata_nv modules are not being loaded so the disks a
*** This bug is a duplicate of bug 73090 ***
The instructions for removing the 'kopt_2_6=root=/dev/hdaX ro' line and
generating the initramfs again does not work for me either.
The boot sequence hangs a while after "waiting for root filesystem".
I noticed that my harddisk(sda1) is not available
*** This bug is a duplicate of bug 73090 ***
One last note; it should be update-grub not grub-update. So the full set
of repair instructions should be:
- remove the '# kopt_2_6=root=/dev/hdaX ro' line from your menu.lst
- $ sudo update-initramfs -u -k 2.6.19-6-generic
- $ sudo update-grub
- re
*** This bug is a duplicate of bug 73090 ***
** Changed in: linux-meta (Ubuntu)
Status: Unconfirmed => Rejected
** Changed in: linux-source-2.6.19 (Ubuntu)
Sourcepackagename: linux-source-2.6.19 => grub
Status: Fix Released => Confirmed
** This bug has been marked a duplicate of bu
Problem solved thanks to Ben Collins,
roundup to fix this problem:
- remove the '# kopt_2_6=root=/dev/hdaX ro' line from your menu.lst
- $ sudo update-initramfs -u -k 2.6.19-6-generic
- $ sudo grub-update
- reboot
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs
Deleted the line and run the update-initramfs command. Kernel still
won't boot. When trying restore mode, the kernel does load, last part it
loads is the usb core. It does reacts on events like adding/removing USB
devices, but it does not get to the point of a shell.
--
kernel 2.6.19-6 does not b
On Mon, 2006-11-27 at 03:27 +, Caspar Adriani wrote:
> in my menu.lst is no enabled kopt_2_6 line and "update-initramfs -u"
> only updates the initramfs of 2.6.19-5-generic. Booting 2.6.19-5-generic
> now gives a new result and ends up in busybox while 2.6.19-6-generic
> still refuses to contin
in my menu.lst is no enabled kopt_2_6 line and "update-initramfs -u"
only updates the initramfs of 2.6.19-5-generic. Booting 2.6.19-5-generic
now gives a new result and ends up in busybox while 2.6.19-6-generic
still refuses to continue to load.
** Attachment added: "menu.lst file"
http://libra
I'm pretty sure this was related to initramfs-tools not including the
new pata drivers. This has been fixed in newer initramfs-tools packages.
If this does not fix your problem, then you have an issue with your grub
menu.lst file. Edit it, finding the line that has kopt_2_6, and delete
that line,
Same problem here (AMD64, 2.6.19-6-generic and 2.6.19-5-generic kernel), It
does load some parts of the kernel but it never reaches the point of mounting
the root disk (XFS partition). nosplash and recovery also won't boot.
I did a upgrade from a fresh edgy and my 2.6.17-10-generic boots fine.
-
hrm, okay, sorry. must have misread it.
** Changed in: linux-meta (Ubuntu)
Status: Rejected => Confirmed
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm sorry, but you're wrong. I have a fully updated system - the udev issue
affected me just as it did everyone else, and I fixed that the way I gather
most people did: with a chroot.
This is a different problem - or perhaps a related, but none the less still
unfixed - problem.
"sudo apt-get di
after that, update your machine with apt-get as normal, and exit.
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
this is due to the temporarily broken udev and/or coreutils of the
previous day.
It has now been fixed.
You can chroot into your feisty / , either from a live cd, or from
another partition on that machine.
use: sudo chroot /feisty/root/location/ su
** Changed in: linux-meta (Ubuntu)
St
Sorry, file didn't attach. Trying again:
** Attachment added: "kernel -6 not working"
http://librarian.launchpad.net/5167425/kernel-6_failing.jpg
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
And this is -6:
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm attaching two files, one showing the -4 kernel working fine and the
other showing the -6 kernel failing to boot.
Here's -4:
** Attachment added: "kernel -4 working"
http://librarian.launchpad.net/5167424/kernel-4_working.jpg
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/730
I haven't got this problem, and I'm using 2.6.19-6.
You can follow the ubuntuforums.org thread here:
http://ubuntuforums.org/showthread.php?t=305926
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
I'm sure it's with -6 -- this was booting fine until I installed all the
updates and rebooted, and now it doesn't boot.
-4 still boots fine, however (using it now).
Expanding on my previous comment, while -6 only runs /scripts/local-
bottom (I believe it's only that) before waiting for root files
Here is my fstab
** Attachment added: "fstab"
http://librarian.launchpad.net/5160841/fstab
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm using udev version: 103-0ubuntu4
but that doesn't solve the problem.
I can only boot by using Edgy's kernel (2.6.17-10-generic).
--
kernel 2.6.19-6 does not boot
https://launchpad.net/bugs/73057
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/list
You are sure that the problem is with the kernel -6?
I'm running this kernel since yesterday, without any problems.
[EMAIL PROTECTED]:~$ uname -a
Linux int 2.6.19-6-generic #2 SMP Tue Nov 21 07:02:59 UTC 2006 i686 GNU/Linux
I think the problems was with udev_103-0ubuntu3_i386.deb package, and
t
I can confirm this, the -4 kernel's booting but -6 hangs on "Waiting for root
file system".
-6 was working on the 22nd nov, but after updates on the 23rd nov it's stopped.
Notably, with the -4 kernel various init scripts are run between
"Mounting.." and where the -6 kernel has "waiting for root".
24 matches
Mail list logo
