matteobp

After several unsuccessful attempts, I decided to use the kernel configuration file of the "Ubuntu MATE 18.04 LTS" as it is, without any change, because in that distribution apcupsd works and the node /dev/usb/hiddev0 exists. Regretfully, it doesn't work on Armbian So my conclusion is that the problem is not just about the kernel, but there must be something else, and I have no idea what it might be. So I had to change and move on to the "Ubuntu Minimal 18.04 LTS" with XFCE Desktop Environment, and it works. https://wiki.odroid.com/odroid-xu4/os_images/linux/ubuntu_4.14/20180531

I have a similar problem with apcupsd on a Odroid XU4 board, see this topic CONFIG_USB_HIDDEV was disabled on the kernel configuration file, while CONFIG_HIDRAW is already enabled. I build the kernel with CONFIG_USB_HIDDEV enabled, but it is still not working. Any ideas? Thanks in advance. P.S. In this case https://forum.odroid.com/viewtopic.php?f=93&t=28978 enabling CONFIG_USB_HIDDEV was enough https://github.com/hardkernel/linux/commit/be592282a08a2493692448e365e46b52ac715b3f

Sure, I won't miss it. The problem is that enabling option CONFIG_USB_HIDDEV is not enough, something is still missing. I wanted to create a specific post in a general section because maybe someone else knows how to do it, but no problem. I'll try to compare the configuration kernel file of the other Ubuntu distribution, which I think is more similar to the Odroid XU4 Armbian configuration file than the Rock64 configuration file. Thanks

I tried this image, and it works. https://forum.odroid.com/viewtopic.php?f=95&t=30888 [ 7.201747] usb 3-1.2.2: Product: Smart-UPS 750 FW:651.13.I USB FW:7.3 [ 7.321793] hid-generic 0003:051D:0002.0004: hiddev97,hidraw3: USB HID v1.10 Device [American Power Conversion Smart-UPS 750 FW:651.13.I USB FW:7.3] on usb-xhci-hcd.3.auto-1.2.2/input0 All posts I found about hiddev feature are based on old kernel, and refers to CONFIG_USB_DEVICEFS that is deprecated. Can I add a new post under Development section about enabling hiddev node in the kernel, or would it be considered a duplicate post? Thanks.

Yes, it works. So I can use the kernel configuration of the Rock64 board, I think this one linux-rockchip-next.config But it not simple, too many differences ... :-(

Can you help me? How can I do it? On the Rock64 I have the ayufan Stretch image 0.6.44, kernel 4.4.132. I have to search in that kernel configuration. And I can try the Rock64 Armbian image to check if apcuspd works with it. Thanks

Same problem with latest Armbian Stretch. In both case I used Desktop version.

Hi. I have a Odroid XU4 with Ubuntu Bionic latest release (5.60), powered with this UPS: APC SmartUPS 750 VA. Apcupsd doesn't work. The problem seems related to the missing /dev/usb/hiddev0. After searching on Google, I found that apcupsd requires this feature enabled in the kernel. CONFIG_USB_HIDDEV=Y I build my own kernel enabling it, but no change. Here the output of the command # dmesg | grep Smart [ 4.125553] usb 1-1.2: Product: Smart-UPS 750 FW:651.13.I USB FW:7.3 [ 4.205622] hid-generic 0003:051D:0002.0001: hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 750 FW:651 On the Rock64 board it works without problem. Here the output of the command # dmesg | grep Smart [ 2.175796] usb 3-1: Product: Smart-UPS 750 FW:651.13.I USB FW:7.3 [ 3.719981] hid-generic 0003:051D:0002.0001: hiddev0,hidraw0: USB HID v1.10 Device [American Power Conversion Smart-UPS 750 FW:651.13.I USB FW:7.3] on usb-ff5d0000.usb-1/input0 As you can see, on the Rock64 board there is hiddev0 hid-generic 0003:051D:0002.0001: hiddev0,hidraw0 and /dev/usb/hiddev0 exists. In the Odroid forum, I found only this post about CONFIG_USB_HIDDEV https://forum.odroid.com/viewtopic.php?f=93&t=28978 Thanks in advance.

Yesterday I downloaded the latest "Debian desktop" image (it should be 5.42) linked here https://www.armbian.com/rock64/ but I'm still having the error reported below. I have never been able to run a version of Armbian on my Rock 64 (1GB version) . I'm currently using Armbian (Debian) on an Orange Pi+ without any problem. What's the problem? Can someone help me please? Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on Aug 13 2017, 15:25:34. Port /dev/ttyUSB0, 20:57:55 Press CTRL-A Z for help on special keys DDR version 1.06 20170424 In LPDDR3 786MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB ddrconfig:1 OUT U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01) setup_ddr_param 1 booted from SPI flash Trying to boot from SPI NOTICE: BL31: v1.3(release):f947c7e NOTICE: BL31: Built : 11:06:00, Jan 12 2018 NOTICE: BL31:Rockchip release version: v1.3 U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177 Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303038000000000d2b11 serial=ea6ec868699cad5 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2960 bytes read in 27 ms (106.4 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 112 bytes read in 21 ms (4.9 KiB/s) "Synchronous Abort" handler, esr 0x96000210 ELR: 3ff77944 LR: 3ff75eb0 x0 : 000000003df2e9b0 x1 : 0000000044000000 x2 : 0000000000000070 x3 : 0000000000000000 x4 : 0000000000000070 x5 : 000000000000000e x6 : 0000000000000000 x7 : 0000000000000000 x8 : 0000000000000000 x9 : 0000000000000008 x10: 000000003df2e9c0 x11: 000000003df13b70 x12: 0000000000000000 x13: 0000000000000200 x14: 000000003df04bfc x15: 00000000ffffffff x16: 0000000060df18a6 x17: 0000000070a12210 x18: 000000003df0ce08 x19: 0000000000000000 x20: 0000000000000070 x21: 0000000044000000 x22: 000000003df2e9b0 x23: 000000003ffa0118 x24: 0000000000000000 x25: 0000000000000000 x26: 000000000000000a x27: 0000000000000001 x28: 0000000000000000 x29: 000000003df02b10 Resetting CPU ... DDR version 1.06 20170424 In SRX LPDDR3 786MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=1 Die Bus-Width=32 Size=1024MB ddrconfig:1 OUT U-Boot SPL 2017.09-g5a90a9a (Jan 12 2018 - 11:06:01) setup_ddr_param 1 booted from SPI flash Trying to boot from SPI NOTICE: BL31: v1.3(release):f947c7e NOTICE: BL31: Built : 11:06:00, Jan 12 2018 NOTICE: BL31:Rockchip release version: v1.3 U-Boot 2017.09-g5a90a9a (Jan 12 2018 - 11:06:15 +0000), Build: jenkins-linux-build-rock-64-177 Model: Pine64 Rock64 DRAM: 1022 MiB MMC: rksdmmc@ff520000: 0, rksdmmc@ff500000: 1 *** Warning - bad CRC, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 misc_init_r cpuid=55524b503039303038000000000d2b11 serial=ea6ec868699cad5 normal boot Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! mmc_init: -95, time 9 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2960 bytes read in 28 ms (102.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 112 bytes read in 22 ms (4.9 KiB/s) "Synchronous Abort" handler, esr 0x96000210 ELR: 3ff77944 LR: 3ff75eb0 x0 : 000000003df2e9d0 x1 : 0000000044000000 x2 : 0000000000000070 x3 : 0000000000000000 x4 : 0000000000000070 x5 : 000000000000000e x6 : 0000000000000000 x7 : 0000000000000000 x8 : 0000000000000000 x9 : 0000000000000008 x10: 000000003df2e9e0 x11: 000000003df13b70 x12: 0000000000000000 x13: 0000000000000200 x14: 000000003df04bfc x15: 00000000ffffffff x16: 0000000060df18a6 x17: 0000000070a12210 x18: 000000003df0ce08 x19: 0000000000000000 x20: 0000000000000070 x21: 0000000044000000 x22: 000000003df2e9d0 x23: 000000003ffa0118 x24: 0000000000000000 x25: 0000000000000000 x26: 000000000000000a x27: 0000000000000001 x28: 0000000000000000 x29: 000000003df02b10 Resetting CPU ...

No. With the latest version of 0.6.x (I tried with 0.6.13) it works. So both ayufan 0.5.15 e 0.6.1x works, at least the debian jessie and debian stretch images. But I was never able to boot the armbian. Here you can find the output log taken via console. Thanks

No one can help me? Why does the armbian image work for some people and doesn't work for other people like me? Thanks.

Hi. The "usb to serial ttl bridge adapter" arrived yesterday, and I tried the 20/11/2017 armbian Rock64 image. This is the output of the console and it loops on " x0 : ... x2 : ... ... x28: ... Resetting CPU ... " I hope that this can help. Thanks.

I think in my case the problem is not the writing: 2 writes with Etcher on Linux and 2 writes with Etcher on Windows with verification on. Moreover, when I write the ayufan image v. 0.5.15 the board works, while I have the same problem with 0.6.x . I think there is something missing/wrong with my board. Is there something like "a firmware" to be updated? AFAIK, the image contains everything I need. Thanks

No change. I used Etcher on Windows to write the SD card: it doesn't start; all leds on, no hdmi output. I think I have to wait for the "usb to serial ttl bridge adapter" (already ordered) and check via serial console what is happening.

Ok, perfect. I'll try and let you know. Thanks very much Matteo