Can anyone tell me why when following the coreboot wiki procedure for using qemu I would get the error message:
"Unrecognized partitioning scheme"
The last few lines are below:
So.FILO does seem to be able to read something from this disk image, from the output. If relevant, the OS I was using was knoppix.
Also I'd like to know if there an easy way to exit qemu. I keep having to run kill -9 <task number>
--------------------------
Jumping to boot code at 0x10e77c
FILO version 0.5 (dsedrich@nwell) Mon Feb 25 20:06:44 EST 2008
menu: hda3:/boot/filo/menu.lst
IDE time out
reset failed, but slave maybe exist
hda: LBA48 2147MB: QEMU HARDDISK
Unrecognized partitioning scheme
--------------------------------------------------
Here is everything that was outputted:
-------------------------------------------
Welcome to elfboot, the open sourced starter.
[dsedrich@nwell:~] $ qemu -L ~ -hda /home/tmp/disk.img -nographic
Could not configure '/dev/rtc' to have a 1024 Hz timer. This is not a fatal
error, but for better emulation accuracy either use a 2.6 host Linux kernel or
type 'echo 1024 > /proc/sys/dev/rtc/max-user-freq' as root.
coreboot-2.0.0-GRUB2 Tue Feb 26 13:31:40 EST 2008 starting...
Copying coreboot to RAM.
(qemu) Jumping to coreboot.
coreboot-2.0.0-GRUB2 Tue Feb 26 13:31:40 EST 2008 booting...
Enumerating buses...
Finding PCI configuration type.
PCI: Using configuration type 1
PCI_DOMAIN: 0000 enabled
PCI: pci_scan_bus for bus 00
PCI: 00:00.0 [8086/1237] enabled
PCI: 00:01.0 [8086/7000] enabled
PCI: 00:01.1 [8086/7010] enabled
PCI: 00:01.3 [8086/7113] enabled
PCI: 00:02.0 [1013/00b8] enabled
PCI: 00:03.0 [10ec/8029] enabled
PCI: pci_scan_bus returning with max=000
done
Allocating resources...
Reading resources...
Done reading resources.
Setting resources...
I would set ram size to 0x20000 Kbytes
PCI: 00:01.1 20 <- [0x0000001400 - 0x000000140f] size 0x00000010 gran 0x04 io
PCI: 00:02.0 10 <- [0x00fc000000 - 0x00fdffffff] size 0x02000000 gran 0x19 prefmem
PCI: 00:02.0 14 <- [0x00fe000000 - 0x00fe000fff] size 0x00001000 gran 0x0c mem
PCI: 00:03.0 10 <- [0x0000001000 - 0x00000010ff] size 0x00000100 gran 0x08 io
Done setting resources.
Done allocating resources.
Enabling resources...
PCI: 00:00.0 subsystem <- 00/00
PCI: 00:00.0 cmd <- 00
PCI: 00:01.0 subsystem <- 00/00
PCI: 00:01.0 cmd <- 07
PCI: 00:01.1 cmd <- 01
PCI: 00:01.3 cmd <- 00
PCI: 00:02.0 cmd <- 03
PCI: 00:03.0 cmd <- 01
done.
Initializing devices...
Root Device init
PCI: 00:00.0 init
PCI: 00:01.0 init
PCI: 00:01.1 init
PCI: 00:01.3 init
PCI: 00:02.0 init
INSTALL REAL-MODE IDT
DO THE VGA BIOS
found VGA: vid=1013, did=b8
rom base, size: c0000
BAD SIGNATURE 0x0 0x0
biosint: INT# 0x10
biosint: eax 0x2 ebx 0x0 ecx 0x80000001 edx 0x0
biosint: ebp 0x11fac esp 0xffa edi 0x0 esi 0x12538
biosint: ip 0x806e cs 0x0 flags 0x46
BIOSINT: Unsupport int #0x10
PCI: 00:03.0 init
Devices initialized
Copying IRQ routing tables to 0xf0000...done.
Verifing copy of IRQ routing tables at 0xf0000...done
Checking IRQ routing table consistency...
check_pirq_routing_table() - irq_routing_table located at: 0x000f0000
done.
Moving GDT to 0x500...ok
Adjust low_table_end from 0x00000530 to 0x00001000
Adjust rom_table_end from 0x000f0400 to 0x00100000
Wrote coreboot table at: 00000530 - 00000bc4 checksum eb9d
Welcome to elfboot, the open sourced starter.
January 2002, Eric Biederman.
Version 1.3
rom_stream: 0xfffc0000 - 0xfffeffff
Found ELF candidate at offset 0
header_offset is 0
Try to load at offset 0x0
New segment addr 0x100000 size 0x3cfe0 offset 0xc0 filesize 0x12fc8
(cleaned up) New segment addr 0x100000 size 0x3cfe0 offset 0xc0 filesize 0x12fc8
New segment addr 0x13cfe0 size 0x48 offset 0x130a0 filesize 0x48
(cleaned up) New segment addr 0x13cfe0 size 0x48 offset 0x130a0 filesize 0x48
Dropping non PT_LOAD segment
Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x000000000003cfe0 filesz: 0x0000000000012fc8
Clearing Segment: addr: 0x0000000000112fc8 memsz: 0x000000000002a018
Loading Segment: addr: 0x000000000013cfe0 memsz: 0x0000000000000048 filesz: 0x0000000000000048
Jumping to boot code at 0x10e77c
FILO version 0.5 (dsedrich@nwell) Mon Feb 25 20:06:44 EST 2008
menu: hda3:/boot/filo/menu.lst
IDE time out
reset failed, but slave maybe exist
hda: LBA48 2147MB: QEMU HARDDISK
Unrecognized partitioning scheme
Also I'd like to know if there an easy way to exit qemu. I keep having to run kill -9 <task number>
I'll answer the easier one :)
Switch to the terminal in which you started qemu and use Ctrl+C.
Myles
are you sure the file you are using is partitioned?
losetup /dev/loop0 /home/tmp/disk.img sfdisk -l /dev/loop0
If it is not partitioned you can boot it raw: hda:/boot/filo/menu.lst
Note I left the '3' out
ron
-----Original Message----- From: ron minnich [mailto:rminnich@gmail.com] Sent: Tuesday, March 04, 2008 5:02 PM To: David Edrich Cc: Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
If it is not partitioned you can boot it raw: hda:/boot/filo/menu.lst
Note I left the '3' out
[David Edrich] Yes you left the '3' out - I Don't know what that means. Can you tell me where I insert this string to make the 'raw' boot happen?
ron
On Wed, Mar 5, 2008 at 1:50 PM, David Edrich dsedrich@violin-memory.com wrote:
-----Original Message----- From: ron minnich [mailto:rminnich@gmail.com] Sent: Tuesday, March 04, 2008 5:02 PM To: David Edrich Cc: Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
If it is not partitioned you can boot it raw: hda:/boot/filo/menu.lst
Note I left the '3' out
[David Edrich] Yes you left the '3' out - I Don't know what that means. Can you tell me where I insert this string to make the 'raw' boot happen?
He was telling you that hda3:... means look on the 3rd partition. if there are no partitions you use hda:...
This string should be in filo's Config file.
BTW: In my first response about killing qemu I didn't realize you were using -nographic, so my advice probably didn't make sense. I prefer to redirect the serial output and use the graphical display.
Something like: qemu -L BIOS disk.img -serial file:ser_out.txt
Myles
-----Original Message----- From: Myles Watson [mailto:mylesgw@gmail.com] Sent: Wednesday, March 05, 2008 5:00 PM To: David Edrich Cc: Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
On Wed, Mar 5, 2008 at 1:50 PM, David Edrich dsedrich@violin-memory.com wrote:
-----Original Message----- From: ron minnich [mailto:rminnich@gmail.com]
If it is not partitioned you can boot it raw: hda:/boot/filo/menu.lst
Note I left the '3' out
[David Edrich] Yes you left the '3' out - I Don't know what that means. Can you tell me where I
insert this string to make the 'raw'
boot happen?
He was telling you that hda3:... means look on the 3rd partition. if there are no partitions you use hda:...
This string should be in filo's Config file.
[David Edrich] So I modified filo to use hda without the '3'. I got additional message mounted extfs2 - which is great I guess then.... "unrecognized partitioning scheme" "unrecognized partitioning scheme" twice... then nothing.
So...Is there anything else to do in filo to make it boot raw? We added the appropriate menu in the file system in the image.
Does filo recognize only a few partitioning schemes and could we be using then an unusual one? All that we did was follow the instructions in the coreboot qemu wiki. We did no special partitioning to create the image.
Thanks
david, can you just send me your disk image file?
ron
It's like 2 Gigabytes. Even if I Tar it, it will be 100's of megs so it doesn't seem practical to send
From my understanding FILO gets to the "menu" file, in the disk image, without any problems. Then, to access files after that, FILO
want to read some partition information from, I would guess, the MBR -- and there is no MBR from the process we used to generate the disk image file. I think that is the problem. I don't know much about qemu-img options that may get around this or if some FILO options do this. I would guess that that would be where to try and find a way out of this.
I'm told, near the beginning, one can run fdisk on the image file, to create an MBR, but then adding the OS files becomes a problem because you must copy them to some offset in the disk image file.
IS the problem that an MBR is needed and that it should have been created or is there something else to do, to make it boot without an MBR?
-----Original Message----- From: ron minnich [mailto:rminnich@gmail.com] Sent: Thursday, March 06, 2008 4:01 PM To: David Edrich Cc: Myles Watson; Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
david, can you just send me your disk image file?
ron
On Thu, Mar 6, 2008 at 3:06 PM, David Edrich dsedrich@violin-memory.com wrote:
It's like 2 Gigabytes. Even if I Tar it, it will be 100's of megs so it doesn't seem practical to send
From my understanding FILO gets to the "menu" file, in the disk image, without any problems. Then, to access files after that, FILO want to read some partition information from, I would guess, the MBR -- and there is no MBR from the process we used to generate the disk image file. I think that is the problem. I don't know much about qemu-img options that may get around this or if some FILO options do this. I would guess that that would be where to try and find a way out of this.
what's your menu file look like? This stuff should all work without partitions or MBR. We solved the first problem -- by saying hda instead of hda3 -- I guess the second problem is solved in the menu file. Can you show us that file?
ron
It's attached.
-----Original Message----- From: coreboot-bounces@coreboot.org [mailto:coreboot-bounces@coreboot.org] On Behalf Of ron minnich Sent: Thursday, March 06, 2008 11:11 PM To: David Edrich Cc: Myles Watson; Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
On Thu, Mar 6, 2008 at 3:06 PM, David Edrich dsedrich@violin-memory.com wrote:
It's like 2 Gigabytes. Even if I Tar it, it will be 100's of megs so it doesn't seem practical to
send
From my understanding FILO gets to the "menu" file, in the disk image, without any problems. Then,
to access files after that, FILO
want to read some partition information from, I would guess, the MBR -- and there is no MBR from
the process we used to generate the
disk image file. I think that is the problem. I don't know much about qemu-img options that may get
around this or if some FILO
options do this. I would guess that that would be where to try and find a way out of this.
what's your menu file look like? This stuff should all work without partitions or MBR. We solved the first problem -- by saying hda instead of hda3 -- I guess the second problem is solved in the menu file. Can you show us that file?
ron
-- coreboot mailing list coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
yes, it is specifying the equivalent of a partition in the menu.lst.
Now I realize -- I don't know how to NOT do this in filo. Anyone know?
hd(0) instead of hd(0,0)?
ron
[David Edrich]
From my understanding FILO gets to the "menu" file, in the disk image, without any problems. Then, to access files after that, FILO want to read some partition information from, I would guess, the MBR -- and there is no MBR from the process we used to generate the disk image file. I think that is the problem. I don't know much about qemu-img options that may get around this or if some FILO options do this. I would guess that that would be where to try and find a way out of this.
I'm told, near the beginning of the image process, one can run fdisk on the image file, to create an MBR, but then adding the OS files becomes a problem because you must copy them to some offset in the disk image file.
IS the problem that an MBR is needed and that it should have been created or is there something else to do, to make it boot without an MBR?
The menu.lst file is: # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda2 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title David Es Linux (2.6.11) root (hd0,0) kernel vmlinuz-2.6.11 ro quiet # initrd initrd-2.6.9-42.0.3.ELsmp.img
-----Original Message----- From: ron minnich [mailto:rminnich@gmail.com] Sent: Friday, March 07, 2008 1:09 PM To: David Edrich Cc: Myles Watson; Coreboot Subject: Re: [coreboot] qemu error message: "Unrecognized partitioning scheme"
yes, it is specifying the equivalent of a partition in the menu.lst.
Now I realize -- I don't know how to NOT do this in filo. Anyone know?
hd(0) instead of hd(0,0)?
ron
[David Edrich] So does anyone know how to do the above? Has anyone followed the instructions on http://www.coreboot.org/QEMU_Build_Tutorial for using qemu with FILO with success?
The fallback for the emulation would be, it seems to build a Linux Kernel payload.
-
David Edrich -
Myles Watson -
ron minnich