While I can't offer any specific advice I suspect the problem might be the weak CPU. btrfs might hit your CPU a bit. If "top" indeed shows high CPU utilization during the copy you might want to try another file system like ext4 or even vfat (just to verify where the bottleneck is).by Muchatet - Debian
desigabri Wrote: > I'll try in this way. I think I'm so confused > because i read about differents way to install > Debian, and some tell that it isn't necessary > modify the bootloader, some using installers, some > using serial access. Linux is flexible so each possible way is explored at least once. The total picture can be confusing then if you see allby Muchatet - Debian
desigabri Wrote: > It seems to me that some basic information aren't > explained, and I can't find them anywhere. This > should mean that they are logical things, but I > don't understand them anyway. I totally feel your pain. Especially if you don't know embedded Linux inside out it's very confusing. But on the plus side the forum is really helpful soby Muchatet - Debian
addy75 Wrote: > Is it possible to upgrade von debian7 to debian8? > Is there any andvantage turning to debian8? Yes, it is possible (just do like you would do it for any other Debian install). Debian 7 (Wheezy) won't get update after (roughly) April next year so at some point you should update (maybe the Debian LTS project can extend this time for some years, let's see). Bby Muchatet - Debian
shv Wrote: > prefere a patch for the stock xhci module to > prevent any possible drawback due to kernel > exchange. If we find a solution it might be > regarded by Zyxel for the next FW update of the > "old" hardware generation. I can totally understand that but I think it will not work this way: Building a kernel for the old firmware seems quite a hassle to me.by Muchatet - Debian
Just to try an explanantion from a different angle: The device tree mechanism is an approach to fix "shortcomings" of the ARM architecture. In the x86 world all devices are discoverable. So the kernel can query the PCIe bus or the USB bus to know which hardware is present and loads drivers/modules accordingly. In the ARM world it works differently: There is a huge variety between deby Muchatet - Debian
bodhi Wrote: ------------------------------------------------------- > Since kernel 4.3 has some problem with cryptodev, are you referring to https://github.com/cryptodev-linux/cryptodev-linux/issues/10 ?by Muchatet - Debian
I think I tried that but in fact I think I might have been unlucky: With some (older) USB drives the memory write works as expected (but very likely I didn't try the mw.l for them). However I ordered some new drives and here I only get uboot hangs: Hit any key to stop autoboot: 0 Marvell>> mw.l f1010100 0020c000 Marvell>> usb reset (Re)start USB... USB: scanning busby Muchatet - uBoot
I have a NSA325v2 which is working just fine (flashed the 2014.07 uboot version, Debian Jessie, ...). Now I got a second box and it seems Zyxel did change something. I'd like to know if someone else observed the same or if I'm doing something stupid here... Problem description For the live of it I can't get the stock uboot to recognize my USB flash drive (it works just fine oncby Muchatet - uBoot
I'd like to say thank you to all the helpful comments replying patiently to my questions. As usual I find it much easier to understand all the previous comments once I understood how it should be done in the end. I was able to fix my CRC errors by setting the correct addresses in /etc/fw_env.config as bodhi suggested.by Muchatet - Debian
I just installed Debian on my NSA325v2 and I have to say that it works quite nicely so far. Thank you very much for all the hard work which surely went into this project. Now I have some questions – I read quite a few threads but I have to admit I didn't read all 40 pages of this top for example. 1. Is there an overview which modifications the root fs tarball contains (over a pristinby Muchatet - Debian