Bug 131740

Summary: Add Automatic support for Qualcom GT 3G Quad card, and vodafone 3g/GPRS service
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Simon Crute <simon.crute>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED WONTFIX QA Contact: Klaus Kämpf <kkaempf>
Severity: Enhancement    
Priority: P5 - None    
Version: RC 4   
Target Milestone: ---   
Hardware: All   
OS: SuSE Linux 10.0   
Whiteboard:
Found By: IS&T Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: y2logs
provider file for vodafone
hwinfo output for gt 3g quad card
hwinfo output for 3g datacard

Description Simon Crute 2005-11-01 12:25:38 UTC
Hi, 
The qualcom GT 3G Quad card works with sl10.0, but requires some manual configuration to get working. 
It would be great if this could be automatically setup.

The card is recognised when inserted, and the usbserial module is loaded OK. The modem is on /dev/ttyUSB0

Yast doesn't recognise the device, but if it's added, it works. 

I will attach the vodafone provider file, and the y2logs. 

We have the card on eval until middle of November, after that it will be harder to track one down if you want to test on my system.
Comment 1 Simon Crute 2005-11-01 12:27:39 UTC
Created attachment 56121 [details]
y2logs

y2logs from yast2 modem
Comment 2 Simon Crute 2005-11-01 12:29:20 UTC
Created attachment 56122 [details]
provider file for vodafone

vodafone provider file for gprs/g3
Works in the UK. may work in other vodafone areas. Not sure.
Comment 3 Martin Vidner 2005-11-03 13:57:35 UTC
For the record, here's how to set it up manually.
https://wiki.innerweb.novell.com/wiki.phtml?title=3G/GPRS_Vodafone_Mobile_Connect_Datacard_-_how_to_get_it_working

It seems that it will be enough to get hwinfo report the card as a modem and add Vodafone to the provider list.

Simon, please attach also the output of hwinfo (with the card inserted, of course) http://www.opensuse.org/Bug_Reporting_FAQ#YaST
Comment 4 Simon Crute 2005-11-03 16:56:53 UTC
Created attachment 56407 [details]
hwinfo output for gt 3g quad card
Comment 5 Simon Crute 2005-11-03 16:58:07 UTC
Created attachment 56408 [details]
hwinfo output for 3g datacard

this is hte hwinfo for a slithgly different card, the "3G datacard". (not q quad card.)
Comment 6 Martin Vidner 2005-11-04 12:27:15 UTC
Thanks. So here is the relevant part for "Fusion UMTS Quad-GPRS" (comment 4)

64: USB 00.0: 0700 Serial controller
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_af0_6300__Serial_Numbe_if0_serial_usb_0
  Unique ID: ZmS7.GHNMJ74MN7E
  Parent ID: 7eqy.docdF7zHNWC
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:01.0/0000:03:00.1/usb6/6-1/6-1:1.0
  SysFS BusID: 6-1:1.0
  Hardware Class: unknown
  Model: "Option N.V Fusion UMTS Quad-GPRS"
  Hotplug: USB
  Vendor: usb 0x0af0 "Option N.V."
  Device: usb 0x6300 "Fusion UMTS Quad-GPRS"
  Serial ID: "?Serial Numbe"
  Driver: "option"
  Device File: /dev/ttyUSB0
  Device Number: char 188:0
  Speed: 12 Mbps
  Module Alias: "usb:v0AF0p6300d0000dc00dsc00dp00icFFiscFFipFF"
  Driver Info #0:
    Driver Status: option is active
    Driver Activation Cmd: "modprobe option"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #63 (Hub)

67: Serial 00.0: 10200 Modem
  [Created at modem.446]
  Unique ID: CBAB.KM1shMXflFC
  Parent ID: ZmS7.GHNMJ74MN7E
  Hardware Class: modem
  Model: "AT Modem"
  Vendor: int 0x2000 "Unknown"
  Device: int 0x0001 "AT Modem"
  Device File: /dev/ttyUSB0
  Speed: 4 Mbps
  Init1: ATZ
  Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #64 (Serial controller)

And here for "Vodafone Mobile Connect Card - 3G" (comment 5)

62: USB 00.0: 0700 Serial controller
  [Created at usb.122]
  UDI: /org/freedesktop/Hal/devices/usb_device_af0_5000_Serial_Number_if0_serial_usb_0
  Unique ID: UfPf.0cu5T+VfZC0
  Parent ID: 2XnU.s3Y2uMAaQE5
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:02:01.0/0000:03:00.0/usb5/5-1/5-1:1.0
  SysFS BusID: 5-1:1.0
  Hardware Class: unknown
  Model: "Vodafone Mobile Connect Card - 3G"
  Hotplug: USB
  Vendor: usb 0x0af0 "Vodafone"
  Device: usb 0x5000 "Vodafone Mobile Connect Card - 3G"
  Serial ID: "Serial Number"
  Driver: "option"
  Device File: /dev/ttyUSB0
  Device Number: char 188:0
  Speed: 12 Mbps
  Module Alias: "usb:v0AF0p5000d0000dc00dsc00dp00icFFiscFFipFF"
  Driver Info #0:
    Driver Status: option is active
    Driver Activation Cmd: "modprobe option"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #61 (Hub)

65: Serial 00.0: 10200 Modem
  [Created at modem.446]
  Unique ID: CBAB.KM1shMXflFC
  Parent ID: UfPf.0cu5T+VfZC0
  Hardware Class: modem
  Model: "AT Modem"
  Vendor: int 0x2000 "Unknown"
  Device: int 0x0001 "AT Modem"
  Device File: /dev/ttyUSB0
  Speed: 4 Mbps
  Init1: ATZ
  Init2: AT Q0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #62 (Serial controller)

Hm, that's strange, it looks like both should get recognized.
Please attach y2logs after running yast2 modem and the output of these commands
 hwinfo --modem
 echo '`Read (.probe.modem)' | /usr/lib/YaST2/bin/y2base stdio scr

Or what do you mean by 'does not recognize the device'? If you mean that the modem appears but is identified as 'AT Modem' instead of the brand name then you don't need to attach more.
Comment 7 Simon Crute 2005-11-04 14:11:30 UTC
Hummmm. 

I could have sworn there was no modem there at all when I first did this. 

I have since removed the modem from yast, then pluged the card in, waited 5 mins and started yast2 modem, and there was an "AT Modem" device there. 

Not sure why....

I guess it's only the name that needs updateing. 

I can't confirm on the older card (the non-quad card) as it's not in the office today. If that's got a a problem, I'll update the ticket. 

If I get the chance, I'll test on a vanilla install, and update/reopen if nessisary. 
Comment 8 Martin Vidner 2006-08-28 11:52:29 UTC
Reassigning to the new maintainer of yast2-network.
Comment 9 Michal Zugec 2006-08-30 06:47:12 UTC
move to later
Comment 10 Stephan Kulow 2008-06-25 09:33:59 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 11 Stephan Kulow 2008-06-25 09:35:39 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 12 Stephan Kulow 2008-06-25 09:41:33 UTC
mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)
Comment 13 Stephan Kulow 2008-06-25 09:53:01 UTC
Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(