Only need reinstall grub2 and uninstall grub and these kernels which
aren't refresh. This is good for me.
--
hardy upgrade: /dev/disk/by-uuid non existant at boot; dropping to a shell
(with "386" kernel)
https://bugs.launchpad.net/bugs/213884
You received this bug notification because you are a
For me, this was the problem I had. Just installed Ubuntu 8.10 - the Intrepid
Ibex on a Intel base.
There was a big delay on booting from bios to os as well. Turned out I had a
jumper on the extra data drives I had in the system, (Western Digital), on the
master w/slave jumpers. Diagram showed f
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You can
Leann...
I am interested in testing the new Kernel for the purposes of using my
GPS. I have a Delorme LT-40 which is supposed to work with the newest
kernel, but which does not work at all with my 2.6.24-19-generic x86
AMD64 kernel.
If I download the live CD and install it on a partition on my d
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
I can confirm this for kernel 2.6.24-16.
I attempted to boot the Hardy liveCD, but it would not load the kernel.
The error was: '/sbin/modprobe' abnormal exit, followed by the BusyBox
shell.
I successfully installed linux using Gutsy, then upgraded using do-
release-upgrade. I can boot this with
I can confirm that the reason for my problem was, as I suggested, that I
was using /dev/hd* references in /etc/fstab.
I have changed it to use UUIDs and installed the now-released Hardy
Heron and the system boots OK now.
--
hardy upgrade: /dev/disk/by-uuid non existant at boot; dropping to a she
In my case, the UUID in menu.lst matches what the entry in /dev/disk/by-
uuid links to my root filesystem.
BUT... /etc/fstab refers to filesystems by the much more sensible (and
memorable) /dev/hd* names; I think because I edited it back that way
after an earlier upgrade. I'll have to try putting
I can confirm this issues. In my particular case I found out what the
problem was and fixed it. Perhaps my problem is only one way to
reproduce this bug, but in any event...here's the issue/fix:
The hard drive UUID in my GRUB menu.lst was wrong. I had swapped out my
hard drive when my machine w
Just noticed the title of this bug specified "386" kernel. My problem
was with an AMD 64 kernel.
--
hardy upgrade: /dev/disk/by-uuid non existant at boot; dropping to a shell
(with "386" kernel)
https://bugs.launchpad.net/bugs/213884
You received this bug notification because you are a member of
I have had a similar experience with upgrading to Hardy.
The new kernel managed to mount my root filesystem (/dev/hda1) but
failed to mount any more of them. running "fdisk /dev/hda" and "fdisk
/dev/hdb" I received an error message that the devices did not exist.
In addition, either the upgrade o
This is the dmesg output WITH THE WORKING ("generic") KERNEL.
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/13215319/dmesg.log
--
hardy upgrade: /dev/disk/by-uuid non existant at boot; dropping to a shell
(with "386" kernel)
https://bugs.launchpad.net/bugs/213884
You receive
** Attachment added: "lspci -vvnn output"
http://launchpadlibrarian.net/13215296/lspci-vvnn.log
--
hardy upgrade: /dev/disk/by-uuid non existant at boot; dropping to a shell
(with "386" kernel)
https://bugs.launchpad.net/bugs/213884
You received this bug notification because you are a member
13 matches
Mail list logo
