| Summary: | Cannot setup Sierra Wireless 890 GPRS ExpressCard modem because of PIN | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Batson <dkbatson> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | mageia, marja11 |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://forums.mageia.org/en/viewtopic.php?f=25&t=546 | ||
| Whiteboard: | |||
| Source RPM: | drakx-net 0.97-1.mga1 | CVE: | |
| Status comment: | |||
|
Description
David Batson
2011-06-13 04:59:49 CEST
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, marja11 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
andré blais
2011-10-23 03:57:23 CEST
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 =>
RESOLVED |