• Content Count

  • Joined

  • Last visited

About matteobp

  • Rank
    Advanced Member

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1446 profile views
  1. 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.
  2. 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 enabling CONFIG_USB_HIDDEV was enough
  3. 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
  4. I tried this image, and it works. [ 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 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,
  5. 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 ... :-(
  6. 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
  7. Same problem with latest Armbian Stretch. In both case I used Desktop version.
  8. 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 [Americ
  9. Yesterday I downloaded the latest "Debian desktop" image (it should be 5.42) linked here 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.
  10. 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
  11. No one can help me? Why does the armbian image work for some people and doesn't work for other people like me? Thanks.
  12. 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.
  13. 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
  14. 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.
  15. Ok, perfect. I'll try and let you know. Thanks very much Matteo