Thanks Lonnie
Looking back at my steps actually I didn't use the ISO image but rather the
.img version "astlinux-1.0-5224-asterisk-1.8.7.1.img". There is no ISO imgae
for that you right :-)
I will try a fresh image of 1.0.0 on a USB stick and if any difference.
I will also look at your "otherwise" steps.
Will get back and let you know about my progress.
Cheers
Ionel
________________________________
From: Lonnie Abelbeck <li...@lonnie.abelbeck.com>
To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
Cc: Ionel Chila <ionelch...@yahoo.com>
Sent: Monday, January 9, 2012 11:06 PM
Subject: Re: [Astlinux-users] AstLinux 1.0.0 Network Interface Issues, fresh
install
Hi Ionel,
Hmmm, the 1.0 beta never had an ISO image, do you recall what image you used
that seemed to work with your switch? How about trying a fresh 1.0.0 install
img.gz to a USB drive (as a test) and boot directly off it. No need to
configure it to test.
(you may need to add rootdelay=5 in the os/astlinux-1.0.0.run.conf KCMD line if
it fails to fully boot the USB flash drive).
Otherwise...
Look at the file "/etc/udev/rules.d/70-persistent-net.rules" and make sure it
only contains the one NIC entry.
Do a "show-union" from the CLI, it should look something like the following:
--
/oldroot/mnt/asturw
/oldroot/mnt/asturw/lost+found
/oldroot/mnt/asturw/etc
/oldroot/mnt/asturw/etc/blkid.tab
/oldroot/mnt/asturw/etc/udev
/oldroot/mnt/asturw/etc/udev/rules.d
/oldroot/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules
/oldroot/mnt/asturw/etc/blkid.tab.old
/oldroot/mnt/asturw/etc/shadow
/oldroot/mnt/asturw/etc/shadow-
/oldroot/mnt/asturw/stat
/oldroot/mnt/asturw/stat/var
/oldroot/mnt/asturw/stat/var/www
/oldroot/mnt/asturw/stat/var/www/admin
/oldroot/mnt/asturw/stat/var/www/admin/.htpasswd
/oldroot/mnt/asturw/stat/var/lib
/oldroot/mnt/asturw/stat/var/lib/asterisk
--
If you have some other files you may have edited it should show up.
From the CLI "ethtool eth0" might give useful info. What does your managed
switch show for that port? Fixing the port on the switch from 'auto' to some
value would be a useful test for negotiation failures.
Have you googled to see if your switch has an issue with the 'RTL8168D/8111D'
NIC ?
Lonnie
On Jan 9, 2012, at 10:06 PM, Ionel Chila wrote:
> Thanks much Lonnie for the prompt response. It is absolutely weird. Already
> switched few cables and also different ports on the switch which is set to
> auto negotiation. Will consistently not work with that switch no matter what
> I do. And yes down the logs I still get the same link down message after all
> the other stuff is loaded. I just didn't want to paste the whole thing :-)
>
> Man I always get the difficult problems :-) I am ready to move everything to
> this system but I need to fix the real problem with this interface since will
> need to be plugged into my main switch
>
>
> Would my install process matter? I did an upgrade from the beta image to
> 1.0.0 via the command line upgrade-run-image upgrade
> http://mirror.astlinux.org/ast18-firmware-1.x and of course upgraded the
> runnix as well
> Since there is no ISO image for generic i586 I took the beta (which does have
> an ISO image) route and upgrade to 1.0.0 after that.
> It shouldn't matter but I wanted to provide all the facts, you never know
> right :-)
>
>
> From: Lonnie Abelbeck <li...@lonnie.abelbeck.com>
> To: AstLinux Users Mailing List <astlinux-users@lists.sourceforge.net>
> Cc: Ionel Chila <ionelch...@yahoo.com>
> Sent: Monday, January 9, 2012 9:26 PM
> Subject: Re: [Astlinux-users] AstLinux 1.0.0 Network Interface Issues, fresh
> install
>
> 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.
