Just reboot. Nothing has been harmed. Do $ sudo gedit /etc/default/sl-modem-daemon and change the default country from USA to your CANADA. Then inform the slmodemd by rebooting or $ sudo /etc/init.d/sl-modem-daemon restart $ ls -l /dev/ttySL0 /dev/pts/* /dev/slamr0 should report these ports setup, and also after any reboot, with * being some number N, /dev/tttySL0 -->/dev/pts/N is a symbolic link to the real port, some /dev/pts/N So to dail out, all that should now be needed is $ sudo wvdial MarvS On Thu, Jun 24, 2010 at 6:59 PM, <beepzapmdm.amabel@xxxxxxxxxxxx> wrote: > i've installed dkms_2.1.1.2-2fakesync1_all.deb by getting the deb on the > internet. > > > I installed wvdial through Ubuntu Software Centre. > > I then did: > "sudo apt-get install sl-modem-source sl-modem-daemon" > > Here're the results: > > > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following NEW packages will be installed: > sl-modem-daemon sl-modem-source > 0 upgraded, 2 newly installed, 0 to remove and 121 not upgraded. > Need to get 779kB of archives. > After this operation, 2,138kB of additional disk space will be used. > Get:1 http://ca.archive.ubuntu.com/ubuntu/ lucid/restricted sl-modem-daemon > 2.9.11~20100303-2 [518kB] > Get:2 http://ca.archive.ubuntu.com/ubuntu/ lucid/multiverse sl-modem-source > 2.9.11~20100303-2 [261kB] > Fetched 779kB in 9s (78.4kB/s) > Preconfiguring packages ... > Selecting previously deselected package sl-modem-daemon. > (Reading database ... 128207 files and directories currently installed.) > Unpacking sl-modem-daemon (from > .../sl-modem-daemon_2.9.11~20100303-2_i386.deb) ... > Selecting previously deselected package sl-modem-source. > Unpacking sl-modem-source (from > .../sl-modem-source_2.9.11~20100303-2_i386.deb) ... > Processing triggers for man-db ... > Processing triggers for ureadahead ... > ureadahead will be reprofiled on next reboot > Setting up sl-modem-daemon (2.9.11~20100303-2) ... > Warning: The home directory /var/log/slmodemd you specified can not be > accessed: No such file or directory > Adding system user `Slmodemd' (UID 116) ... > Adding new group `Slmodemd' (GID 124) ... > Adding new user `Slmodemd' (UID 116) with group `Slmodemd' ... > Not creating home directory `/var/log/slmodemd'. > usermod: no changes > Starting SmartLink Modem driver for: slamr0. > Creating /dev/modem symlink, pointing to: /dev/ttySL0. > > Setting up sl-modem-source (2.9.11~20100303-2) ... > Loading new sl-modem-2.9.11~20100303 DKMS files... > First Installation: checking all kernels... > Building only for 2.6.32-22-generic > Building for architecture i686 > Building initial module for 2.6.32-22-generic > Done. > > slamr.ko: > Running module version sanity check. > - Original module > - Installation > - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/ > > ungrab-winmodem.ko: > Running module version sanity check. > - Original module > - Installation > - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/ > > slusb.ko: > Running module version sanity check. > - Original module > - Installation > - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/ > > depmod.... > > DKMS: install Completed. > Shutting down SmartLink Modem driver normally. > Unloading modem driver from kernel ... slamr. > ERROR: Module slamr does not exist in /proc/modules > dpkg: error processing sl-modem-source (--configure): > subprocess installed post-installation script returned error exit status 1 > Errors were encountered while processing: > sl-modem-source > E: Sub-process /usr/bin/dpkg returned an error code (1) > > ------------------ > > > I haven't restarted the computer yet, so I don't know whether what you wrote > in your first email (6:14pm June 23 Wed Pacific time) will work: > > > ---Marvin's advice --- > The modem should setup automatically upon bootup. > You will have once: > $ sudo wvdialconf > and then follow Antonio's instructions: > $ sudo gedit /etc/wvdial.conf > remove symbols ; < > > and add username/ISP phone no > and a line > Carrier Check = no > and Save > > Try to connect with: > $ sudo wvdial > > --- end of advice ----- > > > > > >
