2011/1/23 Antonio Olivares <olivares14031@xxxxxxxxx>: > Fibonacci, > > We are closer but not there yet :( > I was hesitant because scanModem reported agrsm-11c11040 too > Predictive diagnostics for card in bus 02:06.4: > Modem chipset detected on > NAME="Communication controller: Texas Instruments PCIxx12 GemCore > based SmartCard controller" > CLASS=0780 > PCIDEV=104c:803d > SUBSYS=103c:30ac > IRQ=11 > HDA2=00:1b.0 > HDAchipVendorID=11c1 > CHIP=0x11c13026 > IDENT=slmodemd > SLMODEMD_DEVICE=hw:0,6 > Driver=snd-hda-intel > package=agrsm-11c11040 > > That is definitely disagreeing. If we can get output of > $ sudo aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem] Subdevices: 1/1 Subdevice #0: subdevice #0 > or run > $ sudo alsa-info.sh ALSA Information Script v 0.4.60 -------------------------------- This script visits the following commands/files to collect diagnostic information about your ALSA installation and sound related hardware. dmesg lspci lsmod aplay amixer alsactl /proc/asound/ /sys/class/sound/ ~/.asoundrc (etc.) See './alsa-info.sh --help' for command line options. Automatically upload ALSA information to www.alsa-project.org? [y/N] : n Your ALSA information is in /tmp/alsa-info.txt.5v0IORcMrv That file is HUGE so I'm not pasting it within this message. It can be accessed on http://pastebin.com/KgcNH79 > and send us output > > http://git.alsa-project.org/?p=alsa-driver.git;a=blob_plain;f=utils/alsa-info.sh > > This way we can try to determine which driver is needed to load > (snd_????-modem) if possible. > > Regards, > > Antonio > > On Sun, Jan 23, 2011 at 12:01 PM, Fibonacci Prower > <fibonacci.prower@xxxxxxxxx> wrote: >> 2011/1/23 Antonio Olivares <olivares14031@xxxxxxxxx>: >>> Fibonacci, >>> >>> There are two conflicting drivers here: >>> >>> Potentially useful modem drivers now loaded are: >>> snd_hda_intel slamr >>> >>> Try to do the following: >>> >>> $ sudo modprobe -r slamr >> No problem here: >>> $ sudo modprobe -r snd_hda_intel >> FATAL: Module snd_hda_intel is in use. >>> then reload the latter one >>> $ sudo modprobe snd_hda_intel >>> $ sudo slmodemd -c USA --alsa hw:0,6 >> SmartLink Soft Modem: version 2.9.11 Sep 6 2010 12:33:03 >> 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' >> >> So I'm back to starting a root shell and then running this: >> # ulimit -l 8192 && slmodemd -c USA --alsa hw:0,6 >>> >>> Leave this running in the background, fire up another terminal shell/tab and run >>> $ sudo wvdialconf /etc/wvdial.conf >> >> Editing `/etc/wvdial.conf'. >> >> Scanning your serial ports for a modem. >> >> Modem Port Scan<*1>: S0 S1 >> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >> Modem Port Scan<*1>: S3 >> WvModem<*1>: Cannot get information for serial port. >> ttySL0<*1>: ATQ0 V1 E1 -- OK >> ttySL0<*1>: ATQ0 V1 E1 Z -- OK >> ttySL0<*1>: ATQ0 V1 E1 S0=0 -- OK >> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 -- OK >> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 -- OK >> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK >> ttySL0<*1>: Modem Identifier: ATI -- SmartLink Soft Modem >> ttySL0<*1>: Speed 4800: AT -- OK >> ttySL0<*1>: Speed 9600: AT -- OK >> ttySL0<*1>: Speed 19200: AT -- OK >> ttySL0<*1>: Speed 38400: AT -- OK >> ttySL0<*1>: Speed 57600: AT -- OK >> ttySL0<*1>: Speed 115200: AT -- OK >> ttySL0<*1>: Speed 230400: AT -- OK >> ttySL0<*1>: Speed 460800: AT -- OK >> ttySL0<*1>: Max speed is 460800; that should be safe. >> ttySL0<*1>: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 -- OK >> >> Found a modem on /dev/ttySL0. >> Modem configuration written to /etc/wvdial.conf. >> ttySL0<Info>: Speed 460800; init "ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0" >> >>> >>> to be safe you may run >>> $ dmesg | grep 'sl*' and output of >> Shouldn't it be 'sl' instead of 'sl*'? Anyway this is the output of the former: >> [ 0.000000] SLUB: Genslabs=13, HWalign=64, Order=0-3, MinObjects=0, >> CPUs=2, Nodes=1 >> [ 0.172235] bio: create slab <bio-0> at 0 >> [ 0.560686] Cannot allocate resource for EISA slot 1 >> [ 0.560688] Cannot allocate resource for EISA slot 2 >> [ 0.560691] Cannot allocate resource for EISA slot 3 >> [ 0.560693] Cannot allocate resource for EISA slot 4 >> [ 0.560695] Cannot allocate resource for EISA slot 5 >> [ 0.560697] Cannot allocate resource for EISA slot 6 >> [ 0.560699] Cannot allocate resource for EISA slot 7 >> [ 0.560701] Cannot allocate resource for EISA slot 8 >> [ 0.581865] input: AT Translated Set 2 keyboard as >> /devices/platform/i8042/serio0/input/input3 >> [ 1.135273] ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 >> Gbps 0x1 impl SATA mode >> [ 1.135278] ahci 0000:00:1f.2: flags: 64bit ncq ilck stag pm led >> clo pmp pio slum part >> [ 28.012927] slamr: SmartLink AMRMO modem. >>> $ sudo tail -f /var/log/messages >> Jan 23 12:48:23 prower-laptop kernel: [ 29.696342] Bluetooth: BNEP >> filters: protocol multicast >> Jan 23 12:48:23 prower-laptop kernel: [ 29.700521] Bluetooth: SCO >> (Voice Link) ver 0.6 >> Jan 23 12:48:23 prower-laptop kernel: [ 29.700524] Bluetooth: SCO >> socket layer initialized >> Jan 23 12:48:23 prower-laptop kernel: [ 29.815105] Bluetooth: RFCOMM >> TTY layer initialized >> Jan 23 12:48:23 prower-laptop kernel: [ 29.815112] Bluetooth: RFCOMM >> socket layer initialized >> Jan 23 12:48:23 prower-laptop kernel: [ 29.815115] Bluetooth: RFCOMM ver 1.11 >> Jan 23 12:48:25 prower-laptop kernel: [ 31.407768] EXT4-fs (sda5): >> re-mounted. Opts: errors=remount-ro,commit=0 >> Jan 23 12:48:25 prower-laptop pulseaudio[1626]: lock-autospawn.c: >> Cannot access autospawn lock. >> Jan 23 12:48:26 prower-laptop kernel: [ 32.660192] input: PS/2 >> Generic Mouse as /devices/platform/i8042/serio4/serio5/input/input8 >> Jan 23 12:48:26 prower-laptop kernel: [ 32.888990] EXT4-fs (sda5): >> re-mounted. Opts: errors=remount-ro,commit=0 >>> last few lines when running the above commands. Report back presently. >>> >>> Regards, >>> >>> Antonio >>> >>> On Sun, Jan 23, 2011 at 2:43 AM, Fibonacci Prower >>> <fibonacci.prower@xxxxxxxxx> wrote: >>>> 2011/1/23 Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx>: >>>>> Fibonacci >>>>> >>>>> Please disconnect the USB devices as much as possible, and take out >>>>> any PCMCIA cards >>>>> Your System seems low on RAM. Again run scanModem >>>>> On your first round the important ALSA diagnostics did not get written >>>>> to ModemData.txt >>>>> even the directions to use slmodemd seem correct. >>>>> >>>> >>>> No user-removable USB devices or PCMCIA cards were connnected at the >>>> time I ran scanModem. >>>> The new ModemData.txt is on the bottom. >>>> >>>>> The logic in my scanModem script is not sophisticated enought to >>>>> always succeed when there on two candidate COMM cards. >>>>> >>>>> But as I read it, there is an Agere chip >>>>> CHIP=0x11c13026, hosted on the Subsystem of the High Defintion Audio card >>>>> with the real smarts in the slmodemd helper using the dynamically created >>>>> SLMODEMD_DEVICE=hw:0,6 >>>>> corresponding to /dev/ttySL0 -> /dev/pts/2 (the real port) >>>>> >>>>> You can first try: >>>>> $ lsmod >>>>> to display drivers, then starting from the top of list, try removing >>>>> non-essential drivers with >>>>> $ sudo modprobe -r DriverNames >>>>> >>>> >>>> How do I know which driver does what? >>>> >>>>> A first functionality test is detecting the modem with: >>>>> $ sudo wvdialconf >>>>> >>>> >>>> This is what I get: >>>> >>>> Editing `/etc/wvdial.conf'. >>>> >>>> Scanning your serial ports for a modem. >>>> >>>> Modem Port Scan<*1>: S0 S1 >>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud >>>> ttyS2<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud >>>> ttyS2<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up. >>>> Modem Port Scan<*1>: 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/?WvDial >>>> >>>> If you still have problems, send mail to <wvdial-list@xxxxxxxxxxxx>. >>>> >>>>> Try these and report back >>>>> >>>>> MarvS >>>>> scanModem maintainer >>>>> On Sun, Jan 23, 2011 at 2:15 AM, Fibonacci Prower >>>>> <fibonacci.prower@xxxxxxxxx> wrote: >>>>>> Hello. >>>>>> >>>>>> I'm trying to use the modem which came with my laptop to connect to >>>>>> the internet. Unfortunately it's a winmodem, like most. >>>>>> The output of scanModem (attached) is not clear enough as to which >>>>>> driver should be used on this modem. I finally installed and >>>>>> configured sl-modem-daemon - but I still don't know which country >>>>>> should I specify, since Colombia (where I currently live) is not one >>>>>> of the available options. >>>>>> It appears, nevertheless, that my system is talking to the modem. I >>>>>> can't connect to the internet, though, since I always get this message >>>>>> with either Gnome-PPP or WvDial: >>>>>> >>>>>> --> WvDial: Internet dialer version 1.60 >>>>>> --> Cannot get information for serial port. >>>>>> --> Initializing modem. >>>>>> --> Sending: ATZ >>>>>> ATZ >>>>>> OK >>>>>> --> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>> ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 >>>>>> OK >>>>>> --> Modem initialized. >>>>>> --> Sending: ATM1L3DT019479472323 >>>>>> --> Waiting for carrier. >>>>>> ATM1L3DT019479472323 >>>>>> NO CARRIER >>>>>> --> No Carrier! Trying again. >>>>>> >>>>>> That happens even after I've set Carrier Check = no on wvdial.conf, so >>>>>> I'm stuck here. >>>>>> >>>>>> After rebooting, I get the following error message from both Gnome-PPP >>>>>> and WvDial: >>>>>> >>>>>> --> Cannot open /dev/ttySL0: No such file or directory >>>>>> --> Cannot open /dev/ttySL0: No such file or directory >>>>>> --> Cannot open /dev/ttySL0: No such file or directory >>>>>> >>>>>> Problem is, /dev/ttySL0 is there and world-writable. OK, then, I'll >>>>>> try restarting slmodemd: >>>>>> >>>>>> $ sudo slmodemd -c USA --alsa hw:0,6 >>>>>> error: locked memory limit too low: >>>>>> error: need 8388608 bytes, have 65536 bytes >>>>>> error: try 'ulimit -l 8192' >>>>>> >>>>>> Oh well. Since sudo ulimit doesn't work, I need to start a root shell, >>>>>> THEN run the ulimit code suggested, THEN slmodemd -c USA --alsa >>>>>> hw:0,6, and THEN... nothing. I'm right back at square one - no >>>>>> carrier. >>>>>> >>>>>> Also: the exact same setup works under Windows XP, so I know there's >>>>>> nothing wrong with my hardware. >>>>>> >>>>>> The full content of ModemData.txt follows: >>>>>> >>>>>> 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.35-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, Ubuntu , ALSA_version=1.0.23 >>>>>> Linux version 2.6.35-24-generic (buildd@vernadsky) (gcc version 4.4.5 >>>>>> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #42-Ubuntu SMP Thu Dec 2 01:41:57 >>>>>> UTC 2010 >>>>>> scanModem update of: 2010_12_12 >>>>>> The modem symbolic link is /dev/modem -> ttySL0 >>>>>> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/2 >>>>>> Distrib_ID=Ubuntu >>>>>> DistribCodeName=maverick >>>>>> AptRepositoryStem=http://ubuntu.wikimedia.org/ubuntu/ >>>>>> >>>>>> >>>>>> The dkms driver upgrade utilities are installed, >>>>>> >>>>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>>>> >>>>>> Potentially useful modem drivers now loaded are: >>>>>> snd_hda_intel >>>>>> >>>>>> Attached USB devices are: >>>>>> ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor >>>>>> ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface >>>>>> [Integrated Module] >>>>>> ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 >>>>>> HSDPA/HSUPA Modem >>>>>> ID 0781:5406 SanDisk Corp. Cruzer Micro U3 >>>>>> 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: >>>>>> 02:06.4 Communication controller: Texas Instruments PCIxx12 GemCore >>>>>> based SmartCard controller >>>>>> 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High >>>>>> Definition Audio Controller (rev 01) >>>>>> High Definition Audio cards can host modem chips. >>>>>> >>>>>> For candidate card in slot 02:06.4, firmware information and bootup >>>>>> diagnostics are: >>>>>> PCI slot PCI ID SubsystemID Name >>>>>> ---------- --------- --------- -------------- >>>>>> 02:06.4 104c:803d 103c:30ac Communication controller: Texas >>>>>> Instruments PCIxx12 GemCore based SmartCard controller >>>>>> >>>>>> Modem interrupt assignment and sharing: >>>>>> --- Bootup diagnostics for card in PCI slot 02:06.4 ---- >>>>>> [ 0.293990] pci 0000:02:06.4: reg 10: [mem 0xe420a000-0xe420afff] >>>>>> [ 0.294000] pci 0000:02:06.4: reg 14: [mem 0xe420b000-0xe420bfff] >>>>>> [ 0.294070] pci 0000:02:06.4: supports D1 D2 >>>>>> [ 0.294072] pci 0000:02:06.4: PME# supported from D0 D1 D2 D3hot >>>>>> [ 0.294078] pci 0000:02:06.4: PME# disabled >>>>>> >>>>>> The PCI slot 02:06.4 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:1b.0, firmware information and bootup >>>>>> diagnostics are: >>>>>> PCI slot PCI ID SubsystemID Name >>>>>> ---------- --------- --------- -------------- >>>>>> 00:1b.0 8086:27d8 103c:30ac Audio device: Intel Corporation >>>>>> N10/ICH 7 Family High Definition Audio Controller >>>>>> >>>>>> Modem interrupt assignment and sharing: >>>>>> 45: 16836 0 PCI-MSI-edge hda_intel >>>>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>>>>> [ 0.290686] pci 0000:00:1b.0: reg 10: [mem 0xe4700000-0xe4703fff 64bit] >>>>>> [ 0.290750] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>>>>> [ 0.290755] pci 0000:00:1b.0: PME# disabled >>>>>> [ 28.827744] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >>>>>> [ 28.827779] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >>>>>> [ 28.827788] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >>>>>> low) -> IRQ 16 >>>>>> [ 28.827858] HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X >>>>>> [ 28.827891] 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. >>>>>> >>>>>> >>>>>> === Finished firmware and bootup diagnostics, next deducing cogent software. === >>>>>> >>>>>> Predictive diagnostics for card in bus 02:06.4: >>>>>> Modem chipset detected on >>>>>> NAME="Communication controller: Texas Instruments PCIxx12 GemCore >>>>>> based SmartCard controller" >>>>>> CLASS=0780 >>>>>> PCIDEV=104c:803d >>>>>> SUBSYS=103c:30ac >>>>>> IRQ=11 >>>>>> HDA2=00:1b.0 >>>>>> HDAchipVendorID=11c1 >>>>>> CHIP=0x11c13026 >>>>>> IDENT=slmodemd >>>>>> SLMODEMD_DEVICE=hw:0,6 >>>>>> Driver=snd-hda-intel >>>>>> package=agrsm-11c11040 >>>>>> >>>>>> For candidate modem in: 02:06.4 >>>>>> 0780 Communication controller: Texas Instruments PCIxx12 GemCore >>>>>> based SmartCard controller >>>>>> Primary device ID: 104c:803d >>>>>> Support type needed or chipset: slmodemd >>>>>> >>>>>> >>>>>> 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.23.tar.gz having a compiled >>>>>> slmodemd. Unpack under Linux with: >>>>>> $ tar zxf SLMODEMD_gcc4.4_alsa1.0.23.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 ===================== >>>>>> >>>>>> The AgereSystems/LSI agrsm code supports compiling of a agrmodem + >>>>>> agrserial driver pair. >>>>>> There are a few different chipsets which use this driver pair, but >>>>>> they use different code resources: >>>>>> Chipsets KV* PackageNames (most current as of November 2009) >>>>>> ---------------------------------------------------------------------------------------------- >>>>>> 11c1:048c and 11c1:048f 2.6.29 >>>>>> agrsm048pci-2.1.60_20100108_i386.deb or >>>>>> agrsm048pci-2.1.60_20100108.tar.gz >>>>>> 11c1:0620 2.6.31 >>>>>> agrsm06pci-2.1.80_20100106_i386.deb or >>>>>> agrsm06pci-2.1.80~20100106.tar.gz !! >>>>>> 11c11040 (on HDA audio cards) 2.6.31 >>>>>> agrsm-11c11040_20091225_i386.deb or >>>>>> agrsm-11c11040-2.1.80~20091225.tar.bz2 !! >>>>>> All available at: >>>>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ >>>>>> Additionally there are; >>>>>> automation & testing agrsm-tools_0.0.1_all.deb or >>>>>> agrsm-tools-0.0.1-2.noarch.rpm >>>>>> General background agrsm_howto.txt >>>>>> ------------------------------------------------------------------------------------------------ >>>>>> * KV == latest kernel release with a reported success >>>>>> !! Latest update with major credit to Nikolay Zhuravlev >>>>>> But see conflict issue: >>>>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html >>>>>> For the 11c11040 chip with kernels 2.6.31 and later a change in a >>>>>> modules loading settingmay be necessary. >>>>>> Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for >>>>>> your Distro), change the phrase: >>>>>> options snd-hda-intel power_save=10 >>>>>> to: >>>>>> options snd-hda-intel power_save=0 >>>>>> or the agrsm drivers will not function. For Ubuntu related systems >>>>>> this can be done with: >>>>>> $ sudo gedit /etc/modprobe.d/alsa-base.conf >>>>>> >>>>>> Report from Bjorn Wielens: >>>>>> Please note- trying to load the modules on a OpenSuSE 11.2 system gives >>>>>> an error about the module_version symbol. Using: >>>>>> # modprobe --force agrmodem >>>>>> # modprobe --force agrserial >>>>>> is necessary to load the drivers, and does not appear to cause ill effects. >>>>>> >>>>>> >>>>>> All of the above packages are dkms competent. This means that if your >>>>>> Linux distros dkms package >>>>>> is previously installed, if provides for future updates matching >>>>>> forthcoming kernels. >>>>>> >>>>>> -------------- end Agere Systems section ------------------- >>>>>> >>>>>> >>>>>> Predictive diagnostics for card in bus 00:1b.0: >>>>>> Modem chipset not detected on >>>>>> NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition >>>>>> Audio Controller " >>>>>> CLASS=0403 >>>>>> PCIDEV=8086:27d8 >>>>>> SUBSYS=103c:30ac >>>>>> IRQ=45 >>>>>> >>>>>> For candidate modem in: 00:1b.0 >>>>>> 0403 Audio device: Intel Corporation N10/ICH 7 Family High >>>>>> Definition Audio Controller >>>>>> Primary device ID: 8086:27d8 >>>>>> 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-24-generic resources needed for compiling are >>>>>> not manifestly ready! >>>>>> >>>>>> If compiling is necessary packages must be installed, providing: >>>>>> linux-headers-2.6.35-24-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 eth2 ppp0 >>>>>> 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 >>>>>> 2010-12-21 22:43 /dev/modem -> ttySL0 >>>>>> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 >>>>>> 2010-12-21 22:43 /dev/ttySL0 -> /dev/pts/2 >>>>>> 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/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) >>>>>> /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 -------- >>>>>> >>>>>> >>>>>> -- >>>>>> $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m", >>>>>> chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',( >>>>>> $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39" >>>>>> ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz >>>>>> >>>>> >>>> >>>> This is 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.35-25-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.23 >>>> Linux version 2.6.35-25-generic (buildd@roseapple) (gcc version 4.4.5 >>>> (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #43-Ubuntu SMP Thu Jan 6 22:25:16 >>>> UTC 2011 >>>> scanModem update of: 2010_12_12 >>>> The modem symbolic link is /dev/modem -> ttySL0 >>>> Distrib_ID=Ubuntu >>>> DistribCodeName=maverick >>>> AptRepositoryStem=http://ubuntu.wikimedia.org/ubuntu/ >>>> >>>> >>>> The dkms driver upgrade utilities are installed, >>>> >>>> There are no blacklisted modem drivers in /etc/modprobe* files >>>> >>>> Potentially useful modem drivers now loaded are: >>>> snd_hda_intel slamr >>>> >>>> Attached USB devices are: >>>> ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor >>>> ID 03f0:171d Hewlett-Packard Wireless (Bluetooth + WLAN) Interface >>>> [Integrated Module] >>>> 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: >>>> 02:06.4 Communication controller: Texas Instruments PCIxx12 GemCore >>>> based SmartCard controller >>>> 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High >>>> Definition Audio Controller (rev 01) >>>> High Definition Audio cards can host modem chips. >>>> >>>> For candidate card in slot 02:06.4, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 02:06.4 104c:803d 103c:30ac Communication controller: Texas >>>> Instruments PCIxx12 GemCore based SmartCard controller >>>> >>>> Modem interrupt assignment and sharing: >>>> --- Bootup diagnostics for card in PCI slot 02:06.4 ---- >>>> [ 0.287491] pci 0000:02:06.4: reg 10: [mem 0xe420a000-0xe420afff] >>>> [ 0.287502] pci 0000:02:06.4: reg 14: [mem 0xe420b000-0xe420bfff] >>>> [ 0.287572] pci 0000:02:06.4: supports D1 D2 >>>> [ 0.287574] pci 0000:02:06.4: PME# supported from D0 D1 D2 D3hot >>>> [ 0.287580] pci 0000:02:06.4: PME# disabled >>>> >>>> The PCI slot 02:06.4 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:1b.0, firmware information and bootup >>>> diagnostics are: >>>> PCI slot PCI ID SubsystemID Name >>>> ---------- --------- --------- -------------- >>>> 00:1b.0 8086:27d8 103c:30ac Audio device: Intel Corporation N10/ICH 7 >>>> Family High Definition Audio Controller >>>> >>>> Modem interrupt assignment and sharing: >>>> 45: 1004 0 PCI-MSI-edge hda_intel >>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>>> [ 0.284217] pci 0000:00:1b.0: reg 10: [mem 0xe4700000-0xe4703fff 64bit] >>>> [ 0.284281] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>>> [ 0.284286] pci 0000:00:1b.0: PME# disabled >>>> [ 18.824476] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >>>> [ 18.824512] HDA Intel 0000:00:1b.0: power state changed by ACPI to D0 >>>> [ 18.824522] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, >>>> low) -> IRQ 16 >>>> [ 18.824602] HDA Intel 0000:00:1b.0: irq 45 for MSI/MSI-X >>>> [ 18.824636] 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. >>>> >>>> >>>> === Finished firmware and bootup diagnostics, next deducing cogent software. === >>>> >>>> Predictive diagnostics for card in bus 02:06.4: >>>> Modem chipset detected on >>>> NAME="Communication controller: Texas Instruments PCIxx12 GemCore >>>> based SmartCard controller" >>>> CLASS=0780 >>>> PCIDEV=104c:803d >>>> SUBSYS=103c:30ac >>>> IRQ=11 >>>> HDA2=00:1b.0 >>>> HDAchipVendorID=11c1 >>>> CHIP=0x11c13026 >>>> IDENT=slmodemd >>>> SLMODEMD_DEVICE=hw:0,6 >>>> Driver=snd-hda-intel >>>> package=agrsm-11c11040 >>>> >>>> For candidate modem in: 02:06.4 >>>> 0780 Communication controller: Texas Instruments PCIxx12 GemCore >>>> based SmartCard controller >>>> Primary device ID: 104c:803d >>>> Support type needed or chipset: slmodemd >>>> >>>> >>>> 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.23.tar.gz having a compiled >>>> slmodemd. Unpack under Linux with: >>>> $ tar zxf SLMODEMD_gcc4.4_alsa1.0.23.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 ===================== >>>> >>>> The AgereSystems/LSI agrsm code supports compiling of a agrmodem + >>>> agrserial driver pair. >>>> There are a few different chipsets which use this driver pair, but >>>> they use different code resources: >>>> Chipsets KV* PackageNames (most current as of November 2009) >>>> ---------------------------------------------------------------------------------------------- >>>> 11c1:048c and 11c1:048f >>>> 2.6.29 agrsm048pci-2.1.60_20100108_i386.deb or >>>> agrsm048pci-2.1.60_20100108.tar.gz >>>> 11c1:0620 2.6.31 >>>> agrsm06pci-2.1.80_20100106_i386.deb or >>>> agrsm06pci-2.1.80~20100106.tar.gz !! >>>> 11c11040 (on HDA audio cards) 2.6.31 >>>> agrsm-11c11040_20091225_i386.deb or >>>> agrsm-11c11040-2.1.80~20091225.tar.bz2 !! >>>> All available at: >>>> http://linmodems.technion.ac.il/packages/ltmodem/11c11040/ >>>> Additionally there are; >>>> automation & testing agrsm-tools_0.0.1_all.deb or >>>> agrsm-tools-0.0.1-2.noarch.rpm >>>> General background agrsm_howto.txt >>>> ------------------------------------------------------------------------------------------------ >>>> * KV == latest kernel release with a reported success >>>> !! Latest update with major credit to Nikolay Zhuravlev >>>> But see conflict issue: >>>> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg02753.html >>>> For the 11c11040 chip with kernels 2.6.31 and later a change in a >>>> modules loading settingmay be necessary. >>>> Within the file /etc/modprobe.d/alsa-base.conf (or equivalent for >>>> your Distro), change the phrase: >>>> options snd-hda-intel power_save=10 >>>> to: >>>> options snd-hda-intel power_save=0 >>>> or the agrsm drivers will not function. For Ubuntu related systems >>>> this can be done with: >>>> $ sudo gedit /etc/modprobe.d/alsa-base.conf >>>> >>>> Report from Bjorn Wielens: >>>> Please note- trying to load the modules on a OpenSuSE 11.2 system gives >>>> an error about the module_version symbol. Using: >>>> # modprobe --force agrmodem >>>> # modprobe --force agrserial >>>> is necessary to load the drivers, and does not appear to cause ill effects. >>>> >>>> >>>> All of the above packages are dkms competent. This means that if your >>>> Linux distros dkms package >>>> is previously installed, if provides for future updates matching >>>> forthcoming kernels. >>>> >>>> -------------- end Agere Systems section ------------------- >>>> >>>> >>>> Predictive diagnostics for card in bus 00:1b.0: >>>> Modem chipset not detected on >>>> NAME="Audio device: Intel Corporation N10/ICH 7 Family High Definition >>>> Audio Controller " >>>> CLASS=0403 >>>> PCIDEV=8086:27d8 >>>> SUBSYS=103c:30ac >>>> IRQ=45 >>>> >>>> For candidate modem in: 00:1b.0 >>>> 0403 Audio device: Intel Corporation N10/ICH 7 Family High >>>> Definition Audio Controller >>>> Primary device ID: 8086:27d8 >>>> 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 pppd properties: >>>> -rwsr-xr-- 1 root dip 273248 2010-07-09 11:41 /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 eth2 >>>> 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-01-23 02:10 /dev/modem -> ttySL0 >>>> 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/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) >>>> /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 -------- >>>> >>>> >>>> -- >>>> $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m", >>>> chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',( >>>> $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39" >>>> ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz >>>> >>> >> >> >> >> -- >> $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m", >> chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',( >> $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39" >> ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz >> > -- $0='!/msfQ0yjoV!fe!sfldbi!psup!pmpT'x19xor print+map{("\e[7m \e[0m", chr ord(chop$0)-1)[$_].("\n")[++$i%72]}split//,unpack'B*',pack'H*',( $P='F'x18)."8186078739E1F0F0E19FCF333319CCE6667383CF0733099E67E7F39" ."FCF3333218067E7F39FCF3333319E6666739F860787399E70F0E1$P"#Perl rulz
