Active threads

Showing topics posted in for the last 365 days.

This stream auto-updates     

  1. Past hour
  2. Hi, i really tried to get SPI as spidev to work on my RockPI 4A (Rev. 1.4), using armbianEnv.txt and DT overlays however nothing works as it seems it is just ignored. So does anybody have an idea of how to get SPI working in spidev mode? Because I have board which I want to connect via SPI.
  3. Today
  4. Regarding exotic Bananapi M4 projects. Orangepi gets state subsidies but they only have to use soc from China. Only allwiner and rockchip come into play. Bananpi finances Foxconn. They got the condition to use soc Mediatek or Realtek because it is from Taiwan and not from China. Politics came into play here. Bananapi incurs large losses on its products. Bananapi M4 sold only 60 pieces on aliexpress. W2 is supposed to be a NAS server and has no PCI-e support. Utility sell without drivers. Complete flap. In addition, they incurred the costs of designing the bananapi F2 and S64 and did not put them on sale. Bananapi will be funded until Foxconn cancels them because of the costs involved, with no sales success. And the famous Cubietech basically went bankrupt.
  5. pkfox

    M4 V2

    But I use this cable/adapter on all my other M4 boards without any problems @115200
  6. There are changes dated few days ago. Your problems started then?
  7. Ok, here my result from weekend for those who are interested: armbianio needs patch for Lamobo(armbianio.patch): ------------------------------------------ ...armbianio.patch diff --git a/armbianio.c b/armbianio.c +static int iLamobor1Pins[] = {-1,-1,-1,53,-1,52,-1,259,224,-1, + 225,275,226,274,-1,273,244,-1,245,268, + -1,269,272,267,266,-1 + ,270}; ... ------------------------------------------ Sending 433-Mhz-codes now also work with WiringBPi on kernel >=4... with WiringPi it does not work. Only thing I do still not unterstand is why on PI19(275) worked with 17 on 3.4.x But, now my gpio's work like it should, if I change addresses like in io-3.x-vs-4-x.png
  8. Hi, I have Rock64 with fresh armbian installed: Debian GNU/Linux 10 (buster) 4.4.192-rockchip64 It was installed 2 days ago , first thing I did was "apt-get update" and then "upgrade" which upgraded 3 packages at most. Now whenever I try to run apt-get update I get error with post install : ~# apt-get update Hit:1 buster/updates InRelease Hit:3 buster InRelease Hit:2 buster InRelease Hit:4 buster-updates InRelease Hit:5 buster-backports InRelease Traceback (most recent call last): File "/usr/lib/cnf-update-db", line 26, in <module> col.create(db) File "/usr/share/command-not-found/CommandNotFound/db/", line 94, in create self._fill_commands(con) File "/usr/share/command-not-found/CommandNotFound/db/", line 132, in _fill_commands self._parse_single_contents_file(con, f, fp.stdout) File "/usr/share/command-not-found/CommandNotFound/db/", line 228, in _parse_single_contents_file l = l.decode("utf-8") UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 72: invalid continuation byte Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/lib/command-not-found/ -a -e /usr/lib/cnf-update-db; then /usr/lib/cnf-update-db > /dev/null; fi' E: Sub-process returned an error code Searching in google did not yeld too much results and I'm not linux expert to know what might be culprit Any help would be awesome Best Regards
  9. NanoPi M4 uses 2 lanes out of 4. Don't know about Neo4 but this is how driver configures ov4689 on M4. Some say it's because of dual camera support. Neo4 has only 1 CSI so it may use 4 lanes. But if you want one driver for all 3 NanoPi boards you have to use 2 lanes. I'm currently trying to get 60 FPS over 2 lanes on 4.4 kernel. May be I will help you with mainline driver later.
  10. Change /boot/armbienEnv.txt to have both "verbosity=7" and "console=serial", you will get more details ...
  11. So much thanks, I will try this. I see the last step, thas it mean after a kernel update I need to issue this again?
  12. Special Armbian build script engine know-how is not needed for this challenge. Relevant code location was already added in my previous post. The rest - solving the actual problem - has to be done manual first, then a patch (all four of them to solve for other kernels too) has to be modified. When your modified patch is adjusting post install scripts properly, you submit changes to the code. Take your time. If I put this task on my 2do list it will surely take months - a year - never. I rather help you to solve it even this represent more work.
  13. This is correct way but it can fail in case of: - hardware defects (bad SD card, failed powering = very common) - broken packages This you need to ask Docker specialists, but I don't think you need to do anything ... Docker engine upgrade could be broken, who know? Not an Armbian issue.
  14. thanks guys, i appreciate it
  15. Hi, I'm using the minimal Armbian Debian-based image as a starting point to install my favorite desktop environment KDE and related software. I've got everything set up so that I got it working partially. I remember trying the Armbian desktop (Ubuntu flavor) but it did not have it set up out of the box IIRC (I could be wrong). I took a look at how the hardkernel guys set up their official Ubuntu image for Odroid XU4 and used that as a guide to set it up on my minimal Armbian. So here's what I've done and what I've learned I need to do according to the official image: 1. apt install mali-t62x-x11-driver xserver-xorg-video-armsoc-sun4i 2. copied xorg.conf from official Hardkernel image to /etc/X11 and removed Armbian xorg configuration file from the /etc/X11/xorg.conf.d/ directory 3. chmod 0755 /usr/lib/arm-linux-gnueabihf/ Now I installed my desktop environment (kde-full) and other misc software. Here's there most interesting bit. If I now run es2_info (from the mesa-utils-extra package) I get the following: ERROR: The DDK is not compatible with any of the Mali GPUs on the system. The DDK was built for 0x620 r0p1 status range [0..15], but none of the GPUs matched: Error: eglInitialize() failed but now if do chmod 666 /dev/mali0 and run es2_info | grep -i renderer I get: GL_RENDERER: Mali-T628 So in other words the previous error message is complete bogus and has led me astray for quite a while. It's simply a permission issue that it detects as compatibility error... which doesn't make much sense to me but whatever it works now. There is however an issue with Qt if the permissions of /dev/mali0 is set to anything permissive like 666. Any KDE program I run after setting those permissions get the following error and a crash (example with running konsole): Unable to find an X11 visual which matches EGL config 9 KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = konsole path = /usr/bin pid = 2506 KCrash: Arguments: /usr/bin/konsole KCrash: Attempting to start /usr/lib/arm-linux-gnueabihf/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Stopped konsole Note that other OpenGL ES programs work without issues (es2gears, glmark2-es2), and this seems to be an issue with Qt specifically and not anything driver related. I did some digging and found these old Hardkernel threads discussing the issue: The TL;DR of those threads is: Hardkernel patches Qt (specifically libqt5gui5) to make it detect ARM as a vendor. These are my findings and conclusions. Maybe I am completely wrong and someone may have got it working a different way which does not cause this issue with Qt? I'm just wondering why these fixes aren't in upstream Qt or Armbian because it would seem like a common issue to me. Here is some system info:
  16. Indeed. Swap and ZRam didn't work at all since a pretty messed kernel config. I had went into it when it was new. You might recognize some things echo '9999' > /sys/module/lowmemorykiller/parameters/adj echo '1' > /sys/module/lowmemorykiller/parameters/minfree This was the fix then to make it work. Was because of remainders of android, I checked the kernel and there's still a lot that doesn't belong there. @Brad was the man who found the fix then. I do have it working well on Bionic.
  17. Still waiting for a MAC/Vagrant user that would write what shell be done and send a pull request to the documentation.
  18. If you need s922, it is better to take Ugoos AM6. To date, this is the best option in terms of cost / result ratio.
  19. should be excellent considering kernel 5.4 will be stable by then, will stay tuned chaps. thanks for your efforts!
  20. Yesterday
  21. Spoke too soon. Was having issue with static MAC because I had assigned static DHCP mapping in my firewall. Removed the mapping from the firewall and armbian has no trouble keeping the same mac and ip.
  22. Yes, there is, and you can find the instructions in this same forum: You can skip the Emby part, if you don't want it. As a matter of fact, I now recommend the recent FOSS project Jellyfin over Emby (I myself made the contribution to Jellyfin that enabled XU4/HC1 hardware encoding, so I can confirm it works).
  23. ..okay-maybe not the ideal way, but I had no android for the box for me worked pretty well booting the armbian from card with pressed recovery button and just re-copying the system to emmc via armbian-config again..also 19 alpha Libreelec builds boot/work again as expected, but neither coreelec nor official built images boot, like it should be.. Just installed Armbian_5.99_Aml-g12_Ubuntu_bionic_dev_5.4.0-rc6_desktop_20191010.img.xz (is the timestamp 1010 correct or should it be 1110?!). No issues so far on my x96 mini p281 s905w 2/16 test box.
  24. Thanks! I'll look into it. ­čÖé
  25. Armbian_5.99_Aml-g12_Ubuntu_bionic_next_5.4.0-rc6-next-20191108_desktop meson-gxm-q200.dtb on T95Z Plus (s912) -> no sound
  26. Maybe a stupid comment and i have the OnePlus with H6 without USB3 ports. But it looks like after i install lshw also lsusb -v gives a lote more information. Maybe it could help in troubleshooting? And if it didn┬┤t help sorry for my interrupt.
  27. Hello everyone, I want to do something simple with my OrangePi One Plus. That is to connect a bluetooth speaker and play wireless from the Pi with a CSR8510 A10 USB dongel. The dongel works and i can pair with every device. Even with my JBL Go 2 bluetooth speaker: hj@PLUS-OrangePiOne:~ $ sudo bluetoothctl [NEW] Controller YY:YY:YY:YY PLUS-OrangePiOne [default] Agent registered [bluetooth]# power on Changing power on succeeded [bluetooth]# scan on Discovery started [CHG] Controller YY:YY:YY:YY Discovering: yes [NEW] Device XX:XX:XX:XX JBL GO 2 [bluetooth]# scan off Discovery stopped [CHG] Controller YY:YY:YY:YY Discovering: no [CHG] Device XX:XX:XX:XX TxPower is nil [CHG] Device XX:XX:XX:XX RSSI is nil [bluetooth]# trust XX:XX:XX:XX [CHG] Device XX:XX:XX:XX Trusted: yes Changing XX:XX:XX:XX trust succeeded [bluetooth]# pair XX:XX:XX:XX Attempting to pair with XX:XX:XX:XX [CHG] Device XX:XX:XX:XX Connected: yes [CHG] Device XX:XX:XX:XX UUIDs: 00001108-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110b-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110c-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000110e-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX UUIDs: 0000111e-0000-1000-8000-00805f9b34fb [CHG] Device XX:XX:XX:XX ServicesResolved: yes [CHG] Device XX:XX:XX:XX Paired: yes Pairing successful [CHG] Device XX:XX:XX:XX ServicesResolved: no [CHG] Device XX:XX:XX:XX Connected: no [bluetooth]# connect XX:XX:XX:XX Attempting to connect to XX:XX:XX:XX Failed to connect: org.bluez.Error.Failed But, as you can see above, i can┬┤t connect to the JBL Go2. If i open the bluetooth service i read: hj@PLUS-OrangePiOne:~ $ sudo service bluetooth status * bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Sun 2019-11-10 14:53:35 CET; 1h 9min ago Docs: man:bluetoothd(8) Main PID: 732 (bluetoothd) Status: "Running" Tasks: 1 (limit: 1021) CGroup: /system.slice/bluetooth.service `-732 /usr/lib/bluetooth/bluetoothd Nov 10 15:42:13 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:20 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:36 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:44 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:43:53 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:03 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:09 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:11 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:44:18 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Nov 10 15:59:28 PLUS-OrangePiOne bluetoothd[732]: a2dp-sink profile connect failed for XX:XX:XX:XX Protocol not available Off course did i look on Google and i read something with pulseaudio but that should be installed also the ┬┤pulse-module-bluetooth┬┤ module. i have no idea to fix this. Btw: connecting to non-audio bluetooth devices works. Connecting to the JBL Go2 from Armbian-config does also not work... Does someone of you a sugestion to make a2dp working?
  1. Load more activity