4.4.11 is booting ... http://pastebin.com/VqLPKXZe ... Scan device usb device usb 0:1by pengu - Debian
sorry if I didn't mentioned .. the firmware is still in /lib/firmware and it's running fine now with kernel 4.5.5.by pengu - Debian
kernel 4.4 is ready for testing but building was not successful at first try. I decided to do this on the Medion NAS with -j3, gcc sometimes gets confused. And .. there is another little "problem" ... When the system is running for some hours and I issue a reboot ... it doesn't come back ... U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12)by pengu - Debian
coherency problem? this (4.1 and above) seems to describe it and give some solutions? how can I evoke this reproducable?by pengu - Debian
I'm using this and this tutorial but with some modifications to get debian up and running on this devices. The Medion / ZyXEL firmware has no "flash_erase" so I use flash_eraseall. NOTE: In ZyXEL OS, "mtd0" seems to represent the whole flash, so please backup! nanddump -i --omitoob -f mtd0 /dev/mtd0 nanddump doesn't support --noecc, so I use -iby pengu - Debian
I'm using kernel 4.6.0 on all mentioned devices (kirkwood and x86_64) devices and no matter which firmware I use, the error stays the same. The DVB stuff isn't affected because the situation doesn't change when bulding and using drivers from media_build git the problem appears when probing and only a some but not all afatech based sticks were affected. /* * Ensureby pengu - Debian
- Hauppauge WinTV MiniStick 2 (NSA325, iConnect, x86_64) (prod: f900 ven: 2040) - MSI Digi Vox Mini II (black / white) (NSA325, iConnect) (prod: 9016 ven: 15a4) as mentioned in the linux kernel thread, this sticks cannot be used in kernel 4.6 as they were fully functional in linux 4.5.5 and earlier. after searching a bit around, I found out, that there were some changes betby pengu - Debian
news news .. "hwmon" is now working on NSA320 with kernel 4.6 [ 0.000000] Linux version 4.6.0-kirkwood-rm-1 (root@debianNSA325v2) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Mon May 16 16:26:59 CEST 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machiby pengu - Debian
I think he has one device connected this device only has one USB port.by pengu - Debian
I've seen this on my GFN's with earlier kernels too one day after the device boot. The only way to solve this for me was to use an USB HUB.by pengu - Debian
with kernel 4.6, the LAN isn't working as seen with kernel 4.5by pengu - Debian
kernel 4.6 is out ... it's running on my NSA325 and iconnect ... let's see .. The Hauppauge WinTV MiniStick 2 which I'm using for several months with several kernel versions isn't working anymore .. The firmware cannot be loaded .. (testet two different versions, no luck) Unfortunately, I cannot find any of my other sticks, so I cannot change. [ 1058.488465] usby pengu - Debian
Edit it's working now (4.0.9) no need to run as root. I'll update my first post.by pengu - Debian
The ix2-200 (as mentioned above) is working fine since kernel 4.3 The ix2-dl is usable but has, depending on the hardware, some issues like the NSA325v2 and NSA320s (poweroff doesn't work). And there is no special DTB for this device, but you can use the one for ix2-200. Another thing is that, I think because of this, the NAND (ix2-dl) is unusable inside Debian.by pengu - Debian
bodhi Wrote: ------------------------------------------------------- No, you can't use > fw_printenv or fw_setenv. You need to find the > stock version of this. Log into to stock OS and > try fw_printenv to see if it even there. on ix2-200 it can be resolved I think .. on ix2-dl .. it will be tricky I don't see any output after 'Starting kernel ...by pengu - Debian
U-Boot stuff from ix2-dl: http://pastebin.com/wYKsvPY0 I hope that I've backed up it correctly: mtdparts ix2-200: mtdparts=nand_mtd:0x100000@0(uboot)ro,0x20000@0xA0000(uboot_env),0x300000@0x900000(kernel),0x1400000@0xC00000(root),0x6000000@0x2000000(root2),0x300000@0x100000(iomega_zImage),0x300000@0x540000(iomega_initrd) mtdparts ix2-dl: mtdparts=nand_mtd:0x80000@0(ubootby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > You are using the ix2-200 DTS for the ix2-dl. Are > you sure they are based on the same box? what are > the differences between these 2? - more flash (1 GiB) - 1.6 GHz Marvell Kirkwood 88F6282 - eth0 is coming up fine - same shutdown behaviour as NSA320s / NSA325v2by pengu - Debian
I'm using the patched DTB from here. The one with proper configured MTD partitions isn't there so I have to fix this first. I'm still using Kernel 4.3.2 patched with the 4.2.0 one. This was the first one which is "stable" on this device. But as I see now, the env isn't accessable via debian. No problem with kernel 4.2. The actual bootlog: http://pastebin.cby pengu - Debian
sorry for the late response. The ix2-200 is working fine The ix2-dl is working but: - NAND isn't "recognized" correctly - power off doesn't work @didierw you can use the mentioned rootfs and howto. Since there is no modern U-Boot vor this device, you have to emded the DTB as described in 4bby pengu - Debian
here you can find the GPL Tarball including U-Boot patches The v2.1 Tarball contains the U-Boot patches which can be downloaded here and the V3.1 one contains Patches for Linux-3.3.8 or here Edit The restart thing is happening to a second EA4500 too but the router is (still) pingable. A third one isn't configurabie via original OS (bad gateway) perhaps I will connect toby pengu - Debian
@megal0maniac I'm still using OpenWrt on this box but I plan to use Debian on this device. With stock OS and OpenWrt I have the following issue: When trying to reboot, it doesn't reboot, and runs / stays in an unknown state. The other thing is, that the box runs a little bit hot (54+ degrees when idle, testet with kernel 3.18.x and 4.4.6)by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > Did it power off ok before? noby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > Now use the same stick, but with the old DTB from > kernel 4.4. then it's working fine on NSA320sby pengu - Debian
The NSA320s still doesn't power off: [ 344.951742] ------------[ cut here ]------------ [ 344.956358] WARNING: CPU: 0 PID: 1738 at drivers/power/reset/gpio-poweroff.c:45 SyS_reboot+0x14c/0x1f8() [ 344.965795] Modules linked in: ipv6 evdev orion_wdt marvell_cesa des_generic gpio_keys sg sd_mod uas usb_storage sata_mv libata fixed scsi_mod [ 344.978649] CPU: 0 PID: 1738 Comm: haltby pengu - Debian
bodhi Wrote: >would you please use a new test rootfs 4.4 on a > stick, install the complete kernel (meaning > extract the DTB also). done ... with the new rootfs .. kernel 4.4.0 .. the NSA320s is booting fine. After installing linux-4.5 (haven't touched the DTBs) it's also booting fine ... deleted the "dts" folder and unpacked the "new" one ..by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > > On NSA320s it's no problem with both Kernels > > (unpatched 4.5 rm-1 and patched 4.5 rm-2) > > Not sure I understand this. The NSA320S is not in > the mainline kernel. If it is not patched, then > you can't run it. > > Is the kirkwood-nsa320s.dtb in the stick /boot/dts >by pengu - Debian
@bodhi; the same kernel / stick was used on NSA310s and NSA320s. With unpatched ethernet driver, the LAN / PHY is absent as you mentioned. With patched ethernet driver, I get the mentionend error while initializing the LAN / PHY. On NSA320s it's no problem with both Kernels (unpatched 4.5 rm-1 and patched 4.5 rm-2)by pengu - Debian
me too ... and the only "change" I've found (4.5-rc3) is this one: Nicolas Schichan (1): net: mv643xx_eth: fix packet corruption with TSO and tiny unaligned packets.by pengu - Debian
it seems that the network chip has gone in 4.5 (NSA310s, haven't tested the NSA320s yet) Edit seems to work on my NSA320s [ 0.000000] Linux version 4.5.0-kirkwood-rm-1 (root@debianNSA325v2) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Tue Mar 15 00:45:49 CET 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVby pengu - Debian
bodhi Wrote: > Hi pengu, > > Are you building 4.5? have you tried and seen > ethernet is broken in your NSA325 like I'm seeing > in the NSA310S? yes, 4,5 is running on NSA325v2 for days and now on NSA325, no problems with ethernet. I still have a NSA310s, let's see whats going on there Edit booting with 4.5 on NSA310s doesn't bring up the LAN.by pengu - Debian