Ekkehard, Because there is a precompiled 32 bit component in the slamr code, the driver can never work with a 64 bit installation. MarvS scanModem maintainer On Wed, Feb 23, 2011 at 9:33 PM, Antonio Olivares <olivares14031@xxxxxxxxx> wrote: > Ekkehard, > > scanModem reports what you have written, however the driver that you > need is slamr which works well for 32 bit linux not 64 bit one :( > > (slmodemd + alsa) does not serve this modem, that is why you see the errors. > > Predictive Âdiagnostics for card in bus 04:07.0: >    Modem chipset Âdetected on > NAME="Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT " > CLASS=0703 > PCIDEV=2000:2800 > SUBSYS=122d:2800 > IRQ=22 > HDA2=00:14.2 > HDA2=01:05.1 > IDENT=slamr > > ÂFor candidate modem in: Â04:07.0 > Â0703 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT >   Primary device ID: Â2000:2800 > ÂSupport type needed or chipset:    Âslamr > > > > There is a package sl-modem-source providing a source code the modem driver Â, > If can be searched for at http://pacakge.ubuntu.com. ÂAfter downloading > install under Linux with: > Â$ sudo dpkg -i sl*.deb > It is preferable to install the dkms package first. > With DKMS support installed, driver updates with kernel updates will be > automatically done. > > The modem is supported by the Smartlink > plus the slmodemd helper utility. ÂRead the > DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance. > > > For 2.6.35-25-generic compiling drivers is necessary. As of October 2007 the > current packages at > http://linmodems.technion.ac.il/packages/smartlink/ Âare the > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz > > Writing DOCs/Smartlink.txt > ============ end Smartlink section ===================== > > > To get the modem working you would need 32 bit linux, unless you are > willing to experiment and see if you can get it to work?, the driver > slamr.ko and ungrab-winmodem.ko need to be part of the system and > there have been no success reports for 64 bit versions of linux. > > Regards, > > Antonio > > On Wed, Feb 23, 2011 at 8:17 PM, W. Ekkehard Blanz > <ekkehard.blanz@xxxxxxxxx> wrote: >> Did anybody get the slmodem daemon with ALSA drivers running in a Kubuntu >> 10.10 64 bit system? >> >> Here is my general system HW info: >> ASUS motherboard M4A88TD-V EVO/USB3 featuring >>  Âan AMD 880G / SB850 chipset >>  Âan integrated ATI Radeon HD 4250 GPU >>  Âa Realtek 8111E Gigabit LAN controller >>  Âan ALC892 8 channel High Definition Audio >> 8 GB ÂADATA DDR3 1600G memory >> AMD Phenom II X6 1055T processor >> >> And the relevant software is: >> Kubuntu 10.10 (maverick) Âamd64 >> 2.6.35-25-generic kernel >> ALSA version=1.0.23 >> SmartLink Soft Modem: version=2.9.11 Sep Â6 2010 13:40:56 >> dkms version=2.1.1.2 >> >> The modem is (from scanModem): >> NAME="Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT " >> CLASS=0703 >> PCIDEV=2000:2800 >> SUBSYS=122d:2800 >> IRQ=22 >> HDA2=00:14.2 >> HDA2=01:05.1 >> IDENT=slamr >> >> I had that same modem running just fine for occasional fax use in Kubuntu 10.04 >> 32 bit using the packages dkms, sl-modem-source, and sl-modem-daemon. ÂAfter >> upgrading to a 64 bit system, sl-modem-source is no longer available. ÂHence, >> I was trying to get the modem working with the ALSA drivers (the alsa-base >> package is installed), since the dkms and sl-modem-daemon packages still exist >> in my distro, which I installed both. ÂBut I wasn't successful. >> >> I tried: >> >> sudo slmodemd -c USA --alsa hw:0,0 Â(that correct??) >> >> which gave me: >> >> error: mixer setup: Off-hook switch not found for card hw:0 >> SmartLink Soft Modem: version 2.9.11 Sep Â6 2010 13:40:56 >> symbolic link `/dev/ttySL0' -> `/dev/pts/3' created. >> modem `hw:0,0' created. TTY is `/dev/pts/3' >> Use `/dev/ttySL0' as modem device, Ctrl+C for termination. >> >> but that didn't do the trick. ÂFirst, it needed to up its locked memory limit >> (that OK??), after I did that, it created a device and a link to it (I also >> created the /dev/modem link that efax wants) but whenever I tried to use it, >> it gave me the error message: >> >> error: cannot set channels for playback: Invalid argument >> >> regardless of whether I used it with efax or wvdial. >> >> What am I doing wrong? >> >> I'd be thankful for any suggestions! >> >> Ekkehard >> >> ÂP.S. content of ModemData.txt >> -------------------------- ÂSystem information ---------------------------- >> CPU=x86_64, ÂUbuntu , ÂALSA_version=1.0.23 >> Linux version 2.6.35-25-generic (buildd@crested) (gcc version 4.4.5 >> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC 2011 >> ÂscanModem update of: Â2011_02_04 >> The modem symbolic link is /dev/modem -> ttySL0 >> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/3 >> Distrib_ID=Ubuntu >> DistribCodeName=maverick >> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >> >> >> The dkms driver upgrade utilities are installed, >> >> >> Some modem drivers can only be used in 32 bit modem on x86_64 systems, >> while some others are competent on x86_64 Systems. ÂCases are: >> 1) http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html >> for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem >> controllers. >> In both cases, 32 bit libraries must be installed to support the slmodemd >> helper having a precompiled 32 bit component. >> 2) For USB modems using the slusb.ko driver. 32 bit libraries must be >> installed to support the slmodemd helper having a precompiled 32 bit component >> 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are x86_64 >> competent. >> 4) agrsm packages for LSI/AgereSystems softmodems are not competent on x86_64 >> systems. >> >> ÂThere are no blacklisted modem drivers in /etc/modprobe* Âfiles >> >> ÂPotentially useful modem drivers now loaded are: >> Âsnd_atiixp_modem snd_via82xx_modem snd_intel8x0m  snd_hda_intel >> >> Attached USB devices are: >> ÂID 058f:9410 Alcor Micro Corp. Keyboard >> ÂID 045e:008c Microsoft Corp. Wireless Intellimouse Explorer 2.0 >> ÂID 047d:2043 Kensington >> ÂID 8054:0001 >> ÂID 04a9:1051 Canon, Inc. BJC-3000 Color Printer >> ÂID 046d:c215 Logitech, Inc. Extreme 3D Pro >> ÂID 04f9:002b Brother Industries, Ltd Printer >> ÂID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. >> transcend storejet 25P >> ÂID 058f:6254 Alcor Micro Corp. USB Hub >> ÂID 046d:081b Logitech, Inc. >> If a cellphone is not detected, see >> http://ubuntuforums.org/archive/index.php/t-878554.html >> A sample report is: Âhttp://linmodems.technion.ac.il/bigarch/archive- >> nineth/msg00578.html >> >> If a USB modem or cellphone is attached and was not detected, please >> provide available information in your request to discuss@xxxxxxxxxxxxx >> >> Candidate PCI devices with modem chips are: >> 04:07.0 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT (rev 02) >> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) (rev 40) >> 01:05.1 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] >> High Definition Audio cards can host modem chips. >> >> For candidate card in slot 04:07.0, firmware information and bootup diagnostics >> are: >> ÂPCI slot    PCI ID     ÂSubsystemID   Name >> Â----------   ---------    ---------    -------------- >> Â04:07.0    Â2000:2800    122d:2800    Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI >> Soft DFT >> >> ÂModem interrupt assignment and sharing: >> Â--- Bootup diagnostics for card in PCI slot 04:07.0 ---- >> [  Â1.350060] pci 0000:04:07.0: reg 10: [mem 0xfc000000-0xfcffffff pref] >> [  Â1.350104] pci 0000:04:07.0: PME# supported from D3hot D3cold >> [  Â1.350107] pci 0000:04:07.0: PME# disabled >> [  Â2.302915] serial 0000:04:07.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 >> [  Â2.302918] serial 0000:04:07.0: PCI INT A disabled >> >> ÂThe PCI slot 04:07.0 of the modem card may be disabled early in >> Âa bootup process, Âbut then enabled later. If modem drivers load >> Âbut the Âmodem is not responsive, read DOCs/Bootup.txt about possible fixes. >> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> Âif help is needed. >> >> >> For candidate card in slot 00:14.2, firmware information and bootup diagnostics >> are: >> ÂPCI slot    PCI ID     ÂSubsystemID   Name >> Â----------   ---------    ---------    -------------- >> Â00:14.2    Â1002:4383    1043:841b    Audio device: ATI Technologies Inc SBx00 Azalia >> >> ÂModem interrupt assignment and sharing: >> Â16:     Â0     Â0     Â0     Â0    4803    Â500  IO- >> APIC-fasteoi  hda_intel >> Â--- Bootup diagnostics for card in PCI slot 00:14.2 ---- >> [  Â1.307759] pci 0000:00:14.2: reg 10: [mem 0xfe7f8000-0xfe7fbfff 64bit] >> [  Â1.307784] pci 0000:00:14.2: PME# supported from D0 D3hot D3cold >> [  Â1.307786] pci 0000:00:14.2: PME# disabled >> [  16.629439] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ >> 16 >> >> ÂThe PCI slot 00:14.2 of the modem card may be disabled early in >> Âa bootup process, Âbut then enabled later. If modem drivers load >> Âbut the Âmodem is not responsive, read DOCs/Bootup.txt about possible fixes. >> ÂSend dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx >> Âif help is needed. >> >> >> For candidate card in slot 01:05.1, firmware information and bootup diagnostics >> are: >> ÂPCI slot    PCI ID     ÂSubsystemID   Name >> Â----------   ---------    ---------    -------------- >> Â01:05.1    Â1002:970f    1043:843e    Audio device: ATI Technologies Inc RS880 Audio >> Device [Radeon HD 4200] >> >> ÂModem interrupt assignment and sharing: >> Â19:     Â0     Â0   523806     Â0     Â2     81  IO- >> APIC-fasteoi  ahci, hda_intel >> Â--- Bootup diagnostics for card in PCI slot 01:05.1 ---- >> [  Â1.308136] pci 0000:01:05.1: reg 10: [mem 0xfe9e8000-0xfe9ebfff] >> [  Â1.308149] pci 0000:01:05.1: supports D1 D2 >> [  16.733510] HDA Intel 0000:01:05.1: PCI INT B -> GSI 19 (level, low) -> IRQ >> 19 >> [  16.733567] HDA Intel 0000:01:05.1: setting latency timer to 64 >> >> === Finished firmware and bootup diagnostics, next deducing cogent software. >> === >> >> Predictive Âdiagnostics for card in bus 04:07.0: >>    ÂModem chipset Âdetected on >> NAME="Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT " >> CLASS=0703 >> PCIDEV=2000:2800 >> SUBSYS=122d:2800 >> IRQ=22 >> HDA2=00:14.2 >> HDA2=01:05.1 >> IDENT=slamr >> >> ÂFor candidate modem in: Â04:07.0 >>  0703 Modem: Smart Link Ltd. SmartPCI2800 V.92 PCI Soft DFT >>   ÂPrimary device ID: Â2000:2800 >> ÂSupport type needed or chipset:    Âslamr >> >> >> >> There is a package sl-modem-source providing a source code the modem driver Â, >> If can be searched for at http://pacakge.ubuntu.com. ÂAfter downloading >> install under Linux with: >> Â$ sudo dpkg -i sl*.deb >> It is preferable to install the dkms package first. >> With DKMS support installed, driver updates with kernel updates will be >> automatically done. >> >> The modem is supported by the Smartlink >> plus the slmodemd helper utility. ÂRead the >> DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through guidance. >> >> >> For 2.6.35-25-generic compiling drivers is necessary. As of October 2007 the >> current packages at >> http://linmodems.technion.ac.il/packages/smartlink/ Âare the >> ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz >> >> Writing DOCs/Smartlink.txt >> ============ end Smartlink section ===================== >> >> >> Predictive Âdiagnostics for card in bus 00:14.2: >>    ÂModem chipset not detected on >> NAME="Audio device: ATI Technologies Inc SBx00 Azalia " >> CLASS=0403 >> PCIDEV=1002:4383 >> SUBSYS=1043:841b >> IRQ=16 >> >> ÂFor candidate modem in: Â00:14.2 >>  0403 Audio device: ATI Technologies Inc SBx00 Azalia >>   ÂPrimary device ID: Â1002:4383 >> ÂSupport type needed or chipset: >> >> >> >> Predictive Âdiagnostics for card in bus 01:05.1: >>    ÂModem chipset not detected on >> NAME="Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200]" >> CLASS=0403 >> PCIDEV=1002:970f >> SUBSYS=1043:843e >> IRQ=19 >> >> ÂFor candidate modem in: Â01:05.1 >>  0403 Audio device: ATI Technologies Inc RS880 Audio Device [Radeon HD 4200] >>   ÂPrimary device ID: Â1002:970f >> ÂSupport type needed or chipset: >> >> >> ÂCompleted candidate modem analyses. >> >> ÂThe base of the UDEV device file system is: /dev/.udev >> >> ÂVersions adequately match for the compiler installed: 4.4.5 >>       and the compiler used in kernel assembly: 4.4.5 >> >> Âlinux-headers-2.6.35-25-generic resources needed for compiling are not >> manifestly ready! >> >> ÂIf compiling is necessary packages must be installed, providing: >>     linux-headers-2.6.35-25-generic >> >> >> If a driver compilation fails, with message including some lack of some >> FileName.h (stdio.h for example), then >> Some additional kernel-header files need installation to /usr/include. The >> minimal additional packages are libc6-dev >> and any of its dependents, under Ubuntu linux-libc-dev >> >> If an alternate ethernet connection is available, >> $ Âapt-get update >> $ Âapt-get -s install linux-kernel-devel >> will install needed packages. >> For Debian/Ubuntu related distributions, run the following command to display >> the needed package list: >> >> Otherwise packages have to be found through http://packages.ubuntu.com >> Once downloaded and transferred into a Linux partition, >> they can be installed alltogether with: >> $ sudo dpkg -i *.deb >> >> Checking settings of:  /etc/ppp/options >> asyncmap 0 >> noauth >> crtscts >> lock >> hide-password >> modem >> proxyarp >> lcp-echo-interval 30 >> lcp-echo-failure 4 >> noipx >> >> In case of a message like: >>  Warning: Could not modify /etc/ppp/pap-secrets: Permission denied >> see http://linmodems.technion.ac.il/bigarch/archive-sixth/msg04656.html >> >> For guidance on FAX usage, get from http://linmodems.technion.ac.il/packages/ >> get faxing.tar.gz >> It has samples for a modem using port /dev/ttySL0, which must be changed to >> match your modem's port. >> >> Read Modem/DOCs/YourSystem.txt concerning other COMM channels: eth0 >> Which can interfere with Browser naviagation. >> >> ÂDon't worry about the following, it is for experts should trouble shooting be >> necessary. >> ========================================================== >> >> ÂChecking for modem support lines: >> Â-------------------------------------- >>   /device/modem symbolic link:  lrwxrwxrwx 1 root root 6 2011-02-23 14:03 >> /dev/modem -> ttySL0 >> slmodemd created symbolic link /dev/ttySL0: Âlrwxrwxrwx 1 root root 10 >> 2011-02-23 15:33 /dev/ttySL0 -> /dev/pts/3 >>   Within /etc/udev/ files: >> >>   Within /etc/modprobe.conf files: >> /etc/modprobe.d/blacklist-modem.conf:# Uncomment these entries in order to >> blacklist unwanted modem drivers >> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-atiixp-modem >> /etc/modprobe.d/blacklist-modem.conf:# blacklist snd-via82xx-modem >> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2 >> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2 >> /etc/modprobe.d/sl-modem.conf:install slamr /sbin/modprobe -qb ungrab- >> winmodem; /sbin/modprobe --ignore-install slamr; test -e /dev/slamr0 && (chmod >> 660 /dev/slamr0 && chgrp dialout /dev/slamr0) || (/bin/mknod -m 660 >> /dev/slamr0 c 242 0 2>/dev/null && chgrp dialout /dev/slamr0) >> /etc/modprobe.d/sl-modem.conf:install slusb /sbin/modprobe -qb ungrab- >> winmodem; /sbin/modprobe --ignore-install slusb; test -e /dev/slusb0 && (chmod >> 660 /dev/slusb0 && chgrp dialout /dev/slusb0) || (/bin/mknod -m 660 >> /dev/slusb0 c 243 0 2>/dev/null && chgrp dialout /dev/slusb0) >>   Within any ancient /etc/devfs files: >> >>   Within ancient kernel 2.4.n /etc/module.conf files: >> >> --------- end modem support lines -------- >> >> >> >
