Re: Filo Error Help

2004-07-13 Thread David Aubin




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:[EMAIL PROTECTED] 
  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:   0x1
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   0xd4 0x 0x 0x00088 0x00088 RWE 0
LOAD   0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
LOAD   0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
LOAD   0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE
  0
LOAD   0x1aec22 0x0080 0x0080 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

Re: Filo Error Help

2004-07-13 Thread David Aubin
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:[EMAIL PROTECTED] 
   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:   0x1
 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   0xd4 0x 0x 0x00088 0x00088 RWE 0
 LOAD   0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
 LOAD   0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
 LOAD   0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE
   0
 LOAD   0x1aec22 0x0080 0x0080 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

Re: Filo Error Help

2004-07-13 Thread Peter Stuge
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
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


Re: Filo Error Help

2004-07-13 Thread David Aubin




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
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



attachment: smiley-6.png

RE: Filo Error Help

2004-07-13 Thread YhLu








Can
you get two cpus for the S2885? I would send my rom
image to you for test.



Regards



YH











From:
David Aubin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 13, 2004 9:09
AM
To: Peter Stuge
Cc: LinuxBIOS
Subject: Re: Filo Error Help





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 oneother filesystem is actually supported for initrd:s.//Peter___Linuxbios mailing list[EMAIL PROTECTED]http://www.clustermatic.org/mailman/listinfo/linuxbios




attachment: image001.gif

RE: Filo Error Help

2004-07-13 Thread David Aubin




Hello,

 With all due respect do you really think that an extra cpu would fix
this problem? I've looked at filo and to the best of my knowledge I
did not see any SMP related calls in there. I sincerely appreciate
your help, but I do not think this is the culprit.

Thanks,
Dave

On Tue, 2004-07-13 at 12:49, YhLu wrote:

Can you get two cpus for the S2885? I would send my rom image to you for test.



Regards



YH







From:David Aubin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 13, 2004 9:09 AM
To: Peter Stuge
Cc: LinuxBIOS
Subject: Re: Filo Error Help




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
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios



attachment: image001.gif

Re: Filo Error Help

2004-07-13 Thread ron minnich
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


___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-13 Thread YhLu








FILO
in TWO CPU version LinuxBIOS works well S2885
 in LANL and my lab.



So
I still suggest that you get another CPU to verify the whole process.



Regards



YH









From:
David Aubin [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, July 13, 2004 12:40
PM
To: ron minnich
Cc: Takeshi Sone; YhLu; Hendricks
David W.; LinuxBIOS
Subject: Re: Filo Error Help





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 errorthe 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






Re: Filo Error Help

2004-07-13 Thread ron minnich
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

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


Re: Filo Error Help

2004-07-13 Thread Takeshi Sone
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
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-12 Thread David Aubin




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: 0x1
 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 0xd4 0x 0x 0x00088 0x00088 RWE 0
 LOAD 0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
 LOAD 0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
 LOAD 0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE 0
 LOAD 0x1aec22 0x0080 0x0080 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:[EMAIL PROTECTED] 
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



attachment: image001.gif

RE: Filo Error Help

2004-07-12 Thread David Aubin




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 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:[EMAIL PROTECTED] 
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: 0x1
 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 0xd4 0x 0x 0x00088 0x00088 RWE 0
 LOAD 0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
 LOAD 0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
 LOAD 0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE 0
 LOAD 0x1aec22 0x0080 0x0080 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:[EMAIL PROTECTED] 
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



attachment: image001.gif

RE: Filo Error Help

2004-07-12 Thread YhLu








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:[EMAIL PROTECTED] 
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:
0x1
 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
0xd4 0x 0x 0x00088 0x00088 RWE 0
 LOAD 0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
 LOAD 0x0056f8 0x00091000 0x00091000 0x0
0x00070 RWE 0
 LOAD 0x0056f8 0x0010 0x0010 0x1a952a
0x70 RWE 0
 LOAD
0x1aec22 0x0080 0x0080 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:[EMAIL PROTECTED] 
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




attachment: image001.gif

RE: Filo Error Help

2004-07-12 Thread David Aubin




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 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:[EMAIL PROTECTED] 
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: 0x1
 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 0xd4 0x 0x 0x00088 0x00088 RWE 0
 LOAD 0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
 LOAD 0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
 LOAD 0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE 0
 LOAD 0x1aec22 0x0080 0x0080 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:[EMAIL PROTECTED] 
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



attachment: image001.gif

Re: Filo Error Help

2004-07-12 Thread Takeshi Sone
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:[EMAIL PROTECTED] 
  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:   0x1
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   0xd4 0x 0x 0x00088 0x00088 RWE 0
LOAD   0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
LOAD   0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
LOAD   0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE
  0
LOAD   0x1aec22 0x0080 0x0080 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

RE: Filo Error Help

2004-07-12 Thread YhLu
Good idea.

-Original Message-
From: Takeshi Sone [mailto:[EMAIL PROTECTED] 
Sent: Monday, July 12, 2004 6:56 PM
To: David Aubin
Cc: YhLu; Hendricks David W.; ron minnich; LinuxBIOS
Subject: Re: Filo Error Help

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:[EMAIL PROTECTED] 
  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:   0x1
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   0xd4 0x 0x 0x00088 0x00088 RWE 0
LOAD   0x00015c 0x0001 0x0001 0x0559c 0x1aa24 RWE 0
LOAD   0x0056f8 0x00091000 0x00091000 0x0 0x00070 RWE 0
LOAD   0x0056f8 0x0010 0x0010 0x1a952a 0x70 RWE
  0
LOAD   0x1aec22 0x0080 0x0080 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:[EMAIL PROTECTED] 
  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

RE: Filo Error Help

2004-07-09 Thread David Aubin
 sectors (522 MB)
  sda: assuming Write Enabled
  sda: assuming drive cache: write through
   sda: sda1
  Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
  NET: Registered protocol family 2
  IP: routing cache hash table of 2048 buckets, 32Kbytes
  TCP: Hash tables configured (established 65536 bind 65536)
  NET: Registered protocol family 1
  NET: Registered protocol family 17
  RAMDISK: Compressed image found at block 0
  RAMDISK: incomplete write (-28 != 1) 16777216
  crc error
  EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
  VFS: Mounted root (ext2 filesystem).
  Freeing unused kernel memory: 472k freed
  Kernel panic: No init found.  Try passing init= option to kernel.
  
  This makes me feel a little better as it appears it is something 
  in my etherboot-filo configuration perhaps?
  
  
  On Thu, 2004-07-08 at 17:53, YhLu wrote:
   I wonder if it is after gzip or before gzip.
   
   -Original Message-
   From: ron minnich [mailto:[EMAIL PROTECTED] 
   Sent: Thursday, July 08, 2004 2:44 PM
   To: David Aubin
   Cc: YhLu; LinuxBIOS
   Subject: RE: Filo Error Help
   
   On Thu, 8 Jul 2004, David Aubin wrote:
   
 If so could it be a size issue?  My initrd is 8Meg.  
   
   oh! 
   
   did you config the kernel for that? default is 4M.
   
   ron
  
  ___
  Linuxbios mailing list
  [EMAIL PROTECTED]
  http://www.clustermatic.org/mailman/listinfo/linuxbios
  
 

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-09 Thread David Aubin




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




attachment: smiley-4.png

RE: Filo Error Help

2004-07-09 Thread YhLu








I
have got two cpus and four dimms
for every CPU.



YH











From:
David Aubin [mailto:[EMAIL PROTECTED] 
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




attachment: image001.gif

Filo Error Help

2004-07-08 Thread David Aubin
Hello,

  I'm using Linux BIOS with etherboot-filo.  I have a usb stick has a 
kernel and a usb aware initrd on it.  The problem I am having is when
I use etherboot-filo to boot off of uba1:/boot/vmlinuz
initrd=/boot/initrd root=/dev/sda1
console=tty0 console=ttyS0,115200.  
I get this:
Mounted reiserfs
Found Linux version 2.6.6 ([EMAIL PROTECTED]) #3 SMP Thu Jul 8
09:25:46 EDT 2004 bzImage.
Loading kernel... ok
Loading initrd... dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046d9d
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046da1
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046da9
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046db1
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046db9
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046dc1
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sector=00046dc9
dma_to_td: can not find td
dma_to_td: can not find td
dma_to_td: can not find td
Disk read error dev_type=3 drive=0 sec



Ultimately I get this invalid image:

ide1 at 0x170-0x177,0x376 on irq 15
ide-floppy driver 0.99.newide
mice: PS/2 mouse device common for all mice
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: raid1 personality registered as nr 3
md: raid5 personality registered as nr 4
raid5: measuring checksumming speed
   generic_sse:  5996.000 MB/sec
raid5: using function: generic_sse (5996.000 MB/sec)
raid6: int64x1   1656 MB/s
raid6: int64x2   2390 MB/s
raid6: int64x4   2585 MB/s
raid6: int64x8   1750 MB/s
raid6: sse2x12351 MB/s
raid6: sse2x23367 MB/s
raid6: sse2x43578 MB/s
raid6: using algorithm sse2x4 (3578 MB/s)
md: raid6 personality registered as nr 8
md: multipath personality registered as nr 7
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
device-mapper: 4.1.0-ioctl (2003-12-10) initialised: [EMAIL PROTECTED]
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP: Hash tables configured (established 65536 bind 65536)
NET: Registered protocol family 1
Bluetooth: L2CAP ver 2.1
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.3
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM ver 1.2
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: BNEP (Ethernet Emulation) ver 1.0
Bluetooth: BNEP filters: protocol multicast
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
RAMDISK: Compressed image found at block 0
invalid compressed format (err=2)
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Insert root floppy and press ENTER


I've also placed an elf image of the kernel  intird, but it too failed,
but it seemed to fail in not even seeing the initrd bundled in the elf.
This same elf works fine in etherboot.  Any sugestions?

Thanks,
Dave


___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread YhLu
1. which MB? Which USB stick
2. please try .elf at first. It would be 
uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
format your usb disk with FAT or ext2, because it seems reiserfs
driver has some problem, and it will not work after abnormal shutdown.
3. I guess td is not be freed right after use.

Regards

YH
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread David Aubin




On Thu, 2004-07-08 at 17:11, YhLu wrote:

1. which MB? Which USB stick
2. please try .elf at first. It would be 
	uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
	format your usb disk with FAT or ext2, because it seems reiserfs
driver has some problem, and it will not work after abnormal shutdown.
3. I guess td is not be freed right after use.

Regards

YH


Hi,

1. I'm using a S2885 chipset motherboard by Tyan;) I'm using a Kingston 2.0 stick.
2. At the bottom of my original post I mention I did the elf as well. Did your elf include an initrd?
 If so could it be a size issue? My initrd is 8Meg. 
3. Can you point me as to how to remedy this?

Thanks,
Dave





RE: Filo Error Help

2004-07-08 Thread YhLu
How about the size of the elf?

YH

-Original Message-
From: David Aubin [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 08, 2004 2:27 PM
To: YhLu
Cc: LinuxBIOS
Subject: RE: Filo Error Help

Hi,

1.  I'm using a S2885 chipset motherboard by Tyan;)  I'm using a
Kingston 2.0 stick.
2.  At the bottom of my original post I mention I did the elf as well. 
Did your elf include an initrd?
 If so could it be a size issue?  My initrd is 8Meg.  
3.  Can you point me as to how to remedy this?

Thanks,

Dave

On Thu, 2004-07-08 at 17:25, David Aubin wrote:
 On Thu, 2004-07-08 at 17:11, YhLu wrote: 
  1. which MB? Which USB stick
  2. please try .elf at first. It would be 
  uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
  format your usb disk with FAT or ext2, because it seems reiserfs
  driver has some problem, and it will not work after abnormal shutdown.
  3. I guess td is not be freed right after use.
  
  Regards
  
  YH
 
 Hi,
 
 1.  I'm using a S2885 chipset motherboard by Tyan;)  I'm using a
 Kingston 2.0 stick.
 2.  At the bottom of my original post I mention I did the elf as
 well.  Did your elf include an initrd?
  If so could it be a size issue?  My initrd is 8Meg.  
 3.  Can you point me as to how to remedy this?
 
 Thanks,
 Dave
 
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread YhLu
I could send you my elf, but it is about 6Mb.

YH

-Original Message-
From: ron minnich [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 08, 2004 2:42 PM
To: David Aubin
Cc: YhLu; LinuxBIOS
Subject: Re: Filo Error Help

On Thu, 8 Jul 2004, David Aubin wrote:

 RAMDISK: Compressed image found at block 0

well if found the image ...
 invalid compressed format (err=2)

this is odd. you've got linux up, and it found an image, but it seems 
busted. Are you certain this initrd is ok? You could try booting the 
kernel and initrd on a known-good system to make sure the initrd is right. 

Do you have the right VFS for the initrd build into the kernel?

ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread David Aubin
The size of the elf is:
ls -la boot.elf
-r--r--r--1 daubin   users 4059015 2004-07-08 17:46 boot.elf

Dave

On Thu, 2004-07-08 at 17:38, YhLu wrote:
 How about the size of the elf?
 
 YH
 
 -Original Message-
 From: David Aubin [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, July 08, 2004 2:27 PM
 To: YhLu
 Cc: LinuxBIOS
 Subject: RE: Filo Error Help
 
 Hi,
 
 1.  I'm using a S2885 chipset motherboard by Tyan;)  I'm using a
 Kingston 2.0 stick.
 2.  At the bottom of my original post I mention I did the elf as well. 
 Did your elf include an initrd?
  If so could it be a size issue?  My initrd is 8Meg.  
 3.  Can you point me as to how to remedy this?
 
 Thanks,
 
 Dave
 
 On Thu, 2004-07-08 at 17:25, David Aubin wrote:
  On Thu, 2004-07-08 at 17:11, YhLu wrote: 
   1. which MB? Which USB stick
   2. please try .elf at first. It would be 
 uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
 format your usb disk with FAT or ext2, because it seems reiserfs
   driver has some problem, and it will not work after abnormal shutdown.
   3. I guess td is not be freed right after use.
   
   Regards
   
   YH
  
  Hi,
  
  1.  I'm using a S2885 chipset motherboard by Tyan;)  I'm using a
  Kingston 2.0 stick.
  2.  At the bottom of my original post I mention I did the elf as
  well.  Did your elf include an initrd?
   If so could it be a size issue?  My initrd is 8Meg.  
  3.  Can you point me as to how to remedy this?
  
  Thanks,
  Dave
  

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread YhLu
I wonder if it is after gzip or before gzip.

-Original Message-
From: ron minnich [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 08, 2004 2:44 PM
To: David Aubin
Cc: YhLu; LinuxBIOS
Subject: RE: Filo Error Help

On Thu, 8 Jul 2004, David Aubin wrote:

  If so could it be a size issue?  My initrd is 8Meg.  

oh! 

did you config the kernel for that? default is 4M.

ron
___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


Re: Filo Error Help

2004-07-08 Thread David Aubin
This exact same elf boots up fine with etherboot.
In fact I have etherboot-filo configured to boot off of the
net and it grabs this elf and boots the system well.
But when I use USB and this same elf, it gets a crc error
during the initrd portion.  It loads the kernel fine though.

Dave

On Thu, 2004-07-08 at 17:41, ron minnich wrote:
 On Thu, 8 Jul 2004, David Aubin wrote:
 
  RAMDISK: Compressed image found at block 0
 
 well if found the image ...
  invalid compressed format (err=2)
 
 this is odd. you've got linux up, and it found an image, but it seems 
 busted. Are you certain this initrd is ok? You could try booting the 
 kernel and initrd on a known-good system to make sure the initrd is right. 
 
 Do you have the right VFS for the initrd build into the kernel?
 
 ron
 

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread David Aubin




Your self consists of a kernel and initrd correct? Made with Eric's
mkelfImage2-5?

On Thu, 2004-07-08 at 17:49, YhLu wrote:

I could send you my elf, but it is about 6Mb.

YH

-Original Message-
From: ron minnich [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 08, 2004 2:42 PM
To: David Aubin
Cc: YhLu; LinuxBIOS
Subject: Re: Filo Error Help

On Thu, 8 Jul 2004, David Aubin wrote:

 RAMDISK: Compressed image found at block 0

well if found the image ...
 invalid compressed format (err=2)

this is odd. you've got linux up, and it found an image, but it seems 
busted. Are you certain this initrd is ok? You could try booting the 
kernel and initrd on a known-good system to make sure the initrd is right. 

Do you have the right VFS for the initrd build into the kernel?

ron





RE: Filo Error Help

2004-07-08 Thread David Aubin
Hi,

  With your elf I get the following:
boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
LinuxLabs USB bootloader
New USB device, setting address 2
0008:0006:0050
Manufacturor: Kingston
Product: DataTraveler2.0
Serial: 07B1F140E000617B
Found USB block device 2
Mounted reiserfs
errnum=15
boot: uda1:/ram.elf
Loading Linux version 2.6.5 ([EMAIL PROTECTED]) #11 SMP Mon May 10
14:58:17 PDT 2004...
Jumping to entry point...
DFA Just before C's xstart32
Firmware type: LinuxBIOS
old bootloader convention, maybe loadlin?
Bootdata ok (command line is root=/dev/ram0 rw console=tty0
console=ttyS0,115200n8)
.
.
RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
loop: loaded (max 8 devices)
.
.
usb 2-3: new full speed USB device using address 2
scsi4 : SCSI emulation for USB Mass Storage devices
  Vendor: Kingston  Model: DataTraveler2.0   Rev: 4.70
  Type:   Direct-Access  ANSI SCSI revision: 02
SCSI device sda: 1019392 512-byte hdwr sectors (522 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 sda: sda1
Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
NET: Registered protocol family 2
IP: routing cache hash table of 2048 buckets, 32Kbytes
TCP: Hash tables configured (established 65536 bind 65536)
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: Compressed image found at block 0
RAMDISK: incomplete write (-28 != 1) 16777216
crc error
EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
VFS: Mounted root (ext2 filesystem).
Freeing unused kernel memory: 472k freed
Kernel panic: No init found.  Try passing init= option to kernel.

This makes me feel a little better as it appears it is something 
in my etherboot-filo configuration perhaps?


On Thu, 2004-07-08 at 17:53, YhLu wrote:
 I wonder if it is after gzip or before gzip.
 
 -Original Message-
 From: ron minnich [mailto:[EMAIL PROTECTED] 
 Sent: Thursday, July 08, 2004 2:44 PM
 To: David Aubin
 Cc: YhLu; LinuxBIOS
 Subject: RE: Filo Error Help
 
 On Thu, 8 Jul 2004, David Aubin wrote:
 
   If so could it be a size issue?  My initrd is 8Meg.  
 
 oh! 
 
 did you config the kernel for that? default is 4M.
 
 ron

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios


RE: Filo Error Help

2004-07-08 Thread Hendricks David W.
Looks more like a Linux config problem. Double check your /etc/fstab and 
make sure the root partition entry is correct and that you have virtual 
terminal (VT) support enabled in your kernel.

On Thu, 8 Jul 2004, David Aubin wrote:

 Hi,
 
   With your elf I get the following:
 boot: uda1:/ram0_2.5_2.6.5_k8.2_mydisk7.elf
 LinuxLabs USB bootloader
 New USB device, setting address 2
 0008:0006:0050
 Manufacturor: Kingston
 Product: DataTraveler2.0
 Serial: 07B1F140E000617B
 Found USB block device 2
 Mounted reiserfs
 errnum=15
 boot: uda1:/ram.elf
 Loading Linux version 2.6.5 ([EMAIL PROTECTED]) #11 SMP Mon May 10
 14:58:17 PDT 2004...
 Jumping to entry point...
 DFA Just before C's xstart32
 Firmware type: LinuxBIOS
 old bootloader convention, maybe loadlin?
 Bootdata ok (command line is root=/dev/ram0 rw console=tty0
 console=ttyS0,115200n8)
 .
 .
 RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
 loop: loaded (max 8 devices)
 .
 .
 usb 2-3: new full speed USB device using address 2
 scsi4 : SCSI emulation for USB Mass Storage devices
   Vendor: Kingston  Model: DataTraveler2.0   Rev: 4.70
   Type:   Direct-Access  ANSI SCSI revision: 02
 SCSI device sda: 1019392 512-byte hdwr sectors (522 MB)
 sda: assuming Write Enabled
 sda: assuming drive cache: write through
  sda: sda1
 Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0
 NET: Registered protocol family 2
 IP: routing cache hash table of 2048 buckets, 32Kbytes
 TCP: Hash tables configured (established 65536 bind 65536)
 NET: Registered protocol family 1
 NET: Registered protocol family 17
 RAMDISK: Compressed image found at block 0
 RAMDISK: incomplete write (-28 != 1) 16777216
 crc error
 EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended
 VFS: Mounted root (ext2 filesystem).
 Freeing unused kernel memory: 472k freed
 Kernel panic: No init found.  Try passing init= option to kernel.
 
 This makes me feel a little better as it appears it is something 
 in my etherboot-filo configuration perhaps?
 
 
 On Thu, 2004-07-08 at 17:53, YhLu wrote:
  I wonder if it is after gzip or before gzip.
  
  -Original Message-
  From: ron minnich [mailto:[EMAIL PROTECTED] 
  Sent: Thursday, July 08, 2004 2:44 PM
  To: David Aubin
  Cc: YhLu; LinuxBIOS
  Subject: RE: Filo Error Help
  
  On Thu, 8 Jul 2004, David Aubin wrote:
  
If so could it be a size issue?  My initrd is 8Meg.  
  
  oh! 
  
  did you config the kernel for that? default is 4M.
  
  ron
 
 ___
 Linuxbios mailing list
 [EMAIL PROTECTED]
 http://www.clustermatic.org/mailman/listinfo/linuxbios
 

___
Linuxbios mailing list
[EMAIL PROTECTED]
http://www.clustermatic.org/mailman/listinfo/linuxbios