Which Linux distro are you using? Debian
Which release version? Testing
Which kernel are you using? 6.12.8
Which BIOS version are you using? 3.05
Which Framework Laptop 16 model are you using? (AMD Ryzen™ 7040 Series) Ryzen 7 7840HX
While I always boot with the Audio expansion card inserted, sometimes Debian either forgets it ot refuses to use it after a while, not sure. Plugging anything into it just isn’t registered by the system. Unplugging it and plugging it back in leads to these log messages (with headphones plugged in):
Jan 08 18:38:40 kernel: usb 1-2.2: new high-speed USB device number 14 using xhci_hcd
Jan 08 18:38:40 kernel: usb 1-2.2: New USB device found, idVendor=32ac, idProduct=0010, bcdDevice= 0.02
Jan 08 18:38:40 kernel: usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Jan 08 18:38:40 kernel: usb 1-2.2: Product: Audio Expansion Card
Jan 08 18:38:40 kernel: usb 1-2.2: Manufacturer: Framework
Jan 08 18:38:40 kernel: input: Framework Audio Expansion Card Consumer Control as /devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2/1-2.2:1.2/0003:32AC:0010.000E/input/input27
Jan 08 18:38:40 kernel: hid-generic 0003:32AC:0010.000E: input,hidraw7: USB HID v1.11 Device [Framework Audio Expansion Card] on usb-0000:c1:00.3-2.2/input2
Jan 08 18:38:40 mtp-probe[16512]: checking bus 1, device 14: "/sys/devices/pci0000:00/0000:00:08.1/0000:c1:00.3/usb1/1-2/1-2.2"
Jan 08 18:38:40 mtp-probe[16512]: bus: 1, device: 14 was not an MTP device
And when unplugging these:
Jan 08 18:42:14 framework16 kernel: usbhid 1-2.2:1.2: can't add hid device: -71
Jan 08 18:42:14 framework16 kernel: usbhid 1-2.2:1.2: probe with driver usbhid failed with error -71
Jan 08 18:42:14 framework16 kernel: usb 1-2.2: USB disconnect, device number 15
Is there a solution for this?
Please read the whole post. I never claimed this happens 100 % of the time, it happened sometimes, randomly and seemingly only after a while of running. So booting any live ISO will hardly be a suitable testing environment.
ive had some issues with the audio expansion card on fedora which ive chalked up to the cable not being fully inserted, but im not certain now.
it should be noted that to save power (at least this is the most logical explanation for the behaviour ive observed in the past, before i started having issues) the audio expansion card disconnects itself until it detects a cable plugged into it.
That power saving thing may be true, but then it should work when unplugging the module and plugging it back in. But so far only a reboot can fix it.
I guess the OP is saying booting it to a the live image to try to reproduce something intermittent is a unfeasible task for them?
Not sure if they can use it long enough in a live environment to reproduce the issue other than leaving something playing 24x7 (which may not be feasible). And may not be representative of their work flow which may replicate the issue.
Either way, I do think it’s at least something they can try (leave it playing music or something) while they aren’t using the laptop (background music or video).
Can try it in both a live environment and their current one.
Honestly, I don’t understand the last sentence - OP’s response didn’t sound hostile - just wondering what a live environment can do to help with their issue. Perhaps my expanded text would help - meaning “it may not SEEM like it will help, but at least it will be another data point”.
But also, I would contact Framework to see they can replace the module.
OH, another good test it to use the expansion card on a different PC (same OS or not) - just to see if it’s an issue with the expansion card before reaching out to Framework.
Because it’s intermittent, and no one else having this issue, it might be an issue with the card itself…
FYI, I’m on Fedora 41 (just got 6.12.8) but I don’t use my headphones that often. I can’t test 6.12.8 since I just got it AND my FW16 is on it’s way back to Framework to look into my display issue.
All I can say is prior to 6.12.8 (6.12.7 and prior), I had no issues with detecting my headphones as I do plug and unplug it relatively often.
Booting any live ISO isn’t a usable approach, as the issue happens too randomly. If it was an issue where I just had to boot into it and have my results, sure. But I would have to run it for days to even have a chance of encountering it, and I can’t even tell if only putting the device to sleep instead of shutting down and powering on will even have the same result. So I had to render my FW 16 literally unusable for days or weeks, and it’s questionable if that would even result in a representative test, as it’s a live distro that’s not storing anything, which again can just make the results worthless.
So no, any live ISO can’t be a viable test, not to mention making my life for days or weeks stupidly difficult. My laptop isn’t just some secondary or tertiary device, it’s my one and only computer that I use daily. That’s why I even went with FW, as I will always expect for my computer to last around 10 years, or it’s just not worth its money. With being easily repairable and upgradable, I see FW as pretty much the last company that can guarantee longevity, instead of cheaping out more and more every year so consumers need to replace their devices more frequently.