Internet not working, though KNetworkmanager says connected

[corrupt-reaper]

Hi first post to these here forums. Just bought this new laptop Acer aspire 3050. Just installed 64bit Hardy on it, the only way i could get this to install was to pass the kernel option "acpi=off" .
The problem lies here with the RTL-8139/8139C/8139C+ ethernet card. Knetworkmanager says im connected via dhcp, but yet cant even ping the router (Linksys WRT54G)im connected to. Now ive tested the cable so i know its not that. After reading other posts i came across an article about problem with having the 8139cp & 8139too modules loaded. Not sure if this is a problem. hope fully from this info im about to give you, could please help.

lsmod | grep 8139 gives me:

8139cp 27776 0
8139too 31104 0
mii 7552 2 8139cp,8139too

now im not sure exactly what this means but is this a module fault, i had a quick look and is the mii module for sound?

ifconfig gives me:

eth0 Link encap:Ethernet HWaddr 00:1b:24:72:d2:46
inet6 addr: fe80::21b:24ff:fe72:d246/64
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Rx packets:27 errors:0 dropped:0 overruns:0 frame:0
Tx packets:96 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:730 (730.0 B) TX bytes:2885 (2.8KB)
Interrupt:16 Base Address:0xa000

eth0:avahi Link encap: Ethernet HWaddr 00:1b:24:72:d2:46
inet addr:169.254.6.96 Broadcast: 169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:16 Base Address:0xa000

lo Link encap: Local Loopback
inet addr:127.0.01 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packet:79 errors:0 dropped:0 overruns:0 frame:0
TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7380(7.2KB) TX bytes: 7380(7.2KB)

now to me this would seem to suggest that im using an ipv6 address, now ive read on other posts this would not make a difference, if commented it out in the /etc/modprobe.d/aliases but to no avail.

also i have no idea what connection eth0:avahi is. but it does display the ip worng as it should be 192.168.1.100-199. But Knetworkmanager displays my ip as 0.0.0.0.

dhclient gives me:

Listening on LPF/eth0/00:1b:24:72:d2:46
Sending on LPF/eth0/00:1b:24:72:d2:46
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.1.103 from 192.168.1.1
DHCPREQUEST of 192.168.1.103 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.103 from 192.168.1.1
bound to 192.168.1.103 -- renewal in 41405 seconds

now this seems to me the dhcp transaction is working alright, am i right in saying this.

The hardware of the laptop
AMD64 K8 Sempron @ 2.0Ghz
1Gb DDR2 RAM
80Gb SATA HDD
DVD-RW DL Superdrive
Atheros Wireless - I'll worry about that later :(
Realtek 8139/8139C/8139C+ (Rev 10) Ethernet Controller
HDA Intel Sound

Any Ideas please

[Detonate]

I ran into this same exact problem yesterday on a fresh install of Kubuntu. I do not know what eth0:avahi is either. I did not take the time to trouble shoot the problem thoroughly, and did not find a solution. But to add to the information, this is a fresh install of 32 bit Kubuntu on a computer with a P4 processor and the onboard ethernet is Realtek. The IP address reported is strange, I got the same one, certainly it was not provided by my router.

I had a Linksys PCI ethernet card in my parts box, so I disabled the onboard ethernet and installed that card and now everything works great It is seen as eth1. But if I could get the onboard ethernet working I could get my card back.

[corrupt-reaper]

so you reckon a fault with the card is the cause?

[Detonate]

No. See this post. I have not tried it yet, but seems to make sense. I don't have time to work on it right now, but I will try it tonight and see what happens.

http://omingo.zorngrid.com/

[corrupt-reaper]

thanks everyone for the help, i phoned up acer in the end...
they have apparently bugged the bios so the acpi calls wont work unless you are running windows, so as i didnt wmi installed on the system, thats why it hung at boot.

solved the problem(ish) passed the kernel argument acpid=off rather than acpi=off which in contrast disables everything grrrr....

again thanks for the prompt help you guys