All working here thanks to your instructions: the NSA booted just fine from sata. Kudos!by gaogao - uBoot
ouch :( Anyway, YES and YES: gaogao@mynas:~$ cat /etc/fw_env.config # MTD device nameDevice offsetEnv. sizeFlash sector sizeNumber of sectors /dev/mtd0 0xc0000 0x20000 0x20000 gaogao@mynas:~$ ls -lh uboot.2013.10-tld-1.nsa320.mtd0.kwb -rwxr--r-- 1 gaogao gaogao 384K Aug 18 09:06 uboot.2013.10-tld-1.nsa320.mtd0.kwb gaogao@mynas:~ md5sum uboot.2013.10-tld-1.nsa320.mtd0.kwb b83ebby gaogao - uBoot
@bodhi: as requested serial boot log dmesg output fw_printenv output TKSby gaogao - uBoot
Brilliant! Not only it reads the disk partitions properly, but also the current uboot environment; as a result it booted directly to my previously populated HDD partition :) I assume it's then safe to flash it, pls confirm.by gaogao - uBoot
Tks! Can't wait :) Have you noticed the misleading message given by ext4ls? NSA320> ext4ls ide 0:2 / Failed to mount ext2 filesystem...by gaogao - uBoot
tks bodhi for the tip, "-p" made it work: 99 % [....................................] U-Boot 2013.10-tld-0.1 (Jul 24 2014 - 15:03:15) ZyXEL NSA320 2-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 128 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: egiga0by gaogao - uBoot
bodhi; ETA 2 weeks... (TKS!)by gaogao - uBoot
I took my chances and modified the kernel params introducing 'coherent_pool=1M': success! Tks everyone!by gaogao - Debian
tks bodhi, I was under the assumption that using fw_setenv was not the preferred/safe way to set uboot params. IIRC I read about it some time ago. I'll try during the weekend and report back. Tks a lot!by gaogao - Debian
bingo! [ 32.465001] usb 1-1.2: dvb_usb_v2: found a 'Avermedia A835B(3835)' in warm state [ 32.475491] usb 1-1.2: dvb_usb_v2: will pass the complete MPEG2 transport stream to the software demuxer [ 32.485321] ERROR: 256 KiB atomic DMA coherent pool is too small! [ 32.485321] Please increase it with coherent_pool= kernel parameter! [ 32.499627] dvb_usb_it913x: probe ofby gaogao - Debian
Hi, @pbg4: maybe I'm missing something here: $ sudo modprobe dvb_usb_it913x info=1 Jun 20 19:54:42 mynas kernel: [264086.446133] dvb_usb_it913x: unknown parameter 'info' ignored Jun 20 19:54:42 mynas kernel: [264086.457459] it913x: Chip Version=02 Chip Type=9135 Jun 20 19:54:42 mynas kernel: [264086.463084] it913x: Firmware Version 52953344it913x: Remote propriety (rawby gaogao - Debian
pbg4 Wrote: ------------------------------------------------------- > what happens when you load the frontend by hand? unfortunately same error, I tried that alreadyby gaogao - Debian
bodhi Wrote: ------------------------------------------------------- > Compare the output of > > lsmod > lsusb > here they are attachedby gaogao - Debian
NSA320, Linux mynas 3.13.1-kirkwood-tld-2 #1 PREEMPT Tue Feb 4 03:19:07 PST 2014 armv5tel GNU/Linux Tuner: Bus 001 Device 014: ID 07ca:850a AVerMedia Technologies, Inc. AverTV Volar Black HD (A850) I am not able to make my new USB tuner initialise properly, I have proper firmware files and on a standard ubuntu server with kernel 3.13 the tuner inits fine. I wonder if it's a kernel issuby gaogao - Debian
any luck for the NSA-320?by gaogao - uBoot
they do react properly both red and green. What appears to be not working is the trigger to ide-disk2 (on both LEDs). It seems as only ide-disk1 is ok.by gaogao - Debian
bodhi Wrote: > What is your output of: > ls -R /sys/class/leds $ ls -lR /sys/class/leds /sys/class/leds: total 0 lrwxrwxrwx 1 root root 0 Oct 21 19:25 nsa320:green:copy -> ../../devices/platform/leds-gpio/leds/nsa320:green:copy lrwxrwxrwx 1 root root 0 Oct 21 19:25 nsa320:green:hdd1 -> ../../devices/platform/leds-gpio/leds/nsa320:green:hdd1 lrwxrwxrwx 1 root root 0 Oct 2by gaogao - Debian
The second LED does not reflect second HDD accesses for me, the first one seems to be doing both hdd despite: root@mynas:~$ cat /sys/class/leds/nsa320:red:hdd1/trigger none nand-disk timer oneshot ide-disk2 heartbeat gpio default-on root@mynas:~$ cat /sys/class/leds/nsa320:red:hdd2/trigger none nand-disk timer oneshot ide-disk1 heartbeat gpio default-on @pbg4: can you paste your rc.loby gaogao - Debian
bodhi Wrote: ------------------------------------------------------- > I can see /dev/sda is one of your internal SATA > disks. But the other one? which letter is that one > assigned to? ah, I forgot to disconned the external usb disk (sdc). The SATA disks are sda and sdb.by gaogao - Debian
@bodhi, as I noticed the same LED behaviour: root@mynas:/tmp$ ls -lR /dev/disk/ /dev/disk/: total 0 drwxr-xr-x 2 root root 300 Oct 6 20:47 by-id drwxr-xr-x 2 root root 80 Oct 6 20:47 by-label drwxr-xr-x 2 root root 180 Oct 6 20:47 by-path drwxr-xr-x 2 root root 120 Oct 6 20:47 by-uuid /dev/disk/by-id: total 0 lrwxrwxrwx 1 root root 9 Oct 6 20:09 ata-ST4000DM000-1F2168_W300Fby gaogao - Debian
@pbg4: everything here seems to be the same: $ ll /dev/input/by-path total 0 drwxr-xr-x 2 root root 60 Aug 23 12:17 . drwxr-xr-x 3 root root 100 Aug 23 12:17 .. lrwxrwxrwx 1 root root 9 Aug 23 12:17 platform-gpio-keys-event -> ../event0 $ cat /etc/input-event-daemon.conf # # /etc/input-event-daemon.conf # listen = /dev/input/event0 POWER = shutdown -h now so eithby gaogao - Debian
bodhi Wrote: > I will release 3.10.4 with this config option (in > a couple days).You can give it a try then! unfortunately it did not help, still no events from the power button. TKS for the update anyway!by gaogao - Debian
can't wait then :) TIAby gaogao - Debian
I noticed that I can't shutdown my NSA320 using power button in combination with input-event-daemon. It seems the event is not generated as polling /dev/input/event0 leads to no results. Could it be something related to 3.9.11-kirkwood-tld-1 ?by gaogao - Debian
Aren't you able to UART-boot? if you are, type the saveenv before trying to write uboot again.by gaogao - Debian
as I apparently did at that time: >EDIT EDIT: saveenv from u-boot prompt cured the CRC! try that, it worked for me.by gaogao - Debian
magnificent job, works as a charm on NSA320: usb 1-1.3: dvb_usb_v2: 'AverMedia AVerTV Volar Black HD (A850)' successfully initialized and connected tks a lot!by gaogao - Debian
bodhi Wrote: > Dvb drivers probably were not included in kernel > config (I don't have any video device attached so > never noticed that). If anybody wanted to request > some video drivers to be included, then please > post the specific module info, I will recompile > another version for it. Device name (as known to > Linux) and the ko file name(s) are needed.by gaogao - Debian
tks, hopefully these changes will soon be incorporated in Jeff's packages.by gaogao - uBoot