** Attachment added: "initramfs-tools-0.39-0.39.1.debdiff"
http://launchpadlibrarian.net/14826146/initramfs-tools-0.39-0.39.1.debdiff
** Changed in: initramfs-tools (Ubuntu Hardy)
Status: Confirmed => Fix Committed
** Description changed:
- and this is a problem for my Wubi installation, given that the file
- containing the root filesystem is on a FAT32 partition.
+ The initramfs lacks vfat support. This means that Wubi users coming
+ from a FAT Windows partition will be able to install (casper has vfat),
+ but they will be left with an unbootable system at the first update-
+ initramfs.
- It does not boot !
-
- It worked nicely until 2.6.24-16
-
- Then, I got an update from the update manager end the updated kernel and
- initramfs image don't boot.
-
- I managed to type a
-
- modprobe -v vfat
-
- at the (initramfs) prompt and found out ther was no vfat module.
-
- Since I was at it I also noticed there no ntfs either.
-
- I can't repot any log because there's no filesystem I can mount, without
- vfat. Sorry
-
- Thanks
- Cato
+ TEST CASE:
+ Install Ubuntu using Wubi on a Windows FAT partition and install all
available updates. Reboot and you will be presented with an initramfs prompt.
** Description changed:
The initramfs lacks vfat support. This means that Wubi users coming
from a FAT Windows partition will be able to install (casper has vfat),
but they will be left with an unbootable system at the first update-
initramfs.
TEST CASE:
Install Ubuntu using Wubi on a Windows FAT partition and install all
available updates. Reboot and you will be presented with an initramfs prompt.
+
+ A debdiff of the proposed upload can be found here:
+ http://launchpadlibrarian.net/14826146/initramfs-tools-0.39-0.39.1.debdiff
--
There is no vfat module in the 2.6.24-17 initrd
https://bugs.launchpad.net/bugs/236021
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
