Comment 28 for bug 108230
Revision history for this message
| Alex Sheppard (alex-knows-best) wrote | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Had this problem (on debian), with the info given here and a bit of extra thought i got it figured out and fixed.
The problem was that the ram disk used in the boot process was made when my swap partition was /dev/hda2. The problem appeared when i had to rearrange my hard disk and moved swap to /dev/hda5.
The fix was updating the ram disk using update-initramfs.
BUT, That didn't fix it straight away.
I noticed that it had updated the ram disk for the latest kernel, but my grub entry was still calling a previous kernel version.
So, anyone for whom the update-initramfs didn't help, check the the ram disk updated corresponds to the one actually used in the boot process!!