Marcello, Additionally your Systems's ALSAversion 1.0.11 snd-hda-intel driver does not have the support codes for the Vendor Id: 0x11c11040 chipset. ALSA code will have to be updated. Since Compiling resources appear complete: make utility - /usr/bin/make Compiler version 4.1 kernel_headers base folder /lib/modules/2.6.17-10-generic/build you should get used to the following procedure. Support for the 0x11c11040 chipset is still being completed, and it may have to be repeated as ALSA code is further updated.
From http://www.alsa-project.org/ download the version 1.0.14rc2 driver
and lib packages. Make a folder, say alsa/. $ mkdir alsa Unpack both packages in the alsa/ folder $ cd alsa $ tar jxf PATH_to/alsa*.tar.bz2 will unpack both. Make a useful definition: $ HEADERS=/lib/modules/2.6.17-10-generic/build Check for validity with: $ ls $HEADERS should show files like: arch include lib scripts block init Makefile security crypto ipc mm sound drivers fs kernel net usr ---------------- This definition does not survive a shutdown and must be redone upon reboot, when a new driver compiling is necessary. To compile the driver set, move into the driver folder: $ cd alsa-driver-1.0.14rc2 Look around: $ ls $ make clean Do the configuration with with the following command on ONE LINE: $ ./configure --with-kernel=$HEADERS --with-build=$HEADERS --with-cards=hda-intel If the configuration is successful, the driver set will be compiled with: $ make Do nothing in the alsa-lib-1.0.14rc2/ folder. But it is used during the compile. The new driver set is displayed by: $ ls modules and installed by $ sudo make install THen reboot to have the new drivers used. Again run ./scanModem there should an device specification N suggested for: $ slmodemd -c BRAZIL --alsa hw:0,N when N will be likely 1 or 6 And the modem should be shown by $ aplay -l Try the command: $ su root # slmodemd -c BRAZIL --alsa hw:0,N Hopefully its will announce port creation Follow through with the guidance in the SLMODEMD-gcc4.tar.gz When you report back, please first $ dmesg > dmesg.txt and attach dmesg.txt to your Report on modem functionality MarvS scanModem maintainer On 2/7/07, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote:
Marcelo, I read in your ModemData.txt: BEGIN QUOTE Download from http://linmodems.technion.ac.il/packages/smartlink/ the package SLMODEMD.gcc4.tar.gz having a compiled slmodemd. Unpack under Linux with: $ tar zxf SLMODEMD.gcc4.tar.gz and read instructions therein. But briefly, the modem is setup with command: sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,? reporting dynamic creation of ports: /dev/ttySL0 --> /dev/pts/N , with N some number Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance. END QUOTE The instructions in there say that you need a modprobe snd-something. In your case: modprobe snd-hda-intl Jacques Marcelo Yuji Nomoto wrote: > Hi, > > would you help me configuring this modem? All I did until now is run > the scanmodem. Here is the resulting ModemData.txt. > > Best regards, > > Marcelo > marcelonomoto@xxxxxxxxx > > Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List > Server. > Do use the following as the email Subject Line: > SomeName, YourCountry Kubuntu 6.10 kernel 2.6.17-10-generic > This will alert cogent experts, and distinguish cases in the Archives. > YourCountry will enable Country Code guidance. > Occassionally responses are blocked by an Internet Provider mail filters. > So in a day, also check the Archived responses at > http://www.linmodems.org . > Local Linux experts can be found through: > http://www.linux.org/groups/index.html > -------------------------- System information ---------------------------- > CPU=i686, Kubuntu 6.10 > Linux version 2.6.17-10-generic (root@terranova) (gcc version 4.1.2 > 20060928 (prerelease) (Kubuntu 4.1.1-13ubuntu5)) #2 SMP Tue Dec 5 > 22:28:26 UTC 2006 (Kubuntu 2.6.17-10.34-generic) > scanModem update of: 2007_Jan_22 > > > USB modem not detected by lsusb > > Modem or host audio card candidates have firmware information: > > PCI slot PCI ID SubsystemID Name > ---------- --------- --------- -------------- > 00:1b.0 8086:27d8 1179:ff01 Audio device: Intel Corporation 82801G > > Modem interrupt assignment and sharing: > 58: 1579 0 IO-APIC-level HDA Intel > > --- Bootup diagnositcs for card in PCI slot 00:1b.0 ---- > [17179590.904000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 > (level, low) -> IRQ 58 > [17179590.904000] PCI: Setting latency timer of device 0000:00:1b.0 to 64 > > === Finished modem firmware and bootup diagnostics section. === > === Next deducing cogent software === > > ALSAversion 1.0.11 > 8086:27d8 is a High Definition Audio card, possibly hosting a soft modem. > > > The VendorID 0x11c11040 softmodem chip is in principle supported by > the snd-hda-intel driver > included within the ALSA audio+modem driver set. However recognition > of 0x11c11040 first begins with ALSA version 1.0.13. There are > instructions for upgrading snd-hda-intel and its > dependent driver set at > http://linmodems.technion.ac.il/archive-fourth/msg05023.html > The ? in the device designation in hw:0,? will be manifest after the > driver update. > Typically ? is in the range of 0-6 . > > > There may be novel modem chipset information within the /proc/asound/ > files. They have been copied and packed into a file: Modem/11c1.tgz > Please send 11c1.tgz to the scanModem maintainer: > Marvin.Stodolsky@xxxxxxxxx > > A candidate driver could not be identified. > For candidate modem in PCI bus: 00:1b.0 > Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > Primary PCI_id 8086:27d8 > Subsystem PCI_id 1179:ff01 > Softmodem codec or Vendor from diagnostics: 11c1, an AgereSystems type. > from Archives: 11c1, an AgereSystems type. > > > Lacking a dsp (digital signal processing) chip, the modem is a software > intensive or "softmodem" type. Its primary controller manages the traffic > with the CPU. But the software needed is specified in the Subsystem. > ----------------------------------------- > 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.gcc4.tar.gz having a compiled slmodemd. Unpack > under Linux with: > $ tar zxf SLMODEMD.gcc4.tar.gz > and read instructions therein. But briefly, the modem is setup with > command: > sudo slmodemd -c YOUR_COUNTRY --alsa hw:0,? > reporting dynamic creation of ports: > /dev/ttySL0 --> /dev/pts/N , with N some number > Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance. > > > The diagnostic outputs for this softmodem section have their raw > information in > folders and text files under /proc/asound/ which you can browse. The > information > is from files: > /proc/asound/pcm > ------------------------------- > 00-00: ALC861 Analog : ALC861 Analog : playback 1 : capture 2 > > /proc/asound/modules > ------------------------------- > 0 snd_hda_intel > /proc/asound/card0/codec#1 > ------------------------------- > Codec: Generic 11c1 ID 1040 > Address: 1 > Vendor Id: 0x11c11040 > Subsystem Id: 0x11790001 > Revision Id: 0x100200 > ------------------------------- > Current support status of HDA cards is: > Vendor IDs Chip maker Support type > ---------- ---------- ------------- > 0x14f12bfa Conexant hsfmodem , not slmodemd compatible > 0x11c13026 AgereSystems snd-hda-intel, slmodemd supported > 0x11c11040 AgereSystems " " , patch needed > 0x11c13055 AgereSystems " " , " > 0x163c3055 Smartlink " " , " > 0x163c3155 " " " , " > 0x10573055 Motorola " " , " > 0x10573155 " " " , "" > as of October 2006. > > and from the command: > aplay -l | grep -i modem > > > ----------------end Softmodem section -------------- > > Writing Intel.txt > Writing 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.1.2 > and the compiler used in kernel assembly: 4.1.2 > > > > Compiling resources appear complete: > make utility - /usr/bin/make > Compiler version 4.1 > kernel_headers base folder /lib/modules/2.6.17-10-generic/build > > > Checking pppd properties: > -rwsr-xr-- 1 root dip 260920 2006-07-10 16:13 /usr/sbin/pppd > > In case of an "error 17" "serial loopback" problem, see: > http://phep2.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 > 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/YourSystem.txt concerning other COMM channels: eth0 > Which can interfere with Browser naviagation. > > Don't worry about the following, it is for the 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: > /etc/udev/rules.d/60-symlinks.rules:# Create /dev/modem symlink > /etc/udev/rules.d/60-symlinks.rules:KERNEL=="ttyLTM[0-9]*", > SYMLINK+="modem" > Within /etc/modprobe.conf files: > /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: > > --------- end modem support lines --------
