iB::Topic::another ethernet problem...

	Damn Small Linux :: Damn Small Linux Board The DSL Forums

» Welcome Guest
[ Log In :: Register ]

Damn Small Linux Board » Damn Small Linux » Networking » another ethernet problem...

		Mini-ITX Boards Sale, Fanless BareBones Mini-ITX, Bootable 1G DSL USBs, 533MHz Fanless PC <-- SALE $200 each!
		Get The Official Damn Small Linux Book. DSL Market , Great VPS hosting provided by Tektonic

Pages: (3) </ [1] 2 3 >/

[ Track this topic :: Email this topic :: Print this topic ]

Topic: another ethernet problem..., sorry

< Next Oldest | Next Newest >

matrulesok Offline

Group: Members
Posts: 29
Joined: June 2005

Posted: June 30 2005,13:09

I have an old machine -400mhx hp with 64mb ram. It used to run windows 98 and connect to internet via dialup and more recently usb broadband.
Yesterday i replaced the analogue modem with a (cheap unbranded) ethernet card. Windows connected fine via the router.
Next I installed red hat 9 - too slow, so i came here! DSL is up and running ok, but has never connected to the net. I have also tried it from my main machine which uses a broadcom ethernet controller built into the motherboard (abit KD7-S).
So I assume that because other O/s's using the same lan cable can access the net it is a matter of making DSL configure the ethernet controller.
I have searched and not got very far (mainly because I am not entirely sure what im searching for). So I would be grateful for any help.
As stated above I dont have any info on the ethernet card, but if there is a command i can use to get info, i can do that.
thanks in advance for any help!

hawki

Group: Members
Posts: 175
Joined: Jan. 2004

Posted: June 30 2005,15:56

Hi
There are lots of reasons it's not working. The default boot up looks for and tries to load the modules for your net card. It then tries to start the net card and use DHCP to get it's address.

To see if it found your card at a shell prompt type

dmesg

look for messages that mention eth0. That should let you know if it was found.

Next at a shell prompt type

ifconfig

If eth0 was started you should see information about your net card.

If it is started and does not have an address it did not receive an address using DHCP.

If that is the case you probably net to set the address using the netcardconfig script.

good luck

matrulesok Offline

Group: Members
Posts: 29
Joined: June 2005

Posted: June 30 2005,16:23

thanks hawki, ill let you know, gotta go out now, but i will try later!

matrulesok Offline

Group: Members
Posts: 29
Joined: June 2005

Posted: June 30 2005,21:52

Ok, here are the relavent responces....

dmesg - eth0 appears in the middle and all seems well, then the last 5 lines contain things such as "transmit time out"

Ifconfig - eth0 does not appear until "ifconfig eth0 up" is run, then there is no assigned ip address.

netcardconfig - failed.

pinging my router fails because "network unreachable".

So I guess there is a problem with this DHCP thingamboby.....I belive that this lan cable is always assigned the same ip, so i assume that this is a static ip, does this make a difference?? Thanks for any further info!!

hawki

Group: Members
Posts: 175
Joined: Jan. 2004

Posted: July 01 2005,12:54

Hi

I'm not sure what you mean about
netcardconfig - failed

My guess is that either your cable connection is not working or your router is not configured to assign addresses correctly.

You can further test your netcard by assigning it an address with the netcardconfig script in DSL panel.

Set it to something like 192.168.0.10

Then at a shell prompt type

sudo ping 192.168.0.10
ctrl-c to end

If that works your netcard should be functional.

You will then have to troubleshoot the cable and router.
good luck

12 replies since June 30 2005,13:09

< Next Oldest | Next Newest >

[ Track this topic :: Email this topic :: Print this topic ]

Pages: (3) </ [1] 2 3 >/

Damn Small Linux Board » Damn Small Linux » Networking » another ethernet problem...