On Wed, 2004-01-21 at 14:42, Mark Tombs wrote: > Hi > > I have a problem with a thin client with 2 nics. The client boots from the > floppy, finds the server, gets the kernel, all using the correct NIC - eth1. > However then the linuxrc script detects the wrong NIC - eth0 - and tries to > do the rest using that. However, that is not plugged in. I should mention > that eth1 is a prism2 wireless card, eth0 is an onboard e100, so its not just > a case of plugging in the right card or removing the wrong card. > > So how do I get the client to boot using the right NIC? Or stop the scripts > detecting the wrong NIC?
Option-129 will let you pass parameters to the terminal's kernel to tell it which interrupt to use for the network card, such as "ether=". Look at the kernel-paramters file as well as the notes for your NIC driver. A simpler alternative might be to disable the on-board NIC in the machine's BIOS. -- David Johnston <[EMAIL PROTECTED]> Little Bald Consulting, LLC ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _____________________________________________________________________ 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
