I'm running openSuSE 10.1 and have set up an IO Data (random Japanese company) USB wireless device using ndiswrapper.
Everything worked great the first time I set it up. The default windows drivers worked, I was able to get connected to my access point, fine. Rebooted a few times to see if everything would work, and it did. Great.
Then I shut down my system for the night. I booted up the next day, and the wireless no longer functioned. So I checked out a few things. ndiswrapper -l
listed the driver as installed but the hardware not present. The hardware was obviously plugged in so I checked elsewhere.
showed the device as present but the PCI ID had changed!!!
Before (when I was set up correctly): 04bb:0928
Un/Replugging the USB device had no effect, the PCI ID stayed the same.
The windows drivers disk comes with two different INF files so I tried the other one. That one works with the new PCI ID but crashes the kernel when I modprobe ndiswrapper.
I dual boot with Windows XP currently. I noticed that if I boot into Windows (in which the device always works) then boot back into SuSE, the PCI ID is the working one, 0928. But if I cold boot straight into SuSE without touching Windows, I get the non-working PCI ID, 0929. Obviously Windows has an effect here.
Can someone tell me or guess what's going on and possibly how to correct this?