dalben Posted September 18, 2012 Share Posted September 18, 2012 I dropped RC8 onto my thumb drive and rebooted. The machine came up but was not on the network. I'm assuming RC8 isn't find the r8168 I have in my server. Being a unix noob I had no idea how to try and get it started from the command line. I'v e reverted back to RC6-test2 to get it up again. Here are the syslog entries, first being RC8 and seeing it fail: Sep 18 11:24:04 tdm ifconfig[15390]: eth0: error fetching interface information: Device not found Sep 18 11:24:04 tdm ethtool[15399]: Settings for eth0: Sep 18 11:24:04 tdm ethtool[15399]: No data available and here's the working RC6 Sep 7 07:11:32 tdm kernel: r8168 Gigabit Ethernet driver 8.031.00-NAPI loaded Sep 7 07:11:32 tdm kernel: r8168 0000:03:00.0: irq 51 for MSI/MSI-X Sep 7 07:11:32 tdm kernel: eth%%d: RTL8168E/8111E at 0xf84c4000, f4:6d:04:70:09:44, IRQ 51 Sep 7 07:11:32 tdm kernel: r8168: This product is covered by one or more of the following patents: US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625. Sep 7 07:11:32 tdm kernel: eth0: Identified chip type is 'RTL8168E/8111E'. Sep 7 07:11:32 tdm kernel: r8168 Copyright (C) 2012 Realtek NIC software team <[email protected]> Sep 7 07:11:32 tdm kernel: This program comes with ABSOLUTELY NO WARRANTY; for details, please see <http://www.gnu.org/licenses/>. Sep 7 07:11:32 tdm kernel: This is free software, and you are welcome to redistribute it under certain conditions; see <http://www.gnu.org/licenses/>. Sep 7 07:11:35 tdm dhcpcd[1047]: eth0: carrier acquired Sep 7 07:11:35 tdm dhcpcd[1047]: eth0: broadcasting for a lease Sep 7 07:11:35 tdm kernel: r8168: eth0: link up Sep 7 07:11:35 tdm dhcpcd[1047]: eth0: offered 192.168.1.10 from 192.168.1.1 Sep 7 07:11:35 tdm dhcpcd[1047]: eth0: acknowledged 192.168.1.10 from 192.168.1.1 Sep 7 07:11:35 tdm dhcpcd[1047]: eth0: checking for 192.168.1.10 Sep 7 07:11:36 tdm kernel: r8168: eth0: link up Quote Link to comment
limetech Posted September 18, 2012 Share Posted September 18, 2012 Yes, something went awry in the build... will be posting -rc8a... Quote Link to comment
speeding_ant Posted September 18, 2012 Share Posted September 18, 2012 Same issue here Quote Link to comment
sacretagent Posted September 18, 2012 Share Posted September 18, 2012 same issue here RC8 has no nics RC6 -r8168-test has nic Sep 18 14:43:05 P8H67 kernel: eth0: Identified chip type is 'RTL8168E/8111E'. Sep 18 14:43:05 P8H67 kernel: r8168 Copyright © 2012 Realtek NIC software team <[email protected]> attached logs if needed log.zip Quote Link to comment
dalben Posted September 18, 2012 Author Share Posted September 18, 2012 I can confirm RC8a has resolved the issue. Quote Link to comment
sacretagent Posted September 18, 2012 Share Posted September 18, 2012 nic issue solved for me too Quote Link to comment
brun0 Posted September 18, 2012 Share Posted September 18, 2012 I've just updated to RC8a and my r8168 NIC is still not recognized. I can load the module manually but the NIC is not shown by ifconfig -a (Forgot to check dmesg after loading the module :-/ ) edit: Just tried it again, there is nothing in dmesg... Quote Link to comment
brun0 Posted September 20, 2012 Share Posted September 20, 2012 I just realized I have a r8169 which is not detected, not a r8168 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.