coreboot October 2014

coreboot@coreboot.org

43 participants
111 discussions

Re: [coreboot] unable to build coreboot with grub
by Vipin Gahlaut 12 Oct '14

12 Oct '14

Hi Vladimir, I tried changing under main mainboard -> rom chip size but does not seem to be helping. If I look at .config I suspect that the reason is CONFIG_BOARD_ROMSIZE_KB_256=y which doesn't change even if I change ROM size in main board. Relevant portion of .config after changing it to 512 KB CONFIG_BOARD_ROMSIZE_KB_256=y # CONFIG_COREBOOT_ROMSIZE_KB_64 is not set # CONFIG_COREBOOT_ROMSIZE_KB_128 is not set # CONFIG_COREBOOT_ROMSIZE_KB_256 is not set CONFIG_COREBOOT_ROMSIZE_KB_512=y # CONFIG_COREBOOT_ROMSIZE_KB_1024 is not set # CONFIG_COREBOOT_ROMSIZE_KB_2048 is not set # CONFIG_COREBOOT_ROMSIZE_KB_4096 is not set # CONFIG_COREBOOT_ROMSIZE_KB_8192 is not set # CONFIG_COREBOOT_ROMSIZE_KB_12288 is not set # CONFIG_COREBOOT_ROMSIZE_KB_16384 is not set CONFIG_COREBOOT_ROMSIZE_KB=512 CONFIG_ROM_SIZE=0x80000 May be it is because of the fact that qemu is expected to have only 256KB of BIOS rom. I do not know how much BIOS rom qemu 2.1.2 have. For qemu 0.9.0 it was 256KB and there was a patch ( http://code.coreboot.org/p/buildrom/source/tree/261/buildrom-devel/packages…) to change it to 2MB. However this patch is not applicable on QEMU version 2.1.2 as there are different BIOS_SIZE macros in qemu2.1.2.

1 0

Re: [coreboot] unable to build coreboot with grub
by John Lewis 12 Oct '14

12 Oct '14

Hi, It's in "Chipset Options" -> "Size of CBFS filesystem in ROM" - 0x200000 or 0x400000 will work. Cheers, John. On 12/10/14 10:51, Vipin Gahlaut wrote: > Thanks Vladimir, > > > Can you please let me know how to increase the ROM size? > > > -----Original Message----- > From: Vladimir 'φ-coder/phcoder' Serbinenko [mailto:phcoder@gmail.com > <mailto:phcoder@gmail.com>] > Sent: Sunday, October 12, 2014 3:02 PM > To: Vipin Gahlaut; coreboot > Subject: Re: [coreboot] unable to build coreboot with grub > > On 12.10.2014 08:03, Vipin Gahlaut wrote: > > > Hi, > > > > > > I have cloned latest coreboot and trying to build with grub2 as payload. > > > in make menuconfig I select grub2 instead of seabios. when I fire make > > > command it checkout latest grub and that fails to build. for 2 reasons. > > > > > > 1. Due to some initialization errors that I managed to fix with below > > > changes > > > -struct grub_linux_initrd_context initrd_ctx = { 0, }; > > > +struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 }; > > > > > Sounds like you have an old gcc > > > 2. grub size issue as below that I am unable to resolve and looking > > > for your help. I am building for QEMU and using QEMU version 2.1.2. > > > > > > E: Could not add > > > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes > > > (262 KB)@0x0]; too big? > > > E: Failed to add > > > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM image. > > > > > Increase ROM size. > > > > > > > > > > > > On Sun, Oct 12, 2014 at 11:33 AM, Vipin Gahlaut <gailu96(a)gmail.com > <mailto:gailu96@gmail.com>> wrote: > > Hi, > > I have cloned latest coreboot and trying to build with grub2 as > payload. in make menuconfig I select grub2 instead of seabios. when > I fire make command it checkout latest grub and that fails to build. > for 2 reasons. > > 1. Due to some initialization errors that I managed to fix with > below changes > - struct grub_linux_initrd_context initrd_ctx = { 0, }; > + struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 }; > > 2. grub size issue as below that I am unable to resolve and looking > for your help. I am building for QEMU and using QEMU version 2.1.2. > > E: Could not add > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 > bytes (262 KB)@0x0]; too big? > E: Failed to add > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM > image. > > > > >

3 3

Re: [coreboot] coreboot/filo hangs when enabled all debug option
by Peter Stuge 12 Oct '14

12 Oct '14

Vipin Gahlaut wrote: > If I enable debug_all option in configuration latest coreboot with filo > hangs like below > > FILO version 0.6.0 (vgahlaut@ubuntu) Sun Oct 12 02:47:44 PDT 2014 > boot EAX = 0x0 > boot EBX = 0x0 > boot arg = 0x0 > Current location: 0x101000-0x257fb7 > Relocating to 0x7e77000-0x7fcdfb7... > > Never proceed from here. Check if FILO is built using the reference xgcc toolchain created by 'make crossgcc' and not the toolchain installed by your distribution. It is probably easiest to ensure use of xgcc if you build FILO manually. //Peter

1 0

Re: [coreboot] Coreboot FILO boot from USB
by Vipin Gahlaut 12 Oct '14

12 Oct '14

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 <gailu96(a)gmail.com> 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 > <filo>root (hd0) > <filo>kernel /boot/vmlinuz-2.6.20 root=/dev/hda console=ttyS0 > <filo>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? >

1 0

coreboot/filo hangs when enabled all debug option
by Vipin Gahlaut 12 Oct '14

12 Oct '14

Hi, If I enable debug_all option in configuration latest coreboot with filo hangs like below FILO version 0.6.0 (vgahlaut@ubuntu) Sun Oct 12 02:47:44 PDT 2014 boot EAX = 0x0 boot EBX = 0x0 boot arg = 0x0 Current location: 0x101000-0x257fb7 Relocating to 0x7e77000-0x7fcdfb7... Never proceed from here.

1 0

Re: [coreboot] unable to build coreboot with grub
by Vipin Gahlaut 12 Oct '14

12 Oct '14

Thanks Vladimir, Can you please let me know how to increase the ROM size? -----Original Message----- From: Vladimir 'φ-coder/phcoder' Serbinenko [mailto:phcoder@gmail.com] Sent: Sunday, October 12, 2014 3:02 PM To: Vipin Gahlaut; coreboot Subject: Re: [coreboot] unable to build coreboot with grub On 12.10.2014 08:03, Vipin Gahlaut wrote: > Hi, > > I have cloned latest coreboot and trying to build with grub2 as payload. > in make menuconfig I select grub2 instead of seabios. when I fire make > command it checkout latest grub and that fails to build. for 2 reasons. > > 1. Due to some initialization errors that I managed to fix with below > changes > - struct grub_linux_initrd_context initrd_ctx = { 0, }; > + struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 }; > Sounds like you have an old gcc > 2. grub size issue as below that I am unable to resolve and looking > for your help. I am building for QEMU and using QEMU version 2.1.2. > > E: Could not add > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes > (262 KB)@0x0]; too big? > E: Failed to add > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM image. > Increase ROM size. > > > On Sun, Oct 12, 2014 at 11:33 AM, Vipin Gahlaut <gailu96(a)gmail.com> wrote: > Hi, > > I have cloned latest coreboot and trying to build with grub2 as payload. > in make menuconfig I select grub2 instead of seabios. when I fire make > command it checkout latest grub and that fails to build. for 2 reasons. > > 1. Due to some initialization errors that I managed to fix with below > changes > - struct grub_linux_initrd_context initrd_ctx = { 0, }; > + struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 }; > > 2. grub size issue as below that I am unable to resolve and looking for > your help. I am building for QEMU and using QEMU version 2.1.2. > > E: Could not add [payloads/external/GRUB2/grub2/build/default_payload.elf, > 268862 bytes (262 KB)@0x0]; too big? > E: Failed to add 'payloads/external/GRUB2/grub2/build/default_payload.elf' > into ROM image. > > >

1 0

Re: [coreboot] unable to build coreboot with grub
by Vladimir 'φ-coder/phcoder' Serbinenko 12 Oct '14

12 Oct '14

On 12.10.2014 08:03, Vipin Gahlaut wrote: > Hi, > > I have cloned latest coreboot and trying to build with grub2 as payload. > in make menuconfig I select grub2 instead of seabios. when I fire make > command it checkout latest grub and that fails to build. for 2 reasons. > > 1. Due to some initialization errors that I managed to fix with below > changes > - struct grub_linux_initrd_context initrd_ctx = { 0, }; > + struct grub_linux_initrd_context initrd_ctx = { 0,NULL,0 }; > Sounds like you have an old gcc > 2. grub size issue as below that I am unable to resolve and looking for > your help. I am building for QEMU and using QEMU version 2.1.2. > > E: Could not add > [payloads/external/GRUB2/grub2/build/default_payload.elf, 268862 bytes > (262 KB)@0x0]; too big? > E: Failed to add > 'payloads/external/GRUB2/grub2/build/default_payload.elf' into ROM image. > Increase ROM size. > > >

2 1

Re: [coreboot] unable to build coreboot with grub
by Peter Stuge 12 Oct '14

12 Oct '14

Vipin Gahlaut wrote: > I have cloned latest coreboot and trying to build with grub2 as payload. in > make menuconfig I select grub2 instead of seabios. when I fire make command > it checkout latest grub and that fails to build. I don't think it is wise for coreboot to offer a plethora of payload options, none of which actually work correctly at a given point in time. I think it would be significantly better to only support one or two payload options, and focus on 1) making them work at all and then 2) making them work really well, with useful defaults and good automation of all things that can be automated. //Peter

1 0

Prague meeting: hardware
by Vladimir 'φ-coder/phcoder' Serbinenko 12 Oct '14

12 Oct '14

Hello, all. I've updated http://www.coreboot.org/PragueMeetingHardware#phcoder . If somebody wants me to bring sth, please add a paragraph there, otherwise, I won't take almost anything.

1 0

Re: [coreboot] Coreboot FILO boot from USB
by Vipin Gahlaut 12 Oct '14

12 Oct '14

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 @ 0x100000 (180272 bytes), entry @ 0x100000 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: 0000: 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: 0000: 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: 0000 enabled CPU_CLUSTER: 0 scanning... QEMU: firmware config interface detected QEMU: max_cpus is 1 CPU: APIC: 00 enabled DOMAIN: 0000 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: 0000 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: 0x00000000 +0x08000000 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: 0000 read_resources bus 0 link: 0 DOMAIN: 0000 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: 0000 child on link 0 PCI: 00:00.0 DOMAIN: 0000 resource base 0 size 0 align 0 gran 0 limit ffff flags 40040100 index 10000000 DOMAIN: 0000 resource base 0 size 0 align 0 gran 0 limit ffffffff flags 40040200 index 10000100 DOMAIN: 0000 resource base 0 size a0000 align 0 gran 0 limit 0 flags e0004200 index a DOMAIN: 0000 resource base c0000 size 7f40000 align 0 gran 0 limit 0 flags e0004200 index b DOMAIN: 0000 resource base 510 size 2 align 0 gran 0 limit ffff flags e0000100 index c DOMAIN: 0000 resource base 5658 size 1 align 0 gran 0 limit ffff flags e0000100 index d DOMAIN: 0000 resource base ae00 size 10 align 0 gran 0 limit ffff flags e0000100 index e DOMAIN: 0000 resource base af00 size 20 align 0 gran 0 limit ffff flags e0000100 index f DOMAIN: 0000 resource base afe0 size 4 align 0 gran 0 limit ffff flags e0000100 index 10 DOMAIN: 0000 resource base fec00000 size 100000 align 0 gran 0 limit ffffffff flags e0000200 index 2 DOMAIN: 0000 resource base fee00000 size 10000 align 0 gran 0 limit ffffffff flags e0000200 index 3 PCI: 00:00.0 PCI: 00:01.0 PCI: 00:01.0 resource base 0 size 1000 align 0 gran 0 limit ffff flags c0000100 index 1 PCI: 00:01.0 resource base ff800000 size 800000 align 0 gran 0 limit 0 flags d0000200 index 2 PCI: 00:01.1 PCI: 00:01.1 resource base 0 size 10 align 4 gran 4 limit ffff flags 100 index 20 PCI: 00:01.2 PCI: 00:01.2 resource base 0 size 20 align 5 gran 5 limit ffff flags 100 index 20 PCI: 00:01.3 PCI: 00:01.3 resource base e400 size 40 align 0 gran 0 limit ffff flags d0000100 index 1 PCI: 00:01.3 resource base f00 size 10 align 0 gran 0 limit ffff flags d0000100 index 2 PCI: 00:02.0 PCI: 00:02.0 resource base 0 size 2000000 align 25 gran 25 limit ffffffff flags 1200 index 10 PCI: 00:02.0 resource base 0 size 1000 align 12 gran 12 limit ffffffff flags 200 index 14 PCI: 00:02.0 resource base 0 size 10000 align 16 gran 16 limit ffffffff flags 2200 index 30 PCI: 00:03.0 PCI: 00:03.0 resource base 0 size 20000 align 17 gran 17 limit ffffffff flags 200 index 10 PCI: 00:03.0 resource base 0 size 40 align 6 gran 6 limit ffff flags 100 index 14 PCI: 00:03.0 resource base 0 size 40000 align 18 gran 18 limit ffffffff flags 2200 index 30 DOMAIN: 0000 compute_resources_io: base: 0 size: 0 align: 0 gran: 0 limit: ffff PCI: 00:03.0 14 * [0x0 - 0x3f] io PCI: 00:01.2 20 * [0x40 - 0x5f] io PCI: 00:01.1 20 * [0x60 - 0x6f] io DOMAIN: 0000 compute_resources_io: base: 70 size: 70 align: 6 gran: 0 limit: ffff done DOMAIN: 0000 compute_resources_mem: base: 0 size: 0 align: 0 gran: 0 limit: ffffffff PCI: 00:02.0 10 * [0x0 - 0x1ffffff] prefmem PCI: 00:03.0 30 * [0x2000000 - 0x203ffff] mem PCI: 00:03.0 10 * [0x2040000 - 0x205ffff] mem PCI: 00:02.0 30 * [0x2060000 - 0x206ffff] mem PCI: 00:02.0 14 * [0x2070000 - 0x2070fff] mem DOMAIN: 0000 compute_resources_mem: base: 2071000 size: 2071000 align: 25 gran: 0 limit: ffffffff done avoid_fixed_resources: DOMAIN: 0000 avoid_fixed_resources:@DOMAIN: 0000 10000000 limit 0000ffff avoid_fixed_resources:@DOMAIN: 0000 10000100 limit ffffffff constrain_resources: DOMAIN: 0000 constrain_resources: PCI: 00:00.0 constrain_resources: PCI: 00:01.0 constrain_resources: PCI: 00:01.1 constrain_resources: PCI: 00:01.2 constrain_resources: PCI: 00:01.3 constrain_resources: PCI: 00:02.0 constrain_resources: PCI: 00:03.0 avoid_fixed_resources2: DOMAIN: 0000@10000000 limit 0000ffff lim->base 00005659 lim->limit 0000adff avoid_fixed_resources2: DOMAIN: 0000@10000100 limit ffffffff lim->base 08000000 lim->limit febfffff Setting resources... DOMAIN: 0000 allocate_resources_io: base:5659 size:70 align:6 gran:0 limit:adff Assigned: PCI: 00:03.0 14 * [0x5800 - 0x583f] io Assigned: PCI: 00:01.2 20 * [0x5840 - 0x585f] io Assigned: PCI: 00:01.1 20 * [0x5860 - 0x586f] io DOMAIN: 0000 allocate_resources_io: next_base: 5870 size: 70 align: 6 gran: 0 done DOMAIN: 0000 allocate_resources_mem: base:fc000000 size:2071000 align:25 gran:0 limit:febfffff Assigned: PCI: 00:02.0 10 * [0xfc000000 - 0xfdffffff] prefmem Assigned: PCI: 00:03.0 30 * [0xfe000000 - 0xfe03ffff] mem Assigned: PCI: 00:03.0 10 * [0xfe040000 - 0xfe05ffff] mem Assigned: PCI: 00:02.0 30 * [0xfe060000 - 0xfe06ffff] mem Assigned: PCI: 00:02.0 14 * [0xfe070000 - 0xfe070fff] mem DOMAIN: 0000 allocate_resources_mem: next_base: fe071000 size: 2071000 align: 25 gran: 0 done Root Device assign_resources, bus 0 link: 0 DOMAIN: 0000 assign_resources, bus 0 link: 0 PCI: 00:01.1 20 <- [0x0000005860 - 0x000000586f] size 0x00000010 gran 0x04 io PCI: 00:01.2 20 <- [0x0000005840 - 0x000000585f] size 0x00000020 gran 0x05 io PCI: 00:02.0 10 <- [0x00fc000000 - 0x00fdffffff] size 0x02000000 gran 0x19 prefmem PCI: 00:02.0 14 <- [0x00fe070000 - 0x00fe070fff] size 0x00001000 gran 0x0c mem PCI: 00:02.0 30 <- [0x00fe060000 - 0x00fe06ffff] size 0x00010000 gran 0x10 romem PCI: 00:03.0 10 <- [0x00fe040000 - 0x00fe05ffff] size 0x00020000 gran 0x11 mem PCI: 00:03.0 14 <- [0x0000005800 - 0x000000583f] size 0x00000040 gran 0x06 io PCI: 00:03.0 30 <- [0x00fe000000 - 0x00fe03ffff] size 0x00040000 gran 0x12 romem DOMAIN: 0000 assign_resources, bus 0 link: 0 Root Device assign_resources, bus 0 link: 0 Done setting resources. Show resources in subtree (Root Device)...After assigning values. Root Device child on link 0 CPU_CLUSTER: 0 CPU_CLUSTER: 0 child on link 0 APIC: 00 APIC: 00 DOMAIN: 0000 child on link 0 PCI: 00:00.0 DOMAIN: 0000 resource base 5659 size 70 align 6 gran 0 limit adff flags 40040100 index 10000000 DOMAIN: 0000 resource base fc000000 size 2071000 align 25 gran 0 limit febfffff flags 40040200 index 10000100 DOMAIN: 0000 resource base 0 size a0000 align 0 gran 0 limit 0 flags e0004200 index a DOMAIN: 0000 resource base c0000 size 7f40000 align 0 gran 0 limit 0 flags e0004200 index b DOMAIN: 0000 resource base 510 size 2 align 0 gran 0 limit ffff flags e0000100 index c DOMAIN: 0000 resource base 5658 size 1 align 0 gran 0 limit ffff flags e0000100 index d DOMAIN: 0000 resource base ae00 size 10 align 0 gran 0 limit ffff flags e0000100 index e DOMAIN: 0000 resource base af00 size 20 align 0 gran 0 limit ffff flags e0000100 index f DOMAIN: 0000 resource base afe0 size 4 align 0 gran 0 limit ffff flags e0000100 index 10 DOMAIN: 0000 resource base fec00000 size 100000 align 0 gran 0 limit ffffffff flags e0000200 index 2 DOMAIN: 0000 resource base fee00000 size 10000 align 0 gran 0 limit ffffffff flags e0000200 index 3 PCI: 00:00.0 PCI: 00:01.0 PCI: 00:01.0 resource base 0 size 1000 align 0 gran 0 limit ffff flags c0000100 index 1 PCI: 00:01.0 resource base ff800000 size 800000 align 0 gran 0 limit 0 flags d0000200 index 2 PCI: 00:01.1 PCI: 00:01.1 resource base 5860 size 10 align 4 gran 4 limit adff flags 60000100 index 20 PCI: 00:01.2 PCI: 00:01.2 resource base 5840 size 20 align 5 gran 5 limit adff flags 60000100 index 20 PCI: 00:01.3 PCI: 00:01.3 resource base e400 size 40 align 0 gran 0 limit ffff flags d0000100 index 1 PCI: 00:01.3 resource base f00 size 10 align 0 gran 0 limit ffff flags d0000100 index 2 PCI: 00:02.0 PCI: 00:02.0 resource base fc000000 size 2000000 align 25 gran 25 limit febfffff flags 60001200 index 10 PCI: 00:02.0 resource base fe070000 size 1000 align 12 gran 12 limit febfffff flags 60000200 index 14 PCI: 00:02.0 resource base fe060000 size 10000 align 16 gran 16 limit febfffff flags 60002200 index 30 PCI: 00:03.0 PCI: 00:03.0 resource base fe040000 size 20000 align 17 gran 17 limit febfffff flags 60000200 index 10 PCI: 00:03.0 resource base 5800 size 40 align 6 gran 6 limit adff flags 60000100 index 14 PCI: 00:03.0 resource base fe000000 size 40000 align 18 gran 18 limit febfffff flags 60002200 index 30 Done allocating resources. Enabling resources... PCI: 00:00.0 cmd <- 00 PCI: 00:01.0 cmd <- 00 PCI: 00:01.1 cmd <- 01 PCI: 00:01.2 cmd <- 01 PCI: 00:01.3 cmd <- 00 PCI: 00:02.0 cmd <- 03 PCI: 00:03.0 cmd <- 03 done. Initializing devices... Root Device init CPU_CLUSTER: 0 init Initializing CPU #0 CPU: vendor Intel device 663 CPU: family 06, model 06, stepping 03 CPU #0 initialized PCI: 00:00.0 init Keyboard init... Assigning IRQ 11 to 0:1.2 Assigning IRQ 10 to 0:1.3 Assigning IRQ 11 to 0:3.0 PCI: 00:01.0 init RTC Init PCI: 00:01.1 init IDE: Primary IDE interface: on IDE: Secondary IDE interface: on IDE: Access to legacy IDE ports: off PCI: 00:01.2 init PCI: 00:02.0 init PCI: 00:03.0 init Devices initialized Show all devs...After init. Root Device: enabled 1 CPU_CLUSTER: 0: enabled 1 APIC: 00: enabled 1 DOMAIN: 0000: 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 PCI: 00:01.2: enabled 1 PCI: 00:02.0: enabled 1 PCI: 00:03.0: enabled 1 CPU: 00: enabled 1 Finalize devices... Devices finalized Copying Interrupt Routing Table to 0x000f0000... done. Copying Interrupt Routing Table to 0x07ffb000... done. PIRQ table: 128 bytes. QEMU: found acpi tables in fw_cfg. QEMU: loading "etc/acpi/rsdp" to 0x7fd7000 (len 36) QEMU: loading "etc/acpi/tables" to 0x7fd7040 (len 131072) QEMU: loaded acpi tables from fw_cfg. ACPI tables: 131136 bytes. smbios_write_tables: 07fd6000 Root Device (Emulation QEMU x86 i440fx/piix4) CPU_CLUSTER: 0 (QEMU Northbridge i440fx) APIC: 00 (unknown) DOMAIN: 0000 (QEMU Northbridge i440fx) PCI: 00:00.0 (QEMU Northbridge i440fx) PCI: 00:01.0 (Intel 82371FB/SB/MX/AB/EB/MB Southbridge) PCI: 00:01.1 (Intel 82371FB/SB/MX/AB/EB/MB Southbridge) PCI: 00:01.3 (Intel 82371FB/SB/MX/AB/EB/MB Southbridge) PCI: 00:01.2 (unknown) PCI: 00:02.0 (unknown) PCI: 00:03.0 (unknown) CPU: 00 (unknown) SMBIOS tables: 444 bytes. Writing table forward entry at 0x00000500 Wrote coreboot table at: 00000500, 0x10 bytes, checksum 17e2 Table forward entry ends at 0x00000528. ... aligned to 0x00001000 Writing coreboot table at 0x07fce000 rom_table_end = 0x07fce000 ... aligned to 0x07fd0000 0. 0000000000000000-0000000000000fff: CONFIGURATION TABLES 1. 0000000000001000-000000000009ffff: RAM 2. 00000000000c0000-0000000007fcdfff: RAM 3. 0000000007fce000-0000000007ffffff: CONFIGURATION TABLES 4. 00000000ff800000-00000000ffffffff: RESERVED Wrote coreboot table at: 07fce000, 0x150 bytes, checksum 577d coreboot table: 360 bytes. CBMEM ROOT 0. 07fff000 00001000 CAR GLOBALS 1. 07ffe000 00001000 ROMSTAGE 2. 07ffd000 00001000 GDT 3. 07ffc000 00001000 IRQ TABLE 4. 07ffb000 00001000 ACPI 5. 07fd7000 00024000 SMBIOS 6. 07fd6000 00001000 COREBOOT 7. 07fce000 00008000 CBFS: located payload @ fffd2a38, 70372 bytes. Loading segment from rom address 0xfffd2a38 parameter section (skipped) Loading segment from rom address 0xfffd2a54 code (compression=1) New segment dstaddr 0x100000 memsize 0x154960 srcaddr 0xfffd2ad8 filesize 0x11215 (cleaned up) New segment addr 0x100000 size 0x154960 offset 0xfffd2ad8 filesize 0x11215 Loading segment from rom address 0xfffd2a70 data (compression=1) New segment dstaddr 0x254960 memsize 0x48 srcaddr 0xfffe3ced filesize 0x2f (cleaned up) New segment addr 0x254960 size 0x48 offset 0xfffe3ced filesize 0x2f Loading segment from rom address 0xfffd2a8c Entry Point 0x00101000 Bounce Buffer at 07e4d000, 1575312 bytes Loading Segment: addr: 0x0000000000100000 memsz: 0x0000000000154960 filesz: 0x0000000000011215 lb: [0x0000000000100000, 0x000000000012c030) segment: [0x0000000000100000, 0x0000000000111215, 0x0000000000254960) bounce: [0x0000000007e4d000, 0x0000000007e5e215, 0x0000000007fa1960) Post relocation: addr: 0x0000000007e4d000 memsz: 0x0000000000154960 filesz: 0x0000000000011215 using LZMA [ 0x07e4d000, 07e7416c, 0x07fa1960) <- fffd2ad8 Clearing Segment: addr: 0x0000000007e7416c memsz: 0x000000000012d7f4 FILO 0.6.0, coreboot: 4.0-7016-g0a66991-dirty root_dev = unset [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions.] filo> On Sat, Oct 11, 2014 at 4:39 PM, Vipin Gahlaut <gailu96(a)gmail.com> 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 > <filo>root (hd0) > <filo>kernel /boot/vmlinuz-2.6.20 root=/dev/hda console=ttyS0 > <filo>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? >

1 0

← Newer
1
...
4
5
6
7
8
9
10
11
12
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot October 2014