etherboot-users — Discussion of user issues

[Etherboot-users] pxe boot ?

[Roy W. <roy...@ya...>]

Hi, i'm new to this list after hunting the internet
for months and trying to get something working with
BootP / PXE that is very frustrating. I'm hoping
someone can help me here ?

I have a Fujitsu Stylistic LT tablet PC. these are old
tablet's, not new WinXP tablet edition stuff, just a
Pentium 233, with 64 MB of RAM and a 4 GB drive, but
they are great little units. I have no operating
system on one, and no floppy drive (none built in),
and cannot buy a floppy disc as these are unsupported,
but they *DO* have PXE boot as an option in the BIOS.

So, I have turned on PXE boot, and a DHCP TFTP server
on my main system using tftpd32 which works perfectly.
My Fujitsu is correctly picking up an IP address which
is great. However, on trying to send a package over, I
got constant errors saying "to many packages", with an
error code that I looked up on google that indicated
that PXE will not accept boot images larger than 512KB
! this is an old machine with no possibility of
getting the PXE upgraded to allow larger images. So i
took a 500KB file and pointed that at the machine, and
indeed the error was no longer there. So, now it seems
that I need either a DOS or Linux boot disc that can
boot the system over PXE, but it must be less than
512KB in size ! this is the really tough bit, as I
cannot make a DOS boot disk image smaller than ~650KB
and I'm a bit clueless about making Linux boot discs
...

Please help, as this would help in so many ways,
having a simple system to boot any system on my
network to a command prompt without a floppy or cd
boot can be used for so many useful tasks. I've
actually been trying to get this stuff working on and
off for about 2 years now, and I've never got anywhere
with it. PXE seems to be a real "black art" and useful
information on the internet on this has been very
difficult to find ... so I'm very much hoping that
someone on this list can help me with this.

Thanks / Best Regards,

Roy.


		
___________________________________________________________ 
How much free photo storage do you get? Store your holiday 
snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

Re: [Etherboot-users] [PATCH] ISC dhcpd siaddr (next-server) zero default change in 3.0.2

[Marty C. <md...@et...>]

On Sep 14, 2005, at 8:36 AM, Harald Welte wrote:
> Hi!
> I spent the last three hours debugging a problem where suddenly a  
> number
> of my diskless embedded systems refused to boot.  Those systems are
> based on etherboot (http://www.etherboot.org/).
> After adding tons of debug statements to the etherboot code, I  
> found out
> that

Herald,

Many thanks for your debugging.  We were recently made aware of the  
problem:

     http://sourceforge.net/mailarchive/forum.php? 
thread_id=8122799&forum_id=6401

It certainly is something we need to address.

> 1) Etherboot DHCP client code ignores a DHCPOFFER with "siaddr"  
> 0.0.0.0
> 2) dhcp-3.0.2 suddenly changed the default from the dhcp server  
> address
>    to 0.0.0.0.  This is mentioned in the changelog, but is  
> contradicted
>    by the dhcpd.conf.5 manpage (which still states that the DHCP  
> server
>    address is used as default).
> I don't really understand the reasoning of the change in  
> dhcp-3.0.2.  I
> think it will cause many similar setups to break, and if admins look
> into the dhcpd.conf.5, they verify that their setup is correct  
> according
> to the documentation - but it ceases to work after a isc dhcp upgrade.
> Please find the patch below for dhcpd.conf.5

Perhaps someone on the dhc...@is... list will have something  
to say about the reasoning behind this.  If I was to venture a guess,  
I would guess that it has something to do with interoperability with  
other DHCP server implementations.

> If you still want to continue the semantic change of the default  
> value,
> I strongly suggest to print a warning or even make server startup  
> fail,
> if
> A) any netbooting related directive (root-path, filename, ...) is used
>     _AND_
> B) no "next-server" directive is present in the configuration.
> This way the admin at least knows that something is wrong and has  
> to be
> changed.

Documentation is often the hardest thing to keep up to date.  It's  
good you mentioned this.

> For the etherboot folks: I've attached a suggested patch that prints a
> message if a zero siaddr dhcpoffer is ignored.  The current silent
> failiure makes debugging hard.

The Etherboot patch looks fine at first glance.  I think the wording  
should be a little more general, something like:

+        printf("Ignoring DHCP offer without valid 'siaddr' field,\n "
+               "DHCP config may require explicit 'next-server'  
declaration.\n");

instead of:

+        printf("ignoring DHCP offer without valid 'siaddr' field, on "
+               "ISC dhcpd >= 3.0.2 use 'next-server' configuration\n");

This would make the condition more general, in case other servers do  
this as well.


> Thanks for your consideration,
> -- 
> - Harald Welte <la...@gn...>                      http:// 
> gnumonks.org/
> <dhcpd-3.0.3-manpage-siaddr.patch>
> <etherboot-5.4.1-dhcp-zero-siaddr-warning.patch>

Thank you for your debugging and patch.

Let's see what other folks think.

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] [PATCH] ISC dhcpd siaddr (next-server) zero default change in 3.0.2

[Harald W. <la...@gn...>]

Hi!

I spent the last three hours debugging a problem where suddenly a number
of my diskless embedded systems refused to boot.  Those systems are
based on etherboot (http://www.etherboot.org/).

After adding tons of debug statements to the etherboot code, I found out
that 

1) Etherboot DHCP client code ignores a DHCPOFFER with "siaddr" 0.0.0.0
2) dhcp-3.0.2 suddenly changed the default from the dhcp server address
   to 0.0.0.0.  This is mentioned in the changelog, but is contradicted
   by the dhcpd.conf.5 manpage (which still states that the DHCP server
   address is used as default).

I don't really understand the reasoning of the change in dhcp-3.0.2.  I
think it will cause many similar setups to break, and if admins look
into the dhcpd.conf.5, they verify that their setup is correct according
to the documentation - but it ceases to work after a isc dhcp upgrade.

Please find the patch below for dhcpd.conf.5

If you still want to continue the semantic change of the default value,
I strongly suggest to print a warning or even make server startup fail,
if 

A) any netbooting related directive (root-path, filename, ...) is used 
	_AND_
B) no "next-server" directive is present in the configuration.

This way the admin at least knows that something is wrong and has to be
changed.

For the etherboot folks: I've attached a suggested patch that prints a
message if a zero siaddr dhcpoffer is ignored.  The current silent
failiure makes debugging hard.

Thanks for your consideration,

-- 
- Harald Welte <la...@gn...>          	        http://gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
                                                  (ETSI EN 300 175-7 Ch. A6)

Re: [Etherboot-users] Tftpserver override

[Anselm M. H. <an...@ho...>]

Am Montag, den 12.09.2005, 14:34 -0500 schrieb Simon White:
> Hi,
> 
> After looking through the docs I'm guessing the answer is no, but is there anyway to override or provide the tftpserver address by hardcoding it localally (e.g. in the output image).  For various reasons I cannot get the main dhcp sever config changed and would not be allowed to setup a secondary.  Of course I could attempt such a thing without knowledge higher up but should any problems occur there would not go down at all well.
> 
> If not a convienient way to override would a possible simple code change do the trick, any hints possible?

May I assume you have control over the "filename" in DHCP config? In
that case, you could use something like
	tftp://10.0.0.1//kernel.nbi
as filename, which should be parsed by etherboot to be a "hidden"
next-server statement.

If you do not even have control over the filename that goes through the
wire: Do they send one at all? If not, the DEFAULT_FILENAME (option name
may be a bit different - don't remember) might be your friend.

BR
Anselm

[Etherboot-users] Tftpserver override

[Simon W. <s_a...@em...>]

Hi,

After looking through the docs I'm guessing the answer is no, but is there =
anyway to override or provide the tftpserver address by hardcoding it local=
ally (e.g. in the output image).  For various reasons I cannot get the main=
 dhcp sever config changed and would not be allowed to setup a secondary.  =
Of course I could attempt such a thing without knowledge higher up but shou=
ld any problems occur there would not go down at all well.

If not a convienient way to override would a possible simple code change do=
 the trick, any hints possible?

Thanks in advance,
Simon


--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

Re: [Etherboot-users] 3c905b bug fix compile error

[Marty C. <md...@et...>]

On Sep 9, 2005, at 1:11 PM, le...@mi... wrote:
> Marty,
>      The patch code worked however I had a problem doing the patch - 
> p0 command.
> I looked at the patch file and patched by hand and it worked.  The  
> error I was
> getting was the following.
> --------
> patching file 3c90x.c
> patch: **** malformed patch at line 7: /***  
> a3c90x_internal_WriteEepromWord -
> write a physical word of
> --------
> It doesn't seem to like your comment.

I should have attached the patch as a text file.  My mail program  
badly mangled it when I pasted it in.  Sorry about that!

If anybody with developer cvs access wants to apply the patch to 5.4  
cvs, please go ahead, and update the LOG.  Thanks.

It's nice to hear that the patch worked.  Have you actually able to  
flash some chips on the card?  I assume you are using bromutil to do  
your flashing, and knowing that it is still working would be nice.   
Make sure you stop the ethernet card with something like:

     /sbin/ifconfig eth1 down

before you flash it, even if it's not being used for network traffic,  
else you may have problems flashing.

Another way to go is with Don Becker's diagnostic programs, available  
at:

     http://www.scyld.com/ethercard_diag.html#pci-diags

Specifically:

     ftp://ftp.scyld.com/pub/diag/vortex-diag.c

You would need to compile with the -DLIBFLASH flag and linked against:

     ftp://scyld.com/pub/diag/libflash.c

Don's diag programs are very full-featured, and probably overkill for  
your purpose, but they're very informative, and if you have the time  
and inclination, they're fun to play with.

We'd enjoy hearing how things go for you, and any notes or comments  
you'd like to share about your project.  (if you'd like to jot down a  
quick HOWTO (nothing fancy, just a list of steps), please do).

> Thanks for the Help

Thank you for using Etherboot, and for helping us make it better!

> -Lee

Marty

>
> On Sep 8, 2005, at 11:07 PM, lee@mi... wrote:
>
>> Hello,
>>      I have been reading the mail archive and see there is the bug
>> with the
>> 3c90x cards so I am trying to compile the etherboot bug fix option
>> -DCFG_3C90X_BOOTROM_FIX.
>>
>
>  Hello, and thanks very much for your message.
>
>
>>   I am guessing you put it in the Makefile.main towards
>> the bottom like this but not sure
>> 3C90XFLAGS=     -DINCLUDE_3C90X -DCFG_3C90X_BOOTROM_FIX
>>
>
>  This should work fine.  You could also do:
>
>       CFLAGS+=    -DCFG_3C90X_BOOTROM_FIX
>
>  in src/Config  which might be easier to find and comment out after
>  you've
>  made your floppy.  Either way is fine.
>
>
>> Anyways, If this is correct, when I go to compile I get the
>> following error
>>     # make bin/3c90x.zfd0
>>     ld  -N -T arch/i386/core/etherboot.lds -o bin/3c90x.dsk.rt bin/
>> 3c90x.rt.o
>>     bin/floppyprefix.exit.o
>>     bin/3c90x.rt.o(.text+0x1803): In function `a3c90x_probe':
>>     : undefined reference to `a3c90x_internal_WriteEeprom'
>>     make: *** [bin/3c90x.dsk.rt] Error 1
>>
>
>  This looks like a bug in 3c90x.c.  Here is a patch:
>
>  ===== patch begins at next line=====
>  --- 3c90x.c.orig        2005-09-09 06:53:10.000000000 -0400
>  +++ 3c90x.c     2005-09-09 07:04:17.000000000 -0400
>  @@ -319,7 +319,7 @@
>        }
>  -#if 0
>  +#ifdef CFG_3C90X_BOOTROM_FIX | CFG_3C90X_XCVR
>  /*** a3c90x_internal_WriteEepromWord - write a physical word of
>     *** data to the onboard serial eeprom (not the BIOS prom, but the
>     *** nvram in the card that stores, among other things, the MAC
>  @@ -353,9 +353,7 @@
>        return 0;
>        }
>  -#endif
>  -#if 0
>  /*** a3c90x_internal_WriteEeprom - write data to the serial eeprom,
>     *** and re-compute the eeprom checksum.
>     ***/
>  ===== patch ends with previous line =====
>
>  Part of the code that the BOOTROM_FIX code needed was conditionalized
>  out.  I just made sure that the code was turned on if either of two
>  compile-time options was defined, since they both need it.
>
>  If you copy this patch into a file, say, ~/bootrom-patch.txt", and go
>  to the
>  etherboot-5.4.1/src/drivers/net directory, and do:
>
>       $ patch -p0 < ~/bootrom-patch.txt
>
>  it should apply the patch, and you can then do:
>
>       $ make bin/3c90x.zdsk
>
>  And you should get the floppy you need to fix configure the ROM
>  socket on your 3C905B with the BootROM socket bug.
>
>  Then it's a simple matter of:
>
>       $ cat bin/3c90x.zdsk > /dev/fd0
>
>  and boot once with the floppy (and no EEPROM in the socket!).  Then
>  take out the floppy, put in an EEPROM, and have at it.
>
>
>> I am using etherboot 5.4.1 any help would be great for I am trying
>> to make my
>> own boot rom chips for I have a programmer but so far the cards are
>> not seeing
>> the chips I make at all.  I am hoping this bug fix will fix the
>> problem
>> thanks
>> -Lee
>>
>
>  I should also mention that the good folks of LTSP released a pre-
>  built floppy image (from an older version of Etherboot) that
>  configures 3C905-B ROM sockets.  It is available here:
>
>       http://sourceforge.net/project/showfiles.php?
>  group_id=17723&package_id=13619&release_id=32370
>
>  It should also reconfigure the card.
>
>  I do appreciate your bug report, and would also appreciate it if you
>  would be so kind as to test the patch I provided above.  If it works,
>  we'll apply it to CVS so the fix will be carried forward.
>
>  Thanks again for your help.  Please let us know how things go...
>
>  Marty
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle  
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams *  
> Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/ 
> bsce5sf
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>

[Etherboot-users] 3c905b bug fix compile error

[<le...@mi...>]

Marty,
     The patch code worked however I had a problem doing the patch -p0 command. 
I looked at the patch file and patched by hand and it worked.  The error I was
getting was the following.

--------
patching file 3c90x.c
patch: **** malformed patch at line 7: /*** a3c90x_internal_WriteEepromWord -
write a physical word of
--------
It doesn't seem to like your comment.


Thanks for the Help

-Lee


On Sep 8, 2005, at 11:07 PM, lee@mi... wrote:
 > Hello,
 >      I have been reading the mail archive and see there is the bug  
 > with the
 > 3c90x cards so I am trying to compile the etherboot bug fix option
 > -DCFG_3C90X_BOOTROM_FIX.
 
 Hello, and thanks very much for your message.
 
 >   I am guessing you put it in the Makefile.main towards
 > the bottom like this but not sure
 > 3C90XFLAGS=     -DINCLUDE_3C90X -DCFG_3C90X_BOOTROM_FIX
 
 This should work fine.  You could also do:
 
      CFLAGS+=    -DCFG_3C90X_BOOTROM_FIX
 
 in src/Config  which might be easier to find and comment out after  
 you've
 made your floppy.  Either way is fine.
 
 > Anyways, If this is correct, when I go to compile I get the  
 > following error
 >     # make bin/3c90x.zfd0
 >     ld  -N -T arch/i386/core/etherboot.lds -o bin/3c90x.dsk.rt bin/ 
 > 3c90x.rt.o
 >     bin/floppyprefix.exit.o
 >     bin/3c90x.rt.o(.text+0x1803): In function `a3c90x_probe':
 >     : undefined reference to `a3c90x_internal_WriteEeprom'
 >     make: *** [bin/3c90x.dsk.rt] Error 1
 
 This looks like a bug in 3c90x.c.  Here is a patch:
 
 ===== patch begins at next line=====
 --- 3c90x.c.orig        2005-09-09 06:53:10.000000000 -0400
 +++ 3c90x.c     2005-09-09 07:04:17.000000000 -0400
 @@ -319,7 +319,7 @@
       }
 -#if 0
 +#ifdef CFG_3C90X_BOOTROM_FIX | CFG_3C90X_XCVR
 /*** a3c90x_internal_WriteEepromWord - write a physical word of
    *** data to the onboard serial eeprom (not the BIOS prom, but the
    *** nvram in the card that stores, among other things, the MAC
 @@ -353,9 +353,7 @@
       return 0;
       }
 -#endif
 -#if 0
 /*** a3c90x_internal_WriteEeprom - write data to the serial eeprom,
    *** and re-compute the eeprom checksum.
    ***/
 ===== patch ends with previous line =====
 
 Part of the code that the BOOTROM_FIX code needed was conditionalized  
 out.  I just made sure that the code was turned on if either of two  
 compile-time options was defined, since they both need it.
 
 If you copy this patch into a file, say, ~/bootrom-patch.txt", and go  
 to the
 etherboot-5.4.1/src/drivers/net directory, and do:
 
      $ patch -p0 < ~/bootrom-patch.txt
 
 it should apply the patch, and you can then do:
 
      $ make bin/3c90x.zdsk
 
 And you should get the floppy you need to fix configure the ROM  
 socket on your 3C905B with the BootROM socket bug.
 
 Then it's a simple matter of:
 
      $ cat bin/3c90x.zdsk > /dev/fd0
 
 and boot once with the floppy (and no EEPROM in the socket!).  Then  
 take out the floppy, put in an EEPROM, and have at it.
 
 > I am using etherboot 5.4.1 any help would be great for I am trying  
 > to make my
 > own boot rom chips for I have a programmer but so far the cards are  
 > not seeing
 > the chips I make at all.  I am hoping this bug fix will fix the  
 > problem
 > thanks
 > -Lee
 
 I should also mention that the good folks of LTSP released a pre- 
 built floppy image (from an older version of Etherboot) that  
 configures 3C905-B ROM sockets.  It is available here:
 
      http://sourceforge.net/project/showfiles.php? 
 group_id=17723&package_id=13619&release_id=32370
 
 It should also reconfigure the card.
 
 I do appreciate your bug report, and would also appreciate it if you  
 would be so kind as to test the patch I provided above.  If it works,  
 we'll apply it to CVS so the fix will be carried forward.
 
 Thanks again for your help.  Please let us know how things go...
 
 Marty
 

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Re: [Etherboot-users] 3c905b bug fix compile error

[Marty C. <md...@et...>]

On Sep 8, 2005, at 11:07 PM, le...@mi... wrote:
> Hello,
>      I have been reading the mail archive and see there is the bug  
> with the
> 3c90x cards so I am trying to compile the etherboot bug fix option
> -DCFG_3C90X_BOOTROM_FIX.

Hello, and thanks very much for your message.

>   I am guessing you put it in the Makefile.main towards
> the bottom like this but not sure
> 3C90XFLAGS=     -DINCLUDE_3C90X -DCFG_3C90X_BOOTROM_FIX

This should work fine.  You could also do:

     CFLAGS+=    -DCFG_3C90X_BOOTROM_FIX

in src/Config  which might be easier to find and comment out after  
you've
made your floppy.  Either way is fine.

> Anyways, If this is correct, when I go to compile I get the  
> following error
>     # make bin/3c90x.zfd0
>     ld  -N -T arch/i386/core/etherboot.lds -o bin/3c90x.dsk.rt bin/ 
> 3c90x.rt.o
>     bin/floppyprefix.exit.o
>     bin/3c90x.rt.o(.text+0x1803): In function `a3c90x_probe':
>     : undefined reference to `a3c90x_internal_WriteEeprom'
>     make: *** [bin/3c90x.dsk.rt] Error 1

This looks like a bug in 3c90x.c.  Here is a patch:

===== patch begins at next line=====
--- 3c90x.c.orig        2005-09-09 06:53:10.000000000 -0400
+++ 3c90x.c     2005-09-09 07:04:17.000000000 -0400
@@ -319,7 +319,7 @@
      }
-#if 0
+#ifdef CFG_3C90X_BOOTROM_FIX | CFG_3C90X_XCVR
/*** a3c90x_internal_WriteEepromWord - write a physical word of
   *** data to the onboard serial eeprom (not the BIOS prom, but the
   *** nvram in the card that stores, among other things, the MAC
@@ -353,9 +353,7 @@
      return 0;
      }
-#endif
-#if 0
/*** a3c90x_internal_WriteEeprom - write data to the serial eeprom,
   *** and re-compute the eeprom checksum.
   ***/
===== patch ends with previous line =====

Part of the code that the BOOTROM_FIX code needed was conditionalized  
out.  I just made sure that the code was turned on if either of two  
compile-time options was defined, since they both need it.

If you copy this patch into a file, say, ~/bootrom-patch.txt", and go  
to the
etherboot-5.4.1/src/drivers/net directory, and do:

     $ patch -p0 < ~/bootrom-patch.txt

it should apply the patch, and you can then do:

     $ make bin/3c90x.zdsk

And you should get the floppy you need to fix configure the ROM  
socket on your 3C905B with the BootROM socket bug.

Then it's a simple matter of:

     $ cat bin/3c90x.zdsk > /dev/fd0

and boot once with the floppy (and no EEPROM in the socket!).  Then  
take out the floppy, put in an EEPROM, and have at it.

> I am using etherboot 5.4.1 any help would be great for I am trying  
> to make my
> own boot rom chips for I have a programmer but so far the cards are  
> not seeing
> the chips I make at all.  I am hoping this bug fix will fix the  
> problem
> thanks
> -Lee

I should also mention that the good folks of LTSP released a pre- 
built floppy image (from an older version of Etherboot) that  
configures 3C905-B ROM sockets.  It is available here:

     http://sourceforge.net/project/showfiles.php? 
group_id=17723&package_id=13619&release_id=32370

It should also reconfigure the card.

I do appreciate your bug report, and would also appreciate it if you  
would be so kind as to test the patch I provided above.  If it works,  
we'll apply it to CVS so the fix will be carried forward.

Thanks again for your help.  Please let us know how things go...

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] 3c905b bug fix compile error

[<le...@mi...>]

Hello,
     I have been reading the mail archive and see there is the bug with the
3c90x cards so I am trying to compile the etherboot bug fix option
-DCFG_3C90X_BOOTROM_FIX.  I am guessing you put it in the Makefile.main towards
the bottom like this but not sure

3C90XFLAGS=     -DINCLUDE_3C90X -DCFG_3C90X_BOOTROM_FIX


Anyways, If this is correct, when I go to compile I get the following error


#make bin/3c90x.zfd0

--- snip -----

objcopy -R .text16 bin/floppyprefix.o bin/floppyprefix.entry.o
objcopy -R .prefix bin/floppyprefix.o bin/floppyprefix.exit.o
ld  -N -T arch/i386/core/etherboot.lds -o bin/3c90x.dsk.rt bin/3c90x.rt.o
bin/floppyprefix.exit.o
bin/3c90x.rt.o(.text+0x1803): In function `a3c90x_probe':
: undefined reference to `a3c90x_internal_WriteEeprom'
make: *** [bin/3c90x.dsk.rt] Error 1
rm bin/floppyprefix.exit.o bin/3c90x.rt.o bin/floppyprefix.entry.o

---  end snip ----

I am using etherboot 5.4.1 any help would be great for I am trying to make my
own boot rom chips for I have a programmer but so far the cards are not seeing
the chips I make at all.  I am hoping this bug fix will fix the problem

thanks

-Lee



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Etherboot-users] Etherboot 5.4.1 (production) released

[Marty C. <md...@et...>]

I have released Etherboot 5.4.1 at:

     http://www.etherboot.org/

The release notes are at:

     http://sourceforge.net/project/shownotes.php?release_id=355101

The ChangeLOG is at:

     http://www.etherboot.org/LOG

MD5 sums:

     9d8666f32ca259a045130487e382f88b  etherboot-5.4.1.tar.bz2
     b31b418b88086f69ddc4c886a08c8cfd  etherboot-5.4.1.tar.gz

Notes:

This production release of Etherboot adds a few features, and support
for several new NICs and variations.  Many thanks to all of the  
contributors who
made these improvements possible.

As always, we ask people to test this release.  Especially those who  
sent in
bug reports on 5.4.0.  Hopefully we have fixed most of the problems,  
and added
features and support that will be helpful to you.

I have simultaneously updated http://rom-o-matic.net/ with 5.4.1 to  
make it
easy to try out the latest release.

Please post questions, problems, general comments to the Etherboot- 
Users list,
or to the Etherboot-Developers list, if it seems technically  
appropriate.

It is a great pleasure to serve the FOSS community.

Thanks for all your help and support!

Marty

Partial ChangeLog:
======================================================================== 
======

Changes since 5.4.0:

+ Added PCI ID for Fujistu Siemens Futro C200 by Martin Vogt

+ Liu Tao contributed a driver for the AMD8111 based on the Linux
   driver

+ Till Straumann patch for Sporadic eepro(10)  RX problems after reboot

+ Hermann Gausterer sent a patch to support additional Broadcom PHYs

+ Timothy Legge updated the forcedeth driver to the latest Linux version
   2.6.10 (untested and broken)

+ YhLu fixed the updated forcedeth driver so that it worked and  
confirmed
   that it supports the Gigabit nVidia NICs

+ Timothy Legge fixed relocation issues with the eepro driver

+ Jan Kiszka provided a patch for the smc9000 for missing phy-setup

+ Timothy Legge fixed TX Underrun on centaur-p models of tulip that
   caused the card to stall

+ Krzysztof Lichota provided a patch to pcnet32 that fixed a long  
standing
   issue on certain models of HP Vectra

+ Jorge L. deLyra contributed an improved version of contrib/ 
3c90xutil/cromutil.c
   which enables programming of flash chips on various 3COM 3C905 cards.

+ Marcel Ritter contributed a patch to r8169.c to recognize USR and D- 
Link
   cards that use rtl8169 chips

+ Per Dalgas Jakobsen contributed a patch to allow booting directly from
   a hard disk partition

+ Patrik Reali contributed a network driver patch to 3c90x.c to  
enable support
   for 3C556 "hurricane" cards

======================================================================== 
======

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] ISC dhcpd v3.0.3

[Anselm M. H. <an...@ho...>]

Hello *,

several LTSP users reported problems after an upgrade in ISC dhcpd, from
version 3.0.1 or 3.0.2 to the most recent 3.0.3.

Phil Davey found out that dhcpd behaviour regarding the "next-server"
entry changed. In older versions, if this parameter had not been set at
all, it defaulted to the IP address of the DHCP server. Most etherboot
users probably expected this behaviour... anyway, after an upgrade, you
will have to specify "next-server" in your dhcpd.conf.

Hopefully this saves some people a headache.

Regards,
Anselm

Re: [Etherboot-users] rom-o-matic and a fs

[Alexander H. <mai...@gm...>]

> What are the chances of using mkfs.vfat and a rom-o-matic file to create 
> a floppy that will pxe boot and have a fs to store some files?

I have created such a floppy. It is based on Etherboot 5.4.0.
All you need to do to upgrade to a new Etherboot version, is copying the 
corresponding file to the floppy.

See http://etherboot.anadex.de for details

Cheers
Alex

Re: [Etherboot-users] rom-o-matic and a fs

[Marty C. <md...@et...>]

On Sep 1, 2005, at 10:11 AM, Carl Karsten wrote:
> What are the chances of using mkfs.vfat and a rom-o-matic file to  
> create a floppy that will pxe boot and have a fs to store some files?
> ^Carl Karsten

SYSLINUX sounds like what you may want:

Check out:

     http://syslinux.zytor.com/faq.php

You should be able to create a DOS format floppy, make it bootable  
with SYSLINUX, and have it load a .zlilo version of Etherboot you got  
rom-o-matic.net for your card.

As a matter of fact, if you were to get a .iso image from rom-o- 
matic.net, and take a looks inside, you'd see something like:

     $ sudo mount -o loop eb-5.4.0-3c90x.iso /mnt
     $ cd /mnt
     $ ls -l
     total 38
     -r-xr-xr-x    1 root     root        25986 Sep  1 13:27 3c90x.zli
     -r-xr-xr-x    1 root     root         2048 Sep  1 13:27 boot.cat
     -r-xr-xr-x    1 root     root         9652 Sep  1 13:27  
isolinux.bin
     -r-xr-xr-x    1 root     root          174 Sep  1 13:27  
isolinux.cfg

Then, if you looked at the .cfg file:

     $ cat isolinux.cfg
     # These default options can be changed in the geniso script
     SAY Etherboot ISO boot image generated by geniso
     TIMEOUT 30
     DEFAULT 3c90x.zli
     LABEL 3c90x.zlilo
     KERNEL 3c90x.zli

Don't forget to unmount the .iso image:

     $ cd
     $ sudo umount /mnt


Now, you want to do this on a floppy, but it's a similar process.
You could do something like:

Make your DOS Filesystem on a floppy:

     $ sudo mkfs.msdos /dev/fd0
     mkfs.msdos 2.8 (28 Feb 2001)

Mount the floppy, and check it out:

     $ sudo mount /dev/fd0 /mnt/floppy/
     $ cd /mnt/floppy/

     $ ls -l
     total 8
     -r-xr-xr-x    1 root     root         8184 Sep  1 13:40 ldlinux.sys

Copy a rom-o-matic.net .zlilo image for the card you need:

     $ sudo cp ~/eb-5.4.0-3c90x.zlilo 3c90x.zli

Create a syslinux.cfg file to load the "kernel" (actually an  
etherboot image masquerading as a kernel)

     $ sudo cat > syslinux.cfg
     TIMEOUT 30
     DEFAULT 3c90x.zli
     LABEL 3c90x.zlilo
      KERNEL 3c90x.zli
(hit control-D to end file)

Check out the floppy:

     $ ls -l
     total 34
     -rwxr-xr-x    1 root     root        25986 Sep  1 13:44 3c90x.zli
     -r-xr-xr-x    1 root     root         8184 Sep  1 13:40 ldlinux.sys
     -rwxr-xr-x    1 root     root           65 Sep  1 13:46  
syslinux.cfg

Don't forget to unmount:

     $ cd
     $ sudo umount /mnt/floppy

Now, just for fun, check it out your floppy with mdir:

     $ mdir a:
      Volume in drive A has no label
      Volume Serial Number is 4317-3CC5
     Directory for A:/

     ldlinux  sys      8184 2005-09-01  13:40  ldlinux.sys
     3C90X    ZLI     25986 2005-09-01  13:44  3c90x.zli
     SYSLINUX CFG        65 2005-09-01  13:46  syslinux.cfg
             3 files              34 235 bytes
                               1 422 848 bytes free

So, there it a floppy, with an DOS filesystem on it, booted with  
SYSLINUX, which then loads Etherboot, which then presumably loads  
pxelinux.0 over the network, which finally loads a kernel.

All FLOSS!

I hope this helps you.  Please let us know how things go.  If you get  
something to work, please post a short recipe or tutorial of your  
method, if you can.

Thanks,

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

Re: [Etherboot-users] rom-o-matic and a fs

[Michael B. <mb...@fe...>]

On Thu, 1 Sep 2005, Carl Karsten wrote:
> What are the chances of using mkfs.vfat and a rom-o-matic file to create
> a floppy that will pxe boot and have a fs to store some files?

You could probably create a .zlilo image, copy it to the formatted floppy 
and then run lilo to set up the floppy's boot sector to boot from the 
.zlilo image.

Michael

[Etherboot-users] rom-o-matic and a fs

[Carl K. <ca...@pe...>]

What are the chances of using mkfs.vfat and a rom-o-matic file to create a floppy 
that will pxe boot and have a fs to store some files?

^Carl Karsten

[Etherboot-users] booting paralel or usb

[Carl K. <ca...@pe...>]

Given that over 1/2 the boxes I work with don't have built in support for PXE 
booting, and they don't all have the same nic, so I am messing with rom-o-matic 
floppies more than I want to.

What I would love is a floppy and an external (usb or parallel port) Ethernet 
connection that I can use to PXE boot memdisk and the proper rom-o-matic image for 
whatever nic is in the local box.  I think I can deal with figuring out what nic 
is in the box and picking the right rom-o-matic image, but a "super duper 
universal boots most nics" version would be awesome.

Hmm, now that I think about it, the "universal" rom-o-matic would take care of my 
problem: one floppy that boots all.  How hard would it be for the boot floppy to 
scan the PCI bus and use the ID to load the right driver?  (Not too concerned 
about ISA, USB or multiple nics.)

But, the usb rom-o-matic would have the advantage of being able to use an 801.11 
usb nic, which would be nice.

^Carl K

Re: Re: [Etherboot-users] Kernel creation for use with Etherboot

[Sandeep T. <san...@re...>]

  =0AHi Marty,=0AI'm facing a problem in configuring for the ROM image on r=
om-o-matic. I have the kernel image and the rootfs.=0AI'm making the kernel=
 image network bootable as follows:=0Amknbi-linux linux.binary --param=3D"r=
oot=3D/dev/nfs ip=3D::::::nfsroot=3D/tftpboot/rootfs console=3DttyS0,115200=
" > board/kernel.nb=0ANow I have the net-bootable image in my board directo=
ry.=0AI have the SBC board to which floppy can be connected. so I want to m=
ake the floppy ROM image. How should I configure for it??particularly that =
"advanced_only_encapsulated" option..??=0A=0AThanks,=0ASandeep.=0A=0AOn Tue=
, 21 Jun 2005 Marty Connor wrote :=0A>On Jun 20, 2005, at 3:32 PM, Faber wr=
ote:=0A>>Hi there.  I'm new to etherboot, and while I've been using linux f=
or at least a couple of years, I'm still not quite down with the kernel com=
pile process. I created a directory called /newkernels/ in order to downloa=
d source and compile a custom kernel for a computer which I would like to u=
se etherboot with.  the full directory to my source is /newkernels/src/linu=
x-2.4.27/=0A>>now, I've done make dep, make bzImage, make modules, but I sk=
ipped make modules_install because I didn't want to install any modules on =
the server computer.  the etherboot howto at http://etherboot.sourceforge.n=
et/doc/html/userman/x126.html under "Compiling a Custom Kernel" states that=
 before I can run mkelf-linux to create the boot image, I need to create an=
 initial ram disk for this kernel image.  Now, again I'm not perfectly fami=
lliar with building kernels, and I've hunted around the net, and have no cl=
ue on how to properly use mkinitrd.  I've read the man page which didn't he=
lp solve anything, unfortunately.  Can someone who's done this either help =
me, or point me at a howto for etherboot which is much more in-depth and co=
mprehensive than the one on the website?=0A>>Thanks a lot, I know this isn'=
t exactly on topic, but any help whatsoever is appreciated!=0A>>--Faber=0A>=
=0A>Hi Faber,=0A>=0A>Welcome to Etherboot.  I can understand your confusion=
 about how to proceed.=0A>=0A>Can you describe more about how you would lik=
e things to work after you boot?  It sounds like you would like to have the=
 client computer run without the need for a server after it is booted.=0A>=
=0A>This is certainly possible.=0A>=0A>There are two ways to use Etherboot =
to boot a kernel (and optionally mount an initrd and run a linuxrc script o=
n it).=0A>=0A>You can use mknbi-linux to make an NBI image, which contains =
your kernel, and additionally may include an initrd, or you can use the PXE=
LINUX package to load a kernel and initrd for you.  PXELINUX does not need =
the kernel and initrd to be wrapped.=0A>=0A>Since Etherboot only recently g=
ot PXE support (as of 5.4.0), there is somewhat less documentation on the E=
therboot site about booting via PXE, but there is lots of information on th=
e net about how to use PXELINUX, and if you just treat Etherboot like any o=
ther PXE bootloader, you will be able to load a pxelinux.0 file from your t=
ftp server.  pxelinux.0 will in turn load your kernel and ramdisk as direct=
ed by the configuration file(s) in the pxelinux.cfg directory.=0A>=0A>An ad=
vantage to using PXELINUX is that if you need to change your kernel or init=
rd, you don't have to remake the NBI image, just put the new file on the tf=
tp server and go.=0A>=0A>Here is a link that talks about making initrd imag=
es.  It also has some sample initrd images from some Linux installation CDs=
.=0A>=0A>     http://www.linux-boot.net/InitRD/Creating/=0A>=0A>I also sugg=
est that you check out the LTSP (linux terminal server project) site=0A>=0A=
>    http://www.ltsp.org/=0A>=0A>There is lots of interesting information t=
here about network booting, and especially what to do after the kernel is l=
oaded.=0A>=0A>If you can be more specific about what you are trying to acco=
mplish, perhaps we can point you to or provide more specific information on=
 how to reach your goal.=0A>=0A>Once again, welcome, and I hope this helps =
you find your way.=0A>=0A>Marty=0A>=0A>--     Try: http://rom-o-matic.net/ =
to make Etherboot images instantly.=0A>=0A>    Name: Marty Connor=0A>US Mai=
l: Entity Cyber, Inc.; P.O. Box 391827;=0A>          Cambridge, MA 02139; U=
SA=0A>   Voice: (617) 491-6935; Fax: (617) 491-7046=0A>   Email: mdc@etherb=
oot.org=0A>     Web: http://www.etherboot.org/=0A>=0A>=0A>=0A>-------------=
------------------------------------------=0A>SF.Net email is sponsored by:=
 Discover Easy Linux Migration Strategies=0A> from IBM. Find simple to foll=
ow Roadmaps, straightforward articles,=0A>informative Webcasts and more! Ge=
t everything you need to get up to=0A>speed, fast. http://ads.osdn.com/?ad_=
id=3D7477&alloc_id=3D16492&op=3Dclick=0A>__________________________________=
_____________=0A>Etherboot-users mailing list=0A>Eth...@li...ur=
ceforge.net=0A>https://lists.sourceforge.net/lists/listinfo/etherboot-users=
=0A

[Etherboot-users] Re: [syslinux] pxelinux menu32 and two boot images

[H. P. A. <hp...@zy...>]

Dinesh P. wrote:
> LABEL VRUSHYOG
>     MENU LABEL PXE
>     KERNEL pxe/pxelinux.0
>     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0

This is total nonsense.  First of all, loading a different pxelinux.0 
does not (currently) mean you're loading a different configuration file, 
and either way, "append" does absolutely nothing when combined with a .0 
file.

You might be able to do:

LABEL VRUSHYOG
     MENU LABEL Thinstation
     KERNEL pxe/vmlinuz
     append ramdisk_blocksize=4096 initrd=pxe/initrd root=/dev/rd/0

[Etherboot-users] pxelinux menu32 and two boot images

[Dinesh P. <glo...@gm...>]

Hi, there
             now i am booting pxelinux menu32 with 2 boot images 1. DOS boot 
image 2. Thinstaion pxelinux and my directory structure is like this
(Pxelinux with menu32)

/tftpdroot/pxelinux.0
/tftpdroot/pxelinux.cfg/default
/tftpdroot/dos.imz (DOS bootimage)
/tftpdroot/memdisk (memdisk package)

(Thinstation Pxelinux)
/tftpdrooot/pxe/pxelinux.0
/tftpdroot/pxe/initrd
/tftpdroot/pxe/vmlinuz
/tftpdroot/pxe/otherconfiles
/tftpdroot/pxe/pxelinux.cfg/default

now the config from /tftpdroot/pxelinux.cfg/default     is
DEFAULT menu
PROMPT 0
NOESCAPE 1
TIMEOUT 100
IMPLICIT 0
ALLOWOPTIONS 0
MENU TITLE VRUSHYOG BOOT MENU
LABEL menu
     MENU HIDE
     KERNEL menu.c32
LABEL dos
     MENU LABEL dos nbi
     KERNEL memdisk
     append initrd=pcdos.IMZ
LABEL VRUSHYOG
     MENU LABEL PXE
     KERNEL pxe/pxelinux.0
     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0

and the config from /tftpdroot/pxe/pxelinux.cfg/default is

default linux
prompt 0
label linux
kernel vmlinuz
append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0 
ramdisk_size=262144

now when i boot from dos image it boots and when i try to boot from 
thinstaion linux image it hangs and display one dot only so please suggest 
me what i have to do.


Dinesh P.

Re: [Etherboot-users] pxelinux hangs with etherboot

[Marty C. <md...@et...>]

On Aug 20, 2005, at 9:30 AM, Dinesh P. wrote:
> hi,
>    I have created dos boot image using windows XP, and now running  
> it with memdisk package provided with syslinux, when i start client  
> computer after loading kernel in memory and loading init sequency  
> when loading dos nbi image it hangs on "Starting...." it might be  
> problem with support of memdisk with DOS boot image created from XP  
> or ME i checked on forum.
> Dinesh P.

Once again, and after being warned, you describe what you have done,  
but with few details, without config files, and without showing the  
steps you used to create the disk image, or boot the machine.

You would be wiser to describe in as much detail as possible what you  
wish to happen, and let people offer suggestions on how to actually  
go about it.

I have seen a number of discussions on the web describing things  
similar to what you wish to achieve.
Here's an interesting discussion that even includes a link to a disk  
image (NU2):

     http://home.allegiance.tv/~joem298/

I has screenshots, a discussion of what he did, and why, and  
downloadable images that can be used to recreate his work.

And, by the way, I find your (re)naming of this thread to "pxelinux  
hangs with etherboot" to be both deceptive and wrong.

While I personally think that the thread should be called

     "User with no clue demands free help!"

I have allowed this to continue for a while.

At this point, the problems you are pointing out are pretty clearly  
not provably related to Etherboot.  Further, you have ignored my  
requests to show your work.

Please take your problems with SYSLINUX/PXELINUX to the mailing list  
for that project, and unless you are willing to provide more specific  
details of your problem, do not post.

It brings me no joy to do this, but I think that it is the right  
thing to do.

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] pxelinux hangs with etherboot

[Dinesh P. <glo...@gm...>]

hi,
    I have created dos boot image using windows XP, and now running it with 
memdisk package provided with syslinux, when i start client computer after 
loading kernel in memory and loading init sequency when loading dos nbi 
image it hangs on "Starting...." it might be problem with support of memdisk 
with DOS boot image created from XP or ME i checked on forum.

Dinesh P. 

Re: [Etherboot-users] two pxelinux.0

[Marty C. <md...@et...>]

On Aug 19, 2005, at 1:45 PM, Dinesh P. wrote:
> ... i have tryied to debug the problem but don't know what is it.??

Just saying that you tried to debug isn't enough, if what you want is 
help.  Without showing your work, you make the people trying to help 
you have to guess what really happened, and then you use the mailing 
list as a free consulting service.

You need to describe (preferably with some output) what exactly you 
did, and what happened.

For example, you did not include a copy of your pxelinux.cfg/default 
file.  If you had, we could see whether you made some mistakes in your 
configuration.  Also, your dhcpd.conf file might be interesting to see.

Further, Etherboot 5.3.7 is quite old.  Why not use 5.4.0, which is the 
current production release.

To learn to debug, you need to proceed methodically, make theories 
about what might be happening, and then create a test that proves or 
disproves your theory.

 From your message:

> i have compiled PXE images of thinstation and problem is that there 
> are two pxelinux.0 files 1 for the menu32 and another one of the 
> thinstation,

pxelinux.0 is rarely the problem.  Compiling your own version is 
probably useless, because your configuration is probably broken.

> i have tryied configuring same default config in config directory and 
> also copyied all the thinstation kernel and configuration files in 
> /tftpdroot/pxe and menu files at /tftpdroot now there are two 
> different pxelinux.0

Please show your configuration.  Directory structure, config files, and 
preferably some output, if possible.

>                when i boot the client system using etherboot 5.3.7 it 
> shows option to boot two images but when i select thinstation it 
> dispalys one . and stops for 1 min and then flicker display screen 
> comes.

Etherboot 5.4.0 is current.  Please download an image from 
rom-o-matic.net and do your testing with that.

Then there's the question of your kernels, which is where I suspect the 
real problem lies.  If you feed PXELINUX an nbi file (a kernel and 
initrd packaged by mknbi), I suspect bad things will happen.  PXELINUX 
deals with raw kernels and initrd files which are usually specified in 
the pxelinux.cfg/default file.

Hopefully with this information you will be able to make more progress 
in your debugging.

Marty

-- 
     Try: http://rom-o-matic.net/ to make Etherboot images instantly.

    Name: Marty Connor
US Mail: Entity Cyber, Inc.; P.O. Box 391827;
          Cambridge, MA 02139; USA
   Voice: (617) 491-6935; Fax: (617) 491-7046
   Email: md...@et...
     Web: http://www.etherboot.org/

[Etherboot-users] two pxelinux.0

[Dinesh P. <glo...@gm...>]

Hi,
     First of all i want to say thanks for your help alex, now i have 
compiled PXE images of thinstation and problem is that there are two 
pxelinux.0 files 1 for the menu32 and another one of the thinstation, i have 
tryied configuring same default config in config directory and also copyied 
all the thinstation kernel and configuration files in /tftpdroot/pxe and 
menu files at /tftpdroot now there are two different pxelinux.0
                when i boot the client system using etherboot 5.3.7 it shows 
option to boot two images but when i select thinstation it dispalys one . 
and stops for 1 min and then flicker display screen comes.
                i have tryied to debug the problem but don't know what is 
it.??

Dinesh P. 

Re: [Etherboot-users] Boot menu ?

[Hamish G. <ha...@pr...>]

Marty,

You really are a saint!

I really like the way you expressed your encouragement and tips for 
Dinesh to get more help from the list.

If I may, I will cut and paste those sage words to newbies on other 
other lists I subscribe to - I will, of course, reference the source of 
the quote!

Hamish

Marty Connor wrote:
> Dinesh,
> 
> You need to do a better job asking for help.  You provide very little in 
> the way of information, and then you literally beg for help.
> 
> I applaud Alexander for helping you, but I also think that you need to 
> do more work on your own to try and figure things out.
> 
> If you are having trouble with SYSLINUX/PXELINUX, then at least 
> demonstrate that you have read (or attempted to read) the 
> documentation.  There is also a mailing list for help specifically with 
> that software, if you can't figure out the documentation or examples.
> 
> Also, in debugging, you should attempt to create simple test cases, and 
> when they fail, send input, output, and what you thought should happen 
> to the list for analysis.  Otherwise, all we can do is guess what might 
> be happening.
> 
> I want to encourage you to proceed, but I also want to strongly suggest 
> that if you want help, you need to show that the time of the people 
> trying to help you is not wasted.  You can do this by showing that 
> progress you have made, by producing output, and explaining in more 
> detail what you did.
> 
> If your English skills are a problem, please find a friend who has 
> better skills, and have them help you, in exchange for help with 
> something they need help with.
> 
> I hope you succeed, but even more I hope that in this process you 
> develop better debugging skills, and improve your methods of asking for 
> help.
> 
> Regards,
> 
> Marty
> 
> 
> On Aug 19, 2005, at 1:10 AM, Dinesh P. wrote:
> 
>> Hi, there,
>>            Well now i have booted client using pxelinux.0 with default 
>> config provided by you but problem is that when it try to load kernel 
>> image it say "Invalid or Corrupt kernel image" and that image is 
>> compiled with thinstation and it works it if specified insted of 
>> pxelinux.0 in DHCP but it not works in pxelinux so pealse help me what 
>> is the problem.
>>
>> Dinesh P.
>> ----- Original Message ----- From: "Alexander Heinz" <mai...@gm...>
>> To: <Kevin>
>> Cc: "Dinesh P." <glo...@gm...>
>> Sent: Friday, August 19, 2005 4:30 AM
>> Subject: Re: [Etherboot-users] Boot menu ?
>>
>>
>>>> LABEL thinstation nbi
>>>>     MENU LABEL thinstation
>>>>     KERNEL thinstation.nbi
>>>> LABEL thinstation regular
>>>>     MENU LABEL thinstation
>>>>     KERNEL vmlinuz
>>>>     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0 vga=791
>>>
>>>
>>> that is wrong.
>>>
>>> should be:
>>>
>>> LABEL thin1
>>>     MENU LABEL thinstation nbi
>>>     KERNEL thinstation.nbi
>>> LABEL thin2
>>>     MENU LABEL thinstation pxe
>>>     KERNEL vmlinuz
>>>     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0 vga=791
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> SF.Net email is Sponsored by the Better Software Conference & EXPO
>>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
>>> Practices
>>> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
>>> & QA
>>> Security * Process Improvement & Measurement * 
>>> http://www.sqe.com/bsce5sf
>>> _______________________________________________
>>> Etherboot-users mailing list
>>> Eth...@li...
>>> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>>>
>>>
>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is Sponsored by the Better Software Conference & EXPO
>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
>> Practices
>> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
>> & QA
>> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
>> _______________________________________________
>> Etherboot-users mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>>
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
> 
> 

Re: [Etherboot-users] Boot menu ?

[Marty C. <md...@et...>]

Dinesh,

You need to do a better job asking for help.  You provide very little 
in the way of information, and then you literally beg for help.

I applaud Alexander for helping you, but I also think that you need to 
do more work on your own to try and figure things out.

If you are having trouble with SYSLINUX/PXELINUX, then at least 
demonstrate that you have read (or attempted to read) the 
documentation.  There is also a mailing list for help specifically with 
that software, if you can't figure out the documentation or examples.

Also, in debugging, you should attempt to create simple test cases, and 
when they fail, send input, output, and what you thought should happen 
to the list for analysis.  Otherwise, all we can do is guess what might 
be happening.

I want to encourage you to proceed, but I also want to strongly suggest 
that if you want help, you need to show that the time of the people 
trying to help you is not wasted.  You can do this by showing that 
progress you have made, by producing output, and explaining in more 
detail what you did.

If your English skills are a problem, please find a friend who has 
better skills, and have them help you, in exchange for help with 
something they need help with.

I hope you succeed, but even more I hope that in this process you 
develop better debugging skills, and improve your methods of asking for 
help.

Regards,

Marty


On Aug 19, 2005, at 1:10 AM, Dinesh P. wrote:

> Hi, there,
>            Well now i have booted client using pxelinux.0 with default 
> config provided by you but problem is that when it try to load kernel 
> image it say "Invalid or Corrupt kernel image" and that image is 
> compiled with thinstation and it works it if specified insted of 
> pxelinux.0 in DHCP but it not works in pxelinux so pealse help me what 
> is the problem.
>
> Dinesh P.
> ----- Original Message ----- From: "Alexander Heinz" 
> <mai...@gm...>
> To: <Kevin>
> Cc: "Dinesh P." <glo...@gm...>
> Sent: Friday, August 19, 2005 4:30 AM
> Subject: Re: [Etherboot-users] Boot menu ?
>
>
>>> LABEL thinstation nbi
>>>     MENU LABEL thinstation
>>>     KERNEL thinstation.nbi
>>> LABEL thinstation regular
>>>     MENU LABEL thinstation
>>>     KERNEL vmlinuz
>>>     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0 
>>> vga=791
>>
>> that is wrong.
>>
>> should be:
>>
>> LABEL thin1
>>     MENU LABEL thinstation nbi
>>     KERNEL thinstation.nbi
>> LABEL thin2
>>     MENU LABEL thinstation pxe
>>     KERNEL vmlinuz
>>     append ramdisk_blocksize=4096 initrd=initrd root=/dev/rd/0 vga=791
>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is Sponsored by the Better Software Conference & EXPO
>> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
>> Practices
>> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
>> & QA
>> Security * Process Improvement & Measurement * 
>> http://www.sqe.com/bsce5sf
>> _______________________________________________
>> Etherboot-users mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>>
>>
>
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
> & QA
> Security * Process Improvement & Measurement * 
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>