On Wed, Aug 03, 2011 at 02:47:19PM -0600, Marc Jones wrote:
I'm having a problem with booting a usb flash key that worked previously in version 0.6.2. The USB device is identified but then gets a read error when booting from it. This is the Persimmon, sb800 platform. Any thoughts on what might have changed to cause this?
Could it be just a sporatic failure? The only real USB changes since v0.6.2 were book keeping changes for 'struct pcidevice' - I don't think they would cause drive read errors. Can you post the log?
-Kevin
On Wed, Aug 3, 2011 at 5:22 PM, Kevin O'Connor kevin@koconnor.net wrote:
On Wed, Aug 03, 2011 at 02:47:19PM -0600, Marc Jones wrote:
I'm having a problem with booting a usb flash key that worked previously in version 0.6.2. The USB device is identified but then gets a read error when booting from it. This is the Persimmon, sb800 platform. Any thoughts on what might have changed to cause this?
Could it be just a sporatic failure? The only real USB changes since v0.6.2 were book keeping changes for 'struct pcidevice' - I don't think they would cause drive read errors. Can you post the log?
-Kevin
This is the error I am getting:
enter handle_13: a=00204280 b=00002400 c=0000000a d=00000080 ds=0000 es=07c0 ss=0000 si=00007ba2 di=00002000 bp=000007be sp=00007ba2 cs=07c0 ip=0147 f=0202 disk_op d=0x0000d5e0 lba=2097280 buf=0x0000a000 count=1 cmd=2 ehci_send_bulk qh=0x0009ff00 dir=0 data=0x0009fad8 size=31 ehci_send_bulk qh=0x0009ff80 dir=128 data=0x0000a000 size=512 ehci_send_bulk qh=0x0009ff80 dir=128 data=0x0009faf7 size=13 enter handle_13: a=00204281 b=00002400 c=00000000 d=00000780 ds=0000 es=07e0 ss=0000 si=00007ba2 di=00002000 bp=000007be sp=00007ba2 cs=07c0 ip=0147 f=0206 disk_op d=0x0000d5e0 lba=2097281 buf=0x0000a200 count=1 cmd=2 ehci_send_bulk qh=0x0009ff00 dir=0 data=0x0009fad8 size=31 WARNING - Timeout at ehci_wait_td:570! ehci_send_bulk failed USB transmission failed invalid extended_access:143: a=00204281 b=00002400 c=00000000 d=00000780 ds=0000 es=07e0 ss=0000 si=00007ba2 di=00002000 bp=000007be sp=00007ba2 cs=07c0 ip=0147 f=0206
I now suspect that this is a coreboot problem. The old working seabios with current coreboot fails as well.