Re: Alejandro Nicolás, Spain, kernel 2.6.22-14-generic

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Alejandro,
The best guess is that Subsystem 104d:9005 of your audio card houses aConexant modem chip  . From  http://www.linuxant.com/drivers/hsf/full/downloads-ubuntu-x86.php download hsfmodem_7.68.00.07full_k2.6.22_14_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.
 Read Conexant.txt
Report back after the installation test.The hsfmodem package has good diagnostics.
MarvSscanModem maintainer
On Mon, Apr 21, 2008 at 4:51 AM, Alejandro Piñera Nicolás<apnicolas@xxxxxxxxxxxx> 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.22-14-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.22-14-generic (buildd@terranova) (gcc version 4.1.3>  20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Feb 12>  07:42:25 UTC 2008>   scanModem update of:  2008_04_16>  The modem symbolic link is /dev/modem -> ttySL0>   There are no blacklisted modem drivers in /etc/modprobe*  files>  USB modem not detected by lsusb>>  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    104d:9005    Audio device: Intel Corporation>  82801H>>   Modem interrupt assignment and sharing:>   22:        231        265   IO-APIC-fasteoi   HDA Intel>   --- Bootup diagnostics for card in PCI slot 00:1b.0 ---->  [   15.164000] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level,>  low) -> IRQ 22>  [   15.164000] 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-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 1>>  about /proc/asound/cards:>  ------------------------>   0 [Intel          ]: HDA-Intel - HDA Intel>                       HDA Intel at 0xfc400000 irq 22>>  Modem support under STAC92xx audio card hosts may require upgrade>  of snd-hda-intel + its dependent drivers to ALSA version  1.0.16.>  The following modem only worked after the upgrade from to 1.0.16 from 1.0.14>   PCI ID      SubsystemID     Name>   ---------   ---------       -------------->   8086:27d8   107b:0366       Audio device: Intel Corporation 82801G>  with ALSA diagnostics>  00-00: STAC92xx Analog : STAC92xx Analog : playback 1 : capture 2>  00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1>        Codec: Motorola Si3054>             for 107b:0366 hosted modem chip: 0x10573057>>  For a standard Ubuntu system needed to support the driver compilation were>>  === Finished firmware and bootup diagnostics, next deducing cogent>  software. ===>>  A candidate modem is not evident among the PCI devices:>  ------------------------------------------------>  00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio>  Controller (rev 03)>  00:1f.1 IDE interface: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)>  IDE Controller (rev 03)>  00:1f.2 SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E)>  SATA AHCI Controller (rev 03)>  00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller>  (rev 03)>  01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GT>  (rev a1)>  06:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or>  AGN Network Connection (rev 61)>  08:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8036 PCI-E>  Fast Ethernet Controller (rev 16)>  09:03.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant>  IEEE 1394 Host Controller>  09:03.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia>  Card Reader (SD/MMC/MS/MS PRO/xD)>  ------------------------------------------------>   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/ALSAalejandro.tgz>>  Predictive diagnostics for card in bus 00:1b.0:>     Modem chipset not detected on>  CLASS="Class 0403: 8086:284b">  NAME="Audio device: Intel Corporation 82801H ">  PCIDEV=8086:284b>  SUBSYS=104d:9005>  IRQ=22>  HDA=8086:284b>  SOFT=8086:284b.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:284b.>   If another modem card is present, then most likely 8086:284b 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:284b, 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:284b Audio device: Intel Corporation 82801H>       Primary PCI_id  8086:284b>     Subsystem PCI_id  104d:9005>     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.1.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.1.3>              and the compiler used in kernel assembly: 4.1.3>>>>   Minimal compiling resources appear complete:>    make utility - /usr/bin/make>    Compiler version 4.1>    linuc_headers base folder /lib/modules/2.6.22-14-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.>>  Compressed files at: /usr/src/alsa-driver.tar.bz2 /usr/src/sl-modem.tar.bz2>>>  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-04 21: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.>  ==========================================================>>  # start/stop the daemon when the USB modem is connected>  KERNEL=="slusb[0-9]*", GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon">   Checking for modem support lines:>   -------------------------------------->      /device/modem symbolic link:   lrwxrwxrwx 1 root root 6 2008-04-21>  09:24 /dev/modem -> ttySL0>  slmodemd created symbolic link /dev/ttySL0:>      Within /etc/udev/ files:>  /etc/udev/rules.d/030_sl-modem-daemon.rules:# start/stop the daemon when>  the USB modem is connected>  /etc/udev/rules.d/030_sl-modem-daemon.rules:KERNEL=="slusb[0-9]*",>  GROUP="dialout", RUN+="/etc/init.d/sl-modem-daemon">  /etc/udev/sl-modem-daemon.rules:# start/stop the daemon when the USB>  modem is connected>  /etc/udev/sl-modem-daemon.rules:KERNEL=="slusb[0-9]*", GROUP="dialout",>  RUN+="/etc/init.d/sl-modem-daemon">      Within /etc/modprobe.conf files:>  /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>  /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/sl-modem-daemon.modutils:install slamr modprobe>  --ignore-install ungrab-winmodem ;  modprobe --ignore-install slamr;>  test -e /dev/slamr0 || (/bin/mknod -m 660 /dev/slamr0 c 242 0>  2>/dev/null && chgrp dialout /dev/slamr0)>  /etc/modprobe.d/alsa-base:options snd-atiixp-modem index=-2>  /etc/modprobe.d/alsa-base: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 -------->>

[Index of Archives]     [Linux Media Development]     [Asterisk]     [DCCP]     [Netdev]     [X.org]     [Xfree86]     [Fedora Women]     [Linux USB]

  Powered by Linux