AI Answers: Authority Without Accountability Fun with CMD: 5 Windows command-line tools for music, video, and more All the New Features Landing in Windows 11 This December Lossless vs Lossy: When FLAC, APE, and ALAC Beat MP3 and When They Don't Google Search Tricks You'll Actually Use in 2025 and Beyond Fresh PC Checklist: First 12 Things to Do On a New Windows 11 Machine Running AI Models Locally: What They Are, Where to Find Them, and How to Get Started Deciding Between Idle State, Sleep Mode, and Shutdown: What's Best for Your PC? How to Fix VMware Workstation "The Update Server Could Not Be Resolved" Error Installing VMware Tools How to Remove Google Gemini from Your Phone (and Your Life)|
advertisement
|
Post License:
GNU LGPL
For example, works fine on my Dell laptop under SuSE 10,1 (kernel 2.6.16.27) with Intel chipset.
Works occasionally on my desktop PC (A7V8X-X mobo) under identical SuSE setup. Didn't work at all prior to kernel 2.6.12 or so. As far as I can see there is no discernible pattern to when it does and doesn't work.
My suspiciion is that there's a difference in the way the underlying kernel modules initialise the USB interface depending on your hardware.
Roll on a later kernel with the fix....