Jump to content

ArmBoy1988

Members
  • Posts

    44
  • Joined

  • Last visited

Everything posted by ArmBoy1988

  1. @OttawaHacker What specifically do you mean regarding "on/off" thing? Previously, I updated the Kodi config for for my CEC remote to manage how certain functions work with the remote in CEC. This was done through the menus in Kodi. If you can explain what you're trying to do, I'll try it on my setup. I usually leave the CEC setup so that the TV and other devices are not turned off or switched to/from when the events happen. If you go to Settings / System / Input / Peripherals and then select CEC Adapter, a list of items that can be modified is displayed. I don't know if all of them work or if it depends on your TV, other devices etc. Have a look. Let me know if you want me to post the list.
  2. Needed/wanted to add Bluetooth to my OPi5 and also needed WiFi at the same time. Did not want to use 2 USB ports so I tried the T2UB. Working well. Bluetooth appeared on my Armbian Ubuntu Jammy setup and I plugged in the dongle. It saw a few of my bluetooth devices. Reason I wanted bluetooth is to use a controller for some games/emulators. I'll make another post for that. My PS4 Dualshock controller is not showing up in the list of devices. My version is an older version, Armbian 23.06.420 Jammy with Linux 5.10.160-rk35xx No end-user support: built from trunk Conclusion: TPLink T2UB should work properly on Armbian Ubuntu desktop.
  3. I had one OPi5 setup and working properly with one of my TVs. I was running Kodi and using the remote from my TV to control Kodi using HDMI-CEC. I went to setup a second one on another TV but this time the TV remote did not work properly. Through elimination I came to determine the HDMI cable was the issue. I ordered another HDMI cable that had the Ferrite at each side of the cable. Now it worked properly. Thought this might be useful for others. This is the cable I ordered: https://www.amazon.ca/dp/B003PDHJ6M Conclusion: In order to make HDMI-CEC work properly, make sure the HDMI cable is of sufficient quality. I think ones with the Ferrite may be best to remove any electrical interference.
  4. I don't think the OPi5 has onboard sata. I think there may be an overlay for sata, though. In any case, on my OPi5, I'm running off a 1TB NVME. I'm running with 8 external data drives off a USB 3 hub. I've set up OMV on Armbian Bullseye server version. Running fine. FYI, I don't believe there is an Armbian Bullseye version for the OPi5 Plus. Not sure if you can build that yourself, but you may have to. OMV 6, the current version, requires Debian Bullseye. There is a beta version of OMV7, that could work for you. Some OMV devs have indicated that OMV 7 is just as stable as OMV6. Check the openmediavault forums for details.
  5. There is/are threads/posts about Mesa Panfork either here or on the Collabora site or blog. I believe the last version where the acceleration worked was based on Ubuntu 22.04 LTS. I don't recall/know which Armbian version that mapped to. I also remember people started to see that the acceleration no longer worked.. In any case, that's all I can remember. I don't have any more info on it so I won't be posting anything else in this thread.
  6. I believe the mesa panfork drivers are only available on Jammy/amazingfated versions of Armbian. It actually says that in the line above the box with those lines you quoted. I don't know the details. Joshua-Riek is likely based on that as well. In the future they may/will likely be available more widely.
  7. I found this a while ago. I didn't try it as I'm not really up on Steam. Thought it might help: https://jamesachambers.com/installing-steam-on-the-orange-pi-5-with-armbian/
  8. I'm using a Logitech k400r, I think. It comes with its own usb dongle, is wireless and has a built-in trackpad. Works great. Not sure if it's still available or other Logitech keyboards work with it.
  9. If this u-boot doesn't work out, perhaps there is another option. When I was initially setting up my NVME, I was having an issue. In order to make it work, a small FAT boot partition was created and a 2nd partition for the root fs. I believe there was an early issue with ext4 partitions on the SPI. In any case, perhaps using this configuration, you can more easily modify the boot partition to do what you need it to do.
  10. If the NVME is not showing up, perhaps it's an issue with the NVME? Do they all use the same NVME? Does the issue happen with the same boards all the time? Mostly? Sounds like this is for a product you're going to be selling. Perhaps try a few of the OPi with different NVME and see if the issue happens on those as well. Could even be one or several OPi with issues? Keep good stats and then closely review them at regular intervals. Just throwing out ideas.
  11. I thought I had read that someone had the T2U working out of the box. Well, it's mostly there. When I tried it, didn't work. Got message in dmesg that firmware file not found. Did a Google search and found that it came down to the mediatek firmware files needing to be in the /lib/firmware/mediatek directory but they are currently in the /lib/firmware directory. FYI, the /lib/firmware/mediatek directory already existed and did not need to be created. Also in the current Jammy Gnome desktop Armbian, the file that was being loaded, mt7610e.bin, was not there and only the backup file, mt7610u.bin, was there in the /lib/firmware directory. What I did was download the mt7610e and mt7610u from: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek I placed them in the /lib/firmware/mediatek directory. This was before I saw that the /lib/firmware directory contained the mt7610u.bin file. Rebooted and then no errors in dmesg but correct loading and recognizing the T2U and my WiFi router/SSID. Don't know if there would be issues with other Mediatek dongles or if Armbian needs to be updated for this or it's an issue elsewhere. Just thought this would be useful for others trying to find a working dongle or trying to make their T2U/Mediatek based dongles work.
  12. OK. As I said, I didn't see anything wrong...that's because I don't know this in detail, or at all . Here's a pic of my OPi 5, not a 5b, for your comparison. Looks very different:
  13. I'm not sure I can see the issue you're pointing out. In your image, the part you have circled looks OK to me. Can you explain in more detail what I should be looking at, the error/issue or am I missing something?
  14. @Efe Çetin Out of curiosity and for completeness and people who may have similar issues and questions in the future, does the fix apply to other bluetooth adapters or just the AP6275P that this thread us about?
  15. @jv_5 There are a lot of power related messages in what you posted. Perhaps it's a power supply issue. What kind of power supply are you using? I'm using a 5V4A dumb power supply. I've read about issues using smart/PD type of power supplies with the OPi5. Can't remember the details. Also, I believe the 4A is crucial, especially as you add/use more features, such as a NVME drive that wasn't there before. This is the one I purchased: https://www.amazon.ca/GeeekPi-Supply-Raspberry-Orange-Adapter/dp/B0BMGJNSVS
  16. I've seen cases where some ssd just don't work or aren't recognized. With my nanopc-t4, there was a thread just to identify which worked and which didn't. I'm not sure why some work and some don't. FYI, I have a Samsung 980 1 tb and it's working fine on my opi5. Just thought I'd put it out there. If anyone else had the same ssd as you and it worked, that would give some more info. If you can try another ssd from a different manufacturer that could provide more info. Even if it's smaller, just to see if others will work with your board. Also, do any messages for the ssd show up in dmesg? Maybe boot from an SD card with the ssd plugged in. See if it shows up or there are any messages in dmesg related to it.
  17. It looks like that one uses an FTDI FT232RL chip. I think that one is faster than the pl2303 chips. Perhaps the driver for the ft232 is better or more recent than that for the pl2303 chips or they are knockoff chips that don't work properly. Thanks for letting us know. I'll have to pick one of those up too.
  18. Not sure. Maybe try other software. In that link I posted it shows how to use mincom or minicom. I'll be doing this some time in the near future so I hope you figure it out 😀 When I try it I'll be able to provide my experiences.
  19. I think the TX of the cable needs to plug into the RX on the board and then the RX on the cable plugs into the TX on the board. PS: the listing for the cable you purchased shows it supports up to 3M baud rate so it should handle 1500000.
  20. Confirmed on the OrangePi site that the TTL is 3.3v here: http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/service-and-support/Orange-pi-5.html in the User Manual, v1.5 for the Orange Pi 5.
  21. That means the chip supports those voltages. However, you have to set what voltage to use. Many of these cables are set for just one of the voltages. There are modules that allow you to set the voltage using jumpers. The cable I had purchased only said 5V. The module that royk linked to had the jumpers so the voltage is selectable. I did read that if you had a 3.3v cable, it would likely work on a 5v system but I don't think it works the other way around as the 5v would exceed what the 3.3v can handle.
  22. This one has some good info too: https://wiki.radxa.com/Rockpi4/dev/serial-console Has info for connecting using Linux, Windows and MacOS.
  23. It looks like I purchased the wrong one. I was unaware that it had to be a 3.3v one. Haven't tried this out yet as there was no need to. I had purchased it to try to figure out an issue I was having booting up the OPi5 but I got it booting before trying this. Reading the listing for the one I purchased it says under the wire definitions "red +5v". I'll purchase another one, probably the one you pointed out, that you can set at 3.3v. Thanks.
  24. @royk Thanks. I hadn't considered a type like that one. I picked up this: https://www.amazon.ca/dp/B0BX232GYG I'm hoping it should work. Haven't tried yet. Only thing that I'm not sure about is the baud rate and the voltage. Most of these types of items on Amazon don't list the maximum speed so I'm not sure it can handle a 1500000 baud rate. They also don't mention if one of its presets has that baud rate either. Same goes with the voltage. Most of these don't specify voltage. Some specify 3.3v and 5v others say one or the other. I see the one you identified supports both and can switch with a jumper. Don't know which voltage is needed or if it matters. The three pins on the OPi5 are ground, TX and RX where the voltage wire is not used. So, voltage is taken from the device being connected to? It's used to power the chip the converter cable/chip being used? If that's the case, that means you can't harm the OPi5, hopefully. Right? The one I purchased uses the Pl2303Hx. I figured the cable I purchased is like all/most of the other cables you see and that they are mostly knock-offs. Any way, I'll be trying it at some point in the near future. Thanks again.
  25. At the beginning of the thread that bables150 pointed out: The url for one of his Yandex repositories is https://disk.yandex.ru/d/Xt36QdVcxRdEDA. There's a folder structure. I then went to ArmbianTV / 20230331-legacy and there you'll find the file. I picked that one because it was legacy and I thought it was Debian Bullseye. Any of the images will probably work. After flashing to an SD card, I booted from it and used armbian-install. I then used menu item 7 or whatever the item is to flash the MTD/SPI. I then powered down, took out the SD and rebooted.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines