Mahmood "Jonathan" <modem.support@xxxxxxxxxxxx> can best advise you. Run $ sudo hsfconfig --help $ sudo hsfconfig --diagnose whose output will be written to the /tmp/ folder. Send that output to Jonathan MarvS On Sun, May 24, 2009 at 10:42 AM, Mahmood Naderan <mahmood.nt@xxxxxxxxx> wrote: > I don't know what mistake I made... after installing the HSF package, > the sound driver unexpectedly terminated and after then there was no > sound from the system. > I tried to install the ALSA driver again and here is the output: > > root@magma:~/modem# dpkg -i > alsa-driver-linuxant_1.0.20.0_k2.6.28_11_generic_ubuntu_i386.deb > (Reading database ... 121262 files and directories currently installed.) > Preparing to replace alsa-driver-linuxant > 1.0.20.0-k2.6.28-11-generic-1 (using > alsa-driver-linuxant_1.0.20.0_k2.6.28_11_generic_ubuntu_i386.deb) ... > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > ERROR: Can't stop the Conexant HSF softmodem driver! > ^Cmake: *** [uninstall] Interrupt > dpkg: warning - old pre-removal script killed by signal (Interrupt) > dpkg - trying script from the new package instead ... > dpkg: ... it looks like that went OK. > Unpacking replacement alsa-driver-linuxant ... > Setting up alsa-driver-linuxant (1.0.20.0-k2.6.28-11-generic-1) ... > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > Warning: Module hsfhda is in use > Warning: Module hsfserial is in use by hsfhda > Warning: Module hsfengine is in use by hsfhda,hsfserial > Warning: Module hsfosspec is in use by hsfhda,hsfserial,hsfengine > ERROR: Can't stop the Conexant HSF softmodem driver! > Pre-built driver modules that seem compatible with your system were found under: > /usr/lib/alsa-driver-linuxant/binaries/2.6.28-11-generic > ^Cmake: *** [install-modules] Interrupt > dpkg: error processing alsa-driver-linuxant (--install): > subprocess post-installation script killed by signal (Interrupt) > Errors were encountered while processing: > alsa-driver-linuxant > root@magma:~/modem# > > > > > > On 5/21/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: >>>> 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 >> >> On Thu, May 21, 2009 at 2:25 AM, Mahmood Naderan <mahmood.nt@xxxxxxxxx> >> wrote: >>> When I want to install the .deb file, I get this error: >>> Error: Dependency is not satisfiable: alsa-driver-linuxant. >>> >>> I searched ubuntu jaunty packages but found nothing. Anybody has an idea? >>> >>> >>> On 5/21/09, Marvin Stodolsky <marvin.stodolsky@xxxxxxxxx> wrote: >>>> Mahmood >>>> >>>> >>>> From http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >>>> download hsfmodem-7.80.02.02full_k2.6.28_11_generic_ubuntu_i386.deb.zip >>>> Under Linux unpack with: >>>> $ unzip hsfmodem*.zip >>>> Then install with: >>>> $ sudo dpkg -i hsfmodem*.deb >>>> Subsequently, the modem should be found with >>>> $ sudo wvdialconf /etc/wvdial.conf >>>> Edit in your personal information with: >>>> $ sudo gedit /etc/wvdial.conf >>>> and try dialing out with: >>>> $ sudo wvdial. >>>> See DOCs/Testing.txt for details. >>>> >>>> Read DOCs/Conexant.txt >>>> >>>> MarvS >>>> >>>> On Wed, May 20, 2009 at 11:22 AM, Mahmood Naderan <mahmood.nt@xxxxxxxxx> >>>> wrote: >>>>> 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-11-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-11-generic (buildd@palmer) (gcc version 4.3.3 >>>>> (Ubuntu 4.3.3-5ubuntu4) ) #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 >>>>> scanModem update of: 2009_05_12 >>>>> >>>>> 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 093a:2510 Pixart Imaging, Inc. >>>>> ID 04f2:b016 Chicony Electronics Co., Ltd >>>>> ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB >>>>> ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor >>>>> If a cellphone is not detected, see >>>>> http://ubuntuforums.org/archive/index.php/t-878554.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 103c:30cd Audio device: Intel >>>>> Corporation 82801H >>>>> >>>>> Modem interrupt assignment and sharing: >>>>> 22: 1273 1227 IO-APIC-fasteoi HDA Intel >>>>> --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- >>>>> [ 0.938819] pci 0000:00:1b.0: reg 10 64bit mmio: >>>>> [0xf4500000-0xf4503fff] >>>>> [ 0.938858] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold >>>>> [ 0.938862] pci 0000:00:1b.0: PME# disabled >>>>> [ 13.012913] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 22 (level, >>>>> low) -> IRQ 22 >>>>> [ 13.012968] 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: None >>>>> >>>>> >>>>> The /proc/asound/pcm file reports: >>>>> ----------------------- >>>>> 00-00: CONEXANT Analog : CONEXANT Analog : playback 1 : capture 1 >>>>> 00-01: Conexant Digital : Conexant Digital : playback 1 >>>>> >>>>> about /proc/asound/cards: >>>>> ------------------------ >>>>> 0 [Intel ]: HDA-Intel - HDA Intel >>>>> HDA Intel at 0xf4500000 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-11-generic/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=103c:30cd >>>>> IRQ=22 >>>>> HDA=8086:284b >>>>> SOFT=8086:284b.HDA >>>>> 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 103c:30cd >>>>> Softmodem codec or chipset from diagnostics: >>>>> from Archives: >>>>> >>>>> >>>>> >>>>> 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/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.28_11_generic >>>>> 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: >>>>> sudo 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: >>>>> sudo alsa* -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: >>>>> sudo 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: >>>>> sudo wvdialconf /etc/wvdial.conf >>>>> >>>>> From >>>>> http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php >>>>> download >>>>> hsfmodem-7.80.02.02full_k2.6.28_11_generic_ubuntu_i386.deb.zip >>>>> Under Linux unpack with: >>>>> $ unzip hsfmodem*.zip >>>>> Then install with: >>>>> $ sudo dpkg -i hsfmodem*.deb >>>>> Subsequently, the modem should be found with >>>>> $ sudo wvdialconf /etc/wvdial.conf >>>>> Edit in your personal information with: >>>>> $ sudo gedit /etc/wvdial.conf >>>>> and try dialing out with: >>>>> $ sudo wvdial. >>>>> See DOCs/Testing.txt for details. >>>>> >>>>> 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.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-11-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 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 >>>>> 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/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 -------- >>>>> >>>> >>> >> > > > -- > -------------------------- > *Mahmood Naderan* >