Hi, @Gaogao in your kernel log there is something like it913x: Unknown tuner ID applying default 0x60<6>[11260.049966] maybe the tuner of your dvb device is not identified correctly, and than as a first guess the driver uses a default i2c adress e.g. 0x60, but can not get the tuner initialised??? and than the probing of the device fails, after the firmware is loaded,.. pleaby pbg4 - Debian
Hi, the latest Kernel linux-3.14.0-kirkwood-tld-2 package uploaded recently now includes support for some additional tevii, terratec and technotrend dvb-s2 devices based on the latest patch which I have send to bodhi before building the new kernel package, on my iConnect everything is working fine so far,.. those users of bodhi's kernel package who are interested to test the driverby pbg4 - Debian
Hi bodhi, on the iConnect I was able to test the 3.14 kernel this weekend, everything is running smoothly, however the dvb-usb-dw2102 driver was not able to recognize the usb-id of the tt-s2-4600,.. (i.e 0b48:3011 from Technotrend ), the other device I could test is the 0ccd:00a8 TerraTec dvb-s2 usb card, this is working fine so far,.. when I applied the linux-3.14.0-tld-1-kirkwood.patby pbg4 - Debian
Hi bodhi, please have a look into your pm's, I just sent you the patch for the dvb-usb-dw2102 driver including support for the tt-s2-4600 and some other dvb-usb S2 devices not in mainline kernel land until now, perhaps the patch is suited for inclusion into forthcoming kernel versions of your thread here,... there has been some discussion in early november last year between anttiby pbg4 - Debian
Hi bodhi, my card also has the ASM1061 controller and the other a usb 3.0 chip from NEC, of course will start with UART booting and report back here,.. best wishes pbg4by pbg4 - Debian
Hi bodhi, exactly, the iConnect definitely has its merits with respect to NAND size and compact design and in the combination of features,.. as I have my iConnect attached to the GB net the mini pcie card slot is empty at the moment, because I have detached the Ralink wlan card to save some energy,.. though it's only a half length card I have both a mini pcie sata card and an usb 3.by pbg4 - Debian
Hi bodhi, ..., definitely, but after the dist-upgrade I have to get a couple of wheezeboxes to sound right,.. :) best wishes pbg4 p.s. when I send you the patch for the s2-liplianin dvb-usb-dw2102 per pm, would it be possible to include that in further updates?? of course with maintenance on my side, perhaps it would make some users out there happy,..by pbg4 - Debian
Hi bodhi, the only reason is that the iConnect is serving all the squeezebox stuff in my house, because it has the smallest energy budget for running in 24/7 mode around the year,... so ist is long overdue that all the masses of services running there should have been dist-upgraded to wheezy,.. that is the only reason,.. and the time for doing that,.. best wishes pbg4by pbg4 - Debian
Hi there is another simple solution,.. since I have two NSA320 and an iConnect - which among other services stream DVB-S2 TV- and RADIO Transponders in the WLAN for SONOS and Squeezbox devices all the time - I took some usb 2.0 enclosures I had around and populated them with cheap SANDISK SSD 64GB or 128 GB, no problems any longer on the iConnect for 2 years now,.. the NSA320 internal sby pbg4 - Debian
Hi bodhi, thanks again for your last effort, finally last weekend I had some time to test your 3.13.1-kirkwood-tld-2 kernel on NSA320 and iConnect,.. everything is working smoothly, as my iConnect still has a debian squeeze rootfs I had some problems with the installation of the header files, because with this version 3.13.1 ncurses-5.9 is mandatory in the depends,.. (actually dependsby pbg4 - Debian
Hi, @Rick, last weekend I had the time to test bodhi's new 3.13.1 kernel release on NSA320 and iConnect, everything was fine,... just a few words how to compile dvb-usb-dw2102 for the TT-S2-4600 and a whole bunch of other dvb-usb dvb-s2 devices,.. first you can forget about the idea of getting a complete compilation of s2-liplianin with anything newer than 3.11 linux kernels,by pbg4 - Debian
Hi, @SOL may be I am wrong, but isn't your DNS323 an ORION type of SOC with a 500 MHz Marvell 88f5182-a2 core??,... so provided you have a uboot which is able to boot from usb and a newer kernel which is able to interact with bodhi's wheezy rootfs, this should in principle be possible,.. but would need some efforts from your side definitely,.. @nekitip if you review theby pbg4 - Debian
Hi, @racic for the gpio events and bodhi's new 3.12 kernels you can use esekeyd which works slightly better than the input-event-daemon (the other alternative), simply apt-get install esekeyd and configure it, you can test the events with evtest, which should give you something like evtest /dev/input/event0 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x1 prby pbg4 - Debian
Hi bodhi, thanks again for your effort to bring 3.12 mainline kernel to our kirkwood arm devices !!, on NSA320 and iConnect everything is running smoothely, exept some minor quirks, please add --- drivers/hwmon/Kconfig.orig 2014-01-09 20:35:23.000000000 +0100 +++ drivers/hwmon/Kconfig 2014-01-09 18:21:16.000000000 +0100 @@ -1555,7 +1555,7 @@ config SENSORS_NSA3XX tristate "by pbg4 - Debian
@bodhi: good point you made with different uBoot versions on NSA320, both of my boxes still have the stock firmware zyxel uBoot, maybe I should test davygravy's uBoot version,... he explicitly mentions the ability to boot from BOTH sata ports with his uBoot version,.. which seems not to work with the stock uBoot,.. and also incorporated the fix IDE_BUS(dev) macro,.. so perhaps theby pbg4 - Debian
@bodhi: I have not rebuild the 3.10 kernel used on my NSA320 to a newer version since quite a while, but I see no reason why your ide-led patch should not work on the NSA320, since I need s2-liplianin-v39 drivers for some dvbs usb dongles on my NSA320 boxes I'm going to stick to the 3.10 series and will test it and report back after a rebuild,.... best wishes pbg4by pbg4 - Debian
@enavarrocu: lm-sensors on the NSA320 can get activated quite easily,... you will only need to get the nsa3xx_hwmon module compiled, which is already included in the patch used for the linux-3.11.1-kirkwood-tld-2-bodhi kernel, but not yet activated in the config, if you want to compile it yourself you can use my recipe for recompiling all the hwmon modules which is already posted inby pbg4 - Debian
Hi bodhi, yes, the timer trigger is not really necessary, and I favour your patch because it has the least amount of code lines to get the leds for individual disks working, so its easy to incorporate into the next kernel generations,.. best wishes pbg4by pbg4 - Debian
Hi bodhi, the following link leads directly to the page where the patch mentioned (from Piotr Gozdur Nas-central forum member) with the version v5.2 is linked to (see post no 9 down the page), I looked through it, there seems to be nothing concerning the device-by-path problem, the download link of the patch is still working,.. best wishes pbg4 nas-central zyxel subforum nsa310/320by pbg4 - Debian
Hi bodhi, in the nas-central forum thread on the nsa310/320 kernel in the zyxel subforum there was a while ago a patch for full sata-disk and usb-disk activity, look for nsa3x0.patch_v5.2.txt where everything was included, there are modified versions of "LED IDE-Disk Activity Trigger" subroutine in it, however this means quite some work to adopt for newer kernel, it was on my todoby pbg4 - Debian
@enavarrocu: Hi, it's good that you got the ide-disk trigger leds working, that's fine,... but at the moment both leds for the two sata ports of the sata_mv.c driver behave identical, unless someone is going to invest some time for coding a better patch than this, which of course is a good starting point: diff -ruN a/drivers/ata/sata_mv.c b/drivers/ata/sata_mv.c --- a/driverby pbg4 - Debian
Hi enavarrocu, as bodhi pointed out you can change the leds behaviour in rc.local and adapt it to your specific needs, perhaps it is better to use the ide-disk trigger, my rc.local on a nsa320 with a 3.10.1 ARCH ALARM type kernel contains something like: (which off course you could use also for bodhi's 3.10.4 kernel) if [ -d /sys/class/leds/nsa320:orange:sys ]; then echo noneby pbg4 - Debian
Hi, @gaogao, good to hear, that you got the shutdown button working,.. @bodhi, this weekend I had some time to test your 3.10.4 kernel packages (image and header files) on my iConnect, everything is fine, with a debian squeeze rootfs,.. only the lm63 module for hwmon is missing, .. thanks!! I just recompiled the lm63 module and everything is working now, because this recompilby pbg4 - Debian
Hi, just some comments concerning the NSA320 and the power button,.. I have not tested bodhi's 3.10.4 kernel yet, but: on one of my NSA320 boxes here there ist 3.10.1 mainline kernel running with full ARCH patches and with some minor patches I added because of the sata leds together with bodhi's debian rootfs,.. the power button is working nicely, the input event daemon waitsby pbg4 - Debian
Hi bodhi, please have a look at https://github.com/archlinuxarm/PKGBUILDs/tree/master/core/linux-kirkwood the archlinuxarm patch is ready for 3.10.7 and there was nothing in the forums there concerning usb boot problems, best wishes pbg4by pbg4 - Debian
@bodhi, the zyxel NSA320 has according to its specs: "Gigabit jumbo frame support up to 9K bytes" best wishes pbg4 p.s. I have two of these boxes running under debian, the only problem ist to silence the fan inside, the rest is good value,..by pbg4 - Debian
Hi bodhi, on my NSA320 (with your wheezy rootfs) since several weeks there is a 3.10.1 kernel running with full ARCH patches for quite a while with superior performance,.. the ARCH guys also use the Marvell Phy !!,.. I tested that because of my problems with the generic PHY documented in this forum,... a quick comparison of the dmesg output shows, that you have ata1: SATA link downby pbg4 - Debian
@bodhi, pleases have a look at http://archlinuxarm.org/forum/viewtopic.php?f=27&t=3708&start=30 and http://archlinuxarm.org/forum/viewtopic.php?f=27&t=3851 where the power_resume.sh is discussed, the thread is rather messy so I simply quote the statements from WarheadsSE: "on the nsa320 we have also learned how to set the return from power loss behavior, Apparently,by pbg4 - Debian
Hi wacek, just did a quick test, I got also the same info as you had in your first post: root@debian:~# ethtool -s eth0 wol g Cannot get current wake-on-lan settings: Operation not supported not setting wol but if I shutdown the nsa320 with shutdown -P -h now and than issue a wakeonlan -i 192.168.0.255 c8:6c:87:95:f9:1e on another machine, the nsa320 wakes up and boots as requby pbg4 - Debian
Hi Syong, which uboot are you using on your nsa320, the stock uboot or davys version?? I just posted in bodhi's linux kernel thread, that I also had problems with gigabit ethernet and cured them temporaily by setting the phy of eth0 to Speed: 1000Mb/s and Duplex: Full hard coded in the nsa320-setup.c routine,.. now of course autonegotiation is lost, but I had this problem also witby pbg4 - Debian