habe hier ein älteres System auf Debian 11 aktualisiert. Jetzt erreicht er beim Booten das Prompt nicht mehr und startet auch kein X.
SSH etc ist alles gestarted. Von da kann ich auch gdm3 manuell starten.
# gdm3 &
Ich bin leider noch nicht besonders firm mit systemd.
Die Ausgabe sieht für mich aus, als seien 2 Dinge nicht aktiviert? Wie mache ich die an:
Code: Alles auswählen
boark:(/var/log)# systemctl list-units --type target
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
blockdev@dev-mapper-md2open.target loaded active active Block Device Preparation for /dev/mapper/md2open
blockdev@dev-mapper-md3open.target loaded active active Block Device Preparation for /dev/mapper/md3open
cryptsetup.target loaded active active Local Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded inactive dead start Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded inactive dead start Multi-User System
network-online.target loaded active active Network is Online
network.target loaded active active Network
nss-user-lookup.target loaded active active User and Group Name Lookups
paths.target loaded active active Paths
remote-fs.target loaded active active Remote File Systems
slices.target loaded active active Slices
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
timers.target loaded active active Timers
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
20 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
boark:(/var/log)# systemctl is-enabled multi-user.target.service
enabled
Failed to get unit file state for multi-user.target.service: No such file or directory
-bash: enabled: Kommando nicht gefunden.
Code: Alles auswählen
systemctl enable gdm3
Synchronizing state of gdm3.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable gdm3
insserv: script virtualbox: service vboxdrv already provided!
insserv: script virtualbox: service virtualbox already provided!
insserv: script virtualbox: service vboxdrv already provided!
insserv: script virtualbox: service virtualbox already provided!
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
boark:(/var/log)# systemctl start gdm3
multi-user.target loaded inactive dead start Multi-User System
graphical.target loaded inactive dead start Graphical Interface
Danke, xcomm