Jump to content

mikegleasonjr

Members
  • Posts

    5
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I would like to know that as well.. and bluetooth!
  2. @datajerk @dragonlost Good news. I wrote previously that I had problems with USB drives connected. The issues seems to have been resolved. I just installed a fresh install of Armbian 5.75 (4.4.174). No matter how much I rebooted and worked with the unit, the usb hard drive always was present. OTOH it seems the bluetooth service can't start. I don't mind since I am not using it, but here an armbianmonitor -u output: http://ix.io/1BA5 Here's the systemctl status nanopi-bluetooth.service output: ● nanopi-bluetooth.service - Bluetooth nanopi Loaded: loaded (/lib/systemd/system/nanopi-bluetooth.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2019-02-20 16:24:13 +01; 4min 36s ago Process: 812 ExecStart=/usr/bin/hciattach /dev/ttyS0 bcm43xx 115200 > /dev/null (code=exited, status=203/EXEC) Process: 800 ExecStartPre=/bin/echo 1 > /sys/class/rfkill/rfkill0/state (code=exited, status=0/SUCCESS) CPU: 10ms Feb 20 16:24:13 m4a systemd[1]: Starting Bluetooth nanopi... Feb 20 16:24:13 m4a echo[800]: 1 > /sys/class/rfkill/rfkill0/state Feb 20 16:24:13 m4a systemd[1]: nanopi-bluetooth.service: Control process exited, code=exited status=203 Feb 20 16:24:13 m4a systemd[1]: Failed to start Bluetooth nanopi. Feb 20 16:24:13 m4a systemd[1]: nanopi-bluetooth.service: Unit entered failed state. Feb 20 16:24:13 m4a systemd[1]: nanopi-bluetooth.service: Failed with result 'exit-code'. Let me know if you need anything else.
  3. The good news is the official FriendlyElec distro doesn't have this problem so it is not hardware related. The bad news (for me) is the FriendlyElec distro doesn't have the overlay module in the kernel so I have trouble setting up the latest Docker version. The kernel is also not great and I have problems with apt sometimes. I like Armbian but I bought the M4 for a NAS solution so it doesn't work
  4. Hi, I have issues with external hard drives. First and foremost, I have a proper power supply and a proper cable. In fact, tried several of them. I have a 3a and a 4.2a charger and really, really good cables. Now. 1 time out of 3 when I issue a reboot command the USB hard disk is not "seen" on reboot. The device /dev/sd* doesn't exist. Even if I unplug the drive and plug it back, nothing. I have to issue a poweroff command and unplug the power supply and plug it back for the hard drive to show up on reboot. I have 3 ext4 hard drives, all show the same behaviour. (the 3 are not plugged at the same time). So to repeat the bug: on reboot the hard disk is not seen by the os 1 out of 3 times. Unplugging and plugging it back doesn't help, I have to completely unplug the NanoPi and plug it back to see the HD again. Once in a while also during normal operations, the hard drive will vanish, much like described by @datajerk on nov 9. I have the same issue as him. He also tried multiple power sources and cables, even powering his board through headers and everyone here said it was a power issue. I don't think it is, you just have to reboot a couple of times to see that the drive will get lost. I didn't tried the FriendlyElec distro to see if it exibits the same behaviour. Pretty much happening on every version of Armbian I tried, even the latest kernel in nightly. Thanks for your help! (I have the 4GB board)
  5. Hey guys, just exploring the possibility of having kernel 4.20 at some point for the NanoPi m4. Since it has big/little improvements in it, it would be great for us! Thanks
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines