Hello,
I would like to submit the patch attached, regarding the bootorder documentation.
coincidentally enough, my patch to correct the 'Booting from' text for USB devices (which I just updated) should address the issue you describe in the documentation patch:
https://github.com/MattDevo/SeaBIOS/commit/424fa77d61e6c3b002ccbe00e6e641a45...
it's probably not the ideal implementation, but it was just a quick/dirty patch for me to change the boot text to eliminate user confusion
cheers, Matt
On 9/6/2015 9:43:11 AM, "Maxime de Roucy" maxime.deroucy@gmail.com wrote:
Hello,
I would like to submit the patch attached, regarding the bootorder documentation. -- Regards Maxime de Roucy
On Mon, Sep 07, 2015 at 07:29:27AM +0000, Matt DeVillier wrote:
coincidentally enough, my patch to correct the 'Booting from' text for USB devices (which I just updated) should address the issue you describe in the documentation patch:
https://github.com/MattDevo/SeaBIOS/commit/424fa77d61e6c3b002ccbe00e6e641a45...
it's probably not the ideal implementation, but it was just a quick/dirty patch for me to change the boot text to eliminate user confusion
I don't understand what Maxime is reporting (via the documentation patch), nor what Matt's patch above fixes. Could someone provide a description of the problem/feature?
As for the "Booting from" message - I understand how "Booting from Hard Disk..." could be misleading when the "hard drive" is actually a USB flash drive, but I think a simpler solution would be to change the message to be more generic - like "Booting from disk..." or "Booting from C:" or just "Booting...".
-Kevin
Le lundi 07 septembre 2015 à 10:36 -0400, Kevin O'Connor a écrit :
I don't understand what Maxime is reporting (via the documentation patch), nor what Matt's patch above fixes. Could someone provide a description of the problem/feature?
Lets say you have one SATA drive and one USB drive connected to your board. The SATA drive is blank (no data on it). The USB drive contain a bootable operating system.
You configure the bootorder to : SATA USB PXE HALT
In this situation the user imagine SeaBIOS boot to USB as it will fail to boot from SATA… that's not the case. SATA and USB are both treat as IPL_TYPE_HARDDISK and when SeaBIOS list the devices it only keep the highest priority device of each type.
SATA and USB are both present and SATA has a higher priority than USB. PXE is another type (I don't know which one).
So SeaBIOS only keep SATA and PXE. When it fail to boot from SATA as the drive is blank it fallback to PXE instead of USB as the user expected.
The Matt patch (as I understand it) add an USB type. SeaBIOS will still only keep the highest priority device of each type but as SATA and USB belongs to different type they will be kept. SeaBIOS will boot from USB when it fail to boot from SATA.
On Mon, Sep 07, 2015 at 09:10:03PM +0200, Maxime de Roucy wrote:
Le lundi 07 septembre 2015 à 10:36 -0400, Kevin O'Connor a écrit :
I don't understand what Maxime is reporting (via the documentation patch), nor what Matt's patch above fixes. Could someone provide a description of the problem/feature?
Lets say you have one SATA drive and one USB drive connected to your board. The SATA drive is blank (no data on it). The USB drive contain a bootable operating system.
You configure the bootorder to : SATA USB PXE HALT
In this situation the user imagine SeaBIOS boot to USB as it will fail to boot from SATA… that's not the case.
This is a quirk of the BIOS/bootloader interface - bootloaders on "hard drives" are only able to boot from the C: drive (technically, the drive mapped to 0x80). SeaBIOS can only map one drive as C: per boot - so in the above example, if SeaBIOS maps the SATA drive as C: then only the SATA "hard drive" is bootable.
I don't see this as a huge issue though, because the user can simply reboot and select the USB drive from the boot menu.
SATA and USB are both treat as IPL_TYPE_HARDDISK and when SeaBIOS list the devices it only keep the highest priority device of each type.
SATA and USB are both present and SATA has a higher priority than USB. PXE is another type (I don't know which one).
So SeaBIOS only keep SATA and PXE. When it fail to boot from SATA as the drive is blank it fallback to PXE instead of USB as the user expected.
I understand what you mean now. Not sure the best way to document it.
The Matt patch (as I understand it) add an USB type. SeaBIOS will still only keep the highest priority device of each type but as SATA and USB belongs to different type they will be kept. SeaBIOS will boot from USB when it fail to boot from SATA.
Matt's patch doesn't implement that. The patch would just attempt to boot from C: twice - which would just cause back-to-back failures if the C: drive is not bootable.
-Kevin
-
Kevin O'Connor -
Matt DeVillier -
Maxime de Roucy