Doug, There is another "gotcha" that I might have forgotten to point out :( The alsa driver needs to be patched: http://www.linuxant.com/alsa-driver/ http://www.linuxant.com/alsa-driver/archive/alsa-driver-linuxant-1.0.20.3/alsa-driver-linuxant-1.0.20.3-1.noarch.rpm.zip There is one alsa driver for an earlier Fedora kernel: http://www.linuxant.com/alsa-driver/archive/alsa-driver-linuxant-1.0.20.3/alsa-driver-linuxant-1.0.20.3_k2.6.30.9_96.fc11-1fdr.x86_64.rpm.zip I hope that the above RPM (http://www.linuxant.com/alsa-driver/archive/alsa-driver-linuxant-1.0.20.3/alsa-driver-linuxant-1.0.20.3-1.noarch.rpm.zip) works for you since there are too many kernels and versions that there might not be support for that one yet. I was not sure that it needed to be patched, but I hoped that everything would have gotten take care of. I hope that installing the alsa rpm fixes the situation. Let us know how it goes. Marv, Jonathan Is there dkms support for linuxant drivers(hsf and/or hcf) modems. This way across releases the drivers are automagically generated? Regards, Antonio On 12/19/09, Doug Hutcheson <doug.hutcheson@xxxxxxxxxxx> wrote: > Antonio, > Thanks for getting back so quickly. > > I downloaded and installed as you instructed, but there seems to be an > issue with HDA support not being built in the kernel. > ============================================================ > No pre-built modules for: Fedora-11 linux-2.6.30.9-102.fc11.x86_64 > x86_64-SMP > > Trying to automatically build the driver modules... > (this requires a C compiler and proper kernel sources to be installed) > > Building modules for kernel 2.6.30.9-102.fc11.x86_64, using source > directory > /lib/modules/2.6.30.9-102.fc11.x86_64/build. Please wait... > done. > > Warning: no device detected by hsf driver - HDA modems may require > reboot > > Note: HDA support not compiled in the driver > > Note: kernel module snd-via82xx-modem overridden by hsfmc97via > Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis > Note: kernel module snd-atiixp-modem overridden by hsfmc97ati > ============================================================ > > Running hsfconfig results in similar messages: > ============================================================ > Conexant HSF softmodem driver, version 7.80.02.05x86_64full > > If you need license keys, assistance or more information, please go to: > http://www.linuxant.com/ > > When reporting a problem for the first time, please send > us the file generated by "hsfconfig --dumpdiag". > > Warning: existing driver modules found under: > /lib/modules/2.6.30.9-102.fc11.x86_64/ > Would you like to keep using them? [no] yes > > Warning: no device detected by hsf driver - HDA modems may require > reboot > > Note: HDA support not compiled in the driver > > Note: kernel module snd-via82xx-modem overridden by hsfmc97via > Note: kernel module snd-intel8x0m overridden by hsfmc97ich hsfmc97sis > Note: kernel module snd-atiixp-modem overridden by hsfmc97ati > ============================================================ > > Where do I go from here? Do I have to rebuild the kernel on my machine? > Will I have to do so each time it is updated? > > Kind regards, Doug > > On Sat, 2009-12-19 at 11:29 -0600, Antonio Olivares wrote: >> Doug, >> >> scanModem recommends hsfmodem drivers: >> >> 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:20ac >> IRQ=17 >> HDA=8086:284b >> SOFT=8086:284b.HDA >> ArchivedChip=0x14f12bfa >> CodecClass=14f1 >> IDENT=hsfmodem >> Driver=hsfmodem-drivers >> >> For candidate modem in: 00:1b.0 >> 0403 Audio device: Intel Corporation 82801H >> Primary device ID: 8086:284b >> Subsystem PCI_id 17aa:20ac >> Softmodem codec or chipset from diagnostics: >> from Archives: 0x14f12bfa >> >> >> >> Support type needed or chipset: hsfmodem >> >> >> Writing DOCs/Intel.txt >> >> For owners of a Dell PCs with Conexant HSF modems, a driver source >> package with full speed enabled is available, but requires driver >> compiling. Read >> DOCs/Conexant.txt >> >> Start at http://www.linuxant.com/drivers/hsf/full for >> eventually download of a hsfmodem-7.68.00.12full_k.???.zip package >> with ??? the package type (deb, rpm, tar etc) >> These packages have compiled drivers but will also compile a driver, >> if there is a mismatch between the resident kernel and provided driver. >> The generic hsfmodem-7.68.00.12full.tar.gz package only provides >> compiling support >> >> You will visit/have visited the following page: >> >> http://www.linuxant.com/drivers/hsf/downloads-license.php >> >> click on I agree then go to >> >> http://www.linuxant.com/drivers/hsf/full/downloads.php >> >> Then go to Fedora 11: >> >> http://www.linuxant.com/drivers/hsf/full/downloads-fc11-x86.php >> >> But your CPU is x86_64 so those drivers don't work :( >> >> So your other choice is to get : >> >> http://www.linuxant.com/drivers/hsf/full/archive/hsfmodem-7.80.02.05x86_64full/hsfmodem-7.80.02.05x86_64full-1.x86_64.rpm.zip >> >> unzip it and take it from there. >> >> METHOD A: BINARY RPM PACKAGE (*.{arch}.rpm) >> If you have obtained the driver package in RPM format: >> 1. install the rpm with "rpm -i hsfmodem-{version}.{arch}.rpm" >> 2. if necessary, run "hsfconfig" to complete the installation, enter >> license information, or to change your modem's configuration. >> If you need to rebuild the generic RPM from source, you can get the >> TAR package and run: "rpmbuild -tb hsfmodem-{version}.tar.gz" (if >> rpmbuild is not found, you might have to install the rpm-build package >> or if you have an older RPM version, try "rpm --rebuild ..."). If you >> want a pre-compiled package for the currently running kernel, you can >> try "make rpmprecomp" in the top directory. >> >> If you encounter difficulties use this page as a reference: >> >> http://www.linuxant.com/drivers/hsf/install.php >> >> Regards, >> >> Antonio >> >> On 12/18/09, Doug Hutcheson <doug.hutcheson@xxxxxxxxxxx> wrote: >> > Folks, looking to get the modem working on my Lenovo T61 laptop. I have >> > tried to figure it out for myself, but nothing I have done has worked. >> > I want to get it working as I anticipate an extended hospital stay in >> > the next few months where I will be behind a plain old telephone line. >> > >> > Kind regards, Doug >> > >> > Scanmodem output is: >> > -------------------------- System information >> > ---------------------------- >> > >> > CPU=x86_64, >> > >> > Linux version 2.6.30.9-102.fc11.x86_64 >> > (mockbuild@xxxxxxxxxxxxxxxxxxxxxxxxxxx) (gcc version 4.4.1 20090725 (Red >> > Hat 4.4.1-2) (GCC) ) #1 SMP Fri Dec 4 00:18:53 EST >> > 2009 >> > >> > scanModem update of: >> > 2009_12_10 >> > >> > >> > >> > 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 >> > >> > >> > Some modem drivers can only be used in 32 bit modem on x86_64 systems, >> > while some others are competent on x86_64 Systems. Cases are: >> > 1) >> > http://linmodems.technion.ac.il/bigarch/archive-seventh/msg03119.html >> > for the snd-hda-intel audio+modem driver. Also applicable to AC97 modem >> > controllers. >> > In both cases, 32 bit libraries must be installed to support the >> > slmodemd helper having a precompiled 32 bit component. >> > 2) For USB modems using the slusb.ko driver. 32 bit libraries must be >> > installed to support the slmodemd helper having a precompiled 32 bit >> > component >> > >> > 3) The hsfmodem and hcfpcimodem drivers for Conexant chipsest modes are >> > x86_64 competent. >> > 4) agrsm packages for LSI/AgereSystems softmodems are not competent on >> > x86_64 systems. >> > >> > 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 0483:2016 SGS Thomson Microelectronics Fingerprint Reader >> > ID 0a5c:2110 Broadcom Corp. Bluetooth Controller >> > 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:20ac Audio device: Intel >> > Corporation 82801H >> > >> > Modem interrupt assignment and sharing: >> > 17: 1329 76 IO-APIC-fasteoi uhci_hcd:usb6, >> > firewire_ohci, HDA Intel >> > --- Bootup diagnostics for card in PCI slot 00:1b.0 >> > ---- >> > pci 0000:00:1b.0: reg 10 64bit mmio: >> > [0xfe220000-0xfe223fff] >> > pci 0000:00:1b.0: PME# supported from D0 D3hot >> > D3cold >> > pci 0000:00:1b.0: PME# >> > disabled >> > HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ >> > 17 >> > HDA Intel 0000:00:1b.0: setting latency timer to >> > 64 >> > input: HDA Digital PCBeep >> > as /devices/pci0000:00/0000:00:1b.0/input/input10 >> > >> > 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.20 >> > The modem cards detected by "aplay -l" are: None >> > >> > >> > The /proc/asound/pcm file reports: >> > ----------------------- >> > 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 2 >> > 00-01: AD198x Digital : AD198x Digital : playback 1 >> > >> > about /proc/asound/cards: >> > ------------------------ >> > 0 [Intel ]: HDA-Intel - HDA Intel >> > HDA Intel at 0xfe220000 irq 17 >> > >> > PCI slot 00:1b.0 has a High Definition Audio Card >> > The drivers are in the kernel modules tree at: >> > >> > /lib/modules/2.6.30.9-96.fc11.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko >> > /lib/modules/2.6.30.9-102.fc11.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko >> > /lib/modules/2.6.30.9-99.fc11.x86_64/kernel/sound/pci/hda/snd-hda-intel.ko >> > UNEXPECTED HDA diagnostic >> > outcome. >> > === 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:20ac >> > IRQ=17 >> > HDA=8086:284b >> > SOFT=8086:284b.HDA >> > ArchivedChip=0x14f12bfa >> > CodecClass=14f1 >> > IDENT=hsfmodem >> > Driver=hsfmodem-drivers >> > >> > For candidate modem in: 00:1b.0 >> > 0403 Audio device: Intel Corporation 82801H >> > Primary device ID: 8086:284b >> > Subsystem PCI_id 17aa:20ac >> > Softmodem codec or chipset from diagnostics: >> > from Archives: 0x14f12bfa >> > >> > >> > >> > Support type needed or chipset: hsfmodem >> > >> > >> > Writing DOCs/Intel.txt >> > >> > For owners of a Dell PCs with Conexant HSF modems, a driver source >> > package with full speed enabled is available, but requires driver >> > compiling. Read >> > DOCs/Conexant.txt >> > >> > >> > Start at http://www.linuxant.com/drivers/hsf/full for >> > eventually download of a hsfmodem-7.68.00.12full_k.???.zip package >> > with ??? the package type (deb, rpm, tar etc) >> > These packages have compiled drivers but will also compile a driver, >> > if there is a mismatch between the resident kernel and provided driver. >> > The generic hsfmodem-7.68.00.12full.tar.gz package only provides >> > compiling support >> > >> > >> > Start at http://www.linuxant.com/drivers/hsf/downloads-license.php to >> > find the >> > hsfmodem package matching your System. For several Linux distros, there >> > are >> > precompiled drivers matched to specific kernels. These have within the >> > FileName, >> > your KernelVersion: >> > 2.6.30.9_102.fc11.x86_64 >> > They can be found through >> > http://www.linuxant.com/drivers/hsf/full/downloads.php >> > A more precise location may be given a few paragraphs >> > below. >> > If an EXACT Match with your your KernelVersion is not found, one of >> > the >> > "Generic packages with source" near the bottom of the page must be >> > used. >> > Downloaded packages must be moved into the Linux partition (home folder >> > is OK) >> > and unzipped >> > with: >> > unzip >> > hsf*.zip >> > The installation command for a .deb suffic packages is, with root/adm >> > permission: >> > dpkg -i >> > hsf*.deb >> > while for .rpm suffix it is, >> > with: >> > rpm -i >> > hsf*.rpm >> > >> > Support for Conexant chips hosted on High Definition Audio cards may >> > require >> > installation of additional packages, one of the alsa-driver-linuxant >> > packages >> > on http://www.linuxant.com/alsa-driver/ At the same time download >> > the >> > alsa-driver-1.0.17-1.patch , in case it prove to be later needed. During >> > the >> > hsfmodem install, there will be a message if there is necessary >> > installation of >> > alsa-driver-linuxant >> > >> > >> > The installation command for a .deb suffic packages is, with root/adm >> > permission: >> > dpkg -i >> > hsf*.deb >> > while for .rpm suffix it is, >> > with: >> > rpm -i >> > hsf*.rpm >> > >> > There may a message that "Dependencies" are not satisfied. In this case >> > the Ubuntu/Debian packages to be installed are linux-libc-dev & >> > libc6-dev. >> > Package >> > >> > names may be different for other Linuxes. If not on your install CD, >> > these >> > packages can be searched for at http://packages.ubuntu.com. After >> > download, >> > they can be coinstalled >> > with: >> > >> > dpkg -i >> > li*.deb >> > >> > Again try the >> > alsa-driver-linuxant >> > >> > >> > There may be a message that the patch must be applied. In this case get >> > the >> > ftp://ftp.alsa-project.org/pub/driver/alsa-driver-1.0.17.tar.bz2 >> > Under Linux, this package is unpacked >> > with: >> > $ tar jxf >> > alsa*.tar.bz2 >> > Next the patch is applied >> > with: >> > $ patch -p0 < >> > alsa-driver-1.0.17-1.patch >> > >> > See http://linmodems.technion.ac.il/bigarch/archive-eighth/msg00838.html >> > for details on compiling and installing replacement snd-hda-intel + its >> > dependent drivers. >> > After the installation is completed, rerun the hsfmodem installation. >> > Reboot and try to detect the modem with Root permission: >> > wvdialconf /etc/wvdial.conf >> > >> > Read DOCs/Conexant.txt >> > >> > Writing DOCs/Conexant.txt >> > >> > >> > Completed candidate modem analyses. >> > >> > The base of the UDEV device file system is: /dev/.udev >> > >> > Versions adequately match for the compiler installed: 4.4.1 >> > and the compiler used in kernel assembly: 4.4.1 >> > >> > >> > >> > Minimal compiling resources appear complete: >> > make utility - /usr/bin/make >> > Compiler version 4.4 >> > linuc_headers base folder /lib/modules/2.6.30.9-102.fc11.x86_64/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: >> > -r-xr-xr-x. 1 root root 352328 2009-03-06 17:47 /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 >> > lock >> > >> > 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 >> > virbr0 wlan0 wmaster0 >> > 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 -------- >> > >> > >> > > >
