Hi

There seems to be some trouble with 8139too not working in a previous post. Has anyone found a solution to this? ubuntu version 2.6.24 (Hardy Heron?). Followed all known possibilities but information is all mostly out of date. module 8139too.ok? does not load. Following makefile on 8139too.c supplied, after altering to suit my version, comes up with 3 pages of errors?.
ifconfig shows nothing for eth0

like the last person markjuggles i have hit a brick wall here. Am I wasting my time?

Thanks puzld

this network card installs perfectly in Debian...all kernels...

No clue of the history here, but I've had one of the cards. A few suggestions:

You don't need anything except the standard kernel module 8139.o IIRC

There are a couple of versions of hardware. Modules differ. Make sure 8129.o is not installed

Check the interrupts. If it's configured to look for e.g. irq 11 and gets irq 10 the card may not work I tried booting with "acpi=off noapic" as boot parameters and that helped. I ran with those for years.

Particularly on Via chipsets, the apic can be broken.

/etc/modprobe.conf should have the line
alias eth0 8139

and it should be initialised at boot

Hi
O.K. some history on this
I am running Ubuntu 8.04 Hardy Heron
I get
system, administration,
network settings,
Point to point connection - shaded out
network tools
loopback interface lo - shaded out

conclusion no driver module installed

ifconfig shows

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:346 errors:0 dropped:0 overruns:0 frame:0
TX packets:346 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:17300 (16.8 KB) TX bytes:17300 (16.9 KB)

lspci shows
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev 03)
00:04.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:04.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:06.0 SCSI storage controller: Adaptec AHA-2940U2/U2W / 7890/7891
00:0b.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 04)
00:0b.1 Input device controller: Creative Labs SB Live! Game Port (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation NV15BR [GeForce2 Ultra, Bladerunner] (rev a4)

What now?
do I deduce that the internet card is not present from this though it is installed and plugged in?

Hi
A bit more

I have what I presume is a kernel module 8139too.ok

if I do
insmod 8139.ok
it returns with an error

So where can I find 8139.o IIRC?

Open a root Terminal. try these

lsmod |grep 8139<or whatever> shows you if the module is in.

modprobe 8139<or whatever> Should show you the module and some feedback from the card.

ifconfig eth0 up Will succeed if the cartd is recognized. It will otherwise give you an error.

grep eth0 /etc/modprobe.conf should show only the line

alias eth0 8139<or whatever>

Tell us what you get.

This is modules and module versions. The best place for information is the kernel build help or the kernel Documentation/ directory. I don't know what 8139too.o is but try it

modprobe 9139too

There's a weird problem with Realtek 8139 chipsets if you ever boot windows. Windows can disable this chipset, so linux doesn't see it.
This even survives "turning off" the PC, (but unplugging it from the wall, and removing battery if it's a laptop, also fixes it (until windows is next run))
See this thread, which has the solution: http://www.linuxquestions.org/questi...roblem-591466/

Hi
Ok This is from the linux pc
looking at the lspci list is the clue I think here, no card was detected.

I took the pc apart again and it was not fully in the slot.
This did not cure the problem though

Put another card in and linux found it
The rest was straight forward from network manager.

Being new to all this I think I did lspci from root originally, that just gave me a list of numbers.

doing the same from user gave readable results so I knew that card was not detected.

Its just taken me 2 weeks of linux reading to get to grips with this. A simple guide would have helped here.

I upgraded to Slack 12.2 over Christmas and could not, in any way, get the 8139 chipset NIC to work. It was recognised in lspci but ifconfig only gave me a "device eth0 does not exist" error message. Drivers were all there, it was included in the kernel, everything was as it should be but the fact remained - no NIC activity! I've been using Slackware for over 4 years and never had this kind of persistant problem before. I struggled on, believing it was something I wasn't doing properly. I worked with the 8139 problem for about 2 days and read hundreds of how-to's and guides, to no avail.

In my frustration I ripped out the 8139 card (which had been working perfectly for over a year in the old system) and replaced it with a D-Link 530TX using the Rhine chipset. This works perfectly from the get-go. So it seems, some people have no trouble, some have a little trouble and the unfortunate ones (me included) have nothing but endless trouble with the 8139 on Slackware 12.

I hope you solve your problem with the 8139. If you want my advice/experience, dump it faster than a cheating girlfriend and use a NIC with a different chipset.

At a quick look, kernel 2.6.21.5 offered the following options

1. 8139cp.ko For Realtek 8139 Rev C+ chips
2. 8139too.ko For (apparently) most Realtek 8139 cards
3. ?? For 'tune twister' Realtek 8139 Rev K chips

I gather the tune twister is some equalisation thing. I gather you may not be able to have module 2 & 3 together.

You want the same interrupt as windows assigns the card, if you have dual boot. There is also an earlier module if your card is very very old.
In /etc/modprobe.d/ you could create a file 'network' with the line

alias eth0 your-module, e.g. 'alias eth0 8139cp'

No need for the '.ko'. If /etc/modprobe.d doesn't exist, the file /etc/modprobe.conf should have the line, and no other reference to eth0.

I am presuming this is eth0 and not a tiny bit of a huge setup! If a module picks it up, there will be a interrupt assigned in 'cat /proc/interrupts'