Benito > error: locked memory limit too low: > error: need 8388608 bytes, have 65536 bytes This type of error, I don't recall. It likely is specific to your hardware setup, and is beyond my capability to help. Sorry MarvS On Mon, Apr 23, 2012 at 7:55 PM, <bflores@xxxxxxxxxxxxxx> wrote: > Hi Marvin, I did the following: > > ----------------------------------------------------- > $ tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz > $cd SLMODEMD_gcc4.4-alsa1.0.21 > $ sudo slmodemd -c USA --alsa hw:0,6 > SmartLink Soft Modem: version 2.9.11 Mar 22 2010 23:11:18 > symbolic link `/dev/ttySL0' -> `/dev/pts/1' created. > modem `hw:0,6' created. TTY is `/dev/pts/1' > error: locked memory limit too low: > error: need 8388608 bytes, have 65536 bytes > error: try 'ulimit -l 8192' > alexc@alexc-laptop:~/OmniDataLaptop/SLMODEMD_gcc4.4_alsa1.0.21$ > $ ulimit -l 8192 > bash: ulimit: max locked memory: cannot modify limit: Operation not > permitted > $ sudo ulimit -l 8192 > sudo: ulimit: command not found > -------------------------------------------------------- > > Also I did the following: > > -------------------------------------------------------- > $ sudo wvdialconf /etc/wvdial.conf > [sudo] password for alexc: > Editing `/etc/wvdial.conf'. > > Scanning your serial ports for a modem. > > Modem Port Scan<*1>: S0 > ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud > ttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > Modem Port Scan<*1>: S2 S3 > ATQ0 V1 E1>: Cannot get information for serial port. > ttySL0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud > ttySL0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baudQ0 > V1 E1 > ttySL0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. > ATQ0 V1 E1 > > > Sorry, no modem was detected! Is it in use by another program? > Did you configure it properly with setserial? > > Please read the FAQ at http://open.nit.ca/wiki/?WvDial > > If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. > ~$ > ------------------------------------------------------- > > > Sincerely > Benito Flores > bflores@xxxxxxxxxxxxxx > > > On 3/21/2012 8:29 PM, Marvin Stodolsky wrote: >> Benito, >> >> Since your System is Ubuntu Lucid, it will be simplest if you use the >> standard Ubuntu packages. >> All you need is the package sl-modem-daemon, available through >> searching at http://packages.ubuntu.com/ , which will take you to: >> http://packages.ubuntu.com/search?keywords=sl-modem-daemon&searchon=names&suite=lucid§ion=all >> >> After download install with: >> $ sudo dpkg -i sl*.deb >> The installed scripts will try to activate the modem, though the >> 0x10573055 modem chip is frequently troublesome. >> >> The modem driver support is included in the already installed >> snd-hda-intel driver. >> Check for modem detection with: >> $ sudo wvdialconf >> >> MarvS >> >> >> >> On Wed, Mar 21, 2012 at 9:26 PM, Antonio Olivares >> <olivares14031@xxxxxxxxx> wrote: >>> Dear Marv & List Members, >>> >>>> $ tar zxf SLMODEMD.2_gcc4.4_alsa1.0.20.tar.gz$ sudo slmodemd -c b5 >>>> --alsaerror: mixer setup: attach hw:1 error: No such file or >>>> directoryALSA lib confmisc.c:768:(parse_card) cannot find card '1'ALSA >>> Command example told you to do: >>> >>> $ sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6 >>> Leave it running, then with another terminal open: >>> >>> $ sudo wvdialconf /etc/wvdial.conf >>> and hopefully it finds /dev/ttySL0 as the modem port. >>> >>> Either way the package that you got says 1.20 alsa version when it >>> should be 1.21 as scanModem recommends: >>> >>> $ tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz >>> >>> If someone can clarify better/easier/faster way for Benito to get his >>> modem working, it is greatly appreciated. I tried but maybe my >>> instructions were not very precise? >>> >>> >>> ================================== >>> >>> Benito forwarded his ModemData.txt to list, but in case it is not >>> retrieved easily here it is: >>> >>> 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.32-21-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, Ubuntu , ALSA_version=1.0.21 >>> Linux version 2.6.32-21-generic (buildd@rothera) (gcc version 4.4.3 >>> (Ubuntu 4.4.3-4ubuntu5) ) #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 >>> scanModem update of: 2011_08_08 >>> >>> Distrib_ID=Ubuntu >>> DistribCodeName=lucid >>> AptRepositoryStem=http://us.archive.ubuntu.com/ubuntu/ >>> >>> >>> Presently install your Linux Distributions dkms package. It provides >>> for automated driver updates, >>> following upgrade of your kernel. For details see >>> http://linux.dell.com/projects.shtml#dkms >>> >>> There are no blacklisted modem drivers in /etc/modprobe* files >>> >>> Potentially useful modem drivers now loaded are: >>> snd_hda_intel >>> >>> 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: >>> 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 >>> Family) High Definition Audio Controller (rev 04) >>> High Definition Audio cards can host modem chips. >>> >>> For candidate card in slot 00:1b.0, firmware information and bootup >>> diagnostics are: >>> PCI slot PCI ID SubsystemID Name >>> ---------- --------- --------- -------------- >>> 00:1b.0 8086:2668 152d:0729 Audio device: Intel Corporation >>> 82801FB/FBM/FR/FW/FRW >>> >>> Modem interrupt assignment and sharing: >>> 16: 11633 IO-APIC-fasteoi uhci_hcd:usb5, tifm_7xx1, yenta, >>> i915@pci:0000:00:02.0, HDA Intel >>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>> [ 0.101902] pci 0000:00:1b.0: reg 10 64bit mmio: [0xb0000000-0xb0003fff] >>> [ 0.101966] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>> [ 0.101972] pci 0000:00:1b.0: PME# disabled >>> [ 20.251233] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >>> low) -> IRQ 16 >>> [ 20.251262] HDA Intel 0000:00:1b.0: setting latency timer to 64 >>> [ 20.389567] input: HDA Digital PCBeep as >>> /devices/pci0000:00/0000:00:1b.0/input/input7 >>> [ 393.212102] HDA Intel 0000:00:1b.0: PCI INT A disabled >>> [ 393.228032] PM: suspend of drv:HDA Intel dev:0000:00:1b.0 complete >>> after 223.727 msecs >>> [ 393.272883] HDA Intel 0000:00:1b.0: restoring config space at >>> offset 0x3 (was 0x0, writing 0x8) >>> [ 393.272883] HDA Intel 0000:00:1b.0: restoring config space at >>> offset 0x1 (was 0x100006, writing 0x100002) >>> [ 393.424229] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >>> low) -> IRQ 16 >>> [ 393.424237] HDA Intel 0000:00:1b.0: setting latency timer to 64 >>> >>> The PCI slot 00:1b.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. >>> >>> >>> >>> ===== Advanced Linux Sound Architecture (ALSA) diagnostics ===== >>> The ALSA packages provide audio support and also drivers for some modems. >>> ALSA diagnostics are written during bootup to /proc/asound/ folders. >>> >>> The modem cards detected by "aplay -l" are: >>> tarjeta 0: Intel [HDA Intel], dispositivo 6: Si3054 Modem [Si3054 Modem] >>> >>> The /proc/asound/pcm file reports: >>> ----------------------- >>> 00-00: ALC260 Analog : ALC260 Analog : playback 1 : capture 1 >>> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1 >>> >>> about /proc/asound/cards: >>> ------------------------ >>> 0 [Intel ]: HDA-Intel - HDA Intel >>> HDA Intel at 0xb0000000 irq 16 >>> >>> PCI slot 00:1b.0 has a High Definition Audio Card >>> The drivers are in the kernel modules tree at: >>> /lib/modules/2.6.32-21-generic/kernel/sound/pci/hda/snd-hda-intel.ko >>> The modem codec file for the HDA card is: /proc/asound/card0/codec#1 >>> -------------------------------------------------------- >>> Codec: Motorola Si3054 >>> Address: 1 >>> Function Id: 0x2 >>> Vendor Id: 0x10573055 >>> Subsystem Id: 0x10573055 >>> Revision Id: 0x100700 >>> Modem Function Group: 0x1 >>> >>> The audio card hosts a softmodem chip: 0x10573055 >>> >>> The softmodem chip 0x10573055 is in principle supported by the COMM >>> support of slmodemd >>> and the joint snd-hda-intel audio+modem driver, begun with ALSA >>> version 1.0.13. >>> For HDA cards with ALC883 chips, an upgrade to ALSA verions 1.0.15 way >>> be necessary. >>> Instructions for Upgrading snd-hda-intel and its dependent driver set are at: >>> http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html >>> >>> If not a Conexant modem, the driver snd-hda-intel with its dependent drivers: >>> snd_hda_intel 21877 2 >>> snd_hda_codec 74201 3 >>> snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel >>> snd_pcm 70662 4 >>> snd_hda_codec_si3054,snd_hda_intel,snd_hda_codec,snd_pcm_oss >>> snd 54148 17 >>> snd_hda_codec_si3054,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device >>> snd_page_alloc 7076 2 snd_hda_intel,snd_pcm >>> ---------- >>> provide audio + modem support with the modem chip residing on the subsystem. >>> Any particular card can host any one of several soft modem chips. >>> >>> === Finished firmware and bootup diagnostics, next deducing cogent software. === >>> >>> Predictive diagnostics for card in bus 00:1b.0: >>> Modem chipset detected on >>> NAME="Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW " >>> CLASS=0403 >>> PCIDEV=8086:2668 >>> SUBSYS=152d:0729 >>> IRQ=16 >>> HDA2=00:1b.0 >>> SOFT=8086:2668.HDA >>> HDAchipVendorID=1057 >>> CHIP=0x10573055 >>> IDENT=slmodemd >>> SLMODEMD_DEVICE=hw:0,6 >>> Driver=snd-hda-intel >>> >>> For candidate modem in: 00:1b.0 >>> 0403 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW >>> Primary device ID: 8086:2668 >>> Subsystem PCI_id 152d:0729 >>> Softmodem codec or chipset from diagnostics: 0x10573055 >>> from Archives: >>> The HDA card softmodem chip is 0x10573055 >>> >>> >>> Support type needed or chipset: slmodemd supporting the snd-hda-intel >>> audio+modem driver >>> >>> An ALSA (Advanced Linux Sound Architecture) modem driver: snd-hda-intel >>> 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_gcc4.4_alsa1.0.21.tar.gz having a compiled >>> slmodemd. Unpack under Linux with: >>> $ tar zxf SLMODEMD_gcc4.4_alsa1.0.21.tar.gz >>> and read instructions therein. But briefly, the modem is setup with command: >>> sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,6 >>> 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. >>> >>> >>> 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/.udev >>> >>> Versions adequately match for the compiler installed: 4.4.3 >>> and the compiler used in kernel assembly: 4.4.3 >>> >>> The patch utility is needed for compiling ALSA drivers, and possibly others. >>> >>> >>> Minimal compiling resources appear complete: >>> make utility - /usr/bin/make >>> Compiler version 4.4 >>> linuc_headers base folder /lib/modules/2.6.32-21-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 273312 2010-03-06 19:59 /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 >>> >>> 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: >>> slmodemd created symbolic link /dev/ttySL0: >>> Within /etc/udev/ files: >>> >>> Within /etc/modprobe.conf files: >>> /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/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 >>> Within any ancient /etc/devfs files: >>> >>> Within ancient kernel 2.4.n /etc/module.conf files: >>> >>> --------- end modem support lines -------- >>> >>> >>> >>> >>> >>> On Wed, Mar 21, 2012 at 7:11 PM, <bflores@xxxxxxxxxxxxxx> wrote: >>>> Antonio >>>> >>>> I did: >>>> >>>> $ sudo apt-get sl-modem-src$ sudo apt-get sl-modem-daemon >>>> $ sudo dpkg -i sl*/debthen$ sudo wvdialconf >>>> and I got the following: >>>> >>>> =======================================$ sudo wvdialconf[sudo] password >>>> for alexc: Editing `/etc/wvdial.conf'.Scanning your serial ports for a >>>> modem.Modem Port Scan<*1>: S0 ttyS1<*1>: ATQ0 V1 E1 -- failed with 2400 >>>> baud, next try: 9600 baudttyS1<*1>: ATQ0 V1 E1 -- failed with 9600 baud, >>>> next try: 115200 baudttyS1<*1>: ATQ0 V1 E1 -- and failed too at 115200, >>>> giving up.Modem Port Scan<*1>: S2 S3 Sorry, no modem was detected! Is it >>>> in use by another program?Did you configure it properly with >>>> setserial?Please read the FAQ at http://open.nit.ca/wiki/?WvDialIf you >>>> still have problems, send mail to >>>> <wvdial-list@xxxxxxxxxxxx>.alexc@alexc-laptop:~$ setserialEl programa >>>> «setserial» no está instalado actualmente. Puede instalarlo >>>> escribiendo:sudo apt-get install setserialalexc@alexc-laptop:~$ >>>> ===========================================end of "$ sudo wvdialconf" >>>> >>>> THEN I WENT TO: >>>> http://linmodems.technion.ac.il/packages/smartlink/ >>>> AND DOWNLOADED: >>>> SLMODEMD.2_gcc4.4_alsa1.0.20.tar.gz >>>> AND THEN: >>>> $ tar zxf SLMODEMD.2_gcc4.4_alsa1.0.20.tar.gz$ sudo slmodemd -c b5 >>>> --alsaerror: mixer setup: attach hw:1 error: No such file or >>>> directoryALSA lib confmisc.c:768:(parse_card) cannot find card '1'ALSA >>>> lib conf.c:4154:(_snd_config_evaluate) function snd_func_card_driver >>>> returned error: No such file or directoryALSA lib >>>> confmisc.c:392:(snd_func_concat) error evaluating stringsALSA lib >>>> conf.c:4154:(_snd_config_evaluate) function snd_func_concat returned >>>> error: No such file or directoryALSA lib >>>> confmisc.c:1251:(snd_func_refer) error evaluating nameALSA lib >>>> conf.c:4154:(_snd_config_evaluate) function snd_func_refer returned >>>> error: No such file or directoryALSA lib conf.c:4633:(snd_config_expand) >>>> Evaluate error: No such file or directoryALSA lib >>>> pcm.c:2211:(snd_pcm_open_noupdate) Unknown PCM >>>> cards.pcm.phoneline:CARD=1,DEV=0error: alsa setup: cannot open playback >>>> device 'modem:1': No such file or directoryerror: cannot setup device >>>> `modem:1'alexc@alexc-laptop:~/OmniDataLaptop/SLMODEMD.2_gcc4.4_alsa1.0.20$ >>>> NO CONNECT YET. >>>> >>>> >>>> SincerelyBenito Floresbflores@xxxxxxxxxxxxxx >>>> On 3/11/2012 4:00 PM, Antonio Olivares wrote: >>>> Benito,scanModem reports that you have a supported modem using >>>> SLMODEMD+ALSAdrivers or using deb pacakges sl-modem-src and >>>> sl-modem-daemon:You may >>>> download:http://linmodems.technion.ac.il/packages/smartlink/SLMODEMD_gcc4.4_alsa1.0.21.tar.gzand >>>> follow the instructions above in ModemData.txt or read the onesprovided >>>> in /Modem/DOCs/Smartlink.txtor you may search for deb packages >>>> sl-modem-src and sl-modem-daemon============ instructions for sl-modem >>>> packages ==========Since you are using Ubuntu, it is better to use the >>>> Ubuntu packageproviding slmodemd$ sudo apt-get sl-modem-src$ sudo >>>> apt-get sl-modem-daemonif connection is available, otherwise look for it >>>> in Ubuntu packages. Download the package sl-modem-daemon. Under Ubuntu >>>> it can be installed with:$ sudo dpkg -i sl*/debAfterward the modem >>>> should be dectected by:$ sudo wvdialconfIf successful use$ sudo gedit >>>> /etc/wvdial.confto add a line:Carrier Check = noand edit in your >>>> personal information.Read the DOCs/Smartlink.txt for details.======== >>>> end instructions for sl-modem packages ==========Regards.AntonioOn Sun, >>>> Mar 11, 2012 at 5:25 PM, <bflores@xxxxxxxxxxxxxx> wrote: >>>> >> > >
