LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 06-26-2003, 06:59 PM   #1
delipsingh
LQ Newbie
 
Registered: Jun 2003
Posts: 2

Rep: Reputation: 0
RedHat Linux8.0 giving problem with RealTek 8139 Ethernet card


I installed RedHat Linux 8.0 on HP Pavilion XT936 pc, which has RealTek 8139D chipset on motherboard. But Linux never recognized it on installation (I tried doing multiples installations). Then I added one more Realtek NIC card on PCI slot, but it didn't recognizes it also. RedHat 8.0 has driver for Realtek (8139too.o).
But the driver never got installed. So after few retries with installations, I decided to install the driver manually.

Ifconfig never show me eth0 or eth1, so this is what I followed -
1. #lspci (to find if they are on my pci bus)
And I got -
00:0d.0 Ethernet controller: RealTek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:10.0 Ethernet controller: RealTek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)

2. #lsmod (to find out if drivers are installed)
It didn't show any 8139too entry, which means drivers were not installed.

3. Then I just tried to look into /etc/modules.conf and /etc/sysconfig/network-scripts and didn't find respective entries.

So now I installed the driver manually and did following -
1. #modprobe 8139too
2. lsmod (this time it showed me entry for 8139too)
3. Added line "alias eth0 8139too" in /etc/modules.conf file
4. Created ifcfg-eth0 file in /etc/sysconfig/network-scripts dir as -
DEVICE=eth0
BOOTPROTO=dhcp
ONBOOT=yes
5. #service network restart (to restart the network service)
6. #ifup eth0
It failed to connect to dhcp server
Since eth0 was not up, so I got following errors -
SIOCADDRT: Network unreachable on #route add default gw 192.168.1.1
Connect: Network unreachable on #ping 192.168.1.1

There is no problem with my dhcp server. My same m/c get ip address from dhcp server when i start windows on it.

Now I thought of adding the second NIC and specify static ip to it. So I added new hardware device using GUI (Syaytem Settings->Network) and assigned ip address to it.

Now I was able to add default route and no more SIOCADDRT errors. But still am not able to ping the gateway itself.

Ifconfig now shows both eth0 and eth1 as -eth0 Link encap:Ethernet HWaddr 00:40:2B:13:64:5E
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xd000

eth1 Link encap:Ethernet HWaddr 00:02:E3:0F:82:CD
inet addr:192.168.1.241 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xf400

BUT AM STILL NOT ABLE TO PING ANY MACHINE . I am getting this error -
PING 192.168.1.1 (192.168.1.1) from 192.168.1.241 : 56(84) bytes of data.
From 192.168.1.241 icmp_seq=1 Destination Host Unreachable
From 192.168.1.241 icmp_seq=2 Destination Host Unreachable
From 192.168.1.241 icmp_seq=3 Destination Host Unreachable

Still eth0 is not able to get ip address from dhcp server and i cannot even use eth1 (which has static ip 192.168.1.241)

I am beating my head for last two days to solve this issue, but failed. Looks like some driver related problem.

Any help in this regard is highly appreciated.

Thanks,
Delip
 
Old 06-27-2003, 07:15 AM   #2
certifiableone
LQ Newbie
 
Registered: Jun 2003
Location: West Porter's Lake, Nova Scotia Canada
Distribution: Suse
Posts: 7

Rep: Reputation: 0
Hi Delip,

It seems you and I are having close to the same problem and I can't get anyone to help me out either. I think I may have made a bad post but hey, I'm new at this.

I have an onboard Realtek 8139. When I do the installation Suse 8.2 picks up the network card and installs it. But it will not function. I cannot ping the gateway or the dhcp server.

Everything seems to be functioning perfectly except I can't get an IP address. The same network card works beautifully in Suse 8.1!

When I run etc/init.d/network start (or restart) I am notified that everything is running fine. When I run ifconfig I get the same output that you do. Have you had any success at all?

Thanks
 
Old 06-27-2003, 09:56 AM   #3
Blindsight
Member
 
Registered: Mar 2003
Distribution: Slackware
Posts: 234

Rep: Reputation: 30
eth0 has no ip address assigned to it. Are eth0 and eth1 on the same colision domain? what's your output of route -n?

until ($information)
{ print "Impossible to continue.\n"; }
 
Old 06-27-2003, 04:20 PM   #4
delipsingh
LQ Newbie
 
Registered: Jun 2003
Posts: 2

Original Poster
Rep: Reputation: 0
Not RTL8139 problem, but other

eth0 has no ip address assigned because it failed to get one from dhcp server. eth1 has a statically assigned ip.

I explored the porblem lil more and here are findings -

1. The problem is not with RTK 8139 driver. I tried puting DLink and Intel cards also, but nothing works. The 8139too.o supplied with RedHat 8.0 is just fine.

2. I tried to capture the trace over wire and got some surprising stuff. When i do ifup eth0, I can see dhcp request going out (broadcast 255.255.255.255) and my dhcp server running on 192.168.1.1 sends back the dhcp reply with client address as 192.168.1.174. But the response never reaches ifup, so it keep trying and finally gave up displaying "FAILED" message.

3. If I disbale eth0 and try to ping 192.168.1.1 via eth1, I always get "Destination Unreachable". The routing table is fine and it has entry for default route. The surprising part is that this time I don't see any packets on wire.

So am not able to understand where the problem is. Is it realted with IRQs? I even added the "options eth0 io=0x1800 irq=5" in /etc/modules.conf There are the values i got from "lspci -v"

The IRQ 5 is shared between my two NICs and a sound card on board. I even tried t by disabling the sound card from BIOS, but no luck.

Is there someone to help me out. I can provide as much info you want. I already wasted 3 days debugging it.

DS
 
Old 06-27-2003, 04:34 PM   #5
Looking_Lost
Senior Member
 
Registered: Apr 2003
Location: Eire
Distribution: Slackware 12.0, OpenSuse 10.3
Posts: 1,120

Rep: Reputation: 45
I had similar problems when I added a second card on Red Hat 9 - it got itself in allsorts of a mess. Tried everything, eventually tried using the GNOME network panel, put the settings in there then bound the MAC addresses to each appropriate interface. Rebooted and it started working. Maybe help.
 
Old 07-03-2003, 07:05 AM   #6
DBA_Frog
LQ Newbie
 
Registered: Jul 2003
Posts: 8

Rep: Reputation: 0
You guys aren't ALONE... I have a Realtek NIC card on my RH9 system. I am going Batty trying to get the WebServer up and running.

I can ping my WebServer in the LAN, but CANNOT get thru the ROUTER to my Site from the WAN. I get a DNS \ SERVER unavailable error. I have opened the Router Path, but NO JOY.

I think I am having NIC problems. Even tho it is working locally, I don't think it is properly accepting WAN requests.

I'm going to pull this card and try another card in the system.
 
Old 07-03-2003, 07:25 AM   #7
certifiableone
LQ Newbie
 
Registered: Jun 2003
Location: West Porter's Lake, Nova Scotia Canada
Distribution: Suse
Posts: 7

Rep: Reputation: 0
I think there is a real problem with these onboard Realtek lan chips. I am having similar problems with my Windows 2000 Pro system (I have a dual-boot system - 2000 and Linux). Sometimes when I am in 2000 the internet connection just quits. I do an ipconfig /all and it shows I have an IP address and that everything is A-OK but I can't connect. When I reboot the machine I am given an Automatic IP Address. The only way I can reconnect is to go into my device manager, remove the NIC and then allow plug and play to reinstall it on reboot. Then everything is back to normal. Go figure.
 
Old 07-03-2003, 12:10 PM   #8
DBA_Frog
LQ Newbie
 
Registered: Jul 2003
Posts: 8

Rep: Reputation: 0
I feel better after reading this thread... I was ready to beat my Router with a PENGUIN (lol) for not behaving.

Seriously, I thought I was having problems with my DLINK Di-614+ router interfacing with LINUX. Now, I think it has to do with the admittedly CHEAP Realtec NIC card.
 
Old 08-23-2003, 05:31 AM   #9
JustAGuy
LQ Newbie
 
Registered: Aug 2003
Location: Arizona
Distribution: Mandrake 9.1
Posts: 17

Rep: Reputation: 0
RE: RedHat Linux8.0 giving problem with RealTek 8139 Ethernet card

Hmm. hey guys!

I thought I would add my two cents to the subject.

Has anyone tried switching the DCHP client? I had the same issue with a pair of 8139 cards and Mandrake SNF. I narrowed down the issue by obtaining my "current" DCHP IP address with a Windows box, then switched to Linux and set the interface to the same IP address- static. That got the interface running successfully, which gave me a clue that the issue was not with the card drivers. I then tried switching the DHCP client from "pump" to other clients, finally getting it working with "dhclient"

I do not know why some DHCP clients work, and others don't (it may be a ISP issue in my case), but I hope this will help.
 
Old 08-23-2003, 06:12 AM   #10
hornokplease
LQ Newbie
 
Registered: Jul 2003
Location: Bombay
Distribution: Gentoo
Posts: 21

Rep: Reputation: 15
I have two Realtek 8139 and am using RedHat 9 and am new to linux.

Initially after reading the manuals i managed to get them to work once and had to reconfigure on each reboot. In fact RH9 used to often recognise the card as Fealnx and one other card type which I forget. Finally now my network doesn't work.

I have read all posts and all manuals. I am currently thinking of switching to gentoo since they work fine on the live cd just before installation.

Best of luck.
 
Old 09-01-2003, 02:18 AM   #11
atsol
LQ Newbie
 
Registered: Sep 2003
Distribution: Mandrake
Posts: 1

Rep: Reputation: 0
I am having the same problems with this card. For 3 days now I had no luck with it. So is this issue resolved? I have tried to disable
the on-board card and add a PCI 3Com which I know it works (it works on other PCs) but again the same problem. The dhclient command tries a few times and after it returns "NO DHCP OFFERS received, No working leases in persistent database - sleeping".

Of course the DHCP server is running OK as other PCs get an IP succesfully.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Ethernet Card Realtek 8139 not working on MDK 10.1 community [MDK]NooB Mandriva 3 05-10-2005 02:54 PM
problem with two realtek 8139 ethernet cards w3bbuilder Linux - Newbie 1 08-15-2003 03:46 PM
Realtek / Asound 8139 Network Card with Redhat 8.0 jamesonq Linux - Networking 6 04-06-2003 10:44 PM
Problem activatign eth0 Realtek 8139 Redhat 8.0 stunhcterts Linux - Software 12 04-02-2003 04:34 PM
realtek 8139 ethernet port problem. poortl9109 Linux - Networking 10 01-09-2003 11:07 AM


All times are GMT -5. The time now is 06:34 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration