That's great news! Thanks for the update :)by mpmc - Debian
Would be interesting to see which of these commits caused the issue! https://github.com/torvalds/linux/commits/master/drivers/net/ethernet/realtek/r8169.c Maybe applying this patch will help - https://lore.kernel.org/patchwork/patch/883134/ I'll give it a try and report back when I can!by mpmc - Debian
bodhi Wrote: ------------------------------------------------------- > mpmc Wrote: > ------------------------------------------------------- > > @bodhi > > > > I wonder if they've fixed it in 5.0? I'd build > it > > myself to see but like I say I tried before and > > the cross compile just hung on deb unstable > > > > Iby mpmc - Debian
@bodhi I wonder if they've fixed it in 5.0? I'd build it myself to see but like I say I tried before and the cross compile just hung on deb unstable I'm more than happy to test anything else you can think of though! Cheers!by mpmc - Debian
As requested :) nsa310a login: mark Password: Last login: Tue Feb 26 21:34:28 GMT 2019 on ttyS0 Linux nsa310a 4.20.6-kirkwood-tld-1 #1 PREEMPT Thu Jan 31 21:41:45 PST 2019 armv 5tel The programs included with the Debian GNU/Linuxby mpmc - Debian
As requested :) The paste is too large -> Pastebinned here for your enjoymentby mpmc - Debian
Sorry for the late reply! 4.16.1 and 4.19.0: had no network at first, left Ethernet LED flashing, did modprobe r8169, LEDs out but the network went up! [ 66.296987] libphy: r8169: probed [ 66.308621] r8169 0000:01:00.0 eth0: RTL8168d/8111d, 00:00:00:00:00:30, XID 283000c0, IRQ 38 [ 66.317106] r8169 0000:01:00.0 eth0: jumbo features mark@nsa310a:~$ [ 66.373085] r8169 0000:01:00.0by mpmc - Debian
No luck! It doesn't even detect it anymore, not even a hint of an error, I suppose that's something.by mpmc - Debian
Absolutely when I get out of bed (6am), or maybe arti74 will get a chance before I do :) I tried to build Linux 5.0.rc7 to test as well but make-kpkg kept hanging on Debian unstable (yes cross compile).by mpmc - Debian
@arti74 I have both! The S with 4.20 is fine as it uses a different Ethernet chipby mpmc - Debian
It's just a driver issue :)by mpmc - Debian
I hadn't updated the box for a bit I was still on 4.16 I think. I can try with 4.20.6 if you'd like. EDIT: Sorry I am on 4.20.6! Edit 2: Looking at kernel.org there are SO many changes to the driver it could be any one of them >.<by mpmc - Debian
Yes, I'm getting this on my box as well. [ 9.575337] systemd[1]: Detected architecture arm. [ 9.625431] systemd[1]: Set hostname to <nsa310a>. [ 9.697020] random: systemd: uninitialized urandom read (16 bytes read) [ 9.836602] random: systemd-gpt-aut: uninitialized urandom read (16 bytes reaby mpmc - Debian
mark@nsa310s:~$ ls -lart /boot total 26348 drwxr-xr-x 21 root root 4096 Nov 29 20:12 .. -rw-r--r-- 1 root root 157130 Apr 9 08:49 config-4.16.1-kirkwood-tld-1 -rw------- 1 root root 2633202 Apr 9 14:34 System.map-4.16.1-kirkwood-tld-1 -rw------- 1 root root 4065544 Apr 9 14:34 vmlinuz-4.16.1-kirkwood-tld-1 drwxr-xr-x 2 root root 4096 Apr 10 06:56 dts -rw-r--r-- 1 root rootby mpmc - Debian
bodhi Wrote: ------------------------------------------------------- > mpmc, > > > On the B however, it was a little harder as > there > > was no "initrd.img-4.16.1-kirkwood-tld-1" > included > > to the tars so couldn't generate the uinitrd. > > Thankfully I was able to copy it over from the S > & > > it booted up fine!by mpmc - Debian
Thanks for your hard work on these kernels Bodhi. Upgraded both my NSA310B (stock uboot and own rootfs) and NSA310S (your uboot and rootfs) to the latest 4.16. The upgrade on the S went fine, no problem. On the B however, it was a little harder as there was no "initrd.img-4.16.1-kirkwood-tld-1" included to the tars so couldn't generate the uinitrd. Thankfully I was able to cby mpmc - Debian
Re-installing / setting up my NSA310 & NSA310S & I noticed the NSA310 gets extremely hot, even just idling the CPU is too hot to touch for more than a few seconds.The NSA310S on the other hand isn't as hot, but I have noticed it's much slower. I can only assume that Zyxel noticed this and released the S variant to fix it. I'm planning on getting a small heatsink to try aby mpmc - uBoot
I'm still struggling to get the thing to load a kernel image over 3.1mb. It's more than likely being truncated, leading to a CRC error.. NSA3x0S> fatload usb 0 0x800000 boot.uImage-nsa310s reading boot.uImage-nsa310s 3231728 bytes read in 139 ms (22.2 MiB/s) NSA3x0S> fatload usb 0 0xb00000 initrd reading initrd 9437184 bytes read in 339 ms (26.5 MiB/s) NSA3x0S> setenby mpmc - Debian
bodhi Wrote: ------------------------------------------------------- > .. snip .. Thanks for answering, shame you can't get a rescue system going, but I it's not a big deal :) I'll fix those little issues & put it all back together, then move onto the NSA310 & maybe my ix2 after :pby mpmc - Debian
That thread split was a wild ride! @jst818 Good catch, I'll update that, but even it it's wrong it doesn't cause too much of an issue as I'm attaching the dtb to the kernel image anyway (for now). @bodhi I kind of answered one of my own questions, "can I load my kernel/Initrd images like on the stock uboot", the answer to that is, yes! It worked fine.by mpmc - Debian
Update! I took the risk/plunge and upgraded to your uboot on my NSA310S (I'm planning on doing the old NSA310, Is it A or B, I can't tell which I have, it's the one with the lm85 sensor. It's the original one). It was a bit hairy in places as I kept getting CRC errors when running fw_printenv in Debian, but looked on another thread in which you told someone else to ignoby mpmc - Debian