Send us the file /tmp/alsa-driver-linuxant.6296.log But you will have to run the install again to recreate it. Files in /tmp/ are deleted during a reboot. MarvS On Mon, May 5, 2008 at 9:05 PM, Graham Coward <coward@xxxxxxxxxxxxx> wrote: > Jonathan, > > Installation of ALSA deriver does not work. I get this error message: > > > Selecting previously deselected package linux-libc-dev. > (Reading database ... 116772 files and directories currently installed.) > Unpacking linux-libc-dev (from .../linux-libc-dev_2.6.24-16.30_i386.deb) > ... > Selecting previously deselected package libc6-dev. > Unpacking libc6-dev (from .../libc6-dev_2.7-10ubuntu3_i386.deb) ... > Setting up linux-libc-dev (2.6.24-16.30) ... > Setting up libc6-dev (2.7-10ubuntu3) ... > Selecting previously deselected package alsa-driver-linuxant. > (Reading database ... 117855 files and directories currently installed.) > Unpacking alsa-driver-linuxant (from > .../alsa-driver-linuxant_1.0.16.1-1_all.deb) ... > Setting up alsa-driver-linuxant (1.0.16.1-1) ... > Building kernel modules for the 2.6.24-16-generic kernel, please wait... > done. > ERROR: Build failed. Please review the build log at > /tmp/alsa-driver-linuxant.6296.log > dpkg: error processing alsa-driver-linuxant (--install): > subprocess post-installation script returned error exit status 2 > Errors were encountered while processing: > alsa-driver-linuxant > > Graham > > > > > On 6/05/2008 1:20 AM, Linuxant support (Jonathan) wrote: > > > Hi, > > > > for the 2.6.24-16-* kernels, we have pre-compiled HCF and DGC packages > available and we are working on making a HSF one in the near future as well. > > > > At the moment, the generic package in the DEB format of the HSF driver > will work well on Ubuntu Hardy. However, if you have a HDA modem, you *must* > install first alsa-driver-linuxant available at: > > > > http://www.linuxant.com/alsa-driver/ > > > > before installing the HSF driver or else it will not work. > > > > Regards, > > > > > > Jonathan > > Technical specialist / Linuxant > > www.linuxant.com > > support@xxxxxxxxxxxx > > > > > > > > Marvin Stodolsky wrote: > > > > > Jonathan, > > > The Ubuntu Hardy release is out with 2.6.24-16-* kernels. It > > > would be useful to have compiled drivers for this set. > > > > > > Graham, > > > > > > If it is an internal modem, a Conexant modem chip is most likely in > > > the Subsystem of: > > > Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > > > Primary PCI_id 8086:27d8 > > > Subsystem PCI_id 1631:c017 > > > > > > Read the Conexant.txt > > > > > > From http://www.linuxant.com/drivers/hsf/full/downloads.php > > > get the hsfmodem_7.68.00.09full_i386.deb.zip > > > Under Ubuntu: > > > $ unzip hsf*.zip > > > $ sudo dpkg -i hsf*.deb > > > and follow through with the output instructions. > > > The drivers will be compiled enroute. > > > > > > A reboot may be necessary before trying to detect the modem with: > > > $ wvdialconf /etc/wvdial.conf > > > if detected, edit in your dialout info with: > > > $ sudo gedit /etc/wvdial.conf > > > removing the ; < > symbols > > > > > > Please report back after thus testing. > > > > > > MarvS > > > scanModem > > > > > > On Sat, May 3, 2008 at 11:14 PM, Graham Coward <coward@xxxxxxxxxxxxx> > 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.24-16-generic > > > > With this Subject Line cogent experts will be alerted, and useful > case > > > > names left in the Archive. > > > > YourCountry will enable Country specific guidance. Your contry's > local > > > > Linux experts > > > > 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.24-16-generic (buildd@palmer) (gcc version 4.2.3 > (Ubuntu > > > > 4.2.3-2ubuntu7)) #1 SMP Thu Apr 10 13:23:42 UTC 2008 > > > > scanModem update of: 2008_05_01 > > > > > > > > There are no blacklisted modem drivers in /etc/modprobe* files > > > > USB modems not recognized > > > > 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 1631:c017 Audio device: Intel > > > > Corporation 82801G > > > > > > > > Modem interrupt assignment and sharing: > > > > 21: 7316 0 IO-APIC-fasteoi HDA Intel > > > > --- Bootup diagnostics for card in PCI slot 00:1b.0 ---- > > > > [ 30.540111] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 23 (level, > low) > > > > -> IRQ 21 > > > > [ 30.540140] PCI: Setting latency timer of device 0000:00:1b.0 to > 64 > > > > > > > > > > > > ===== 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. > > > > PCI slot 00:1b.0 has a High Definition Audio Card > > > > > > > > The ALSA verion is 1.0.15 > > > > The modem cards detected by "aplay -l" are: > > > > > > > > > > > > The /proc/asound/pcm file reports: > > > > ----------------------- > > > > 00-01: ALC260 Digital : ALC260 Digital : playback 1 > > > > 00-00: ALC260 Analog : ALC260 Analog : playback 1 : capture 1 > > > > > > > > about /proc/asound/cards: > > > > ------------------------ > > > > 0 [Intel ]: HDA-Intel - HDA Intel > > > > HDA Intel at 0x4c340000 irq 21 > > > > === Finished firmware and bootup diagnostics, next deducing cogent > > > > software. === > > > > > > > > A candidate modem is not evident among the PCI devices: > > > > ------------------------------------------------ > > > > 00:02.0 VGA compatible controller: Intel Corporation Mobile > 945GM/GMS, > > > > 943/940GML Express Integrated Graphics Controller (rev 03) > > > > 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, > > > > 943/940GML Express Integrated Graphics Controller (rev 03) > > > > 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High > > > > Definition Audio Controller (rev 02) > > > > 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) > SATA > > > > IDE Controller (rev 02) > > > > 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus > Controller (rev > > > > 02) > > > > 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG > Network > > > > Connection (rev 02) > > > > 05:02.0 FireWire (IEEE 1394): O2 Micro, Inc. Firewire (IEEE 1394) > (rev 02) > > > > 05:02.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD > Controller > > > > (rev 01) > > > > 05:02.3 Mass storage controller: O2 Micro, Inc. Integrated MS/xD > Controller > > > > (rev 01) > > > > 05:08.0 Ethernet controller: Intel Corporation PRO/100 VE Network > > > > Connection (rev 02) > > > > ------------------------------------------------ > > > > with USB and bridge devices not displayed. > > > > > > > > If your modem is connected by an external serial cable, > > > > or mounted internally on an ISA card, scanModem would not access it. > > > > Try with Root permission > > > > $ sudo wvdialconf /etc/wvdial.conf > > > > to detect these modem types and some USB modems. > > > > If the detection is successful, read the wvdial.txt . > > > > Edit the /etc/wvdial.conf with Root permission: > > > > sudo gedit /etc/wvdial.conf > > > > will be able to dial out with Root permission: > > > > sudo wvdial > > > > > > > > Many modems for which scanModem fails have Conexant chips. > > > > From http://www.linuxant.com/drivers/modemident.php > > > > get the ListModem tool, which will report on Conexant chipset modems > > > > > > > > If the above tests fail, please provide any independent information > > > > available on your modem. > > > > If an alternative boot into Microsoft windows can be done, do mouse > > > > clicks on: > > > > Start > Settings > Control Panel > Classical View (for Window XP) > > > > > System > > > > > Hardware > Device Manager > Modems > Click on the + > Modem. Double > click > > > > to > > > > expand the graphic. Manufacturer information may be displayed. For > example, > > > > CXT > > > > stands for Conexant. Click the Diagnostics Tab. Record any hardware > ID or > > > > vendor > > > > and device information. > > > > Next do the Query Modem and record the ATI specifications displayed > such > > > > as: > > > > ATI3 - Agere SoftModem Version 2.1.22 > > > > ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27 > > > > Try to identify the modem setup file, with name perhaps MODEM.INF. > > > > If may contain chipset Vendor informaton. > > > > > > > > The /proc/asound/ audio+modem diagostics are being copied. > > > > Finished copy to Modem/ALSAgraham.tgz > > > > > > > > Predictive diagnostics for card in bus 00:1b.0: > > > > Modem chipset not detected on > > > > CLASS="Class 0403: 8086:27d8" > > > > NAME="Audio device: Intel Corporation 82801G " > > > > PCIDEV=8086:27d8 > > > > SUBSYS=1631:c017 > > > > IRQ=21 > > > > HDA=8086:27d8 > > > > SOFT=8086:27d8.HDA > > > > > > > > > > > > High Definition Audio (HDA) cards MAY host a modem chip in their > > > > Subsystem, > > > > and many are supported by the ALSA audio+modem driver snd-hda-intel > > > > A modem was not detected on HDA card 8086:27d8. > > > > If another modem card is present, then most likely 8086:27d8 does not > host > > > > a modem. > > > > If another modem card has not been detected, then possibilities are: > > > > 1) A Conexant modem chip is present on 8086:27d8, as Conexant > chips > > > > are frequently not detectable by ALSA diagnostics > > > > 2) The modem may be of the older non-PCI Controller Chipset > > > > (hardware) type. > > > > Try detection with Root permission: > > > > sudo wvdialconf /etc/wvdial.conf > > > > > > > > For candidate modem in: 00:1b.0 > > > > Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G > > > > Primary PCI_id 8086:27d8 > > > > Subsystem PCI_id 1631:c017 > > > > Softmodem codec or chipset from diagnostics: > > > > from Archives: > > > > > > > > > > > > > > > > Support type needed or chipset: > > > > > > > > Support can likely be achieved through two mutually exclusive > alternatives: > > > > 1) The hsfmodem software for Conexant chipset modems: Read > Conexant.txt > > > > The following ALSA alternative CANNOT work with Conexant modems. > > > > > > > > 2) An ALSA modem driver plus slmodemd. Read Smartlink.txt for > details, and > > > > to test get the package SLMODEMD.gcc4.2.tar.gz from: > > > > http://linmodems.technion.ac.il/packages/smartlink/ > > > > > > > > ----------------end Softmodem section -------------- > > > > > > > > Writing 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 > > > > Conexant.txt > > > > > > > > Read Conexant.txt > > > > > > > > Writing Conexant.txt > > > > > > > > Writing Smartlink.txt > > > > ============ end Smartlink section ===================== > > > > > > > > > > > > The base of the UDEV device file system is: /dev/.udev > > > > > > > > Versions adequately match for the compiler installed: 4.2.3 > > > > and the compiler used in kernel assembly: 4.2.3 > > > > > > > > > > > > > > > > Minimal compiling resources appear complete: > > > > make utility - /usr/bin/make > > > > Compiler version 4.2 > > > > linuc_headers base folder /lib/modules/2.6.24-16-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 libc6-dev (and > for > > > > Debian/Ubuntu, linux-libc-dev). The also required headers of package > libc6 > > > > are commonly installed by default. 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 package > > > > 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 269256 2007-10-05 05:57 /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/YourSystem.txt concerning other COMM channels: eth0 wlan0 > > > > wmaster0 > > > > 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: > > > > > > > > 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 -------- > > > > > > > > > > > > > > > > > > > >
