Summary: | LiveUSB method described in the above URL won't work due unnecessary '-t iso9660' mount option | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Durval Menezes <jm165> |
Component: | genkernel | Assignee: | Gentoo Release Team <releng> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jm165, koen, spitrage, tefiszx |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/liveusb.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Durval Menezes
2006-09-11 06:18:54 UTC
I just ran into this myself, with some hardware that absolutely needed 2006.1 (the 2006.0 kernel doesn't boot on it). I changed: -t iso9660 to: -t auto Because mount will not always default to auto, depending on the circumstances. *** Bug 147265 has been marked as a duplicate of this bug. *** (In reply to comment #0) > - The documentation on the above URL is wrong when it mentions a > "dobladecenter" boot option: init doesn't check for anything with > that name and will silently ignore it. From examination of the /init > script inside gentoo.igz, I've determined that the correct option is > "scandelay". Actually, the correct option is "slowusb" rather than scandelay. Anyway, the documentation isn't maintained by us, and I actually never knew it became an "official" document, as Release Engineering does not support LiveUSB and the developer who did the work on it has left the project. That being said, I've fixed the initrd.scripts for both the iso9660 and SUBDIR bugs. These will be fixed in the next genkernel, but a new Gentoo release using it will not be out for quite some time. *** Bug 145932 has been marked as a duplicate of this bug. *** Fixed in 3.4.1, thanks! *** Bug 158530 has been marked as a duplicate of this bug. *** Actually... this should probably stay open until 2007.0 is released. Well, that was fixed but it appears that there's a different error, which is handled in a different bug (173117). Actually, 143774 is the bug for the exact fix. |