[solved] Can't connect to network with 64-bit kernel

jc · 2012-06-12 05:03:03

On 64-bit Arch Linux, I can't get any network access. On 32-bit Arch Linux, I can connect to my router with an ethernet cable or a wireless card using dhcpcd or networkmanager.

In 64-bit, I have tried
- Upgrading my kernel from 3.3.8 to 3.4.2 from the testing repos
- Getting networkmanager-git from AUR
- Using the r8168 driver for my ethernet card (which is actually exactly the same one as the one from https://wiki.archlinux.org/index.php/Co … k_messages )

But I haven't been able to get "dhcpcd eth0" to tell me anything but

dhcpcd[677]: eth0: sending IPv6 Router Solicitation
dhcpcd[677]: eth0: broadcasting for a lease
dhcpcd[677]: eth0: sending IPv6 Router Solicitation
dhcpcd[677]: eth0: sending IPv6 Router Solicitation
dhcpcd[677]: eth0: sending IPv6 Router Solicitation
dhcpcd[677]: eth0: no IPv6 Routers available

while "dmesg | tail" fills with

eth0: no IPv6 routers present
eth0: no IPv6 routers present
eth0: no IPv6 routers present

My rc.conf has the correct settings for dhcp:

interface=eth0
address=
netmask=
broadcast=
gateway=

I can get whatever 64-bit packages I need to get the internet to work in 64-bit linux by downloading them in 32-bit linux and then upgrading to 64-bit linux.

My goal is to get networking to work on 64-bit linux through either eth0 or wlan0 (eventually I'll need wlan0 but right now neither works, so if one starts working, the other probably will), or for someone to say "It's impossible dude, go download opensuse and see if you get a different damning error over there".

Happy trails,
jc

Last edited by jc (2012-06-13 23:21:31)

ewaller · 2012-06-12 05:18:02

Are you doing this on the same computer with different kernels?
Are you sharing /etc between the 32 and 64 bit kernels?

Can you post your 64 bit system's /etc/dhcpcd.conf file?
On your 64 bit system, what is the output of ip addr
What is the version of your 32 bit kernel?

Have you tried dhclient instead of dhcpcd ?

jc · 2012-06-12 05:35:37

ewaller wrote:

Are you doing this on the same computer with different kernels?

Yep.

Are you sharing /etc between the 32 and 64 bit kernels?

Yes. Networking doesn't work on the 64-bit install disk either though, which obviously doesn't share its /etc with anything.

Can you post your 64 bit system's /etc/dhcpcd.conf file?

hostname
option domain_name_servers, domain_name, domain_search, host_name
option classless_static_routes
option ntp_servers
option interface_mtu
require dhcp_server_identifier
nohook lookup-hostname
noipv4ll

On your 64 bit system, what is the output of ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
        valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 14:da:e9:0f:69:85 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::16da:e9ff:fe0f:6985/64 scope link
        valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether e0:69:95:d3:7e:e9 brd ff:ff:ff:ff:ff:ff

What is the version of your 32 bit kernel?

3.3.8

Have you tried dhclient instead of dhcpcd ?

I have. No cake.

ewaller · 2012-06-12 05:58:05

I'm stumped. It looks like your system is not even trying to get an IP 4 address. My major concern was you would have 32 bit executables in a 64 bit environment, but you say you've the same problem with the 64 bit install disk. I assume that means just the bare bones disk and the tools on that iso; not a chroot into your system from that boot disk.

Gcool · 2012-06-12 06:25:21

The "eth0: sending IPv6 Router Solicitation" messages can safely be ignored. It just means that dhcpcd is trying to find ipv6 routers on the link (on top of the normal ipv4 broadcast).

As for the issue at hand, what happens if you try with a static ip setup (just to pinpoint the issue to either dhcp or "elsewhere")?

jc · 2012-06-13 00:50:36

Gcool wrote:

As for the issue at hand, what happens if you try with a static ip setup (just to pinpoint the issue to either dhcp or "elsewhere")?

I had my router give a dhcp reservation to eth0, and set the settings in rc.conf to

interface=eth0
address=192.168.0.101
netmask=255.255.255.0
broadcast=
gateway=192.168.0.1

to match the dhcp reservation. I couldn't ping the router.

ewaller wrote:

My major concern was you would have 32 bit executables in a 64 bit environment

Rumor has it lib32-glibc mitigates that. What does lib32-glibc do exactly?

In other news, I'm looking at what it would take to build a kernel from ABS in case this is some freak bug in the kernel that I can fix just by using some other kernel.

ewaller · 2012-06-13 02:02:44

jc wrote:

ewaller wrote:
My major concern was you would have 32 bit executables in a 64 bit environment
Rumor has it lib32-glibc mitigates that. What does lib32-glibc do exactly?

I don't think this migration is a simple as you think it is. Just a hunch

Last edited by ewaller (2012-06-13 02:03:11)

jc · 2012-06-13 23:20:50

ewaller wrote:

jc wrote:
ewaller wrote:
My major concern was you would have 32 bit executables in a 64 bit environment
Rumor has it lib32-glibc mitigates that. What does lib32-glibc do exactly?
I don't think this migration is a simple as you think it is. Just a hunch

That page is the rumor that has it :]

I fixed the problem by disabling IOMMU in by bios.

Edit: No idea what IOMMU is either by the way.

Edit: Updated my bios and now I can enable IOMMU.

Last edited by jc (2013-02-23 19:48:00)

humilleitor · 2012-09-09 14:32:38

Same problem here. I'm trying to install Arch with the 2012.08.04 dual iso but it fails at wireless network connection. It happens the same whether I boot in 32 or 64 bit modes. When trying to netcfg (after setting up the ESSID and password, of course, and stopping the network daemon), after some seconds of "BUSY" state, it ends up with a "dhcp ip lease failed", and the /var/log/everything.log reports "no ipv6 routers present", then a timeout.

Relevant info: my router works flawlessly with all of my hardware and software, other Linux versions, and even some previous Arch installations I've had in this same computer.
I haven't tried assigning to my machine a fixed IP address in the router, but I will not do it. I reckon it would work, but this post is not a request for help: I'm positive that there is a bug (or misbehaviour, if it makes developers happier) in the network connection software in this release. I'm only posting here for confirming the OP's issue.

By the way: if I do a "netcfg <myWireless>" just after booting the install disk and configuring <myWireless>, I get a false connection success: netcfg reports "DONE", but there is no connection. It's necessary to do first a "/etc/rc.d/network stop" for it to actually _try_ connecting. If some responsible is reading this, I suggest to include this step (stopping the network daemon) in the documentation, because otherwise, for a non-expert, it may be close to impossible to find out why his connection doesn't work after having got a "DONE" report.

Last edited by humilleitor (2012-09-09 14:52:09)

Arch Linux

#1 2012-06-12 05:03:03

[solved] Can't connect to network with 64-bit kernel

#2 2012-06-12 05:18:02

Re: [solved] Can't connect to network with 64-bit kernel

#3 2012-06-12 05:35:37

Re: [solved] Can't connect to network with 64-bit kernel

#4 2012-06-12 05:58:05

Re: [solved] Can't connect to network with 64-bit kernel

#5 2012-06-12 06:25:21

Re: [solved] Can't connect to network with 64-bit kernel

#6 2012-06-13 00:50:36

Re: [solved] Can't connect to network with 64-bit kernel

#7 2012-06-13 02:02:44

Re: [solved] Can't connect to network with 64-bit kernel

#8 2012-06-13 23:20:50

Re: [solved] Can't connect to network with 64-bit kernel

#9 2012-09-09 14:32:38

Re: [solved] Can't connect to network with 64-bit kernel

Board footer