Hi Ionel, That is very weird. FYI, the r8168 driver in the 1.0-beta is exactly the same as in 1.0.0.
Looking at my Atom Dual-core D525 system (Jetway board) with a r8168 NIC, (eth3 for me) connected to a OS X MacBook... -- Jan 9 17:25:16 pbx user.info kernel: r8168 Gigabit Ethernet driver 8.025.00-NAPI loaded Jan 9 17:25:16 pbx user.info kernel: r8168 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 Jan 9 17:25:16 pbx user.debug kernel: r8168 0000:02:00.0: setting latency timer to 64 Jan 9 17:25:16 pbx user.debug kernel: r8168 0000:02:00.0: irq 43 for MSI/MSI-X Jan 9 17:25:16 pbx user.info kernel: eth%d: RTL8168B/8111B at 0xf81b8000, 00:30:18:xxxx:xx, IRQ 43 Jan 9 17:25:16 pbx user.info kernel: r8168: This product is covered by one or more of the following patents: ... Jan 9 17:25:16 pbx user.debug kernel: eth3: Identified chip type is 'RTL8168D/8111D'. Jan 9 17:25:16 pbx user.warn kernel: r8168 Copyright (C) 2011 Realtek NIC software team <nic...@realtek.com> --snip-- Jan 9 17:25:16 pbx user.info kernel: r8168: eth3: link down Jan 9 17:25:16 pbx user.info kernel: ADDRCONF(NETDEV_UP): eth3: link is not ready --snip-- Jan 9 17:25:16 pbx user.info kernel: r8168: eth3: link up Jan 9 17:25:16 pbx user.info kernel: ADDRCONF(NETDEV_CHANGE): eth3: link becomes ready Jan 9 17:25:16 pbx user.info kernel: r8168: eth3: link up -- all during the same second (with multiple cores the logs can get tangled somewhat) So, check down in the your logs to see if there are more r8168 or eth0 entries, the first 'link down' log is normal. I then swapped my cables and connected my r8168 eth3 to an HP 1800-8G switch, the resulting logs are *exactly* the same as above, using a different cable and different connecting NIC. I'd check your cable, if a managed switch make sure that port is set to "auto" negotiation. Try a different port on your switch. Let us know... Lonnie On Jan 9, 2012, at 8:02 PM, Ionel Chila wrote: > On my Atom Dual-core D525 system > (http://www.amazon.com/Foxconn-Dual-core-Barebone-System-R40-D4/dp/B004XLFP7U/ref=pd_sxp_f_pt) > after doing a fresh install of 1.0.0 I get inconsistent network interface > behavior. When plugged into my main gigabit switch the eth0 interface will > not come up for some reason. I fI plug into a hub, or into a lan port in my > wireless router then the eth0 interface does come up just fine. Is really > really weird. On the same system I had the beta image before 1.0.0 was final > and it worked just fine the same hardware/switch configuration. Could > anything be wrong with the driver? Or maybe is the negotiation on the speed? > Should I hard code the eth0 interface speed in Astlinux if possible? > > Here is a quick list of my messages to see the eth0 interface used and all > that: > > > Real Time Clock Driver v1.12b > Linux Tulip driver version 1.1.15 (Feb 27, 2007) > natsemi dp8381x driver, version 2.1, Sept 11, 2006 > originally by Donald Becker <bec...@scyld.com> > 2.4.x kernel port by Jeff Garzik, Tjeerd Mulder > 8139too: 8139too Fast Ethernet driver 0.9.28 > via-rhine.c:v1.10-LK1.4.3 2007-03-06 Written by Donald Becker > pcnet32: pcnet32.c:v1.35 21.Apr.2008 tsbog...@alpha.franken.de > Intel(R) PRO/1000 Network Driver - version 8.0.35-NAPI > Copyright (c) 1999-2010 Intel Corporation. > e1000e: Intel(R) PRO/1000 Network Driver - 1.6.3-NAPI > e1000e: Copyright(c) 1999 - 2011 Intel Corporation. > ns83820.c: National Semiconductor DP83820 10/100/1000 driver. > r8168 Gigabit Ethernet driver 8.025.00-NAPI loaded > r8168 0000:02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 > r8168 0000:02:00.0: setting latency timer to 64 > r8168 0000:02:00.0: irq 42 for MSI/MSI-X > eth%d: RTL8168B/8111B at 0xf827c000, d0:27:88:3b:50:e3, IRQ 42 > 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. > eth0: Identified chip type is 'RTL8168D/8111D'. > r8168 Copyright (C) 2011 Realtek NIC software team <nic...@realtek.com> > This program comes with ABSOLUTELY NO WARRANTY; for details, please see > <http://www.gnu.org/licenses/>. > This is free software, and you are welcome to redistribute it under certain > conditions; see <http://www.gnu.org/licenses/>. > dahdi: Telephony Interface Registered on major 196 > dahdi: Version: 2.4.1.1 > wctdm 0000:03:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 > Freshmaker version: 73 > Freshmaker passed register test > Module 0: Installed -- AUTO FXO (FCC mode) > Module 1: Installed -- AUTO FXS/DPO > Module 2: Installed -- AUTO FXS/DPO > Module 3: Installed -- AUTO FXS/DPO > Found a Wildcard TDM: Wildcard S400P Prototype (4 modules) > dahdi_echocan_oslec: Registered echo canceler 'OSLEC' > dahdi: Registered tone zone 0 (United States / North America) > r8168: eth0: link down ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.