Summary should be changed from "initramfs not generated correctly on
upgrade to Dapper" to "initramfs not generated correctly on dist-
upgrade". This just happened to me going from Gutsy to Hardy. Marking
kernels for reinstallation and applying in Synaptic made system bootable
with Hardy kernels an
I have found this to occur in Feisty.
I attempted to update the kernel to that in Gutsy - added Gutsy to the
repository list.
On rebooting, the boot stops at the point where it tries to mount the hard disc
(inferred from symptoms).
After many minutes, I get a prompt from busybox.
When I check
update:
The point where it fails seems to be when the kernel detects the IDE devices:
...
hda: ERROR, PORTS ALREADY IN USE
hdb: ERROR, PORTS ALREADY IN USE
...
This kind of error has been reported elsewhere (on ubuntuforums) - I'll
go look there for an answer.
eriksoe
--
initramfs not generated
I have recently upgraded to feisty, and have just run into the same
problem.
I think I first upgraded the initram-stuff (which complained that the kernel
was too old), then I upgraded the kernel.
Re-installing and dpkg-reconfigure'ing does not seem to work.
In the initrd-shell, the only devices
is this still an issue in feisty
--
initramfs not generated correctly on upgrade to Dapper
https://bugs.launchpad.net/bugs/32123
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
I've made working images for 2.6.15-23-386 and -686:
http://purehatred.org/image/
I used the surviving kernel from Breezy to boot, installed yaird,
and ran mkinitrd.yaird to generate them. Both are tested on other
people's systems.
There's definitely something wrong with both mkinitramfs and
mkin
