NSA310 non fdt kernel LED and FAN problem

This forum is for topics dealing with problems with software specifically in the ARMv5 repo.

NSA310 non fdt kernel LED and FAN problem

Postby marlemion » Sun Apr 17, 2016 2:13 pm

Hi,

I installed bodhis new uboot on my NSA310 and want to boot a non fdt (i.e. linux-kirkwood) kernel. This kernel appears to boot ok.

[ 0.000000] Machine: Zyxel NSA-310

Network device comes up as enp0s1, however, I get the following error:

[ 38.332861] libphy: PHY orion-mdio-mii:00 not found
[ 38.350324] rtc-pcf8563 0-0051: chip found, driver version 0.4.4
[ 38.362901] rtc-pcf8563 0-0051: pcf8563_write_block_data: err=-6 addr=0e, data=03
[ 38.370441] rtc-pcf8563 0-0051: pcf8563_probe: write error
[ 38.432843] rtc-pcf8563: probe of 0-0051 failed with error -5
[ 38.446735] r8169 0000:00:01.0 enp0s1: renamed from eth0

I usually resemble the original zyxel software behavior of the leds by giving them the right values (echo them in on boot). This works fine, altough there is a crash for the first time I write a number to those leds:

[ 61.529944] ------------[ cut here ]------------
[ 61.534612] WARNING: CPU: 0 PID: 307 at drivers/gpio/gpiolib.c:85 gpio_to_desc+0xdc/0x118()
[ 61.618562] invalid GPIO -813686336
[ 61.622075] Modules linked in: reiserfs mv_cesa rtc_pcf8563 ip_tables x_tables ipv6
[ 61.646066] CPU: 0 PID: 307 Comm: echo Not tainted 4.4.7-1-ARCH #1
[ 61.685320] Hardware name: Zyxel NSA-310
[ 61.689436] [<c00104cc>] (unwind_backtrace) from [<c000d9f0>] (show_stack+0x10/0x14)
[ 61.731981] [<c000d9f0>] (show_stack) from [<c0020654>] (warn_slowpath_common+0x80/0xb8)
[ 61.757424] [<c0020654>] (warn_slowpath_common) from [<c00206bc>] (warn_slowpath_fmt+0x30/0x40)
[ 61.779918] [<c00206bc>] (warn_slowpath_fmt) from [<c03b5e2c>] (gpio_to_desc+0xdc/0x118)
[ 61.797561] [<c03b5e2c>] (gpio_to_desc) from [<c001c274>] (nsa310_gpio_blink_set+0x44/0x5c)
[ 61.814497] [<c001c274>] (nsa310_gpio_blink_set) from [<c052a1cc>] (gpio_led_set+0x48/0x70)
[ 61.835348] [<c052a1cc>] (gpio_led_set) from [<c05295c0>] (brightness_store+0x58/0x88)
[ 61.844070] r8169 0000:00:01.0 enp0s1: link up
[ 61.867962] [<c05295c0>] (brightness_store) from [<c019e668>] (kernfs_fop_write+0xb8/0x1ac)
[ 61.885892] [<c019e668>] (kernfs_fop_write) from [<c01291f8>] (vfs_write+0x90/0x1a4)
[ 61.893737] [<c01291f8>] (vfs_write) from [<c0129b24>] (SyS_write+0x44/0xa4)
[ 61.920863] [<c0129b24>] (SyS_write) from [<c000a420>] (ret_fast_syscall+0x0/0x38)
[ 61.951849] ---[ end trace f0c6015c4192ca61 ]---

Finally, the fan does not work. The fdt kernel allowed me beforehand to control the pwm via:

/sys/devices/platform/ocp\@f1000000/f1011000.i2c/i2c-0/0-002e/hwmon/hwmon0/

However, that is gone. There is no adt7475 module present in the kernel package. lm85 does not work. It seems to me that there is a problem with the right device tree stuff. In fact, there is nothing called *pwm* in /sys.

Any idea?
marlemion
 
Posts: 11
Joined: Fri Apr 17, 2015 12:10 pm

Return to ARMv5

Who is online

Users browsing this forum: No registered users and 5 guests