I have a bit of an odd issue with my Surface Pro 3, which is running Debian 12.

Occasionally (perhaps 1 in 15 to 20 boots) it fails to detect the keyboard properly (this is a genuine Microsoft keyboard cover that connects via the pins on the edge of the Surface, not one of the generic bluetooth ones you can get now). When that happens, the onscreen keyboard logo appears in the top right corner whilst the grub boot menu is displayed.

When it then tries to boot Debian, it throws some kind of Secure Boot error and displays this error message:

 undefined

    
SbatLevel variable initialization failed
Something has gone seriously wrong: SbatLevel UEFI variable setting failed: Invalid Parameter

  

I then have to force it to power off and then try booting again. Usually it works the next time around.

This one's got me stuck, as I don't know much about the Secure Boot process and I've struggled to find any other references to this error online apart from [this question](https://www.redd

Recently, my NixOS system has started taking around 2 minutes to boot. The delay happens when stopping system-udevd and multiple USB errors are thrown during it. I've tried booting with zero usb devices connected, but the issue still occurs. I have also tried updating my mobo, disabling XHCI handoff, legacy USB support, and the builtin wireless chipset. I haven't even been able to identify what USB port could be causing the issue. Motherboard is an MSI X670E TOMAHAWK WIFI.

Hastebin dump with the journalctl, lsusb -t, lsusb, lspci, and usb-devices output

Full dmesg dump

I would really appreciate any help, I've been losing my mind trying to fix this.

Edit: I looked at some dumps on linux-hardware.org, it seems likely that its the bluetooth chipset causing the issue. I'd already disabled this in the motherboard settings, but that apparently isn't enough.

If anybody knows how to make systemd-udevd ignore this device,

I want to hide the about tag in rEFInd. So, I did according to the info in config and website, which is to add a showtools line with no options.

And, nothing happens. I still see About, Shutdown, Reboot, Firmware tools in the rEFInd screen

 This is my rEFInd config containing showtools 👇

    
# Default is shell,memtest,gdisk,apple_recovery,windows_recovery,mok_tool,about,hidden_tags,shutdown,reboot,firmware,fwupdate
# To completely disable scanning for all tools, provide a showtools line
# with no options.
#
#showtools shell, bootorder, gdisk, memtest, mok_tool, apple_recovery, windows_recovery, about, hidden_tags, reboot, exit, firmware, fwupdate
showtools

  

Eventhough the previous showtools line is a just a comment, I removed it too. And still nothing happens.

Does anybody have any idea?

I only want Shutdown, Reboot.

SOLVED

It seems like a rEFInd problem in latest version.

**[https://lemmy.frozeninferno.xyz/comment/16257252](https://lem

I'm looking to buy a drawing tablet, specifically the XP-Pen Deco L to use with Krita. I'm running Fedora KDE with Wayland on my desktop and was wondering if anyone has experience using drawing tablets on Wayland, and if all works as it should. I checked the digi-mend driver and it supports this tablet and XP-Pen themselves publish a driver on their website, but from a quick search it seems to be X11 based.

Followup: The tablet arrived today and after plugging it in it got recognized and started working immediately! All buttons are mappable in Plasmas system settings, both on the pen and the tablet itself. This is with Fedora kernel 6.11.10-200.fc40.x86_64

General information:

• I'm using EndeavourOS, with KDE Plasma. I am very happy with my setup as it is, but since Wayland is "the future" I'm thinking of getting a move on.
• It came default with just X11, no Wayland. I know KDE supports Wayland but have no idea how to switch.
• I play a lot of games, I read somewhere that Wayland has worse gaming performance. I don't know if true or not, though.
• ... I have an AMD GPU. I'm not enough of a masochist to try and use Linux with NVidia.
• ..... BUT I've been thinking of upgrading to an Intel Arc GPU in the nearish future.

Let me know if there is any, more important, specific info I should be giving.

EDIT: I have changed. ... I felt no difference, but I suppose that is the whole point. Thank you to everyone who answered.