Re: NetworkManager and Dell 5530

[Dan Williams <dcbw redhat com>]

On Fri, 2009-03-27 at 22:50 +0000, Miles Sabin wrote:
> [Hmm ... sorry about that, the last reply got munged somehow]
> 
> On Fri, Mar 27, 2009 at 10:16 PM, Dan Williams <dcbw redhat com> wrote:
> > Can you try to blacklist the 'option' driver
> > (in /etc/modprobe.d/blacklist by adding a link "blacklist option") and
> > reboot, and see how many ttys you get?  The device should then be driven
> > by cdc-acm instead of option, which is really the correct driver for the
> > modem.
> 
> That seems to do the trick ... with "blacklist option" I get a good connection.
> 
> I'm not 100% sure how to parse your last sentence: is cdc-acm the
> correct driver for the device or is option? With option I've
> successfully used gpsd in conjunction with /dev/ttyUSB10 to interact
> with the device's GPS ... if cdc-acm is the correct driver which would
> be the correct device for the GPS stream?

Yes, cdc-acm is the "more" correct driver.  Ideally you use the modem's
Ethernet interface (driven by cdc-ether) instead of PPP, but since NM
doesn't support the Ethernet interface of the 5530 in 0.7.x (though git
head will), PPP is the best we get.

Any of the AT-capable ports can actually do GPS commands once you turn
on the NMEA flow using the Sony-Ericsson specific commands.  So just
pick a port that NM isn't using.

Dan

> > Also, the output of 'udevadm info --export-db' would be useful (remove
> > non-tty-related entries) so we can see what the prober is doing.  We can
> > also log the prober output to see what's going on.
> 
> Before the blacklist and reboot I get,
> 
> miles lewis:~$ udevadm info --export-db | grep ttyUSB
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.0/ttyUSB0/tty/ttyUSB0
> N: ttyUSB0
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.1/ttyUSB1/tty/ttyUSB1
> N: ttyUSB1
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.10/ttyUSB10/tty/ttyUSB10
> N: ttyUSB10
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.2/ttyUSB2/tty/ttyUSB2
> N: ttyUSB2
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.3/ttyUSB3/tty/ttyUSB3
> N: ttyUSB3
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.4/ttyUSB4/tty/ttyUSB4
> N: ttyUSB4
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.5/ttyUSB5/tty/ttyUSB5
> N: ttyUSB5
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.6/ttyUSB6/tty/ttyUSB6
> N: ttyUSB6
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.7/ttyUSB7/tty/ttyUSB7
> N: ttyUSB7
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.8/ttyUSB8/tty/ttyUSB8
> N: ttyUSB8
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.9/ttyUSB9/tty/ttyUSB9
> N: ttyUSB9
> 
> after the blacklist and reboot I get,
> 
> miles lewis:~$ udevadm info --export-db | grep ttyACM
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.1/tty/ttyACM0
> N: ttyACM0
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.3/tty/ttyACM1
> N: ttyACM1
> P: /devices/pci0000:00/0000:00:1d.7/usb2/2-6/2-6:1.9/tty/ttyACM2
> N: ttyACM2
> 
> > Just for reference, I did check -4 against an F3507g (same card) in a
> > Thinkpad X200 and it was working fine with that.  So it should be
> > working OK, just need to track down what the issue is.
> 
> I believe you: I'm not whining ... just grateful for all the work
> you've put in on this :-)
> 
> Cheers,
> 
> 
> Miles