RE: > # bash: slmodem: command not found The command is slmodemd , not slmodem Also use USA, not b5 # slmodem --country=USA --alsa modem:1 But first do: # cat /proc/asound/pcm which ouput should include a line 01-00: Modem something Intel ICH4 If it is not there, there is a resource conflict. Primary candidates would be drivers/hardware sharing the IRQ 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, ehci_hcd, Try blacklisting these drivers. See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg01842.html on blacklisting guidance. MarvS On Tue, Jun 24, 2008 at 9:45 AM, postid <postid@xxxxxxxxxxxx> wrote: > On Tuesday 24 June 2008 06:53 pm, Antonio Olivares wrote: >> Many things look fine, you have setup the modem correctly. AT least >> one problem is >> >> /**** scanModem output ****/ >> Modem interrupt assignment and sharing: >> 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, ehci_hcd, >> uhci_hcd, uhci_hcd, uhci_hcd, eth2, radeon@PCI:1:0:0, eth0 >> --- Bootup diagnostics for card in PCI slot 0000:00:1f.6 ---- >> ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) -> IRQ 11 >> ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) -> IRQ 11 >> >> Packages needed for support of Advanced Linux Sound Architecture (ALSA) >> support should be installed: alsa-base and alsa-utilities!! >> They are necessary for support of ALSA modem drivers, many Conexant >> chipset modems and success of modem diagnostics for modems requiring >> slmodemd actions. >> /**** scanModem output ****/ >> >> You do not have packages alsa-base and alsa-utilities. :( Apparently >> this is what is holding the modem back from functioning. >> > Pardon me for forgetting to mention that I did follow the instruction to > install alsa-base and alsa-utils. This computer had OSS installed previously. > >> If you install those packages and the problem persists, then something >> else is getting in the way. > > When I do as instructed in slmodem-ALSA.txt > > # slmodem --country=b5 --alsa hw:1 > > or > > # slmodem --country=b5 --alsa hw:0 > > > I get the following response: > > # bash: slmodem: command not found > > I have slmodemd in /usr/sbin and the command produced an error message > before. What did I do wrong? >> >> Regards, >> >> Antonio >> >> On 6/24/08, postid <postid@xxxxxxxxxxxx> wrote: >> > A few years ago I tried to get this working (see archives for Red Hat >> > 2.4.20-20.9 on IBM R40 with Agere softmoden) but the Agere driver once >> > available through IBM gave flaky performance. I've been using a PCMCIA >> > modem, >> > but it recently got fried by a campus phone system so I'm back to looking >> > at the internal modem. This time I'm using Debian Sarge, but hope to >> > upgrade when Lenny goes stable. >> > >> > I ran scanmodem, then followed the directions to download >> > SLMODEMD.gcc3.3.tar.gz, then followed the directions found there to >> > install the ALSA packages, then do: >> > >> > R40:/home/ellsworth# cp slmodemd /usr/sbin >> > R40:/home/ellsworth# modprobe snd-intel8x0m >> > >> > At the next steps I got errors: >> > >> > R40:/home/ellsworth# slmodemd --alsa -c b5 modem:1 >> > error: mixer setup: attach hw:1 error: No such file or directory >> > ALSA lib pcm.c:1947:(snd_pcm_open_conf) Invalid type for PCM modem:1 >> > definition (id: modem, value: cards.pcm.modem) >> > error: alsa setup: cannot open playback device 'modem:1': Invalid >> > argument error: cannot setup device `modem:1' >> > R40:/home/ellsworth# modprobe -r snd-intel8x0m >> > R40:/home/ellsworth# modprobe snd-intel8x0m >> > R40:/home/ellsworth# cat /proc/asound/pcm >> > 00-00: Intel ICH - Modem : Intel 82801DB-ICH4 Modem - Modem : playback 1 >> > : capture 1 >> > R40:/home/ellsworth# slmodemd --alsa -c b5 modem:1 >> > error: mixer setup: attach hw:1 error: No such file or directory >> > ALSA lib pcm.c:1947:(snd_pcm_open_conf) Invalid type for PCM modem:1 >> > definition (id: modem, value: cards.pcm.modem) >> > error: alsa setup: cannot open playback device 'modem:1': Invalid >> > argument error: cannot setup device `modem:1' >> > R40:/home/ellsworth# >> > >> > I'm getting in over my head again. Advice? >> > >> > >> > >> > 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 Debian GNU/Linux 3.1 kernel 2.6.8-2-686 >> > 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, Debian GNU/Linux 3.1 >> > Linux version 2.6.8-2-686 (dilinger@xxxxxxxxxxxxxxxxxxxx) (gcc version >> > 3.3.5 (Debian 1:3.3.5-6)) #1 Mon Jan 24 03:58:38 EST 2005 >> > scanModem update of: 2008_06_17 >> > >> > There are no blacklisted modem drivers in /etc/modprobe* files >> > USB modems not recognized >> > >> > For candidate card in slot 0000:00:1f.6, firmware information and bootup >> > diagnostics are: >> > PCI slot PCI ID SubsystemID Name >> > ---------- --------- --------- -------------- >> > 0000:00:1f.6 8086:24c6 1014:0524 Modem: Intel Corp. 82801DB/DBL/DBM >> > >> > Modem interrupt assignment and sharing: >> > 11: 135715 XT-PIC yenta, ohci1394, Intel ICH4, ehci_hcd, >> > uhci_hcd, uhci_hcd, uhci_hcd, eth2, radeon@PCI:1:0:0, eth0 >> > --- Bootup diagnostics for card in PCI slot 0000:00:1f.6 ---- >> > ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) -> IRQ 11 >> > ACPI: PCI interrupt 0000:00:1f.6[B] -> GSI 11 (level, low) -> IRQ 11 >> > >> > >> > Packages needed for support of Advanced Linux Sound Architecture (ALSA) >> > support should be installed: alsa-base and alsa-utilities!! >> > They are necessary for support of ALSA modem drivers, many Conexant >> > chipset modems and success of modem diagnostics for modems requiring >> > slmodemd actions. >> > >> > === Finished firmware and bootup diagnostics, next deducing cogent >> > software. === >> > >> > Predictive diagnostics for card in bus 0000:00:1f.6: >> > Modem chipset detected on >> > NAME="Modem: Intel Corp. 82801DB/DBL/DBM " >> > CLASS=0703 >> > PCIDEV=8086:24c6 >> > SUBSYS=1014:0524 >> > IRQ=11 >> > SOFT=8086:24c6.MC97 >> > CodecArchived=SIL27 >> > IDENT=slmodemd >> > SLMODEMD_DEVICE=modem:1 >> > >> > For candidate modem in: 0000:00:1f.6 >> > 0703 Modem: Intel Corp. 82801DB/DBL/DBM >> > Primary device ID: 8086:24c6 >> > Subsystem PCI_id 1014:0524 >> > Softmodem codec or chipset from diagnostics: >> > from Archives: SIL27, an >> > LSI/AgereSystems type >> > >> > >> > >> > Support type needed or chipset: slmodemd >> > >> > An ALSA (Advanced Linux Sound Architecture) modem driver: >> > provides Low Level support enabling contact with the modem hardware. >> > For all BUT Conexant chip soft modems (using hsfmodem software) >> > complementary High Level support is through a Smartlink utility: >> > slmodemd >> > >> > Download from http://linmodems.technion.ac.il/packages/smartlink/ >> > the package SLMODEMD.gcc3.3.tar.gz having a compiled slmodemd. Unpack >> > under Linux with: >> > $ tar zxf SLMODEMD.gcc3.3.tar.gz >> > and read instructions therein. But briefly, the modem is setup with >> > command: >> > slmodemd -c YOUR_COUNTRY --alsa modem:1 >> > reporting dynamic creation of ports: >> > /dev/ttySL0 --> /dev/pts/N , with N some number >> > Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow through >> > guidance. >> > >> > ----------------end Softmodem section -------------- >> > >> > Writing DOCs/Intel.txt >> > Writing DOCs/Smartlink.txt >> > ============ end Smartlink section ===================== >> > >> > Completed candidate modem analyses. >> > >> > The base of the UDEV device file system is: /dev/.udevdb >> > >> > Versions adequately match for the compiler installed: 3.3.5 >> > and the compiler used in kernel assembly: 3.3.5 >> > >> > >> > >> > Minimal compiling resources appear complete: >> > make utility - /usr/bin/make >> > Compiler version 3.3 >> > linuc_headers base folder /lib/modules/2.6.8-2-686/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 libc6-dev (and for >> > Debian/Ubuntu, >> > linux-libc-dev). 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. >> > >> > >> > >> > kernel-kbuild is installed >> > >> > >> > 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 265880 2005-03-24 14:21 /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) >> > chmod a+x /usr/sbin/pppd >> > or under Ubuntu related Linuxes >> > chmod a+x /usr/sbin/pppd >> > >> > Checking settings of: /etc/ppp/options >> > asyncmap 0 >> > auth >> > 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 eth1 >> > eth2 >> > sit0 >> > 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: >> > slmodemd created symbolic link /dev/ttySL0: >> > Within /etc/udev/ files: >> > >> > Within /etc/modprobe.conf files: >> > >> > Within any ancient /etc/devfs files: >> > >> > Within ancient kernel 2.4.n /etc/module.conf files: >> > >> > --------- end modem support lines -------- >
