MASTER Network Manager should probe for GSM and CDMA command sets. It doesnt detect 3g modems with serial capability only in hal
Bug #268095 reported by
Alexander Sack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HAL |
Fix Released
|
Medium
|
|||
network-manager (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: network-manager
problem is that almost all modems are detected as "serial" v.250 modems, but that isnt enough for NM to decide whether its a GSM or CDMA modem.
Without that info network manager cannot properly detect which commands to use and ends up not supporting them.
Adding all the pci ids to the modem.fdi isnt the way to go. instead we need to use AT commands to probe whether its a CDMA or GSM modem.
This probing could be done as a hal hook or in NM directly. The right approach has yet to be decided.
Test packages: http://
Changed in network-manager: | |
importance: | Undecided → High |
milestone: | none → ubuntu-8.10 |
status: | New → Triaged |
Changed in hal: | |
status: | Unknown → Confirmed |
Changed in hal: | |
status: | Confirmed → In Progress |
Changed in hal: | |
status: | In Progress → Fix Released |
Changed in hal: | |
importance: | Unknown → Medium |
Changed in hal: | |
importance: | Medium → Unknown |
Changed in hal: | |
importance: | Unknown → Medium |
To post a comment you must log in.
Relaying my comment from bug 262490:
Some devices, like the Dell internal USB HSDPA modems, lack CDC ACM descriptors. There is no way to recognize these devices as GSM/CDMA modems without a kernel driver being explicitly told about it by USB vendor/device ID, or by force-loading the generic usb-serial driver (using vendor and product ID params) then tweaking HAL to tell NM that the serial device is a modem.
To ensure that NM can then identify these devices, any found to be using the `option', `airprime', etc drivers should really be given a modem.command_sets attribute including V.250 , so NM's future GSM/CDMA probing support can identify them. Additionally, the GSM/CDMA drivers need support for user-specified vendor and product IDs because of the extensive re-branding that goes on in this area. I'll submit a patch for that shortly.
I've attached a new HAL fdi file that matches the option and airprime drivers (for a start; there are surely other GSM/CDMA drivers out there) and adds the V.250 capability to them. This should be dropped into /usr/share/ hal/fdi/ information/ 20thirdparty/ by the network-manager package. Once NM knows how to probe these devices that'll get them working as soon as the kernel drivers know about them - without having to exhaustively list vendor and product IDs in HAL's config.