Linux Help
guides forums blogs
Home Desktops Distributions ISO Images Logos Newbies Reviews Software Support & Resources Linuxhelp Wiki

Welcome Guest ( Log In | Register )



Advanced DNS Management
New ZoneEdit. New Managment.

FREE DNS Is Back

Sign Up Now
 
Reply to this topicStart new topic
> Install rtl8139 on Debian 5 Lenny
rivetlust
post Apr 24 2009, 02:58 PM
Post #1


Whats this Lie-nix Thing?
*

Group: Members
Posts: 3
Joined: 24-April 09
Member No.: 14,418



I'm having trouble installing a Linksys FA311 which is a Realtek 8139C rev 10 chipset as recognized by lspci.

#modprobe --first-time 8139too

...shows that the module is already in the kernel. I tried booting off the Debian net-inst CD, but it didn't seem to see the Realtek NIC.

I'm afraid I'm a little new at installing networking hardware under Linux. Can someone point me in the right direction?

I'm setting up my first Linux based router and getting stuck pretty badly. Any help is appreciated.
Go to the top of the page
 
+Quote Post
michaelk
post Apr 24 2009, 05:31 PM
Post #2


Its GNU/Linuxhelp.net
*******

Group: Support Specialist
Posts: 1,797
Joined: 23-January 03
Member No.: 360



look at the output of the lsmod command. Is the module loading?
Look at the output of the dmesg command. Is the adapter being recognized.
Look at the output of the command ifconfig -a. Is there some ouput for all the adapters?
Go to the top of the page
 
+Quote Post
rivetlust
post Apr 25 2009, 04:14 AM
Post #3


Whats this Lie-nix Thing?
*

Group: Members
Posts: 3
Joined: 24-April 09
Member No.: 14,418



lsmod output shows:

8139too 20320 0
mii 4896 3 8139cp,e100,8139too

ifconfig -a includes the onboard Intel ethernet and a third party PCMCIA wireless card but not the rtl8139

dmesg shows the following output for 8139:

[ 2.216417] 8139too Fast Ethernet driver 0.9.28
[ 2.609637] 8139too 0000:01:04.0: region #0 not a PIO resource, aborting
[ 2.612880] ACPI: PCI Interrupt 0000:01:07.2[C] -> GSI 16 (level, low) -> IRQ 16
[ 2.665739] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16] MMIO=[e800a000-e800a7ff] Max Packet=[2048] IR/IT contexts=[4/4]
[ 2.672895] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 2.675121] 8139cp 0000:01:04.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
[ 2.675172] 8139cp 0000:01:04.0: Try the "8139too" driver instead.

I thought 8139too was already present.

[edit]

So I did the sensible thing and added 8139too to /etc/modules and the output has changed a bit, but it's still not working:

dmesg says:

[ 2.214953] 8139too Fast Ethernet driver 0.9.28
[ 2.574632] 8139too 0000:01:04.0: region #0 not a PIO resource, aborting
[ 2.574744] ACPI: PCI Interrupt 0000:01:07.2[C] -> GSI 16 (level, low) -> IRQ 16
[ 2.627573] ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[16] MMIO=[e800a000-e800a7ff] Max Packet=[2048] IR/IT contexts=[4/4]
[ 2.638474] 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 3.440871] 8139cp 0000:01:04.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
[ 3.440921] 8139cp 0000:01:04.0: Try the "8139too" driver instead.


modprobe output is as follows:

[hostname]:~# modprobe --first-time 8139too
FATAL: Module 8139too already in kernel.

I just read something about PIO versus MMIO so I'm going to go check it out. What little I saw was way over my head.

[edit#2]

It turns out I had another card based off the 8139D chipset. Listed as a "Honeywell" or somesuch. On the plus side, it looks like the 8139too driver loads without complaining at all. On the downside, the interface doesn't appear in ifconfig -a output.

[edit#3]

Okay, well looks like I was mistaken. The second 8139D card gives the same output as the first one. Turns out shutdown -h does something different than simply rebooting the poor box. The output is exactly the same, except how the card identifies.
Go to the top of the page
 
+Quote Post
michaelk
post Apr 25 2009, 08:59 AM
Post #4


Its GNU/Linuxhelp.net
*******

Group: Support Specialist
Posts: 1,797
Joined: 23-January 03
Member No.: 360



You might need to specify the module for the second card as an alias to force it to use the 8139too
http://www.usenet-forums.com/linux-network...ot-working.html

Typically network cards are recognized first in order of card slot # and last the built in motherboard adapter.
Just for some more info post the output of the lspci command for both adapters.
Go to the top of the page
 
+Quote Post
rivetlust
post Apr 27 2009, 09:20 AM
Post #5


Whats this Lie-nix Thing?
*

Group: Members
Posts: 3
Joined: 24-April 09
Member No.: 14,418



I am completely and utterly dumbfounded. In a drunken fit, I installed BSD thus trashing my Debian installation (along with me entire /var/www/ directory, thank goodness for backups). BSD saw the Realtek with no problem whatsoever. So I installed Debian again. The net install CD is not only able to see the Realtek, it is currently installing Debian over the 'net.

I don't know what to say. It works now and I hope it works after the install finishes. Just in case anyone runs in to this exact same problem, I'm going to follow up after the install completes. I wish I could give a more definitive step-by-step on how this got to work, but I'm afraid I'll have to defer to "magic".

Thank you very much for your help, Michael. It was very much appreciated.
Go to the top of the page
 
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 22nd October 2017 - 02:25 PM