I mean if you build tg3filoide_disk.zelf, it will confuse the Etherboot. So you can only build tg3filo.zelf or tg3ide_disk.zelf. Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it. Then connect that to your MB do test. hda1:/ram0_......elf Regards YH _____ From: David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help Hi, I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time. Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support? Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet.... The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a. ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0 There are no sections in this file. Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0 There is no dynamic segment in this file. There are no relocations in this file. There are no unwind sections in this file. No version information found in this file. Thanks, Dave On Fri, 2004-07-09 at 15:48, YhLu wrote: I have got two cpus and four dimms for every CPU. YH _____ From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help Hi, Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase. This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine. I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;) Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that. Thanks, Dave On Fri, 2004-07-09 at 13:05, YhLu wrote: Did you try the tg3--filo.zelf I sent to you? YH
Ah, I got ya. Yes, I do. I'll let you know, if that worked. Thanks, Dave On Mon, 2004-07-12 at 16:01, YhLu wrote:
I mean if you build tg3—filo—ide_disk.zelf, it will confuse the Etherboot. So you can only build tg3—filo.zelf or tg3—ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a.
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks, Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that.
Thanks, Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
Here are the results: I took my known working hard drive and stuck it in the device to test with filo. The results were the same! Meaning a known working kernel & intird on my hard drive failed at the initrd portion, again with the crc error. I'm now going to try a basic etherboot test without filo to see if I can read off of the hard drive, just as a baseline. Any other ideas would be appreciated. Thanks, Dave On Mon, 2004-07-12 at 16:01, YhLu wrote:
I mean if you build tg3—filo—ide_disk.zelf, it will confuse the Etherboot. So you can only build tg3—filo.zelf or tg3—ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a.
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks, Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that.
Thanks, Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
Can you try out my FILO? (http://te.to/~ts1/filo/) If it works, it might help narrow the problem. On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote:
Here are the results:
I took my known working hard drive and stuck it in the device to test with filo. The results were the same! Meaning a known working kernel & intird on my hard drive failed at the initrd portion, again with the crc error.
I'm now going to try a basic etherboot test without filo to see if I can read off of the hard drive, just as a baseline.
Any other ideas would be appreciated.
Thanks, Dave
On Mon, 2004-07-12 at 16:01, YhLu wrote:
I mean if you build tg3?filo?ide_disk.zelf, it will confuse the Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a.
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks, Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that.
Thanks, Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
-- Takeshi
Yes, yes indeed I will try it and Thank you:) On Mon, 2004-07-12 at 21:56, Takeshi Sone wrote:
Can you try out my FILO? (http://te.to/~ts1/filo/) If it works, it might help narrow the problem.
On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote:
Here are the results:
I took my known working hard drive and stuck it in the device to test with filo. The results were the same! Meaning a known working kernel & intird on my hard drive failed at the initrd portion, again with the crc error.
I'm now going to try a basic etherboot test without filo to see if I can read off of the hard drive, just as a baseline.
Any other ideas would be appreciated.
Thanks, Dave
On Mon, 2004-07-12 at 16:01, YhLu wrote:
I mean if you build tg3?filo?ide_disk.zelf, it will confuse the Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a.
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks, Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that.
Thanks, Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error I'm using reiserfs, I'll try ext2. I'm really running out of ideas. Thanks, Dave On Mon, 2004-07-12 at 21:56, Takeshi Sone wrote:
Can you try out my FILO? (http://te.to/~ts1/filo/) If it works, it might help narrow the problem.
On Mon, Jul 12, 2004 at 05:14:39PM -0400, David Aubin wrote:
Here are the results:
I took my known working hard drive and stuck it in the device to test with filo. The results were the same! Meaning a known working kernel & intird on my hard drive failed at the initrd portion, again with the crc error.
I'm now going to try a basic etherboot test without filo to see if I can read off of the hard drive, just as a baseline.
Any other ideas would be appreciated.
Thanks, Dave
On Mon, 2004-07-12 at 16:01, YhLu wrote:
I mean if you build tg3?filo?ide_disk.zelf, it will confuse the Etherboot. So you can only build tg3?filo.zelf or tg3?ide_disk.zelf.
Do you have spare IDE disk? If So format the disk into ext3 or fat format and copy the .elf file into it.
Then connect that to your MB do test.
hda1:/ram0_......elf
Regards
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Monday, July 12, 2004 12:50 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
I am unable to get my kernel & initrd off of the usb stick. I was reading through the documents and came across this line in README.etherboot_in_filo: You can not use filo and ide_disk at the same time.
Can you tell me what this means? Do I need to rebuild filo without IDE support to get USB support?
Just to recap: My kernel & initrd fails as the initrd execution complaining of a bad CRC when I use the elf as a payload to load with with filo. I then try uda1:/kernel initrd=/boot/initrd root=/dev/sda1 and I get those td errors. I then tried your ramfs.elf and I get the same behavior are my elf image with the CRC complaining when the initrd portion is executed. Note, I have confirmed my elf works with etherboot, just not filo yet....
The CRC error makes me think that the image did not get loaded correctly by the elf boot. Can you confirm you used Eric's mkelfImage2-5? Here is my dump of the readelf -a.
ELF Header: Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00 Class: ELF32 Data: 2's complement, little endian Version: 1 (current) OS/ABI: UNIX - System V ABI Version: 0 Type: EXEC (Executable file) Machine: Intel 80386 Version: 0x1 Entry point address: 0x10000 Start of program headers: 52 (bytes into file) Start of section headers: 0 (bytes into file) Flags: 0x0 Size of this header: 52 (bytes) Size of program headers: 32 (bytes) Number of program headers: 5 Size of section headers: 0 (bytes) Number of section headers: 0 Section header string table index: 0
There are no sections in this file.
Program Headers: Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align NOTE 0x0000d4 0x00000000 0x00000000 0x00088 0x00088 RWE 0 LOAD 0x00015c 0x00010000 0x00010000 0x0559c 0x1aa24 RWE 0 LOAD 0x0056f8 0x00091000 0x00091000 0x00000 0x00070 RWE 0 LOAD 0x0056f8 0x00100000 0x00100000 0x1a952a 0x700000 RWE 0 LOAD 0x1aec22 0x00800000 0x00800000 0x2769f5 0x2769f5 RWE 0
There is no dynamic segment in this file.
There are no relocations in this file.
There are no unwind sections in this file.
No version information found in this file.
Thanks, Dave
On Fri, 2004-07-09 at 15:48, YhLu wrote:
I have got two cpus and four dimms for every CPU.
YH
______________________________________________________________________
From:David Aubin [mailto:daubin@actuality-systems.com] Sent: Friday, July 09, 2004 12:07 PM To: YhLu Cc: Hendricks David W.; ron minnich; LinuxBIOS Subject: RE: Filo Error Help
Hi,
Yes, I did, but I don't have a DHCP environment so it kept searching at the DHCP phase.
This problem is odd. I can boot my elf fine with etherboot, but not with filo. I can boot my kernel fine with filo, but not the initrd. I can even boot your kernel of the ram.elf you sent me, but when it hits the initrd it fails with the same error as mine.
I suspect either my filo is not configured like yours or that there is a problem loading a mulitpart elf (kernel & initrd in filo). I'm confused as to why filo didn't just use the etherboot portion of elf_load. It could be you were on the, "bleeding" edge? ;)
Can you tell me how much memory you have in your working system? I have just one cpu and 512meg memory. Curious if loading it high & it runs out of memory or something like that.
Thanks, Dave
On Fri, 2004-07-09 at 13:05, YhLu wrote:
Did you try the tg3--filo.zelf I sent to you?
YH
On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
I'm using reiserfs, I'll try ext2. I'm really running out of ideas.
For the initrd? I believe only ext2, minix, cramfs and perhaps one other filesystem is actually supported for initrd:s. //Peter
Hi, No no no, the disk. The initrd is ext2. Tried changing the disk to ext2 and still get the same results. This did work, but is not what I need. 1. Etherboot the filo.elf (4.2) as a payload 2. Run the filo.elf 3. It is able to load my kernel & initrd.elf, only off of the hd, not the usb stick. Arg! My setup uses etherboot as a primary to get the kernel & intird as an elf. But if that connection dies I want it to use the kernel & initrd elf on my usb stick. This first part works just fine. It is finding a way to get the second part that is taking me weeks! :( On Tue, 2004-07-13 at 11:48, Peter Stuge wrote:
On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
I'm using reiserfs, I'll try ext2. I'm really running out of ideas.
For the initrd? I believe only ext2, minix, cramfs and perhaps one other filesystem is actually supported for initrd:s.
//Peter _______________________________________________ Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios
On Tue, 13 Jul 2004, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
the few times I've seen the crc error is the initrd is configured too small. I still think you might have a config problem here. Put some debug prints in the initrd code and try to zoom in better to what's going on. ron
That's interesting. Too small? Uncompressed it is: ls -la : 8192000 2004-07-13 15:37 initrd I have my ram disk set to 65536. I made it bigger just to be sure. Are you saying the initrd and the ramdisk_size must be equal? If so then this would explain why Yhlu's and my elf's did not work. I'll try an exact ramdisk_size and initrd. Thanks, Dave On Tue, 2004-07-13 at 15:27, ron minnich wrote:
On Tue, 13 Jul 2004, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
the few times I've seen the crc error is the initrd is configured too small. I still think you might have a config problem here.
Put some debug prints in the initrd code and try to zoom in better to what's going on.
ron
On Tue, 13 Jul 2004, David Aubin wrote:
I have my ram disk set to 65536. I made it bigger just to be sure. Are you saying the initrd and the ramdisk_size must be equal?
no, now that I see what you're doing I'm lost as to the problem. When I've had this problem I just jam debug printks into the kernel and see why it's really failing. It always boils down to a failure to read or copy out the ramdisk image. ron
I now have a matching kernel ramdisk size of 8192k and initrd of the same size. It is failing the crc check in the kernel lib/inflate.c. I haven't probed further than that. Next step is to see what the kernel thinks the initrd is. Dave On Tue, 2004-07-13 at 15:27, ron minnich wrote:
On Tue, 13 Jul 2004, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
the few times I've seen the crc error is the initrd is configured too small. I still think you might have a config problem here.
Put some debug prints in the initrd code and try to zoom in better to what's going on.
ron
On Tue, Jul 13, 2004 at 11:35:01AM -0400, David Aubin wrote:
Thank yo for the image, but oddly it fails exactly the same way.... Found initrd block 0 crc error
Have you tried booting bzImage kernel with FILO? If it succeeds the culprit is my version of ELF boot code. Anyways I would like to see full DEBUG_ALL output of FILO. -- Takeshi
participants (5)
-
David Aubin -
Peter Stuge -
ron minnich -
Takeshi Sone -
YhLu