Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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 have two machines, one running Red Hat 7.3, the other running Red Hat 8.0
The configuration on my Red Hat 7.3 is fine but Red Hat 8 cant seem to detect the NIC I have installed in it.
Both machines have different types of NICs
Red Hat 8.0 machine: Belkin 10/100
Red Hat 7.3 machine: Linksys 10/100
In Red Hat 8 I did a
ping 127.0.0.1
It reported back no loss and 100% success so at least I know the card works. When I open my hardware browser, the NIC is not listed.
I'm trying to assign an IP address to my Red Hat 8 machine so I can have a little peer to peer set up. On the Red Hat 8 machine I'm using the Kde desktop and on my Red Hat 7.3 machine I'm using the Gnome desktop.
What can I do so that Red Hat 8 can detect my NIC?
why would pinging 127.0.0.1 be a good indeication that your NIC works? 127.0.0.1 is the localhost, which would register on the loopback interface, the sucessfully check a NIC you would need to ping somthing OUTSIDE of the NIC.
Redhat dosnt have drivers for the specific nic or its not picking up that there is a NIC in there?
now Im confused
I dont know much about networking so bare with me
If I didnt have a NIC or if my NIC was broken would I be able to do 127.0.0.1?
I thought that if I didnt do 127.0.0.1 and I also failed to ping another machine that it would mean one of two things
1. My nic is broken
2. My network configuration is wrong
I thought that by doing 127.0.0.1 I would be able to eliminate the first problem.
but since your telling me my nic has nothing to do with 127.0.0.1 I guess it was a wast of time.
I was just doing 127.0.0.1 to see if my nic worked.
I cant configure anything and ping another machine because my nic isnt detected in the first place, either that or it is not showing up in my harware browser window for some reason.
127.0.0.1 resolves back to localhost.localdomain, which is the machine you are sitting on, in essense when your ping 127.0.0.1 it dosnt have to go out and come back, it just sits on the machine, loop back interface is what it is i do believe. Is there lights on the nic? what do they look like when booting into redhat?
pinging the IP address of your network card tests your ethernet driver.
pinging a host out on the wire tests connectivity to other machines (obviously).
First, see if redhat is detecting your NIC by issuing the command "ifconfig -a". This will list all network interfaces detected by your OS. If you don't have an ethX (probably eth0) listed, you need to load the module for your NIC or recompile the kernel with your NIC's driver.
If you know where the modules are stored (likely /lib/modules), you can use modprobe to find the driver that suits your NIC. You can do this by doing:
modprobe tulip; ifconifg -a (to see if the card shows up.)
modprobe rtl8329too; ifconfig
...
jamrock: there is no reference to eth0 or eth1 when Red Hat 8.0 starts up on my machine.
I just went to Red Hats website and didnt see anything about my NIC in the HCL. I dont think Red Hat supports it at all. I had windows 98 in the machine before I got rid of it and replaced it with Red Hat 8. I just left the NIC in the machine and hoped it would work, I guess I need a new NIC.
From the Red Hat 8.0 desktop menu go to Systems Settings and to the submenu item Network and try adding the device there. I had to do the same thing for mine. And you may have to activate it too in the Systems Tools -> Network Device Control too.
the modules directory is where you said it would be (/lib/modules)
I dont know what modprobe is so I read the man page about it, Im still not too sure what it is or how it works.
I tried to use it and I keep getting 'command not found'
Im not a very technical person but I refuse to give up just because I dont understand.
If you want to get snide because you know more about linux than I do or if you lack the patience to help someone like me who is new to linux than dont help me. lets not wast eachothers time.
The home page of this website states
Quote:
Welcome to LinuxQuestions.org. You can visit our forum where Linux newbies can ask questions and Linux experts can offer advice.
Im a newbie whos asking a question, if you dont like my question or how I ask it, dont answer it. if you want to help me and not insult me I would appreciate it. If you are going to insult me the whole way, dont bother. yeah Im used to windows, I grew up using windows, now I want to learn something new without getting put down and told to just stick to windows because I dont understand or because Im not as technical as others.
again, Id like to thank everyone whos helped me so far, ALL of you.
My intention wasn't to arouse your anger. When I post an answer that I know is going to work for someone and they ignore it, it just seems to me like someone didn't get the easy answer they expected.
Nothing I said was meant to be insulting. Most of my posts are unbiasedly informative (IMHO).
Quote:
If you follow my directions, you'll get your card to work. If you wanna f*ck around with HCL's and Hardware Qualifiers, stick to windows.
Both statements are quite truthful. You can get just about any device to work in linux. You aren't limited to an "HCL". (even winmodems, which it's intended home was, obviously, windows.) It just takes time for someone to develop the tools to use it (or you develop it yourself, whatever the case may be.)
The Soundblaster Audigy is another good example. There isn't any native kernel code out (to my knowledge). There's a development team that posts drivers to this card using Sourceforge. ( http://www.sourceforge.net )
When you login, are you logging in as root or are you "su"-ing to root?
Your paths are jacked up, that's why just "ifconfig -a" isn't working for you.
modprobe is also going to be located in /sbin.
If a driver isn't compiled into your kernel, you can (with some drivers) load them as a module. Which means, while the kernel is running (Linux is booted up.) you can insert drivers into it allowing your hardware componants to work. This is a very neat feature of Linux. modprobe is a utility used to load modules into the running kernel.
I'm not sure where you can obtain documentation on how modules work, but http://www.tldp.org may be a good place to start looking. If you plan to learn Linux more in depth, this is a site to keep bookmarked.
I'm not sure where you can obtain documentation on how modules work, but http://www.tldp.org may be a good place to start looking. If you plan to learn Linux more in depth, this is a site to keep bookmarked.
This is the type of useful information Im looking for, to assume Im just looking for an easy answer is wrong.
Quote:
When I post an answer that I know is going to work for someone and they ignore it, it just seems to me like someone didn't get the easy answer they expected.
I ignored it because it was over my head, I didnt know what you were talking about
Quote:
You can get just about any device to work in linux. You aren't limited to an "HCL".
If Im new to linux, there is no way for me to know this.
Anyway your last post cleared some things up for me and I would like to thank you for all your help.
If Redhat recognizes the card, it automatically loads the drivers and initializes the card. If it doesn't recognize the card, you can sometimes use a compatible driver.
I have never worked with those cards.
Perhaps you could check each company's website and see if they have Linux drivers. They may also have info. somewhere regarding compatible drivers.
Are these PCI or ISA cards?
You could also try contacting the relevant manufacturer's tech. support. The email address should be listed on the card's box or on the website.
Let me know how it works out.
BTW, the following links have some info. re: Linux and network cards:
OrganicX, I had exactly the same problem with the same make of network card on Redhat 7.3 The problem with so many people when they are troubleshooting is that they go for the difficult options first. I appreciate the fact that you're new to Linux - some other people are not so understanding. Always check the simple things first, even the blindingly stupid. We're all human and we can all forget to do the most simple thing. Don't even consider recompling the Kernel yet or anything like that.
The first thing to try is to go into your BIOS and set the "Plug and Play Aware OS" to "NO". This worked for me with my network card, my on-board Firewire port and my soundcard... and not just on one machine as well I might add. If all goes to plan after you have changed the aforementioned setting in your BIOS then you should see Kudzu detect the card and ask you if you want to setup networking now! If it doesn't let me know and we'll try some other things.
ppuddick I checked my Bios and it was configured for windows 98/2000, the computer came with windows 98 so I changed the configuration to "other". When I rebooted, kudzu detected my network card right away.
Both my machines are able to ping eachother with 0% loss.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.