All Activity

I try installing Debian Trixie using the installer by 2 differents approachs but It didn’t succeeds. 1) using a bootable USB key with ARMhf (Generic version), found on Debian web site 2) Has described in DEBIAN ARMhf installation manual, using hd-media to include the asus c100p correct .dtb (tree) files during the creation of the external USB. Regardless the method, the USB key with intaller, is not recognized, when typing CTRL+U, in developper mode. The Chromebook didn’t see the key, but it work well with Zutchi group, but not here. I only received a serie of bibs, when doing CTRL+U. I also try building an ARMBIAN image, but, Asus C100P is not available in choices, and I look in EXPERT mode, not supported, but didn’t find a generic ARMhf file having features: RK3288 processor, 4Gb of RAM, 16Gb of emmc, 2 x USB, USBc, hdmi, wifi, so I didn’t complete the process. I am open to suggestions, but my next trial is using ‘dd’ and install the ‘Velvet trixie’ image found on GitHub directly on emmc ‘drive’, if not succeed, I will try Archlinuxarm with PostmarketOS. Thanks for your comments and suggestions.

@Tomi Skies try the x96q images https://github.com/NickAlilovic/build/releases/tag/20250306

Everything worked fine, even tried some ffmpeg for hardware decode

This is on minimal. So no xorg or Wayland. But I use xorg normally. I generally start with minimal and work up. I despise both Ubuntu and gnome. You won't find those on any computer I own. I compromise with xfce for the little time I might use it before I have everything set up. I've just reversed direction and installed debian xfce stable. Mostly to avoid the hassle of replacing net plan with network manager. A PIA. I can uninstall all the stuff I don't like that comes with the desktop version. Probably easier. With xfce there are two screens, but the one on the built in screen seems to be double the size it should be. I can only see half the dog. I can live with that for now. At least it uses the Fullscreen of the HDMI.

Couple of data points that may be helpful. Platform: BTT PI v1.2 D/C 2023.11.8 with the U2C CAN board Distro: Armbian 25.8.1 Bookworm Kernel: 6.12.43-current-sunxi64 Overlays: spidev0_0 1. Adding a sleep 5 hack did not work for me, however what does *seem* to work is inserting the following line to /etc/netplan/30-wifis-dhcp.yaml activation-mode: manual WiFi was still activated (which may be another bug) for at least 3 cold boots in a row (didn't have time to test more thoroughly). Here's a pastebin link from right after one such boot - https://paste.armbian.com/umijapukiy 2. The error from wpa_supplicant is CTRL-EVENT-SCAN-FAILED ret=-1 retry=1 .Same error code (-1) is also reported when attempting a manual scan pi@jubilee:~$ sudo iw wlan1 scan command failed: Operation not permitted (-1) 3. Broken state of the WiFi driver seems to be correlated with mmc errors in dmesg [ 11.490708] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490745] sunxi-mmc 4021000.mmc: send stop command failed [ 11.490856] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.490880] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491071] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491098] sunxi-mmc 4021000.mmc: send stop command failed [ 11.491224] sunxi-mmc 4021000.mmc: data error, sending stop command [ 11.491248] sunxi-mmc 4021000.mmc: send stop command failed These are not present if wifi was activated successfully. Here's a pastebin link from right after such boot - https://paste.armbian.com/xovixuniti I did run F3 on that SD card before installation so I doubt it's at fault, but I am currently running another test with armbianmonitor -c overnight just to be sure. 3. Reloading the kernel driver (8189fs) when it is already in a broken state is very slow and provokes a slew of mmc errors $ sudo /sbin/rmmod 8189fs pi@jubilee:~$ time sudo /sbin/modprobe 8189fs real 2m15.835s user 0m0.008s sys 0m0.048s $ dmesg .... [ 673.262192] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262286] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262379] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262471] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262563] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262656] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.262716] ====>_BlockWrite 101 i:0 [ 673.262742] ====>_WriteFW 230 [ 673.263001] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263088] sunxi-mmc 4021000.mmc: data error, sending stop command [ 673.263141] ====>_BlockWrite 101 i:0 [ 673.263162] ====>_WriteFW 230 Again the same problem is not present if WiFi was activated successfully after boot: Shutting down the interface and reloading the driver works just fine. Please let me know if there's anything else I can collect that can help to track this down. Given this is a fresh install and has no personal data in it yet, I can share my SD card image if that would be helpful.

What do you mean by that? You mean LCD screen on the device and HDMI monitor. This should probably work OOB on vendor 6.1.y kernel. It should also work with mainline, but I haven't tested that and I am not sure that this is included in latest stable build as it was added not long ago. Try build from sources, use EDGE kernel perhaps. It is very specific case - probably nobody asked for that before. At least I don't recall. Core features are based on SoC, so when you are looking for clues, look wider - Orange 5 *, Khadas Edge 2, Bananapi M7, ... all that carries RK3588 SoC. Best is to start with recommended Gnome image. That is most polished.

"*** Warning - bad CRC, using default environment" This is safe to ignore. It is strange why Ubuntu doesn't work, while Bookworm does. This could be some build infrastructure issue. https://docs.armbian.com/Developer-Guide_Build-Preparation/

Does anyone have any clues to give as to setting up dual screen on the Nanopi m6? I searched the forum and found nothing. I don't know why I can never easily find Anything here. The forum shows one post for the Nanopi m6 and I know that can't be right. The Nanopi mirrors by default, and that is just not going cut it. Currently installing X on a minimal install. But that's the next thing. Get a reasonablf sized terminal up.

Welcome to Armbian, I'm your emotional support, I'll give you all the support if you want to start developing a custom firmware for this device, we have all the time in the world, one day this will be ready and we will put your name on it, it will be cool, I believe you have the ability to start volunteering, get in touch

for Pi-Hole i'm using: "cbcrowe/pihole-unbound" https://hub.docker.com/r/cbcrowe/pihole-unbound For docker Containers I'm on Casa-OS curl -fsSL https://get.casaos.io | sudo bash pihole-unbound.yaml

for thoses who want to install sd to emmc, use this script (remove the line about haos near the end)

everything is in the main post

No idea what causes this, will need to check on my device

What you are reporting is quite common with tv boxes. The case markings often are different than the internals. What is it you are looking for? Your post didn't really ask for anything other than to report that you got a common tv box with internals that differ from the case.

No, i gave up compiling on Armbian, i installed the debian bookworm server image provided by orangepi instead

I was having some pretty substantial problems with several different builds before developing this hold pattern, Werner

IIRC until like half a year ago this also worked just fine. I assume then this check was introduced upstream which caused this - more or less cosmetical - error.

@JohnTheCoolingFan any clue?

If I hold those packages I don't see any issues at all.

moved. All boards using rk3588/s soc most likely work best with either vendor or edge kernel. Current has limited functionality since when this kernel became LTS only basic support was there. All further enhancements regarding hardware featureless were upstreamed later.

I think there are some directories in /etc which contain initramfs pre/post scripts. I don't have hw on hand to check right now but I believe there was some script starting with z50- filename that contained this check and there should be a 2nd one from Armbian that actually does what the upstream script refuses to do.

@0jay it should also happen for your build as well since I'm using generic Raspberry Pi build on RPi5. Or you never see it because of the "hold"? @Werner That's good to know. May I know if there's any way for me to check for certain? Thanks a lot!

Yep... that looks like the method I had thought about: get the source from https://github.com/philipl/mpv.git#branch=v4l2request and compile it with the v4l2request option I have old experience making redhat rpms, but I need to learn how to make debian debs UPDATE: I wrote my self built debian trixie xfce image with 6.15.4 from July (need 6.13+ for v4l2 kernel functions)... then Install the apt.undo.it repo and ffmpeg, as per the first post of this thread (Following guide from https://github.com/philipl/mpv/tree/v4l2request) $ sudo apt install libavcodec-dev (installs libavutil-dev libswresample-dev automatically) $ sudo apt install libavdevice (installs libavfilter-dev libavformat-dev libpostproc-dev libswscale-dev automatically) $ sudo apt install meson cmake pkg-config Download code: $ wget https://github.com/philipl/mpv/archive/refs/heads/v4l2request.zip $ unzip v4l2request.zip $ cd mpv-4l2request Install libplacebo source $ mkdir -p subprojects $ git clone https://code.videolan.org/videolan/libplacebo.git --depth=1 --recursive subprojects/libplacebo Build: $ meson setup build Now I ran out of time to try this... anyone trying to do it, please post progress

So there is some conflicting naming between the name of the unit and the name on the board revision code. The name of the unit would suggest that it's a X96-Q clone, but the revision number suggests that it's a T95 mini. Like as seen in this video

Thanks! we hope this guy could get the time to do it, I will be here for every testing need ! 😁 I already installed Armbien on an orange Pi zero 3, and I'm running pihole on it. Works fantastic! At least this allows me have some experiencie with Armbian