So, I would be super interested how you inferred it was Linux’ fault but I sssume b/s at this point.
So, I would be super interested how you inferred it was Linux’ fault but I sssume b/s at this point.
"Fried" was a poor choice of words - the device is dead - but it's due to firmware and probably something to do with sleep states.
I didn't mean to imply the radio was actually fried.
It'll be interesting to see what the technicians end up doing to get it working. It might be enough to disconnect the card and force some even deeper reset than a power cycle with drained laptop battery does - but as I still have valid guarantee on the machine, I stopped short of opening it up. Especially since I might need a new wifi card anyway.
Chance is you could probably have Claude or Codex had look into it and have them fix it for you.
Ed: user AI on the Linux side, to help with getting firmware blobs etc - might be random combination of flaky firmware, flaky Linux support and reboots that did it - not AI or any particular driver/firmware version.
It's the first time I've seen drivers knock out a hw component completely on a consumer product - but I gather the platform is fickle.
The arm64 Snapdragon elite support is very poor unfortunately (due to there being zero upstream support).
Which wouldn't be so bad if they weren't marketed with a promise of Linux support.