[SeaBIOS] SeaBIOS recognising USB 3.0 on boot works - partly

edward wandasiewicz 0.w3ntd at gmail.com
Mon Nov 30 20:04:55 CET 2015

On 30 Nov 2015 5:35 p.m., "Kevin O'Connor" <kevin at koconnor.net> wrote:
> On Mon, Nov 30, 2015 at 04:47:29PM +0000, edward wandasiewicz wrote:
> > I started over, as I forgot which device was in which port.
> >
> > It seem's like a race condition, as I managed to get a USB device
> > detected twice with JohnLewis RW_LEGACY as well now, although it
> > doesn't happen very frequently. I pressed Ctrl-L and ESC with not much
> > pause and got a double device detection.
> To confirm, the "double device" is an error right - there aren't
> actually two of these devices in the machine?

Correct. One Philips USB device and One Mushkin Ventura Ultra. Nothing
more. Nothing less.

> Looks like two separate issues are occurring - the Philips drive is
> being detected as both a high speed device and as a super speed
> device.  I need a log with CONFIG_DEBUG_LEVEL=5 to diagnose that.  The
> second issue appears to be a USB_TRANSACTION_ERROR response from the
> set_address command.  I think the controller may just be a bit too
> picky on stall responses from devices in that situation.  I've put up
> a patch to try and work around that in the repo at:
>   https://github.com/KevinOConnor/seabios/tree/testing
> Are you able to compile SeaBIOS from source and install it on your
> Samus?
> -Kevin

Compile? I could have a go, but don't want to brick my device. Happy
to write a RW_LEGACY from John Lewis.

Or learn how to - bit risky for a newbie?

I tried to boot OpenBSD on SAMUS with the USB Philips drive attached,
nothing else attached, and got the following output

probing pc0 com0 mem[639K 1997M 14320M a20=on]
disk: hd0+ hd1+* hd2*
>> OpenBSD/amd64 BOOT 3.29

boot > machine diskinfo
Disk BIOS# Type Cyls   Heads Secs Flags Checksum
hd0  0x80    label 1023  255      63      0x2       0x0
hd1  Ox81   label 1023  255      63      0x1       0x0
hd2  Ox82   label 1023  255      63      0x0       0x0

Meaning of +, +*, * after hd0+, hd+*, hd2*

The '+' character after the "hd0" indicates that the BIOS has told
/boot that this disk can be accessed via LBA. When doing a first-time
install, you will sometimes see a '*' after a hard disk -- this
indicates a disk that does not seem to have a valid OpenBSD disk label
on it.

OpenBSD developers tell me + means "big disk support".

hd0 is my ChromeOS hard disk with OpenBSD installed on it.

hd1 and hd2 is the single Philips USB 3.0 disk. It has been zero'd with dd.

Seems SeaBIOS is telling OpenBSD, the same drive, can and can't be
accessed via LBA, and is and isn't a "big disk support" device.

Hope this helps.


More information about the SeaBIOS mailing list