Ankur, If you have installed the sl-modem-daemon package, uninstall it because it is useless for the snd-hda-intel case and may interfere. Uninstall with: $ sudo apt-get remove sl-modem-daemon Then run $ find /usr -name slmodemd which will locate the slmodemd . This is usually at /usr/sbin/slmodemd If $ slmodemd --version reports version 2.9.11, all is OK. if not rerun the slmodemd install from the SLMODEMD.gcc4.3.tar.gz Afterwards again check $ slmodemd --version MarvS On Thu, Sep 3, 2009 at 10:31 PM, Ankur Joshi<pharmankur@xxxxxxxxx> wrote: > Thanks for yor replies. > > but when i try your steps following thing occurs:- > > ankur@ankur:~/Desktop$ tar zxf SLMODEMD.gcc4.3.tar.gz > ankur@ankur:~/Desktop$ sudo slmodemd -c INDIA --alsa hw:0,6 > [sudo] password for ankur: > error: alsa setup: cannot open playback device 'hw:0,6': Device or resource > busy > error: cannot setup device `hw:0,6' > ankur@ankur:~/Desktop$ > ankur@ankur:~/Desktop$ > > > Note :- I have tried a no. of times for installing the modem ... is it > because of such attempts create some 'Debris' & give me the error ..? if so > plz tell me how to clear the Debris of my previous failed attempts... > > and oh yes ... thanks again for your help. > > > > Regards, > Ankur Joshi > > > On Fri, Sep 4, 2009 at 12:51 AM, Marvin Stodolsky > <marvin.stodolsky@xxxxxxxxx> wrote: >> >> Pablo, >> >> Try to get the tarball made of the functioning kernel+plus modules, so >> I can package it for others >> >> List, >> Does anyone have a modem success using the snd-hda-intel driver >> under ANY 2.6.28 kernel?? If so, what Distro and kernel? >> >> Ankur, >> >> RE responses. >> Please be carefull to send in plain text or your emails are rejected >> by the List server. >> >> Re modem failures. Use for activation: >> $ sudo slmodemd -c INDIA --alsa hw:0,6 >> and then >> $ sudo wvdial >> should in principle result in a dialout, provided that >> /etc/wvdial.conf has been properly written It should contain an added >> line: >> Carrier Check = no >> >> However all that being well, there is evidence that there is a problem >> with snd-hda-intel modem support under 2.6.28 kernels, seee below, and >> we are trying to figure this situation out. >> >> If failures continue under your 2.6.28 kernel, it might be simplest to >> install a 2.6.27 kernel of the Intepid series. Instructions are in: >> >> http://linmodems.technion.ac.il/bigarch/archive-nineth/msg01316.html >> >> MarvS >> ------------------------ >> from Pablo Marcondes <pablo.mmarcondes@xxxxxxxxx> >> to Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> >> cc David Monniaux <David.Monniaux@xxxxxxx>, >> discuss@xxxxxxxxxxxxx >> date Tue, Aug 18, 2009 at 5:30 PM >> subject Re: problems with HP Pavilion tx1219us (Si3054) >> >> None, I think theres something with the kernel itself. >> >> Ive tested with a self compiled kernel 2.6.28-10-686 and it works, but >> not with 2.6.28-11-generic from jaunty. >> >> And Im in need of this modem working with jaunty too, If I got any >> success I will let you know. >> >> Thanks, >> >> >> >> >> On Thu, Sep 3, 2009 at 8:00 AM, Antonio Olivares<olivares14031@xxxxxxxxx> >> wrote: >> > Ankur, >> > >> > scanModem reports that your modem is supported by >> > SLMODEMD.gcc4.3.tar.gz: >> > >> > For candidate modem in: 00:1b.0 >> > 0403 Audio device: Intel Corporation 82801H >> > Primary device ID: 8086:284b >> > Subsystem PCI_id 17aa:384e >> > 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.3.tar.gz having a compiled slmodemd. Unpack >> > under Linux with: >> > $ tar zxf SLMODEMD.gcc4.3.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. >> > >> > Have you tried the SLMODEMD.gcc4.3.tar.gz and the slmodemd contained >> > in it? If you have, have you addressed the IRQ issue:? >> > >> > For candidate card in slot 00:1b.0, firmware information and bootup >> > diagnostics are: >> > PCI slot PCI ID SubsystemID Name >> > ---------- --------- --------- -------------- >> > 00:1b.0 8086:284b 17aa:384e Audio device: Intel Corporation >> > 82801H >> > >> > Modem interrupt assignment and sharing: >> > 22: 756 750 IO-APIC-fasteoi HDA Intel >> > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> > [ 0.533455] pci 0000:00:1b.0: reg 10 64bit mmio: >> > [0xf8200000-0xf8203fff] >> > [ 0.533503] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> > [ 0.533509] pci 0000:00:1b.0: PME# disabled >> > [ 13.316811] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, >> > low) -> IRQ 22 >> > [ 13.316973] 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. >> > >> > >> > Other than above advice, we need more information in order to try to >> > help you. >> > >> > Regards, >> > >> > Antonio >> > >> > On Thu, Sep 3, 2009 at 2:08 AM, Ankur Joshi<pharmankur@xxxxxxxxx> wrote: >> >> >> >> Hi, >> >> Following is my modemdata.txt file output. Pls help me in insatlling >> >> modem >> >> drivers & setup dialup internet connection. >> >> >> >> NOTE :- this is my 5th mail to you & till date whatever you have >> >> suggested >> >> have never worked. AND more bad is I did not received prompt replies >> >> from u. >> >> PLZ help me this time at least ... >> >> >> >> >> >> >> >> 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.28-15-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.28-15-generic (buildd@palmer) (gcc version 4.3.3 >> >> (Ubuntu >> >> 4.3.3-5ubuntu4) ) #49-Ubuntu SMP Tue Aug 18 18:40:08 UTC 2009 >> >> scanModem update of: 2009_08_15 >> >> The modem symbolic link is /dev/modem -> ttySL0 >> >> The slmodemd set symbolic link is /dev/ttySL0 -> /dev/pts/0 >> >> 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 04f3:0217 Elan Microelectronics Corp. >> >> ID 0bda:0158 Realtek Semiconductor Corp. Mass Stroage Device >> >> ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth >> >> 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 >> >> >> >> For candidate card in slot 00:1b.0, firmware information and bootup >> >> diagnostics are: >> >> PCI slot PCI ID SubsystemID Name >> >> ---------- --------- --------- -------------- >> >> 00:1b.0 8086:284b 17aa:384e Audio device: Intel Corporation >> >> 82801H >> >> >> >> Modem interrupt assignment and sharing: >> >> 22: 756 750 IO-APIC-fasteoi HDA Intel >> >> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >> >> [ 0.533455] pci 0000:00:1b.0: reg 10 64bit mmio: >> >> [0xf8200000-0xf8203fff] >> >> [ 0.533503] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >> >> [ 0.533509] pci 0000:00:1b.0: PME# disabled >> >> [ 13.316811] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, low) >> >> -> >> >> IRQ 22 >> >> [ 13.316973] 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 ALSA verion is 1.0.18 >> >> The modem cards detected by "aplay -l" are: >> >> card 0: Intel [HDA Intel], device 6: Si3054 Modem [Si3054 Modem] >> >> >> >> The /proc/asound/pcm file reports: >> >> ----------------------- >> >> 00-00: ALC861VD Analog : ALC861VD 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 0xf8200000 irq 22 >> >> >> >> PCI slot 00:1b.0 has a High Definition Audio Card >> >> The drivers are in the kernel modules tree at: >> >> /lib/modules/2.6.28-14-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> /lib/modules/2.6.27-7-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> /lib/modules/2.6.28-15-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> /lib/modules/2.6.27-11-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> /lib/modules/2.6.28-13-generic/kernel/sound/pci/hda/snd-hda-intel.ko >> >> /lib/modules/2.6.28-11-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 >> >> 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 434100 6 >> >> snd_pcm 83076 4 snd_hda_intel,snd_pcm_oss >> >> snd 62756 20 >> >> >> >> snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device >> >> snd_page_alloc 16904 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 82801H " >> >> CLASS=0403 >> >> PCIDEV=8086:284b >> >> SUBSYS=17aa:384e >> >> IRQ=22 >> >> HDA=8086:284b >> >> SOFT=8086:284b.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 82801H >> >> Primary device ID: 8086:284b >> >> Subsystem PCI_id 17aa:384e >> >> 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.3.tar.gz having a compiled slmodemd. Unpack >> >> under >> >> Linux with: >> >> $ tar zxf SLMODEMD.gcc4.3.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.3.3 >> >> and the compiler used in kernel assembly: 4.3.3 >> >> >> >> The patch utility is needed and is needed for compiling ALSA drivers, >> >> and >> >> possibly others. >> >> >> >> >> >> Minimal compiling resources appear complete: >> >> make utility - /usr/bin/make >> >> Compiler version 4.3 >> >> linuc_headers base folder /lib/modules/2.6.28-15-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 277352 2009-02-20 22:55 /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 >> >> eth1 >> >> 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 2009-08-31 >> >> 17:27 /dev/modem -> ttySL0 >> >> slmodemd created symbolic link /dev/ttySL0: lrwxrwxrwx 1 root root 10 >> >> 2009-08-31 17:27 /dev/ttySL0 -> /dev/pts/0 >> >> 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 >> >> Within any ancient /etc/devfs files: >> >> >> >> Within ancient kernel 2.4.n /etc/module.conf files: >> >> >> >> --------- end modem support lines -------- >> >> >> >> >> > > >
