Yes exactly.On Thu, Dec 01, 2022 at 07:25:24PM +0100, jd wrote:On 2022-12-01 19:05, Tim Woodall wrote:On Thu, 1 Dec 2022, jd wrote:On 2022-11-30 18:52, Hans wrote:Am Mittwoch, 30. November 2022, 18:33:49 CET schrieb jd: Try to deinstall cups and remove any usb cameras. I had had the problem, that cups detected an usb camera as a printer and then stopped booting.I tried removing all cups packages, then it just stalled at Unattended upgrades shutdown instead. So I tried disabling that, and now it stalls at Hostname Service.is it stalled or just taking a very long time? DNS timing out can sometimes cause issues like this.That depends on how long it can get stuck due to DNS issues, I've left it for several hours and it's still stuck in the same place. If it was a DNS issue it should have gotten somewhere after several hours no?But when you say "stuck", what you really mean is "I never get a login prompt on tty1". But you *are* getting login prompts on other TTYs, right?
Which installation image did you use,
https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.5.0-amd64-netinst.iso
and how deeply have you investigated the systemd getty/console startup stuff?
Not very, I wouldn't really know how.
As it turns out I didn't need to but for future use, do you have
any tips on where one might find documentation about how agetty
interacts with the rest of the debian startup process? I've
searched but the results have been scant.
The problem is now solved, but unsatisfactorily I still don't know what the problem was or exactly what solved it.
Anyhow what I did was to reinstall in bios-mode instead of uefi mode. After that the problem remained but to my surprise startx now worked, which it didn't before. After that I installed a bunch of packages that I usually do after a fresh install, one of which was lightdm, and all of a sudden everything works and the problem is gone.
Thanks to everyone for all the help and suggestions along the
way.
cheers
jd