Jump to content

SchmuseTigger

Members
  • Posts

    53
  • Joined

  • Last visited

Everything posted by SchmuseTigger

  1. can anybody upload a changed file that I can import? I tried to do that change but nothing happend.
  2. Ah ok. I have a small fan, but I got a cheap one from china and it startet to make noise after a few weeks. I think I have to get some better ones. But my temp was about 10 degrees lower a few patches ago
  3. Question: does anybody have any ideas how to connect the uart bus so the onboard bt adapter uses it? Or any link or keywords for google? Thanks
  4. So the temp shown after booting is not correct? Because mine still shows really high temps after booting without the pi doing anything basically.
  5. Well, I try to do all those things. But most of it looks kinda alien to me. From the bottom up, no I did nothing with a modprobe. The pins say: pin 198 (PG6): 5000400.serial (GPIO UNCLAIMED) function uart1 group PG6 pin 199 (PG7): 5000400.serial (GPIO UNCLAIMED) function uart1 group PG7 pin 200 (PG8): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 201 (PG9): (MUX UNCLAIMED) (GPIO UNCLAIMED) So seems they are not connected now the other thing above with the dtb file: I found the first one: uart1-pins { pins = "PG6\0PG7"; function = "uart1"; phandle = < 0x1e >; }; and the second: uart1-rts-cts-pins { pins = "PG8\0PG9"; function = "uart1"; phandle = < 0x1f >; }; And to the HCI config: hci0: Type: Primary Bus: USB BD Address: 00:15:83:0C:BF:EB ACL MTU: 339:8 SCO MTU: 128:2 UP RUNNING RX bytes:966 acl:0 sco:0 events:41 errors:0 TX bytes:901 acl:0 sco:0 commands:41 errors:0 And the other one (the first one is a usb one that unfortunatly is not a LE so it does not work with what I want to do with it) And second one is still: hci1: Type: Primary Bus: SDIO BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 So, it seems I have to connect the device with modprobe to actually use those uart/gpio pins somehow?
  6. how or where would I be able to change that? I activated UART in the armbian-config but have honestly no clue or what to google to find that out
  7. that makes so much sense. So you could run the cores differently? But even after updating to latest version and going to slower governor still kinda hot
  8. yes, after the change it says conservative, but temp still 60+
  9. CPU temp: 62°C Usage of /: 61% of 7.1G Last login: Tue Sep 17 08:51:11 2019 from 192.168.178.20 root@orangepi3:~# cpufreq-info |grep governor available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil The governor "ondemand" may decide which speed to use not sure why the output was 4 times the same, but that is how it looked on my side.
  10. 64° while running stuff like PiHole. And yes has a heatsink but now fan running right now. But yes, seems higher then before.
  11. thanks anyhow. I feel I'm so close with the description stating that the file need to be there and that is it. And I have the file there and it is not working but showing up in a different color.
  12. Do you need only the first file or all the others too? BCM4345C5.hcd add ap6256 firmware8 months ago config.txt add ap6256 firmware8 months ago fw_bcm43456c5_ag.bin add ap6256 firmware8 months ago fw_bcm43456c5_ag_apsta.bin add ap6256 firmware8 months ago nvram.txt well, I got them to the directory, but they show up in green, does that mean anything. If it look at it with lsattr it looks the same: --------------e---- ./BCM4345C5.hcd and with hciconfig it still show the BT device as 0000000 and not working
  13. Still the BT shows: hci1: Type: Primary Bus: SDIO BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:0 errors:0 Running 5.3.0 RC8
  14. yes, that is the one I'm running and no it does not have working BT
  15. Seems to not work on OP3. Hope eventually it will work
  16. Did you have any luck with BT support? https://megous.com/git/linux/commit/?h=opi3-5.2&id=9c296799c4d3dd90986833cfded392098c1979bd I tried that but after all the steps it did not work at the end. And I could never figure out what I did wrong.
  17. For me it did not even install Pi, got an error with apt-get and stopped after a few seconds into the install. But does not change that if you go https://dl.armbian.com/orangepi3/ And check the dates on the latest updates that very much looks like a dead project to me.
  18. no clue. I have the buster version which does not work with a lot of software yet (no pi hole, no iobroker for instance), updates with apt-get show some errors and on the download section here the last update is weeks ago. Seems to be a low priority (not many people working on it). I personally wait for a good offer for a pi 4 and will just buy that, as it is supported by so many people. And then use the opie3 in a year or so for something else with the hope that the software will work then.
  19. That would suck. I tried to get it to work using the description I found in the BT thread here in the forum, but it did not work. Sucks as the files exist for 4 month to make BT 5.0 work but for a Linux newbie even with tinkering for hours I could not make it work.
  20. Wait, I thought the CPU/GPU support only comes with 5.2? I mean automatically because it is in the Linux Kernel? And I still hope for BT 5.0
  21. mine is 5.88 even with apt-get update and going to nightly build
  22. if you get it to work, please write how you did it. Also 5.2 should have it working.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines