On Mon, Jun 2, 2008 at 11:20 PM, Sanjeet Kumar <[EMAIL PROTECTED]> wrote: > > recently...when i executed /sbin/ipw3945d-start the device node got created > and i could find a directory eth0 for the device in > /sys/class/net....(ipw3945 is the driver)....but why doesn't it startup at > boot......and i still cannot connect to any ap using dhclient
A couple things: 1. Try to use the iwlwifi drivers if you can. The ipw3945 driver has been dropped, partly because of the need for a userspace daemon which is not used in iwl3945. They will work just by loading the driver and having the firmware available. http://intellinuxwireless.org/ 2. If you are using the ipw3945 drivers, you need some sort of udev RUN rule so that the /sbin/ipw3945d-start script is run when the kernel uevent is created. Google should be able to help you there. > there's no modprobe.d modprobe.conf module.conf in /etc directory as > suggested by other mailing lists.....though i created modprobe.conf with the > contents 'alias eth0 ipw3945' If you need to have the network interfaces named differently, see the "Configuring the network script" section of the book: http://www.linuxfromscratch.org/lfs/view/6.2/chapter07/network.html -- Dan -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
