All Activity

I am checking now Before installing plymouth, I checked that panel-mipi-dbi-spi is still loaded late: I added the include-lcd-bin.sh and installed plymouth: Checking that my bin file is there: The LCD works with plymouth: it starts the LCD earlier, with a smaller font, then switches to normal font, showing all the boot messages My armbian is not setup yet with lightdm+openbox (x11) or greetd+gtkgreet+labwc (wayland)... I will continue tomorrow

Currently trying to follow the manual https://manpages.ubuntu.com/manpages/bionic/man8/initramfs-tools.8.html#configuration hook scripts I want to include this file: Creating this file: chmod +x include-lcd-bin.sh Then I updated the initrd: Then I checked, and the desired file was included I will repeat this with the actual armbian OS with plymouth, tomorrow.

Hi Igor and thank you. It was a problem with the SSD. Thank you and best regards Christian

Hello Mark, Thanks for everything you shared with us with help of Nick and many others. I also begin with Armbian,I bought the exact same hardware piece and I would like to do the same thing. To save me a lot of time and also help other people in the community who have the same equipment. Have you made a github repo of this project ? Or is there a place where we could download it? Best Regards, Guillaume

I am using my orange pi zero 3 with an SPI 4.0" LCD, with driver panel-mipi-dbi-spi. It works great with Linux 6.13.7 (started with a self built image with edge, minimal, Bookworm) and older, but I am having troubles with 6.14.8. Result from armbianmonitor -u after upgrading to linux 6.14.8: sudo apt install linux-image-edge-sunxi64=25.5.1 I reboot and the SPI LCD starts the text mode console, then turns black instead of starting lightdm https://paste.armbian.com/ucoxuwetiq Also xorg log after "sudo startx" fails to start. When I start the opiz3 with an HDMI screen connected (appears as /dev/fb0), startx and lightdm start normally, but NOT displaying anything in the small LCD Then, I downgrade to linux 6.13.7, sudo apt install linux-image-edge-sunxi64=25.2.3 I reboot and lightdm starts normally in the 4.0 LCD https://paste.armbian.com/uqafuxexiv Stopping lightdm and trying x11 to see the log sudo startx ... starts xorg normally Just downgrading to Linux 6.13.7 allows the 4.0" SPI LCD to work again. Dowgrading the linux package did not cause a downgrade of X11 (version 1.21.1.7). The small LCD always works ok in text mode. The driver is DRM but it is using the X11 fbdev submodule The fbdev.conf file: Using an HDMI screen is not affected When I disable the fbdev conf file sudo mv 99-fbdev.conf 99-fbdev.conf.disabled Then x11 fails in another way: The xorg log doesn't show any error: dmesg|grep MESA shows nothing. Probably here is the solution https://github.com/agherzan/meta-raspberrypi/issues/1389 rebuilding mesa with some extra dependencies Bookworm containg mesa 22.3.6 right now, but Trixie contains mesa 25.0.5 I tried the same in Trixie and Sid, but still get the same error: not able to load panel-mipi-dbi_dri.so I don't know what else to look for.

@Turbine Thank you, I had this problem and your solution was spot on. Problem fixed.

Tried creating an overlay and changing it to; peripheral? /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h2-plus", "allwinner,sun8i-h3"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "peripheral"; }; }; };

some progress $ sudo rfcomm bind /dev/rfcomm0 41:BB:00:D0:D3:D8 && ls -l /dev/rfcomm* crw-rw---- 1 root dialout 216, 0 Jul 7 22:46 /dev/rfcomm0 but $ sudo hcitool info 41:BB:00:D0:D3:D8 Requesting information ... Can't create connection: Input/output error

Hi @stanelie, I so very happy because you can restored your box, I was only able to read the messages now, I'm just a curious, but I'm available to help!

please be sure to share whatever learnings you have with us

I'd say, boot from a different medium and then try the dd commands again (use pv for a nice progress bar) to see if you have the same errors again.

Thank you for reporting back. I am happy to hear you were able to find another way to solve the underlying issue without needing the v4l2loopback-dkms package anymore. I see you already have backports enabled but probably with low priority (as you should) by default. You can check "man apt" for information how to install that specific version (or use aptitude like I do). That being said, "sudo apt install v4l2loopback-dkms/bookworm-backports" should probably get you the version you need and hopefully it would install fine.

sound is a gotcha on the opi z3, actually opi z3 has sound but output only. accordingly opi z2 has sound both input (mic) and output. and i think for 'convenience' many would after all use a usb sound card instead, just that there is only one usb port and the other 2 is actually on the extension pins on opi z3 as do with the audio output on z3 http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-Zero-3.html as for usb + audio extension, orangepi sells an extension board but that accordingly without that it may be possible to hack those usb connectors https://www.aliexpress.com/w/wholesale-usb-female-type-a-with-wire.htmll if one is willing to go the distance with electronics, for the microphone i did a little research and found that there are mems microphone modules around small, compact and possibly can be easily paired with boards like z , z2 or z3 https://www.aliexpress.com/w/wholesale-mems-microphone.html but that most of these are I2S interfaces and I'm not too sure if it is feasible apparently it is there for output, but I'm not sure about input https://github.com/elkoni/Opi_Zero_3_I2S3_5.4

Thank you for the report and this indeed does look like a general bug. It appears as if this comes from the file 10-armbian-header and in particular line 199 or possibly line 214, but I cannot look into it further right now. It's probably got something to do with network not being configured at the point at which you encountered this. I do certainly encourage you to open a ticket on github with the first entry on the pulldown "bug report for the armbian build framework".

SBC Orange Pi Zero V1 is still a popular SBC and is still sold on the market, among other things, because it has an integrated sound card and for this reason, a lot of hamradio operators still buy this model because it allows you to build very compact mobile hotspots without having to attach a USB sound card protruding outside the housing and that is why it is very popular and still sold despite the fact that versions V2 and V3 have been released, so it is not an SBC that has completely gone down in history.

I haven't tested this... but I see that pins PH1, PI11, PI14 are not connectable in the orange pi zero 3. Only PH3 would be connectable. Is this correct? Is there an overlay to get PWM in PH2? (i read in the post from April 5 that it can be a PWM pin)

I've some old boards too e.g. https://www.armbian.com/orange-pi-one/ interestingly there is an updated image for it, but that things I remember there are lots of gotcha unlike the whole many generation of incremental improvements between boards that finally evolved into a opi z3. among the gotchas on orangepi one and orangepi pc h3 is that it uses a proprietary openrisc chip for power off which back then, if you run poweroff, the cpu will instead become very hot rapidly and you have to pull the usb cable quickly. today there is this thing crust which i've not yet tried which is deemed to be able to orderly shutdown the soc https://github.com/crust-firmware/crust opi z3 uses a PMIC with its own internal firmware and I think it is comms i2c etc that starts the shutdown process. things are different between the generations (of boards and kernel) --- my guess is to try a new u-boot, it may take doing a build and the changes may be quite similar to this https://github.com/armbian/build/pull/8334 https://github.com/armbian/build/pull/8334/commits/49ccbe88bc2ddf31b55ece850d28ef18c6ae8a1a --- if you want to venture and experiment with just u-boot alone here is how I once tried https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3 https://github.com/ag88/1.5GB_Fix_for_Armbian_on_OrangePiZero3/blob/main/build.md

The problem was resolved by upgrading. I had been running Armbian_25.5.1_Orangepi5_bookworm_vendor_6.1.115_minimal and everything was was fine except after a reboot, there would be an Oops error. I reimaged the machine with Armbian_25.5.1_Orangepi5_bookworm_current_6.12.28_minimal and the problem has been resoled.

@Benedito Portela Thanks!! You saved my ass, I was able to install Armbian even if I was not able to restore the original firmware. I used the SD card method with the multitool :

Thank you, I found the manual for initramfs-tools and hooks ... it looks like I can do it

Hello WDR_s, If you upgraded kernel recently, did you have any problem starting X11 (or lightdm, or desktop)? I started with a downloaded arm minimal image with linux 6.12, and my DTS would bring up the panel-mipi-dbi-spi driver correctly in text mode, but X11 can't start. When I have my normal 99-fbdev.conf, I get this: FBDEV(0): FBIOPUT_VSCREENINFO: Invalid argument, When I remove 99-fbdev.conf and let X11 setup everything automatically, X11 complains about needing panel-mipi-dbi_dri.so. I restored an old armbian OS backup with linux 6.11, and everything worked normally. You are using a different LCD driver, did you have any problem?

@Benedito Portela Thanks for finding the maskrom pin, my device is now successfully in maskrom mode, ready for recovery. However, I fail to go any further. With the rkdevtool, I tried to flash back the original firmware, so I can restart from there, but after it says Test device start, I get a test device fail message : Do you have any tips? Thanks!

Hi @Benedito Portela. I managed to get a original firmware dump of my MX10 unit with rkdumper before hosing it like you did. I am currently working to restore mine. Would that firmware dump be of interest? If so, where do I upload it? Is there a page somewhere where we could compile all the data we find about those MX10 units? Thanks!

The last year has seen substantial progress on the DRM infrastructure required to write GPU drivers in Rust. Developed in collaboration with Arm and Google, Tyr is a new Rust-based DRM driver targeting CSF-based Arm Mali GPUs. View the full article

just like to say that the recent images works just well _ _ _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ __ ___ _ __ _ __ _ _ _ _ (_) |_ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ / _/ _ \ ' \| ' \ || | ' \| | _| || | /_/ \_\_| |_|_|_|_.__/_\__,_|_||_|_\__\___/_|_|_|_|_|_\_,_|_||_|_|\__|\_, | |___| |__/ v25.8 rolling for Orange Pi Zero3 running Armbian Linux 6.12.35-current-sunxi64 Packages: Debian stable (bookworm) Support: for advanced users (rolling release) IPv4: (LAN) xxx.xxx.xxx.xxx (WAN) yyy.yyy.yyy.yyy IPv6: fd00:xxxx:xxxx::xxxx:xxxx (WAN) xxxx:xxxx::yyyy:yyyy WiFi AP: SSID: (ssid), Performance: Load: 2% Uptime: 3:50 Memory usage: 4% of 3.83G CPU temp: 41°C Usage of /: 3% of 58G RX today: 7 MiB Commands: Configuration : armbian-config Monitoring : htop