Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm trying to get my intel 3945 setup so that it automatically is turned on when I reboot... currently, to get it working, I've got to log in as root, then:
cd root
cd ipw3945-1.0.12/
sudo ./load debug=0
iwconfig eth1 essid MYWIRELESS
ifup eth1
and this will only work when I log in as root... i changed ONBOOT=YES in:
/etc/sysconfig/networking/devices/ifcfg-eth1
and when I reboot, it tries to load eth1 but throws back an error about it not existing.
Distribution: approximately NixOS (http://nixos.org)
Posts: 1,900
Rep:
I think you should write a script, chmod a+x it, place it in /etc/rc.d/init.d and link it from /etc/rc.d/rc<runlevel>.d/S<number><name>. Such links are sorted lexically and files pointed by them are executed at boot.
Please indicate which distro you are using. Different distro's name their startup scripts differently.
The problem could also be a missing alias in /etc/modprobe.conf or a missing /etc/modprobe.d/ipw3945. ( Two ways of doing the same thing. )
When you created the driver, perhaps the "depmod -a" step was skipped. If a library is involved ( I doubt it ), then "ldconfig" may need to be run. Running these can't hurt.
It may be possible that it is expected that your ipw3945 driver is in the initrd file. Perhaps running "mkinitrd" would help.
After running these commands and rebooting, if you have a "network devices" configuration setup program, such as in Yast, run it and see if the device shows up. If it shows up, you device is being loaded on boot, and you can configure your network settings there. The settings will change the contents of your /etc/sysconfig/network/ifcfg-eth0. Please note that your system may use a different naming convention instead such as "/etc/sysconfig/network/ifcfg-eth-bus-pci-0000\:02\:01.0" instead. The network devices configuration program may have a "hardware name" entry on one of its pages where that can be changed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.