Hello,
I tried filo 0.4 from openbios.org, which was able to ide boot but hangs on usb boot with this:
Welcome to elfboot, the open sourced starter. January 2002, Eric Biederman. Version 1.3
rom_stream: 0xfffe0000 - 0xfffeffff Found ELF candiate at offset 0 header_offset is 0 Header addresap[1].size = 0x9f390, mem->map[1].type = 0x1 n_type: 00000001 n_name(8): ELFBoot n_desc(10): Etherboot n_type: 00000002 n_name(8): ELFBoot n_desc(6): 5.4.2 Loading Etherboot version: 5.4.2 access the elf segments Dropping non PT_LOAD segment malloc Enter, size 32, free_mem_ptr 00122d0c malloc 0x00122d0c New segment addr 0x10000 size 0x430c0 offset 0x0 filesize 0xcc90 (cleaned up) New segment addr 0x10000 size 0x430c0 offset 0x0 filesize 0xcc90 lb_start : 0x0000000000100000, lb_end : 0x000000000012a000) start : 0x0000000000010000, middle : 0x000000000001cc90, end : 0x00000000000530c0 Load the segments Loading Segment: addr: 0x0000000000010000 memsz: 0x00000000000430c0 filesz: 0x000000000000cc90 dest:0x0000000000010000, middle:000000000001cc90, end:0x00000000000530c0, start_offset:0000000000000000, offset:0000000000000000 Skip the unused bytes Copy data from the initial buffer dest:0x0SOLE_BTEXT pci_init Scanning PCI: found 28 devices function allot, address = bffffc70 allot(0) function allot, address = bffffc60 Boot from (N)etwork (D)isk or (Q)uit? D
Answer : Disk device present boot = 0x00000001, type = 1, failsafe = 0 function allot, address = bffffc60 Probing pci disk... [FILO]boot eax = 0xe1040170 boot ebx = 0x00800401 boot arg = 0x00000000
FILO version 0.4.1 (root@frlanzf00595) Tue Oct 31 17:00:24 CET 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200 dev=uda1, path=/bzImage name = uda1, type = 3, drive = 0, part = 1, offset = 0x00000000, length = 0x00000000 LinuxLabs USB bootloader Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030c0 Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030e0 frame_list is at bffede50 frame_list_link: addr: fffefe50 frame_list_link: raw addr: 00000800 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 frame_list is at bffebe50 frame_list_link: addr: ffff0650 frame_list_link: raw addr: 00000040 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 New USB device, setting address 2 port = 0x000030d0 controller =0x00000000 lowspeed = 0 next_usb_dev = 0x00000003 addr = 0x00000002 uhci_control_msg: request_type = 00000000 request = 00000005 wLength=0 ctrl_msg( 00000000, 00000000, 00000005, 00000002, 00000000, 00000000, p) 0 bytes in payload lowspeed = u HCI at 000030c0 failed_transaction: TD(0002e5a0): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 0002e5c0 failed_transaction: raw addr: 0003e770 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(0002e5c0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fffefe50 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed! value = 0x00001080 poll_usb 1 hc_type[1] = 00000000
...
There is a USB device, but it won't init! This is a bad thing.
failed to open usb boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200
Now, how can etherboot-filo be fixed to boot at all? And, how can filo 0.5 be fixed to boot USB?
Thanks!
_________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
* jean raymond jeanraymond19769earrond@hotmail.com [061102 07:53]:
Hello,
I tried filo 0.4 from openbios.org, which was able to ide boot but hangs on usb boot with this:
Interesting... There is no filo 0.4 on openbios.org ;-) Only 0.5...
n_type: 00000001 n_name(8): ELFBoot n_desc(10): Etherboot n_type: 00000002 n_name(8): ELFBoot n_desc(6): 5.4.2 Loading Etherboot version: 5.4.2
So you are using etherboot from etherboot.org?
Yinghai, can you help?
Boot from (N)etwork (D)isk or (Q)uit? D
FILO version 0.4.1 (root@frlanzf00595) Tue Oct 31 17:00:24 CET 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200 dev=uda1, path=/bzImage name = uda1, type = 3, drive = 0, part = 1, offset = 0x00000000, length = 0x00000000 LinuxLabs USB bootloader Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030c0 Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030e0 frame_list is at bffede50 frame_list_link: addr: fffefe50 frame_list_link: raw addr: 00000800 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 frame_list is at bffebe50 frame_list_link: addr: ffff0650 frame_list_link: raw addr: 00000040 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 New USB device, setting address 2 port = 0x000030d0 controller =0x00000000 lowspeed = 0 next_usb_dev = 0x00000003 addr = 0x00000002 uhci_control_msg: request_type = 00000000 request = 00000005 wLength=0 ctrl_msg( 00000000, 00000000, 00000005, 00000002, 00000000, 00000000, p) 0 bytes in payload lowspeed = u HCI at 000030c0 failed_transaction: TD(0002e5a0): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 0002e5c0 failed_transaction: raw addr: 0003e770 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(0002e5c0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fffefe50 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed! value = 0x00001080 poll_usb 1 hc_type[1] = 00000000
...
There is a USB device, but it won't init! This is a bad thing.
failed to open usb boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200
What board are you using, what LinuxBIOS revision,...?
Now, how can etherboot-filo be fixed to boot at all? And, how can filo 0.5 be fixed to boot USB?
What's the error you are seeing with filo 0.5?
Stefan
I'm using Etherboot version 5.4.2 from etherboot.org. I'm using LinuxBIOS version2-2394 and a i386 board.
The error is when I want to boot linux which is on device USB (so I use FILO in Etherboot). I use LinuxBIOS and Etherboot. LinuxBIOS works properly, and when I want to load linux, I have this error:
HCI at 000030c0 failed_transaction: TD(0002e5a0): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 0002e5c0 failed_transaction: raw addr: 0003e770 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(0002e5c0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fffefe50 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed!
and it repeats it.
I suppose I have a bad config. So can you give me a config an example of config in order to boot on USB.
Thanks for your help!
From: Stefan Reinauer stepan@coresystems.de To: jean raymond jeanraymond19769earrond@hotmail.com CC: linuxbios@linuxbios.org Subject: Re: [LinuxBIOS] USB Bootloader Date: Thu, 2 Nov 2006 11:32:44 +0100
- jean raymond jeanraymond19769earrond@hotmail.com [061102 07:53]:
Hello,
I tried filo 0.4 from openbios.org, which was able to ide boot but hangs on usb boot with this:
Interesting... There is no filo 0.4 on openbios.org ;-) Only 0.5...
n_type: 00000001 n_name(8): ELFBoot n_desc(10): Etherboot n_type: 00000002 n_name(8): ELFBoot n_desc(6): 5.4.2 Loading Etherboot version: 5.4.2
So you are using etherboot from etherboot.org?
Yinghai, can you help?
Boot from (N)etwork (D)isk or (Q)uit? D
FILO version 0.4.1 (root@frlanzf00595) Tue Oct 31 17:00:24 CET 2006 Press <Enter> for default boot, or <Esc> for boot prompt... boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200 dev=uda1, path=/bzImage name = uda1, type = 3, drive = 0, part = 1, offset = 0x00000000, length
=
0x00000000 LinuxLabs USB bootloader Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030c0 Resetting UHCI uhc_init setting framelist to: 000101b0 Starting UHCI HCI at 000030e0 frame_list is at bffede50 frame_list_link: addr: fffefe50 frame_list_link: raw addr: 00000800 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 frame_list is at bffebe50 frame_list_link: addr: ffff0650 frame_list_link: raw addr: 00000040 frame_list_link: terminate: 00000000 frame_list_link: queue: 00000000 frame_list_link: depth: 00000000 New USB device, setting address 2 port = 0x000030d0 controller =0x00000000 lowspeed = 0
next_usb_dev
= 0x00000003 addr = 0x00000002 uhci_control_msg: request_type = 00000000 request = 00000005 wLength=0 ctrl_msg( 00000000, 00000000, 00000005, 00000002, 00000000, 00000000, p) 0 bytes in payload lowspeed = u HCI at 000030c0 failed_transaction: TD(0002e5a0): failed_transaction: type: SETUP failed_transaction: retries: 00000003 failed_transaction: IOC failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000000 failed_transaction: max_transfer: 00000007 failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: 0002e5c0 failed_transaction: raw addr: 0003e770 failed_transaction: terminate: 00000000 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 failed_transaction: TD(0002e5c0): failed_transaction: type: IN failed_transaction: retries: 00000000 failed_transaction: active: 00000001 failed_transaction: device_addr: 00000000 failed_transaction: endpoint: 00000000 failed_transaction: data_toggle: 00000001 failed_transaction: max_transfer: 000007ff failed_transaction: actual: 00000000 failed_transaction: link: failed_transaction: addr: fffefe50 failed_transaction: raw addr: 00000000 failed_transaction: terminate: 00000001 failed_transaction: queue: 00000000 failed_transaction: depth: 00000000 configure_device: set_address failed! value = 0x00001080 poll_usb 1 hc_type[1] = 00000000
...
There is a USB device, but it won't init! This is a bad thing.
failed to open usb boot: uda1:/bzImage root=/dev/sda2 console=tty0 console=ttyS0,115200
What board are you using, what LinuxBIOS revision,...?
Now, how can etherboot-filo be fixed to boot at all? And, how can filo 0.5 be fixed to boot USB?
What's the error you are seeing with filo 0.5?
Stefan
-- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: info@coresystems.de • http://www.coresystems.de/
-- linuxbios mailing list linuxbios@linuxbios.org http://www.openbios.org/mailman/listinfo/linuxbios
_________________________________________________________________ Add a Yahoo! contact to Windows Live Messenger for a chance to win a free trip! http://www.imagine-windowslive.com/minisites/yahoo/default.aspx?locale=en-us...
* jean raymond jeanraymond19769earrond@hotmail.com [061102 12:39]:
I'm using Etherboot version 5.4.2 from etherboot.org. I'm using LinuxBIOS version2-2394 and a i386 board.
which one?
I suppose I have a bad config. So can you give me a config an example of config in order to boot on USB.
It might just be a missing bit in the USB configuration of the board you are using.
Thanks for your help!
you're welcome.
-
jean raymond -
Stefan Reinauer