Linux cable modem help

[StormRavn]

I recently installed Red Hat 9.0 on a box full install and i want to be able to hook my cable modem i am very new to the linux world i was hopin i could just plug my ethernet cord in the nic card and it will just pop online no problem what so ever

i use charter pipeline as my cable so if anyone can tell me how to make my cable work on my linux box i would be very grateful what to type when i type in root ifconfig -a it just shows

inet is 127.0.0.1
mask is 255.0.0.0

i know these numbers are wrong cause thats not the ip of my cable modem

[kilgoretrout]

It's been a while since I ran rh but I'm sure ther's a network configuration utility in there somewhere. Your ISP is undoubtedly using dhcp which makes it real easy. Just plug in the ethernet cable from the modem to your nic and run the utility. Choose dhcp when asked if your given an option.

This is usually very easy to setup in linux; if everything is connected during the install, it's usually done automatically.

[StormRavn]

well that would be nice but RH says i dont have a nic card when i do so a little conflict of interest

[Karnevil9]

If I remember from RH9 Kilgoretrout is on the right track. In the Internet configuration, you have to select an etho device. It will give you a list of all the NIC's cards that are supported. Hopefully yours is in there and all you have to do is select it and it should install the kernel for it, then go through the rest and select the dhcp as suggested. If it is not there, then you have to a little investigating and find a place that has a driver for your card.
You can try www.linuxquestions.org . Go to forums and select distribution. They have a place for all redhat problems.

[kilgoretrout]

What's your nic, and more importantly what kind of chipset does it use? To get a listing of everything on the pci bus run as root:

# lspci

Here's the output I get for my nic:

02:0d.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)

The chipset is RTL8139, which is a common RealTech chipset used by many manufacturers. It's driver module is 8139too.

Post back your results. Some integrated nics have problems in linux,particularly those on nforce motherboards. ISA nics are also very problematic in linux.

[bailey]

127.0.0.1 is your local nic address for loop-back test

[StormRavn]

well i am usin a D Link nic card
intel 800 mhz cpu
512 mb of ram
on board video/sound
(hewelt packard pc)

[StormRavn]

it just keep tellin me my nic isnt present so UGH!!!

[kilgoretrout]

Give the lspci printout; it will give the chipset the card is using. The network config tool is not seeing the card because no driver is loaded for it. Once we know the chipset, loading the driver and configuring the network for dhcp is trivial. I assume this is a pci card, correct me if I'm wrong.

If your not sure how to run lspci in a console, post back and I'll go into more detail.

[StormRavn]

in root when i type #lspci to bring up a list of all my pci items for my ethernet this is what i get

01.0a.0 Ethernet Controller D-Link System Inc Rth8139 Ethernet (rev10)

i hope this is what ya wanted to see kilg hopefully you can tell me what i can type or do to make this work

[kilgoretrout]

Let's try to get the driver loaded first. I'll just skip the config tools for now. doing this by hand isn't that hard. Open a console and run:

$ su
[enter root password]
# /sbin/ifconfig

You should get some printout relating to your present network configuration. there should be one entry for "lo" and nothing for "eth0". If that's not the case post your printout. If you have something for eth0, the wrong driver is probably loading in all likelyhood and we have to remove it first.

If you only have "lo" then you need to load your nic driver. You do so with this command:

# modprobe 8139too

Then run ifconfig again and see if you get some printout for eth0.

[StormRavn]

thankx its a runnin very well i ended up takin out the nic card and tryin the onboard ethernet port and a fresh install it fired right up selected my modem and ip addy that wasnt my windows box and worked just fine then had to go through all the fun of updating all the various packages but thank you much for all the help and support you gave me lots of ideas to make it all work
=)

[kilgoretrout]

Glad it worked. The onboard nic was the problem. The autoconfig tools never seem to work right when two nics are present. I've always had to do that by hand when two nics are present. Good luck to you in your linux adventures.

[StormRavn]

yea i know so far it is a interesting OS to play around with i am havin fun goin through all the menus and various features

but once again thankx for the help