roberts
Group: Members
Posts: 4983
Joined: Oct. 2003 |
|
Posted: Jan. 12 2006,19:18 |
|
There are many issues with USB booting. Here is some background as we have tried to address some of them.
One that became apparent with 2.0 is that we tried acpi=off as a default boot parameter. We found some systems wouldn't boot USB especially the ebox3 machines. This in fact is the only time John or I have seen an issue with USB booting. That is not to say there are not other issues. With 2.1 we dropped this parameter. The ebox3 machines boot usb ok. Now, I have already seen a post that 2.0 worked them and not 2.1 So some machines may need it others may not. We can't have it both ways.
Another common issue is the timing of the USB ports. Front ports are slower than back ports to register the device. We made the bootfloppy-usb.img, which is specifically for booting USB devices have a delay to improve time to register.
The standard cdrom images, of course have a much wider array of boot devices to support and an order of searching devices and we don't want to unnecessarily want to delay the bootup for everyone.
Then we used to require net access for installation to pendrives, this allowed the script to download the special bootfloppy-usb image to be used for the pendrive. But users wanted not to require net access, so now the script use the standard boot image files.
Then there is the issue, as is always the case, John and I do not have every conciveable device to test with. That is why we now have an open public release candidate testing. Still, when we cannot reproduce or see the issue it can become difficult to solve.
But we are both committed to trying to constantly improve DSL with each release. But as with any software product perfection is elusive.
Edited by roberts on Jan. 12 2006,19:20
|