etherboot-users Mailing List for Etherboot (Page 8)
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-users — Discussion of user issues
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(46) |
Sep
(127) |
Oct
(116) |
Nov
(188) |
Dec
(109) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(105) |
Feb
(123) |
Mar
(115) |
Apr
(136) |
May
(196) |
Jun
(178) |
Jul
(179) |
Aug
(167) |
Sep
(164) |
Oct
(171) |
Nov
(179) |
Dec
(192) |
| 2002 |
Jan
(157) |
Feb
(132) |
Mar
(174) |
Apr
(128) |
May
(104) |
Jun
(139) |
Jul
(124) |
Aug
(165) |
Sep
(116) |
Oct
(100) |
Nov
(75) |
Dec
(113) |
| 2003 |
Jan
(99) |
Feb
(131) |
Mar
(166) |
Apr
(160) |
May
(51) |
Jun
(68) |
Jul
(189) |
Aug
(118) |
Sep
(91) |
Oct
(46) |
Nov
(74) |
Dec
(114) |
| 2004 |
Jan
(99) |
Feb
(139) |
Mar
(78) |
Apr
(149) |
May
(139) |
Jun
(130) |
Jul
(80) |
Aug
(123) |
Sep
(56) |
Oct
(40) |
Nov
(51) |
Dec
(36) |
| 2005 |
Jan
(96) |
Feb
(88) |
Mar
(89) |
Apr
(65) |
May
(64) |
Jun
(83) |
Jul
(52) |
Aug
(33) |
Sep
(41) |
Oct
(36) |
Nov
(34) |
Dec
(30) |
| 2006 |
Jan
(44) |
Feb
(28) |
Mar
(25) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
|
From: John L. <le...@oa...> - 2005-10-19 20:32:22
|
Timothy Legge wrote:
>> This is my first attempt at booting over a network. I am
>> trying to load an image across the network and I am receiving
>> the following message (using Etherboot v4.6.7):
>>
>> "error: not a tagged file
>> unable to load file"
>>
>> over and over and over and over and over and over and over .
>> . . and over again.
>>
>> I've run "mkelf-linux --rootdir=/tftpboot vmlinuz initrd.img
>>
>>> linux.nb"
>>
>> on my image and am still receiving the message. I created an
>> Etherboot
>> v5.4.1 boot disk and am able to load the image via PXE, so
>> I'm sure the vmlinuz and initrd.img files are correct.
>> Updating the onboard ROM isn't an option at this point; I'm
>> stuck with v4.6.7.
>
> No you are not. Simply use 4.6.7 to download a 5.4.1 version of
> etherboot first. If you have a 5.4.1 version of the rom file (zrom)
> then I believe it is simply mknbi-rom whateverrom.zrom >
> whateverrom.zrom.nbi.
>
> Then update your dhcpd.conf file to send whateverrom.zrom.nbi if the
> vendor string is etherboot 4 and the kernel if it is etherboot 5.x
>
> Tim
Thank you Tim. Your solution did indeed work.
Additional info:
Etherboot v4.6.7 does not report a vendor-class-identifier so I was able
to do the following:
if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
filename "my_image";
} else {
filename "eb-5.4.1.nb";
}
to first load the new Etherboot version than the image I wanted.
John
|
|
From: Roy W. <roy...@ya...> - 2005-10-19 18:03:37
|
well, could you show me how please Alexander ? that's all I've really been after for these past few months. I don't care much what dhcp / tftp server i use, i just want it to work. any chance you could zip up what you have and let me have it also ? then i can see it working and then take apart things for a look to see how it all works ? All the best, Roy. --- Alexander Heinz <mai...@gm...> wrote: > > If so then great, I was going to write something > but > > if you are keen to do it then excellent. I'd > gladly > > show you what I've got, but basically, I get > syslinux > > (which is supposed to include pxelinux and > memlinux) > > and use tftpd32 (which we know is pxelinux > compatible, > > this is guarenteed), and pxelinux starts to boot, > but > > menu.x32 and memlinux are fatally broken and there > are > > no sample scripts for "default" to allow booting a > DOS > > or other image. for pxelinux booting on windows > > environments, it's basically just a big mess. > > > > Let me know if you get it working, I'd appreciate > it > > so much, I really want this tech to work, and it's > so > > frustrating that it's all broken :o( > > pxelinux, memdisk and menu.c32 work great for me > (using an ISC DHCP > server and the tftp server by hpa). tftpd32 is the > only new part for me. > > Alex > ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: Alexander H. <mai...@gm...> - 2005-10-19 17:51:04
|
> If so then great, I was going to write something but > if you are keen to do it then excellent. I'd gladly > show you what I've got, but basically, I get syslinux > (which is supposed to include pxelinux and memlinux) > and use tftpd32 (which we know is pxelinux compatible, > this is guarenteed), and pxelinux starts to boot, but > menu.x32 and memlinux are fatally broken and there are > no sample scripts for "default" to allow booting a DOS > or other image. for pxelinux booting on windows > environments, it's basically just a big mess. > > Let me know if you get it working, I'd appreciate it > so much, I really want this tech to work, and it's so > frustrating that it's all broken :o( pxelinux, memdisk and menu.c32 work great for me (using an ISC DHCP server and the tftp server by hpa). tftpd32 is the only new part for me. Alex |
|
From: Alexander H. <mai...@gm...> - 2005-10-19 16:20:51
|
> In any case, please let us know how it goes. I'd really like to know > how you get this working, and add it to the wiki. I will download tftp32.exe today and write a corresponding article. Alex |
|
From: Marty C. <md...@et...> - 2005-10-19 15:50:50
|
On Oct 19, 2005, at 11:36 AM, Roy Wiseman wrote:
> ...
> ok, over to the syslinux user list with my questions.
> i'm a little scared of the answers i'll get ... :-s
Well, the author of SYSLINUX is on the Etherboot list, and they're
quite helpful there.
In any case, please let us know how it goes. I'd really like to know
how you get this working, and add it to the wiki.
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/
|
|
From: Roy W. <roy...@ya...> - 2005-10-19 15:36:42
|
> Sounds like you should join the SYSLINUX mailing > list and ask there. I never knew it existed ! I'll get on there right away thanks ... :) > > I did a google search for: > > tftpd32 pxe boot windows > > And found a lot of links that looks interesting. > > Here is one that seemed to have specific, practical, > information. > > http://pxes.sourceforge.net/howtos/ms_only_environment/ I've seen this before, but it doesn't help past the dhcp ... it helps *nothing* to actually make pxelinux rrun <doh!> ... ok, only 6-12 months trying to get this working ... seems crazy as this is such useful technology, why o why do those syslinux people have to write unintelligible documentation as if they were unix guys ... oh, it's cos they is unix guys right ? ;o) ("before starting with pxelinux please read the 40 pages of syslinux documentation, then reference the manual of some other thing, then look at another 20 pages of some other intelligible documentation. once you have done that please continue with this document" and I'm not kidding here either, this is *exactly* what they do. I cannot think of a better way to dissaude people from using your technology. alternatively : "here is a useful 5 page document with example scripts to get you up and running in 15-20 minutes" ... wow, now that would really be something ...) ok, over to the syslinux user list with my questions. i'm a little scared of the answers i'll get ... :-s ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com |
|
From: Marty C. <md...@et...> - 2005-10-19 15:04:27
|
On Oct 19, 2005, at 7:45 AM, Roy Wiseman wrote:
> Hello,
> ok, in summary, I have tftpd32.exe running on a
> Windows XP box. DHCP is turned off on my router so
> that tftpd32 controls the DHCP for the PXEBOOT. I
> point the DHCP in tftp32d to provide pxelinux.0 to pxe
> clients, and this works in that, I pxelinux.0 is found
> and boots.
I'm glad you got that far.
> The problem seems to be menu.c32 and getting memlinux
> to go for a new DOS image (or any other image). maybe.
Sounds like you should join the SYSLINUX mailing list and ask there.
I did a google search for:
tftpd32 pxe boot windows
And found a lot of links that looks interesting.
Here is one that seemed to have specific, practical, information.
http://pxes.sourceforge.net/howtos/ms_only_environment/
> ...
> Please, has someone got a working pxelinux boot system
> on windows xp with tftpd32.exe ? There is that page
> that describes how to setup tftpd32 that I was pointed
> to from this list but that only provides useful
> information up to the dhcp boot part. it does not help
> at all with pxelinux / default / menu.c32 / memlinux.
> i.e. it doesn't help to get a boot image to boot at
> all.
> please help ? somebody must have done this somewhere
> right ?
The SYSLINUX list is probably the first and best place for you to be
asking this kind of thing. If they say that Etherboot's PXE
implementation is somehow not working properly, then we could debug
things here, but so far, it looks PXELINUX specific.
> Once I can get a simple DOS image booting across the
> network, I can then start to learn all the in's and
> out's of pxelinux, but without any basic working
> system, I can't do anything (oh, for useful
> documentation with examples ! I'll gladly write it
> myself for Win32 if you guys can help me to get this
> working).
This seems like sound reasoning. One thing I would recommend is
trying to do this on a Linux system, which is much more well-
documented (and there are probably a lot more people who can help you
with it), then see if there is something different between the two
systems (tftpd vs. win32tftpd, dhcpd vs. the windows equivalent, etc.)
If you provide enough specific information for those of us who have a
windows machine around to duplicate your setup, some of us will be
willing to do this, I'm sure. (others may say they don't do windows,
but don't let that bother you :)
> Roy.
Thanks for writing. I encourage you to continue, and to rely on the
Etherboot and SYSLINUX mailing lists. I would be very interested in
getting a writeup when you get this working.
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/
|
|
From: Timothy L. <tim...@al...> - 2005-10-19 14:05:33
|
> This is my first attempt at booting over a network. I am=20 > trying to load an image across the network and I am receiving=20 > the following message (using Etherboot v4.6.7): >=20 > "error: not a tagged file > unable to load file" >=20 > over and over and over and over and over and over and over .=20 > . . and over again. >=20 > I've run "mkelf-linux --rootdir=3D/tftpboot vmlinuz initrd.img=20 > > linux.nb"=20 > on my image and am still receiving the message. I created an=20 > Etherboot > v5.4.1 boot disk and am able to load the image via PXE, so=20 > I'm sure the vmlinuz and initrd.img files are correct. =20 > Updating the onboard ROM isn't an option at this point; I'm=20 > stuck with v4.6.7. No you are not. Simply use 4.6.7 to download a 5.4.1 version of etherboot first. If you have a 5.4.1 version of the rom file (zrom) then I believe it is simply mknbi-rom whateverrom.zrom > whateverrom.zrom.nbi. Then update your dhcpd.conf file to send whateverrom.zrom.nbi if the vendor string is etherboot 4 and the kernel if it is etherboot 5.x Tim ********************************************************************** 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. |
|
From: Roy W. <roy...@ya...> - 2005-10-19 11:46:22
|
Hello, ok, in summary, I have tftpd32.exe running on a Windows XP box. DHCP is turned off on my router so that tftpd32 controls the DHCP for the PXEBOOT. I point the DHCP in tftp32d to provide pxelinux.0 to pxe clients, and this works in that, I pxelinux.0 is found and boots. The problem seems to be menu.c32 and getting memlinux to go for a new DOS image (or any other image). maybe. I'm using the default syslinux distribution for win32. end result, big failure. I've then used Cristian's great default script (note, pxelinux only talk in abstract terms, terrible documentation, no examples), so I've used Cristian's script to make my pxelinux.cfg folder. end result, failure. Cristian then gave me his menu.c32 and memlinux (as again, pxelinux provide *no* examples of this in Windows and these are not compiled for win32 in the win32 distribution. Surely a great way to cause people waste time for months is to release incomplete distributions for an environment that are fundamentally broken, which this is). end result, this failed also, with no difference between this attempt and previous attempt. Please, has someone got a working pxelinux boot system on windows xp with tftpd32.exe ? There is that page that describes how to setup tftpd32 that I was pointed to from this list but that only provides useful information up to the dhcp boot part. it does not help at all with pxelinux / default / menu.c32 / memlinux. i.e. it doesn't help to get a boot image to boot at all. please help ? somebody must have done this somewhere right ? Once I can get a simple DOS image booting across the network, I can then start to learn all the in's and out's of pxelinux, but without any basic working system, I can't do anything (oh, for useful documentation with examples ! I'll gladly write it myself for Win32 if you guys can help me to get this working). Thanks, Roy. > > pxelinux.cfg/default file > > > > <file> > > default menu.c32 > > prompt 0 > > timeout 0 > > > > menu title pxelinux boot menu > > > > label DOS > > menu label DOS > > kernel ::/memdisk > > append initrd=::/dosboot.img > > </file> > > > > > > > > Output from PXE Client : > > > > Found PXENV+ structure > > PXE API version is 0063 > > Old PXE API detected, using PXENV+ structure > > UNDI data segment at: 9880 > > UNDI data segment size: 5520 > > UNDI code segment at: 9DD2 > > UNDI code segment size: 1BD0 > > PXENV entry point found (we hope) at 9140:0092 > > My IP address seems to be 0A000032 10.0.0.50 > > ip=10.0.0.50:10.0.0.10:10.0.0.1:255.255.255.0 > > TFTP prefix: > > Trying to load: pxelinux.cfg/01-00-00-0e-b0-a0-70 > > Trying to load: pxelinux.cfg/0A000032 > > Trying to load: pxelinux.cfg/0A00003 > > Trying to load: pxelinux.cfg/0A0000 > > Trying to load: pxelinux.cfg/0A000 > > Trying to load: pxelinux.cfg/0A0 > > Trying to load: pxelinux.cfg/0A > > Trying to load: pxelinux.cfg/0 > > Trying to load: pxelinux.cfg/default > > Could not find kernel image: linux > > boot: ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com |
|
From: John L. <le...@oa...> - 2005-10-18 22:37:42
|
Hi all, This is my first attempt at booting over a network. I am trying to load an image across the network and I am receiving the following message (using Etherboot v4.6.7): "error: not a tagged file unable to load file" over and over and over and over and over and over and over . . . and over again. I've run "mkelf-linux --rootdir=/tftpboot vmlinuz initrd.img > linux.nb" on my image and am still receiving the message. I created an Etherboot v5.4.1 boot disk and am able to load the image via PXE, so I'm sure the vmlinuz and initrd.img files are correct. Updating the onboard ROM isn't an option at this point; I'm stuck with v4.6.7. Any help would be appreciated. Also, if anyone has a confirmed NBI file, I'd be happy to try that out too. Thanks! John Lee |
|
From: Roy W. <roy...@ya...> - 2005-10-15 10:35:47
|
Hello Cristian, I wanted to try and get this sorted out once and for all, I think I'm very close, so I'm going to go through things simply and carefully, hopefully you can see where I'm going wrong ? > To boot a DOS image (let's say a floppy image) you > can get away with PXE booting and pxelinux from > Syslinux (syslinux.zytor.com). PXE booting > loads pxelinux.0 that cand boot, via memdisk, a > DOS floppy. This I still cannot do. The documentation is difficult but I'm close I think ... > To boot a DOS image (let's say a floppy image) you > can get away with PXE booting and pxelinux from > Syslinux (syslinux.zytor.com). PXE booting loads > pxelinux.0 that cand boot, via memdisk, a > DOS floppy. ok, that's clear, very clear, but *how* to implement it is not completely clear to me. I'll explain : Ok, as you say the 2 core files (along with a working tftp server and dhcp server) to allow a boot are > /tftpboot/pxelinux.0 > /tftpboot/pxelinux.cfg/default That's fine, and I see a boot happening across the network but it cannot boot anything So on my Windows box, I have the 2 files : C:\tftpboot\pxelinux.0 C:\tftpboot\pxelinux.cfg\default and I am running tftpd32.exe allowing the pxe booting to happen. I also have a simple dos 6.22 boot image C:\tftpboot\dosboot.img Now, you said the following : > Files layout (on the tftp server, serves files from /tftpboot, > stripping the directory prefix) : > /tftpboot/pxelinux.0 > /tftpboot/pxelinux.cfg/default > /tftpboot/menu.c32 > /tftpboot/freedos/odinBig.img Stripping your pxelinux.cfg/default file just for the dos boot, I get <file> default menu.c32 prompt 0 timeout 0 menu title pxelinux boot menu label DOS menu label DOS kernel ::/memdisk append initrd=::/dosboot.img </file> Now, the missing bits ... > menu.c32 is from Syslinux (please read the > README.menu file to see how you can use it). I read that, it's referencing all sorts of linux stuff and doesn't seem to say how to build a menu.c32. there is no default menu.c32 in the syslinux distribution, could you let me see what is in your menu.c32 and I will use that as an example to work from ? Here is the output that I get when I network boot: Found PXENV+ structure PXE API version is 0063 Old PXE API detected, using PXENV+ structure UNDI data segment at: 9880 UNDI data segment size: 5520 UNDI code segment at: 9DD2 UNDI code segment size: 1BD0 PXENV entry point found (we hope) at 9140:0092 My IP address seems to be 0A000032 10.0.0.50 ip=10.0.0.50:10.0.0.10:10.0.0.1:255.255.255.0 TFTP prefix: Trying to load: pxelinux.cfg/01-00-00-0e-b0-a0-70 Trying to load: pxelinux.cfg/0A000032 Trying to load: pxelinux.cfg/0A00003 Trying to load: pxelinux.cfg/0A0000 Trying to load: pxelinux.cfg/0A000 Trying to load: pxelinux.cfg/0A0 Trying to load: pxelinux.cfg/0A Trying to load: pxelinux.cfg/0 Trying to load: pxelinux.cfg/default Could not find kernel image: linux boot: ok, end result of the above, my main problems are : - something is missing, but what ? is memlinux working ??? is the menu.c32 essential, and can I see a very basic menu.c32 please ??? > When booting and Pxelinux is loaded, I get to > this menu: > http://img355.imageshack.us/my.php?image=pxelinux6cu.png That looks great, and if I ever see something like that then I will be very happy ! > I know the lack of precise documentation can be > sometimes disconcerting, but you'll get there :). Well, hopefully today with some luck ! :) :) :) (I tell you, that online documentation is hell, this should be 5 minutes to setup, not 5 months ! You've given me great descriptions that have got me this far, but that huge confusing online documentation is like being forced to eat nails for a few hours ... examples examples examples, that's all that they really need to do, but instead of good clear examples, they've written the documentation like blueprints for the Space Shuttle ... inscrutable !) Cheers!, Roy. ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com |
|
From: Carl K. <ca...@pe...> - 2005-10-13 07:22:04
|
Any chance of this pci card being Eitherbooted? root@dhcp44:~# lspci -s :0e 0000:00:0e.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface root@dhcp44:~# lspci -s :0e -n 0000:00:0e.0 0280: 104c:9066 ^Carl K |
|
From: Carl K. <ca...@pe...> - 2005-10-12 15:34:57
|
> here. When loading the machine, I did not see any output messages out > of the ordinary pertaining to the network card or its attempts to boot Long shot: hit ^S for Setup (like every second between power on and some message tha tells you all is lost). ^S is what my Intel card uses. ^C |
|
From: Timothy L. <tim...@al...> - 2005-10-12 12:13:30
|
> Today my professor at college gave to me a bundle of EISA=20 > Intel Pro/10mbit Ethernet Cards, as he became aware of my=20 > interest in diskless machines and centralized operating=20 > system images. (Intel FA82595TX chip). On the card is a 32=20 > pin socket containing a ROM with an Intel sticker that has=20 > "Intel (C) 1994 352226-001" on it. I assume this is the boot rom. That would be a boot rom but it is difficult to say what type it might be. I forget when Intel introduced PXE. > boot from here. When loading the machine, I did not see any=20 > output messages out of the ordinary pertaining to the network=20 > card or its attempts to boot using the ROM. All i ever=20 > received was an "invalid boot disk, press enter to continue." There may be an option in the bios to enable boot from network, but more likely you need to use an Intel utility to enable the boot rom on the card. It may be disabled by default. The invalid boot disk may simply be the bios not finding any thing to boot (no hard drive and os perhaps). Since the network boot is not starting it will try to find a hard disk or floppy. > I accepted this, as the network card was not connected to any=20 > other network interface, such as one with BOOTP or TFTP bound=20 > to it. However, just to see if anything was going out the=20 > wire when the machine booted, i ran a protocol analyzer. If I understand correctly you did not have the card connected to a RJ45 cable. If this is the case it may not attempt to use the network boot at all (I am unsure of this though). > How does a computer that has a BIOS without a "boot from=20 > network" option know how to boot from the network? The boot=20 > rom on the Intel Pro/10 is from 1994, and I dont recall=20 > seeing "boot from network" in any 586 or lower BIOS i have=20 > ever worked with. Did these older BIOSES require a boot=20 > floppy to pass on booting to the old-style boot rom? Typically you need to enable the rom using an Intel configuration utility for that card. > option in order to pass booting to the boot rom, then why is=20 > it that the protocol analyzer showed no traffic originating=20 > from the Intel Pro/10? Should there have not been at least a=20 > broadcast ARP or BOOTP messages originating from it? Not if the rom is disabled > Or, should I have installed a BOOTP server first? Would the=20 > BOOTP server initiate a proper conversation with the Intel=20 > Pro/10 card, or is it up to the boot rom enabled card to=20 > initiate a conversation with the server? I have not read the=20 > RFC on BOOTP yet, sorry about that one. If the rom is enabled, a packet sniffer like Ethereal should show the dhcp broadcast. Tim ********************************************************************** 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. |
|
From: Carl K. <ca...@pe...> - 2005-10-11 03:29:45
|
It would be really nice if I could just hit http://rom-o-matic.net/5.4.1/ and enter 8086:1229 somewhere instead of going blind trying to find it in the list. root@cp600:/home/carl # lspci -s 0d 0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro 100] (rev 08) root@cp600:/home/carl # lspci -s 0d -n 0000:00:0d.0 0200: 8086:1229 (rev 08) ^C |
|
From: Carl K. <ca...@pe...> - 2005-10-11 03:25:00
|
Using the defaults, I was able to create: eb-5.4.1-rtl8139.zdsk so good. ^C |
|
From: Carl K. <ca...@pe...> - 2005-10-11 03:08:04
|
rtl8139.zdsk Build Failed Build failed. Status = 2. Following is the output from make: make: Entering directory `/tmp/ROM0hn6ZK' gcc -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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 core/main.c: In function `loadkernel': core/main.c:483: warning: implicit declaration of function `dns_resolver' core/main.c:483: warning: assignment makes pointer from integer without a cast gcc -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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 core/nfs.c: In function `await_rpc': core/nfs.c:63: warning: unused parameter `ptype' core/nfs.c: In function `rpc_lookup': core/nfs.c:111: warning: passing arg 1 of `await_reply' from incompatible pointer type core/nfs.c: In function `nfs_mount': core/nfs.c:227: warning: passing arg 1 of `await_reply' from incompatible pointer type core/nfs.c: In function `nfs_umountall': core/nfs.c:281: warning: passing arg 1 of `await_reply' from incompatible pointer type core/nfs.c: In function `nfs_readlink': core/nfs.c:322: warning: passing arg 1 of `await_reply' from incompatible pointer type core/nfs.c:299: warning: unused parameter `fh' core/nfs.c: In function `nfs_lookup': core/nfs.c:393: warning: passing arg 1 of `await_reply' from incompatible pointer type core/nfs.c: In function `nfs_read': core/nfs.c:455: warning: passing arg 1 of `await_reply' from incompatible pointer type gcc -DASK_BOOT=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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=3 -DBOOT_FIRST=BOOT_NIC -DBOOT_SECOND=BOOT_DISK -DBOOT_THIRD=BOOT_NOTHING -DBOOT_INDEX=0 -DSIZEINDICATOR -DDHCP_CLIENT_ID=\"Realtek\" -DDHCP_CLIENT_ID_LEN= -DDHCP_CLIENT_ID_TYPE= -DDHCP_USER_CLASS=\"floppy\" -DDHCP_USER_CLASS_LEN= -DALLOW_ONLY_ENCAPSULATED -DDEFAULT_BOOTFILE=\"tftp:///tftpboot/kernel\" -DCONGESTED -DBACKOFF_LIMIT=7 -DTIMEOUT=180 -DTRY_FLOPPY_FIRST=0 -DTAGGED_IMAGE -DELF_IMAGE -DPXE_IMAGE -DDNS_RESOLVER -DDOWNLOAD_PROTO_TFTP -DDOWNLOAD_PROTO_NFS -DCOMCONSOLE=0x3F8 -DCONSPEED=9600 -DCOMPARM=0x03 -DPXE_EXPORT -DCONFIG_PCI -DBUILD_ID=\"Oct10-05\" -Os -ffreestanding -Wall -W -Wno-format -DPCBIOS -DPXELOADER_KEEP_ALL -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:79: parse error before ',' token core/nic.c:79: warning: initialization makes integer from pointer without a cast core/nic.c:79: initializer element is not computable at load time core/nic.c:79: (near initialization for `dhcpdiscover[24]') core/nic.c:83: parse error before ',' token 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[26]') core/nic.c:137: parse error before ',' token core/nic.c:137: warning: initialization makes integer from pointer without a cast core/nic.c:137: initializer element is not computable at load time core/nic.c:137: (near initialization for `dhcprequest[36]') core/nic.c:141: parse error before ',' token 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[38]') make: *** [bin/nic.o] Error 1 make: Leaving directory `/tmp/ROM0hn6ZK' Please let us know that this happened. I picked a bunch of custom options, kinda playing around. "NFS support? I might try that sometime..." ^Carl |
|
From: Timothy L. <tl...@ro...> - 2005-10-06 00:56:31
|
Timothy Legge wrote: > It looks like there have been some updates to the linux version of the > driver that include mac versions. It looks like I will need to pull > that in. Give me a few days. I did a diff between the linux 2.4.21 driver and a current 2.6.13 driver and the result is not pretty. The diff is 3 times the size of the driver. ;-) It will take a bit to separate what exactly is needed. Since I don't have a copy of your card, it will take more time. Feel free to contact me off list if you can provide a sample. Tim > > Tim > > Alexander Martins Silva wrote: > >> Hi Tim, >> >> I cant to give you this information now because im not at >> work, but the cards have the same chip realtek. One is a Planet ENW >> 9605 and the second is Encore *ENL832-GB/ENLGA-1320. >> >> Alexander. >> * >> Timothy Legge wrote: >> >>> Alexander Martins Silva wrote: >>> >>>> I've got a serious problem with network cards with the Realtk >>>> 8169s/8101 chipset. With two differents cards I couldnt etherboot a >>>> client machine, with the same error message: "Searching server >>>> (DHCP)...No IP Address", but works when I use a machine with a >>>> different network card (nvidia2). What's happening? The r8169 drive >>>> dont work for the rtl8169? Someone got the same problem? >>>> >>>> Thanks is advance, >>> >>> >>> >>> >>> Hi >>> >>> Please provide the PCI ids for the card. >>> >>> Tim >>> >>> >>> ------------------------------------------------------- >>> This SF.Net email is sponsored by: >>> Power Architecture Resource Center: Free content, downloads, >>> discussions, >>> and more. http://solutions.newsforge.com/ibmarch.tmpl >>> _______________________________________________ >>> Etherboot-users mailing list >>> Eth...@li... >>> https://lists.sourceforge.net/lists/listinfo/etherboot-users >>> >> >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: >> Power Architecture Resource Center: Free content, downloads, discussions, >> and more. http://solutions.newsforge.com/ibmarch.tmpl >> _______________________________________________ >> Etherboot-users mailing list >> Eth...@li... >> https://lists.sourceforge.net/lists/listinfo/etherboot-users >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Etherboot-users mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-users > |
|
From: Timothy L. <tl...@ro...> - 2005-10-05 10:18:17
|
It looks like there have been some updates to the linux version of the driver that include mac versions. It looks like I will need to pull that in. Give me a few days. Tim Alexander Martins Silva wrote: > Hi Tim, > > I cant to give you this information now because im not at work, > but the cards have the same chip realtek. One is a Planet ENW 9605 and > the second is Encore *ENL832-GB/ENLGA-1320. > > Alexander. > * > Timothy Legge wrote: > >> Alexander Martins Silva wrote: >> >>> I've got a serious problem with network cards with the Realtk >>> 8169s/8101 chipset. With two differents cards I couldnt etherboot a >>> client machine, with the same error message: "Searching server >>> (DHCP)...No IP Address", but works when I use a machine with a >>> different network card (nvidia2). What's happening? The r8169 drive >>> dont work for the rtl8169? Someone got the same problem? >>> >>> Thanks is advance, >> >> >> >> Hi >> >> Please provide the PCI ids for the card. >> >> Tim >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by: >> Power Architecture Resource Center: Free content, downloads, discussions, >> and more. http://solutions.newsforge.com/ibmarch.tmpl >> _______________________________________________ >> Etherboot-users mailing list >> Eth...@li... >> https://lists.sourceforge.net/lists/listinfo/etherboot-users >> > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: > Power Architecture Resource Center: Free content, downloads, discussions, > and more. http://solutions.newsforge.com/ibmarch.tmpl > _______________________________________________ > Etherboot-users mailing list > Eth...@li... > https://lists.sourceforge.net/lists/listinfo/etherboot-users > |
|
From: James S. <js...@cp...> - 2005-10-05 04:39:05
|
Hello, please note that I am not using any images made by etherboot or rom-o-matic. I am, however, using a boot rom from Intel, and i have no practical experience with these things. Anyway, here we go: Today my professor at college gave to me a bundle of EISA Intel Pro/10mbit Ethernet Cards, as he became aware of my interest in diskless machines and centralized operating system images. (Intel FA82595TX chip). On the card is a 32 pin socket containing a ROM with an Intel sticker that has "Intel (C) 1994 352226-001" on it. I assume this is the boot rom. When i got home from school, I plugged the NIC into an ATX motherboard with an AWARD 686 PCI PNP bios. The motherboard also contains slots for EISA. Looking through the BIOS config, I did not notice any option for "Boot from network card." I decided to do a cold boot, hoping that the ROM would be detected, and that the bootsrap would attempt to boot from here. When loading the machine, I did not see any output messages out of the ordinary pertaining to the network card or its attempts to boot using the ROM. All i ever received was an "invalid boot disk, press enter to continue." I accepted this, as the network card was not connected to any other network interface, such as one with BOOTP or TFTP bound to it. However, just to see if anything was going out the wire when the machine booted, i ran a protocol analyzer. The only data going out the wire was NOT coming from the Intel Pro/10 - it was coming from the other computer and included broadcast ARP and IP traffic once the link came up. The Intel Pro/10 did not even respond to the broadcast arp. Keep in mind, the computer running the protocol analyzer did not have a boot rom in it (i dont think this matters). Anyway, my questions are as follows: How does a computer that has a BIOS without a "boot from network" option know how to boot from the network? The boot rom on the Intel Pro/10 is from 1994, and I dont recall seeing "boot from network" in any 586 or lower BIOS i have ever worked with. Did these older BIOSES require a boot floppy to pass on booting to the old-style boot rom? If using a boot floppy to pass off the boot sequence is not the issue, or if my BIOS doesnt require 'boot from network' option in order to pass booting to the boot rom, then why is it that the protocol analyzer showed no traffic originating from the Intel Pro/10? Should there have not been at least a broadcast ARP or BOOTP messages originating from it? Or, should I have installed a BOOTP server first? Would the BOOTP server initiate a proper conversation with the Intel Pro/10 card, or is it up to the boot rom enabled card to initiate a conversation with the server? I have not read the RFC on BOOTP yet, sorry about that one. Anyway, if there is anyone with general information that can help me clarify things here, please let me know. Thanks! |
|
From: Alexander M. S. <ale...@uo...> - 2005-10-04 10:59:46
|
Hi Tim,
I cant to give you this information now because im not at
work, but the cards have the same chip realtek. One is a Planet ENW 9605
and the second is Encore *ENL832-GB/ENLGA-1320.
Alexander.
*
Timothy Legge wrote:
> Alexander Martins Silva wrote:
>
>> I've got a serious problem with network cards with the Realtk
>> 8169s/8101 chipset. With two differents cards I couldnt etherboot a
>> client machine, with the same error message: "Searching server
>> (DHCP)...No IP Address", but works when I use a machine with a
>> different network card (nvidia2). What's happening? The r8169 drive
>> dont work for the rtl8169? Someone got the same problem?
>>
>> Thanks is advance,
>
>
> Hi
>
> Please provide the PCI ids for the card.
>
> Tim
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Power Architecture Resource Center: Free content, downloads, discussions,
> and more. http://solutions.newsforge.com/ibmarch.tmpl
> _______________________________________________
> Etherboot-users mailing list
> Eth...@li...
> https://lists.sourceforge.net/lists/listinfo/etherboot-users
>
|
|
From: Timothy L. <tl...@ro...> - 2005-10-03 22:47:27
|
Alexander Martins Silva wrote: > I've got a serious problem with network cards with the Realtk > 8169s/8101 chipset. With two differents cards I couldnt etherboot a > client machine, with the same error message: "Searching server > (DHCP)...No IP Address", but works when I use a machine with a different > network card (nvidia2). What's happening? The r8169 drive dont work for > the rtl8169? Someone got the same problem? > > Thanks is advance, Hi Please provide the PCI ids for the card. Tim |
|
From: Alexander M. S. <ale...@uo...> - 2005-10-03 22:21:45
|
Hi,
I've got a serious problem with network cards with the Realtk
8169s/8101 chipset. With two differents cards I couldnt etherboot a
client machine, with the same error message: "Searching server
(DHCP)...No IP Address", but works when I use a machine with a different
network card (nvidia2). What's happening? The r8169 drive dont work for
the rtl8169? Someone got the same problem?
Thanks is advance,
Alexander.
|
|
From: Jacky <jac...@gm...> - 2005-10-02 17:45:34
|
hi, I try using thinstation 2.2beta6 and I use PC HP Netsever E30 Pentium 166 Mhz, Ram 128, Vga S3-Trio 1 MB, Nic 3c905-tx with bootrom and etherboot 5.4.1. when booting thinstation stop and no proccess. Issuing RESET: mknbi-1.4.4/first32.c (ELF) (GPL) Top of ramdisk is 0X006C9000 You passed undefined mode number. Press <RETURN> to see video modes available, ,<SPACE> to continue or wait 3= 0 secs Uncompressing Linux...Ok, booting the kernel and then stop no proccess.. this is my build.conf ################################################ ### --- Thinstation Build Config --- ### ################################################ # # This is Thinstation's basic setup file. In this file you decide which # hardware, programs and features to be included in the Thinstation boot image # generated by running "./build". # # You can customize/limit the possibilities in the thinstation.conf files later. # # Anything after a "#" is a comment. You activate "things" by removing the = # # and remove "things" by putting a # in front of them. # # First we define which modules to include. Modules are hardware drivers. # NEVER include more than necessary - the more modules the longer boot time ################################################ ### --- Modules to include in boot image --- ### ################################################ # Any modules may be added as "module" or "module_pkg". # If defined as a "module" the driver is included in the boot image. # If defined as a "module_pkg" the driver is added from outside the image. # Normally use "module", and only "module_pkg" if you want to dynamically load modules # Note: If you create a module_pkg network driver, and depend to load it of= f a tftp # server, this won't work as it won't have a network driver to get the module_pkg # in the first place. #!Hardware #!!System #!!!Bus Modules #module pcm # PCMCIA Cards module apm # Advanced power management module serial # Serial Device Support #!!!AGP Modules module agpgart # AGP bus module for use with AGP video cards #module ali-agp # ALI chipset support #module amd64-agp # AMD Opteron/Athlon64 on-CPU GART support #module amd-k7-agp # AMD Irongate, 761, and 762 chipset support #module ati-agp # ATI chipset support #module efficeon-agp # Transmeta Efficeon support #module intel-agp # Intel 440LX/BX/GX, I8xx and E7x05 chipset support #module nvidia-agp # NVIDIA nForce/nForce2 chipset support #module sis-agp # SiS chipset support #module via-agp # VIA chipset support #!!!PCMCIA/CardBus bridges # Only include what you really need! #module yenta_socket # CardBus card and (Yenta) bridge support (Very common= ) #module i82365 # Intel i82365 compatible ISA-bus bridge support #module tcic # Databook TCIC host bridge support (old systems) # --- Network cards modules # Have as few as possible #!!Network #!!!Ethernet 10-100 Mbit Modules #module 3c501 # 3c501 "EtherLink" support #module 3c503 # 3c503 "EtherLink II" support #module 3c505 # 3c505 "EtherLink Plus" support #module 3c507 # 3c507 "EtherLink 16" support module 3c509 # 3c509/3c529 (MCA)/3c579 "EtherLink III" support #module 3c515 # 3c515 ISA "Fast EtherLink" #module 3c59x # 3c590/3c900 series (592/595/597) "Vortex/Boomerang" support module 8139too # RealTek RTL-8139 PCI Fast Ethernet Adapter support # # VERY common in no-name network cards. Covers also 8129 #module 8139cp # RealTek RTL-8139 C+ PCI Fast Ethernet Adapter support #module ac3200 # Ansel Communications EISA 3200 support #module amd8111e # AMD 8111 (new PCI lance) support #module at1700 # AT1700/1720 support module b44 # Broadcom 4400 ethernet support #module cs89x0 # CS89x0 support #module de4x5 # Generic DECchip & DIGITAL EtherWORKS PCI/EISA #module de2104x # Early DECchip Tulip (dc2104x) PCI support #module depca # DEPCA, DE10x, DE200, DE201, DE202, DE422 support #module dgrs # Digi Intl. RightSwitch SE-X support #module dmfe # Davicom DM910x/DM980x support #module hp100 # HP 10/100VG PCLAN (ISA, EISA, PCI) support #module e100 # EtherExpressPro/100 support (e100, Alternate Intel driver) #module e2100 # Cabletron E21xx support module eepro # EtherExpressPro support/EtherExpress 10 (i82595) support module eepro100 # EtherExpressPro/100 support (eepro100, original Becker driver) #module eexpress # EtherExpress 16 support #module epic100 # SMC EtherPower II #module eth16i # ICL EtherTeam 16i/32 support #module ewrk3 # EtherWORKS 3 (DE203, DE204, DE205) support #module fealnx # Myson MTD-8xx PCI Ethernet support #module forcedeth # nForce Ethernet support #module hp-plus # HP PCLAN+ (27247B and 27252A) support #module hp # HP PCLAN (27245 and other 27xxx series) support #module lp486e # LP486E on board Ethernet #module lance # AMD LANCE and PCnet (AT1500 and NE2100) support #module ne io=3D0x300 # NE2000/NE1000 support #module ne2k-pci # PCI version of NE-2000 #module natsemi # National Semiconductor DP8381x series PCI Ethernet suppor= t #module ni5010 # Racal-Interlan (Micom) NI cards #module ni52 # Racal-Interlan (Micom) NI cards #module ni65 # Racal-Interlan (Micom) NI cards module pcnet32 # AMD PCnet32 PCI support module sis900 # SiS 900/7016 PCI Fast Ethernet Adapter support # # Common in integrated motherboards #module smc-ultra # SMC Ultra support #module smc9194 # SMC 9194 support #module starfire # Adaptec Starfire/DuraLAN support #module sundance # Sundance Alta support #module tlan # TI ThunderLAN support, Compaq Neteligent 10/100 #module typhoon # 3cr990 series "Typhoon" support #module tulip # DECchip Tulip (dc21x4x) PCI support #module via-rhine # VIA Rhine support (both Rhine I and II). Common in integrated motherboards #module wd # WD80*3 support #module winbond-840 # Winbond W89c840 Ethernet support #module xircom_cb # Xircom CardBus support #module xircom_tulip_cb # Xircom Tulip-like CardBus support #!!!Ethernet 1000 Mbit Modules module acenic # Alteon AceNIC/3Com 3C985/NetGear GA620 Gigabit support #module dl2k # D-Link DL2000-based Gigabit Ethernet support module e1000 # Intel(R) PRO/1000 Gigabit Ethernet support #module ns83820 # National Semiconductor DP83820 support #module hamachi # Packet Engines Hamachi GNIC-II support #module yellowfin # Packet Engines Yellowfin Gigabit-NIC support #module r8169 # Realtek 8169 Gigabit Ethernet support #module sk98lin # Marvell Yukon Chipset / SysKonnect SK-98xx Support module tg3 # Broadcom Tigon3 support #module via-velocity # VIA Velocity support #!!!Ethernet 10000 Mbit Modules #module ixgb # Intel(R) PRO/10GbE support #module s2io # S2IO 10Gbe XFrame NIC #!!!Token Ring modules #module 3c359 # 3Com 3C359 Token Link Velocity XL adapter support #module abyss # Madge Smart 16/4 PCI Mk2 support #module ibmtr # IBM Tropic chipset based adapter support #module lanstreamer # IBM Lanstreamer chipset PCI adapter support #module olympic # IBM Olympic chipset PCI adapter support #module smctr # SMC ISA/MCA adapter support #module proteon # Proteon ISA support #module skisa # SysKonnect TR4/16 ISA support #module tmsisa # Generic TMS380 ISA support #module tmspci # Generic TMS380 PCI support #module mtok # Madge Token Ring Linux Driver #!!!PCMCIA Network Modules #module 3c589_cs # 3Com 3c589 PCMCIA support #module 3c574_cs # 3Com 3c574 PCMCIA support #module fmvj18x_cs # Fujitsu FMV-J18x PCMCIA support #module pcnet_cs # NE2000 compatible PCMCIA support #module nmclan_cs # New Media PCMCIA support #module smc91c92_cs # SMC 91Cxx PCMCIA support #module xirc2ps_cs # Xircom 16-bit PCMCIA support #module axnet_cs # Asix AX88190 PCMCIA support #module ibmtr_cs # IBM PCMCIA tokenring adapter support #!!!Wireless PCMCIA Network Modules #module ray_cs # Aviator/Raytheon 2.4MHz wireless support #module netwave_cs # Xircom Netwave AirSurfer Pcmcia wireless support #module wavelan_cs # AT&T/Lucent old WaveLAN Pcmcia wireless support #!!!Wireless Modules #module orinoco_pci # Prism 2.5 PCI 802.11b adaptor support (EXPERIMENTAL) #module orinoco_cs # Hermes PCMCIA card support #module airo_cs # Cisco/Aironet 34X/35X/4500/4800 PCMCIA cards #!!Modem Modules #module cdc-acm # USB Modem support (CDC ACM) #!!USB Palm Devices #module visor # USB Handspring Visor / Palm m50x / Sony Clie Driver #!!Sound Modules # #!!!ISA # #module snd-ad1816a # Analog Devices SoundPort AD1816A #module snd-ad1848 # AD1848 (Analog Devices) or CS4248 (Cirrus Logic) #module snd-cs4231 # CS4231 chips from Cirrus Logic #module snd-cs4232 # CS4232 chips from Cirrus Logic #module snd-cs4236 # CS4235,CS4236,CS4237B,CS4238B,CS4239 chips from Cirrus Logic #module snd-es968 # ESS AudioDrive ES968 chips #module snd-es1688 # ESS AudioDrive ES688 or ES1688 chips #module snd-es18xx # ESS AudioDrive ES18xx chips #module snd-gusclassic # Gravis UltraSound Classic soundcards #module snd-gusextreme # Gravis UltraSound Extreme soundcards #module snd-gusmax # Gravis UltraSound MAX soundcards #module snd-interwave # AMD InterWave based soundcards (Gravis UltraSound Plug & Play # STB SoundRage32, MED3210, Dynasonic Pro, Panasonic PCA761AW) #module snd-interwave-stb # AMD InterWave based soundcards with a TEA6330T bass and # treble regulator (UltraSound 32-Pro) #module snd-opti92x-ad1848 # Opti 82C92x or OTI-601 chips and using an AD1848 codec #module snd-opti92x-cs4231 # Opti 82C92x chips and using a CS4231 codec #module snd-opti93x # Opti 82C93x chips #module snd-sb8 # Creative Sound Blaster 1.0 2.0/Pro (8-bit) or 100% compatible #module snd-sb16 # Sound Blaster 16 soundcards (including Plug and Play version) #module snd-sbawe # Sound Blaster AWE soundcards (including Plug and Play version) #module snd-wavefront # Turtle Beach Maui, Tropez, Tropez+ based on the Wavefront chip #module snd-als100 # Avance Logic ALS100, ALS110, ALS120 and ALS200 chips #module snd-azt2320 # Aztech Systems AZT2320 chip #module snd-cmi8330 # C-Media CMI8330 chip #module snd-dt019x # Diamond Technologies DT-019X or Avance Logic ALS-007 chips #module snd-opl3sa2 # Yamaha OPL3-SA2 and OPL3-SA3 chips #module snd-sgalaxy # Aztech Sound Galaxy soundcards #module snd-sscape # Ensoniq SoundScape PnP soundcards # #!!!PCI # #module snd-ali5451 # AC97 intergrated device with ALi M5451 Audio Controller # (M1535/M1535D/M1535+/M1535D+ south bridges) #module snd-atiixp # AC97 intergrated device with ATI chipsets # (ATI IXP 150/200/250/300/400) #module snd-au8810 # Aureal Advantage soundcards #module snd-au8820 # Aureal Vortex soundcards #module snd-au8830 # Aureal Vortex 2 soundcards #module snd-azt3328 # Aztech AZF3328 (PCI168) soundcards #module snd-cs46xx # Cirrus Logic CS4610/CS4612/CS4614/CS4615/CS4622/ # CS4624/CS4630/CS4280 chips #module snd-cs4281 # Cirrus Logic CS4281 chips #module snd-emu10k1 # Sound Blaster PCI 512, Live!, Audigy and # E-mu APS (partially supported) soundcards #module snd-korg1212 # Korg 1212IO soundcards #module snd-mixart # Digigram miXart soundcards #module snd-nm256 # NeoMagic NM256AV/ZX chips #module snd-rme32 # RME Digi32, Digi32 PRO and Digi32/8 (Sek'd Prodif32, # Prodif96 and Prodif Gold) audio devices #module snd-rme96 # RME Digi96, Digi96/8 and Digi96/8 PRO/PAD/PST soundcard= s #module snd-rme9652 # RME Hammerfall (RME Digi9652/Digi9636) soundcards #module snd-hdsp # RME Hammerfall DSP Audio soundcards #module snd-trident # Trident 4D-Wave DX/NX or SiS 7018 chips #module snd-ymfpci # Yamaha PCI chips YMF724,YMF724F,YMF740,YMF740C,YMF744,YMF754 #module snd-als4000 # Avance Logic ALS4000 chips #module snd-cmipci # C-Media CMI8338 or CMI8738 chips #module snd-ens1370 # Ensoniq AudioPCI ES1370 chips #module snd-ens1371 # Ensoniq AudioPCI ES1371 chips and Sound Blaster PCI 6= 4 or 128 #module snd-es1938 # ESS Solo-1 (ES1938, ES1946, ES1969) chips #module snd-es1968 # ESS Maestro 1/2/2E chips #module snd-maestro3 # ESS Maestro 3 (Allegro) chips #module snd-fm801 # ForteMedia FM801 chip #module snd-ice1712 # ICE1712 (Envy24) chip #module snd-ice1724 # ICE/VT1724/1720 (Envy24HT/PT) chips #module snd-intel8x0 # AC97 intergrated device with Intel/SiS/nVidia/AMD chipsets, or # ALi chipsets using the M5455 Audio Controller #module snd-sonicvibes # S3 SonicVibes chip #module snd-sonicvibes # S3 SonicVibes chip #module snd-via82xx # AC97 intergrated device with VIA chipsets #module snd-vx222 # Digigram VX222 soundcards #!!USB Devices module usb-hid # Needed for USB keyboards and mice #module usb-storage # Needed for USB-Sticks module usb-printer # Needed for USB-Printers #!!Storage Devices #module ide-floppy # LS-120, Iomega Zip module floppy # Floppy disk support module ide-cd # CD-Rom Drive Support #!!Filesystem Support # -- Every mounted device needs a filesystem, choose which ones are supported below. module autofs4 # Automount and autofs support module isofs # ISO9960 file system support for CDRoms module vfat # Fat and VFat file system support module ntfs # NTFS file system support #module ext2 # Ext2 file system support #module ext3 # Ext3 file system support module supermount # Supermount support for auto unmounting of removable media #module nfs # NFS file system support #module smbfs # Samba client FS Support, allows you to mount smb filesystem= s ################################################# ### --- Packages to include in boot image --- ### ################################################# # A package is a program or utility. # Any packages may be added as "package" or "pkg". # If defined as a "package" the program is included in the boot image. # If defined as a "pkg" the program is added from outside the image. # Normally use "package", and only "pkg" if you want to dynamically load packages # --- Packages to include in boot image # --- Packages below may be "package" or "pkg" #!!Miscellaneous #package hwclock # Utility to set system time from hardware clock #package sound-esd # Enable one of these modules if you want to be able to control #package sound-nasd # sound on your thinstation from another computer or # your remote session. #!!X related #package xorg6-tinyx # TinyX Xvesa server (for low memory machines) # works with ICA too, is slower, don't choose any X modules with # this server, you don't need anything else. # Otherwise choose from Xfree 3 or 4 (4 is recommended) #package xf3-svga # XF86_SVGA 3.3.6 server #package xf3-s3 # XF86_S3 3.3.6 server #package xf3-vmware # VMWare X server for development #package xorg6vnc # Xorg VNC Server Module. With this package you can # connect to the TS client's desktop from a java # browser on "http://<TS ip>:5800 # --- Xorg6R8.2 # General Xorg6R8.2 video drivers: # Only include what you really need! #package xorg6-apm # Alliance ProMotion video driver #package xorg6-ark # Ark Logic video driver #package xorg6-ati # ATI video driver #package xorg6-chips # Chips and Technologies video driver #package xorg6-cirrus # Cirrus Logic video driver #package xorg6-cyrix # Cyrix video driver #package xorg6-glint # GLINT/Permedia video driver #package xorg6-i128 # Number 9 I128 video driver #package xorg6-i740 # Intel i740 video driver package xorg6-i810 # Intel 8xx integrated graphics chipsets #package xorg6-mga # Matrox video driver #package xorg6-neomagic # Neomagic video driver #package xorg6-nsc # Nsc video driver package xorg6-nv # NVIDIA video driver #package xorg6-r128 # ATI Rage 128 video driver #package xorg6-radeon # ATI RADEON video driver #package xorg6-rendition # Rendition video driver package xorg6-s3 # S3 video driver #package xorg6-s3virge # S3 ViRGE video driver #package xorg6-savage # S3 Savage video driver #package xorg6-siliconmotion # Silicon Motion video driver package xorg6-sis # SiS video driver #package xorg6-tdfx # 3Dfx video driver #package xorg6-tga # DEC TGA video driver package xorg6-trident # Trident video driver #package xorg6-tseng # Tseng Labs video driver package xorg6-vesa # Generic VESA driver, use this if you don't know what t= o use #package xorg6-vga # VGA 320x200 8 bit #package xorg6-via # VIA video driver #package xorg6-vmware # VMware SVGA video driver #!!Keyboard layouts (Language/Country) #package keymaps-ar # Arabic #package keymaps-cs # Czech #package keymaps-da # Danish #package keymaps-de # German #package keymaps-de_ch # German-Switzerland #package keymaps-en_gb # English-Great Britian #package keymaps-en_in # English-United States International #package keymaps-en_nz # English-New Zealand package keymaps-en_us # English-United States #package keymaps-es # Spanish #package keymaps-et # Estonian #package keymaps-fr_be # French-Belgium #package keymaps-fr_ca # French-Canada #package keymaps-fr_ch # French-Switzerland #package keymaps-fr # French #package keymaps-hr # Croatian #package keymaps-hu # Hungarian #package keymaps-it # Italian #package keymaps-ja # Japanese #package keymaps-la # Latin #package keymaps-lt # Lithuanian #package keymaps-lv # Latvian #package keymaps-mk # Macedonian #package keymaps-nl # Dutch #package keymaps-nl_be # Dutch-Belgium #package keymaps-nb # Norwegian #package keymaps-pl # Polish #package keymaps-pt_br # Portuguise-Brazil #package keymaps-pt # Portuguise #package keymaps-ro # Romanian #package keymaps-ru # Russian #package keymaps-sv_fi # Swedish-Finland #package keymaps-sv # Swedish #package keymaps-sl # Slovenian #package keymaps-th # Thai #package keymaps-tr # Turkish #!Applications #!!Connection Package types (Choose *at least* one!) package rdesktop # X RDP client for Windows Terminal Services (ver 1.3.1) #package rdesktop_svga # SVGA RDP client, This is Version 1.1 of rdesktop Only # Use this for low memory machines #package vncviewer # VNC client (vncviewer) #package ica # Citrix ICA client support #package tarantella # Tarantella client support #package ica_wfc # Citrix ICA manager #package xnest # XDM in a window client #package rxvt # Light Xterm Client (vt102) package xterm # Xterm Client (vt220) #package ssh # Secure Shell client #package tn5250 # 5250 terminal emulator #package dillo # Dillo light web browser #package nx # No Machine NX client #package firefox # Firefox web browser (ver 1.0) #package flash # Macromedia Flash (ver 7.0) #!!Window Managers (Choose no more than 1 window manager) # Not needed if you don't want to manage windows #package blackbox # "Blackbox" window manager. Makes TS a light workstation= . package icewm # "ICEWM" window manager. Makes TS a light workstation. # Is a little bigger than blackbox #!!Window Manager Utils package xtdesk # Adds icons to desktop #!!Other services #package www # Web access to client. From a browser: "http://<IP number>" # The standard page is for general user settings, administrative access # is on port 6800 package lp_server # Remote printing daemon (JetDirect compatible) #package lpr # LPR Print Server, for use with samba-server package #package sshd # Dropbear secure shell server #package tftpd # TFTP, built in tftpd server # Useful for making a tftpserver for thinstation on a WAN # over a slow link #package samba-server # Samba server FS Support, allows you to share # local floppy/cdrom/hd/printer to other Windows # PCs; Needs supermount for removeable media #!!Miscellaneous #package e3 # Basic vi like Editor #package debug # Debug support, adds strace and other commands # not recommended for normal use. #!Parmeters ######################################## ### --- Miscellaneous Parameters --- ### ######################################## #!!Basic param rootpasswd P1ndoadmin # Do Change! Console/telnet password for Root # If this is enabled, Telnetd will be enabled param xorgvncpasswd pleasechangeme # VNC Access Password param storagepasswd pleasechangeme # Password for storage server param dialuppasswd pleasechangeme # Password for dialin account param sambapasswd pleasechangeme # Password for samba shares when using use= r mode security param bootlogo true # Want a backgound picture during boot param bootresolution 1024x768 param defaultconfig thinstation.conf.buildtime # The file with default setu= p # no other config file is found # during boot param basename thinstation # used for all config/tftp file names param basepath . # used to determine path to tftp files param localpkgs false # to determine is PKG files are to be loaded locally param fulllocales false # Use full locale support for packages param icaencryption false # Use ica encryption support, add 290k to image param bootvebosity 3 # Increased vebosity when booting TS # 0 no verbose messages # 1 boot # 2 network # 4 init # 8 kernel # 16 modules # 32 packages # 64 email bootlog file to SMTP server & user set in # thinstation.conf file. This will only work # if networking is working. # # Combinations can be used, ie 12 does Kernel and Module Messages #!!Advanced # Leave this alone unless you can't download (wget required on your Linux box): param icaurl http://download2.citrix.com/files/en/products/client/ica/current/linuxx86.t= ar.gz param tarantellaurl http://www.b2-net.com/tom/tarantella/tnci3li.tar param flashurl http://fpdownload.macromedia.com/get/shockwave/flash/english= /linux/7.0r25/install_flash_player_7_linux.tar.gz param nxurl http://www.nomachine.com/download/1.5.0/client/nxclient-1.5.0-106.i386.tar.= gz #param httpproxy http://192.168.1.2:8080 -- Regards, Jacky |
|
From: Cristian M. <cri...@on...> - 2005-09-27 12:22:50
|
* Roy Wiseman <roy...@ya...> [27-09-05 14:59]: > Hi Cristian, [...] > This is great, I think I'll be able to do it simply > with this. but, this page > http://syslinux.zytor.com/memdisk.php > is causing me some grief. it describes a lot about > what memdisk is and how to use it, but it's not part > of pxelinux. When I boot PXE linux and get to the > command line, memdisk is not a valid command, so this > is not too helpful ... any ideas how to *use* memdisk > ? Ok, so syslinux/pxelinux loads a kernel optionally an initrd, passes them some parameters and boots. The memdisk trick is that you can simulate with it a new boot environment, so if you load memdisk instead of a linux kernel, the initrd loaded can be a floppy image or a disk image. See my previously posted pxelinux.cfg/default file . > Thanks, > > Roy. mitu |
38 messages has been excluded from this view by a project administrator.
