Hi bodhi, Adam Bakers patch for nsa320-hwmon after long reviews got finally upstream just in time for 4.6,.. https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/diff/drivers/hwmon/nsa320-hwmon.c?id=v4.6&id2=v4.5 what puzzles me is that pengu reports nsa3xx-hwmon is working, this is the naming of my intermediate patch which is now obsolete,.. did you incorporate this intby pbg4 - Debian
Hi bodhi, this is just a confirmation for you that my second NSA320 is working fine with latest uboot.2015.10-tld-1.nsa320, it was tested with uart booting before and than flashed to mtd0, together with your latest env image, especially powering the phy for eth0 is working OK over all combinations of shutdown, poweroff, reboot, etc.,.. the only thing I did was twiddling a litte bit withby pbg4 - uBoot
Hi, the patch from Adam for nsa320-hwmon just has passed the 3. review round and is accepted, but now that the rc7 was released it is too late putting it to arm-soc for the 4.6 kernel, so it will hopefully land in 4.7 kernel, best wishes pbg4by pbg4 - Debian
Hi, the Terratec S2 Box and the S662 patch is now already in the media_tree as well, so should all be included in future releases, http://git.linuxtv.org/media_tree.git/commit/?id=6ede20f9683c55dac8281b63d80b5cc669640252 best wishes pbg4by pbg4 - Debian
Hi, @immergut, good to know it works, after you copied the new module dvb-usb-dw2102 to /lib/modules/4.4.0-kirkwood-tld-1/kernel/drivers/media/usb/dvb-usb maybe you forgot a depmod -a ? otherwise use an entry of dvb-usb-dw2102 in /etc/modules for loading at startup, as you have the device also for further testing I will send an email to Olli Salonen to include the Terratec S2 Box 0ccdby pbg4 - Debian
Hi, @sebr: to generate a suitable kirkwood-nsa310b.dts for testing you only have to patch the code block for i2c and lm85 which I posted above into kirkwood-nsa310.dts which has all the leds assigned, than compile kirkwood-nsa310b.dtb, load it in the kernel and test, and report back, maybe some finetuning of mpps and gpios is necessary, but most probably not since I diffed both verby pbg4 - Debian
Hi, if you forget for a while the minor led differences, than the real difference in kirkwood-nsa310a.dts is i2c@11000 { status = "okay"; lm85: lm85@2e { compatible = "national,lm85"; reg = <0x2e>; }; whereas in kirkwood-nsa310.dts there is i2c@11000 { status = "okay"; adt7476: adt7476a@2e { compatible = &by pbg4 - Debian
Hi, the lm9600 has three pwm1,2,3 output pins, have you tested the other pwm2 and pwm3 also? from the lm9600 pdf you linked on p.27 application diagram it is clear, that if there is no low pwm output voltage the basis of the transistor regulateing the fan voltage is pulled high by the 470 ohm resistor and the fan is on full speed,.. the nsa310 and nsa310a dts files simply differ becauseby pbg4 - Debian
Hi sebr, since the NSA310 has an lm85 compatible sensor chip i.e. an ADT7476 it should theoretically be able to control the fan by sending out a pwm modulated voltage to the fan, so pwmconfig and fancontrol from lm-sensors package should work with the right values in /etc/fancontrol,.. BUT: if you look at the pcb picture here http://masu.6f.sk/index.php?title=Nsa310_pcb there are a lot!!by pbg4 - Debian
Hi sebr, there is some discussion about fan control in nas-central zyxel forums, someone also wrote a small fan control daemon for NSA310 which you could use, perhaps you should have a look there, https://github.com/lzap/fan3xxnsa and more discussion here: http://forum.nas-central.org/viewtopic.php?f=249&t=7405 since the NSA310 ( at least the first version produced by zyxel) hby pbg4 - Debian
Hi bodhi, have you downloaded the NSA325 kernel sources?, it might be worth to look if zyxel has implemented something like a /proc/hwmon device, this was the case with NSA320 which has the least capable simple holtek mcu, but that was sufficient to implement nsa3xx-hwmon new, but because zyxel used i2cget commands to read out the values from the newer holtek mcu in the NSA325, maybeby pbg4 - Debian
Hi, in linux-arm kernel recently there were some reports which suggested it might be worth to try disabling TCP offloading in /etc/network/interfaces: auto eth0 iface eth0 inet dhcp offload-rx off # disables TCP RX offloading offload-tx off # disables TCP TX offloading in order to work around a regression introduced with kernel 4.4, so thatby pbg4 - Debian
Hi @immergut best would be to look into your terratec dvb-s2 device if frontend and demodulator chips match the version of the tt-s2-4600, i.e. montage ds3103 and ts2022, than a simple device and vendor id patch should work, because the usb bridges should be identical, otherwise the patch in the former kernels would not have worked,.. than take this short tutorial and compile dvb-usbby pbg4 - Debian
Hi, based on the activities here in the forum to get nsa3xx-hwmon working again in bodhis newer devicetree based kernels Adam Baker found my patch, after some email discussions with us he decided to clean the patch and send it upstream for inclusion in mainline, so hopefully it will be included in 4.6, lets see,.. the patch adresses the NSA320 with the old holtek mcu (factory programmed bby pbg4 - Debian
Hi, @immergut when moving to kernel 4.2 my patch for bodhi for dvb-s devices in 3.18.5 and 4.0.0 based on crazy cats git version of the old s2-liplianin drivers was not supportable any longer because of upstream changes, this relates to the terratec S2 usb box and some clones of tevii dvb-s2 usb devices, if the Terratec S2 Box 0ccd:0105 has a ds3103 dvb-frontend and ts2022 demod, it isby pbg4 - Debian
Hi bodhi, there is no need to set CONFIG_HWMON_DEBUG_CHIP=y except in a test kernel package, as this affects all hwmon sensor chips for all devices supported by the kernel, as we have already a test kernel for NSA3X0 and nsa3xx-hwmon you can leave it as it is for now, best wishes pbg4by pbg4 - Debian
Hi shivahoj, just tested the 4.2 kernel on one of my NSA320 boxes, all is fine here,.. sensors are working, just put nsa3xx-hwmon in /etc/modules to get the module loaded at boot time,.. since bodhi rightly did not activate # CONFIG_HWMON_DEBUG_CHIP (which is not set to y in the config) the hwmon debug in this production kernel 4.2 is not activated, (although it was activated in the teby pbg4 - Debian
Hi shivahoj, the only kernel tested by me which was released from bodhi with my patch for nsa3xx-hwmon included was the 4.1.0-kirkwood-tld-3-test kernel mentioned above, the link is in my answer above, this was a test kernel with a working nsa3xx-hwmon module with some debugging info spit out in the kernel messages when lm-sensors is used, if you want a working temp sensor and fan speeby pbg4 - Debian
Hi, this was the last status end of august this year 2015, http://forum.doozan.com/read.php?2,23555 both of my NSA320 systems have this kernel and are running fine and the fan speed sensor is working fine, the patch I added was a port to device tree descriptions for testing purposes,.. since nobody else tested I did not make any further modifications, that is all,.. best wishes pbgby pbg4 - Debian
Hi, I've installed the test kernel on NSA320 and can confirm that everything works with nsa3xx-hwmon on this platform as described here: http://forum.doozan.com/read.php?2,12096,23387#msg-23387 it is completely the same output with all the details given above, except,.. root@debian-jessie:~# uname -a Linux debian-jessie 4.1.0-kirkwood-tld-3-test #2 PREEMPT Thu Aug 27 00:36:56by pbg4 - Debian
Hi, the patches for the DT port of nsa3xx-hwmon are out per email to bodhi, as this was tested on my NSA320 successfully, just a hint, when looking through the sources I have found that at least three versions of NSA310 must be around, an older one with a pcf8563 realtime clock at i2c adress 0x51 which has an mcu and should be able to use nsa3xx-hwmon driver, this one very similar to Nby pbg4 - Debian
Hi bodhi, the final testing of my conversion of nsa3xx-hwmon.c to devicetree structures just has finished, it is working now, the debugging went faster because one of the linux arm kernel devs kindly helped me in the debugging phase, it is tested now for NSA320, root@debian-jessie:/usr/src/linux-4.1.0# sensors nsa3xx-isa-0000 Adapter: ISA adapter Chassis Fan: 4800 RPM Systemby pbg4 - Debian
Hi, there are no perl binaries for perl 5.20 and armel in the LMS download, only armhf or x86_64, so either you have to use the buildme.sh script and compile the needed modules natively under armel, or use this link which is still working https://server.vijge.net/static/squeezebox/arm-linux-gnueabi-thread-multi-64int.tar.gz where in this thread http://forums.slimdevices.com/showtby pbg4 - Debian
Hi, the kirkwood soc gpios 16,17 (i.e. act and clk) direction are set as output, gpio 14 (i.e. data) as input, than in mcu_status_read_fn the inner loop simply clocks out the data on the falling edge, i.e.1/0 transitions of the clock signal and writes the content bitwise in mcu_data, 16 bit temp, 8 bit rpss and 8 bit magic number, the mcu sits outside the kirkwood soc, so output directiby pbg4 - Debian
Hi bodhi, not really, at least one of the linux-arm kernel devs has answered an email I send to him, so the plan what to do is clear to me, see my answer here: http://forum.doozan.com/read.php?3,12381,23047#msg-23047 but it will take some more time due to the normal professional duties,.. best wishes pbg4by pbg4 - Debian
bodhi Wrote: ------------------------------------------------------- > shivahoj Wrote: > -------------------------------------------------- > ----- > > Hello, > > about two weeks ago i wrote about the > > missing/nonfunctional sensors stuff on zyxel > > NSA320 (sudo sensors-detect finds no sensors). > > I did not understand all of pbg4's andby pbg4 - uBoot
Hi bodhi, just a quick test on a NSA320 box with custom zyxel uboot gave positive results, if I set power_resume = 0 i.e. no power resume and than the box is shutdown, upon coming up with the Power button afterwards kwboot results are: kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2014.07-tld-4.nsa320.mtd0.kwb -p Sending boot message. Please reboot the target...| Sending boot image...by pbg4 - uBoot
Hi bodhi, yes, the lm63 module does not need CONFIG_KIRKWOOD_THERMAL to work with lm-sensors, it is identified and connected over i2c, my email was meant primarily for owners of the NSA325, so they can test the internal thermal sensor of the 6282 soc, on the iConnect all information comes from the lm63 temp sensors and its module attached via i2c, at adress 0x4c, but if you compare iCby pbg4 - Debian
Hi bodhi, yes, exactly; and the internal temperature sensor than also has support from lm-sensors,.. in the links posted above someone also claimed that the internal thermal sensor of the 6282 soc is mentioned in the public part of the datasheet,.. best wishes pbg4by pbg4 - Debian
Hi, has anybody of the NSA325 owners here in this thread already used the kirkwood thermal monitor, which is part of newer kernels since this patch: http://www.spinics.net/lists/arm-kernel/msg211570.html Once enabled (CONFIG_KIRKWOOD_THERMAL), the inclusion of kirkwood-6282.dtsi in the nsa325 dts file automatically provides the following information to describe how the SoC temperature sby pbg4 - Debian