Hi folks,
I’m working on setting up an old c771T with linux for my nieces as an educational and art-making machine, and I’ve got a handful of issues that I haven’t figured out yet and I was hoping someone here could provide some insights.
Input device issues
- My touchscreen worked on a fresh installation, but it would stop accepting inputs some time into a session, though it would work after rebooting. Recently, though, the touch screen seems to have stopped working entirely.
- keyd v2.5.0 (installed by WeirdTreeThing’s cros-keyboard-mapscript) ends intermittently with a “Floating point exception.” I’ve been restarting the process manually from a terminal window when I want to mess with the built-in multimedia keys, but that’s not a permanent solution
- The debugging script couldn’t find libinput
Audio issues
- There’s a popping sound when playback is initiated over a wired headset. It’s most noticeable when I used function keys to raise/lower the volume. Popping ranges from innocuous to very loud.
- The internal microphone doesn’t seem to be working. Input works fine from both wired and bluetooth headsets.
Here’s my output from the chrultrabook debug script: debug-logs-Lars-2025-01-19_17h12m.tar.gz - Google Drive
(I saw the warning to “Remember to remove WiFi information from dmesg to protect your privacy,” but I didn’t see any SSIDs or addresses or the like in that log; hopefully I’m not ignorant of something important!)
Thank you!
Hi again! It looks like I can’t edit the the subject of my original post. The scope of my issues have increased significantly and I’m not sure whether I should start a new thread or continue to post in this one. I’ve continued to have touchscreen, keyboard remapping (keyd stopping unexpectedly), and audio issues on kernal 6.11 installed through debian backports, as well as on kernals 6.11 and 6.12 on an installation of Fedora 41 Cinnamon spin.
Currenly on Fedora 41:
- Touchscreen inputs are no longer registered as clicks
- Touching the touchscreen will consistently cause the top tow of keys to revert to being function row keys. I can restore remappings by running sudo keyd (and leaving the terminal window open) or by re-running WeirdTreeThing’s cros-keyboard-mapscript. Touching the touch screen will cause keyd to stop with the same “Floating point exception” output I saw on LDME.
- Speaker output is working flawlessly on Fedora 41 despite the chrultrabook audio script stating in no uncertain terms that speakers would be disabled. The internal microphone is still not working and output through the headphone/headset jack does not work. Input through the 3.5mm jack seems just fine when I plug in a headset.
Here’s my latest debug script outputs for Fedora 41 on kernal 6.11: debug-logs-Lars-2025-01-26_16h06m.tar.gz - Google Drive
…and kernal 6.12: debug-logs-Lars-2025-01-26_16h14m.tar.gz - Google Drive
The script could not find alsaucm (despite alsa-utils being installed), nor strace.
Cinnamon seems to be the common denominator between these overlapping issues, so I guess I’ll try other desktop environments next and report back.
KDE’s built-in “Google Chromebook” keyboard layout obviates the need for keyd to be running, but it does not address the underlying problem that touching the touchscreen crashes keyd. Issues persist in KDE and Xfce.
Ok, I’m just using this thread as my thinking-out-loud space for now.
Here are some audio-related warnings and errors I found today:
A lot of my boots starting on the morning on 01/26 have 4 similar errors to the ones above.

So the alsa folks added use cases for max98357a in version v1.2.13: Detailed changes v1.2.12 v1.2.13 - AlsaProject
This might (?) explain why my speakers work unexpectedly on Fedora 41; 1.2.13 is what I’ve had installed from the star. That doesn’t get me any closer to figuring out what’s gone wrong with the headphone jack, though. Mic input over 3.5mm hasn’t been working recently either (I’m kicking myself for documenting that yet), though I guess I’ve only tested that in KDE in the last two weeks and not in other desktop environments.
Mic input on the 3.5mm jack is actually working fine - you just can’t immediately see that it’s working at a glance form KDE’s sound configuration page like you can on Cinnamon’s.