Network is configured per the wiki and up and running now. Thanks for the replies everyone. Marked SOLVED.
]]>dmesg | grep eth
systemd-udevd[153]: renamed network interface eth0 to enp1s0
I checked out /etc/udev/rules.d and there aren't any rules there so what in the world is going on here? Why does udev wanna rename it? Also, this name doesn't appear in /dev.
]]>lspci -v
... yields...
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards
Flags: bus master, fast devsel, latency 0, IRQ42
I/O ports at e800 [size=256]
Memory at fdfff000 (64-bit, prefetchable) [size=4K]
Memory at fdff8000 (64-bit, prefetchable) [size=15K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Kernel driver in use: r8169
and...
dmesg | grep r816
gives
r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
r8169 0000:01:00.0: irq 42 for MSI/MSI-X
r8169 0000:01:00.0: eth0: RTL8168e/8111e at 0xf8b120000, 54:04:a6:ec:57:31, XID 0c200000 IRQ 42
r8169 0000:01:00.0: eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
So based on this it would appear that the system is loading the driver and recognizing the NIC as eth0 right? So why does ip addr only give lo: and not eth0: as well? It's also not found in /dev/ at all.
I'm dumbfounded. This is on a clean install this is still happening.
Whew that took forever to type!
]]>Thanks.
]]>I got pulled into a 4 day trip for work so I can't get you the output of lspci right now but if I remember correctly its the RealTek 8168/8111b rev 06. It's an onboard NIC on an ASUS P5 series. Don't remember the exact model off the top of my head. If you stay tuned I can get you the output when I get home. Dmesg is also always indicating the driver is loaded.
I can't believe a fresh install didn't even work even after the install media recognizes it. It's installed on a USB drive but I can't see why that would make any difference.
Hm... Your NIC should be supported by r8169. For my asus motherboard (M5A88-M):
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards
Flags: bus master, fast devsel, latency 0, IRQ 44
I/O ports at e800 [size=256]
Memory at fdfff000 (64-bit, prefetchable) [size=4K]
Memory at fdff8000 (64-bit, prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: r8169
The last kernel which had an incomplete support for this controller was 3.4.9...
]]>I can't believe a fresh install didn't even work even after the install media recognizes it. It's installed on a USB drive but I can't see why that would make any difference.
]]>$ modinfo r8169| gr rtl_nic
firmware: rtl_nic/rtl8168g-1.fw
firmware: rtl_nic/rtl8106e-1.fw
firmware: rtl_nic/rtl8411-1.fw
firmware: rtl_nic/rtl8402-1.fw
firmware: rtl_nic/rtl8168f-2.fw
firmware: rtl_nic/rtl8168f-1.fw
firmware: rtl_nic/rtl8105e-1.fw
firmware: rtl_nic/rtl8168e-3.fw
firmware: rtl_nic/rtl8168e-2.fw
firmware: rtl_nic/rtl8168e-1.fw
firmware: rtl_nic/rtl8168d-2.fw
firmware: rtl_nic/rtl8168d-1.fw
At some point I ran a system upgrade. My problem was I was still using the old init scripts and I wanted to switch to systemd. I didn't realize all that was involved etc. and wound up just running a pacman -Syu. Ever since that update I have not been able to get my onboard NIC to work with my install.
I've read plenty of forum posts about this particular chipset and it seems kernel upgrades frequently cause issues. I've actually never had any problems with it up to this point but I tried several of the suggestions in the forums.
When I boot the live USB image the NIC is properly loaded and obtains an address through DHCP but even after rolling back my kernel to 3.6.9 and trying the r8168-all package in the AUR I cannot get my NIC to be recognized. Running lspci -v shows it in there and shows the driver module is loaded but it doens't appear in /dev/ and I can't get anything from it using 'ip'. It does still work though because I can easily get it with the live USB image.
I'm at my witts end and can't figure this out. Can someone please help? What should I post to help people help me?
Thanks!
]]>