Description of problem: Everytime I try to set up my Sierra Wireless 890 AirCard in MCC as a GPRS modem, the software keeps asking for a PIN and will not accept anything I input (even blank). AirCard does not require a PIN with Fedora 15 to set up and use. Had this indentical problem when testing the Beta 2 Live CD with this 890 AirCard. Version-Release number of selected component (if applicable): How reproducible: Try to set up Sierra Wireless 890 AirCard from MCC or from Network Center. Steps to Reproduce: 1. Open MCC 2. Choose Network & Internet 3. Choose Setup a new network interface... 4. Choose GPRS/EDGE/3G, then Next 5. Choose Next for "ppp0: Sierra Wireless, Incorporated AC890" 6. Can't get past the PIN screen regardless of no pin or any number I input.
Hi David, Sorry for responding so very, very late. I've been googling for related bugs, but all I find are a lot of reports you made mentioning this bug in Mageia... if it doesn't get solved, you're the last one to blame! Maybe I overlooked a similar problem I should have found. I saw your post: Re: Huawei E583C not finding pin - heeelllppp Postby David Batson » July 20th, 2011, 12:35 pm I ran into a similar problem with my Sierra Wireless 890 AirCard in Mageai 1 when trying to configure with MCC. I could not get past the PIN screen. Tried kppp and was able to connect just fine. You need to know what dev port to use for your device with kppp. In my case it was /dev/ttyUSB3. Mandriva Linux 2010.2 Free 32-bit on a ThinkPad T42. I understand that connecting in Mageia with kppp worked fine, so with kppp no pin was asked for, is that correct?
CC: (none) => andre999mga, marja11Component: Release (media or process) => RPM PackagesSource RPM: (none) => drakx-net 0.97-1.mga1
Found a whole thread, now, in the Mageia Forum: https://forums.mageia.org/en/viewtopic.php?f=25&t=546 So yes, using kppp solved the issue for you
URL: (none) => https://forums.mageia.org/en/viewtopic.php?f=25&t=546
CC: andre999mga => (none)
@ blino I tend to close this report as "worksforme" because no one else reported this issue, and it got solved for the reporter. But since you are the maintainer of drakx-net, I think you should decide
CC: (none) => mageia
Closing, because the reporter found a workaround and no one else reported this issue
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME