It doesn’t accept touch input. I expect the undermentioned is the cause:
Recent kernel update seems to have introduces a bug that stops the FW16 touchpad from getting recognised. I’ve just revertered back to version 6.8.7 and can use my touchpad again. Now to patiently wait for the upstream to get a patch.
However, because this is a new installation, I can’t feasibly use an old kernel version, surely?
Actually, @AKNickolai, that kernel version was when I was using the live install. I now have both it and 6.10.11-200 installed simultaneously (I presume with it defaulting to the latter, although GRUB2 doesn’t appear by default, allowing me to confirm). The touchpad remains undiscovered.
No output whatsoever. Removing grep displays mostly the keyboard and numpad modules, with a few for the video bus, lid switch, and power button.
Grub not appearing by default is strange, did you modify your grub config file on this install?
It sounds like the touchpad also did not work under the live ISO. Do you have the ability to test with another OS or windows? You don’t have to install it, just see if it works after boot while you’re navigating the install menus.
If its not showing up with libinput list-devices and doesn’t work during install process for other OS’s you might just have a bad unit and need to RMA.
I have a 16 running the same Fedora 40 KDE distro, so I was able to verify all those steps on the same machine/OS.
I’ve only thought of this because I’m unable to establish a connection between the device and the charger when multiple cables are connected (presumably because its wattage is too low).
However, I wouldn’t expect any effect from it to persist after the cable has been disconnected.
Actually that’s by design, see the Changes/HiddenGrubMenu page on the Fedora wiki, also for steps/keyboard shortcuts to make it visible again. Tagging @RokeJulianLockhart as well, since that might be info useful to both.
On systems with only a single OS installed, the grub menu’s only function is to allow booting older kernels, which is only necessary as a rescue option in case of a severe kernel bug and as such not something which is directly useful for normal use.
Fedora already has a lot of work done to not show too technical boot messages to end users during bootup, e.g. we pass quiet to the kernel and we’ve plymouth to show a bootsplash instead of a bunch of “Starting service-foo: OK” messages.
The grub menu with its kernel versions is another example of showing too technical info to end-users and on non multi-boot systems it normally is not necessary, so it is better to hide it.
This change will add menu-auto-hide functionality to grub, which when enabled will hide the menu if:
The machine only has a single OS installed; and
The previous boot has set a flag to indicate it successfully booted