All Activity

@Seb042 For the DAC you would need to port the RPI overlay so the correct pin names are used and the you would need to check if that kernel module is installed. It might be that you're activating conflicting overlays, in the manual you could find the SPI pin names and just activate that one. Some pins do have something like the same function on m0 as on m1, activating both won't work. Other pins has different functions on the same pin like spi and i2c, activating both won't work either.

Vontar R3 RGB (multi)

bartek666666, did you manage to solve this? I have a goclever A972BK, which from what i can tell is exactly the same spec as your A971..

On this one, I have also activated all the ic2 overlays: https://paste.armbian.com/ivuyayuzub You can see the recurring message: 151.145487] rk3x-i2c fec80000.i2c: timeout, ipd: 0x80, state: 3 [ 151.150943] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_cancel_cpu_limit_freq freq qos nod add [ 151.158929] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_set_cpu_limit_freq: cpu4 policy NULL [ 151.213756] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_cancel_cpu_limit_freq freq qos nod add [ 151.221833] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_set_cpu_limit_freq: cpu4 policy NULL [ 151.248815] rk3x-i2c fec80000.i2c: timeout, ipd: 0x80, state: 3 [ 151.276408] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_cancel_cpu_limit_freq freq qos nod add [ 151.284401] rk_hdmirx fdee0000.hdmirx-controller: hdmirx_set_cpu_limit_freq: cpu4 policy NULL If I disable the overlays finishing by m1 and m4 I don't have the messages anymore.

Here the logs: https://paste.armbian.com/iwufuponax I took some time to validate that my wiring is ok with a raspberry (it's ok, I can read from the mcp3008). In the config you see above, I just activated spidev buses.

NB: armbianmonitor did not work. No such package, and nothing that I can find to install.

I have recently accepted the 23.11.1 armbain kernel release on my RockPro 64 The update has not rebuilt or updated the uIntrd for the 6.1.63 kernel. Note that the /boot/uInitrd symlink still points to the old uInitrd version but the other two symlinks have updated. root@jupiter:~# ls -l /boot/dtb /boot/Image /boot/uInitrd lrwxrwxrwx 1 root root 29 Dec 2 20:38 /boot/dtb -> dtb-6.1.63-current-rockchip64 lrwxrwxrwx 1 root root 33 Dec 2 20:38 /boot/Image -> vmlinuz-6.1.63-current-rockchip64 lrwxrwxrwx 1 root root 33 Nov 30 18:04 /boot/uInitrd -> uInitrd-6.1.50-current-rockchip64 root@jupiter:~# ls -l /boot/uInitrd* lrwxrwxrwx 1 root root 33 Nov 30 18:04 /boot/uInitrd -> uInitrd-6.1.50-current-rockchip64 -rw-r--r-- 1 root root 17777215 Jul 22 21:07 /boot/uInitrd-5.15.93-rockchip64 -rw-r--r-- 1 root root 17560966 Nov 30 12:06 /boot/uInitrd-6.1.50-current-rockchip64 The first time after the update I did not notice before rebooting, and the box failed to boot properly. I got to a rescue console and was able to restore the three 6.1.50 kernel files from a backup, and restore the symlinks. I tried running: apt reinstall armbian-config armbian-firmware linux-dtb-current-rockchip64 linux-image-current-rockchip64 linux-u-boot-rockpro64-current base-files But this did not fix the problem. Google is not helping me find the command to create the 6.1.63 uInitrd file by hand. I have also tried installing the 6.1.64 kernel from beta.armbian.com but that had the same issue. Currently my device is running 6.1.50-current-rockchip64 but the 6.1.64-current-rockchip64 kernel is installed and I suspect that there are inconsistencies in how things are setup. For example wireguard is not working correctly. How can I restore my device back to a stable working state?

2SteeMan: sorry, my mistake the image based on Armbain build from here: https://ReARM.it How can I enable vga port on Orange pi 800 in Armbian?

No not the same thing at all

2SteeMan: Retropie build on Rasbian os. Does Rasbian not the same as Armbian?

These forums are for Armbian software. You need to go to ask your questions in a forum/site that supports the software you are running. If it isn't Armbian we can't help you.

Hello, could someone please help me. I've got image Retropie for OrangePI 4 LTS, put it to SD-card. My Orange pi 800 started with this SD-card, everything worked fine, but video enabled only thru HDMI port. MY old CRT display didn't started with vga port, however CRT display works on the other oficial images sach as Ubuntu, OS droid, Manjaro. How to enable vga port in Retropie?

Hello again, I was forced to reinstall OS and right now I have no sound at all. I managed to fixed it in first place but can't find website where I found solution. https://paste.armbian.com/omovipuyub So far I had installed pulseaudio and edited manually /etc/asound.conf but no success so far.

Hello everyone, I recently installed the version "Armbian 23.11.1 bookworm" on an old Odroid C2, mainly to run Openhab there. Now I wanted to be informed about certain events on my Fritzbox (e.g. window open for too long) via linphone and I also found instructions for this: https://community.openhab.org/t/make-dect-phones-e-g-fritzfons-connected-to-fritzbox-ring-as-alerting-mechanism-from-openhab-should-be-useful-also-to-have-openhab-make-arbitrary-phone-calls-with-alerts-announcements/132940 I installed the package “linphone-nogtk” with version 5.1.65-4. If I type on the console the following commands: linphonecsh init linphonecsh register --host fritz.box --username <username> --password <password> linphonecsh dial **610 I get the following error message: Call 1 with sip:**610@fritz.box error. Error from linphone_core_invite. Unfortunately, after a lot of Googling, I couldn't find anything helpful about this error message. However, a test under Ubuntu 20.04 with version 4.4.21 of the package and another test on a Raspi under "Raspbian GNU/Linux 10 (buster)" with version 3.12.0 of the package were successful. The internal telephone rings there and no error message is displayed. Is anyone able to help me? Is this perhaps a bug in version 5.1.65 or does something still need to be configured/installed? I run the Odroid without a monitor, so everything should only run on the console. What does the error message “Error from linphone_core_invite.” mean?

Hello, i´ve got the same problem here. Non off the bullseye images in the archive will boot (no blue light) except of: https://armbian.lv.auroradev.org/archive/odroidn2/archive/Armbian_21.08.1_Odroidn2_bullseye_current_5.10.60.img.xz after update&upgrade there is no ethernet and black screen so i can´t use it anymore. Bookworm and jammy works fine, but i need openmediavault so i need bullseye. Any ideas? Sorry for my english. Best wishes sportyspice

Hello, sorry if this has been answered somewhere else. I was just wondering how i upgrade my Orange Pi 5 running Arbmian 23.11.1 Bookworm w/ Linux 5.10.160-legacy-rk35xx to the latest Kernel. I tried using `sudo armbian-config` and updating via that with kernel upgrades unfrozen but it doesn't seem to work. Is there something I'm missing? Startup splash below: ___ ____ _ ____ / _ \| _ \(_) | ___| | | | | |_) | | |___ \ | |_| | __/| | ___) | \___/|_| |_| |____/ Welcome to Armbian 23.11.1 Bookworm with Linux 5.10.160-legacy-rk35xx System load: 4% Up time: 0 min Memory usage: 8% of 3.83G IP: 192.168.1.69 10.121.215.1 CPU temp: 40°C Usage of /: 6% of 57G RX today: 38.2 MiB

@Energokom https://chinagadgetsreviews.com/download-android-13-stock-firmware-for-vontar-r3-rgb-tv-box-2.html this is the image ? Can you give me a link to dl r3 RGB firmware thanks

Using the Rockchip Create Upgrade Disk Tool Version 1.7, write the vontar r3 RGB firmware to SD card, insert the card into the TV box and connect USB to USB to the PC and then the TV box will determine the system.

@jock I tried again with lsusb and the curdent. I thought it might be the cable. I tried the same technique with my other dq08 box (exactly the same one which is not brick), it recognized it. So the cable's fine, my tricks are good. The box doesn't even want to be recognized.

Thanks

This image works very well on R5S. Thanks. Is there any plan to add support to R5C which is very close (Friendly Elec offers the same software for both devices) ? Or must I try to adapt? R5C boots well on this image, and at first glance, the two points which are not working well are the names of ethernet ports, which can be fixed by an udev rule, and the Leds which remain off. This also can probably be fixed by Udev. How are the Leds handled on R5S ?

@jock I have dq08 4go. I tried with the usb to usb, with the software for reset (a software that the aliexpress salesmen said to use). And it's not even recognized by the windows device manager

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

https://docs.armbian.com/User-Guide_Getting-Started/

Latest kernel upgrade broke the odroid again, executing the command by @jbergler (with manually changed kernel version) fixed it again.