Skip to contentSkip to conversation

8139too v0.9.17 - w/ 8139B, DFE538TX 10/100 [NOT working]

DISCUSSION Adam 3 participants 3 messages May 10, 2001

lore
Share & tools
lore

Adam

author
#0 lore raw

Using DHCP, on Slackware 7.1 w/ GLIBC 2.2, kernel 2.4.4(and 2.4.5pre1 w/ 8139too.patch to v0.9.17)
---
media is unconnected, link down, or incompatible connection
---

Is the exact message I get, though, with the v0.9.15c version of the driver, my NIC works perfectly fine, should I revert to using kernel 2.4.3 w/ v0.9.15c of the 8139too driver until it is fixed?

If there is anymore information needed to help in possibly fixing the problem I'd be more than glad to oblige.

Signature · 3 lines
Adam
[email protected]
Linux user #190288
#1 lore raw
Quoted 3 lines · Adam

Is the exact message I get, though, with the v0.9.15c version of the driver, my NIC works perfectly fine, should I revert to using kernel 2.4.3 w/ v0.9.15c of the 8139too driver until it is fixed?

Well, if it doesn't work you pretty much have to revert to the older working version. :(

Working on a fix...

Signature · 3 lines
Jeff Garzik      | Game called on account of naked chick
Building 1024    |
MandrakeSoft     |
#2 lore raw

Curious boot problem: linux-2.4.4SMP/AsusTek MB

In reply to Adam

Hi,
A friend of mine uses linux-2.4.4 on his nice dual P3-1000 machine (AsusTek Motherboard). The problem is that the kernel gets stuck at the initialization of the APIC during boottime. The real weird thing is that if he boots linux-2.2.18 and afterwards 2.4.4, the kernel boots properly. So it seems that kernel 2.2 does some "initalization" that helps 2.4.4 to boot.

Does anyone have a clue?

Best Regards,
Hermann

Signature · 4 lines
 ,_,
(O,O)     "There is more to life than increasing its speed."
(   )     -- Gandhi
-"-"--------------------------------------------------------------