View Issue Details

IDProjectCategoryView StatusLast Update
0007892Kali Linux[All Projects] Kali Package Bugpublic2022-12-23 07:33
ReporterEtan Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version2022.3 
Target VersionFixed in Version 
Summary0007892: Kali 2022.3 GUI not compatible with Hyper-V 2022 bare metal
DescriptionWhen booting a new 2022.3 installation OR an updated previous version with the 5.18 kernel, lightdm will not run. This appears to be Hyper-V only. It works fine in VirtualBox. This happens even if kali-tweaks Hyper-V enhanced is installed. Work around is to use 5.16 kernel.
Steps To ReproduceInstall 2022.3 or update a previous version (my testing used 2022.2), lightdm does not run. One gets a blinking cursor in the upper left corner. One is still able to ALT + Fn a TTY, but GUI will not start. Neither executing "lightdm" or "startx" works. Error message attached.

If when starting one chooses the 5.16 kernel instead, the GUI runs fine. It appears to be a difference between 5.16 and 5.18.

Activities

Etan

2022-08-26 01:39

reporter  

Capture2.PNG (54,664 bytes)
Capture2.PNG (54,664 bytes)
Capture1.PNG (134,686 bytes)
Capture1.PNG (134,686 bytes)

steev

2022-08-26 19:59

manager   ~0016653

Can you give the dmesg and lsmod output please?

Also, can you show the lightdm logs as well? They should be in /var/log/lightdm/

Etan

2022-08-27 20:11

reporter   ~0016665

Attached. Let me know if you need anything else.

lsmod.log (2,587 bytes)
lightdm.log (2,925 bytes)
dmesg.log (38,263 bytes)

steev

2022-08-27 20:38

manager   ~0016666

Can you also attach the xorg log file from the lightdm folder?

Etan

2022-08-29 03:14

reporter   ~0016668

Attached

Xorg.0.log (6,527 bytes)

Etan

2022-08-29 03:15

reporter   ~0016669

This one also.

x-0.log (1,242 bytes)

steev

2022-08-29 14:21

manager   ~0016672

Okay, can you also boot into 5.16 and attach the same Xorg log files?

Etan

2022-08-29 15:14

reporter   ~0016673

Attached

x-0-2.log (867 bytes)
Xorg.0-2.log (16,243 bytes)

steev

2022-08-29 17:43

manager   ~0016675

Last edited: 2022-08-29 20:13

View 3 revisions

Okay, so it looks like with 5.16, it falls back to fbdev for the driver for Xorg; Can you add an xorg snippet in /etc/X11/xorg.conf.d/10-fbdev.conf (create the directory as it likely won't exist)

with

Section "Device"
    Identifier "FBDEV"
    Driver "fbdev"
    Option "fbdev" "/dev/fb0"
# Option "ShadowFB" "false"
EndSection

in it? You may need to adjust the fbX device.

(Edited to remove the un-needed not-blanking config bits)

Etan

2022-09-05 21:40

reporter   ~0016702

THAT WORKS!!!!!! THANK YOU!!!!!

steev

2022-12-23 07:33

manager   ~0017278

Hey Etan,

I have a question - what generation is your Hyper-V VM? Is it set to Gen1 or Gen2? (I do not know where to actually find this in the settings, but I'm sure it should say it somewhere in there)

Issue History

Date Modified Username Field Change
2022-08-26 01:39 Etan New Issue
2022-08-26 01:39 Etan File Added: Capture2.PNG
2022-08-26 01:39 Etan File Added: Capture1.PNG
2022-08-26 19:59 steev Note Added: 0016653
2022-08-27 20:11 Etan File Added: lsmod.log
2022-08-27 20:11 Etan File Added: lightdm.log
2022-08-27 20:11 Etan File Added: dmesg.log
2022-08-27 20:11 Etan Note Added: 0016665
2022-08-27 20:38 steev Note Added: 0016666
2022-08-29 03:14 Etan File Added: Xorg.0.log
2022-08-29 03:14 Etan Note Added: 0016668
2022-08-29 03:15 Etan File Added: x-0.log
2022-08-29 03:15 Etan Note Added: 0016669
2022-08-29 14:21 steev Note Added: 0016672
2022-08-29 15:14 Etan File Added: x-0-2.log
2022-08-29 15:14 Etan File Added: Xorg.0-2.log
2022-08-29 15:14 Etan Note Added: 0016673
2022-08-29 17:43 steev Note Added: 0016675
2022-08-29 17:44 steev Note Edited: 0016675 View Revisions
2022-08-29 20:13 steev Note Edited: 0016675 View Revisions
2022-09-05 21:40 Etan Note Added: 0016702
2022-12-23 07:33 steev Note Added: 0017278