Setup Fails on Trixie

[TerrorPUP]

Hi, 

I've tried to setup the latest Debian 13 (Trixie) for the Renegade board. I can flash the image with no issue. The problem comes it boots up, prompts for root password. I can type in then press enter, and then it goes to login. This only happens on the Debian 13 (Trixie).  I am using the Debian 12 XFCE imange no issue. 

I am not sure if this is a bug or what, but I loved to use Debian 13, I am trying to setup Docker with the latest OS. 

[laibsch]

Are you saying you are missing further steps in between setting root passwd and being logged in?

[TerrorPUP]

I type the root password once, press enter to retype it, but it jumps straight to the login prompt. Do not pass Go, do not collect $200. I’ve been dealing with this for the past month. At first, I thought it was just my 2GB model acting weird, but today I had two 4GB units do the same thing.

It only happens with the Debian 13 Minimal/IOT image. I didn't want the overhead, but I am using the Debian 12/XFCE Desktop image that works. 

[laibsch]

Can you run a uefi-x86 image in a VM and see if you can reproduce the behaviour?  I doubt this is specific to your board but an error somewhere else.

[TerrorPUP]

Yes, give me a couple days as I am in the middle of project. 

[eselarm]

11 hours ago, TerrorPUP said:

It only happens with the Debian 13 Minimal/IOT image. I didn't want the overhead, but I am using the Debian 12/XFCE Desktop image that works. 

You can remove Xfce from an installation, via apt purge --autoremove options, may just by un-ticking it in tasksel, and systemctl set-default multi-user.target

Done that kind of trick to get rid of RPi PiXel DE in the past when they had no -Lite images and/or I wanted to keep my rootfs while upgrading in-place to newer Debian main release. Same Actuallt recently for ROCK3A Armbian Bookworm cloned from NanoPi-R6C to Armbian Trixie just headless/CLI.

My last run/config of a Armbian 25.11.1 image was with autologin root and doing 1st run config, the usual I know from Armbian. So the image you use is wrongly generated maybe, but the big question mark is what image?

URL+sha256sum enables others to check/confirm without guessing and maybe picking a newer/different 'latest' image or so, else DIY.