[coreboot] Coreboot FILO boot from USB
Hi Experts, I am trying to boot Linux from USB using coreboot and FILO and not able to find any documentation what parameter should I set on FILO prompt. I have enabled USB support while building FILO and libpayload. Booting from hard disk works fine as below. Start qemu with -hda disk.img option and give following on FILO prompt root (hd0) kernel /boot/vmlinuz-2.6.20 root=/dev/hda console=ttyS0 boot Now I am trying to boot from USB and start qemu with -usbdevice disk:disk.img I am not finding any information what parameter should I set. I tried using root (hd0) (hd1) (sd0) FILO is not able to find my kernel image in /boot/ See errors below. filo> root (hd1) filo> kernel /boot/vmlinuz-2.6.20 Drive 1 does not exist Error 15: File not found filo> root (sd0) filo> kernel /boot/vmlinuz-2.6.20 Unknown device type: sda Error 15: File not found filo> root (hd0) filo> kernel /boot/vmlinuz-2.6.20 Drive 0 does not exist Error 15: File not found filo> Can someone please let me know what is expected device name for the usb I enabled in qemu? -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Coreboot FILO boot from USB
Hi, I have enabled USB DEBUG option but not getting any usb related log. Any idea why. My qemu command is' qemu-system-i386 -bios ./coreboot.rom -hda hda.img -usbdevice disk:usb.img -nographic and the logs are below coreboot-4.0-7016-g0a66991-dirty Sat Oct 11 14:42:09 PDT 2014 starting... CBMEM: root @ 07fff000 254 entries. Trying CBFS ramstage loader. CBFS: loading stage fallback/ramstage @ 0x10 (180272 bytes), entry @ 0x10 QEMU debugcon not found [port 0x402] coreboot-4.0-7016-g0a66991-dirty Sat Oct 11 14:42:09 PDT 2014 booting... CBMEM: recovering 3/254 entries from root @ 07fff000 Moving GDT to 07ffc000...ok Enumerating buses... Show all devs...Before device enumeration. Root Device: enabled 1 CPU_CLUSTER: 0: enabled 1 APIC: 00: enabled 1 DOMAIN: : enabled 1 PCI: 00:00.0: enabled 1 PCI: 00:01.0: enabled 1 PCI: 00:01.1: enabled 1 PCI: 00:01.3: enabled 1 Compare with tree... Root Device: enabled 1 CPU_CLUSTER: 0: enabled 1 APIC: 00: enabled 1 DOMAIN: : enabled 1 PCI: 00:00.0: enabled 1 PCI: 00:01.0: enabled 1 PCI: 00:01.1: enabled 1 PCI: 00:01.3: enabled 1 scan_static_bus for Root Device CPU_CLUSTER: 0 enabled DOMAIN: enabled CPU_CLUSTER: 0 scanning... QEMU: firmware config interface detected QEMU: max_cpus is 1 CPU: APIC: 00 enabled DOMAIN: scanning... PCI: pci_scan_bus for bus 00 PCI: 00:00.0 [8086/1237] ops PCI: 00:00.0 [8086/1237] enabled PCI: 00:01.0 [8086/7000] bus ops PCI: 00:01.0 [8086/7000] enabled PCI: 00:01.1 [8086/7010] ops PCI: 00:01.1 [8086/7010] enabled PCI: 00:01.2 [8086/7020] ops PCI: 00:01.2 [8086/7020] enabled PCI: 00:01.3 [8086/7113] bus ops PCI: 00:01.3 [8086/7113] enabled PCI: 00:02.0 [1013/00b8] ops PCI: 00:02.0 [1013/00b8] enabled PCI: 00:03.0 [8086/100e] enabled scan_static_bus for PCI: 00:01.0 scan_static_bus for PCI: 00:01.0 done scan_static_bus for PCI: 00:01.3 scan_static_bus for PCI: 00:01.3 done PCI: pci_scan_bus returning with max=001 scan_static_bus for Root Device done done found VGA at PCI: 00:02.0 Setting up VGA for PCI: 00:02.0 Setting PCI_BRIDGE_CTL_VGA for bridge DOMAIN: Setting PCI_BRIDGE_CTL_VGA for bridge Root Device Allocating resources... Reading resources... Root Device read_resources bus 0 link: 0 CPU_CLUSTER: 0 read_resources bus 0 link: 0 APIC: 00 missing read_resources CPU_CLUSTER: 0 read_resources bus 0 link: 0 done QEMU: 10 files in fw_cfg QEMU: etc/boot-fail-wait [size=4] QEMU: etc/smbios/smbios-tables [size=320] QEMU: etc/smbios/smbios-anchor [size=31] QEMU: etc/e820 [size=20] QEMU: genroms/kvmvapic.bin [size=9216] QEMU: etc/system-states [size=6] QEMU: bootorder [size=0] QEMU: etc/acpi/tables [size=131072] QEMU: etc/table-loader [size=4096] QEMU: etc/acpi/rsdp [size=36] QEMU: e820/ram: 0x +0x0800 QEMU: reserve ioports 0x0510-0x0511 [firmware-config] QEMU: reserve ioports 0x5658-0x5658 [vmware-port] QEMU: reserve ioports 0xae00-0xae0f [pci-hotplug] QEMU: reserve ioports 0xaf00-0xaf1f [cpu-hotplug] QEMU: reserve ioports 0xafe0-0xafe3 [piix4-gpe0] DOMAIN: read_resources bus 0 link: 0 DOMAIN: read_resources bus 0 link: 0 done Root Device read_resources bus 0 link: 0 done Done reading resources. Show resources in subtree (Root Device)...After reading. Root Device child on link 0 CPU_CLUSTER: 0 CPU_CLUSTER: 0 child on link 0 APIC: 00 APIC: 00 DOMAIN: child on link 0 PCI: 00:00.0 DOMAIN: resource base 0 size 0 align 0 gran 0 limit flags 40040100 index 1000 DOMAIN: resource base 0 size 0 align 0 gran 0 limit flags 40040200 index 1100 DOMAIN: resource base 0 size a align 0 gran 0 limit 0 flags e0004200 index a DOMAIN: resource base c size 7f4 align 0 gran 0 limit 0 flags e0004200 index b DOMAIN: resource base 510 size 2 align 0 gran 0 limit flags e100 index c DOMAIN: resource base 5658 size 1 align 0 gran 0 limit flags e100 index d DOMAIN: resource base ae00 size 10 align 0 gran 0 limit flags e100 index e DOMAIN: resource base af00 size 20 align 0 gran 0 limit flags e100 index f DOMAIN: resource base afe0 size 4 align 0 gran 0 limit flags e100 index 10 DOMAIN: resource base fec0 size 10 align 0 gran 0 limit flags e200 index 2 DOMAIN: resource base fee0 size 1 align 0 gran 0 limit flags e200 index 3 PCI: 00:00.0 PCI: 00:01.0 PCI: 00:01.0 resource base 0 size 1000 align 0 gran 0 limit flags c100 index 1 PCI: 00:01.0 resource base ff80 size 80 align 0 gran 0 limit 0 flags d200 index 2 PCI: 00:01.1 PCI: 00:01.1 resource base 0 size 10 align 4 gran 4 limit flags 100 index 20 PCI: 00:01.2 PCI: 00:01.2 resource base 0 size 20 align 5 gran 5 limit flags 100 index 20 PCI: 00:01.3 PCI: 00:01.3 resource base e400 size 40 align 0 gran 0 limit flags d100 index 1 PCI: 00:01.3 resource base
Re: [coreboot] Coreboot FILO boot from USB
Looking at blockdev.c I believe that usb disks are listed as ud so I tried root (ud0) with no luck so far. filo> root (ud0) filo> kernel /boot/vmlinuz Error 15: File not found filo> On Sat, Oct 11, 2014 at 4:39 PM, Vipin Gahlaut wrote: > Hi Experts, > > I am trying to boot Linux from USB using coreboot and FILO and not able to > find any documentation what parameter should I set on FILO prompt. I have > enabled USB support while building FILO and libpayload. > > Booting from hard disk works fine as below. > Start qemu with -hda disk.img option and give following on FILO prompt > root (hd0) > kernel /boot/vmlinuz-2.6.20 root=/dev/hda console=ttyS0 > boot > > Now I am trying to boot from USB and start qemu with > -usbdevice disk:disk.img > > I am not finding any information what parameter should I set. I tried > using root (hd0) (hd1) (sd0) FILO is not able to find my kernel image in > /boot/ > > See errors below. > > filo> root > (hd1) > filo> kernel > /boot/vmlinuz-2.6.20 > Drive 1 does not > exist > > > Error 15: File not > found > filo> root > (sd0) > filo> kernel > /boot/vmlinuz-2.6.20 Unknown > device type: sda > > > Error 15: File not > found > filo> root > (hd0) > filo> kernel > /boot/vmlinuz-2.6.20 > Drive 0 does not > exist > > > Error 15: File not > found > filo> > > Can someone please let me know what is expected device name for the usb I > enabled in qemu? > -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
