New Install Works then Fails

CaptainKirk · 2012-03-21 15:24:07

New install of 64 bit Arch. I turned on the network via dhcpcd eth0 and I was online fine and got my packages etc. I upgraded everything to latest (including removing my locale.sh file I think) and installed Xorg and Xfce. Then I added to /etc/rc.conf:

# DHCP example
# interface=eth0
# address=
# netmask=
# gateway=

interface=eth0
address=
netmask=
broadcast=
gateway=

Which is what my other Arch box on this same LAN has. Now when I reboot I get:

[root@myhost ~]# dhcpcd eth0
dhcpcd[572]: version 5.5.4 starting
dhcpcd[572]: Kernel is not configured to accept IPv6 RAs
dhcpcd[572]: eth0: interface not found or invalid

I removed

interface=eth0

and rebooted, but it's the same. lspci says I have a Realtek Semiconductor Co. RTL8101E/RTL8102E PCI Express Fast Ethernet Controller

I tried modprobe rtl8187se and modprobe 8139too module and then dhcpcd eth0 again but no go.

I rebooted and get this:

[root@myhost ~]# dhcpcd
dhcpcd[572]: version 5.5.4 starting
dhcpcd[572]: Kernel is not configured to accept IPv6 RAs
dhcpcd[572]: no valid interfaces found
dhcpcd[572]: no interfaces have a carrier
dhcpcd[572]: forked to background, child pid 573

I'm lost now.

jdarnold · 2012-03-21 16:10:14

Is eth0 found? Does it show up in dmesg?

$ dmesg|grep eth0
[    4.110085] r8169 0000:0c:00.0: eth0: RTL8168e/8111e at 0xffffc90000c7c000, bc:5f:f4:0b:8a:da, XID 0c200000 IRQ 57
[    4.110087] r8169 0000:0c:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[    6.871535] r8169 0000:0c:00.0: eth0: link down
[    6.871541] r8169 0000:0c:00.0: eth0: link down
[    6.871924] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   11.645141] r8169 0000:0c:00.0: eth0: link up
[   11.645513] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   22.357425] eth0: no IPv6 routers present

CaptainKirk · 2012-03-21 16:27:30

No dmesg|grep eth0 shows no results.

But after the initial install dhcpcd eth0 worked and got me online. Something in all the upgrades (and reboot) broke it.

jdarnold · 2012-03-21 16:55:23

Is there *any* eth? does 'grep eth' show anything? It may have renumbered itself. I'd suggest using 'ifconfig' but it isn't installed by default any more.

CaptainKirk · 2012-03-21 17:01:15

jdarnold wrote:

Is there *any* eth? does 'grep eth' show anything?

No, nothing.

jdarnold wrote:

I'd suggest using 'ifconfig' but it isn't installed by default any more.

I know.

There's this:

$ 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

and on my working PC:

$ 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 70:71:bc:9a:f0:82 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.1/24 brd 10.0.0.255 scope global eth0
    inet6 fe80::7271:bcff:fe9a:f082/64 scope link 
       valid_lft forever preferred_lft forever

Gcool · 2012-03-21 17:54:15

According to my sources (Google); the driver module for that nic would be "r8169". Try that one.

CaptainKirk · 2012-03-21 18:12:42

I did modprobe r8169 and then dhcpcd but no change in dmesg nor ip addr.

jdarnold · 2012-03-21 19:45:28

It really doesn't look like it is seeing the network "card" at all. What about a live boot cd, like maybe the ArchBang one? Does it see the network card? Could be a hardware problem.

CaptainKirk · 2012-03-21 19:59:28

ArchBang LiveCD works fine. I just rebooted into it. eth0, as it should be.

Gcool · 2012-03-21 20:06:53

When you're booted with your Arch livecd; take a look at which driver is getting loaded for your nice (lspci -k will show you). Once you know that; try adding that one to your MODULES array in /etc/rc.conf and reboot.

CaptainKirk · 2012-03-22 10:38:31

Good idea. Here it is copied from ArchBang:

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: agpgart-intel
	Kernel modules: intel-agp
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel modules: i915
00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: HDA Intel
	Kernel modules: snd-hda-intel
00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 01)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2 (rev 01)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci-hcd
00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: ehci_hcd
	Kernel modules: ehci-hcd
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel modules: intel-rng, iTCO_wdt, leds-ss4200
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: ata_piix
	Kernel modules: piix, ata_piix
00:1f.2 IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix
00:1f.3 SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: i801_smbus
	Kernel modules: i2c-i801
01:05.0 Communication controller: Conexant Systems, Inc. HSF 56k Data/Fax Modem
	Subsystem: Conexant Systems, Inc. Soft Data Fax Modem with SmartCP
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 01)
	Subsystem: Hewlett-Packard Company Device 2a59
	Kernel driver in use: r8169
	Kernel modules: r8169

and dmesg | grep eth0:

[   16.544154] r8169 0000:02:00.0: eth0: RTL8101e at 0xf8960000, 00:1e:8c:de:ed:85, XID 94200000 IRQ 40
[   29.335226] r8169 0000:02:00.0: eth0: link down
[   29.335236] r8169 0000:02:00.0: eth0: link down
[   31.081606] r8169 0000:02:00.0: eth0: link up

Now I will reboot and try

modprobe r8169

CaptainKirk · 2012-03-22 13:04:27

Rebooted and tried modprobe r8169 but same result.

This PC had before a working Arch 32 bit so I formatted the drive and installed a fresh 32 bit. Worked fine. Then ran pacman -Syu and rebooted and now I am stuck with the same precise situation.

I think I will just install Debian. I just need this PC to work.

Gcool · 2012-03-22 13:14:10

Perhaps try loading the module through your initramfs and see what that gives as a result.

- Add r8169 to your MODULES array in /etc/mkinitcpio.conf
- Run 'mkinitcpio -p linux'
- Reboot

Last edited by Gcool (2012-03-22 13:21:42)

bohoomil · 2012-03-22 13:17:28

For what it's worth, check if the lts kernel works for you. It's only a workaround, but if your setup is working correctly otherwise you may save some time this way.

Arch Linux

#1 2012-03-21 15:24:07

New Install Works then Fails

#2 2012-03-21 16:10:14

Re: New Install Works then Fails

#3 2012-03-21 16:27:30

Re: New Install Works then Fails

#4 2012-03-21 16:55:23

Re: New Install Works then Fails

#5 2012-03-21 17:01:15

Re: New Install Works then Fails

#6 2012-03-21 17:54:15

Re: New Install Works then Fails

#7 2012-03-21 18:12:42

Re: New Install Works then Fails

#8 2012-03-21 19:45:28

Re: New Install Works then Fails

#9 2012-03-21 19:59:28

Re: New Install Works then Fails

#10 2012-03-21 20:06:53

Re: New Install Works then Fails

#11 2012-03-22 10:38:31

Re: New Install Works then Fails

#12 2012-03-22 13:04:27

Re: New Install Works then Fails

#13 2012-03-22 13:14:10

Re: New Install Works then Fails

#14 2012-03-22 13:17:28

Re: New Install Works then Fails

Board footer