[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
trewornan wrote: > > I can't explain this: before I loaded the KingMax up via Unetbootin I > set it up as a single FAT32 partition and marked it bootable same as > with the Kingston. The only odd thing I can find is that the KingMax > although it says 4GB actually the partition (which as far as I can > see covers the entire memory) says 3.8GB. Is it possible there's some > peculiar proprietary partitioning that isn't apparent under normal > usage. Possible but just list the partitions and look "fdisk -l /dev/sdX" or "parted /dev/sdX". I've fought similar today, USB flash devices can be difficult to boot. I think the most likely cause if partition is correct is problems with the master boot record, just blat it "aptitude install mbr" "install-mbr /dev/sdX", then use parted or other partition tool to ensure the FAT32 partition is correctly flagged as bootable. In my case the separate partitioning was too painful to fiddle with, I went with sticking the Debian bootable image over the whole device "zcat boot.img.gz >/dev/sdX" which worked nicely for Debian. -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html