megi

Members
  • Content Count

    31
  • Joined

  • Last visited

2 Followers

About megi

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. USB3 is fine. I run Intel SSD over JMS578 USB-SATA bridge, and don't have any stability issues. But I don't power the SSD from the USB, because that turned out not to be very reliable. Intel SSD probably has spiky load requirements, or something. OTOH, Opi 3 doesn't have any current protection on the USB bus (there's direct connection from DCIN to USB Vbus), so if the drive load is not very spiky, it should work fine just with USB power. You should not need any special cooling. I just have a common undervolted 12cm fan next to the board, and I can't make it throttle even at 1.8GHz. Instead of throwing away CPU frequency, you may just disable a core or two, and you'll get sustained full singlecore performance without any cooling. It depends on your use case.
  2. I don't see them in armbian. Anyway, I only have Opi 3 working, and lite2 may have a different bluetooth chip.
  3. Also without kernel's H6 RTC patches, you'll not make this work, because BT will not have clock enabled.
  4. hciattach is not necessary, the kernel does that automatically if configured like this: https://megous.com/git/linux/commit/?h=opi3-5.2&id=0c27ac4b4586bc2c0dded85b5bf82f78531d01c3 Sorry, I don't have guide to make BT work, because there's shouldn't be much to configure. All you need is a kernel with the support and then you just need to configure BT address (btmgmt public-addr) for your device. Kernel part is something armbian should figure out.
  5. This already works with 5.1 if armbian is still using my kernel patches. All that's needed is putting firmware in /lib/firmware.
  6. Bluetooth is supported in my kernel. All you need is have firmware in /lib/firmware and then run: btmgmt public-addr 00:03:19:9e:8b:00 or some other address. After boot. How to get FW is described here: https://megous.com/git/linux/commit/?h=opi3-5.2&id=9c296799c4d3dd90986833cfded392098c1979bd (On orange pi 3 that is)
  7. Don't worry, these are just early driver probe failures, that succeed later on as they are retried.
  8. @martinayotte Pine64 has bus-width set to 4 in 5.1-rc#. There are no boards that don't set it mainline: You can check with: grep -L bus-width `grep -Rl '&mmc0'`
  9. Everything necessary is built in. It's just a dd for u-boot and cp for kernel and dtb, and that's it. You don't even need /lib/firmware or /lib/modules.
  10. Configuring a reset line to the phy may also help, if it is connected to some GPIO on the SoC.
  11. If rtl ephy is powered by two power supplies, they need to be enabled at the same time, otherwise it will fail (maybe not always, but it may). I've seen DTS files flying around that have this wrong and insert power up delays in wrong places. I only work on Orange Pi 3 though, so I have no concrete input on what other baords do.
  12. You need to use the same config I use. I don't use defconfig, so maybe your kernel is missing something. My config can be found in those pre-built packages, I linked above.
  13. My HDMI looks like this: cat /sys/class/drm/card0-HDMI-A-1/modes 1920x1080 1920x1080 1920x1080 1920x1080i 1920x1080i 1920x1080 1920x1080i 1680x1050 1280x1024 1280x1024 1440x900 1280x960 1152x864 1280x720 1280x720 1280x720 1280x720 1280x720 1440x576 1440x576 1024x768 1024x768 1024x768 1440x480 1440x480 1440x480 1440x480 832x624 800x600 800x600 800x600 800x600 720x576 720x576 720x576 720x480 720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480 640x480 640x480 720x400 Perhaps some problem with your board/monitor?
  14. No meaningful difference. I also have pre-built kernel/u-boot with all the firmwares included here: https://xff.cz/kernels
  15. @martinayotte I only work on Opi3 support on opi3-5.1 branch. So all the most recent changes are there. For my u-boot I only work on v2019.04-rc*.