Dan, These lines: > Setting up sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ... > Adding system user `Slmodemd' (UID 112) ... > Adding new group `Slmodemd' (GID 124) ... > Adding new user `Slmodemd' (UID 112) with group `Slmodemd' ... > Not creating home directory `/'. > FATAL: Module ungrab_winmodem not found. > FATAL: Module slamr not found. are created during preliminary install of the sl-modem-daemon package providing automation scripts. They evidently represent some update of this package, which I will check through. But all the succeeding lines of the install record are OK, and you should just proceed to test the modem. Do NOT again run $ sudo ./setup or the work which you will next do will be overwritten. First read the wvdial.txt info THen run (if it was not automatically done at the end of the ./setup) $ sudo wvdialconf /etc/wvdial.conf which should report finding the modem. Then edit in your personal info with: $ sudo gedit /etc/wvdial.conf removing the ; < > symbols and adding a line: Carrier Check = no Save. Try a dialout with $ sudo wvdial Between successive dialouts under the same bootup, you may find it necessary to: $ sudo /etc/init.d/sl-modem-daemon restart This nuisance represents more general Linux code changes and not a slamr driver issue per se. MarvS On Sat, Jul 19, 2008 at 4:51 AM, Dan <wade196884@xxxxxxxxxxx> wrote: > It looks like setup is having trouble: > > dan@dan-desktop:/media/disk/slamr-2.6.24-19-generic$ sudo ./setup > installing drivers for kernel version 2.6.24-19-generic > driver=slamr > > Installing the Debian packages supporting autoloading > Selecting previously deselected package sl-modem-daemon. > (Reading database ... 95844 files and directories currently installed.) > Unpacking sl-modem-daemon (from > sl-modem-daemon_2.9.10+2.9.9d+e-pre2-5ubuntu4_i386.deb) ... > Setting up sl-modem-daemon (2.9.10+2.9.9d+e-pre2-5ubuntu4) ... > Adding system user `Slmodemd' (UID 112) ... > Adding new group `Slmodemd' (GID 124) ... > Adding new user `Slmodemd' (UID 112) with group `Slmodemd' ... > Not creating home directory `/'. > FATAL: Module ungrab_winmodem not found. > FATAL: Module slamr not found. > Starting SmartLink Modem driver for: auto. > Creating /dev/modem symlink, pointing to: /dev/ttySL0. > > > Copying over newer files > Making folder /lib/modules/2.6.24-19-generic/extra > Copying drivers to /lib/modules/2.6.24-19-generic/extra > Checking driver install > slamr.ko slusb.ko ungrab-winmodem.ko > Copying newer slmodemd to /usr/sbin/ > Checking slmodemd version. Should be 2.9.11 > SmartLink Soft Modem: version 2.9.11 Apr 28 2008 08:04:56 > Finished installs. > Informing the System > > Starting function tests, loading drivers: > Running diagnostic: > > [ 289.856532] slamr: module license 'Smart Link Ltd.' taints kernel. > [ 289.862020] slamr: SmartLink AMRMO modem. > [ 289.862366] slamr: probe 1057:3052 SL1900 card... > [ 290.087728] slamr: slamr0 is SL1900 card. > > ports should be created by: > slmodemd -c USA /dev/slamr0 > SmartLink Soft Modem: version 2.9.11 Apr 28 2008 08:04:56 > symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > modem `slamr0' created. TTY is `/dev/pts/1' > Use `/dev/ttySL0' as modem device, Ctrl+C for termination. > > > > > -- > Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ > ____________________________________________________________ > Stuck in a dead end job?? Click to start living your dreams by earning an > online degree. > http://thirdpartyoffers.netzero.net/TGL2241/fc/Ioyw6i4uI3ttrrlsKo96VQQPIeNiJudWKV4O2pQvr3IIhdI1HAybko/ >
