etherboot-users — Discussion of user issues

Re: [Etherboot-users] Questions about building "netboot floppy " in ~600KB

[Michael S. <sch...@gm...>]

Nico Oosthuizen schrieb:

> Have you looked at http://etherboot.anadex.de/.
> There is a section that deal with a universal 
> boot floppy.

I have looked there, yes. There is a boot floppy available, but I could
not find information about how it was created (the README on the floppy
contains links to all the programs used to build it, but no build
options etc. in it either).

Michael

Re: [Etherboot-users] Questions about building "netboot floppy" in ~600KB

[Michael S. <sch...@gm...>]

Berend De Schouwer schrieb:
> On Wednesday 25 January 2006 15:03, Michael Schierl wrote:
>> Hi all,
>>
>> On this floppy there are still about 600KB free, so I thought to put
>> a few etherboot .zlilos onto it as well. They are intended for
>> booting knoppix-terminalserver (or grml-terminalserver) when the used
>> BIOS is too old for netboot support.
> 
> I've used Netboot on a 386SX, with 2MB RAM, to boot Linux 1.2.13.  It's 
> unlikely that hardware too old for Netboot will boot Knoppix of any 
> sort.  Are we talking about the same Netboot?

I guess not.

For me, netboot is the feature included in most modern mainboard BIOSes
to boot via network without any other hardware/software, just enable it
in BIOS and boot. Works like a charm if the BIOS support it. Just like
boot from CDROM or boot from USB. And I know of Pentium PCs that have a
BIOS that does not support that (some even lack support booting from CDROM).

And if you think Knoppix is too slow on these machines (even for
recovery when someone misconfigured his system), replace Knoppix by
UDPcast (for taking an image of a broken filesystem before trying to
repair it).

Michael

Re: [Etherboot-users] Questions about building "netboot floppy " in ~600KB

[Nico O. <ni...@an...>]

Hi Michael

Have you looked at http://etherboot.anadex.de/.
There is a section that deal with a universal 
boot floppy.

Nico 

Re: [Etherboot-users] Boot disk or network based on DHCP option string

[Nico O. <ni...@an...>]

Hi David

Maybe this will help.

I use rom-o-matic for my boot images.
The first setting in the Configure section of the images 
you can specify how long it must wait before trying a 
boot image. If you set if to something like 20 seconds you 
don't have to be quit to choose if to boot (L)ocal or 
(N)etwork.

This is the section I mentioned:
#  ASK_BOOT:  
  Ask "Boot from (N)etwork ... or (Q)uit? " at startup,
timeout after n seconds (0 = no timeout). If unset or
negative, don't ask and boot immediately using the default.
 
#

The next choice in the configure section section you
can even set the sequence it must try to boot from. So if
you mostly boot from local disk and not from the network,
it will boot after the time you have set from the first
selection you made if that is available. 

Nico

>     Is there a way to control etherboot via a dhcp option
> string? (I.E. set it to boot from disk or the network) I
> want to do this because hitting the L or N keys at the
> correct time is getting annoying. At the moment, PXE
> booting does not work, So I am loading ELF images and
> booting them. I want to control wether or not the node
> grabs its kernel from the netwok or from disk.
> 
> Thank you,
> 
> -David

Re: [Etherboot-users] Questions about building "netboot floppy" in ~600KB

[Berend De S. <ber...@uc...>]

On Wednesday 25 January 2006 15:03, Michael Schierl wrote:
> Hi all,
>
> On this floppy there are still about 600KB free, so I thought to put
> a few etherboot .zlilos onto it as well. They are intended for
> booting knoppix-terminalserver (or grml-terminalserver) when the used
> BIOS is too old for netboot support.

I've used Netboot on a 386SX, with 2MB RAM, to boot Linux 1.2.13.  It's 
unlikely that hardware too old for Netboot will boot Knoppix of any 
sort.  Are we talking about the same Netboot?

> - are there any known incompatibilities (like driver foo crashes when
> it finds card bar) to avoid when making images for multiple drivers?

Yes.  Some 8390/ne2000 drivers will crash other add-on cards and the PC.  
Not just network cards.  It'll take down SCSI cards too.  That's why 
you need to specify I/O port.  But this is for 8 and 16 bit ISA -- not 
for PCI.


Regards,
Berend

-- 
Confidentiality notice: http://ucs.co.za/conf.html

[Etherboot-users] Questions about building "netboot floppy" in ~600KB

[Michael S. <sch...@gm...>]

Hi all,

I got tired of needing lots of boot floppies to do different stuff
(memtest, cmospwd, grub, smart boot manager, freedos, etc.) which are
almost empty, so I decided to build a floppy that can do all of the above.

On this floppy there are still about 600KB free, so I thought to put a
few etherboot .zlilos onto it as well. They are intended for booting
knoppix-terminalserver (or grml-terminalserver) when the used BIOS is
too old for netboot support. But it should remain as generic as
possible, i. e. boot everything else a netboot BIOS can usually boot.
However, I don't have an idea on which PCs I'll have to use it, so I
cannot select the correct driver before building it.

So I have a few questions:

- etherboot has quite a lot of compilation options about supported
images and the like. Which of them are usually supported by a common
netboot BIOS (on modern mainboards), which are never supported? I intend
to remove the latter ones.

- when making all zlilos (with default options, one for each driver)
they consume more than one megabyte disk space -- too much for my size
constraints. But I guess they contain lots of duplicate code. Is there
an option somewhere I missed that allows to make the zlilos two-part
(like using a generic zlilo as "kernel" and a small driver-specific file
as "initrd" -- or the same with GNU multiboot modules)?

- making an image of all drivers fails. So I guess the best option would
be a bunch of zlilos sorted by card manufacturer or something like this.
The RELNOTES suggest to use the "multiple driver rule". Where do I find
documentation about that? Simply using

make bin/foo--bar--baz.zlilo

(as I read the comment in parentheses) did not work for me.

- are there any known incompatibilities (like driver foo crashes when it
finds card bar) to avoid when making images for multiple drivers? Are
there any drivers that do not work at all (so they could be removed) or
that are built-in into chipsets that always contain a netboot-able BIOS
anyway (so are not needed on a generic floppy)?

- Any other suggestions? I noticed that other etherboot disks uses
SYSLINUX as boot loader. Replacing GRUB with SYSLINUX is no option for
me (unless SYSLINUX supports all the stuff i need from GRUB, and I doubt
that), but I'd chainload SYSLINUX if that made my life easier.

Thanks in advance for your suggestions,

Michael

[Etherboot-users] Boot disk or network based on DHCP option string

[David T. P. <phe...@un...>]

Hello everybody,

    Is there a way to control etherboot via a dhcp option string? (I.E. =
set it to boot from disk or the network) I want to do this because =
hitting the L or N keys at the correct time is getting annoying. At the =
moment, PXE booting does not work, So I am loading ELF images and =
booting them. I want to control wether or not the node grabs its kernel =
from the netwok or from disk.

Thank you,

-David

[Etherboot-users] Re: [Ltsp-discuss] Questions about pxe and etherboot

[Richard B. <ra...@xs...>]

Marty,

thanks for your reply.

Op zondag 22 januari 2006 03:13, schreef Marty Connor:
..... [skipped] .....
> >   In my case I have succesfully created floppy boot images.  Is
> > it now possible (in the client system)  to swap these floppy
> > bootimages for
> > networkcard pxe images (by programming an eprom image from rom-o-
> > matic) and
> > have the same machine still booted via the network?  I mean is no
> > there no
> > bios option that needs to be changed (for example: change boot
> > order.  Make
> > lan the first thing to try instead of the floppy disk drive).  As
> > far as I
> > remember I have not seen a 'boot from the lan' option in the bioses
> > that I
> > have looked at.   Is it like this, that when a pxe image is present
> > in a
> > network card, it automatically boots the machine?
> > I did not find this explained on this page:
> > http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE hence I my question.
>
> BIOSes have evolved, and have different ways of expressing network
> booting capability.  If you have a reasonably recent Intel
> motherboard, for instance, with a Phoenix BIOS, and you put a NIC
> card in with a PXE boot ROM on it, when you go to the BOOT menu, you
> can actually see the boot ROM as a boot option along with the floppy
> and hard drive, and you can set its order.  

Checked 2 computers today and the "lan" boot option is present.  unfortenately 
those computers are not part of the ltsp setup...

> This is part of the BIOS 
> specification, and if your boot ROM is "PNP Conformant" (and your
> BIOS is), you can set the boot priority of things like Adaptec SCSI
> cards, and Ethernet Cards, and your BIOS will respect it.

Hmm,  how can I see that a bios or bootrom is PNP conformant (check the 
documentation that comes with the computer?).  

> Not all BIOSes correctly implement PNP, but quite a few do.  A BIOS
> update in many cases will help. If the BIOS copyright date is in the
> early 1990s, you may have some difficulty, and in that case,
> Etherboot will likely just run.
>
> > For the moment I just assume that pxe boots the system when it is
> > present.
> > This is for my next question.  In case a noteboot does not support
> > pxe on its
> > own ethernet card (pcmcia card), would the following card make any
> > notebook
> > pxe enabled:
> > http://www.argontechnology.com/product.aspx/cid1/103/pid/304 ?
> > It sounds strange to me, that when a notebook is not aware of pxe
> > on its one
> > because it was never designed for it, that it would now
> > automatically work
> > when the above mentioned card is plugged in....
>
>    Product Description
>    Argon's EP-4103DL-PXE Cardbus Fast Ethernet PC Card with PXE
>    10/100 Fast Ethernet Dongle-less PCMCIA
>    Complies with IEEE 802.3 10BaseT and 802.3u 100BaseTX Standards
>    Supports 10/100M Auto-Negotiation 32bit High Performance 100Mbps
> Networking
>
>    PXE Support included with Argon's PXE on Disk: works with Argon
> Client Management
>    Services (CMS) PXE Server or Microsoft Remote Installation
> Services (RIS).
>
> Hmm, I believe that you'll need to boot from their floppy to get PXE
> to work.
>
> The technical reason is that when most notebook boot, unless their
> Ethernet ports are on the motherboard, they have to initialize a PCI
> to PCMCIA bridge chip.
>
> The question is, where is the code to do this?  Well, it kind of has
> to be done by the BIOS, which would then have to know how to control
> whatever PCMCIA Ethernet card you happen to have plugged into your
> PCMCIA slot.
>
> There's the rub.  Unless your laptop BIOS specifically knows what
> bridge chip is being used, and what PCMCIA card is being used, most
> laptops without Ethernet wait for a kernel or other boot code (like
> Argon's PXE on Disk (kind of like an Etherboot floppy)), to do it.
>
> Etherboot, unfortunately doesn't yet know how to deal with PCMCIA
> buses.  It's one of the things we hope to add, but so far, we do PCI
> and ISA buses mainly, which takes care of the majority of cases.
> We'd like to do PCMCIA and USB, and I'm sure we'll get there in time.
> Someone will decide they want it, and do it or fund it, just like PXE
> support.
>
> > I'll highly appreciate any explanation on pxe.  The wiki pages are
> > good, but
> > unfortenately they just missed the 2 points mentioned above.
>
> I hope this is helpful.  I think my answers are correct.  I hope and
> expect that someone will correct me if I am mistaken.

Sofar it clarifies a lot for me.

> > Another question I have (just out of curiousty); what ethercards
> > support pxe
> > out the box nowadays all?  Or should they all get an eprom to
> > enable pxe?
> > Same question for notebooks, which notebooks support pxe nowadays,
> > is that
> > all or for example only the IBM thinkpad (that's the answer from
> > google) ;)
>
> For an Ethernet card to support PXE out of the box, it needs a flash
> EEPROM.  This raises the cost, but not so much as in the old days.  I
> think I noticed an RTL8169 (Gigabit Card) that has PXE on it for not
> too much more than $20 the other day.

hmmm, that sounds attractive.  But the ltsp shop site list an network card 
with bootrom for $20 as well (If I not mistaken).

> Now, if you're a bargain hunter, you can find old Intel EEPRO100s and
> 3COM 3C905CTXM cards, which have PXE in flash memory, and will
> network boot by loading PXELINUX.0 from the SYSLINUX/PXELINUX/
> ISOLINUX package.

Will the ltsp boot sequence do as well, or must it have to be 
SYSLINUX/PXELINUX/ISOLINUX package.  I think the ltsp server provides 
PXELINUX.0.  At least that is what I saw in /tftp/.... directory.

-- 
Richard Bos
Without a home the journey is endless

[Etherboot-users] Re: [Ltsp-discuss] Questions about pxe and etherboot

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

On Jan 21, 2006, at 5:10 PM, Richard Bos wrote:

> would you be so kind to get me updated about booting from the net  
> via pxe,
> etherboot and the like.

Hi there.  Perhaps I can be of help.  I created and maintain rom-o- 
matic.net, and am Project Leader for the Etherboot team.

PXE is a method for booting and managing computer via a network  
connection.  Etherboot implements PXE as do various pieces of  
software.  Etherboot didn't used to implement the PXE method of  
booting. Support for PXE was added in the last couple of years.

>     I understand how it works, but I miss the fine
> details to really implement it.  BTW I started to become interested  
> in pxe
> after reading an email exchange between Jim McQuillan and Simon  
> Langley about
> getting notebooks/laptops connected with a wireless pocket access  
> point
> device (wireless bridge) (september last year).   From the wiki I  
> understand
> that the notebook should be booted using pxe.... here my adventure
> (questions) starts ;)

Good questions.  I'm glad you're wondering, and glad you're trying to  
find out.

> Sofar I understand that the etherboot images from rom-o-matic can  
> be used for
> this purpose.

They can be used to boot computers over the network using both PXE  
method and what we'll call the NBI method of network booting.   
Etherboot and PXE methods both use DHCP and TFTP.  Etherboot supports  
some additional protocols, and when using Etherboot's older method of  
booting, the image to be booted is prepared (wrapped) using a tool  
called mknbi (make-network-boot-image).

>   In my case I have succesfully created floppy boot images.  Is
> it now possible (in the client system)  to swap these floppy  
> bootimages for
> networkcard pxe images (by programming an eprom image from rom-o- 
> matic) and
> have the same machine still booted via the network?  I mean is no  
> there no
> bios option that needs to be changed (for example: change boot  
> order.  Make
> lan the first thing to try instead of the floppy disk drive).  As  
> far as I
> remember I have not seen a 'boot from the lan' option in the bioses  
> that I
> have looked at.   Is it like this, that when a pxe image is present  
> in a
> network card, it automatically boots the machine?
> I did not find this explained on this page:
> http://wiki.ltsp.org/twiki/bin/view/Ltsp/PXE hence I my question.

BIOSes have evolved, and have different ways of expressing network  
booting capability.  If you have a reasonably recent Intel  
motherboard, for instance, with a Phoenix BIOS, and you put a NIC  
card in with a PXE boot ROM on it, when you go to the BOOT menu, you  
can actually see the boot ROM as a boot option along with the floppy  
and hard drive, and you can set its order.  This is part of the BIOS  
specification, and if your boot ROM is "PNP Conformant" (and your  
BIOS is), you can set the boot priority of things like Adaptec SCSI  
cards, and Ethernet Cards, and your BIOS will respect it.

Not all BIOSes correctly implement PNP, but quite a few do.  A BIOS  
update in many cases will help. If the BIOS copyright date is in the  
early 1990s, you may have some difficulty, and in that case,  
Etherboot will likely just run.

> For the moment I just assume that pxe boots the system when it is  
> present.
> This is for my next question.  In case a noteboot does not support  
> pxe on its
> own ethernet card (pcmcia card), would the following card make any  
> notebook
> pxe enabled:
> http://www.argontechnology.com/product.aspx/cid1/103/pid/304 ?
> It sounds strange to me, that when a notebook is not aware of pxe  
> on its one
> because it was never designed for it, that it would now  
> automatically work
> when the above mentioned card is plugged in....

   Product Description
   Argon's EP-4103DL-PXE Cardbus Fast Ethernet PC Card with PXE
   10/100 Fast Ethernet Dongle-less PCMCIA
   Complies with IEEE 802.3 10BaseT and 802.3u 100BaseTX Standards
   Supports 10/100M Auto-Negotiation 32bit High Performance 100Mbps  
Networking

   PXE Support included with Argon's PXE on Disk: works with Argon  
Client Management
   Services (CMS) PXE Server or Microsoft Remote Installation  
Services (RIS).

Hmm, I believe that you'll need to boot from their floppy to get PXE  
to work.

The technical reason is that when most notebook boot, unless their  
Ethernet ports are on the motherboard, they have to initialize a PCI  
to PCMCIA bridge chip.

The question is, where is the code to do this?  Well, it kind of has  
to be done by the BIOS, which would then have to know how to control  
whatever PCMCIA Ethernet card you happen to have plugged into your  
PCMCIA slot.

There's the rub.  Unless your laptop BIOS specifically knows what  
bridge chip is being used, and what PCMCIA card is being used, most  
laptops without Ethernet wait for a kernel or other boot code (like  
Argon's PXE on Disk (kind of like an Etherboot floppy)), to do it.

Etherboot, unfortunately doesn't yet know how to deal with PCMCIA  
buses.  It's one of the things we hope to add, but so far, we do PCI  
and ISA buses mainly, which takes care of the majority of cases.   
We'd like to do PCMCIA and USB, and I'm sure we'll get there in time.  
Someone will decide they want it, and do it or fund it, just like PXE  
support.

> I'll highly appreciate any explanation on pxe.  The wiki pages are  
> good, but
> unfortenately they just missed the 2 points mentioned above.

I hope this is helpful.  I think my answers are correct.  I hope and  
expect that someone will correct me if I am mistaken.

> Another question I have (just out of curiousty); what ethercards  
> support pxe
> out the box nowadays all?  Or should they all get an eprom to  
> enable pxe?
> Same question for notebooks, which notebooks support pxe nowadays,  
> is that
> all or for example only the IBM thinkpad (that's the answer from  
> google) ;)

For an Ethernet card to support PXE out of the box, it needs a flash  
EEPROM.  This raises the cost, but not so much as in the old days.  I  
think I noticed an RTL8169 (Gigabit Card) that has PXE on it for not  
too much more than $20 the other day.

Now, if you're a bargain hunter, you can find old Intel EEPRO100s and  
3COM 3C905CTXM cards, which have PXE in flash memory, and will  
network boot by loading PXELINUX.0 from the SYSLINUX/PXELINUX/ 
ISOLINUX package.

Well, hopefully some of that will make sense, and help you on your  
way.  If you need more information, please post to the list.  We're  
here to help.

> TIA

You're welcome.

> Richard Bos
> Without a home the journey is endless

Marty

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

Re: [Etherboot-users] Problem with EXIT_IF_NO_OFFER (starting over and over)

[Igor M. <i.m...@sw...>]

Hello,

Booting from Etherboot floppy you already use the BIOS'es first boot device... 
Evidently, the situation is: BIOS ->first boot device --> Etherboot --> BIOS 
->first boot device --> Etherboot -->....

Try to put Etherboot code into ROM, all things should work then.

Regards,
Igor.

Mathieu Martin wrote:
> Hi,
> 
> I'm using etherboot on a floppy (version 5.4.1). I'm trying to set it so 
> that it tries to boot from the network first, and boot locally from the 
> hard drive in case it couldn't boot from network. According to the docs, 
> BOOT_SECOND=BOOT_DISK won't work with a regular bios (would work with 
> linuxbios only?). So I tried with the EXIT_IF_NO_OFFER flag set and 
> MAX_BOOTP_RETRIES set to 1 (I added a printf in core/main.c to make sure 
> the condition mas  met).. According to _my interpretation of_ the docs, 
> after MAX_BOOTP_RETRIES tries, etherboot should exit and  the bios 
> should skip to the next drive in it's configured boot order.. but it 
> actually loads the etherboot code from floppy again, and again, and 
> again. I tried with vmware and a real computer and got the same result.
> 
> Any idea?
> 
> Thanks
> 
> Mathieu Martin
> IMNET
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
> 

[Etherboot-users] Problem with EXIT_IF_NO_OFFER (starting over and over)

[Mathieu M. <ju...@ma...>]

Hi,

I'm using etherboot on a floppy (version 5.4.1). I'm trying to set it so 
that it tries to boot from the network first, and boot locally from the 
hard drive in case it couldn't boot from network. According to the docs, 
BOOT_SECOND=BOOT_DISK won't work with a regular bios (would work with 
linuxbios only?). So I tried with the EXIT_IF_NO_OFFER flag set and 
MAX_BOOTP_RETRIES set to 1 (I added a printf in core/main.c to make sure 
the condition mas  met).. According to _my interpretation of_ the docs, 
after MAX_BOOTP_RETRIES tries, etherboot should exit and  the bios 
should skip to the next drive in it's configured boot order.. but it 
actually loads the etherboot code from floppy again, and again, and 
again. I tried with vmware and a real computer and got the same result.

Any idea?

Thanks

Mathieu Martin
IMNET

[Etherboot-users] Re: Wireless boot, is it possible?

[<fel...@gm...>]

Hi,

>    I'm testing LTSP and getting great results using wired network...
>    Now I would like to start with Wireless Cards, I have one DWL-G520 
> but I dont know how to procede...
>    I cannot find the correct module to boot from floppy...
>    What can I do ?? Is there another cards with support??

There is support for serveral wirless network cards within etherboot. 
You should have a look at the sources, especially: drivers/net/prism2_plx.c

I had the "3com AirConnect 3CRWE777A" once working.  Booting the kernel 
over it was not a problem.  But you will have to use NX if you want to 
run a full X-Session over it...

LTSP has some packages for wirless booting, but the require the kernel 
and an initrd to be stored locally.
You might want to have a look at the wiki under wiki.ltsp.org.

Felix

[Etherboot-users] Wireless boot, is it possible?

[Daniel K. <da...@si...>]

Hello everybody,
    I'm testing LTSP and getting great results using wired network...
    Now I would like to start with Wireless Cards, I have one DWL-G520 
but I dont know how to procede...
    I cannot find the correct module to boot from floppy...
    What can I do ?? Is there another cards with support??

Thanks in advance...
Daniel K. P. Rezende
   

[Etherboot-users] Re: Via RNG xstore in Etherboot

[Robert H. <rob...@ya...>]

I've figured it out after paying closer attention to
the Via padlock programmers guide!

If I set bit 9 on CR4 using the following bit of
assembly (from the Linux kernel) it works. Something
to do with a dependency on the SSE instructions,
according to the docs.

static inline void set_in_cr4 (unsigned long mask)
{
    __asm__("movl %%cr4,%%eax\n\t"
        "orl %0,%%eax\n\t"
        "movl %%eax,%%cr4\n"
        : : "irg" (mask)
        :"ax");
}

and call with:

set_in_cr4( 0x0200 );

Hope the info is useful to someone!

Robert

> BTW the processor is a VIA Eden, with Nehemiah core
> (stepping 8), and the xstore call works once the
> Linux
> kernel is up and running - so I know that it can
> work...
> 
> --- Robert Hamilton <rob...@ya...>
> wrote:
> 
> > Hi all,
> > 
> > OK this question may be a bit obscure, but I hope
> > someone might have some insight as to what is
> going
> > on...
> > 
> > I am trying to call the Via RNG (xstore
> instruction)
> > from etherboot, and my platform resets every time
> I
> > call it.
> > 
> > I have copied the xstore asm() code from the
> > hw_random.c driver in Linux. I have made sure the
> > Via
> > MSR 0x110b is set up correctly. I've checked that
> > the
> > assembler and byte code looks OK (the same as the
> > hwrandom driver), but I still get the reset.
> > 
> > Do I have to set something else up on the
> processor,
> > or call xstore in a different way?
> > 
> > Thanks,
> > 
> > Robert
> > 
> > The following is the code I am using showing the
> MSR
> > initialization and the xstore call. Though the
> first
> > read of the MSR indicates that the RNG is enabled
> by
> > default anyway. It is pretty much a straight copy
> > from
> > hw_random.c.
> > 
> > #define MSR_VIA_RNG 0x110b
> > enum {
> >     VIA_STRFILT_CNT_SHIFT = 16,
> >     VIA_STRFILT_FAIL = (1 << 15),
> >     VIA_STRFILT_ENABLE = (1 << 14),
> >     VIA_RAWBITS_ENABLE = (1 << 13),
> >     VIA_RNG_ENABLE = (1 << 6),
> >     VIA_XSTORE_CNT_MASK = 0x0F,
> > 
> >     VIA_RNG_CHUNK_8 = 0x00, /* 64 rand bits, 64
> > stored
> > bits */
> >     VIA_RNG_CHUNK_4 = 0x01, /* 32 rand bits, 32
> > stored
> > bits */
> >     VIA_RNG_CHUNK_4_MASK = 0xFFFFFFFF,
> >     VIA_RNG_CHUNK_2 = 0x02, /* 16 rand bits, 32
> > stored
> > bits */
> >     VIA_RNG_CHUNK_2_MASK = 0xFFFF,
> >     VIA_RNG_CHUNK_1 = 0x03, /* 8 rand bits, 32
> > stored
> > bits */
> > 
> >     VIA_RNG_CHUNK_1_MASK = 0xFF,
> > };
> > 
> > #define rdmsr(msr,val1,val2) \
> >     __asm__ __volatile__("rdmsr" \
> >         : "=a" (val1), "=d" (val2) \
> >         : "c" (msr))
> > 
> > #define wrmsr(msr,val1,val2) \
> >     __asm__ __volatile__("wrmsr" \
> >         : /* no outputs */ \
> >         : "c" (msr), "a" (val1), "d" (val2))
> > 
> > static int via_RNGinit( void )
> > {
> >     u32 lo, hi, old_lo;
> > 
> >     printf( "VIA init\n" );
> >     rdmsr(MSR_VIA_RNG, lo, hi);
> >     printf( "lo = %#x, hi = %#x\n", lo, hi );
> > 
> >     old_lo = lo;
> >     lo &= ~(0x7f << VIA_STRFILT_CNT_SHIFT);
> >     lo &= ~VIA_XSTORE_CNT_MASK;
> >     lo |= (VIA_STRFILT_ENABLE | VIA_STRFILT_FAIL |
> > VIA_RAWBITS_ENABLE);
> >     lo |= VIA_RNG_ENABLE;
> >     lo |= ( 0x3 << 8 );
> > 
> >     if (lo != old_lo)
> >         wrmsr(MSR_VIA_RNG, lo, hi);
> > 
> >     rdmsr(MSR_VIA_RNG, lo, hi);
> >     printf( "lo = %#x, hi = %#x\n", lo, hi );
> >     if ((lo & VIA_RNG_ENABLE) == 0) {
> >         printf( "cannot enable VIA C3 RNG,
> > aborting\n");
> >         return -1;
> >     }
> > 
> >     printf( "Done!\n" );
> > 
> >     return 0;
> > }
> > 
> > static inline u32 xstore(u32 *addr, u32 edx_in)
> > {
> >     u32 eax_out;
> > 
> >     asm volatile (".byte 0x0f,0xa7,0xc0 /* xstore
> > %%edi (addr=%0) */"
> >         : "=a"(eax_out), "=m"(*addr)
> >         : "D"(addr), "d"(edx_in));
> > 
> >     return eax_out;
> > }
> > 
> > 
> > 
> > 		
> > __________________________________________ 
> > Yahoo! DSL – Something to write home about. 
> > Just $16.99/mo. or less. 
> > dsl.yahoo.com 
> > 
> > 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> http://mail.yahoo.com 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Etherboot-users] Re: Via RNG xstore in Etherboot

[Robert H. <rob...@ya...>]

BTW the processor is a VIA Eden, with Nehemiah core
(stepping 8), and the xstore call works once the Linux
kernel is up and running - so I know that it can
work...

--- Robert Hamilton <rob...@ya...>
wrote:

> Hi all,
> 
> OK this question may be a bit obscure, but I hope
> someone might have some insight as to what is going
> on...
> 
> I am trying to call the Via RNG (xstore instruction)
> from etherboot, and my platform resets every time I
> call it.
> 
> I have copied the xstore asm() code from the
> hw_random.c driver in Linux. I have made sure the
> Via
> MSR 0x110b is set up correctly. I've checked that
> the
> assembler and byte code looks OK (the same as the
> hwrandom driver), but I still get the reset.
> 
> Do I have to set something else up on the processor,
> or call xstore in a different way?
> 
> Thanks,
> 
> Robert
> 
> The following is the code I am using showing the MSR
> initialization and the xstore call. Though the first
> read of the MSR indicates that the RNG is enabled by
> default anyway. It is pretty much a straight copy
> from
> hw_random.c.
> 
> #define MSR_VIA_RNG 0x110b
> enum {
>     VIA_STRFILT_CNT_SHIFT = 16,
>     VIA_STRFILT_FAIL = (1 << 15),
>     VIA_STRFILT_ENABLE = (1 << 14),
>     VIA_RAWBITS_ENABLE = (1 << 13),
>     VIA_RNG_ENABLE = (1 << 6),
>     VIA_XSTORE_CNT_MASK = 0x0F,
> 
>     VIA_RNG_CHUNK_8 = 0x00, /* 64 rand bits, 64
> stored
> bits */
>     VIA_RNG_CHUNK_4 = 0x01, /* 32 rand bits, 32
> stored
> bits */
>     VIA_RNG_CHUNK_4_MASK = 0xFFFFFFFF,
>     VIA_RNG_CHUNK_2 = 0x02, /* 16 rand bits, 32
> stored
> bits */
>     VIA_RNG_CHUNK_2_MASK = 0xFFFF,
>     VIA_RNG_CHUNK_1 = 0x03, /* 8 rand bits, 32
> stored
> bits */
> 
>     VIA_RNG_CHUNK_1_MASK = 0xFF,
> };
> 
> #define rdmsr(msr,val1,val2) \
>     __asm__ __volatile__("rdmsr" \
>         : "=a" (val1), "=d" (val2) \
>         : "c" (msr))
> 
> #define wrmsr(msr,val1,val2) \
>     __asm__ __volatile__("wrmsr" \
>         : /* no outputs */ \
>         : "c" (msr), "a" (val1), "d" (val2))
> 
> static int via_RNGinit( void )
> {
>     u32 lo, hi, old_lo;
> 
>     printf( "VIA init\n" );
>     rdmsr(MSR_VIA_RNG, lo, hi);
>     printf( "lo = %#x, hi = %#x\n", lo, hi );
> 
>     old_lo = lo;
>     lo &= ~(0x7f << VIA_STRFILT_CNT_SHIFT);
>     lo &= ~VIA_XSTORE_CNT_MASK;
>     lo |= (VIA_STRFILT_ENABLE | VIA_STRFILT_FAIL |
> VIA_RAWBITS_ENABLE);
>     lo |= VIA_RNG_ENABLE;
>     lo |= ( 0x3 << 8 );
> 
>     if (lo != old_lo)
>         wrmsr(MSR_VIA_RNG, lo, hi);
> 
>     rdmsr(MSR_VIA_RNG, lo, hi);
>     printf( "lo = %#x, hi = %#x\n", lo, hi );
>     if ((lo & VIA_RNG_ENABLE) == 0) {
>         printf( "cannot enable VIA C3 RNG,
> aborting\n");
>         return -1;
>     }
> 
>     printf( "Done!\n" );
> 
>     return 0;
> }
> 
> static inline u32 xstore(u32 *addr, u32 edx_in)
> {
>     u32 eax_out;
> 
>     asm volatile (".byte 0x0f,0xa7,0xc0 /* xstore
> %%edi (addr=%0) */"
>         : "=a"(eax_out), "=m"(*addr)
>         : "D"(addr), "d"(edx_in));
> 
>     return eax_out;
> }
> 
> 
> 
> 		
> __________________________________________ 
> Yahoo! DSL – Something to write home about. 
> Just $16.99/mo. or less. 
> dsl.yahoo.com 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[Etherboot-users] Via RNG xstore in Etherboot

[Robert H. <rob...@ya...>]

Hi all,

OK this question may be a bit obscure, but I hope
someone might have some insight as to what is going
on...

I am trying to call the Via RNG (xstore instruction)
from etherboot, and my platform resets every time I
call it.

I have copied the xstore asm() code from the
hw_random.c driver in Linux. I have made sure the Via
MSR 0x110b is set up correctly. I've checked that the
assembler and byte code looks OK (the same as the
hwrandom driver), but I still get the reset.

Do I have to set something else up on the processor,
or call xstore in a different way?

Thanks,

Robert

The following is the code I am using showing the MSR
initialization and the xstore call. Though the first
read of the MSR indicates that the RNG is enabled by
default anyway. It is pretty much a straight copy from
hw_random.c.

#define MSR_VIA_RNG 0x110b
enum {
    VIA_STRFILT_CNT_SHIFT = 16,
    VIA_STRFILT_FAIL = (1 << 15),
    VIA_STRFILT_ENABLE = (1 << 14),
    VIA_RAWBITS_ENABLE = (1 << 13),
    VIA_RNG_ENABLE = (1 << 6),
    VIA_XSTORE_CNT_MASK = 0x0F,

    VIA_RNG_CHUNK_8 = 0x00, /* 64 rand bits, 64 stored
bits */
    VIA_RNG_CHUNK_4 = 0x01, /* 32 rand bits, 32 stored
bits */
    VIA_RNG_CHUNK_4_MASK = 0xFFFFFFFF,
    VIA_RNG_CHUNK_2 = 0x02, /* 16 rand bits, 32 stored
bits */
    VIA_RNG_CHUNK_2_MASK = 0xFFFF,
    VIA_RNG_CHUNK_1 = 0x03, /* 8 rand bits, 32 stored
bits */

    VIA_RNG_CHUNK_1_MASK = 0xFF,
};

#define rdmsr(msr,val1,val2) \
    __asm__ __volatile__("rdmsr" \
        : "=a" (val1), "=d" (val2) \
        : "c" (msr))

#define wrmsr(msr,val1,val2) \
    __asm__ __volatile__("wrmsr" \
        : /* no outputs */ \
        : "c" (msr), "a" (val1), "d" (val2))

static int via_RNGinit( void )
{
    u32 lo, hi, old_lo;

    printf( "VIA init\n" );
    rdmsr(MSR_VIA_RNG, lo, hi);
    printf( "lo = %#x, hi = %#x\n", lo, hi );

    old_lo = lo;
    lo &= ~(0x7f << VIA_STRFILT_CNT_SHIFT);
    lo &= ~VIA_XSTORE_CNT_MASK;
    lo |= (VIA_STRFILT_ENABLE | VIA_STRFILT_FAIL |
VIA_RAWBITS_ENABLE);
    lo |= VIA_RNG_ENABLE;
    lo |= ( 0x3 << 8 );

    if (lo != old_lo)
        wrmsr(MSR_VIA_RNG, lo, hi);

    rdmsr(MSR_VIA_RNG, lo, hi);
    printf( "lo = %#x, hi = %#x\n", lo, hi );
    if ((lo & VIA_RNG_ENABLE) == 0) {
        printf( "cannot enable VIA C3 RNG,
aborting\n");
        return -1;
    }

    printf( "Done!\n" );

    return 0;
}

static inline u32 xstore(u32 *addr, u32 edx_in)
{
    u32 eax_out;

    asm volatile (".byte 0x0f,0xa7,0xc0 /* xstore
%%edi (addr=%0) */"
        : "=a"(eax_out), "=m"(*addr)
        : "D"(addr), "d"(edx_in));

    return eax_out;
}



		
__________________________________________ 
Yahoo! DSL – Something to write home about. 
Just $16.99/mo. or less. 
dsl.yahoo.com 

[Etherboot-users] Re: etherboot loading etherboot images

[Robert H. <rob...@ya...>]

OK I've managed to get somewhere.
 
 The mkelf-img and mkelfImage was a digression.
 
 All I needed to do was build via_rhine.ebi/elf using the relocation address of 0x84000 (the original image was at 0x94000) and then download this as the image. So it doesn't try to overwrite running code (doh!).
 
 I need to make sure nothing else is broken from running at the 0x84000 version, but this solves the core of my problem.
 
 Sorry if my original question was dumb!

Robert Hamilton <rob...@ya...> wrote: Hello,
 
 Hope someone can help me out with the following...
  
 I am trying to load a new (debug) version of etherboot using an existing version of etherboot in rom.
 
 Platform info:
 linuxbios
 via-rhine network interface
 etherboot version 5.0.10
 latest mknbi (1.4.4)
 
 I have successfully created and used a rom image for the platform using my code-base, but now want a way to network upgrade etherboot (without flashing).
 
 I have tried a number of things to create an image I can use. I have built via-rhine.img, and used:
 
 mkelf-img --output=etherboot.nb via-rhine.img
 
 The etherboot.nb downloads successfully, and etherboot restarts, but not with the new version - instead the rom version runs again.
 
 I've also tried mkelfImage with via-rhine.elf as the kernel, but I get a "segment in reserved area" error message when the image tries to download.
 
 mkelfImage --kernel=via-rhine.elf ...
 
 I kind of  expected that result, but was getting desperate.
 
 I am guessing that this is a pretty standard thing that people do when developing etherboot, so hopefully someone has some insight into what I could be doing wrong.
 
 Many thanks,
 
 Robert
 
    

---------------------------------
 Yahoo! DSL Something to write home about. Just $16.99/mo. or less


			
---------------------------------
Yahoo! Photos
 Ring in the New Year with Photo Calendars. Add photos, events, holidays, whatever.

[Etherboot-users] etherboot loading etherboot images

[Robert H. <rob...@ya...>]

Hello,
 
 Hope someone can help me out with the following...
  
 I am trying to load a new (debug) version of etherboot using an existing version of etherboot in rom.
 
 Platform info:
 linuxbios
 via-rhine network interface
 etherboot version 5.0.10
 latest mknbi (1.4.4)
 
 I have successfully created and used a rom image for the platform using my code-base, but now want a way to network upgrade etherboot (without flashing).
 
 I have tried a number of things to create an image I can use. I have built via-rhine.img, and used:
 
 mkelf-img --output=etherboot.nb via-rhine.img
 
 The etherboot.nb downloads successfully, and etherboot restarts, but not with the new version - instead the rom version runs again.
 
 I've also tried mkelfImage with via-rhine.elf as the kernel, but I get a "segment in reserved area" error message when the image tries to download.
 
 mkelfImage --kernel=via-rhine.elf ...
 
 I kind of expected that result, but was getting desperate.
 
 I am guessing that this is a pretty standard thing that people do when developing etherboot, so hopefully someone has some insight into what I could be doing wrong.
 
 Many thanks,
 
 Robert
 
 
		
---------------------------------
 Yahoo! DSL Something to write home about. Just $16.99/mo. or less

RE: [Etherboot-users] Bios 32 error while booting

[Timothy L. <tim...@al...>]

cd etherboot-5.4/src
grep -r DCONFIG_PCI_DIRECT *

It returns:

arch/i386/Config:#      -DCONFIG_PCI_DIRECT
arch/i386/Config:#CFLAGS+=3D -DLINUXBIOS -DCONFIG_TSC_CURRTICKS
-DCONSOLE_SERIAL
-DCOMCONSOLE=3D0x3f8 -DCOMPRESERVE -DCONFIG_PCI_DIRECT -DELF_IMAGE
arch/i386/Config:# CFLAGS+=3D     -DCONFIG_PCI_DIRECT

uncomment one of the lines (remove the #) containing -DCONFIG_PCI_DIRECT
=20
grep is your friend...

Tim

> -----Original Message-----
> From: eth...@li...=20
> [mailto:eth...@li...] On=20
> Behalf Of Nico Oosthuizen
> Sent: Wednesday, January 04, 2006 7:52 AM
> To: eth...@li...
> Subject: Re: [Etherboot-users] Bios 32 error while booting
>=20
> Sorry. Don't know. I just download the zrom image from=20
> rom-o-matic and then use DOS tools to add it to my ROM BIOS=20
> and then flash it to the computer BIOS. Have not written it=20
> to an eeprom so can't help.
>=20
> Nico
>=20
> >  Hello,
> >          I had seen this option but where do i have to change this=20
> > option  while compiling from linux box.
> > =20
> >         Thanks for reply.
> > =20
> >  Regards,
> >  Vinu
> > >=20
> > >> Under the www.rom-o-matic.net Configure section there
> > is an
> > >> option that mentions your problem.
> > >>
> > >> CONFIG_PCI_DIRECT
> > >>  Define this for PCI BIOSes that do not implement
> > BIOS32
> > >>  or not correctly. Normally not needed. Only works for=20
> BIOSes of a=20
> > >> certain era.
> > >>
> > >>>                 I am using etherboot 5.2.6 and bulit =20
> .zrom image=20
> > >>> from my linux box and wrote it in 27C512 eeprom, i written 3=20
> > >>> eeproms and 2 of them are running on my 32bit
> > computers
> > >>> such as celeron 1.1ghz, PIII-1.13 but when i try to
> > run
> > >>> lan card with bootrom my my 64bit computer which is=20
> having Intel=20
> > >>> 915 Orignal motherboard and P4 3.0 ghz
> > 64bit
> > >>> processor it gives error on all of the cards error is
> > as
> > >>> follows
> > >>>
> > >>> Probing Pci nic...
> > >>>   Pci_init: no BIOS32 detected
> > >>>   Probing isa nic...
> > >>>   Probing PC disk
> > >>>   <Sleep>
> > >>>
> > >>>             sorry for bad english.
> > >>>             please reply it as soon as possible
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep=20
> through log files for problems?  Stop!  Download the new AJAX=20
> search engine that makes searching your log files as easy as=20
> surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>=20

**********************************************************************
This E-mail message (including attachments, if any) is intended for the use=
 of the individual or entity to which it is addressed and may contain infor=
mation that is privileged, proprietary, confidential and exempt from disclo=
sure. If you are not the intended recipient, you are notified that any diss=
emination, distribution or copying of this communication is strictly prohib=
ited. If you have received this communication in error, please notify the s=
ender and erase this E-mail message immediately.=20

Le present message electronique (y compris les pieces qui y sont annexees, =
le cas echeant) s'addresse au destinataire indique et peut contenir des ren=
seignements de caractere prive ou confidentiel. Si vous n'etes pas le desti=
nataire de ce document, nous vous signalons qu'il est strictement interdit =
de le diffuser, de le distribuer ou de le reproduire. Si ce message vous a =
ete transmis par erreur, veuillez en informer l'expediteur et le  supprimer=
 immediatement.

Re: [Etherboot-users] Bios 32 error while booting

[Nico O. <ni...@an...>]

Sorry. Don't know. I just download the zrom image from
rom-o-matic and then use DOS tools to add it to my ROM BIOS
and then flash it to the computer BIOS. Have not written it
to an eeprom so can't help.

Nico

>  Hello,
>          I had seen this option but where do i have to
> change this option 
>  while compiling from linux box.
>  
>         Thanks for reply.
>  
>  Regards,
>  Vinu
> > 
> >> Under the www.rom-o-matic.net Configure section there
> is an
> >> option that mentions your problem.
> >>
> >> CONFIG_PCI_DIRECT
> >>  Define this for PCI BIOSes that do not implement
> BIOS32
> >>  or not correctly. Normally not needed. Only works for
> >> BIOSes of a certain era.
> >>
> >>>                 I am using etherboot 5.2.6 and bulit
> >>>  .zrom image from my
> >>> linux box and wrote it in 27C512 eeprom, i written 3
> >>> eeproms and 2 of them are running on my 32bit
> computers
> >>> such as celeron 1.1ghz, PIII-1.13 but when i try to
> run
> >>> lan card with bootrom my my 64bit computer which is
> >>> having Intel 915 Orignal motherboard and P4 3.0 ghz
> 64bit
> >>> processor it gives error on all of the cards error is
> as
> >>> follows
> >>>
> >>> Probing Pci nic...
> >>>   Pci_init: no BIOS32 detected
> >>>   Probing isa nic...
> >>>   Probing PC disk
> >>>   <Sleep>
> >>>
> >>>             sorry for bad english.
> >>>             please reply it as soon as possible

Re: [Etherboot-users] Bios 32 error while booting

[Thinwala <thi...@gm...>]

 Hello,
         I had seen this option but where do i have to change this option 
 while compiling from linux box.
 
        Thanks for reply.
 
 Regards,
 Vinu
> ----- Original Message ----- 
> From: "Nico Oosthuizen" <ni...@an...>
> To: <eth...@li...>
> Sent: Wednesday, January 04, 2006 4:18 PM
> Subject: Re: [Etherboot-users] Bios 32 error while booting
> 
> 
>> Under the www.rom-o-matic.net Configure section there is an
>> option that mentions your problem.
>>
>> CONFIG_PCI_DIRECT
>>  Define this for PCI BIOSes that do not implement BIOS32
>>  or not correctly. Normally not needed. Only works for
>> BIOSes of a certain era.
>>
>>
>> On Wed, 4 Jan 2006 12:41:04 +0530
>> "Thinwala" <thi...@gm...> wrote:
>>> Hello friends,
>>>                 I am using etherboot 5.2.6 and bulit
>>>  .zrom image from my
>>> linux box and wrote it in 27C512 eeprom, i written 3
>>> eeproms and 2 of them are running on my 32bit computers
>>> such as celeron 1.1ghz, PIII-1.13 but when i try to run
>>> lan card with bootrom my my 64bit computer which is
>>> having Intel 915 Orignal motherboard and P4 3.0 ghz 64bit
>>> processor it gives error on all of the cards error is as
>>> follows
>>>
>>> Probing Pci nic...
>>>   Pci_init: no BIOS32 detected
>>>   Probing isa nic...
>>>   Probing PC disk
>>>   <Sleep>
>>>
>>>             sorry for bad english.
>>>             please reply it as soon as possible
>>
>>
>> -------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
>> files
>> for problems?  Stop!  Download the new AJAX search engine that makes
>> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>> _______________________________________________
>> Etherboot-users mailing list
>> Eth...@li...
>> https://lists.sourceforge.net/lists/listinfo/etherboot-users 
>

Re: [Etherboot-users] Bios 32 error while booting

[Nico O. <ni...@an...>]

Under the www.rom-o-matic.net Configure section there is an
option that mentions your problem.

CONFIG_PCI_DIRECT 
  Define this for PCI BIOSes that do not implement BIOS32
  or not correctly. Normally not needed. Only works for
BIOSes of a certain era.  


On Wed, 4 Jan 2006 12:41:04 +0530
 "Thinwala" <thi...@gm...> wrote:
> Hello friends,
>                 I am using etherboot 5.2.6 and bulit
>  .zrom image from my 
> linux box and wrote it in 27C512 eeprom, i written 3
> eeproms and 2 of them are running on my 32bit computers
> such as celeron 1.1ghz, PIII-1.13 but when i try to run
> lan card with bootrom my my 64bit computer which is
> having Intel 915 Orignal motherboard and P4 3.0 ghz 64bit
> processor it gives error on all of the cards error is as
> follows
> 
> Probing Pci nic...
>   Pci_init: no BIOS32 detected
>   Probing isa nic...
>   Probing PC disk
>   <Sleep>
> 
>             sorry for bad english.
>             please reply it as soon as possible

[Etherboot-users] Bios 32 error while booting

[Thinwala <thi...@gm...>]

Hello friends,
                I am using etherboot 5.2.6 and bulit  .zrom image from my 
linux box and wrote it in 27C512 eeprom, i written 3 eeproms and 2 of them 
are running on my 32bit computers such as celeron 1.1ghz, PIII-1.13 but when 
i try to run lan card with bootrom my my 64bit computer which is having 
Intel 915 Orignal motherboard and P4 3.0 ghz 64bit processor it gives error 
on all of the cards error is as follows

Probing Pci nic...
  Pci_init: no BIOS32 detected
  Probing isa nic...
  Probing PC disk
  <Sleep>

            sorry for bad english.
            please reply it as soon as possible









Vinu

[Etherboot-users] User Class

[Timo H. <Tim...@ik...>]

Hi,

I have tried to define user class option with rom-o-matic.net,
but it ends up to a compiler error, see below.

- Timo

make: Entering directory `/tmp/ROMSyPqTA'
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 
-DINCLUDE_RTL8139 -o bin/rtl8139.o -c drivers/net/rtl8139.c
drivers/net/rtl8139.c:544: warning: `used' attribute ignored
drivers/net/rtl8139.c:544: warning: `rtl8139_driver' defined but not used
gcc -E -Wp,-Wall -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC 
-DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 
-DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -Ui386 
-D ASSEMBLY arch/i386/core/start32.S | as  -o bin/start32.o
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/linuxbios.o -c firmware/linuxbios/linuxbios.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/bios.o -c arch/i386/firmware/pcbios/bios.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/console.o -c arch/i386/firmware/pcbios/console.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/memsizes.o -c arch/i386/firmware/pcbios/memsizes.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/basemem.o -c arch/i386/firmware/pcbios/basemem.c
arch/i386/firmware/pcbios/basemem.c:90: warning: static declaration for 
`_allot_base_memory' follows non-static
arch/i386/firmware/pcbios/basemem.c:160: warning: static declaration for 
`_forget_base_memory' follows non-static
arch/i386/firmware/pcbios/basemem.c:224: warning: static declaration for 
`free_unused_base_memory' follows non-static
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/hidemem.o -c arch/i386/firmware/pcbios/hidemem.c
gcc -E -Wp,-Wall -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC 
-DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 
-DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -Ui386 
-D ASSEMBLY arch/i386/firmware/pcbios/e820mangler.S | as  -o 
bin/e820mangler.o
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/realmode.o -c arch/i386/core/realmode.c
gcc -E -Wp,-Wall -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC 
-DBOOT_SECOND=BOOT_NOTHING -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 
-DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -Ui386 
-D ASSEMBLY arch/i386/core/realmode_asm.S | as  -o bin/realmode_asm.o
arch/i386/core/realmode_asm.S: Assembler messages:
arch/i386/core/realmode_asm.S:524: Warning: indirect ljmp without `*'
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/callbacks.o -c arch/i386/core/callbacks.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/pxe_callbacks.o -c arch/i386/core/pxe_callbacks.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/config.o -c core/config.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/main.o -c core/main.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/osloader.o -c core/osloader.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/nfs.o -c core/nfs.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/misc.o -c core/misc.c
core/misc.c:229:2: warning: #warning "gateA20_set should test to see if 
it is already set"
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/proto_slam.o -c core/proto_slam.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/proto_tftm.o -c core/proto_tftm.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/proto_http.o -c core/proto_http.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/floppy.o -c drivers/disk/floppy.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/proto_fsp.o -c core/proto_fsp.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/serial.o -c core/serial.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/timer.o -c core/timer.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/relocate.o -c core/relocate.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/heap.o -c core/heap.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/btext.o -c core/btext.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/pc_kbd.o -c core/pc_kbd.c
gcc -DASK_BOOT=0 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_NOTHING 
-DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DDHCP_CLIENT_ID_LEN= 
-DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"eunb\" 
-DDHCP_USER_CLASS_LEN=4 -DALLOW_ONLY_ENCAPSULATED -DCONGESTED 
-DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE 
-DELF_IMAGE -DPXE_IMAGE -DDOWNLOAD_PROTO_TFTP -DCOMCONSOLE=0x3F8 
-DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -Os 
-ffreestanding -Wall -W -Wno-format  -DPCBIOS -fstrength-reduce 
-fomit-frame-pointer -march=i386 -falign-jumps=1 -falign-loops=1 
-falign-functions=1 -mcpu=i386 -DVERSION_MAJOR=5 -DVERSION_MINOR=4 
-DVERSION=\"5.4.1\"  -I include -I arch/i386/include -DARCH=i386 -o 
bin/nic.o -c core/nic.c
core/nic.c:83: warning: initialization makes integer from pointer 
without a cast
core/nic.c:83: initializer element is not computable at load time
core/nic.c:83: (near initialization for `dhcpdiscover[24]')
core/nic.c:141: warning: initialization makes integer from pointer 
without a cast
core/nic.c:141: initializer element is not computable at load time
core/nic.c:141: (near initialization for `dhcprequest[36]')
make: *** [bin/nic.o] Error 1
make: Leaving directory `/tmp/ROMSyPqTA'

[Etherboot-users] Re: [Etherboot-developers] PXE-on-a-disk Intel EM64T reboot

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

Hi Josh,

[ I added Etherboot-Users to the list for wider distribution. ]

This looks like a great tool!

     ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html

A Universal PXE-on-a-disk floppy is a really neat thing.  I have read  
the thread on the SYSLINUX list, and see how it differs from:

     http://etherboot.anadex.de/

Which is another neat tool.

Thanks so much for doing this.  I would like to continue discussion  
of the outstanding issues that you mention, and maybe we can make it  
even better.

I think that there are a few people on the lists that may be able to  
help debug the EM64T issue.
Is there any chance of a hardware donation we can offer to someone  
who is willing to figure it out?  We can also offer a small cash  
reward (although Eternal Glory may be enough ;)

In any case, thanks very much for your work!  It's a nice tool, and I  
encourage you to keep polishing it.  It might be something to  
consider putting on the Etherboot web site.

Everyone who can, please test this tool, and send your findings to  
Etherboot-Users.

Thanks,

Marty

On Dec 30, 2005, at 11:16 PM, Josh Lehan wrote:
> Hello.  I've used Etherboot and SYSLINUX to create a "PXE-on-a- 
> disk" implementation: a floppy and CD image that is self-booting.   
> It does what a PXE BIOS would do, and is useful for computers that  
> don't have a built-in PXE BIOS.
>
> The disk is full of compiled Etherboot packages, one build for each  
> supported PCI driver.  Ethersel (part of SYSLINUX) autodetects the  
> PCI network card, and selects the proper Etherboot package to  
> load.  Works fine from there!
>
> Here's a simple webpage I made about it, and a download link:
>
> ftp://ftp.scyld.com/private/jlehan/pxe-on-a-disk.html
>
> The only problem is on the Intel EM64T (Intel's clone of AMD's 64- 
> bit architecture).  After the download of the Linux kernel  
> succeeds, something goes wrong, and instead of starting the kernel,  
> the machine reboots.  I'm guessing it's some kind of cleanup issue,  
> or something early on in the transition from 16-bit BIOS to 64-bit  
> kernel.
>
> I've tested on 32-bit machines, and AMD Opteron 64-bit machines,  
> and it works fine there.  It's also not related to any particular  
> brand of network card.
>
> On the Intel EM64T machines this problem happens on, I was able to  
> PXE boot just fine from the on-board BIOS, and also from the local  
> hard drive.  It worked fine from there, so know it's not a problem  
> with PXELINUX, or the booting process in general, on that  
> particular machine.
>
> This is all probably a moot point, since it'd be a fair guess that  
> all Intel EM64T machines ever made have a working PXE BIOS in them,  
> making this "PXE-on-a-disk" unnecessary, but thought I'd mention  
> it, in case anybody else has seen this.
>
> Thanks!
>
> Josh Lehan
> jl...@sc...

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