Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Eth1/LinuxConf problem

Status
Not open for further replies.

OzDog

MIS
Jan 10, 2002
192
GB
I am a bit of a newbie to Linux - used a little @ uni & little @ home, tho I have been working in IT for 10 years.

My expertise is mainly in MS & Citrix worlds (that's enough of the jeering thanks all you Linux-heads :)). I know a fair bit about computers/networking, it's just the application of the knowledge in Linux that is getting me.

I am now running RedHat 7(.3 I think?) at home, Kernel 2.4.7-10, using 2 NICs. Eth0 is a 3Com which auto-detected at install, and is working fine for my home LAN. Eth1 is a Cisco Aironet 4800, connected to my corporate 802.11b wireless.

I originally installed PCMCIA services with the OS, so didn't have to re-compile the kernel to get the card going, just ran the install script for the card. All OK.

Now that I've finished that, I can reboot and eth1 does not attempt to start. If I run "insmod airo" the card starts and works OK. (BTW - What is "insmod", what does it do??)

I downloaded linxconf (purely because the instructions semmed to indicate it was the "be all and end all" fix), and tried to install the Aironet as a eth1, but the driver is not listed. I added it as a wireless card however, and it works, but still I need to run "insmod" whenever I reboot to enable the card.

I guess my question is - How do I install the card so that it appears in the Network Configuration the same as the 3Com, and starts at boot time? I assume that if the driver were listed there I could add it OK?>?

Sorry if I seem to be all over the place - that's how we MS people work!!! Cheers,
Sam

Please let members know if you found their posts helpful.
 
The kernel package you have is built up of a core kernel, which contains most of the important drivers and functions to get the OS started. Because there are so many drivers most are kept out of the kernel and only loaded when needed - these are your modules. 'insmod' is for 'installing' modules into the running kernel, ie. loading drivers.
when you restart RedHat isn't configured to load this module automatically. i think you might be able to change this by running kudzu or it might be as simple as adding the line

alias eth1 airo

to your /etc/modules.conf - if you look in here you'll probably see some of your other modules being loaded.
 
You can run your own custom commands that will be started at boot time if you add them to the end of the /etc/rc.d/rc.local file. You might want to add the insmod command here if the /etc/modules.conf file doesn't start it. As for eth1, check in the /etc/sysconfig/network-scripts directory. You might need to add the ifcfg-eth1 file there.


ChrisP
 
You also might want to stay away from linuxconf. It has a tendancy to mess things up. Even Red Hat advises against using it, which is why it isn't installed by default anymore.

Use the Red Hat network confuguration utility

/usr/sbin/redhat-config-network

It's a GUI interface and works protty well.

I hope this helps.

Todd :> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Todd Hutchins
Microcomputer Specialist II
El Dorado County Office of Education
thutchin@edcoe.k12.ca.us
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top