Edward, Apologies for $ sudo modprobe slusb.ko should have used syntax: $ sudo modprobe slusb that is the name of the driver , slusb, not the name of its software modules, slusb.ko This: $ sudo slmodemd -c SOUTHAFRICA /dev/slusb0 SmartLink Soft Modem: version 2.9.9e-pre1 Sep 30 2007 00:07:03 symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. -------- is OK in principle. But 2.9.9e-pre1 is an old version that came from the sl-modem-daemon package or the restricted drivers. The slmodemd in the package I sent you is: $ slamr-2.6.22-14-generic/slmodemd --version SmartLink Soft Modem: version 2.9.11 May 26 2007 13:41:57 So do $ sudo mv /usr/sbin/slmodemd /usr/sbin/slmodemd_2.9.9 and from within the slamr-2.6.22-14-generic/ folder $ sudo cp slmodemd /usr/sbin/slmodemd $ sudo chmod +x /usr/sbin/slmodemd Recheck the version $ slmodemd --version And retest as before. Try $ sudo modprobe slusb there should an autocreation of the device node, Check: $ ls -l /dev/slusb0 Then proceed from the $ sudo slmodemd -c SOUTHAFRICA /dev/slusb0 Leave slmodemd running, and do the modem testing from a 2nd console or TAB of the same console. If you kill the slmodemd, if will kill the /dev/ttySL0 --> /dev/pts/N MarvS
