Thanks bodhi .. I cannot do this all the time anymore .. so .. didn't noticed ...by pengu - Debian
The USB Serial converter .... I'm using a fiew cp210x based ones .. and I'm seeing the following: To power up the device, I have to disconnect tx/rx for a while to bring the box up. The next thing is that ZyXEL OS is starting ... whenever I connect the serial cable to the box ... To use Debian again, I have to disconnect the serial cable while the system is running .. I'mby pengu - Debian
same here .. tested with all mentioned DTBs ..by pengu - Debian
YES it's based on your config as my kirkwood kernel builds were too. The patch can still be applied without failures I think its usable but ... see below. The file attached is diff between your config and the one I'm using now. lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.0 (stretch) Release: 9.0 Codename: stretby pengu - Debian
Yes it's amber ... (Kernel 4.9, 4.10 and now 4.11 rc2)by pengu - Debian
Still no sources, see here: http://www.zyxelforum.de/viewtopic.php?f=306&t=9904by pengu - Debian
ok it's back here again so I can have a closer look on it. After doing a apt-get purge mdadm && apt-get install mdadm the RAID (0 or 1) is back again. It also survives a reboot (as it should)by pengu - Debian
As I mentioned earlier, I have to use bodhis kernel because with all of my builds, only one HDD appears. I didn't have that box anymore but it seems to have an RAID issue. When creating a RAID0 it's still there after rebooting the box but a RAID 1 doesn't apeear after reboot. Same rootfs, my kernel (4.4.6 and 4.4.18) on Iomega ix2-200) all good, the RAID appears. [ 9.7by pengu - Debian
You can use the oxnas rootfs + kernel from here Another way is described here. It's possible to use the Kirkwood rootfs, build a Oxnas kernel (what I've done) and install it to that rootfs. Atm I'm using vanilla 4.4.16 + patches from OpenWrt + modified config from the Oxnas Rootfs + Kernel thread. The only thing you have to keep in mind is that you have to embed the DTS whenby pengu - Debian
I've got a fiew Pogoplug v3 / pro devices which doesn't boot propery. With serial attached I noticed that U-Boot env is modified. The stock kernel is booting up but a rootfs cannot be found. I think a fiew people have modified their boxes in that way because there wasn't any newer U-Boot available and accessing / booting from USB isn't possible in stock U-Boot. So theyby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > CableCat Wrote: > -------------------------------------------------- > ----- > > bodhi Wrote: > > > -------------------------------------------------- > > > ----- > > > No. I don't have the Iomega ix4-300d and it > has > > > not been supported in the mainlby pengu - Debian
a NSA310 box is here again so I could have a closer look again on it. I tried to compare the raw network throughput (iperf) and I see some differences: With the "r8169" driver, you can get : 300 - 600 MBit (NSA310 server) 200 - 500 mbit/s (NSA310 client). This changes a bit when it comes to the "r8168" driver: 700 MBit (NSA310 server) 700 MBIt - 900 MBit (Nby pengu - Debian
ok ... kernel 4.4.12 is running ... I'm trying with .. java -jar -Xms16m -Xmx32m free -m total used free shared buffers cached Mem: 118 106 11 0 1 10 -/+ buffers/cache: 94 23 Swap: 149 40 109 lsmod Module Size Used by cpufreq_cby pengu - Debian
> > > > [ 2.776931] : > > /ocp@f1000000/mdio-bus@72004/ethernet-phy@1: > > Whitelisted compatible string. Please remove > > > > > > At the moment everything works fine, nothing to > > complain. Wanted to know if i can ignore this > > warning. I've seen that too (when using old DTB, and the network device appears .. witby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu > > Well, if you look at the code, looks like the > firmware loading has not been completed. And that > does not have anything to do with pintctrl. > > > [ 12.662092] usb 1-1.2: dvb_usb_v2: found a > 'Hauppauge WinTV-MiniStick 2' in cold state > [ 12.773961] usbby pengu - Debian
let's see .. sysctl --system * Applying /etc/sysctl.conf ... net.core.rmem_max = 2097152 net.core.wmem_max = 2097152 net.ipv4.tcp_rmem = 4096 87380 2097152 net.ipv4.tcp_wmem = 4096 16384 2097152 vm.min_free_kbytes = 16384 (the rest is taken from my kirkwood image) free -m total used free shared buffers cached Mem: 117by pengu - Debian
the firmware (dvb-usb-it9135-02.fw) is in /lib/firmware and it gets loaded when running linux-4.5.6 and earlier and doesn't load when running linux-4.6.0 and later. The firmware files can be found here and the recommanded file which works when running Linux-4.5.6 and earlier can be found here. Same thing when using MSI DigiVox Mini II (dvb-usb-af9015.fw) (arm only) The recommanded andby pengu - Debian
downloaded, testet, working ... There is something wrong with your download (faulty internet connection I think. MD5 should be: 2adb2405b7413c9f41d5c9683f7f3eebby pengu - Debian
The problem persists in linux-4.7-rc1 .. [ 0.000000] Linux version 4.7.0-rc1-kirkwood-rm-2 (root@debianNSA325v2) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 PREEMPT Sat Jun 4 03:50:52 CEST 2016 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine model: Iomega Iconnect ... ..by pengu - Debian
perhaps, JD is too much for this box: swapper/0: page allocation failure: order:0, mode:0x2080020 CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.11-oxnas-rm-1 #1 Hardware name: PLXTECH NAS782X SoC (Flattened Device Tree) [<c0010c6c>] (unwind_backtrace) from [<c000cf9c>] (show_stack+0x10/0x14) [<c000cf9c>] (show_stack) from [<c02b7780>] (dump_stack+0x84/0xa0)by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > Thanks pengu, > > > cp /usr/bin/qemu-arm <location of the mounted > > stick>/usr/bin > > chroot <location of the mounted stick> > /bin/bash > > You could have chroot directly into it in a > kirkwood box, too, no qemu needed. qemu is needed and also this: mouby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > Do you remember how you created this rootfs? based > on which version? The rootfs is based un my Kirkwood rootfs and this is based on your "Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2" As you mentioned earlier, I only have to replace the kernel and that's what I've done. To do this,by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > @pengu, > > Are these u-boot SPL and u-boot version still on > this box? > yes they are.by pengu - Debian
$ uptime 16:37:05 up 2 days, 12:51, 1 user, load average: 0,35, 0,26, 0,24 thats the third one ... as you can see .. I should replace the HDD (perhaps). I see nothing like that on the other two devices. Booting Linux on physical CPU 0x0 Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Initializing cgroup subsys cpuacct Linux version 4.4.11-oxnas-rm-1 (rootby pengu - Debian
confirmed ... OX810SE -->ARM926EJ-S --> ARM9 Edit: first tests made .... Iperf : 600 mbit (tcp) samba 38 mb/s read, 32 mb/s write (windows 8.1 and 10) when comparing the tcp throughput with other devices, I see the following: D-Link DIR-825 (560 MHz, atheros): 300 mbit (tcp) 1000 mbit (udp) D-Link DIR-645 (500 MHz, ralink): 300 mbit (tcp) 1000 mbit (uby pengu - Debian
it seems that wie do not need all the patches in future. The Oxnas target is now available in Kernel 4.7by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > And thanks for the OXNAS patch files. Did you use > their config, mine, or your own? I'm using a config based on your oxnas config (4.1.0) >I would like you to run this with samba, nfs, ntpd, autofs, and possibly other apps that you normally run. Please post back a >couple days from now. I willby pengu - Debian
> > Mostly, not possible. Recent mainline u-boot does > not support chainloading a substantially different > u-boot from itself. I think the problem is, that most U-Boot builds use the same memory. > > What you need to do in case of bad blocks is > repartitioning MTDs (if necessary) and make sure > it has enough good blocks to flash u-boot. U-Boot must beby pengu - uBoot
news news .. after booting the 4.4.11 kernel, I could build this kernel without gcc confusion. The mentioned hung between the two bootloader stages is also gone (till now) the shutdown: in ZyXEL OS, the device reboots, wenn issuing a poweroff or halt .. with the 4.4.11 kernel using stg-212 dtb ... the HDD is spinning down but it doesn't fully power off ( still 3,9W) but I thinkby pengu - Debian
I've read that some guys have bad blocks (0 - 1024 kb) and there is no place for flashing U-Boot in typical size (512 kb - 1 mb). is it possible to "jump" to another working NAND position and start U-Boot there? The loader (U-Boot) which can do this should be configured freely. I remember that is was possible to start another U-Boot from stock U-Boot (Cloud Engines) Is it posby pengu - uBoot