Walter Zambotti

The problem turns out to be the kernel version. The minimal image comes with 6.1.30 which provides a new video device (called None-1) and the desktop image comes with 6.1.11 which does not have this mystery video device. All working with the reverted kernel.

Seems the fix is to use kernel 6.1.11 that comes with the desktop version and not 6.1.30 that comes with the minimal version.

it turns out this mystery video device (None-1) is provided by Kernel 6.1.30 and revertiong back to 6.1.11removes the device.

So I edited the boot.cmd file and added this line after each of the setenv bootarg ... lines : setenv bootargs "${bootargs} video=None-1:d" recompiled with sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr checked the lines had made it to boot.scr and rebooted. But the None-1 video device still persists and xrandr still shows that device is being used by Xorg!!!

I am unable to configure Xorg to ignore (and stop using as its default) the None-1 video device causing me not to be able to display a desktop via the HMDI-1-1 device. It has been suggested (https://ubuntu-mate.community/t/how-to-configure-xorg/26732/3) that I disable this device in the kernel, hopefully, via a kernel option such as : video=None-1:d Does anyone know where (which file) and how (specific method) I should do this?

Armbian 23.5 Ubuntu Not sure what I touched but my OpenGL has reverted from the Mali-G52 hardware accelerated renderer back to the llvmpipe. How can I changed this?

I have multiple n2s and I don't want them all to be called odroidn2. What is the recommended way to change the hostname of an armbian system?

I noticed this on the download page for the Odroid N2/N2+: On modern kernels adding “video=HDMI-A-1:1920x1080M@60D” to boot /boot/armbianEnv.txt (extraargs=) should force HDMI to 1080p instead of the 4K native resolution. I'll check if that will also works with 2560x1440 monitors!

@Dantes Thanks I took a look at your script. I don't think it will address my QHD resolution at boot issue! Good work, 👍

I managed to get it going! I suspected it was working so unplugged the HDMI cable from my QHD monitor and plugged it into a FHD and wala instant picture. Then I plugged it back into my QHD monitor and it was still displaying. I then used the display control to set the resolution to 2560x1440 and it still worked. So the problem seems to be using QHD from boot. That doesn't work. Seems like a firmware setting that should be changed. I suspect it doesn't see a FHD single so assumes a 4K monitor instead.

Thanks I went into armbian-config but can't see any setting that would be relevant as GUI is already set to enabled! I tried disabling and re-enabling but no difference. Blank screen!

I'm using the Odroid N2/N2+ 23.5 Jammy minimal image. I then updated and upgraded successfully. I then attempted to install MATE via tasksel (which I installed) but that immediate fails with an apt package missing error. SO then I tried to install MATE manually by: $ sudo apt install mate-desktop-environment mate-desktop-environement-extras $ reboot There didn't seem to be any display manger installed so I stalled lighdm $ sudo apt install lightdm lighdm-gtk-greeter $ reboot Then I noticed that Xserver was not installed (really, that's no a MATE dependency!!!) $ sudo aqt install xserver-xorg $ reboot But the xserver was not starting and so I noticed xinit was not installed (really. why wouldn't this be a dependency of MATE or the xserver) $ sudo apt install xinit $ reboot Now it boots and starts everything and then switches to console tty07 but is just a black screen. I can see from console tty01 that all the correct (I assume) processes have started but nothing but a black screen. Xorg is running lightdm session is running lightdm-greeter-session is running lightdm-gtk-greeter is running But still no login screen (or mouse) is visible (just a blank screen) I can see the ~/.Xauthority file is blank so don't know what has happened. What else have I missed?

I suspect something is missing from the Armbian meson hardware/firmware, because if I boot two copies of Ubuntu then the KVM appears to operate correctly and if I boot two copies of Armbian I see neither system.

Hi have two N2s (an N2+ and N2). Both are connected to a Viewsonic 2560x1440 2 HDMI ports monitor where they both work well. One system (N2+) is running Ubuntu 22.04 the other is running Armbian jammy 22.04.01 Kernel 6.0.13 #22.11.2. I have purchased a ATEN CS22H 2 port HDMI/USB KIVM switch. When I connect both systems to the monitor via the KVM I only get a picture from the Ubuntu system. The Armbian system is always black. Can I force the kernel/firmware to be 2560x1440x60hz. I was looking at this post : Regarding forcing the kernel to be a fixed resolution but wasn't sure it was relevant. I am able to connect to the Artmbian system via ssh if I need to. Any suggestions welcome!

Using a Realtek 8821CU Bluetooth + Wifi USB adapter. Working fine on stable build jammy with kernel 5.10.123. (current) Using the Armbian->Config->System->Other and selecting the latest 5.15 kernel. System reboots and confirm kernel has been updated and chosen. Wifi hotspots are all seen but fails to connect and repeatedly asks for password. Security is WAP2 personal. Setting the kernel back to 5.10.current reverts to Wifi working as expected. I will try the 5.17 kernel and report back. I have seen this before on other Deb distros. From memory this is caused by a missing/outdated kernel encryption module or wpa_supplicant. However don't quote me. It was quite some time ago.