You know what? After watching the exchange on this email, I've decided to migrate to the 64-bit version of KUbuntu and just give up on Linux ever giving modems the respect they deserve. I'll have to keep a Windows partition around to send a fax when I don't feel like paying $2 to that Internet fax site. Please unsubscribe me from this bug.
On May 3, 2010 at 5:30 PM "أحمد المحمودي (Ahmed El-Mahmoudy)" <[email protected]> wrote: > ** Description changed: > > Ever since I updated to Jaunty, I cannot access the Winmodem in my > Thinkpad X24 any longer. This used to work fine in Hardy. I think I > have the necessary packages installed and even upgraded to the PPA > packages from Ahmed, the Debian maintainer. The dkms module is compiled > fine, there just is no /dev/ttySL0 device node. /dev/modem thus points > into nirvana. > > $ dpkg -l sl-modem* dkms > Desired=Unknown/Install/Remove/Purge/Hold > | >Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: >uppercase=bad) > ||/ Name Version Description > > +++-=========================-=========================-====================== >============================================ > ii dkms 2.0.21.1-0ubuntu3 Dynamic Kernel >Module Support Framework > ii sl-modem-daemon 2.9.11~20090222-1~ppa1 SmartLink software >modem daemon > un sl-modem-modules <none> (no description >available) > un sl-modem-modules-new <none> (no description >available) > ii sl-modem-source 2.9.11~20090222-1~ppa1 SmartLink software >modem driver - module building source > > - $ ll /dev/modem > + $ ll /dev/modem > lrwxrwxrwx 1 root root 6 2009-05-11 23:33 /dev/modem -> ttySL0 > + > + > + =========== Test case ============== > + > + * ALSA (uses snd_atiixp_modem module) > + In /etc/default/sl-modem-daemon: > + SLMODEMD_DEVICE=modem:1 > + > + $ sudo invoke-rc.d sl-modem-daemon start > + Starting SmartLink Modem driver for: modem:1. > + Creating /dev/modem symlink, pointing to: /dev/ttySL0. > + > + $ ls -l /dev/ttySL0 > + lrwxrwxrwx 1 root root 10 2010-03-25 03:48 /dev/ttySL0 -> /dev/pts/2 > + > + $ ls -l /dev/pts/2 > + crw-rw---- 1 root dialout 136, 2 2010-03-25 03:51 /dev/pts/2 > + > + $ sudo invoke-rc.d sl-modem-daemon stop > + Shutting down SmartLink Modem driver normally. > + Unloading modem driver from kernel ... snd_atiixp_modem. > + > + * slamr > + In /etc/default/sl-modem-daemon: > + SLMODEMD_DEVICE=slamr0 > + > + $ sudo invoke-rc.d sl-modem-daemon start > + Starting SmartLink Modem driver for: slamr0. > + Creating /dev/modem symlink, pointing to: /dev/ttySL0. > + > + $ ls -l /dev/ttySL0 > + lrwxrwxrwx 1 root root 10 2010-03-25 04:00 /dev/ttySL0 -> /dev/pts/1 > + > + $ ls -l /dev/pts/1 > + crw-rw---- 1 root dialout 136, 1 2010-03-25 04:00 /dev/pts/1 > + > + * Dialup to internet (in both cases: ALSA & slamr) is done with wvdial, > + I have the following setting in wvdial.conf: > + > + Carrier Check = no > + > + * Tested fax sending using efax, and it sent faxes. Of course that only > + works with slamr module. > > -- > no more /dev/ttySL0 device node > https://bugs.launchpad.net/bugs/375148 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “sl-modem” package in Ubuntu: Triaged > > Bug description: > Ever since I updated to Jaunty, I cannot access the Winmodem in my Thinkpad > X24 any longer. This used to work fine in Hardy. I think I have the > necessary packages installed and even upgraded to the PPA packages from Ahmed, > the Debian maintainer. The dkms module is compiled fine, there just is no > /dev/ttySL0 device node. /dev/modem thus points into nirvana. > > $ dpkg -l sl-modem* dkms > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: > uppercase=bad) > ||/ Name Version Description > +++-=========================-=========================-====================== > ============================================ > ii dkms 2.0.21.1-0ubuntu3 Dynamic Kernel Module > Support Framework > ii sl-modem-daemon 2.9.11~20090222-1~ppa1 SmartLink software > modem daemon > un sl-modem-modules <none> (no description > available) > un sl-modem-modules-new <none> (no description > available) > ii sl-modem-source 2.9.11~20090222-1~ppa1 SmartLink software > modem driver - module building source > > $ ll /dev/modem > lrwxrwxrwx 1 root root 6 2009-05-11 23:33 /dev/modem -> ttySL0 > > > =========== Test case ============== > > * ALSA (uses snd_atiixp_modem module) > In /etc/default/sl-modem-daemon: > SLMODEMD_DEVICE=modem:1 > > $ sudo invoke-rc.d sl-modem-daemon start > Starting SmartLink Modem driver for: modem:1. > Creating /dev/modem symlink, pointing to: /dev/ttySL0. > > $ ls -l /dev/ttySL0 > lrwxrwxrwx 1 root root 10 2010-03-25 03:48 /dev/ttySL0 -> /dev/pts/2 > > $ ls -l /dev/pts/2 > crw-rw---- 1 root dialout 136, 2 2010-03-25 03:51 /dev/pts/2 > > $ sudo invoke-rc.d sl-modem-daemon stop > Shutting down SmartLink Modem driver normally. > Unloading modem driver from kernel ... snd_atiixp_modem. > > * slamr > In /etc/default/sl-modem-daemon: > SLMODEMD_DEVICE=slamr0 > > $ sudo invoke-rc.d sl-modem-daemon start > Starting SmartLink Modem driver for: slamr0. > Creating /dev/modem symlink, pointing to: /dev/ttySL0. > > $ ls -l /dev/ttySL0 > lrwxrwxrwx 1 root root 10 2010-03-25 04:00 /dev/ttySL0 -> /dev/pts/1 > > $ ls -l /dev/pts/1 > crw-rw---- 1 root dialout 136, 1 2010-03-25 04:00 /dev/pts/1 > > * Dialup to internet (in both cases: ALSA & slamr) is done with wvdial, > I have the following setting in wvdial.conf: > > Carrier Check = no > > * Tested fax sending using efax, and it sent faxes. Of course that only > works with slamr module. > > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/sl-modem/+bug/375148/+subscribe Roland Hughes, President Logikal Solutions (630)-205-1593 - cell http://www.theminimumyouneedtoknow.com http://www.infiniteexposure.net -- no more /dev/ttySL0 device node https://bugs.launchpad.net/bugs/375148 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
