This is the message I got in the end. Linuxbios tries to load the ELF image. It seems that there are 2 segments in the ELF. In the end, linuxbios jumps to an entry that looks like the in the middle of the first segment. Does it look right? The FILO.elf doesn't seem to load succeffully.
Gin ============================================================
Found ELF candiate at offset 0
(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 filesize 0xd068 (cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize 0x48 Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 filesz: 0x00 0000000000d068 Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 filesz: 0x00 00000000000048
Jumping to boot code at 0x1092e4
entry = 0x001092e4 lb_start = 0x00004000 lb_size = 0x00024000 adjust = 0xfe5d8400 buffer = 0xfe5b8400 elf_boot_notes = 0x00015680 adjusted_boot_notes = 0xfe5eda80
I tested my payload(FILO.elf) with linux loader Grub. It has no problem at all. So something must go wrong when linuxbios jumps to the payload. FILO doesn't seem to run at all. No debug message over the console.
Don't' know if there is anyone familiar with ELF. This is the message over the console at the end. It seems that there are 2 segments in the ELF. In the end, linuxbios jumps to an entry that looks like the in the middle of the first segment. Does it look right?
============================================================
Found ELF candiate at offset 0
(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 filesize 0xd068 (cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize 0x48 Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 filesz: 0x00 0000000000d068 Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 filesz: 0x00 00000000000048
Jumping to boot code at 0x1092e4
entry = 0x001092e4 lb_start = 0x00004000 lb_size = 0x00024000 adjust = 0xfe5d8400 buffer = 0xfe5b8400 elf_boot_notes = 0x00015680 adjusted_boot_notes = 0xfe5eda80
I am not able to get linuxbios to load my payload(FILO.elf). Linuxbios went through and jumps to the entry of the payload.
1. Is the elfboot code robust enough(I checked most of the code, it seems good)? 2. Can you suggest any direction for debugging? (everything looks good to me but it won't boot)? 3. would change the boot loader(rather than elfboot) help?
Thanks, Gin
If you do an 'objdump -f' on the executable, what does it say is the start address? 0x1092e4 seems a bit strange.
Greg
On Dec 1, 2004, at 11:17 PM, Gin wrote:
I tested my payload(FILO.elf) with linux loader Grub. It has no problem at all. So something must go wrong when linuxbios jumps to the payload. FILO doesn't seem to run at all. No debug message over the console.
Don’t’ know if there is anyone familiar with ELF.
This is the message over the console at the end.
It seems that there are 2 segments in the ELF. In the end, linuxbios jumps to an entry that looks like the in the middle of the first segment.
Does it look right?
============================================================
Found ELF candiate at offset 0
(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 filesize 0xd068
(cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize 0x48
Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 filesz: 0x00 0000000000d068
Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 filesz: 0x00 00000000000048
Jumping to boot code at 0x1092e4
entry = 0x001092e4
lb_start = 0x00004000
lb_size = 0x00024000
adjust = 0xfe5d8400
buffer = 0xfe5b8400
elf_boot_notes = 0x00015680
adjusted_boot_notes = 0xfe5eda80
This is the header of my payload Filo.elf. it does have the starting address.
================================================= start address 0x001092e4
Program Header: LOAD off 0x000000a0 vaddr 0x00100000 paddr 0x00100000 align 2**5 filesz 0x0000d048 memsz 0x000270d0 flags rwx LOAD off 0x0000d100 vaddr 0x001270e0 paddr 0x001270e0 align 2**5 filesz 0x00000048 memsz 0x00000048 flags rw- NOTE off 0x000000c0 vaddr 0x00100020 paddr 0x00100020 align 2**5 filesz 0x00000088 memsz 0x00000088 flags r-- ======================================================
-----Original Message----- From: linuxbios-admin@clustermatic.org [mailto:linuxbios-admin@clustermatic.org] On Behalf Of Greg Watson Sent: Thursday, December 02, 2004 10:57 PM To: Gin Cc: 'LinuxBIOS' Subject: Re: jump to boot code
If you do an 'objdump -f' on the executable, what does it say is the start address? 0x1092e4 seems a bit strange.
Greg
On Dec 1, 2004, at 11:17 PM, Gin wrote:
I tested my payload(FILO.elf) with linux loader Grub. It has no problem at all. So something must go wrong when linuxbios jumps to the
payload. FILO doesn't seem to run at all. No debug message over the console.
Dont know if there is anyone familiar with ELF.
This is the message over the console at the end.
It seems that there are 2 segments in the ELF. In the end, linuxbios jumps to an entry that looks like the in the middle of the first segment.
Does it look right?
============================================================
Found ELF candiate at offset 0
(cleaned up) New segment addr 0x100000 size 0x270f0 offset 0xa0 filesize 0xd068
(cleaned up) New segment addr 0x127100 size 0x48 offset 0xd120 filesize 0x48
Dropping non PT_LOAD segment
Loading Segment: addr: 0x0000000000100000 memsz: 0x00000000000270f0 filesz: 0x00 0000000000d068
Loading Segment: addr: 0x0000000000127100 memsz: 0x0000000000000048 filesz: 0x00 00000000000048
Jumping to boot code at 0x1092e4
entry = 0x001092e4
lb_start = 0x00004000
lb_size = 0x00024000
adjust = 0xfe5d8400
buffer = 0xfe5b8400
elf_boot_notes = 0x00015680
adjusted_boot_notes = 0xfe5eda80
_______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
the problem is that your error messages are kind of ok. Did you build a filo with serial port only console?
ron
Yes, when I tested the filo with Grub. I could see the messages over the serial console.....
gin
-----Original Message----- From: Ronald G. Minnich [mailto:rminnich@lanl.gov] Sent: Thursday, December 02, 2004 11:29 PM To: Gin Cc: 'LinuxBIOS' Subject: Re: jump to boot code
the problem is that your error messages are kind of ok. Did you build a filo with serial port only console?
ron
On Fri, Dec 03, 2004 at 09:32:31AM +0800, Gin wrote:
Yes, when I tested the filo with Grub. I could see the messages over the serial console.....
Did you try memtest86 as payload?
Given that filo runs ok under grub, I think the memory configuration of LinuxBIOS is not working properly. Especially the memory size that LB reports might be wrong, I guess.
Did you try memtest86 as payload?
No, do you know where I can get it? Thanks.
Given that filo runs ok under grub, I think the memory configuration of LinuxBIOS is not working properly. Especially the memory size that LB reports might be wrong, I guess.
But the LB size was set during the link time according to the linker script. How does it have to do with my mem configuration?
gin
On Fri, Dec 03, 2004 at 12:35:01PM +0800, Gin wrote:
Did you try memtest86 as payload?
No, do you know where I can get it? Thanks.
Given that filo runs ok under grub, I think the memory configuration of LinuxBIOS is not working properly. Especially the memory size that LB reports might be wrong, I guess.
But the LB size was set during the link time according to the linker script. How does it have to do with my mem configuration?
I meant the size of RAM installed to your board. It is detected by LB at runtime.
On Fri, 3 Dec 2004, Gin wrote:
Yes, when I tested the filo with Grub. I could see the messages over the serial console.....
and nothing over vga, right? your filo is not trying to use vga.
ron
Linuxbios choked when it jumps to the payload. I put a post code in the beginning of the FILO. It doesn't seem to be executed. I think it might have a hard time jumping to the payload entry. Looks like the payload image was loaded into the memory ok. Does anyone have similar experience?
gin
On Mon, 6 Dec 2004, Gin wrote:
Linuxbios choked when it jumps to the payload. I put a post code in the beginning of the FILO. It doesn't seem to be executed. I think it might have a hard time jumping to the payload entry. Looks like the payload image was loaded into the memory ok.
put printk's into linuxbios itself to hexdump the payload once loaded. What is your platform again? I think you still have some memory issues.
ron
-
Gin -
Greg Watson -
Ronald G. Minnich -
Takeshi Sone