i dont know what is the cause of this problem i just change timeout=0 in the grub.cfg file and update grub but when i choice on the menu “manjaro” it appear just the prompt ,iknow that can log with alt+ctrl+F2 but all kind of update pacman cant restore the system as first… someone can help me?
Have to be changed here: /etc/default/grub and then update-grub.
/boot/grub/grub.cfg is generated.
hi ,maybe i had changed /etc/default/grub right, but the grub work and after i choose the system manjaro i can see the 3 tiny central point of the system loading but after it not show the desktop ,but only the prompt in black screen and fan run fast,
now i have switched on my pc and am on live cd and i can run all comman you ask to resolve this issue… just ask thans
Then you need to use the Manjaro USB stick and chroot into the system.
i have tried manjaro-chroot from live cd ,i think it s right…?
i also tried pamac snap ecc... mkinitcpio. ecc...
but the issue cant solve
sorry but i am a newbie
i don t want re-install the system because i made it just 2 day ago…
only do not want wait the grub countdown…
so revert the changes you made?
and the issue you describe doesnt look like its caused by changing the timeout… since you can enter into TTY…
so first, boot into manjaro live usb, connect to internet, chroot:
manjaro-chroot -a
and rerun update:
pacman-mirrors -f 5 && pacman -Syyu
are there any errors from this? if yes post them here
hi,ok
[manjaro@manjaro ~]$ manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/sda4]
--> mount: [/mnt]
[manjaro /]# pacman-mirrors -f 5 && pacman -Syyu
::INFO Downloading mirrors from Manjaro
::INFO => Mirror pool: https://repo.manjaro.org/mirrors.json
::INFO => Mirror status: https://repo.manjaro.org/status.json
::INFO Using default mirror file
::INFO Querying mirrors - This may take some time
0.399 Netherlands : http://ftp.snt.utwente.nl/pub/linux/manjaro/
0.737 Sweden : https://ftp.lysator.liu.se/pub/manjaro/
..... Russia : https://mirror.kamtv.ru/manjaro/
0.616 Austria : https://mirror.alwyzon.net/manjaro/
1.872 United_States : https://mirrors.sonic.net/manjaro/
::INFO Writing mirror list
::Netherlands : http://ftp.snt.utwente.nl/pub/linux/manjaro/stable
::Austria : https://mirror.alwyzon.net/manjaro/stable
::Sweden : https://ftp.lysator.liu.se/pub/manjaro/stable
::United_States : https://mirrors.sonic.net/manjaro/stable
::Russia : https://mirror.kamtv.ru/manjaro/stable
::INFO Mirror list generated and saved to: /etc/pacman.d/mirrorlist
:: Synchronizing package databases...
core 160.3 KiB 425 KiB/s 00:00 [######################] 100%
extra 1829.0 KiB 2.06 MiB/s 00:01 [######################] 100%
community 7.5 MiB 1433 KiB/s 00:05 [######################] 100%
multilib 166.4 KiB 997 KiB/s 00:00 [######################] 100%
:: Starting full system upgrade...
there is nothing to do
looks ok, provide logs from the failed boot:
journalctl -b-1 -p4 --no-pager
mhwd-kernel -li && mhwd -l -li
[manjaro /]# journalctl -b-1 -p4 --no-pager
mhwd-kernel -li && mhwd -l -li
Dec 29 23:24:42 computer kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
Dec 29 23:24:42 computer kernel: core: CPUID marked event: 'bus cycles' unavailable
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.0: incomplete constraints, dummy supplies not allowed
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.0: incomplete constraints, dummy supplies not allowed
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.4: incomplete constraints, dummy supplies not allowed
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.4: incomplete constraints, dummy supplies not allowed
Dec 29 23:24:42 computer kernel: sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
Dec 29 23:24:44 computer systemd-journald[264]: File /var/log/journal/bed4d9618bb2448dbb2befd0b65b5c5f/system.journal corrupted or uncleanly shut down, renaming and replacing.
Dec 29 23:24:47 computer kernel: at24 0-0050: incomplete constraints, dummy supplies not allowed
Dec 29 23:24:47 computer kernel: kauditd_printk_skb: 68 callbacks suppressed
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
Dec 29 23:24:52 computer systemd-udevd[303]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
Dec 29 23:24:54 computer kernel: kauditd_printk_skb: 134 callbacks suppressed
Dec 29 23:24:55 computer bluetoothd[629]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
Dec 29 23:24:55 computer bluetoothd[629]: src/plugin.c:plugin_init() Failed to init vcp plugin
Dec 29 23:24:55 computer bluetoothd[629]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
Dec 29 23:24:55 computer bluetoothd[629]: src/plugin.c:plugin_init() Failed to init mcp plugin
Dec 29 23:24:55 computer bluetoothd[629]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
Dec 29 23:24:55 computer bluetoothd[629]: src/plugin.c:plugin_init() Failed to init bap plugin
Dec 29 23:25:00 computer kernel: kauditd_printk_skb: 5 callbacks suppressed
Dec 29 23:25:10 computer kernel: kauditd_printk_skb: 1 callbacks suppressed
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: Configuration file /home/hello/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 29 23:27:14 computer systemd-journald[264]: File /var/log/journal/bed4d9618bb2448dbb2befd0b65b5c5f/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:2: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:3: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:4: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:5: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:6: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xfce-pbw.sh:7: Assignment outside of section. Ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: /home/hello/.config/autostart/xcape.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
Dec 29 23:27:14 computer systemd-xdg-autostart-generator[846]: Configuration file /home/hello/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
Dec 29 23:28:14 computer kernel: kauditd_printk_skb: 6 callbacks suppressed
Dec 29 23:43:37 computer NetworkManager[630]: <warn> [1672353817.0847] dispatcher: (8) failed (after 0.001 sec): Refusing activation, D-Bus is shutting down.
Dec 29 23:43:37 computer systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Failed with result 'exit-code'.
Dec 29 23:43:38 computer kernel: watchdog: watchdog0: watchdog did not stop!
Currently running: 6.1.1-1-MANJARO (linux61)
The following kernels are installed in your system:
* linux61
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
> 0000:01:00.0 (0300:1002:68e0) Display controller ATI Technologies Inc:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
[manjaro /]#
and everything was working before you edited the grub?
reinstall your kernel and install also the 515:
pacman -S linux61 linux515
if there are errors post them here;
open this:
nano /etc/default/grub
and edit these to look like this:
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
save it with ctrl+x; update grub:
update-grub
reboot and try booting with the 515 kernel
yes of course! it s very fast before… the system have done installed that kernel but in my grub file i have GRUB_TIMEOUT_STYLE=hidden an i overwrite GRUB_TIMEOUT_STYLE=menu (i hope its right)
and this is the result of update-grub
[manjaro /]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 10 on /dev/sda1
Root filesystem isn't btrfs
If you think an error has occurred, please file a bug report at "https://github.com/Antynea/grub-btrfs"
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
[manjaro /]#
now i reboot and notice you about if it work
sorry but it not work yet,i had tried to launch firefox in tty mode and return:
firefox -P
ERROR: no DISPLAY environment variable specified
i am loading live cd again…
did you tried with the 5.15 kernel?
post again logs:
journalctl -b-1 -p4 --no-pager
i dont know that i need to choose let me try again…
ok my friend,now it work 
,i choose the 5.15 kernel inside the advanced grub option,maybe something damaged in the previous kernel…
[hello@computer ~]$ journalctl -b-1 -p4 --no-pager
dic 30 11:03:53 computer kernel: x86/cpu: VMX (outside TXT) disabled by BIOS
dic 30 11:03:53 computer kernel: core: CPUID marked event: 'bus cycles' unavailable
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.0: incomplete constraints, dummy supplies not allowed
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.0: incomplete constraints, dummy supplies not allowed
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.0: Will use DMA mode even though HW doesn't fully claim to support it.
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.4: incomplete constraints, dummy supplies not allowed
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.4: incomplete constraints, dummy supplies not allowed
dic 30 11:03:53 computer kernel: sdhci-pci 0000:03:00.4: Will use DMA mode even though HW doesn't fully claim to support it.
dic 30 11:03:55 computer systemd-journald[269]: File /var/log/journal/bed4d9618bb2448dbb2befd0b65b5c5f/system.journal corrupted or uncleanly shut down, renaming and replacing.
dic 30 11:03:57 computer kernel: kauditd_printk_skb: 62 callbacks suppressed
dic 30 11:03:58 computer kernel: at24 0-0050: incomplete constraints, dummy supplies not allowed
dic 30 11:04:02 computer kernel: kauditd_printk_skb: 90 callbacks suppressed
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc0183, and key code 226: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1001, and key code 216: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1002, and key code 212: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1003, and key code 392: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1004, and key code 393: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1005, and key code 442: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100a, and key code 235: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100b, and key code 168: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100c, and key code 208: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc100f, and key code 184: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1010, and key code 185: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1011, and key code 403: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1012, and key code 402: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1013, and key code 212: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1014, and key code 152: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1015, and key code 167: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1016, and key code 213: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1017, and key code 161: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1018, and key code 171: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1019, and key code 184: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101a, and key code 185: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101b, and key code 186: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101c, and key code 154: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc101f, and key code 419: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1020, and key code 418: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1021, and key code 420: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1023, and key code 206: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1027, and key code 139: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1028, and key code 371: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1029, and key code 410: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102a, and key code 158: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102b, and key code 154: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102c, and key code 464: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc102d, and key code 150: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1031, and key code 218: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1032, and key code 223: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1041, and key code 138: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1042, and key code 421: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1043, and key code 423: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1044, and key code 425: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1045, and key code 131: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1046, and key code 182: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1047, and key code 210: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1048, and key code 234: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc1049, and key code 148: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104a, and key code 149: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104b, and key code 202: Invalid argument
dic 30 11:04:05 computer systemd-udevd[295]: event0: Failed to call EVIOCSKEYCODE with scan code 0xc104c, and key code 203: Invalid argument
dic 30 11:04:06 computer bluetoothd[628]: profiles/audio/vcp.c:vcp_init() D-Bus experimental not enabled
dic 30 11:04:06 computer bluetoothd[628]: src/plugin.c:plugin_init() Failed to init vcp plugin
dic 30 11:04:06 computer bluetoothd[628]: profiles/audio/mcp.c:mcp_init() D-Bus experimental not enabled
dic 30 11:04:06 computer bluetoothd[628]: src/plugin.c:plugin_init() Failed to init mcp plugin
dic 30 11:04:06 computer bluetoothd[628]: profiles/audio/bap.c:bap_init() D-Bus experimental not enabled
dic 30 11:04:06 computer bluetoothd[628]: src/plugin.c:plugin_init() Failed to init bap plugin
dic 30 11:04:08 computer kernel: kauditd_printk_skb: 46 callbacks suppressed
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: Configuration file /home/hello/.config/autostart/xfce-pbw.sh is marked executable. Please remove executable permission bits. Proceeding anyway.
dic 30 11:05:03 computer systemd-journald[269]: File /var/log/journal/bed4d9618bb2448dbb2befd0b65b5c5f/user-1000.journal corrupted or uncleanly shut down, renaming and replacing.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:2: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:3: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:4: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:5: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:6: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xfce-pbw.sh:7: Assignment outside of section. Ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: /home/hello/.config/autostart/xcape.desktop:9: Unknown key name 'RunHook' in section 'Desktop Entry', ignoring.
dic 30 11:05:03 computer systemd-xdg-autostart-generator[844]: Configuration file /home/hello/.config/autostart/xfce-panel-workaround.desktop is marked executable. Please remove executable permission bits. Proceeding anyway.
dic 30 11:07:00 computer login[835]: pam_systemd(login:session): Failed to release session: Interrupted system call
dic 30 11:07:00 computer kernel: kauditd_printk_skb: 6 callbacks suppressed
dic 30 11:07:01 computer NetworkManager[629]: <warn> [1672394821.5106] dispatcher: (8) failed (after 0.007 sec): Refusing activation, D-Bus is shutting down.
dic 30 11:07:02 computer systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount: Failed with result 'exit-code'.
dic 30 11:07:02 computer kernel: watchdog: watchdog0: watchdog did not stop!
[hello@computer ~]$
so you booted normally with the 5.15 kernel?
and also i noticed you are having windows… fast startup needs to be disabled in windows, otherwise it can cause issues
ok soon i go resolve this thing ,now ther is reason to return to the last kernel 6.xx or i can wor normaly in this same?
yes use the 5.15 … and try reinstalling the 61, remove it first:
sudo mhwd-kernel -r linux61
install it again:
sudo mhwd-kernel -i linux61
reboot and try booting again with it…
but first boot into windows and disable the fast startup
ok… i notice you later… but what could it have cause this damage on the kernel ? fast startup ?
really dont know… and the fast startup is not likely the cause, but it should be disabled anyway, so do it… maybe the reinstall mentioned in the command above will resolve it…