All Activity

Armbian is written to a µSD card as a small file (a gig or two if I recall). If the card is 64gigs, the image is still just a few gigs written to that card. When booted on the device, though, it automatically expands the file system to the full size of the card. How exactly does it do that? And... How do I do the reverse? Take the file system from a working armbian install and create a small image that when written to a µSD card, will stay small, but then auto-expand when booted on a device?

@Popolon indeed this issue rot for a long time. I cleaned up my backlog to have more time for armbian. Also I still have quite a few processes to learn about armbian board maintenance still to this day. But you confirm that with mainline 6.12 all is fine ? But, indeed no HDMI out and no audio. I still have a patch for mainline 6.12 in the pipe about a race condition between SATA chip and nvme as far as I remind. I will prioritize data vendor kernel debugging if this mainline patch is not required (and indeed mainline still lacks any multimedia capability, this might be a showstopper for most users) even though I am close to complete testing and send PR for this one. As of now I have confirmed that this mainline patch set does not help vendor as the vendor branch has a hack that workaround the issue that mainline faces about this SATA/nvme race.

I haven't checked yet, first of all I was interested in the main core of 6.15

Tried again kernel 6.12, still no display, and it looks, like SATA instability depend on kernel version for 6.1 and have to stop/start several time the power to have it work on recent one. A bit tired of this too. It will probably not be good for the hardware to start/shutdown several time the power. After SATA disks are up they work parfectly. Looks like a power management bug, but not sure?

Did you give BSP kernel source 6.6 a try?

100mbps is enough for all my projects. if not, there are some usb3 gigabit adapters

did the 100mbps LAN make you work worse?

did you try it on windows? https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/page/8/#findComment-187561

Looks like the server images uses systemd for network control, but desktop images use network manager. I believe this should build the server images with network manager: ./compile.sh NETWORKING_STACK="network-manager"

Network bridge is added within armbian-config Docker install ... Perhaps open a ticket https://github.com/armbian/configng so this is eventually done properly.

Reinstall docker from armbian-config solved problem, with manual installed docker it won't work.

@ZjemCiKolege than you! Now wireless is activated by the overlay. @c0rnelius wifi ok but I'm still missing bluetooth (pb with the controller). See dmseg attached. dmseg-H-wifi-bt.txt

@c0rnelius here you are. Denis dmseg-H.txt

@ScoreABSM If you enable overlay via armbian-config remove "sun50i-h616" in boot enviroment(armbianEnv.txt) should be look like this overlays=bananapi-m4-sdio-wifi-bt https://github.com/armbian/configng/issues/542

Issues with the build framework, building Armbian to say, should be reported in the framework repository. https://github.com/armbian/build/ Make sure you include full logs. Use the curl command at the very and of the process or use SHARE_LOG=yes as build switch. Otherwise report might be rejected.

I guess the image with Gnome already built-in ships some extra package that makes this work or has some tweaks. Latter are obviously missing when installing from standard packages. You have to dive into the code where tweaks are applied and/or into package lists. https://github.com/armbian/build

Ubuntu 22 gnome desktop compilation encounters' Configuring Locales' exception: bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] setfont: ERROR kdfontop.c:285 put_font_piofont: PIO_FONT: unsupported font height: 16 [🔨] The keyboard is in some unknown mode I'm trying： functions/configuration/main-config.sh Pre set the value of 'DEST_LANG' It can't change either！ help

Thank you, I will study it.

Mainline audio is not working. Vendor audio is working but not activated by default yet

Sorry took so long: workaround is to set the two mixer controls via cli: amixer -c 4 sset 'Left Headphone Mixer Left DAC' on amixer -c 4 sset 'Right Headphone Mixer Right DAC' on they are off on armbian and on the initial image I was testing with which you properly sorted out was Radxa default Debian image. Edit: note you can increase the sound output by increasing "Headphone Mixer", via amixer or interactively via "alsamixer -c 4". Edit 2: note that this only works for the vendor kernel. I don't get audio out with the mainline one (replace -c 4 by -c 0 there as there is only one audio device available with mainline)

Sorry for the late reply. Note the baud rate is set in U-Boot to 1.5Mbps (and your device tells max 1Mbps).

This is for rock 5b. The U-boot requirements is for rock 5b only as it seems to be due to rock 5b being powered via this usb-c port (and talks about the USB-PD negociation needing to happen in u-boot). So this patch to rock 5b dts will not fix rock-5-itx support. Edit: Mind I have not checked yet if the rock-5-itx dts already has this code or not.

Hi, Mainline status is here: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md and description of the submitted patch is here: https://lore.kernel.org/linux-rockchip/20241210163615.120594-1-sebastian.reichel@collabora.com/ It mentions that more recent U-Boot versions handle some USB communications, so I was also thinking that updating the U-Boot on my board might help although I haven't quite worked out how to do that yet.

How do I change the default desktop environment on Debian 12 startup from cinnamon to xfce4? I have installed xfce4 and it's related "goodies", added a .Xclients file containing "startxfc4" in both root and ~/ folder locations. But the unit sometimes boots back into cinnamon. I do not see anything under armbian-config to control the desktop environment or to switch between cli/gui. I recall such options under orangepi-config (at least the cli/gui switching).

@ScoreABSM can I see the dmesg?