The_Loko

Members
  • Content Count

    13
  • Joined

  • Last visited

About The_Loko

  • Rank
    Member

Recent Profile Visitors

332 profile views
  1. Without the exact error it's impossible to help.
  2. I'm interested in the current Bluetooth status. I read that it's not working yet. What needs to be done? I only know that it uses the Ampak AP6256 and it's connected over UART, so it should work with hciattach.
  3. The_Loko

    The_Loko

  4. You need to use -lpthread instead of -llibpthread.
  5. The HC-05 module works over serial, I just hook it up to the serial header
  6. The default sound output is hdmi, you need to change it on /etc/asound.conf. This is the default file: pcm.!default { type hw card 1 } ctl.!default { type hw card 1 } You need to change the card number to 0 on both lines, if it is not 0 you can check the card number with cat /proc/asound/cards
  7. I had this working some time ago, but I don't know why it doens't work anymore, maybe it is a bug on newer Armbian versions.
  8. What's the difference between installing this and libgl1-mesa-dri package? I installed the latter as I needed OpenGL for some applications like the OpenCV camera viewer and it seems to work fine.
  9. Green led has now "heartbeat" trigger enabled by default, it blinks like the "heart" of the CPU, on higher loads it blinks slightly faster than on lower ones.
  10. Te asc file is a PGP signature used to verify the image authenticity, you don't need to use it for anything else.
  11. Anyone using any of those cheap bluetooth dongles? I have been trying to get it working but when connecting it freezes the OPi PC (the heartbeat led stops blinkng). The dongle is fine as it works on other Linux and Windows computers. This is the lsusb output: Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 003: ID 14b2:3c22 Ralink Technology, Corp. Conceptronic C54RU v3 802.11bg Wireless Adapter [Ralink RT2571W] Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub It seems that no matter what usb port I use it's detected as usb 1.1 device, so maybe this is why it fails? As it freezes the board there is not any relevant log saved.: 694, stack limit = 0xee1c42f8) Today after pairing a device, I received the "sunxi oops" attached as output on bluetoothctl, it didn't froze the board as the led was still blinking but it was unresponsive and lost the network connection. Any idea what's producing this? I think it could be the btusb driver because on 3.4 kernel it had some CSR dongles blacklisted. sunxioops.txt
  12. I have never used Windows to write images, so I can't help with Rufus. The prebuilt image available to OPI is legacy because it uses the legacy kernel (3.4.X from linux-sunxi project) instead of the vanilla kernel. Anyway it uses Debian Jessie like vanilla release. It will work fine for your purposes.
  13. You need to write the Armbian raw files to SD. If using Linux you can use the dd command, on Windows you can use Rufus as explained here The debian and every image from OPi forums can be used with the same tools, but I won't use it as they are not mantained anymore and they are full of bugs (overheating, wrong voltages and such)
  14. I had the same problem with a Class 10 SD, it worked fine untill powered off and it won't boot again. I tried some other cards (Crappy chinese Class 4 and Samsung Class 10) and both work fine, so it seems that the OPI is very fussy with the SD cards, it doesn't seem to matter the class or quality