Horst, I checked the niclist file, and that card should be automatically identified.
But, it requires the IO= setting in dhcpd.conf, option-129. The problem is that there are some versions of Etherboot that don't pass the kernel commandline options properly. I think it has to do with using an older version of Etherboot (Pre 5.0.0) with newer versions of mknbi (we used 1.2-2 for ltsp). So the args in dhcpd.conf aren't getting passed to the kernel. The only way I've found to get around this is to re-tag the kernel with mknbi-linux. You will need to download the ltsp_initrd_kit, and take a look at the buildk script. there's an example of a "--append" line that will add the commandline options to the tagged image. I think that will take care of the problem. Or, you could make a new bootrom with a newer version of Etherboot. Jim McQuillan. [EMAIL PROTECTED] Horst Prote wrote: >Jim, > >In your answer to Doug last week you said > > > Doug, > > > > ... > > > > 2) Option-128 is a vendor ID tag. The value 'e4:45:74:68:00:00' is a > > special value indicating > > Etherboot. That is, etherboot recognizes that number. Etherboot > > will ignore any additional > > options, like option-129, if option-128 does NOT have that special > > value. > > > > The latest versions of our kernel package don't need option-128 or > > option-129, because > > we now autodetect the network card. (assuming it's a PCI card). > >Is it possible that not all PCI network cards are autodetected? > >I just tried 2.09pre3 (lts_core-2.09pre3.tgz, lts_kernel-2.09pre3.tgz, >lts_x_core-2.09pre3.tgz) with a D-Link DE528CT >(http://www.dlink.com/products/adapters/de528ct/) network card (with >ne2kpci.rom bootrom image, downloaded in Feb 2000 from ltsp.org; this >card works with lts-2.0 and kernel vmlinuz.ne2000). The client >successfully contacts the DHCP-Server, downloads vmlinuz.ltsp via tftp >and then starts the kernel which crashes with: > > ... > Freeing unused kernel memory: 68k freed > =================================================================== > Running /linuxrc > Mounting /proc > > ERROR! No IO specified. > The NIC requires an IO=0xNNN entry on the kernel commandline. > This is setup in the /etc/dhcpd.conf file using option-129 > > Kernel panic: Attempted to kill init! > >The server machine is RedHat 7.1 with dhcp-2.0pl5-4. I tried it with >and without this two lines in /etc/dhcpd.conf: > option option-128 e4:45:74:68:00:00; > option option-129 "NIC=ne2k_pci IO=0x300"; >(By the way. Is my guess correct that ^^^^^this "NIC-name" corresponds >to the kernel config option for the network card?) > >Regards > >Horst > >_____________________________________________________________________ >Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: > https://lists.sourceforge.net/lists/listinfo/ltsp-discuss >For additional LTSP help, try #ltsp channel on irc.openprojects.net > _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.openprojects.net
