Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Fresh installation do not boot to the desktop (Read 764 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Fresh installation do not boot to the desktop

Hello guys,

For weeks I have had the problem that fresh installations do not boot to the desktop after a first reboot.
It doesn't matter whether I use one of the stable ISO images or one of the weekly ISO images.
Each time the system boots to the login prompt and then it stops.
I always use the offline mode for installation.

The only thing they have in common is that I use runit as the init system.

Does anyone have an idea or a tip as to why this could be?

Thanks in advance for all of your answers.

regards
roberto

Re: Fresh installation do not boot to the desktop

Reply #1 –
Which ISOs specifically? Qt ones use sddm, Gtk ones lightdm. What does /var/log/Xorg.0.log say?

Re: Fresh installation do not boot to the desktop

Reply #2 –
I tried plasma 5 stable runit (artix-plasma-runit-20230814-x86_64.iso) then xfce weekly ISO (artix-xfce-runit-20240517-x86_64.iso) and finally cinnamon runit (artix-cinnamon-runit-20240520-x86_64.iso).

With all three with the same result.

Re: Fresh installation do not boot to the desktop

Reply #3 –
Wild guess based on the complete lack of any details about the hardware:

You have an old GPU which isn't supported by the current driver ?

Re: Fresh installation do not boot to the desktop

Reply #4 –
Sorry, here is my configuration:

Code: [Select]
[roberto@Elitebook ~]$ inxi -F 
System: 
 Host: Elitebook Kernel: 6.6.32_1 arch: x86_64 bits: 64 
 Desktop: KDE Plasma v: 6.0.4 Distro: Void Linux 
Machine: 
 Type: Laptop System: HP product: HP EliteBook 640 14 inch G9 Notebook PC 
   v: N/A serial: <superuser required> 
 Mobo: HP model: 8AA6 v: KBC Version 21.09.50 serial: <superuser required> 
   UEFI: HP v: U86 Ver. 01.04.02 date: 11/23/2022 
Battery: 
 ID-1: BAT0 charge: 22.8 Wh (47.2%) condition: 48.3/51.3 Wh (94.2%) 
   volts: 11.8 min: 11.6 
CPU: 
 Info: 10-core (2-mt/8-st) model: 12th Gen Intel Core i5-1235U bits: 64 
   type: MST AMCP cache: L2: 6.5 MiB 
 Speed (MHz): avg: 1549 min/max: 400/4400:3300 cores: 1: 3200 2: 3200 
   3: 3200 4: 400 5: 400 6: 1872 7: 400 8: 2378 9: 2343 10: 400 11: 400 12: 400 
Graphics: 
 Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics] driver: i915 v: kernel 
 Device-2: Luxvisions Innotech HP HD Camera driver: uvcvideo type: USB 
 Display: wayland server: X.Org v: 23.2.4 with: Xwayland v: 23.2.4 
   compositor: kwin_wayland driver: X: loaded: intel 
   unloaded: fbdev,modesetting,vesa dri: i965 gpu: i915 
   resolution: 1920x1080~60Hz 
 API: EGL v: 1.5 drivers: N/A platforms: gbm,wayland,x11 
 API: OpenGL v: 4.6 vendor: intel mesa v: 24.0.7 renderer: Mesa Intel 
   Graphics (ADL GT2) 
Audio: 
 Device-1: Intel Alder Lake PCH-P High Definition Audio 
   driver: sof-audio-pci-intel-tgl 
 API: ALSA v: k6.6.32_1 status: kernel-api 
 Server-1: PulseAudio v: 16.1 status: active 
Network: 
 Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi 
 IF: wlp0s20f3 state: up mac: a0:29:42:e5:73:6a 
 Device-2: Intel Ethernet I219-V driver: e1000e 
 IF: enp0s31f6 state: down mac: 7c:4d:8f:07:6a:77 
 IF-ID-1: virbr0 state: up speed: 10000 Mbps duplex: unknown 
   mac: 52:54:00:ba:03:9d 
 IF-ID-2: vnet0 state: unknown speed: 10000 Mbps duplex: full 
   mac: fe:54:00:b9:dd:7b 
Bluetooth: 
 Device-1: Intel driver: btusb type: USB 
 Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: not found 
   rfk-block: hardware: no software: no address: see --recommends 
Drives: 
 Local Storage: total: 238.47 GiB used: 11.14 GiB (4.7%) 
 ID-1: /dev/nvme0n1 vendor: KIOXIA model: N/A size: 238.47 GiB 
Partition: 
 ID-1: / size: 97.87 GiB used: 10.89 GiB (11.1%) fs: ext4 dev: /dev/nvme0n1p3 
 ID-2: /boot/efi size: 511 MiB used: 144 KiB (0.0%) fs: vfat 
   dev: /dev/nvme0n1p1 
 ID-3: /home size: 126.87 GiB used: 252.2 MiB (0.2%) fs: ext4 
   dev: /dev/nvme0n1p4 
Swap: 
 ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) 
   dev: /dev/nvme0n1p2 
Sensors: 
 Src: /sys System Temperatures: cpu: 69.0 C mobo: N/A 
 Fan Speeds (rpm): N/A 
Info: 
 Memory: total: 16 GiB note: est. available: 15.26 GiB used: 8.84 GiB (57.9%) 
 Processes: 307 Uptime: 1h 53m Shell: Bash inxi: 3.3.34

At the moment I have installed Void Linux because the Artix installation is not working.
But I would like to switch.

Re: Fresh installation do not boot to the desktop

Reply #6 –
I will try a fresh installation and then I check the log file.

First of all thanks for your help  :)

Re: Fresh installation do not boot to the desktop

Reply #7 –
I have tested a fresh installation on various notebooks, most recently on a Lenovo T450s. I have the same problem on all devices, the boot process stops at the login line.
I have taken screenshots of the last installation.

Does anyone have any idea what I am doing wrong?

 

Re: Fresh installation do not boot to the desktop

Reply #8 –
I am a big step further and I have the impression that it is related to runit as init-system.

I installed the stable openrc version of Plasma 5 (artix-plasma-openrc-20230814-x86_64) on the T450s last night.
After the installation my notebook booted without any problems and I was able to install all updates.
Since then the system runs like a machine.

Is it possible that this is the reason?
I mean, no runit version booted to the desktop after the installation.

In any case, I will switch to openrc.

Thanks to everyone who took care of my problem.

Best regards
Roberto

Re: [SOLVED] Fresh installation do not boot to the desktop

Reply #9 –
Quote from: Roberto – on
Does anyone have any idea what I am doing wrong?

"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "

Re: [SOLVED] Fresh installation do not boot to the desktop

Reply #10 –
Quote from: Roberto – on
I am a big step further and I have the impression that it is related to runit as init-system.

Wrong, nothing has changed in runit.
After installation, restart and login is sufficient:

Code: [Select]
ln -s /etc/runit/sv/ntpd /etc/runit/runsvdir/default
ln -s /etc/runit/sv/dhcpcd /etc/runit/runsvdir/default
ln -s /etc/runit/sv/lightdm /etc/runit/runsvdir/default
"Wer alles kann, macht nichts richtig"

Artix USE="runit openrc slim openbox lxde gtk2 qt4 qt5 qt6 conky
-gtk3 -gtk4 -adwaita{cursors,themes,icons} -gnome3 -kde -plasma -wayland "