Thread: RE: [Etherboot-users] etherboot pci wifi
Brought to you by:
marty_connor,
stefanhajnoczi
Menu
▾
▴
etherboot-users
|
From: Timothy L. <tim...@al...> - 2005-05-25 13:29:50
|
> Behalf Of Carl Karsten > Are there any PCI nics that will pxe boot, either nativly or=20 > with a floppy? The Prism based DLW-520 (I believe) will boot via etherboot with a floppy. If you have a spare pci slot, a cheapo rtl8139 can be used to hold the rom for the prism chip to allow it to boot without a floppy. 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 fromdisclos= ure. If you are not the intended recipient, you are notified thatany dissem= ination, distribution or copying of this communication is strictly prohibit= ed. If you have received this communication in error, please notify the sen= der 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: Hermann G. <eth...@mr...> - 2005-05-27 18:55:43
|
On Wed, May 25, 2005 at 10:29:38AM -0300, Timothy Legge wrote: > The Prism based DLW-520 (I believe) will boot via etherboot with a > floppy. If you have a spare pci slot, a cheapo rtl8139 can be used to > hold the rom for the prism chip to allow it to boot without a floppy. or as a advanced user, you would first try to boot with a floppy, and if that works, add etherboot to the system bios chip. :-) so it works without additional hardware let us know how it works! hermann |
|
From: Carl K. <ca...@pe...> - 2005-05-27 19:33:33
|
Hermann Gausterer wrote: > On Wed, May 25, 2005 at 10:29:38AM -0300, Timothy Legge wrote: > >>The Prism based DLW-520 (I believe) will boot via etherboot with a >>floppy. If you have a spare pci slot, a cheapo rtl8139 can be used to >>hold the rom for the prism chip to allow it to boot without a floppy. > > > or as a advanced user, you would first try to boot with a floppy, > and if that works, add etherboot to the system bios chip. :-) > so it works without additional hardware > > let us know how it works! Wait.. you can add etherboot to the system bios chip? Like the Mother Board Bios? and so the NIC would still have an empty eprom socket? (I am excited) So is it specific for the NIC, or can it be generic for any NIC plugged into the PCI buss? Carl K |
|
From: Hermann G. <eth...@mr...> - 2005-05-27 19:52:05
|
On Fri, May 27, 2005 at 02:34:29PM -0500, Carl Karsten wrote: > Wait.. you can add etherboot to the system bios chip? Like the Mother=20 > Board Bios? and so the NIC would still have an empty eprom socket? >=20 > (I am excited) yes, exactly that ... :-o details are in the etherboot wiki: http://wiki.etherboot.org/pmwiki.php/Main/PuttingEtherbootIntoYourBIOS > So is it specific for the NIC, or can it be generic for any NIC plugged= =20 > into the PCI buss? no, that is not possible ....=20 the bios scans for the pci-id in the rom; if such an hardware is found, the eprom is enabled and etherboot can work. but, if the free space in the rom is large enough, you can put in a romfile for your wlan nic, and one for your "wired" one ... :-) from the system point of view, an wlan nic is nothing other than a pci card ... so if it works with a floppy, it works also in the BIOS hermann |
|
From: Carl K. <ca...@pe...> - 2005-05-27 21:20:07
|
> > http://wiki.etherboot.org/pmwiki.php/Main/PuttingEtherbootIntoYourBIOS A wiki! Mind if I add some of my config files? Like what is below here, and a simple dhcpd.conf. I'll even add some more commetns. ck root@shaz:/var/lib/tftpboot # cat pxelinux.cfg/default # pxelinux.cfg/default # display ubuntu-installer/i386/boot-screens/syslinux.txt default menu prompt 1 timeout 0 F1 pxelinux.cfg/default label pxesmb # SMB on pxe TCP/IP stack kernel memdisk append initrd=smb/pxesmbboot.IMA keeppxe label sbm-floppy # smart boot manager - menu of all bootable devices on the local box kernel memdisk append initrd=util/sbm.img label menu # makes a menu out of this file, allows editing the options on the client kernel menu.c32 label memtest86 # test memory of local box kernel memtest label memtest86+ # a better version? kernel memtest1 label tomsrtbt # Linux on one floppy (doesn't work with pxe - help?) kernel memdisk append initrd=linux/tomsrtbt.raw pause label linux # ubuntu instaler kernel ubuntu-installer/i386/linux append vga=normal initrd=ubuntu-installer/i386/initrd.gz ramdisk_size=13318 root=/dev/rd/0 rw -- label expert kernel ubuntu-installer/i386/linux append DEBCONF_PRIORITY=low vga=normal initrd=ubuntu-installer/i386/initrd.gz ramdisk_size=13318 root=/dev/rd/0 rw -- label server kernel ubuntu-installer/i386/linux append base-config/package-selection= base-config/install-language-support=false vga=normal initrd=ubuntu-installer/i386/initrd.gz ramdisk_size=13318 root=/dev/rd/0 rw -- label server-expert kernel ubuntu-installer/i386/linux append base-config/package-selection= base-config/install-language-support=false DEBCONF_PRIORITY=low vga=normal initrd=ubuntu-installer/i386/initrd.gz ramdisk_size=13318 root=/dev/rd/0 rw -- label linux-hands-off kernel ubuntu-installer/i386/linux append initrd=initrd.gz ramdisk_size=12890 root=/dev/rd/0 rw preseed/locale=en_US kbd-chooser/method=us netcfg/wireless_wep= netcfg/choose_interface=eth1 netcfg/get_hostname= preseed/url=http://192.168.1.7/preseed.cfg vga=6 -- label server-ho kernel ubuntu-installer/i386/linux append initrd=initrd.gz ramdisk_size=12890 root=/dev/rd/0 rw preseed/locale=en_US kbd-chooser/method=us netcfg/wireless_wep= netcfg/get_hostname= preseed/url=http://192.168.1.7/preseed.server.cfg vga=6 -- label freedos # um... some sort of dos that isn't M$. kernel memdisk append initrd=floppy.img label image # hard disk imager, will burn multipe CD's on a local burner kernel memdisk append initrd=BootItNG/image-exe.img label dosimage # hard disk imager, will burn multipe CD's on a local burner kernel memdisk append initrd=BootItNG/dosimage.IMA label proboot # Intel Boot Agent Utility (wiats this?) kernel memdisk append initrd=util/proboot.ima label dell333b # Intel Eather Express Pro (built into Dell V333), tcp/ip, smb kernel memdisk append initrd=smb/dell333.img label xpmsdos # WinME, might read NTFS, dosn't boot from here. kernel memdisk append initrd=util/xpmsdos.img pause label w98ebd # Win98 Emergancy Boot Disk - has drivers for all sorts of old CD's # and a .cab uf handy utilities that get expanded into a ram disk. kernel memdisk append initrd=util/w98ebd.img |
|
From: Carl K. <ca...@pe...> - 2005-05-29 17:00:11
|
Ok, so how do I format config files? I tired [=, <pre> and a few other things, nothing is even close. Here are the 2 pages in need of help: http://wiki.etherboot.org/pmwiki.php/Main/ShazPxeDefault http://wiki.etherboot.org/pmwiki.php/Main/ShazDhcpdConf I am guessing the Admin (Anselm?) needs to define a style? Carl K |
|
From: Marty C. <md...@et...> - 2005-06-02 19:36:11
|
Carl, First, many thanks for your Config files! It is always exciting and interesting to see how people are using Etherboot. I hope you will add more comments to your Wiki pages. After seeing your pxelinux.cfg/default file, I think it would be a good basis for a tutorial for people who want to use PXELINUX and Etherboot to make a menu-driven booting menu. You certainly seem to have made good use of memdisk and floppy images. I would be interested in an explanation of how you made images such as "image.img" Regarding your quesion: On May 29, 2005, at 1:00 PM, Carl Karsten wrote: > Ok, so how do I format config files? I tired [=, <pre> and a few > other things, nothing is even close. Here are the 2 pages in need of > help: > > http://wiki.etherboot.org/pmwiki.php/Main/ShazPxeDefault > http://wiki.etherboot.org/pmwiki.php/Main/ShazDhcpdConf > > I am guessing the Admin (Anselm?) needs to define a style? > Carl K I have mostly fixed up your pages. Rules for formatting are here: http://www.pmwiki.org/wiki/PmWiki/TextFormattingRules The one you need is somewhat obscurely written: " ... Lines indented with one or more spaces (or tabs) are monospace font, and placed inside of a box with dashed-line border. " So the first thing I did was to indent your files exactly one space to make them mono-spaced. That took care of most of the formatting issues. There is, however, another feature of pmwiki that causes a bit of a problem: " On some PmWiki installations, capitalized words joined together (e.g., WikiWords) can also be used to make references to other pages without needing the double-brackets. " This leads to problems with lines like: append initrd=BootItNG/image-exe.img in which pmWiki thinks BootItNG should be a link, and adds a "_?" after it. The solution is to indent the whole file (or region) 1 space, and then do: Here is a listing: [= line 1 line 2 ... line n =] to prevent formatting of the indented text. Note that you have to do " [=" on the first line of indented text. Thanks again, Carl for the pxelinux.cfg files. They are quite nice, and hopefully now you will add some comments and maybe even turn them into a mini-tutorial on how to use PXELINUX to do a menu, and how to make various image types work with Etherboot. Regards, 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: <fel...@gm...> - 2005-06-05 19:47:52
|
Hi, >>Are there any PCI nics that will pxe boot, either nativly or >>with a floppy? > The Prism based DLW-520 (I believe) will boot via etherboot with a > floppy. If you have a spare pci slot, a cheapo rtl8139 can be used to > hold the rom for the prism chip to allow it to boot without a floppy. I am facing the same problem and would be really interested in your results. Did you have any success so far? I have googled quite a bit on it today but wasn't able to find a single PXE enabled nic, not even 3com. I found some discussion about code for the prism2 chip being merged into etherboot 5.2. Is this still working? Can anybody report on it? Felix |
|
From: Michael B. <mb...@fe...> - 2005-06-06 15:39:53
|
On Sun, 5 Jun 2005, Felix M=F6ller wrote: > > The Prism based DLW-520 (I believe) will boot via etherboot with a > > floppy. If you have a spare pci slot, a cheapo rtl8139 can be used to > > hold the rom for the prism chip to allow it to boot without a floppy. > I am facing the same problem and would be really interested in your resul= ts.=20 > Did you have any success so far? >=20 > I have googled quite a bit on it today but wasn't able to find a single P= XE=20 > enabled nic, not even 3com. >=20 > I found some discussion about code for the prism2 chip being merged into= =20 > etherboot 5.2. Is this still working? Can anybody report on it? I wrote the Prism2 code for Etherboot. As far as I know it still works;=20 if it fails, please let me know. Michael |
|
From: Timothy L. <tl...@ro...> - 2005-06-06 22:21:13
|
Michael Brown wrote: >>I found some discussion about code for the prism2 chip being merged into >>etherboot 5.2. Is this still working? Can anybody report on it? > > > I wrote the Prism2 code for Etherboot. As far as I know it still works; > if it fails, please let me know. I fixed a relocation issue as of Etherboot 5.2.6 and Etherboot 5.3.10. I have not tested it since then but I do expect that the prism_pci driver still works. Tim |
|
From: <fel...@gm...> - 2005-06-06 22:40:53
|
Hi, thank you for your answer! > I wrote the Prism2 code for Etherboot. As far as I know it still works; > if it fails, please let me know. I do not have the hardware yet. I looked into the source and it seems as I should buy a card mentioned at the beginning of drivers/net/prism2_plx.c. I started looking on ebay, but didn't find the right card yet. As I do not have the hardware yet I'd be happy about someone else testing the prism support, but if nobody is able to I will try it in the next weeks myself. Felix |
|
From: Hermann G. <eth...@mr...> - 2005-06-07 09:59:42
|
On Tuesday 07 June 2005 00:38, Felix M=F6ller wrote: > I do not have the hardware yet. I looked into the source and it seems as= I > should buy a card mentioned at the beginning of drivers/net/prism2_plx.c= =2E=20 > I started looking on ebay, but didn't find the right card yet. fortunatly i own such a card ;-) > As I do not have the hardware yet I'd be happy about someone else testing > the prism support, but if nobody is able to I will try it in the next wee= ks > myself. i tried with an old tekram tc-400 .... wow what an old card ;-) i did a to stage loading: 3comMBA -> prism2.pxe -> etherboot-prism boot the accesspoint has all wep & accesslists and such turned off all macs are "anomyzed" ;-) output of etherboot: =2D----------------------------------------------- Etherboot 5.4.0 (GPL) http://etherboot.org Drivers: Prism2_PCI Images: NBI ELF PXE Exports: PXE Protocols: DHCP TFTP Relocating _text from: [0007ec10,00090b80) to [07eee090,07f00000) Probing pci nic... [prism2_pci]Prism2.5 has registers at 0xd9112f70 MAC address 00:02:DD:XX:XX:XX Attempting to autojoin to any available access point (attempt 1)...done Link not connected (status 0x0006) Attempting to autojoin to any available access point (attempt 2)...done Link connected (BSSID 00:80:C8:XX:XX:XX - MAC address 8F:00:00:XX:XX:XX) Searching for server (DHCP)...Tx exception occurred with fid 0x01ed hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x0111 hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x01ee hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x01cb hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x0249 hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x0201 hfa384x: Tx error occurred (status 0x0001): ...retry error =2ENo IP address Tx exception occurred with fid 0x039f hfa384x: Tx error occurred (status 0x0001): ...retry error =2E =2D-----------------------------------------------=20 after here ... it does not progress anymore =2D-----------------------------------------------=20 accesspoint logfile shows a connection: Jun/07/2005 11:46:07 Wireless PC connected 00-02-DD-XX-XX-XX =2D----------------------------------------------- tethereal shows one frame with correct source MAC, but the rest is total ZERO =2D----------------------------------------------- $ tethereal -Vx -r prism2-wlan-etherboot.cap frame.number =3D=3D 51 =46rame 51 (60 bytes on wire, 60 bytes captured) Arrival Time: Jun 7, 2005 11:36:05.362512000 Time delta from previous packet: 1.890025000 seconds Time since reference or first frame: 8.915167000 seconds Frame Number: 51 Packet Length: 60 bytes Capture Length: 60 bytes IEEE 802.3 Ethernet Destination: ff:ff:ff:ff:ff:ff (Broadcast) Source: 00:02:dd:XX:XX:XX (tekram-pc-400) Length: 8 Trailer: 000000000000000000000000000000000000000000000000... Logical-Link Control DSAP: NULL LSAP (0x00) IG Bit: Individual SSAP: NULL LSAP (0x00) CR Bit: Command Control field: I, N(R)=3D0, N(S)=3D0 (0x0000) 0000 000. .... .... =3D N(R): 0 .... .... 0000 000. =3D N(S): 0 .... .... .... ...0 =3D Frame type: Information frame (0x0000) Data (4 bytes) 0000 ff ff ff ff ff ff 00 02 dd XX XX XX 00 08 00 00 .........XXX.... 0010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0020 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 0030 00 00 00 00 00 00 00 00 00 00 00 00 ............ =2D----------------------------------------------- i think something does not run correctly maybe my card is not working correctly, never get it to work with linux directly .. and the original M$ drivers are a P.I.T.A!! :-o mfg hermann |
|
From: Michael B. <mb...@fe...> - 2005-06-07 16:16:13
|
On Tue, 7 Jun 2005, Hermann Gausterer wrote: > i tried with an old tekram tc-400 .... wow what an old card ;-) > > i did a to stage loading: > > 3comMBA -> prism2.pxe -> etherboot-prism boot > > the accesspoint has all wep & accesslists and such turned off > > all macs are "anomyzed" ;-) > > output of etherboot: > ------------------------------------------------ > Etherboot 5.4.0 (GPL) http://etherboot.org > Drivers: Prism2_PCI Images: NBI ELF PXE Exports: PXE > Protocols: DHCP TFTP > Relocating _text from: [0007ec10,00090b80) to [07eee090,07f00000) > Probing pci nic... > [prism2_pci]Prism2.5 has registers at 0xd9112f70 > MAC address 00:02:DD:XX:XX:XX > Attempting to autojoin to any available access point (attempt 1)...done > Link not connected (status 0x0006) > Attempting to autojoin to any available access point (attempt 2)...done > Link connected (BSSID 00:80:C8:XX:XX:XX - MAC address 8F:00:00:XX:XX:XX) > Searching for server (DHCP)...Tx exception occurred with fid 0x01ed > hfa384x: Tx error occurred (status 0x0001): > ...retry error > > <snip> > > maybe my card is not working correctly, never get it to work > with linux directly .. and the original M$ drivers are a P.I.T.A!! :-o The driver is definitely communicating with the card, otherwise you'd never get a successful join to the access point. Do you have a known working card that you could test with? Michael |
|
From: <fel...@gm...> - 2005-06-14 11:53:04
|
Hi, >>I do not have the hardware yet. I looked into the source and it seems as I >>should buy a card mentioned at the beginning of drivers/net/prism2_plx.c. >>I started looking on ebay, but didn't find the right card yet. > fortunatly i own such a card ;-) >>As I do not have the hardware yet I'd be happy about someone else testing >>the prism support, but if nobody is able to I will try it in the next weeks >>myself. > i tried with an old tekram tc-400 .... wow what an old card ;-) > maybe my card is not working correctly, never get it to work > with linux directly .. and the original M$ drivers are a P.I.T.A!! :-o As I am kind of interested in this project I bought a card for myself it is a 3com AirConnect 3CRWE777A. [1] I did not receive the card yet, but as soon as I have it, I will try etherboot with it and report back. MfG Felix [1] http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=5779358226 |
|
From: Hermann G. <eth...@mr...> - 2005-06-07 19:59:22
|
On Tuesday 07 June 2005 18:15, you wrote: > Do you have a known working card that you could test with? no, not with a prism 2.5 chip ... :-( but maybe i can get it work first with linux ..=20 which are the best drivers for this card? there are so many wlan driver packets out there ... and also lots of different firmwares too ... :-( i guess that etherboot uses the firmware on the card;=20 maybe that is a problem too; this card is realy from the first generation of 802.11b i will also try to check with a wlan sniffer too; maybe the cards produces more packets, but the accesspoint=20 ignores them (because of errors ....) hermann |
|
From: Michael B. <mb...@fe...> - 2005-06-08 07:44:56
|
On Tue, 7 Jun 2005, Hermann Gausterer wrote: > > Do you have a known working card that you could test with? > > no, not with a prism 2.5 chip ... :-( > but maybe i can get it work first with linux .. > which are the best drivers for this card? there are so > many wlan driver packets out there ... and also lots of > different firmwares too ... :-( The Etherboot driver is based on the linux-wlan-ng driver. > i guess that etherboot uses the firmware on the card; > maybe that is a problem too; this card is realy from the > first generation of 802.11b It uses the firmware only to the same extent as the Linux driver, so this shouldn't be a problem. Michael |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X