haajee

I run it on Buster with kernel 5.6.2

I am a little bit flabbergasted. In thought: i download the Android 9 / TV image from the Rockpi site for the Rock Pi 4 who has also a RK3399 chipset. So i did and flashed it to a SD card and put in the Orange Pi 4. Ethernet activity and link lights up and a red light. Nothing looks happen but there was a lot of traffic. So i disconnected the power supply and back in and... Rock Pi Kernel on my TV. Than the Android Booting logo and there was Android itself. Tries a few things but looks like mostly all things work. Bluetooth works, sound works, wifi works. When i look by the buildnumber i see also: RK3399-Pi. Without Rock Pi or something. So it looks like just a universal image. But the Rock Pi android version is a lot more up to date. Oh there is one thing what not works. When i choose for restart by shutdown it hangs and do i need to remove and replug the power supply again....

Oh i see now there is a # for the echo temperature. Deleted and worked. #echo "temp: $temp, target: ${CpuTemps[$i]}, duty: $DUTY"

I saved the file in my home dir as pwm-fan.sh and run it as administrator with bash ./pwm-fan.sh And the fan spins up full speed but after that it stops running. Even when the temperature is over the 30 degrees celsius. I have changed 48000 in the above script to 30000. So i think there is also something else to change but i have no idea what. Who could help me?

Hi all, So if a lot of you maybe know is a heatsink and fan a must for the OrangePi 4. With my temporarly installed fan makes a lot of noise i maked yesterday the step to order a Noctua NF-A4x20 5V PWM. The price was arround €17,- not the cheapest but te reviews are amazing. Even on full speed its a lot more silence then the 20x20 mini fan but with a good air flow. But as you could read did i choose for a PWM variant so i could control the rpm´s with a PWM GPIO pin. And amazingly it did work! I have the PWM pin connected to pin 7 of the OrangePi 4. Commands to start pwm for the first time: cd /sys/class/pwm/pwmchip1/ echo 0 > export echo 1000000 > pwmchip1/pwm0/period echo 500000 > pwm0/duty_cycle #and with this step the fan goes on a lower speed echo 1 > pwm0/enable #and back on full speed without PWM echo 0 > pwm0/enable So it´s really nice. And i found a nice script for the Nanopi M4 with also a RK3399 chip from @mar0ni in this topic To make it complete i paste also here the script from @mar0n

Hmm, sadly does not work... The result of your command: $ sudo dmesg | grep Blue [ 25.829280] Bluetooth: Core ver 2.22 [ 25.829368] Bluetooth: HCI device and connection manager initialized [ 25.829384] Bluetooth: HCI socket layer initialized [ 25.829392] Bluetooth: L2CAP socket layer initialized [ 25.829419] Bluetooth: SCO socket layer initialized

Oh i will try now!

bluetoothctl didn´t find any controllers. Bluetooth service gives this error but start: ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-04-13 17:33:55 CEST; 3min 45s ago Docs: man:bluetoothd(8) Main PID: 4218 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4533) Memory: 1.0M CGroup: /system.slice/bluetooth.service └─4218 /usr/lib/bluetooth/bluetoothd apr 13 17:33:55 4-OrangePi systemd[1]: Starting Bluetooth service... apr 13 17:33:55 4-OrangePi bluetoothd[4218]: Bluetooth daemon 5.50 apr 13 17:33:55 4-OrangePi systemd[1]: Started Bluetooth service. apr 13 17:33:55 4-OrangePi bluetoothd[4218]: Starting SDP server apr 13 17:33:55 4-OrangePi bluetoothd[4218]: kernel lacks bnep-protocol support apr 13 17:33:55 4-OrangePi bluetoothd[4218]: System does not support network plugin apr 13 17:33:55 4-OrangePi bluetoothd[4218]: Bluetooth management interface 1.15 initialized

Hmm, maybe do i something wrong. But copied the files to the corresponding folders and installed the 2 .deb files. But when i start bluetoothctl it hangs... When i remove and reinstall bluetooth support via armbian-config i can start bluetoothctl but says there are no controllers found. After reboot bluetoothctl hangs.

But how can i as simple user add the fix? Looks very difficult for me?

Thank you so much! Like to use bluetooth. Is bluetooth also just usable with bluetoothctl headless?

Always good to share this troubles. :) Learn from mistakes from others, you couldn't make them all by yourself. :P And trust me: i make a lot. ;)

I read a lot of stability problems... What do you all use for power supply? A USB charger is not the same a power supply. Special is the are USB-C PD chargers. See also this. Since i use on all my orange pi´s a simple cheap 5v 3A like hese power supply it works all smooth and very stable. I also tested some USB-C cables with USB PD chargers or quick charge chargers. And a lot of time it won´t boot of it freezes...

The first thing just yesterday done I could also generate self a build. But i don´t have enough diskspace

Is dit also possible to generate a Armbian Buster server / headless with kernel 5.4? Now there is only a headless buster with 4.4 or with desktop 5.4.

Strange enough do i got troubles when i format it before in EXT3 of EXT4 and write the image. When i format it before as FAT32 it works ok.

How do you put the image on the card? And how do you format the SD card before? I format it on Linux Mint as FAT32 and then write it. But that could be also great with Belena Etcher. And do you have the Orange Pi 4 with eMMC or without? I think with the eMMC because you say it boots the onboard Android. Flashing to eMMC is described in this manual. https://drive.google.com/file/d/1wko5XfiFaw8qpB2uKXpdIYjiwlVFq4QG/view?usp=sharing

I run now a few days 20.02.3 stable with kernel 5.4.23 and the things i discover are: Bluetooth looks not to work (headless) APCUPSD do i not get to work. With an older kernel it works Cannnot switch to kernel 5.5.8. Get an error. In switch_kernel.log is to read: ´linux-image-dev-rockchip64=20.05.0-trunk.069 linux-dtb-dev-rockchip64=20.05.0-trunk.069 linux-u-boot-orangepi4-dev´. Dont know also what ´trunk.069´ means Maybe simple things to fix. But i learn a lot but i am really sure not a advanced linux user.

I think for the price it´s a good board. A heatsink is a must btw.

Oh, you mean the hardware fault in the H6 with result in a not working PCI-E port? I know to much about the details but readed on Facebook i thought that the PCI-E extension module worked. I got bluetooth not working. Wifi works. I want to try the GPIO pins but don't just know how to got it working.

Not really tested yet. I use the board headless so i don´t knnow. Because the board is not long relesed and also chinese new year and the corona virus makes that delivery takes a lot more time. It works ok what i see now. But remember that Armbian is just work in progress for this board. If you stay on safe could you better buy a Rockpi 64 or something.

My Orange Pi 4 arrives this week and i am now testing it. It''s a lot faster than the H6 and works ok! I hope, and if someone have a suggestion, there comes a case for this Orange Pi 4. I have btw the most basic version. No NPU and no internal flash. With my higher quality HDMI cable i got no display like i has on the OnePlus. Strange enough: when i plug a cheap hdmi cable in i got display. Maybe display works with HDMI 1.4 cable and not 2.0? A heatsink with a fan looks essential. I have broke a heatsink from a old Fritzbox 7490 and attached a fan to it. Now is it IDLE arround the 30 degrees and with full load arround the 45 When it boots it takes a really long time before i could get access via SSH or see something on HDMI. What is the system doing in that time?

Hmm, yesterday back to kernel 5.3.something and now after apt upgrade back on 5.4.20 stable. Just with the continuously load of files when i trie to start armbian-config. When i try to switch to kernel 4.19.104 i got an error. The rest is just working fine.

I have also with Armbian Buster 5.4.20 that every time when i start armbian-config he reload all the packages for armbian-config?

Hmm, mines is continuously around 38 degrees with active cooling. Thnx for your info. Maybe is it placebo but it feels like the pi works faster! So i hope