Zyxel NSA310 u-boot-2014.07-tld-4 for testing

I've uploaded the Zyxel NSA310 u-boot-2014.07-tld-4 for testing.

Note that this is for the Zyxel NSA310 box. The NSA310S is on the other thread.

Download at Dropbox
uboot.2014.07-tld-4.nsa310.bodhi.tar
md5:
b5a2605f7d5841aa3cd2c36ab25bd5ec

Please test this with UART serial console. Since this is the NAND version, kwboot must be executed with -p option:

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4.nsa310.mtd0.kwb -p

Warning: Please do not flash this version until after it has been confirmed to work without problem in UART booting.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hey, unfortunately it will take some time until I have access to my nsa310 again.

One question: is the networking device issue resolved?

Thanks for your work!

marlemion Wrote:
-------------------------------------------------------
> Hey, unfortunately it will take some time until I
> have access to my nsa310 again.
>
> One question: is the networking device issue
> resolved?
>
> Thanks for your work!

Hi marlemion!

I was not aware that the Nsa310 has networking issue, could you describe it? Also, when you have access, you could boot this with UART and check it out at the serial cosole prompt.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hey bodhi,

I already got uboot booted with UART a while ago. See this post here:

http://forum.doozan.com/read.php?3,12381,21223#msg-21223

So I will certainly will test it ASAP.

However, I did not get the network device to be initialized, as it is a different one than in NSA320 or NSA310s. See 'EDIT5' and the following in the mentioned post. The post is quite lengthy and confusing, sorry about that. :)

I see, it was a little bit confusing :) but this is the network problem:

Quote

EDIT5: The problem is that the NSA310 has a Realtek 8169 network chip instead of a Marvell Alaska 88E1318.

Let me know if you can ping your router at the serial prompt.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I will, but it may take some time, as the nsa310 is happily running as a mini server at my parents home and I don't know yet when I will be there again.

marlemion,

When you do have access the first thing to check for is which version your NSA310 is (if you don't already know).

Quote
http://zyxel.nas-central.org/wiki/Category:NSA-310
There are at least two versions of the NSA-310 'in the wild'. The rebranded TDC Homedisk, and the 'genuine' NSA-310. Yet another version was presentd at CeBIT 2007, but I never found evidence that it has actually been sold. According to the GPL sources there are at least 3 different versions, the TDC, the OBM and the SGW.

Stock u-boot envs should show the model ID. That will give us a hint where to find the source in the GPL tarball. And if you keep the serial boot log with you then you can post dmesg and/or u-boot envs here.

Also, I don't have the NSA310, but I did a sanity boot test on a GoFlex Home to verify the image. It did show the network is running, even though it has a different LAN chip.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/20/2015 04:18PM by bodhi.

U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56)
ZyXEL NSA310 1-Bay Power Media Server 


SoC:   Kirkwood 88F6281_A1
DRAM:  256 MiB
WARNING: Caches not enabled
NAND:  128 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot:  0

the networking issue is still present, when setting ipaddr and serverip nothing is pingable.


as marlemion mentioned, the NSA310 has a different LAN chip.

r8168 Gigabit Ethernet driver 8.023.00-NAPI loaded
r8168 0000:00:01.0: no MSI. Back to INTx.
 Set LED ... 
eth%d: RTL8168B/8111B at 0xd0900000, 00:00:00:00:00:30, IRQ 9

MODEL_ID=A203

This shold be the TDC Homedisk.



Edited 1 time(s). Last edit at 08/21/2015 12:52AM by pengu.

pengu Wrote:
-------------------------------------------------------
>

> U-Boot 2014.07-tld-4 (Aug 19 2015 - 20:51:56)
> ZyXEL NSA310 1-Bay Power Media Server 
> 
> 
> SoC:   Kirkwood 88F6281_A1
> DRAM:  256 MiB
> WARNING: Caches not enabled
> NAND:  128 MiB
> *** Warning - bad CRC, using default environment
> 
> In:    serial
> Out:   serial
> Err:   serial
> Net:   egiga0
> PHY reset timed out
> MV88E1318 PHY initialized on egiga0
> Hit any key to stop autoboot:  0 
>

>
> the networking issue is still present, when
> setting ipaddr and serverip nothing is pingable.
>
>
> as marlemion mentioned, the NSA310 has a different
> LAN chip.
>
>

> r8168 Gigabit Ethernet driver 8.023.00-NAPI
> loaded
> r8168 0000:00:01.0: no MSI. Back to INTx.
>  Set LED ... 
> eth%d: RTL8168B/8111B at 0xd0900000,
> 00:00:00:00:00:30, IRQ 9
>

>
>
>

> MODEL_ID=A203
>

> This shold be the TDC Homedisk.

Ah! that makes a lot of sense. The orginal NSA310 network should work fine. I'll see if I can find and incorporate this TDC Homedisk version.

Was this from dmesg?

> r8168 Gigabit Ethernet driver 8.023.00-NAPI
> loaded
> r8168 0000:00:01.0: no MSI. Back to INTx.
>  Set LED ... 
> eth%d: RTL8168B/8111B at 0xd0900000,
> 00:00:00:00:00:30, IRQ 9

And does your box has TDC label in front plate?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/21/2015 01:24AM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> pengu Wrote:
> --------------------------------------------------
> -----


> >

> > MODEL_ID=A203
> >

> > This shold be the TDC Homedisk.
>
> Ah! that makes a lot of sense. The orginal NSA310
> network should work fine. I'll see if I can find
> and incorporate this TDC Homedisk version.

no it's the seme on the original NSA310 because it uses the same LAN chip

>
> Was this from dmesg?
>

> > r8168 Gigabit Ethernet driver 8.023.00-NAPI
> > loaded
> > r8168 0000:00:01.0: no MSI. Back to INTx.
> >  Set LED ... 
> > eth%d: RTL8168B/8111B at 0xd0900000,
> > 00:00:00:00:00:30, IRQ 9
>

dmesg on ZyXEL OS

[    1.959239] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[    1.965135] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[    1.965291] r8169 0000:01:00.0: enabling bus mastering
[    1.965954] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.975602] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

debian


> And does your box has TDC label in front plate?

yes TDC and only SYS and HDD LED were shown



Edited 3 time(s). Last edit at 08/21/2015 01:47AM by pengu.

pengu,

> no it's the seme on the original NSA310 because it
> uses the same LAN chip

That's not the same LAN chip, if it shows RTL8169

> > > r8168 Gigabit Ethernet driver 8.023.00-NAPI
> > > loaded
> > > r8168 0000:00:01.0: no MSI. Back to INTx.
> > >  Set LED ... 
> > > eth%d: RTL8168B/8111B at 0xd0900000,
> > > 00:00:00:00:00:30, IRQ 9
> 
> dmesg on ZyXEL OS 
>

> [    1.959239] r8169 0000:01:00.0: enabling device
> (0140 -> 0143)
> [    1.965135] r8169 0000:01:00.0: enabling
> Mem-Wr-Inval
> [    1.965291] r8169 0000:01:00.0: enabling bus
> mastering
> [    1.965954] r8169 0000:01:00.0 eth0:
> RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30,
> XID 083000c0 IRQ 83
> [    1.975602] r8169 0000:01:00.0 eth0: jumbo
> features [frames: 9200 bytes, tx checksumming:
> ko]
>

> debian
>
>
> > And does your box has TDC label in front
> plate?
>
> yes TDC and only SYS and HDD LED were shown

Does it have the red USB LED?
Does dmesg show PCI controller being initialized?

Please post/pastebin serial log.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/21/2015 02:40AM by bodhi.

bodhi Wrote:
-------------------------------------------------------


> That's not the same LAN chip, if it shows RTL8169

both is from the same box so ZyXEL OS uses a different driver for the same chip

http://abload.de/img/nsa310_lanbisgx.jpg

> Does it have the red USB LED?

ls /sys/class/leds/nsa310:red:usb
.  ..  brightness  device  max_brightness  power  subsystem  trigger  uevent

> Does dmesg show PCI controller being initialized?

dmesg | grep PCI
[    0.268538] PCI: CLS 0 bytes, default 32
[    0.913091] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[    0.913683] PCI: bus0: Fast back to back transfers disabled
[    0.914498] PCI: bus1: Fast back to back transfers disabled
[    0.914796] pci 0000:00:01.0: PCI bridge to [bus 01]
[    1.990971] ehci-pci: EHCI PCI platform driver

lspci
00:01.0 PCI bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 03)
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

Edited 2 time(s). Last edit at 08/21/2015 02:54AM by pengu.

pengu,

> both is from the same box so ZyXEL OS uses a
> different driver for the same chip

So when you opened it, the chip inside is Marvell Alaska?

But does it "really" have a USB LED that turns red? And I should have asked "does PCI appear to be used in anything, e.g. USB 3.0".

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/21/2015 02:59AM by bodhi.

yes, the red usb is working:

 echo usb-host > /sys/class/leds/nsa310\:red\:usb/trigger

http://abload.de/img/nsa310_red_usbgas60.jpg

the pci stuff:

http://pastebin.com/ZDj9F2Bh

nsa310 pcb:

http://abload.de/img/nsa310_pcbuwucn.jpg



Edited 2 time(s). Last edit at 08/21/2015 03:41AM by pengu.

Btw. even though I don't have the device here, I can confirm that my NSA310 has the same RTL chip as shown by the picture of pengu above! I saw it when I opened the case.

I'll get back to you when having more information.

I could not see where is the LAN chip is, does it say 88E1318? if it does, then there is no need for another u-boot sub-version to use the RTL8169.

It looks like we need another build to take care of the 88E1318 PHY. I'll rebuild and upload.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

This one: http://abload.de/img/nsa310_lanbisgx.jpg

I can confirm that this one is on my NSA310. If you read EDIT6 here:

http://forum.doozan.com/read.php?3,12381,21223#msg-21223

you will see that I mentioned it there, too.



Edited 1 time(s). Last edit at 08/21/2015 04:15AM by marlemion.

marlemion Wrote:
-------------------------------------------------------
> This one:
> http://abload.de/img/nsa310_lanbisgx.jpg
>
> I can confirm that this one is on my NSA310. If
> you read EDIT6 here:
>
> http://forum.doozan.com/read.php?3,12381,21223#msg
> -21223
>
> you will see that I mentioned it there, too.

OK. Got it. I think pengu misunderstood what I've asked up there :)). Now I reread what you post and looked at pengu's picture. We've confirmed that it is RTL8111DL.

EDIT6: Well, the chip is a RTL8111d chip (so reported by linux kernel, the chip itself says RTL8111DL). This chips should be supported by the rtl8169.c driver provided by u-boot. However, I have difficulties to add it to the nsa310 uboot build.

The nsa310 code can be replicated to make a different nsa310 version, i,e. nsa310t (for TDC). It is clear that if we build it correctly to u-boot design standard, we do need either a subversion for the NSA310 (using make option and use ifdefs for the nework chip code), which I think where you ran into problem. Or making it a fully separated nsa310t board, which I think is justifiable since we already have nsa 310, 310s, 320, 320s, and 325.

I'm wondering where are other NSA310 owners who have the version that uses 88E1318 Alaska? ...Is that even true? i.e perhaps the 88E1318 code were wrong in the first place.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 08/21/2015 04:44AM by bodhi.

pengu & marlemion,

I would like to find out if there is a NSA310 box that uses the 88E1318 chip (before I start creating a separated board directory or sub-board version :-).

A very long thread at NAS-Central:

http://forum.nas-central.org/viewtopic.php?f=249&t=5145&start=15

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

AFAIK there is only the NSA310S, which uses the Alaska chip:

http://archlinuxarm.org/forum/viewtopic.php?f=57&t=8827

marlemion Wrote:
-------------------------------------------------------
> AFAIK there is only the NSA310S, which uses the
> Alaska chip:
>
> http://archlinuxarm.org/forum/viewtopic.php?f=57&t
> =8827

Yes. I've just finished a new u-boot for that:
http://forum.doozan.com/read.php?3,23331

I'm starting to doubt whether any flavor of the NSA310 boxes has the 88E1318 chip. Does yours have TDC brand in the front of the box?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I am sorry, I cannot tell you right now. But AFAIR it hasn't.

Is this the TDC brand: http://i1.c.dk/pics/1/6/8/65861/org.jpg ?

I don't remember that. It was pure Zyxel.

Here is the page that has pics of both:

http://zyxel.nas-central.org/wiki/Category:NSA-310

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

both, the "ZyXEL" and the "TDC" brand has a Realtek LAN chip
I haven't seen any NSA310 with Marvell Chip

pengu Wrote:
-------------------------------------------------------
> both, the "ZyXEL" and the "TDC" brand has a
> Realtek LAN chip
> I haven't seen any NSA310 with Marvell Chip

Do you have the orginal NSA310 dmesg output?

Or if marlemion indeed has the orginal 310 then it would clear up the confusion. The current NSA310 u-boot code patch I am using has the 88E1318, so it might have be a mistake, which has led me to assume that it was the right chip :)

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/21/2015 01:34PM by bodhi.

nsa310 here, zyxel one.

It does seem to have indeed that realtek chip.

kwbooted and your uboot has no ethernet access.

rebooting into normal uboot, see below

uboot booting, look at last line about eth1 being [PRIME] (whatever that means)
It probably does something fishy and eth0 is either fake or not connected electrically (why?)

_ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_ 
| | | |___|  _ \ / _ \ / _ \| __| 
| |_| |___| |_) | (_) | (_) | |_ 
 \___/    |____/ \___/ \___/ \__| 
 ** MARVELL BOARD: RD-88F6281A LE 

U-Boot 1.1.4 (Jun  8 2011 - 18:48:37) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFEE0

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz 

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB 
DRAM Total size 256MB  16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0x4640000.

Streaming disabled 
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0, egiga1 [PRIME]

this is the first mention of eth, boots marvell driver then realtek one.

[    1.897609] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    1.904949] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral
[    1.913257] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.918935] pci 0000:00:01.0: enabling device (0140 -> 0143)
[    1.925466] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd0912000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.935135] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

then I get multiple errors of marvell driver like below, suspectging the dts is wrong, it maybe says there is a marvell eth when there is none. I am using dts booting with dts in uimage (or zimage), kernel 3.17. dts nsa310, not nsa310a.

[    2.990508] platform mv643xx_eth_port.0: Driver mv643xx_eth_port requests probe deferral

then complains about firmware but eth0 works fine and gets IP from my router shortly afterwards on eth0.
Probably because it is not rtl816d but the rtl8111D like it detects above.

[   18.227450] r8169 0000:01:00.0: Direct firmware load for rtl_nic/rtl8168d-2.fw failed with error -2
[   18.236645] r8169 0000:01:00.0 eth0: unable to load firmware patch rtl_nic/rtl8168d-2.fw (-2)
[   18.264769] r8169 0000:01:00.0 eth0: link down
[   18.269244] r8169 0000:01:00.0 eth0: link down
[   18.273787] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

the same marvell driver keeps erroring 5 times or so with the same line as above.

only eth I can detect with scans is the realtek one, no marvell ethernet.

there seems to be some significant confusion somehwere, I can assure you that this is NOT a nsa325, yet lshw tells me this

description: Computer
    product: ZyXEL NSA325
    width: 32 bits
  *-core
       description: Motherboard
       physical id: 0
       capabilities: zyxel_nsa325 marvell_kirkwood-88f6282 marvell_kirkwood
     *-cpu
          description: CPU
          product: cpu
          physical id: 0
          bus info: cpu@0
     *-memory
          description: System memory
          physical id: 2
          size: 245MiB
     *-pci
          physical id: 1
          bus info: pci@0000:00:01.0
          version: 03
          width: 32 bits
          clock: 33MHz
          capabilities: pci bus_master
          resources: ioport:10000(size=4096) memory:e0000000-e00fffff
        *-network
             description: Ethernet interface
             physical id: 0
             bus info: pci@0000:01:00.0
             logical name: eth0
             version: 03
             serial: 00:00:00:00:00:30
             size: 100Mbit/s
             capacity: 1Gbit/s
             width: 64 bits
             clock: 33MHz
             capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
             configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full ip=10.42.0.58 latency=0 link=yes multicast=yes port=MII speed=100Mbit/s
             resources: irq:83 ioport:10000(size=256) memory:e0014000-e0014fff memory:e0010000-e0013fff memory:e0000000-e000ffff

In case you were wondering, yes it is connected to a crappy router, 100Mbit/s is normal.



Edited 4 time(s). Last edit at 08/21/2015 05:37PM by bobafetthotmail.

bobafetthotmail Wrote:
-------------------------------------------------------
> nsa310 here, zyxel one.
>
> It does seem to have indeed that realtek chip.

Cool! thanks for the confirmation.

> kwbooted and your uboot has no ethernet access.

No wonder!

> rebooting into normal uboot, see below

> then I get multiple errors of marvell driver like
> below, suspectging the dts is wrong, it maybe says
> there is a marvell eth when there is none. I am
> using dts booting with dts in uimage (or zimage),
> kernel 3.17. dts nsa310, not nsa310a.

Yes, either the DTS or kernel ethernet config is suspected. I'm surprised nobody has reported this. iirc, some users have tried and/or use my built kernel for NSA310.

> there seems to be some significant confusion
> somehwere, I can assure you that this is NOT a
> nsa325, yet lshw tells me this
>
> description: Computer
> product: ZyXEL NSA325
> width: 32 bits
> *-core
> description: Motherboard
> physical id: 0
> capabilities: zyxel_nsa325
> marvell_kirkwood-88f6282 marvell_kirkwood

Check your appended DTB if it is the right one, and/or try to boot with 3.16 to see if the same info show up. And 3.6 kernel needs u-boot envs:

arcNumber - set to 4022
machid - removed this env

BTW, does your dmesg show that it is the NSA310, not NSA325?

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Quote
http://forum.doozan.com/read.php?3,12381,21223#msg-21223

marlemion said:

EDIT7: So the RTL8111d chip is an PCI-e chip. PCI-e is initialized, however, the linking problems remain. Does anybody know how to get further?

And:
http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=5&Level=5&Conn=4&ProdID=193

This is going to be troublesome.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Attached here is the first cut to enable RTL8169 chip ( not sure how far we'll get with this image :).

I turned on RTL8169 debug so we can see if the card is intialized at all.

Please test with UART only (not flashing to NAND)

kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4-test-1.nsa310.mtd0.kwb -p

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 08/22/2015 06:13AM by bodhi.

the "ZyXEL" NSA310 has arrived so let's see
it has the _same_ ethernet chip as the "TDC" one.

http://abload.de/img/nsa310_lan_chipapkr9.jpg <- lan chip

http://abload.de/img/nsa310_pcb_2auqoo.jpg <- pcb


@bobafetthotmail

I never had problems with the NSA310 (ZxXEL and TDC) (Kernel 3.18.3, 4.0.0, 4.10)
that one on which I tested the new U-Boot yesterday has some memory issues

[    1.947877] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[    1.953538] pci 0000:00:01.0: enabling device (0140 -> 0143)
[    1.959242] pci 0000:00:01.0: enabling bus mastering
[    1.959260] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[    1.965155] r8169 0000:01:00.0: enabling Mem-Wr-Inval
[    1.965310] r8169 0000:01:00.0: enabling bus mastering
[    1.965975] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd090e000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[    1.975622] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]

...
...

   14.253938] NET: Registered protocol family 10
[   14.444661] r8169 0000:01:00.0 eth0: link down
[   14.449151] r8169 0000:01:00.0 eth0: link down
[   14.453708] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   16.308575] r8169 0000:01:00.0 eth0: link up
[   16.312903] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1
Copyright 2004-2014 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth0/5c:f4:ab:e3:e6:1e
Sending on   LPF/eth0/5c:f4:ab:e3:e6:1e
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.1.1
DHCPACK from 192.168.1.1

there were no memory issues so I can go furher:
http://pastebin.com/m0dyJqYS

no linking problems but poor performance (read)
I never noticed this before but a friend of me has the same issue
with some tuning I get 25 MB/s read and 38 MB/s write



Edited 8 time(s). Last edit at 08/22/2015 01:29PM by pengu.