iki Try using > http://linmodems.technion.ac.il/packages/smartlink/ are the > ungrab-winmodem-20070505.tar.gz and slmodem-2.9.11-20080126.tar.gz as I can no longer assemble a package as old as 2.6.24 on my Jaunty system. If you are just starting usage of Ubuntu, you would be better served doing an installation with the new Jaunty release, as maintenance thereafter is much easier. Let us know which route you are taking, for some more detailed advice to follow. MarvS scanModem maintainer On Fri, May 15, 2009 at 7:00 PM, iki sham <ikisham@xxxxxxxxx> wrote: > Hi, I would like to know which slamr package I should download for my > kernel since there are versions 16, 17, 19 and 21 for the 2.6.24 > kernel while mine is version 24 (I have version 23 too). From here: > http://linmodems.technion.ac.il/packages/smartlink/Ubuntu/ > > Also I would like to know if I can follow these instructions: > http://linmodems.technion.ac.il/bigarch/archive-nineth/msg00539.html > > My country is Brazil. > > ModemData.txt: > > Only plain text email is forwarded by the Discuss@xxxxxxxxxxxxx List Server, > as HTML can contain viruses. Use as the email Subject Line: > YourName, YourCountry kernel 2.6.24-24-generic > With this Subject Line cogent experts will be alerted, and useful > case names left in the Archive. > YourCountry will enable Country specific guidance. Linux experts in > YourCountry > can be found through: http://www.linux.org/groups/index.html. > They will know your Country's modem code, which may be essential for > dialup service. > Responses from Discuss@xxxxxxxxxxxxx are sometimes blocked by an > Internet Provider mail filters. > So in a day, also check the Archived responses at http://www.linmodems.org > -------------------------- System information ---------------------------- > CPU=i686, > Linux version 2.6.24-24-generic (buildd@rothera) (gcc version 4.2.4 > (Ubuntu 4.2.4-1ubuntu4)) #1 SMP Wed Apr 15 15:54:25 UTC 2009 > scanModem update of: 2009_05_12 > The modem symbolic link is /dev/modem -> ttySL0 > 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 > > If a USB modem or cellphone is attached and was not detected, please > provide available information in your request to discuss@xxxxxxxxxxxxx > > For candidate card in slot 00:07.0, firmware information and bootup > diagnostics are: > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:07.0 1057:3052 1057:3020 Modem: Motorola SM56 Data Fax Modem > > Modem interrupt assignment and sharing: > --- Bootup diagnostics for card in PCI slot 00:07.0 ---- > [ 25.726819] ACPI: PCI Interrupt 0000:00:07.0[A] -> GSI 19 (level, > low) -> IRQ 16 > [ 25.728083] 0000:00:07.0: ttyS2 at I/O 0xd008 (irq = 16) is a 16450 > [ 25.728837] 0000:00:07.0: ttyS3 at I/O 0xd010 (irq = 16) is a 8250 > [ 25.729111] Couldn't register serial port 0000:00:07.0: -28 > [ 62.959839] ACPI: PCI interrupt for device 0000:00:07.0 disabled > > The PCI slot 00: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. > > > === Finished firmware and bootup diagnostics, next deducing cogent software. === > > Predictive diagnostics for card in bus 00:07.0: > Modem chipset detected on > NAME="Modem: Motorola SM56 Data Fax Modem " > CLASS=0703 > PCIDEV=1057:3052 > SUBSYS=1057:3020 > IRQ=16 > IDENT=slamr > > For candidate modem in: 00:07.0 > 0703 Modem: Motorola SM56 Data Fax Modem > Primary device ID: 1057:3052 > Support type needed or chipset: slamr > > > > 1057:3052 has a Motorola chipset, poorly supported by Motorola itself > However Zello discovered that drivers written to support Smartlink > modems do support the 1057:3052 chipset!! > It sufficed to add 1057:3052 to the list of modem cards recognized by > the Smartlink slamr driver. > There is a ungrab-winmodem driver used in conjunction with slamr, > which must have 1057:3052 > similarly added. See messages from Zello: > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00846.html > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00848.html > and Alvaro Aguirre about the ungrab-winmodem fix: > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00990.html > For general guidance on ungrab-winmodem + slamr usage, read the > DOCs/Smartlink.txt > > 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.24-24-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 ===================== > > Completed candidate modem analyses. > > The base of the UDEV device file system is: /dev/.udev > > Versions adequately match for the compiler installed: 4.2.4 > and the compiler used in kernel assembly: 4.2.4 > > > > Minimal compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.2 > linuc_headers base folder /lib/modules/2.6.24-24-generic/build > > However some compilations and executable functions may need additional files, > in the FileNames.h (so called kernel "h"eaders) collection installed > in /usr/include/ . > For martian_modem, additional required packages are needed. The also > required headers of package libc6 are commonly installed by default. > Compiling hsfmodem drivers does require linux-libc-dev and libc6-dev > packages, for kernels 2.6.24 and later versions. > In not included on your install CD, search for them at > http://packages.ubuntu.com > or comparable Repository for other Linux distros. > When compiling ALSA drivers, the utility "patch" will also be needed. > > > > > 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 pppd properties: > -rwsr-xr-- 1 root dip 269256 2007-10-04 16:57 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://linmodems.technion.ac.il/linmodems/archive-sixth/msg02637.html > > To enable dialout without Root permission do: > $ su - root (not for Ubuntu) > sudo chmod a+x /usr/sbin/pppd > or under Ubuntu related Linuxes > sudo chmod a+x /usr/sbin/pppd > > 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 > > 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. > ========================================================== > > # start/stop the daemon when the USB modem is connected > KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > Checking for modem support lines: > -------------------------------------- > /device/modem symbolic link: lrwxrwxrwx 1 root root 6 > 2009-05-15 19:20 /dev/modem -> ttySL0 > slmodemd created symbolic link /dev/ttySL0: > Within /etc/udev/ files: > /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon > when the USB modem is connected > /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB > modem is connected > /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", > GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon" > Within /etc/modprobe.conf files: > /etc/modprobe.d/sl-modem-daemon.modutils:install slamr modprobe > --ignore-install ungrab-winmodem ; modprobe --ignore-install slamr; > test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0 > 2>/dev/null && chgrp dialout /dev/slamr0) > /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2 > /etc/modprobe.d/alsa-base:options snd-via82xx-modem index=-2 > /etc/modprobe.d/blacklist-modem:# Uncomment these entries in order to > blacklist unwanted modem drivers > /etc/modprobe.d/blacklist-modem:# blacklist snd-atiixp-modem > /etc/modprobe.d/blacklist-modem:# blacklist snd-via82xx-modem > Within any ancient /etc/devfs files: > > Within ancient kernel 2.4.n /etc/module.conf files: > /etc/modules~:ungrab-winmodem > --------- end modem support lines -------- >
