Comments

2 Comments
karma

Generally works fine.

Too bad the drm/vmwgfx fixes for their previous changes merged as part of 6.10.4 don't seem to be fixing non-working graphics for me :/ Thus leaving me still on 6.10.3 for my local virtual machine usage.

I guess it's time to attempt to build my own kernel with some additional DRM/vmware surface format logging to see what the mode and DRM surface types are...

kernel: Linux version 6.10.8-200.fc40.x86_64 (mockbuild@81267993c0ea4676bef76f8dd2b2ffea) (gcc (GCC) 14.2.1 20240801 (Red Hat 14.2.1-1), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Wed Sep  4 21:41:11 UTC 2024
kernel: vmwgfx 0000:00:0f.0: vgaarb: deactivate vga console
kernel: vmwgfx 0000:00:0f.0: [drm] FIFO at 0x00000000fb800000 size is 8192 KiB
kernel: vmwgfx 0000:00:0f.0: [drm] VRAM at 0x00000000f0000000 size is 131072 KiB
kernel: vmwgfx 0000:00:0f.0: [drm] Running on SVGA version 2.
kernel: vmwgfx 0000:00:0f.0: [drm] Capabilities: rect copy, cursor, cursor bypass, cursor bypass 2, 8bit emulation, alpha cursor, 3D, extended fifo, multimon, pitchlock, irq mask, display topology, gmr, traces, gmr2, screen object 2, command buffers, command buffers 2, gbobject,
kernel: vmwgfx 0000:00:0f.0: [drm] DMA map mode: Caching DMA mappings.
kernel: vmwgfx 0000:00:0f.0: [drm] Legacy memory limits: VRAM = 4096 KiB, FIFO = 256 KiB, surface = 0 KiB
kernel: vmwgfx 0000:00:0f.0: [drm] MOB limits: max mob size = 131072 KiB, max mob pages = 196608
kernel: vmwgfx 0000:00:0f.0: [drm] Max GMR ids is 64
kernel: vmwgfx 0000:00:0f.0: [drm] Max number of GMR pages is 65536
kernel: vmwgfx 0000:00:0f.0: [drm] Maximum display memory size is 131072 KiB
kernel: vmwgfx 0000:00:0f.0: [drm] Screen Target display unit initialized
kernel: vmwgfx 0000:00:0f.0: [drm] Fifo max 0x00040000 min 0x00001000 cap 0x0000077f
kernel: vmwgfx 0000:00:0f.0: [drm] Using command buffers with DMA pool.
kernel: vmwgfx 0000:00:0f.0: [drm] Available shader model: Legacy.
kernel: [drm] Initialized vmwgfx 2.20.0 20211206 for 0000:00:0f.0 on minor 0
kernel: fbcon: vmwgfxdrmfb (fb0) is primary device
kernel: fbcon: Deferring console take-over
kernel: vmwgfx 0000:00:0f.0: [drm] fb0: vmwgfxdrmfb frame buffer device
kernel: [drm:vmw_kms_new_framebuffer [vmwgfx]] *ERROR* Invalid surface format for requested mode.
kernel: [drm:vmw_kms_fb_create [vmwgfx]] *ERROR* failed to create vmw_framebuffer: -22

That might happen to users, who didn't change their passwords since 2007 or so, as libxcrypt now reports the use of very unsafe hash methods to PAM.

That is interesting, since this happened with a ~2016 server install, which has been slowly upgraded as time went by. Specifically this was with the 4.4.21 version

    Upgrade       libxcrypt-4.4.21-1.fc34.x86_64                      @updates-testing
    Upgraded      libxcrypt-4.4.20-2.fc34.x86_64                      @@System
    Upgrade       libxcrypt-compat-4.4.21-1.fc34.x86_64               @updates-testing
    Upgraded      libxcrypt-compat-4.4.20-2.fc34.x86_64               @@System

Afterwards, at every login prompt it would just prompt me to change my password. The first time it popped back up it was weird, but I went along with it. It logged me out and I attempted to log in again. I hit the same thing, and at this point I decided it was in a loop. Thankfully I had some free time now to utilize a recovery image and chroot into my actual sysroot, and downgrade back to 4.4.20.

Excerpts from journal:

  1. Initial login, password change:
May 27 20:07:02 das-hostname systemd[1]: Starting User Manager for UID USER_ID...
May 27 20:07:02 das-hostname systemd[695]: pam_unix(systemd-user:account): expired password for user das_user (root enforced)
May 27 20:07:02 das-hostname systemd[695]: PAM failed: Authentication token is no longer valid; new one required
May 27 20:07:02 das-hostname systemd[695]: user@USER_ID.service: Failed to set up PAM session: Operation not permitted
May 27 20:07:02 das-hostname systemd[695]: user@USER_ID.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
May 27 20:07:02 das-hostname systemd[1]: user@USER_ID.service: Main process exited, code=exited, status=224/PAM
May 27 20:07:02 das-hostname systemd[1]: user@USER_ID.service: Failed with result 'exit-code'.
May 27 20:07:02 das-hostname systemd[1]: Failed to start User Manager for UID USER_ID.
May 27 20:07:02 das-hostname systemd[1]: Started Session 1 of user das_user.
May 27 20:07:02 das-hostname sshd[692]: pam_unix(sshd:session): session opened for user das_user(uid=USER_ID) by (uid=0)

May 27 20:17:28 das-hostname passwd[697]: pam_unix(passwd:chauthtok): password changed for das_user
  1. Second attempt
May 27 20:17:31 das-hostname systemd[1]: Starting User Manager for UID USER_ID...
May 27 20:17:31 das-hostname systemd[709]: pam_unix(systemd-user:account): expired password for user das_user (root enforced)
May 27 20:17:31 das-hostname systemd[709]: PAM failed: Authentication token is no longer valid; new one required
May 27 20:17:31 das-hostname systemd[709]: user@USER_ID.service: Failed to set up PAM session: Operation not permitted
May 27 20:17:31 das-hostname systemd[709]: user@USER_ID.service: Failed at step PAM spawning /usr/lib/systemd/systemd: Operation not permitted
May 27 20:17:31 das-hostname systemd[1]: user@USER_ID.service: Main process exited, code=exited, status=224/PAM
May 27 20:17:31 das-hostname systemd[1]: user@USER_ID.service: Failed with result 'exit-code'.
May 27 20:17:31 das-hostname systemd[1]: Failed to start User Manager for UID USER_ID.
May 27 20:17:31 das-hostname systemd[1]: Started Session 2 of user das_user.
May 27 20:17:31 das-hostname sshd[706]: pam_unix(sshd:session): session opened for user das_user(uid=USER_ID) by (uid=0)

I have not tested 4.4.22 yet, if that improves things. Additionally, are there any hints in f.ex. password -S das_user which would give a hint to the user that they would be hitting issues?