Hi folks,
I have a problem getting the network controller of my laptop (MEDION
MD9580-F) to work with both, Ubuntu and the latest Debian 4.0. With Debian
3.1, ("Sarge" with kernel 2.4.27) everything works like a charm straight
away.
However, I would still like to try Debian 4.0 as initially intended, but
obviously broken network support spoils the whole thing.
First symptom during both test installations of Ubuntu and Debian was that
DHCP did not work, although I have an otherwise fully functional DHCP
server on my LAN.
So I had to revert to manual network setup with a static address, as both
installers offer. Everything looks good after that:
eth0 Link encap:Ethernet HWaddr 00:30:54:00:2B:EE
inet addr:192.168.254.196 Bcast:192.168.254.255
Mask:255.255.255.0
inet6 addr: fe80::230:54ff:fe00:2bee/64 Scope:Link
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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xa000
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
192.168.254.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.254.1 0.0.0.0 UG 0 0 0 eth0
But a ping to the default gateway fails as shown below:
ubuntu@ubuntu:~$ sudo ping 192.168.254.1
PING 192.168.254.1 (192.168.254.1) 56(84) bytes of data.
From 192.168.254.196 icmp_seq=1 Destination Host Unreachable
in dmesg I then find two rather odd things:
1. "transmit timed out" message:
[17180006.036000] NETDEV WATCHDOG: eth0: transmit timed out
[17180009.036000] eth0: Transmit timeout, status 0c 0005 c07f media 10.
[17180009.036000] eth0: Tx queue start entry 4 dirty entry 0.
[17180009.036000] eth0: Tx descriptor 0 is 0008a03c. (queue head)
[17180009.036000] eth0: Tx descriptor 1 is 0008a03c.
[17180009.036000] eth0: Tx descriptor 2 is 0008a03c.
[17180009.036000] eth0: Tx descriptor 3 is 0008a03c.
[17180009.036000] eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
2. An attempt (!) to load the driver module "8139cp" and an apparently
successfull load of "8139too":
[17179651.188000] 8139cp: 10/100 PCI Ethernet driver v1.2 (Mar 22, 2004)
[17179651.188000] 8139cp: pci dev 0000:00:09.0 (id 10ec:8139 rev 10) is not
an 8139C+ compatible chip
[17179651.188000] 8139cp: Try the "8139too" driver instead.
[17179651.196000] 8139too Fast Ethernet driver 0.9.27
[17179651.196000] PCI: Enabling device 0000:00:09.0 (0000 -> 0003)
[17179651.196000] ACPI: PCI Interrupt 0000:00:09.0[A] -> Link [LNKA] -> GSI
10 (level, low) -> IRQ 10
[17179651.196000] eth0: RealTek RTL8139 at 0xd085a000, 00:30:54:00:2b:ee,
IRQ 10
[17179651.196000] eth0: Identified 8139 chip type 'RTL-8139C'
Very strangely, lsmod showed _both_ driver modules, "8139cp" and "8139too"
as loaded.
Taking eth0 down and unloading both modules and reloading only one and doing
a networking restart did not change anything.
This is what lspci has to say about my onboard network controller:
00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 64, IRQ 10
I/O ports at 1c00 [size=256]
Memory at fc001000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
As I have mentioned, the problem seems to be exactly the same under Ubuntu
and Debian 4.0.
Any suggestions would be greatly appreciated. I am also happy to collect any
additional information and post it here, in order to get this solved, but
due to the lack of a Debian 4.0 live DVD, I can only provide this running
Ubuntu.
Thanks for any help & Kind Regards,
Martin
PS: Happy new year !
|
Similar Threads
Linear Mode
