When I login using this kernel on Wayland my screens stay black, flicker a little and then I am able to open for example a terminal via the Ctrl + Alt + T shortcut but essentially there are no desktop elements present (opening windows via the terminal still works though, and they can still be snapped while holding Ctrl - I’m writing this while being in that session).
No clue if this is helpful but this is my journalctl (journalctl --since yesterday > out.log) in which I first open a X11 session (no problems) and then logout and open a Wayland session (Ctrl + F: unknown[1831]: Now starting Wayland session): journalctl_boot.log · GitHub
That kinda fixed it for me. The first time I rebooted it crashed the whole PC, when I restarted the PC and then accidentally logged in again using a Wayland session it just worked like in the previous kernels.
(I updated the line GRUB_CMDLINE_LINUX="nvidia_drm.modeset=1 to GRUB_CMDLINE_LINUX="nvidia_drm.modeset=1 nvidia-drm.fbdev=1" in the file /etc/default/grub and ran sudo update-grub before restarting)
On the 14th I received an update with the kernel and plymouth.
Installed and got errors, one of which doesn’t appear in the image I’m going to share, which has to do with something similar to zdt or ztd. the rest of the errors are in this image that I captured now when reinstalling the system. On the 14th I got a black screen, both with the latest kernel and the LTS version.another error: WARNING: consolefont: no font found in configuration. If I restart I am left without a system again.
Since the latest testing update I’ve not been able to switch on bluetooth at all. Not even through a good ol’ restart.
sudo systemctl start bluetooth yields no output and does not resolve the issue.
FYI:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:2822 VIA Labs, Inc. USB2.0 Hub
Bus 001 Device 003: ID 27c6:60c2 Shenzhen Goodix Technology Co.,Ltd. Goodix USB2.0 MISC
Bus 001 Device 004: ID 048d:8910 Integrated Technology Express, Inc. ITE Device
Bus 001 Device 005: ID 2537:1081 Norelsys NS1081
Bus 001 Device 006: ID 0e8d:0608 MediaTek Inc. Wireless_Device
Bus 001 Device 007: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet
Bus 001 Device 008: ID 14cd:8601 Super Top 4-Port hub
Bus 001 Device 009: ID 291a:8388 Anker Innovations Limited. Anker USB-C Hub Device
Bus 001 Device 010: ID 3384:4216 System76 USB4216 Smart Hub
Bus 001 Device 011: ID 3384:0001 System76 Launch Configurable Keyboard (launch_1)
Bus 001 Device 012: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More&Better]
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0c45:6362 Microdia Integrated Camera
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[ 18.746113] Bluetooth: Core ver 2.22
[ 18.746130] NET: Registered PF_BLUETOOTH protocol family
[ 18.746131] Bluetooth: HCI device and connection manager initialized
[ 18.746134] Bluetooth: HCI socket layer initialized
[ 18.746136] Bluetooth: L2CAP socket layer initialized
[ 18.746139] Bluetooth: SCO socket layer initialized
[ 18.939209] bluetooth hci0: Direct firmware load for mediatek/BT_RAM_CODE_MT7961_1a_2_hdr.bin failed with error -2
[ 18.939213] Bluetooth: hci0: Failed to load firmware file (-2)
[ 18.939215] Bluetooth: hci0: Failed to set up firmware (-2)
[ 18.939216] Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
[ 19.044405] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.044409] Bluetooth: BNEP filters: protocol multicast
[ 19.044414] Bluetooth: BNEP socket layer initialized
Booting into Linux 6.8 resolves the above issue. It seems 6.9 fails to load the bluetooth driver for my machine.
Please do not post images of text, use copy+paste and proper formatting.
From what I can make out there are no errors visible in that terminal window (yay for terminal transparency - it makes the contents all the more harder to read )
Why was KMS forcefully added to my mkinitcpio.conf without my consent?
Is there a known issue, or system component, which required this hook to be sneaked in with a script in this way?
I dont see anything related to this on the mkinitcpio 39.1 changelog, the announcement, nor the wiki post.
I havent had the time to do much research, but I am genuinely interested in an answer.
Its been default in arch for some time and manjaro both adopted and did the forced sed because it reduces (but does not eliminate) the amount of blackscreens that plymouth produces.
It would have been in a pacnew for however long, but I guess it was ignored by users enough and deemed necessary enough to ‘force apply’.
Not my reasoning, but I’m pretty sure thats how it went.
kms does a lot more than just ‘fix’ plymouth.
Its just the reason that spurred the manjaro team to want it.
I have always made sure to enable KMS, and early at that. In general it can lead to better power efficiency and performance etc. With some possible slight slower boot time.
(read: negligible to the point of almost not being worth mentioning)
There are some edge cases where KMS might produce funny results.
But my summation is roughly that - if it doesnt result in any noticeable breakage then its desirable to have enabled/configured.
Strictly speaking you did consent to updating packages, but could not give informed consent because there is no mention of it the any of usual places (assuming users on Testing branch are not expected to read commits on Manjaro.Gitlab before updating)
But it would also be correct to say that the KMS was forcefully added without your knowledge
For the usual scenario (e.g. mkinitcpio.conf.pacnew created for user to merge the microcode hook) user is informed about creation of a .pacnew only after consenting to the update:
[2024-05-14T08:55:40+0100] [ALPM] warning: /etc/mkinitcpio.conf installed as /etc/mkinitcpio.conf.pacnew
IMO both of these are sub-optimal and users should have information in update announcements so they are informed about changes before consenting to update
1st or 2nd post only needs minimal information for ABCYA purposes (Always Be Covering Your A***)
)
)