You are not logged in.
I did a clean Arch Install. Then i installed KDE and then networkmanager & then nm-applet(network manager client for gnome). Started the applet as normal user & I got the DHCP Server reply & ip was assigned & everything worked perfectly.
Thats the good part of story.
But, then I ran pacman -Syu & holy shit! dhcpcd stopped working (the sole reason i reinstalled my 3yrs old arch)
my pacman log :- pacman -Syu done at 762 - http://pastebin.com/U0Le9EQX
dhcpcd output before upgrade http://pastebin.com/ePNVScxe
dhcp lease dump:- http://pastebin.com/M3sJAHCJ
I have been struggling since last two days and have been trying to ask in IRC too but no success.
Is there a workaround to get my net working again. I am on ASDL conenction
Last edited by shadyabhi (2010-11-02 02:35:14)
My blog:-
http://blog.abhijeetr.com
Offline
This was the post I did yesterday https://bbs.archlinux.org/viewtopic.php?id=107574
I failed to find a solution. As I knew that ubuntu does that without issues, I decided to reinstall arch. I did a clean install but as I said, that dhcpcd bug was reproduced again by doing pacman -Syu
My blog:-
http://blog.abhijeetr.com
Offline
PLs see the last 4 comments of http://bugs.gentoo.org/show_bug.cgi?id=331415
May be its related to kernel upgrade. I am no expert.
My dhcpcd returned me address even after line 756 http://pastebin.com/U0Le9EQX . That means its not issue dhcpcd upgrade
My blog:-
http://blog.abhijeetr.com
Offline
If I understand you correct. everything was working like this (http://pastebin.com/ePNVScxe) until you did pacman -Syu...
Whats the output of "sudo dhcpcd -d eth0" now? And what is "ifconfig" showing? perhaps your networking card is not recognized by default in the new kernel?
Last edited by toffyrn (2010-11-01 10:39:56)
Offline
dhcpcd[2204]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[2204]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[2204]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[2204]: eth0: rebinding lease of 123.237.133.195
dhcpcd[2204]: eth0: sending REQUEST (xid 0x76235ad), next in 3.87 seconds
dhcpcd[2204]: eth0: sending REQUEST (xid 0x76235ad), next in 7.98 seconds
dhcpcd[2204]: eth0: broadcasting for a lease
dhcpcd[2204]: eth0: sending DISCOVER (xid 0xaa575221), next in 4.50 seconds
dhcpcd[2204]: eth0: sending DISCOVER (xid 0xaa575221), next in 8.28 seconds
dhcpcd[2204]: eth0: sending DISCOVER (xid 0xaa575221), next in 16.12 seconds
dhcpcd[2204]: timed out
And to make a point about my eth0 not being detected, I can see RX bytes & TX bytes with a finite value in the output of ifconfig.
My blog:-
http://blog.abhijeetr.com
Offline
And what is "ifconfig" showing?
Offline
[shadyabhi@ArchLinux ~]$ sudo dhcpcd -d eth0
Password:
dhcpcd[2030]: version 5.2.8 starting
dhcpcd[2030]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd[2030]: eth0: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd[2030]: eth0: reading lease `/var/lib/dhcpcd/dhcpcd-eth0.lease'
dhcpcd[2030]: eth0: discarding expired lease
dhcpcd[2030]: eth0: broadcasting for a lease
dhcpcd[2030]: eth0: sending DISCOVER (xid 0xbf0b7d19), next in 3.11 seconds
dhcpcd[2030]: eth0: sending DISCOVER (xid 0xbf0b7d19), next in 8.75 seconds
dhcpcd[2030]: eth0: sending DISCOVER (xid 0xbf0b7d19), next in 16.21 seconds
dhcpcd[2030]: eth0: sending DISCOVER (xid 0xbf0b7d19), next in 31.18 seconds
dhcpcd[2030]: timed out
[shadyabhi@ArchLinux ~]$ sudo /sbin/ifconfig
eth0 Link encap:Ethernet HWaddr 00:19:D1:3C:74:6E
inet6 addr: fe80::219:d1ff:fe3c:746e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7131 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:471663 (460.6 Kb) TX bytes:2632 (2.5 Kb)
Interrupt:20 Memory:90300000-90320000
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:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:240 (240.0 b) TX bytes:240 (240.0 b)
[shadyabhi@ArchLinux ~]$
/var/log/messages while using nm-applet http://pastebin.com/LEpRkSMx
The name of my connection in nm-applet is Reliance
My blog:-
http://blog.abhijeetr.com
Offline
I don't have much knowledge about ipv6. But it looks somehow like you are connected to a local ipv6 address: "fe80::219:d1ff:fe3c:746e/64", but not to any ipv4 address.
If dhcp didn't get anything it all, shouldn't the ipv6 field be empty as well?
Offline
I don't have much knowledge about ipv6. But it looks somehow like you are connected to a local ipv6 address: "fe80::219:d1ff:fe3c:746e/64", but not to any ipv4 address.
If dhcp didn't get anything it all, shouldn't the ipv6 field be empty as well?
As I observed in windows, it said for ipv4, connectivity as INTERNET.
for ipv6, it said LOCAL.
My blog:-
http://blog.abhijeetr.com
Offline
From personal experience, I can tell you that the 2.6.35 kernel(arch's current kernel) breaks some, but not all, onboard intel gigabit ethernet adapters that use the e1000e driver module. If that's the nic you have, this is undoubtedly your problem. It is definitely an upstream kernel issue as I've seen similar reports on both the gentoo and aptosid forums and the problem goes away with the 2.6.36 kernel. The 2.6.36 kernel is in the Arch testing repo at the present time.
Last edited by kilgoretrout (2010-11-01 16:39:00)
Offline
From personal experience, I can tell you that the 2.6.35 kernel(arch's current kernel) breaks some, but not all, onboard intel gigabit ethernet adapters that use the e1000e driver module. If that's the nic you have, this is undoubtedly your problem. It is definitely an upstream kernel issue as I've seen similar reports on both the gentoo and aptosid forums and the problem goes away with the 2.6.36 kernel. The 2.6.36 kernel is in the Arch testing repo at the present time.
Problem SOLVED...
Thanks kilgoretrout. You are a life saver!!!
My blog:-
http://blog.abhijeetr.com
Offline