incorrect warning of no /boot on dove
Bug #461681 reported by
Paul Larson
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| partman-uboot (Ubuntu) |
Expired
|
Low
|
Unassigned | ||
Bug Description
Binary package hint: ubiquity
Ubiquity version 2.0.4 on Dove
Uboot has some special requirements - it needs /boot to be on ext2 or vfat in order to read the kernel/initrd from it. Guided partitioning creates a small /boot on ext2 and allocates the rest to / (ext4) and swap. However, another valid disk configuration would be to have a sufficiently sized root fs using either ext2 or vfat.
Using guided partitioning, I attempted to create / as a 20G ext2fs, and no separate /boot. I received a warning saying that I needed a /boot for uboot to work properly, but it should have accepted this configuration as valid. This is lower priority since it also lets the user continue anyway.
| tags: | added: armel |
| Changed in ubiquity (Ubuntu): | |
| importance: | Undecided → Low |
| affects: | ubiquity (Ubuntu) → partman-uboot (Ubuntu) |
Revision history for this message
| Paul Larson (pwlars) wrote | #1 |
| tags: | added: iso-testing |
Revision history for this message
| Tobin Davis (gruemaster) wrote | #2 |
| Changed in partman-uboot (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in partman-uboot (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
After looking into this further, it seems that there is a new "uboot" filesystem type for Dove installs. I hadn't noticed this previously and just selected ext2 for the boot partition since it can boot from it. So this can also be reproduced if you have a separate /boot, and it is ext2 instead of uboot. Would still be useful if it recognized that it can boot from the current configuration and not complain about it, but certainly it's low priority.