All Activity

well.. just to answer your questions.. i always were very close with computers, i know a lot of programming languages and in essence i am addicted to computers and generally everything related to technology.. for someone who knows how to deal with pratically everything i get my hands on in terms of messing with hardware and programming in several degrees, i really don't get it whats so hard just by oppening the 4 screws on the bottom of the boxes, and read the cpu, lan, wifi and Bluetooth and simply installing the basic system and it's drivers.. yes, its as simple as doing that after dealing with the bootloader, and that, with so much shares there are nowadays in the internet i can honestly say i never had any problem with any box i had in my hands.. and basically, there are a lot of boxes, i can say around 90% that have compatible firmwares, being the main and biggest problem for a lot of people, the wifi, the lan and the Bluetooth.. and after you know how to build your drivers, it's really so easy to get things going.. so yeah, in a tech perspective i think it's ridiculous to think that there are boxes impossible to get it working right.. it just takes a bit of work, but for anyone that knows how to deal with linux (and this forum is about armbian, essentially linux) i see all that hate as comparable to someone in a Windows forum putting hate for someone saying they are having difficulties installing a driver on Windows on computers that are not from a bigger brand.. and for the kind of affirmation you made it looks like you think i'm one of those superfans of iptv that sells boxes with servers subscription 😂 but nop, not one of those.. i never wanted anything to do with it, but i sold a lot of android boxes to guys like that, so yeah, i know what you mean 😉 essentially, i had here in my country since 2013, a big website during almost 10 years called lojandroid.com, "loja" from that name is the equivallent to "store". Nowadays everyone knows what a android box is and it's sold even in supermarkets, but during at least in my first 3 years selling them, i can tell you i had sales on several portuguese marketplaces that didn't had another seller with android boxes beside me 😉 As i said before, i always loved messing with hardware, and for several years i sold lots of android boxes with all kind of servers installations, and my customers just come back sometimes asking for warranty for heating and freezing installations and/or corrupt installations on the ROM or on the sdcard, when its the later i simply had to copy from my backup of the system i had for that model, burn to a new sdcard, and the customer just had to put the sdcard on the box, turn it on and voilá, a new system on a push of a button.. because yes, every model box i sold i made a backup of its original firmware and of mine with my modifications.. The brand i sold a lot during the first years, was minix, and i can tell you that the some problems i had with the cheapest, also had with minix.. but the big question there is that 1 minix box price would pay around 3 boxes with the same hardware on white brands.. There will always exist the purists and normal people that know that the world is a lot bigger than the bigger brands.. but for the looks of you affirmations it looks like for example you dont know that for example nowadays the chinese eletric cars are becoming far superior than the most known brands.. Nowadays BYD, Polestar and a lot more brands are superior than the Teslas, but the teslas purists will say that it's not the same.. it's also the same things like Apple people say from the other brands or operating systems.. Nothing against teslas and iphones, in fact i adore teslas and even had two iphones, but in case of the iphone, me being me, i don't like to be locked, i also always messed a lot with the firmwares on my phones, and in Iphones, besides the jailbrake that just leaves it a bit more usable, i never got much to play concerning the things i like to do 😂 in conclusion, i'm not saying bad of the specific chipsets used for armbian! I just dont think that is white or black.. theres really of gray area in between, i for my experience know that the World is really a lot, lot, lot bigger than that, and chipsets simply are nothing more than a computer, and a lot easy to mess on that sense after getting the hang of it.. hope i gave someone a fun reading, and keep cool everyone 😉👍

Interesting effect of changing the ili9488 10cm (4.0 inch) for a 9cm (3.5 inch) LCD, same resolution https://a.aliexpress.com/_mMKRqan https://a.aliexpress.com/_mqk0Qbv maybe I need a different spi frequency

Honestly I was quite tired of playing with kernels where things are not working as expected. It's not a criticism towards the armbian developers community, but despite the ongoing effort, a stable maturity of the kernel\sotware is not reached yet. For my personal use cases, I need: - server mode and no vendor Radxa Os. - SATA working - audio working Despite some overoptimistic initail tests with the 6.1.99 vendor kernel, at the end of the day SATA is not stable enough. Sometimes I've to turn off/on the device up to 3 / 4 times before having the SATA drives detected. Taken by an overwhelming frustration, I took the risk and removed the R29 resistor as described here. Now SATA is working as expected everytime at least with vendor kernel 6.1.99: I need this version also because it has the audio drivers working correctly. I hope that a definitive software solution can be found in the near future without the need of hardware hacks.

tested sd card: No difference iperf3 from client to Helios around 20mb/s I tested another local 2.5Gbit transfer client (arch arm) - server (armbian) 2.34Gbit/s (292mbit/s) and reverse 326mbit/s (40mb/s) Maybe a setup problem with the switch or with arm-arch client drivers Nevertheless thank you for your help! ;)

Dear friends, in the end, I’ll answer myself... I have thoroughly studied the entire documentation from both Orange Pi and the RK3588 datasheet, and I am almost certain — unless I made a mistake — that there is no PCM function on the pins listed in the documentation for the Orange Pi 5 MAX. I have created a map of all the pins and their functions in various modes, and I hope it will be useful to someone.

Why? Will cause recompilation on every build This does not exist anymore IIRC. Non-standard docker image can cause rebuild since it is now based on Noble. This is not needed since it is default behavior. Also unneeded since default is yes already.

You know one can have multiple DE's installed and select which one to use at login? sudo tasksel kde-desktop lets you add KDE Plasma for every Debian based install. Important note is that RK3588 needs a pretty new mainline kernel otherwise forget KDE. With vendor kernel it should be no issue. So if you want to use KDE Plasma, no new image or install is needed. But maybe you only want to build an image and not use it.

I apologize if this is a basic question. I'm trying to make a minimal Orange Pi Zero 3 Trixie image with a btrfs file system and NetworkManager for the networking stack using Docker without having to compile a new kernel (i.e., I just want to use the precompiled kernel found in the CSC version). I created a `config-myimage.conf` file under `build/userpatches`: BOARD=orangepizero3 BRANCH=current RELEASE=trixie CLEAN_LEVEL=cache KERNEL_CONFIGURE=no BUILD_KSRC=no BUILD_MINIMAL=yes NETWORKING_STACK=network-manager DOCKER_ARMBIAN_BASE_IMAGE=ubuntu:jammy ROOTFS_TYPE=btrfs BTRFS_COMPRESSION=zlib CONSOLE_AUTOLOGIN=yes #BOOTSIZE=96 # need larger boot size to prevent 'disk out of space' # on kernel upgrade BOOTSIZE=256 COMPRESS_OUTPUTIMAGE='sha,xz' EXTRAWIFI=yes function user_config__010_modify_package_list() { # adds additional packages to the package cache add_packages_to_rootfs btrfs-progs neovim pmount nmap tmux # edit this list to remove packages from cache remove_packages nano } I then ran `./compile.sh myimage`, but it launches into kernel compilation. I did this once before uisng bookworm, but I can't remember how....

I found the dts setting about "ethernet@5020000" was different between kernel 5.15.93 and kernel 6.1.47. We need to make sure the following things are correct: 1. Ethernet driver uses the correct clock/reset 2. GPIO reset can be pulled up 3. MDIO can correctly go to PHY 4. Pinmux correctly sets Ethernet pins #Kernnel 5.15.93-sunxi64 ethernet@5020000 { compatible = "allwinner,sun50i-h6-emac\0allwinner,sun50i-a64-emac"; syscon = <0x31>; reg = <0x5020000 0x10000>; interrupts = <0x00 0x0c 0x04>; interrupt-names = "macirq"; resets = <0x04 0x21>; reset-names = "stmmaceth"; clocks = <0x04 0x54>; clock-names = "stmmaceth"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0x32>; phy-mode = "rgmii-id"; phy-handle = <0x33>; phy-supply = <0x34>; phy-io-supply = <0x35>; allwinner,rx-delay-ps = <0xc8>; allwinner,tx-delay-ps = <0xc8>; phandle = <0x78>; mdio { compatible = "snps,dwmac-mdio"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x79>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x01>; reset-gpios = <0x1f 0x03 0x0e 0x01>; reset-assert-us = <0x3a98>; reset-deassert-us = <0x9c40>; phandle = <0x33>; }; }; }; #Kernel 6.1.47-current-sunxi64 ethernet@5020000 { compatible = "allwinner,sun50i-h6-emac\0allwinner,sun50i-a64-emac"; syscon = <0x32>; reg = <0x5020000 0x10000>; interrupts = <0x00 0x0c 0x04>; interrupt-names = "macirq"; resets = <0x06 0x21>; reset-names = "stmmaceth"; clocks = <0x06 0x54>; clock-names = "stmmaceth"; status = "okay"; pinctrl-names = "default"; pinctrl-0 = <0x33>; phy-mode = "rgmii-id"; phy-handle = <0x34>; phy-supply = <0x2e>; phy-io-supply = <0x35>; allwinner,rx-delay-ps = <0xc8>; allwinner,tx-delay-ps = <0xc8>; phandle = <0x79>; mdio { compatible = "snps,dwmac-mdio"; #address-cells = <0x01>; #size-cells = <0x00>; phandle = <0x7a>; ethernet-phy@1 { compatible = "ethernet-phy-ieee802.3-c22"; reg = <0x01>; reset-gpios = <0x1e 0x03 0x0e 0x01>; reset-assert-us = <0x3a98>; reset-deassert-us = <0x9c40>; phandle = <0x34>; }; }; };

To troubleshoot this thing I would just boot from another sd card with a fresh bookworm image leaving your system on emmc or on another sd untouched. In 'sudo ethtool -i <interface>' the name of your 2.5G interface has to be inserted - 'ifconfig' will reveal it (I renamed mine to end1). If the rtl_nic firmware is recognized correctly it will display: root@grid:~# sudo ethtool -i end1 driver: r8152 version: v1.12.13 firmware-version: rtl8156a-2 v2 04/27/23 ...

I am trying to downgrade to kernel 5.15.93-sunxi64 and found the eth0 is worked. pi@orangepi3:~$ dmesg | grep eth0 [ 18.467932] dwmac-sun8i 5020000.ethernet eth0: PHY [stmmac-0:01] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 18.468969] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 18.469701] dwmac-sun8i 5020000.ethernet eth0: No Safety Features support found [ 18.469727] dwmac-sun8i 5020000.ethernet eth0: No MAC Management Counters available [ 18.469734] dwmac-sun8i 5020000.ethernet eth0: PTP not supported by HW [ 18.475463] dwmac-sun8i 5020000.ethernet eth0: configuring for phy/rgmii-id link mode [ 20.510690] dwmac-sun8i 5020000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 20.510735] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

See https://github.com/canonical/netplan/pull/456#discussion_r1569065581 The way the netplan + networkd integration is designed requires all the network devices (wlan0 in particular) to exist at /sbin/init time - otherwise, the netplan generator disables `systemd-networkd-wait-online.service` which also causes `network-online.target` to be reached early. In particular, this breaks any network FS mounts on boot. Of note, I tried logging in to file the bug via the dev contribution platform, but it looks I'm blocked from JIRA access, so am filing it here instead.

My log : https://paste.armbian.com/idomububex I find the phy issue stiil happened in OranpePi3 when using Kernel 6.1.47-current-sunxi64 and 6.12.20-current-sunxi64. @Jack07 @JohnnyLaw Do you still have same issue when using 6.X.X verion kernel?

@Werner I will close this Topic and discuss the issue in the old one.

@Werner Yes, My SBC model is "OrangePi3", not LTS.

Great. Just to avoid cross-contamination. You are sure you have the Orange Pi 3 and not the Orange Pi 3 LTS model? Background: OrangePi naming scheme is kind a ridiculous, makes no sense often enough and introduces confusion. In this particular case they switch to a different PHY chip which I think was migitated by Armbian but not sure if they still have separate images. Seems like a similar topic already exists: https://forum.armbian.com/topic/34024-cannot-attach-to-phy-after-upgrade-to-202381/

Now I am trying to downgrade Kernel back to 5.51.X and figure out it.

@Werner Got it! Thank you for your help. https://paste.armbian.com/idomububex Provided the link.

Hi KDE Plasma is not an officially supported DE, therefore hidden behind code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } EXPERT=yes switch. May work, maybe not. No support for it, just like for any user-built image. Example without interactive menu including all available app groups: ./compile.sh build BOARD=orangepi5-plus BRANCH=vendor BUILD_DESKTOP=yes BUILD_MINIMAL=no DESKTOP_APPGROUPS_SELECTED='browsers chat desktop_tools editors internet multimedia office programming remote_desktop' DESKTOP_ENVIRONMENT=kde-plasma DESKTOP_ENVIRONMENT_CONFIG_NAME=config_base EXPERT=yes KERNEL_CONFIGURE=no RELEASE=bookworm

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

moved

The eth0 device does not work when using 6.1.47-current-sunxi64 and 6.12.20-current-sunxi64 kernels. There will be the following errors in the kernel log. pi@orangepi3:~$ dmesg | grep eth0 [ 16.997431] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 16.998219] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 19.284111] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 19.284754] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 19.308140] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 19.308738] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 19.334063] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 19.334754] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 19.358727] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 19.359417] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 151.380407] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 151.381105] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 157.928629] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 157.929360] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 320.009515] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 320.010271] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 320.037458] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 320.038169] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 320.062716] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 320.063428] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19) [ 320.082662] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 320.083389] dwmac-sun8i 5020000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19)

Hi Providing logs with PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

moved

Only with kernel versions 6.1.x am I able to apply the static network config for RTL8211F interface (but sometimes it'll fail), but with newer kernel versions (v6.6.16/v6.6.63/v6.12.22/v6.14.0-rc4/v6.15.0-rc1), trying to apply the network config with `netplan apply` always fails with `Failed to reset the dma` error.