Re: [LinuxBIOS] (fwd) Re: USB bootloader

[yhlu]

Are you using normal BIOS instead of LinuxBIOS?

YH

On 9/10/06, Al Boldi  wrote:
> yhlu wrote:
> > http://www.linuxbios.org/index.php/Etherboot
>
> Success!  Thanks a lot!
>
> This info should probably be in the README.
>
> The following flags in src/arch/i386/Config are critical for a normal bios:
> CFLAGS+= -DPCBIOS
> #CFLAGS+= -DLINUXBIOS
> CFLAGS+= -DCONFIG_PCI_DIRECT
> CFLAGS+= -DCONSOLE_DIRECT_VGA
> #filo is for some reason dependent on serial; will hang otherwise
> CFLAGS+= -DCONSOLE_SERIAL -DCOMCONSOLE=0x3f8
> #don't uncomment this one; will slow down display on fast machines (P4)
> #CFLAGS+= -DCOMPRESERVE
>
> Confirmed boot for filo.zelf, filo.zlilo, filo.zrom on UHCI i440bx/zx, i810,
> and VIA.
>
> There is one thing though, it only boots on a second try after detecting the
> USB-device, like this:
>    boot: uda1:/vmlinuz
>    LinuxLabs USB bootloader
>    New USB device, setting address 2  (repeats 1-forever times, until
>                                        usb-device pulled)
>    boot: uda1:/vmlinuz
>    LinuxLabs USB bootloader
>    (...now boots ok @ 100kb/s ...)
>
> Any easy way to fix this?
>
> Thanks again!
> > YH
> >
> > On 9/9/06, Al Boldi  wrote:
> > > yhlu wrote:
> > > > you need to use filo.zelf
> > >
> > > same reboot with filo.zelf.
> > >
> > > See attached Config, compiled with gcc4.0.1 RHEL4
> > >
> > > Thanks!
> > > > On 9/8/06, Al Boldi  wrote:
> > > > > yhlu wrote:
> > > > > > did you try filo on Etherboot?
> > > > > >
> > > > > > I remember I first tried out on UHCI, and then added OHCI support.
> > > > >
> > > > > Yes, but filo.zlilo on etherboot5.4.2 just reboots on initial
> > > > > loading.
> > > > >
> > > > > Filo 0.5 from openbios.org works fine with ide but not usb.
> > > > >
> > > > > Also, the i440bx board has a UHCI controller.
> > > > >
> > > > > Thanks for looking into this!
> > > > > > YH
> > > > > >
> > > > > > On 9/7/06, Stefan Reinauer  wrote:
> > > > > > > Hi,
> > > > > > >
> > > > > > > anyone has an idea on this one?
> > > > > > >
> > > > > > > ----- Forwarded message from Al Boldi -----
> > > > > > >
> > > > > > > Date: Thu, 7 Sep 2006 13:52:28 +0300
> > > > > > > From: Al Boldi 
> > > > > > > To: Stefan Reinauer 
> > > > > > > Cc: [e-mail],
> > > > > > > [e-mail] Subject: Re: USB
> > > > > > > bootloader
> > > > > > >
> > > > > > >
> > > > > > > Thanks for your response!
> > > > > > >
> > > > > > > Stefan Reinauer wrote:
> > > > > > > > * Al Boldi  [060904 20:58]:
> > > > > > > > >     FILO version 0.5 ....
> > > > > > > > >     Can't get memory map from firmware. Using hardcoded
> > > > > > > > > default. Press ...
> > > > > > > > >     boot: uda1:/vmlinuz
> > > > > > > > >     LinuxLabs USB bootloader
> > > > > > > > >     New USB device, setting address 2  (repeats 1-4 times)
> > > > > > > > >     boot: uda1:/vmlinuz
> > > > > > > > >     LinuxLabs USB bootloader
> > > > > > > > >     Out of heap space
> > > > > > > >
> > > > > > > > Please try increasing the heap space in i386/ldscript by
> > > > > > > > changing the following lines:
> > > > > > > >    /* 16KB heap and stack */
> > > > > > > >    HEAP_SIZE = 16384;
> > > > > > > > to
> > > > > > > >    /* 32KB heap and 16K stack */
> > > > > > > >    HEAP_SIZE = 32768;
> > > > > > > >
> > > > > > > > > And, how can filo 0.5 be fixed to boot USB?
> > > > > > > >
> > > > > > > > If the message stays, try all the way up to 262144.
> > > > > > >
> > > > > > > Ok, the message is gone, but it still does not boot.
> > > > > > >
> > > > > > > Turning on debug repeats this:
> > > > > > >
> > > > > > > FILO version 0.5 (root@localhost) Thu Sep  7 13:40:13 AST 2006
> > > > > > > collect_sys_info: boot eax = 0x0
> > > > > > > collect_sys_info: boot ebx = 0x0
> > > > > > > collect_sys_info: boot arg = 0xfeee330
> > > > > > > collect_elfboot_info: Bootloader: Etherboot
> > > > > > > collect_elfboot_info: Version: 5.4.1
> > > > > > > malloc_diag: alloc: 0 bytes (0 blocks), free: 262136 bytes (1
> > > > > > > blocks) malloc_diag: alloc: 16 bytes (1 blocks), free: 262120
> > > > > > > bytes (1 blocks) collect_elfboot_info: Image name:
> > > > > > > /tftpboot/boot/pxelinux.0 malloc_diag: alloc: 32 bytes (2
> > > > > > > blocks), free: 262104 bytes (1 blocks) collect_linuxbios_info:
> > > > > > > Searching for LinuxBIOS tables...
> > > > > > > Can't get memory map from firmware. Using hardcoded default.
> > > > > > > malloc_diag: alloc: 72 bytes (3 blocks), free: 262064 bytes (1
> > > > > > > blocks) collect_sys_info: 0000000000000000-00000000000a0000
> > > > > > > collect_sys_info: 0000000000100000-0000000002000000
> > > > > > > collect_sys_info: RAM 32 MB
> > > > > > > relocate: Current location: 0x100000-0x16d827
> > > > > > > relocate: Relocating to 0x1f927d0-0x1fffff7... ok
> > > > > > > setup_timers: CPU 413 MHz
> > > > > > > pci_init: Scanning PCI: found 9 devices
> > > > > > > malloc_diag: alloc: 192 bytes (4 blocks), free: 261944 bytes (1
> > > > > > > blocks) pci_init: 00:00.0 8086:7120 0600 00
> > > > > > > pci_init: 00:01.0 8086:7121 0300 00
> > > > > > > pci_init: 00:1e.0 8086:2418 0604 00
> > > > > > > pci_init: 01:04.0 1282:9102 0200 00
> > > > > > > pci_init: 01:05.0 10ec:8139 0200 00
> > > > > > > pci_init: 01:0a.0 1191:8040 0100 00
> > > > > > > pci_init: 00:1f.0 8086:2410 0601 00
> > > > > > > pci_init: 00:1f.1 8086:2411 0101 80
> > > > > > > pci_init: 00:1f.2 8086:2412 0c03 00
> > > > > > >
> > > > > > > boot: uda1:/vmlinuz
> > > > > > > malloc_diag: alloc: 216 bytes (5 blocks), free: 261920 bytes (1
> > > > > > > blocks) malloc_diag: alloc: 232 bytes (6 blocks), free: 261904
> > > > > > > bytes (1 blocks) file_open: dev=uda1, path=/vmlinuz
> > > > > > > LinuxLabs USB bootloader
> > > > > > > uhc_init: Found UHCI at ffffd000
> > > > > > > uhc_reset: Resetting UHCI
> > > > > > > uhc_init: uhc_init setting framelist to: 01e927d0
> > > > > > > uhc_start: Starting UHCI
> > > > > > > dump_uhci: HCI at ffffd000
> > > > > > > malloc_diag: alloc: 8432 bytes (7 blocks), free: 253704 bytes (1
> > > > > > > blocks) init_framelist: frame_list is at 12a000
> > > > > > > dump_link: frame_list_link: addr: 00125850
> > > > > > > dump_link: frame_list_link:  raw addr: 1fb8020
> > > > > > > dump_link: frame_list_link: terminate: 0
> > > > > > > dump_link: frame_list_link: queue: 1
> > > > > > > dump_link: frame_list_link: depth: 0
> > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes
> > > > > > > (1 blocks) poll_usb: poll_usb1 i=0 poll_u_root_hub1 v=00001083
> > > > > > > poll_u_root_hub2 v=00001083      poll_u_root_hub21 v=00001083
> > > > > > > Connection on port d010 New USB device, setting address 2
> > > > > > > uhci_control_msg: uhci_control_msg: request_type = 0 request = 5
> > > > > > > wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free:
> > > > > > > 246520 bytes (1 blocks) dump_uhci: HCI at ffffd000
> > > > > > > dump_td: failed_transaction: TD(0011d860):
> > > > > > > dump_td: failed_transaction: type: SETUP
> > > > > > > dump_td: failed_transaction: retries: 3
> > > > > > > dump_td: failed_transaction: IOC
> > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > dump_td: failed_transaction: data_toggle: 0
> > > > > > > dump_td: failed_transaction: max_transfer: 7
> > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > dump_td: failed_transaction: link:
> > > > > > > dump_link:      failed_transaction: addr: 0011d880
> > > > > > > dump_link:      failed_transaction:  raw addr: 1fb0050
> > > > > > > dump_link:      failed_transaction: terminate: 0
> > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > dump_td: failed_transaction: TD(0011d880):
> > > > > > > dump_td: failed_transaction: type: IN
> > > > > > > dump_td: failed_transaction: retries: 0
> > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > dump_td: failed_transaction: data_toggle: 1
> > > > > > > dump_td: failed_transaction: max_transfer: 7ff
> > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > dump_td: failed_transaction: link:
> > > > > > > dump_link:      failed_transaction: addr: fe16d830
> > > > > > > dump_link:      failed_transaction:  raw addr: 0000
> > > > > > > dump_link:      failed_transaction: terminate: 1
> > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes
> > > > > > > (1 blocks) configure_device: configure_device: set_address
> > > > > > > failed!
> > > > > > >
> > > > > > > poll_u_root_hub: poll_u_root_hub1 v=00001080    poll_usb1 i=0
> > > > > > > poll_u_root_hub1 v=00001083      poll_u_root_hub2 v=00001083
> > > > > > > poll_u_root_hub21 v=00001083 Connection on port d010
> > > > > > > New USB device, setting address 2
> > > > > > > uhci_control_msg: uhci_control_msg: request_type = 0 request = 5
> > > > > > > wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks), free:
> > > > > > > 246520 bytes (1 blocks) dump_uhci: HCI at ffffd000
> > > > > > > dump_td: failed_transaction: TD(0011d860):
> > > > > > > dump_td: failed_transaction: type: SETUP
> > > > > > > dump_td: failed_transaction: retries: 3
> > > > > > > dump_td: failed_transaction: IOC
> > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > dump_td: failed_transaction: data_toggle: 0
> > > > > > > dump_td: failed_transaction: max_transfer: 7
> > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > dump_td: failed_transaction: link:
> > > > > > > dump_link:      failed_transaction: addr: 0011d880
> > > > > > > dump_link:      failed_transaction:  raw addr: 1fb0050
> > > > > > > dump_link:      failed_transaction: terminate: 0
> > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > dump_td: failed_transaction: TD(0011d880):
> > > > > > > dump_td: failed_transaction: type: IN
> > > > > > > dump_td: failed_transaction: retries: 0
> > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > dump_td: failed_transaction: data_toggle: 1
> > > > > > > dump_td: failed_transaction: max_transfer: 7ff
> > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > dump_td: failed_transaction: link:
> > > > > > > dump_link:      failed_transaction: addr: fe16d830
> > > > > > > dump_link:      failed_transaction:  raw addr: 0000
> > > > > > > dump_link:      failed_transaction: terminate: 1
> > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624 bytes
> > > > > > > (1 blocks) configure_device: configure_device: set_address
> > > > > > > failed!
> > > > > > >
> > > > > > > (...repeats...)
> > > > > > >
> > > > > > >
> > > > > > > Thanks again!
> > > > > > >
> > > > > > > --
> > > > > > > Al
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > ----- End forwarded message -----
> > > > > > >
> > > > > > > --
> > > > > > > coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
> > > > > > >      Tel.: [phone] • Fax: [phone]
> > > > > > > Email: [e-mail]  • http://www.coresystems.de/
> > > > > > >
> > > > > > > --
> > > > > > > linuxbios mailing list
> > > > > > > [e-mail]
> > > > > > > http://www.openbios.org/mailman/listinfo/linuxbios

[LinuxBIOS] (fwd) Re: USB bootloader

[Al Boldi]

yhlu wrote:
> Are you using normal BIOS instead of LinuxBIOS?

Yes.

Does LinuxBIOS work with i440bx?

Thanks!
> On 9/10/06, Al Boldi  wrote:
> > yhlu wrote:
> > > http://www.linuxbios.org/index.php/Etherboot
> >
> > Success!  Thanks a lot!
> >
> > This info should probably be in the README.
> >
> > The following flags in src/arch/i386/Config are critical for a normal
> > bios: CFLAGS+= -DPCBIOS
> > #CFLAGS+= -DLINUXBIOS
> > CFLAGS+= -DCONFIG_PCI_DIRECT
> > CFLAGS+= -DCONSOLE_DIRECT_VGA
> > #filo is for some reason dependent on serial; will hang otherwise
> > CFLAGS+= -DCONSOLE_SERIAL -DCOMCONSOLE=0x3f8
> > #don't uncomment this one; will slow down display on fast machines (P4)
> > #CFLAGS+= -DCOMPRESERVE
> >
> > Confirmed boot for filo.zelf, filo.zlilo, filo.zrom on UHCI i440bx/zx,
> > i810, and VIA.
> >
> > There is one thing though, it only boots on a second try after detecting
> > the USB-device, like this:
> >    boot: uda1:/vmlinuz
> >    LinuxLabs USB bootloader
> >    New USB device, setting address 2  (repeats 1-forever times,
> >
> > until usb-device pulled)
> >        boot: uda1:/vmlinuz
> >        LinuxLabs USB bootloader
> >        (...now boots ok @ 100kb/s ...)
> >
> > Any easy way to fix this?
> >
> > Thanks again!
> > > YH
> > >
> > > On 9/9/06, Al Boldi  wrote:
> > > > yhlu wrote:
> > > > > you need to use filo.zelf
> > > >
> > > > same reboot with filo.zelf.
> > > >
> > > > See attached Config, compiled with gcc4.0.1 RHEL4
> > > >
> > > > Thanks!
> > > > > On 9/8/06, Al Boldi  wrote:
> > > > > > yhlu wrote:
> > > > > > > did you try filo on Etherboot?
> > > > > > >
> > > > > > > I remember I first tried out on UHCI, and then added OHCI
> > > > > > > support.
> > > > > >
> > > > > > Yes, but filo.zlilo on etherboot5.4.2 just reboots on initial
> > > > > > loading.
> > > > > >
> > > > > > Filo 0.5 from openbios.org works fine with ide but not usb.
> > > > > >
> > > > > > Also, the i440bx board has a UHCI controller.
> > > > > >
> > > > > > Thanks for looking into this!
> > > > > >
> > > > > > > YH
> > > > > > >
> > > > > > > On 9/7/06, Stefan Reinauer  wrote:
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > anyone has an idea on this one?
> > > > > > > >
> > > > > > > > ----- Forwarded message from Al Boldi -----
> > > > > > > >
> > > > > > > > Date: Thu, 7 Sep 2006 13:52:28 +0300
> > > > > > > > From: Al Boldi 
> > > > > > > > To: Stefan Reinauer 
> > > > > > > > Cc: [e-mail],
> > > > > > > > [e-mail] Subject: Re: USB
> > > > > > > > bootloader
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks for your response!
> > > > > > > >
> > > > > > > > Stefan Reinauer wrote:
> > > > > > > > > * Al Boldi  [060904 20:58]:
> > > > > > > > > >     FILO version 0.5 ....
> > > > > > > > > >     Can't get memory map from firmware. Using hardcoded
> > > > > > > > > > default. Press ...
> > > > > > > > > >     boot: uda1:/vmlinuz
> > > > > > > > > >     LinuxLabs USB bootloader
> > > > > > > > > >     New USB device, setting address 2  (repeats 1-4
> > > > > > > > > > times) boot: uda1:/vmlinuz
> > > > > > > > > >     LinuxLabs USB bootloader
> > > > > > > > > >     Out of heap space
> > > > > > > > >
> > > > > > > > > Please try increasing the heap space in i386/ldscript by
> > > > > > > > > changing the following lines:
> > > > > > > > >    /* 16KB heap and stack */
> > > > > > > > >    HEAP_SIZE = 16384;
> > > > > > > > > to
> > > > > > > > >    /* 32KB heap and 16K stack */
> > > > > > > > >    HEAP_SIZE = 32768;
> > > > > > > > >
> > > > > > > > > > And, how can filo 0.5 be fixed to boot USB?
> > > > > > > > >
> > > > > > > > > If the message stays, try all the way up to 262144.
> > > > > > > >
> > > > > > > > Ok, the message is gone, but it still does not boot.
> > > > > > > >
> > > > > > > > Turning on debug repeats this:
> > > > > > > >
> > > > > > > > FILO version 0.5 (root@localhost) Thu Sep  7 13:40:13 AST
> > > > > > > > 2006 collect_sys_info: boot eax = 0x0
> > > > > > > > collect_sys_info: boot ebx = 0x0
> > > > > > > > collect_sys_info: boot arg = 0xfeee330
> > > > > > > > collect_elfboot_info: Bootloader: Etherboot
> > > > > > > > collect_elfboot_info: Version: 5.4.1
> > > > > > > > malloc_diag: alloc: 0 bytes (0 blocks), free: 262136 bytes
> > > > > > > > (1 blocks) malloc_diag: alloc: 16 bytes (1 blocks), free:
> > > > > > > > 262120 bytes (1 blocks) collect_elfboot_info: Image name:
> > > > > > > > /tftpboot/boot/pxelinux.0 malloc_diag: alloc: 32 bytes (2
> > > > > > > > blocks), free: 262104 bytes (1 blocks)
> > > > > > > > collect_linuxbios_info: Searching for LinuxBIOS tables...
> > > > > > > > Can't get memory map from firmware. Using hardcoded default.
> > > > > > > > malloc_diag: alloc: 72 bytes (3 blocks), free: 262064 bytes
> > > > > > > > (1 blocks) collect_sys_info:
> > > > > > > > 0000000000000000-00000000000a0000 collect_sys_info:
> > > > > > > > 0000000000100000-0000000002000000 collect_sys_info: RAM 32
> > > > > > > > MB
> > > > > > > > relocate: Current location: 0x100000-0x16d827
> > > > > > > > relocate: Relocating to 0x1f927d0-0x1fffff7... ok
> > > > > > > > setup_timers: CPU 413 MHz
> > > > > > > > pci_init: Scanning PCI: found 9 devices
> > > > > > > > malloc_diag: alloc: 192 bytes (4 blocks), free: 261944 bytes
> > > > > > > > (1 blocks) pci_init: 00:00.0 8086:7120 0600 00
> > > > > > > > pci_init: 00:01.0 8086:7121 0300 00
> > > > > > > > pci_init: 00:1e.0 8086:2418 0604 00
> > > > > > > > pci_init: 01:04.0 1282:9102 0200 00
> > > > > > > > pci_init: 01:05.0 10ec:8139 0200 00
> > > > > > > > pci_init: 01:0a.0 1191:8040 0100 00
> > > > > > > > pci_init: 00:1f.0 8086:2410 0601 00
> > > > > > > > pci_init: 00:1f.1 8086:2411 0101 80
> > > > > > > > pci_init: 00:1f.2 8086:2412 0c03 00
> > > > > > > >
> > > > > > > > boot: uda1:/vmlinuz
> > > > > > > > malloc_diag: alloc: 216 bytes (5 blocks), free: 261920 bytes
> > > > > > > > (1 blocks) malloc_diag: alloc: 232 bytes (6 blocks), free:
> > > > > > > > 261904 bytes (1 blocks) file_open: dev=uda1, path=/vmlinuz
> > > > > > > > LinuxLabs USB bootloader
> > > > > > > > uhc_init: Found UHCI at ffffd000
> > > > > > > > uhc_reset: Resetting UHCI
> > > > > > > > uhc_init: uhc_init setting framelist to: 01e927d0
> > > > > > > > uhc_start: Starting UHCI
> > > > > > > > dump_uhci: HCI at ffffd000
> > > > > > > > malloc_diag: alloc: 8432 bytes (7 blocks), free: 253704
> > > > > > > > bytes (1 blocks) init_framelist: frame_list is at 12a000
> > > > > > > > dump_link: frame_list_link: addr: 00125850
> > > > > > > > dump_link: frame_list_link:  raw addr: 1fb8020
> > > > > > > > dump_link: frame_list_link: terminate: 0
> > > > > > > > dump_link: frame_list_link: queue: 1
> > > > > > > > dump_link: frame_list_link: depth: 0
> > > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624
> > > > > > > > bytes (1 blocks) poll_usb: poll_usb1 i=0 poll_u_root_hub1
> > > > > > > > v=00001083 poll_u_root_hub2 v=00001083     
> > > > > > > > poll_u_root_hub21 v=00001083 Connection on port d010 New USB
> > > > > > > > device, setting address 2 uhci_control_msg:
> > > > > > > > uhci_control_msg: request_type = 0 request = 5 wLength=0
> > > > > > > > malloc_diag: alloc: 15616 bytes (9 blocks), free: 246520
> > > > > > > > bytes (1 blocks) dump_uhci: HCI at ffffd000
> > > > > > > > dump_td: failed_transaction: TD(0011d860):
> > > > > > > > dump_td: failed_transaction: type: SETUP
> > > > > > > > dump_td: failed_transaction: retries: 3
> > > > > > > > dump_td: failed_transaction: IOC
> > > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > > dump_td: failed_transaction: data_toggle: 0
> > > > > > > > dump_td: failed_transaction: max_transfer: 7
> > > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > > dump_td: failed_transaction: link:
> > > > > > > > dump_link:      failed_transaction: addr: 0011d880
> > > > > > > > dump_link:      failed_transaction:  raw addr: 1fb0050
> > > > > > > > dump_link:      failed_transaction: terminate: 0
> > > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > > dump_td: failed_transaction: TD(0011d880):
> > > > > > > > dump_td: failed_transaction: type: IN
> > > > > > > > dump_td: failed_transaction: retries: 0
> > > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > > dump_td: failed_transaction: data_toggle: 1
> > > > > > > > dump_td: failed_transaction: max_transfer: 7ff
> > > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > > dump_td: failed_transaction: link:
> > > > > > > > dump_link:      failed_transaction: addr: fe16d830
> > > > > > > > dump_link:      failed_transaction:  raw addr: 0000
> > > > > > > > dump_link:      failed_transaction: terminate: 1
> > > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624
> > > > > > > > bytes (1 blocks) configure_device: configure_device:
> > > > > > > > set_address failed!
> > > > > > > >
> > > > > > > > poll_u_root_hub: poll_u_root_hub1 v=00001080    poll_usb1
> > > > > > > > i=0 poll_u_root_hub1 v=00001083      poll_u_root_hub2
> > > > > > > > v=00001083 poll_u_root_hub21 v=00001083 Connection on port
> > > > > > > > d010 New USB device, setting address 2
> > > > > > > > uhci_control_msg: uhci_control_msg: request_type = 0 request
> > > > > > > > = 5 wLength=0 malloc_diag: alloc: 15616 bytes (9 blocks),
> > > > > > > > free: 246520 bytes (1 blocks) dump_uhci: HCI at ffffd000
> > > > > > > > dump_td: failed_transaction: TD(0011d860):
> > > > > > > > dump_td: failed_transaction: type: SETUP
> > > > > > > > dump_td: failed_transaction: retries: 3
> > > > > > > > dump_td: failed_transaction: IOC
> > > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > > dump_td: failed_transaction: data_toggle: 0
> > > > > > > > dump_td: failed_transaction: max_transfer: 7
> > > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > > dump_td: failed_transaction: link:
> > > > > > > > dump_link:      failed_transaction: addr: 0011d880
> > > > > > > > dump_link:      failed_transaction:  raw addr: 1fb0050
> > > > > > > > dump_link:      failed_transaction: terminate: 0
> > > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > > dump_td: failed_transaction: TD(0011d880):
> > > > > > > > dump_td: failed_transaction: type: IN
> > > > > > > > dump_td: failed_transaction: retries: 0
> > > > > > > > dump_td: failed_transaction: active: 0001
> > > > > > > > dump_td: failed_transaction: device_addr: 00
> > > > > > > > dump_td: failed_transaction: endpoint: 0
> > > > > > > > dump_td: failed_transaction: data_toggle: 1
> > > > > > > > dump_td: failed_transaction: max_transfer: 7ff
> > > > > > > > dump_td: failed_transaction: actual: 0
> > > > > > > > dump_td: failed_transaction: link:
> > > > > > > > dump_link:      failed_transaction: addr: fe16d830
> > > > > > > > dump_link:      failed_transaction:  raw addr: 0000
> > > > > > > > dump_link:      failed_transaction: terminate: 1
> > > > > > > > dump_link:      failed_transaction: queue: 0
> > > > > > > > dump_link:      failed_transaction: depth: 0
> > > > > > > > malloc_diag: alloc: 11512 bytes (8 blocks), free: 250624
> > > > > > > > bytes (1 blocks) configure_device: configure_device:
> > > > > > > > set_address failed!
> > > > > > > >
> > > > > > > > (...repeats...)
> > > > > > > >
> > > > > > > >
> > > > > > > > Thanks again!
> > > > > > > >
> > > > > > > > --
> > > > > > > > Al
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > ----- End forwarded message -----
> > > > > > > >
> > > > > > > > --
> > > > > > > > coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
> > > > > > > >      Tel.: [phone] • Fax: [phone]
> > > > > > > > Email: [e-mail]  • http://www.coresystems.de/
> > > > > > > >
> > > > > > > > --
> > > > > > > > linuxbios mailing list
> > > > > > > > [e-mail]
> > > > > > > > http://www.openbios.org/mailman/listinfo/linuxbios

[LinuxBIOS] (fwd) Re: USB bootloader

[Richard Smith]

> Yes.
>
> Does LinuxBIOS work with i440bx?

Depends on your definition of work.  It boots.   Do you need working RAM? :)

[LinuxBIOS] (fwd) Re: USB bootloader

[Al Boldi]

Richard Smith wrote:
> > Does LinuxBIOS work with i440bx?
>
> Depends on your definition of work.  It boots.   Do you need working RAM?

Did you get filo to load?

And, does the filo USB bootloader work without retrying the USB device under 
LinuxBIOS?

Also, which target did you use?

Thanks!

[LinuxBIOS] (fwd) Re: USB bootloader

[Richard Smith]

On 9/12/06, Al Boldi  wrote:
> > Depends on your definition of work.  It boots.   Do you need working RAM?
>
> Did you get filo to load?

Sorry.  I was trying to be funny and ended up not being clear.

i440bx does not currently work in V2.  It will boot and dump the
contents of the SPD for the RAM you have installed but goes no
further.  RAM is not enabled and without RAM you can't do anything.

[LinuxBIOS] (fwd) Re: USB bootloader

[Al Boldi]

Richard Smith wrote:
> On 9/12/06, Al Boldi  wrote:
> > > Depends on your definition of work.  It boots.   Do you need working
> > > RAM?
> >
> > Did you get filo to load?
>
> Sorry.  I was trying to be funny and ended up not being clear.
>
> i440bx does not currently work in V2.

Ok, so has anyone tried filo with LinuxBIOS, on any board, and found that the 
USB bootloader loads on first try of detecting the USB device?

And, does filo affect the bios state of the machine?  i.e:  filo boots 
perfectly but apm support is mysteriously gone.

Also, is it possible to instruct filo to boot the bootblock?

Thanks for enduring my questions!

[LinuxBIOS] (fwd) Re: USB bootloader

[yhlu]

1. with LinuxBIOS, It works with one Tyan Intel based MB (UHCI) and
some other Opteron base MBs.
2. maybe Etherboot heap used by FILO USB packet buffer overwirte the
APM info in RAM.
you need to find out where is APM info is.
3. Bootblock on flash? You could boot elf on flash. mem@0xfff8000

YH.

On 9/13/06, Al Boldi  wrote:
> Richard Smith wrote:
> > On 9/12/06, Al Boldi  wrote:
> > > > Depends on your definition of work.  It boots.   Do you need working
> > > > RAM?
> > >
> > > Did you get filo to load?
> >
> > Sorry.  I was trying to be funny and ended up not being clear.
> >
> > i440bx does not currently work in V2.
>
> Ok, so has anyone tried filo with LinuxBIOS, on any board, and found that the
> USB bootloader loads on first try of detecting the USB device?
>
> And, does filo affect the bios state of the machine?  i.e:  filo boots
> perfectly but apm support is mysteriously gone.
>
> Also, is it possible to instruct filo to boot the bootblock?
>
> Thanks for enduring my questions!

[LinuxBIOS] (fwd) Re: USB bootloader

[Al Boldi]

yhlu wrote:
> with LinuxBIOS, It works with one Tyan Intel based MB (UHCI) and
>
> some other Opteron base MBs.

Great!  So maybe the delayed USB boot is hw related, but why?
> maybe Etherboot heap used by FILO USB packet buffer overwirte the
>
> APM info in RAM.

This happens even with FILO IDE.

Etherboot PXE works OK.
> you need to find out where is APM info is.

How can I find out?
> Bootblock on flash? You could boot elf on flash. mem@0xfff8000

Bootblock on IDE/USB.  Why is it not possible to boot the the 512byte BBS?

Thanks!

[LinuxBIOS] (fwd) Re: USB bootloader

[Indrek Kruusa]

Al Boldi wrote:
> yhlu wrote:
> > with LinuxBIOS, It works with one Tyan Intel based MB (UHCI) and
> >
> > some other Opteron base MBs.
>
> Great!  So maybe the delayed USB boot is hw related, but why?
> > maybe Etherboot heap used by FILO USB packet buffer overwirte the
> >
> > APM info in RAM.
>
> This happens even with FILO IDE.
>
> Etherboot PXE works OK.

How did you managed to compile etherboot for LinuxBIOS with PXE?

I have tried several confs without success and rom-o-matic.net fails too.

thanks,
Indrek

[LinuxBIOS] (fwd) Re: USB bootloader

[Al Boldi]

Indrek Kruusa wrote:
> Al Boldi wrote:
> > yhlu wrote:
> > > with LinuxBIOS, It works with one Tyan Intel based MB (UHCI) and
> > >
> > > some other Opteron base MBs.
> >
> > Great!  So maybe the delayed USB boot is hw related, but why?
> > > maybe Etherboot heap used by FILO USB packet buffer overwirte the
> > >
> > > APM info in RAM.
> >
> > This happens even with FILO IDE.
> >
> > Etherboot PXE works OK.
>
> How did you managed to compile etherboot for LinuxBIOS with PXE?
>
> I have tried several confs without success and rom-o-matic.net fails too.

yhlu pointed me to this http://www.linuxbios.org/index.php/Etherboot

I had to modify these instructions to get it to work with the normal 
AwardBIOS, as LinuxBIOS does not work on the i440bx board yet.

BTW, does anyone know of a standard way of porting LinuxBIOS to any 
unsupported board?

Thanks!