View previous topic :: View next topic |
Author |
Message |
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Fri Mar 08, 2024 5:59 pm Post subject: SOLVED Unable to login after activate KVM support in kernel |
|
|
Hello All,
I trying to install QEMU/KVM on my Gentoo, so before installation I follow this wiki "https://wiki.gentoo.org/wiki/QEMU" to prepare the kernel when I activate this 2 modules below in kernel, after boot I can't to login to my desktop nor access to the system with console, to fix this problem I must to rollback on the previous kernel.
Code: | *] Virtualization --->
<*> Kernel-based Virtual Machine (KVM) support
<M> KVM for Intel processors support |
I have an Intel Core i7 vpro sixth generation, on my bios virtualization and GVT parameter are activated.
Do you have any idea what could be wrong ?
Any help will be appreciate.
Thank you for your help.
SmokyRun
Last edited by smokyrun on Tue Mar 12, 2024 6:09 pm; edited 1 time in total |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21849
|
Posted: Fri Mar 08, 2024 6:56 pm Post subject: |
|
|
KVM support should not be able to cause this problem. What processes become uncooperative when running a KVM-enabled kernel? What errors do they log? |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Fri Mar 08, 2024 7:50 pm Post subject: |
|
|
When I look at in messages logfile the last message write before shutdown is by elogind :
Code: | Mar 8 21:13:16 himalaya kernel: RSP: 002b:00007ffdcb1d44c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Mar 8 21:13:16 himalaya kernel: RAX: ffffffffffffffda RBX: 0000000000000020 RCX: 00007f41004c6f1b
Mar 8 21:13:16 himalaya kernel: RDX: 00007ffdcb1d4600 RSI: 00000000c020462b RDI: 0000000000000009
Mar 8 21:13:16 himalaya kernel: RBP: 00007ffdcb1d4570 R08: 00007ffdcb1d4600 R09: 00007ffdcb1d461c
Mar 8 21:13:16 himalaya kernel: R10: 00007ffdcb1e2248 R11: 0000000000000246 R12: 00007ffdcb1d4600
Mar 8 21:13:16 himalaya kernel: R13: 0000000000000009 R14: 00000000c020462b R15: 000000000000002b
Mar 8 21:13:16 himalaya kernel: </TASK>
Mar 8 21:13:33 himalaya kernel: elogind-daemon[1495]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Mar 8 21:13:33 himalaya shutdown[3706]: shutting down for system halt |
|
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 1713
|
Posted: Fri Mar 08, 2024 8:30 pm Post subject: |
|
|
smokyrun wrote: | When I look at in messages logfile the last message write before shutdown is by elogind :
Code: | Mar 8 21:13:16 himalaya kernel: RSP: 002b:00007ffdcb1d44c0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Mar 8 21:13:16 himalaya kernel: RAX: ffffffffffffffda RBX: 0000000000000020 RCX: 00007f41004c6f1b
Mar 8 21:13:16 himalaya kernel: RDX: 00007ffdcb1d4600 RSI: 00000000c020462b RDI: 0000000000000009
Mar 8 21:13:16 himalaya kernel: RBP: 00007ffdcb1d4570 R08: 00007ffdcb1d4600 R09: 00007ffdcb1d461c
Mar 8 21:13:16 himalaya kernel: R10: 00007ffdcb1e2248 R11: 0000000000000246 R12: 00007ffdcb1d4600
Mar 8 21:13:16 himalaya kernel: R13: 0000000000000009 R14: 00000000c020462b R15: 000000000000002b
Mar 8 21:13:16 himalaya kernel: </TASK>
Mar 8 21:13:33 himalaya kernel: elogind-daemon[1495]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Mar 8 21:13:33 himalaya shutdown[3706]: shutting down for system halt |
|
The memfd_create bits are a red herring aimed at developers to improve their code. What would be really interesting is additional context if possible (before what is listed here). |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sat Mar 09, 2024 4:29 am Post subject: |
|
|
When I look generated messages during the boot system messages log are OK
https://pastebin.com/LgweUWmu
I don't know why I can't login across desktop and why I can't run any system console when I activate KVM kernel module.
Thank you for your help. |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 21849
|
Posted: Sat Mar 09, 2024 3:47 pm Post subject: |
|
|
That output looks to me like the proprietary nVidia drivers did something that caused a warning. Does this work if you direct the kernel not to load the proprietary nVidia drivers? |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Sat Mar 09, 2024 7:22 pm Post subject: |
|
|
smokyrun wrote: | When I look generated messages during the boot system messages log are OK
https://pastebin.com/LgweUWmu
I don't know why I can't login across desktop and why I can't run any system console when I activate KVM kernel module.
Thank you for your help. |
What do you mean by login across desktop? How do you try to run system console?
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sat Mar 09, 2024 7:30 pm Post subject: |
|
|
In fact any Nvidia drivers is loaded from kernel because I have an hybrid graphic card whose primary is an Intel card, only this one is loaded from the kernel.
In the messages log I found this message :
Mar 9 17:54:52 himalaya kernel: RSP: 002b:00007ffe077e9010 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Mar 9 17:54:52 himalaya kernel: RAX: ffffffffffffffda RBX: 0000000000000020 RCX: 00007f72bd020f1b
Mar 9 17:54:52 himalaya kernel: RDX: 00007ffe077e9150 RSI: 00000000c020462b RDI: 0000000000000009
Mar 9 17:54:52 himalaya kernel: RBP: 00007ffe077e90c0 R08: 00007ffe077e9150 R09: 00007ffe077e916c
Mar 9 17:54:52 himalaya kernel: R10: 00007ffe077f0248 R11: 0000000000000246 R12: 00007ffe077e9150
Mar 9 17:54:52 himalaya kernel: R13: 0000000000000009 R14: 00000000c020462b R15: 000000000000002b
Mar 9 17:54:52 himalaya kernel: </TASK>
Mar 9 17:54:52 himalaya kernel: INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 3.301 msecs
Mar 9 17:55:30 himalaya kernel: elogind-daemon[1518]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
Mar 9 17:55:30 himalaya shutdown[3706]: shutting down for system halt
I don't know if it's important
Thank you for your help. |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sat Mar 09, 2024 7:35 pm Post subject: |
|
|
About desktop I mean Cinnamon desktop, to run system console I run Crtl+Alt+F1 or F2... but in this case that doesn't work, I run the system in rescue mode to try to investigate |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Sat Mar 09, 2024 8:04 pm Post subject: |
|
|
smokyrun wrote: | to run system console I run Crtl+Alt+F1 or F2... but in this case that doesn't work, I run the system in rescue mode to try to investigate |
Try pressing ALT+PrtScr+R prior to pressing CTRL+ALT+functional key.
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sun Mar 10, 2024 9:32 am Post subject: |
|
|
Thank you so much for your help Georgi, I did Ctrl+PrintScreen+R prior opening a console terminal but always unable to open session.
I checked all option in my BIOS about virtualisation everything is OK
I upgraded my system yesterday but the problem persist.
I think the problem is not a problem with the kernel but with pam modules regarding the content of auth.log :
Code: |
Mar 10 12:44:03 himalaya lightdm: pam_unix(lightdm-greeter:session): session opened for user root(uid=0) by root(uid=0)
Mar 10 12:44:23 himalaya lightdm: gkr-pam: unable to locate daemon control file
Mar 10 12:44:23 himalaya lightdm: gkr-pam: stashed password to try later in open session
Mar 10 12:44:23 himalaya lightdm: pam_unix(lightdm-greeter:session): session closed for user root
[b]Mar 10 12:44:23 himalaya lightdm: pam_elogind(lightdm-greeter:session): Failed to release session: No session '1' known[/b]
Mar 10 12:44:23 himalaya lightdm: pam_unix(lightdm:session): session opened for user willy(uid=1000) by willy(uid=0)
Mar 10 12:44:23 himalaya lightdm: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
|
|
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Sun Mar 10, 2024 1:55 pm Post subject: |
|
|
smokyrun wrote: | but always unable to open session. |
You mean you're unable to switch to a framebuffer console or your login is not accepted?
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sun Mar 10, 2024 4:10 pm Post subject: |
|
|
Yes I'm unable to switch to a framebuffer console and my login is accepted but unable to open a cinnamon session I only have the wallpaper of the desktop.
Thank you for your help. |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Sun Mar 10, 2024 4:21 pm Post subject: |
|
|
Describe how you updated your kernel and share the kernel config.
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sun Mar 10, 2024 4:42 pm Post subject: |
|
|
Please find below the content of .config file :
https://pastebin.com/NXfmfrF3
To update my kernel :
1) I remove in /boot {System.map-6.6.13-gentoo config-6.6.13-gentoo initramfs-6.6.13-gentoo.img vmlinuz-6.6.13-gentoo}
2) In /usr/src/linux run make menuconfig
3) I set all module and parameters I need and I save modifications
4) I run make -j8
5) I run make modules_install
6) I run make install
7) I run grub-install --target=x86_64-efi --efi-directory=/boot/efi
I run grub-mkconfig -o /boot/grub/grub.cfg
Kind regards,
Willy |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Sun Mar 10, 2024 5:06 pm Post subject: |
|
|
I forget this step :
dracut --kver 6.6.13-gentoo |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Sun Mar 10, 2024 5:59 pm Post subject: |
|
|
You don't need 1 and 7 is only needed if there's been a grub package update that concerns the loader.
Now I'm not a kernel config guru, I hope somebody else step in, in the mean time why don't you try booting gentoo-kernel-bin and see if it works. If it does, post the output of lsmod and lspci -nnk. Or boot with the LiveGUI and post the outputs of the same two commands.
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Mon Mar 11, 2024 1:53 pm Post subject: |
|
|
Code: | [code][/code]Thank you so much for your help and your advices, see below the output of lspci and lsmod command :
lsmod:
[code]Module Size Used by
ctr 12288 2
ccm 20480 6
8021q 32768 0
ipv6 512000 28
fan 12288 0
iwlmvm 499712 0
mac80211 1064960 1 iwlmvm
libarc4 12288 1 mac80211
intel_pmc_core_pltdrv 12288 0
intel_pmc_core 69632 0
x86_pkg_temp_thermal 12288 0
kvm_intel 323584 0
snd_soc_avs 147456 0
iwlwifi 417792 1 iwlmvm
snd_soc_hda_codec 16384 1 snd_soc_avs
kvm 995328 1 kvm_intel
snd_hda_ext_core 20480 2 snd_soc_avs,snd_soc_hda_codec
snd_hda_codec_realtek 147456 1
snd_soc_core 253952 2 snd_soc_avs,snd_soc_hda_codec
dm_multipath 28672 0
dm_mod 143360 1 dm_multipath
snd_hda_codec_generic 77824 1 snd_hda_codec_realtek
snd_hda_codec_hdmi 61440 1
ledtrig_audio 12288 1 snd_hda_codec_generic
snd_compress 16384 2 snd_soc_avs,snd_soc_core
cfg80211 954368 3 iwlmvm,iwlwifi,mac80211
dax 32768 1 dm_mod
snd_hda_intel 40960 0
rtsx_pci_sdmmc 20480 0
snd_intel_dspcfg 12288 2 snd_soc_avs,snd_hda_intel
mmc_core 167936 1 rtsx_pci_sdmmc
snd_hda_codec 122880 6 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_codec_realtek
i2c_designware_platform 12288 0
think_lmi 32768 0
i2c_designware_core 28672 1 i2c_designware_platform
firmware_attributes_class 12288 1 think_lmi
ee1004 12288 0
wmi_bmof 12288 0
intel_wmi_thunderbolt 12288 0
snd_hda_core 86016 8 snd_hda_codec_generic,snd_soc_avs,snd_hda_codec_hdmi,snd_soc_hda_codec,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek
snd_pcm 126976 7 snd_soc_avs,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_compress,snd_soc_core,snd_hda_core
irqbypass 12288 1 kvm
crct10dif_pclmul 12288 1
intel_lpss_pci 24576 0
snd_timer 36864 1 snd_pcm
sha512_ssse3 45056 0
snd 98304 9 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
intel_lpss 12288 1 intel_lpss_pci
video 57344 0
sha512_generic 12288 1 sha512_ssse3
i2c_i801 20480 0
backlight 16384 1 video
sha256_ssse3 28672 0
i2c_smbus 12288 1 i2c_i801
sha1_ssse3 32768 0
rtsx_pci 81920 1 rtsx_pci_sdmmc
sha1_generic 12288 1 sha1_ssse3
i2c_core 77824 5 i2c_designware_platform,i2c_designware_core,ee1004,i2c_smbus,i2c_i801
rfkill 28672 6 iwlmvm,cfg80211
soundcore 12288 1 snd
mfd_core 12288 2 rtsx_pci,intel_lpss
thermal 20480 0
battery 20480 0
wmi 24576 4 video,intel_wmi_thunderbolt,wmi_bmof,think_lmi
pinctrl_sunrisepoint 24576 0
ac 12288 0
acpi_pad 16384 0
button 16384 0
efivarfs 24576 1
btrfs 1585152 2
blake2b_generic 16384 0
xor 20480 1 btrfs
zlib_deflate 28672 1 btrfs
zstd_compress 364544 1 btrfs
raid6_pq 118784 1 btrfs
usb_storage 65536 1
crc32c_intel 16384 2
aesni_intel 356352 4
crypto_simd 12288 1 aesni_intel
cryptd 24576 1 crypto_simd
e1000e 229376 0
nvme 45056 3
ptp 32768 2 iwlmvm,e1000e
xhci_pci 16384 0
pps_core 12288 1 ptp
nvme_core 126976 4 nvme
xhci_hcd 237568 1 xhci_pci[/code]
lspci :
[code]00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:1910] (rev 07)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [17aa:224d]
Kernel driver in use: skl_uncore
00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)
Subsystem: Lenovo 6th-10th Gen Core Processor PCIe Controller (x16) [17aa:224d]
Kernel driver in use: pcieport
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:191b] (rev 06)
Subsystem: Lenovo HD Graphics 530 [17aa:224d]
00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:224d]
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [17aa:224d]
Kernel driver in use: xhci_hcd
00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family Thermal Subsystem [17aa:224d]
00:15.0 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 [8086:a160] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family Serial IO I2C Controller [17aa:224d]
Kernel driver in use: intel-lpss
00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family MEI Controller [17aa:224d]
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family PCI Express Root Port [17aa:224d]
Kernel driver in use: pcieport
00:1c.2 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 [8086:a112] (rev f1)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family PCI Express Root Port [17aa:224d]
Kernel driver in use: pcieport
00:1c.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family PCI Express Root Port [17aa:224d]
Kernel driver in use: pcieport
00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family PCI Express Root Port [17aa:224d]
Kernel driver in use: pcieport
00:1d.4 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13 [8086:a11c] (rev f1)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family PCI Express Root Port [17aa:224d]
Kernel driver in use: pcieport
00:1f.0 ISA bridge [0601]: Intel Corporation CM238 Chipset LPC/eSPI Controller [8086:a154] (rev 31)
Subsystem: Lenovo CM238 Chipset LPC/eSPI Controller [17aa:224d]
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family Power Management Controller [17aa:224d]
00:1f.3 Audio device [0403]: Intel Corporation CM238 HD Audio Controller [8086:a171] (rev 31)
Subsystem: Lenovo CM238 HD Audio Controller [17aa:224d]
Kernel driver in use: snd_hda_intel
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)
Subsystem: Lenovo 100 Series/C230 Series Chipset Family SMBus [17aa:224d]
Kernel driver in use: i801_smbus
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] (rev 31)
Subsystem: Lenovo Ethernet Connection (5) I219-LM [17aa:224d]
Kernel driver in use: e1000e
01:00.0 3D controller [0302]: NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] [10de:1436] (rev a1)
Subsystem: Lenovo GM206GLM [Quadro M2200 Mobile] [17aa:224d]
01:00.1 Audio device [0403]: NVIDIA Corporation GM206 High Definition Audio Controller [10de:0fba] (rev a1)
Kernel driver in use: snd_hda_intel
04:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
Subsystem: Intel Corporation Wireless 8260 [8086:0130]
Kernel driver in use: iwlwifi
3e:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]
Subsystem: Samsung Electronics Co Ltd SSD 970 EVO [144d:a801]
Kernel driver in use: nvme
3f:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01)
Subsystem: Lenovo RTS525A PCI Express Card Reader [17aa:224d]
Kernel driver in use: rtsx_pci[/code] |
Have a nice day.
Willy |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Mon Mar 11, 2024 5:45 pm Post subject: |
|
|
I guess this is from gentoo-kernel-bin? If so, is there a reason you don't want to tun it? Custom kernel configuration is tedious.
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Tue Mar 12, 2024 12:17 pm Post subject: |
|
|
No, it is a comoiled kernel, I think my problem is not a kernel problem but a problem with X11.
I disabled display-manager and xdm and the system works fine, any problem.
My graphic card is an hybrid card with an Intel card as primary and an Nvidia card as secondary, I'm not sure but I think when a activated KVM module in the kernel the system prefer to use the Nividia card, which is more effcient than the Intel, currently I'm trying to see how to do to allow the system to use the Nvidia card.
Before the activation of KVM module the system used the Intel card and worked fine.
Kind regards,
Willy |
|
Back to top |
|
|
logrusx Veteran
Joined: 22 Feb 2018 Posts: 1659
|
Posted: Tue Mar 12, 2024 3:08 pm Post subject: |
|
|
smokyrun wrote: | No, it is a comoiled kernel, I think my problem is not a kernel problem but a problem with X11.
I disabled display-manager and xdm and the system works fine, any problem.
My graphic card is an hybrid card with an Intel card as primary and an Nvidia card as secondary, I'm not sure but I think when a activated KVM module in the kernel the system prefer to use the Nividia card, which is more effcient than the Intel, currently I'm trying to see how to do to allow the system to use the Nvidia card.
Before the activation of KVM module the system used the Intel card and worked fine.
Kind regards,
Willy |
Did you reemerge the nvidia-drivers for the new kernel?
Best Regards,
Georgi |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Tue Mar 12, 2024 3:24 pm Post subject: |
|
|
No I didn't I'm going to do it.
Thank you. |
|
Back to top |
|
|
smokyrun n00b
Joined: 26 Dec 2023 Posts: 42 Location: Reunion Island
|
Posted: Tue Mar 12, 2024 6:09 pm Post subject: |
|
|
Thank you so much for you help Georgi, now everything work fine
I reemerge nvidia-drivers as you told me after that the system told to set IBT parameter to off in the kernel, after the compile of kernel everything are OK;
I'm very happy, I succeeded to set up :
Gentoo
Lightdm
Cinnamon
Nordvpn
KVM
Thank you again for your help and your advises !!!
Kind regards,
Willy |
|
Back to top |
|
|
|