The issue with Chromebooks seems to be the way a device is configured. A device that normally works in Linux/Debian fails because it is configured in a way that the kernel doesn't recognise, and it won't work until the kernel "knows" about the way the device is configured.
Try a newer kernel from Backports and see if it contains configuration information for the device on your hardware. Try a live USB image of Trixie and see if that has configuration information for the device in any of the files that inform the kernel of unusual hardware setups.
Try a newer kernel from Backports and see if it contains configuration information for the device on your hardware. Try a live USB image of Trixie and see if that has configuration information for the device in any of the files that inform the kernel of unusual hardware setups.
Statistics: Posted by FreewheelinFrank — 2024-08-17 15:14 — Replies 6 — Views 226