Fred, does your Neoware happen to have a Via Rhine II NIC? Which kernel version are you using?
I ran into problems with a Neoware e90 and the above NIC. I researched the kernel bug archives rather thoroughly, and discovered that they've been tweaking with the settings on these particular types of devices. It's somewhat hit or miss as far as which kernel works it seems because they've changed it in each kernel release. The versions of the LTSP kernel that I've experienced are 2.6.17.8 which doesn't work, and 2.6.16.1 which does. (oddly enough, I had a Dell Optiplex with a different NIC that was exactly the opposite, working with 17, but not 16) If you have the resources on the server you can simply download the kernel kit and the source for the latest 2.6.16 kernel. Or, I can forward you the LTSP kernel and modules that were packaged with 4.2u1 If you do need to send different kernels to different NICs, here's an intro to that: http://wiki.ltsp.org/twiki/bin/view/Ltsp/DHCP#Setting_kernel_parameters_for_a Jeremy Young Programmer/Analyst O'Reilly Auto Parts (417) 862-2674 x1858 [EMAIL PROTECTED] Thanks John, I may have my terms wrong. I set the bios on the Neoware to enable the bootrom. It starts writing to the black screen just like my other non-Neoware PCs that work. It sends a dhcp request. THe server gives an IP, then the server does three tries of DHCPDISCOVER/OFFER with no success. THe client then shows dhcpcd failed, kernel panic, etc. >I may be wrong, but the mention of "PCI" leads me to suspect that the PCI LAN >boot means that it will use a bootrom on the PCI LAN NIC. Is there such a ROM >on your hardware? If not, then that would be consistant with your surmise >that there is no NIC driver, but unfortunately that would mean you won't be >booting diskless until a bootrom in installed. Since it is reporting a dhcp >failure, I think that this scenario is likely. If the failure came *after* it >had an IP address, then it might be a PXE vs. Etherboot issue. On Friday 06 October 2006 09:56, [EMAIL PROTECTED] wrote: >> Sorry if this is a duplicate, I was haveing "suspicious header" problems. >> >> Hi, thanks to those who helped me realize my Neoware client was not >> really functioning as an LTSP client. I now have it set to do PCI LAN >> boot, but I am getting the "dhcpcd failed - kernel panic message at >> boot. I have read in the archives about this usually being where there >> is no driver found for the LAN card. It is a fairly new Neoware e140. >> I have regular PC LTSP clients workng fine from the same server. >> >> There are no media drives on this unit, so alternate booting is not a >> possibilty. I am using 4.2u2. I see 4.2u3 upgraded the kernel, perhaps >> that added a LAN driver? Do lan driver problems get fixed by using >> newer kernels or do you have to add the actual driver you need to >> kernel. If anyone has "the worlds biggest LTSP kernel" that has all >> drivers, please send it to me. Can I just get the upgraded 4.2u3 kernel >> file and put it in my 4.2u2 system or does that not work? Where would I >> get the new kernel file? I installed from iso onto SLED 10, but I don't >> see a 4.2u3 or 4 iso, is one available? >> >> Thanks for any ideas, >> fred >> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _____________________________________________________________________ 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.freenode.net
