Comment 97 for bug 375148

Revision history for this message
Darik Horn (dajhorn) wrote :

This bug persists into Ubuntu 10.04 Lucid, but it seems to have changed slightly.

When the slusb module is loaded on my computer, I get these lines in my dmesg:

  -- ST7554 USB Modem.
  -- usbcore: registered new interface driver ST7554 USB Modem

The /dev/slusb0 device node is created, but it is improperly hooked to the actual hardware.

If you can get the direct bus address from `lsusb -v` or a similar program, then you can manually start slmodemd like this:

  $ sudo -i
  # ulimit -l 8192
  # /usr/sbin/slmodemd -d /dev/bus/usb/002/002
  SmartLink Soft Modem: version 2.9.11 Mar 22 2010 23:11:18
  <677.757945> SmartLink Soft Modem: version 2.9.11 Mar 22 2010 23:11:18
  <677.758157> 002: startup modem...
  <677.759501> 002: update termios...
  symbolic link `/dev/ttySL129' -> `/dev/pts/1' created.
  modem `002' created. TTY is `/dev/pts/1'
  <677.759650> open file: /var/lib/slmodem/data.002...
  <677.764930> main: rt applyed: SCHED_FIFO, pri 99
  <677.765158> main: dropped privileges to 127.118
  Use `/dev/ttySL129' as modem device, Ctrl+C for termination.

The "/dev/bus/usb/002/002" parameter will be different on your computer.

This works on my computer running the 32-bit i386 build, but 64-bit amd64 is incompatible on the same computer because the sl-modem-source package is missing.