akulbe
(Aaron Kulbe)
March 5, 2025, 10:35pm
1
I am running the F41 i3 Spin.
I’m running it as a VM on Proxmox. (Using “Standard VGA” as the display) There is an RTX 3060 in the host, but there’s no passthrough configured in this case.
00:01.0 VGA compatible controller: Device 1234:1111 (rev 02)
After some period of inactivity, the desktop goes dark.
My assumption is that it’s going into suspend mode. I wasn’t sure how exactly to disable suspend mode on a fresh F41-i3-Spin install.
Cursory research made me think that logind.conf
was where it’d end up getting done.
These were the mods I made:
akulbe@tiny:~$ grep -v ^# /etc/logind.conf
[Login]
HandleSuspendKey=ignore
HandleSuspendKeyLongPress=ignore
HandleHibernateKey=ignore
HandleHibernateKeyLongPress=ignore
HandleLidSwitch=ignore
HandleLidSwitchExternalPower=ignore
IdleAction=ignore
and it didn’t change the results any.
The weird thing is that I am still able to SSH in to the system, and interact with it.
In order to interact with the desktop, I have to reboot the machine from the SSH session, then I’m able to log in via the LightDM greeter. But once the idle time is passed, whatever that really is, game over. The screen goes black, and I’m back to needing to reboot the VM.
Is there anything obvious I might be missing? Is there any other data I can provide to be helpful?
Thanks in advance!
Aaron Kulbe
Look at the system logs for errors.
I would guess you need to configure proxmon to provide enough virtual GPU for the desktop to run.
Edit: please install sudo dnf install inxi
and post the output of inxi -Fzxx
.
That will tell us a lot about how the VM is setup.
akulbe
(Aaron Kulbe)
March 6, 2025, 2:21pm
3
Hey @barryascott , thanks for the reply. Here’s the inxi
output
System:
Kernel: 6.13.5-200.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
Console: pty pts/1 DM: LightDM Distro: Fedora Linux 41 (Forty One)
Machine:
Type: Kvm System: QEMU product: Standard PC (Q35 + ICH9, 2009) v: pc-q35-9.0
serial: <superuser required> Chassis: type: 1 v: pc-q35-9.0 serial: <superuser required>
Mobo: N/A model: N/A serial: N/A UEFI: Proxmox distribution of EDK II v: 4.2023.08-4
date: 02/15/2024
CPU:
Info: 2x 1-core model: QEMU Virtual version 2.5+ bits: 64 type: SMP arch: K8 rev: 1 cache:
L1: 2x 128 KiB (256 KiB) L2: 2x 512 KiB (1024 KiB) L3: 2x 16 MiB (32 MiB)
Speed (MHz): avg: 3992 min/max: N/A cores: 1: 3992 2: 3992 bogomips: 15970
Flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Graphics:
Device-1: vendor: Red Hat driver: bochs-drm v: N/A ports: active: Virtual-1 empty: none
bus-ID: 00:01.0 chip-ID: 1234:1111
Display: unspecified server: X.org v: 1.21.1.16 driver: X: loaded: modesetting
alternate: fbdev,vesa gpu: bochs-drm tty: 118x91
Monitor-1: Virtual-1 model: QEMU Monitor res: 1280x800 dpi: 100 diag: 383mm (15.1")
API: OpenGL Message: GL data unavailable in console. Try -G --display
Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel 82801I HD Audio vendor: Red Hat QEMU Virtual Machine driver: snd_hda_intel
v: kernel bus-ID: 00:1b.0 chip-ID: 8086:293e
API: ALSA v: k6.13.5-200.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse status: off 2: wireplumber
status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
Network:
Device-1: Red Hat Virtio network driver: virtio-pci v: 1 port: 7080 bus-ID: 06:12.0
chip-ID: 1af4:1000
IF: enp6s18 state: up speed: -1 duplex: unknown mac: <filter>
Drives:
Local Storage: total: 100 GiB used: 7.21 GiB (7.2%)
ID-1: /dev/sda vendor: QEMU model: HARDDISK size: 100 GiB speed: <unknown> serial: <filter>
Partition:
ID-1: / size: 98.41 GiB used: 6.86 GiB (7.0%) fs: btrfs dev: /dev/sda3
ID-2: /boot size: 973.4 MiB used: 345 MiB (35.4%) fs: ext4 dev: /dev/sda2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat dev: /dev/sda1
ID-4: /home size: 98.41 GiB used: 6.86 GiB (7.0%) fs: btrfs dev: /dev/sda3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:
Src: lm-sensors+/sys Message: No sensor data found using /sys/class/hwmon or lm-sensors.
Info:
Memory: total: 32 GiB available: 31.3 GiB used: 1.06 GiB (3.4%)
Processes: 408 Power: uptime: 14h 35m wakeups: 0 Init: systemd v: 256 target: graphical (5)
default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.32
running-in: pty pts/1 inxi: 3.3.37
Aaron Kulbe:
bochs-drm
You would need to find out if the gpu is supported by light dm.
I don’t know the answer.
akulbe
(Aaron Kulbe)
March 8, 2025, 12:59am
5
Is there a correlation between the drivers a DM uses an whether it’ll work, or not?
Because bochs-drm
works fine on Fedora Workstation 41 with GDM, I can log in and the desktop remains available. So shouldn’t it work with LightDM on i3 too?
akulbe
(Aaron Kulbe)
March 8, 2025, 6:00am
6
Actually, I think I figured out what is happening, but not why it’s happening.
LightDM is stopping for some reason. If I restart it, the desktop comes back.
I created a gist from the journal, but I’m not sure why it’s stopping. I’m not sure if the “gkr-pam” entries are relevant, or not.
Each GUI app may use different GPU API features and may have different bugs as a result. One working DM does not mean all DM will work.
I would report this to the lightdm maintainers.