Re: Sarit, Thailand Debian GNU/Linux 4.0 kernel 2.6.18-6-amd64

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

 



sarit,

You have two possibilities

<quote>
 For candidate modem in PCI bus:  00:14.2
  Class 0403: 1002:4383 Audio device: ATI Technologies Inc SB600 Azalia
     Primary PCI_id  1002:4383
   Subsystem PCI_id  103c:30c2
   Softmodem codec or chipset from diagnostics:
                              from    Archives:



 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:

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/
</quote>

Regards,

Antonio

On Wed, Apr 9, 2008 at 12:53 PM, sarit ritwirune <coca_yaba@xxxxxxxxxxx> 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 Debian GNU/Linux 4.0  kernel 2.6.18-6-amd64
>   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=x86_64,  Debian GNU/Linux 4.0
>  Linux version 2.6.18-6-amd64 (Debian 2.6.18.dfsg.1-17etch1) (dannf@xxxxxxxxxx) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Wed Jan 23 06:27:23 UTC 2008
>   scanModem update of:  2008_02_07
>
>
>   There are no blacklisted modem drivers in /etc/modprobe*  files
>
>  The Advanced Linux Sound Architecture (ALSA) packages providing audio support,
>  also includes drivers for some modems. The ALSA diagnostics are written during
>  bootup to /proc/asound/ folders.
>
>   The /proc/asound/ audio+modem diagostics are being copied.
>   Finished copy to Modem/ALSAzero.tgz
>
>  The ALSA verion is 1.0.13
>  The modem cards detected by "aplay -l"  are:
>
>
>  The /proc/asound/pcm file reports:
>  -----------------------
>  00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1
>
>  about /proc/asound/cards:
>  ------------------------
>   0 [SB             ]: HDA-Intel - HDA ATI SB
>                       HDA ATI SB at 0x6a000000 irq 10
>
>  USB modem not detected by lsusb
>
>  For candidate card in slot 00:14.2, firmware information and bootup diagnostics are:
>   PCI slot       PCI ID          SubsystemID     Name
>   ----------     ---------       ---------       --------------
>   00:14.2        1002:4383       103c:30c2       Audio device: ATI Technologies Inc SB600 Azalia
>
>   Modem interrupt assignment and sharing:
>   10:      11217          XT-PIC  libata, yenta, HDA Intel, wlan0
>   --- Bootup diagnostics for card in PCI slot 00:14.2 ----
>  PCI: Cannot allocate resource region 0 of device 0000:00:14.2
>
>
>   === Finished modem firmware and bootup diagnostics section. ===
>   === Next deducing cogent software ===
>
>
>
>
>  Predictive diagnostics for card in PCI bus 00:14.2:
>         Modem chipset not detected on
>  CLASS="Class 0403: 1002:4383"
>  NAME="Audio device: ATI Technologies Inc SB600 Azalia"
>  PCIDEV=1002:4383
>  SUBSYS=103c:30c2
>  SUBven=103c
>  IRQ=10
>  HDA=1002:4383
>  SOFT=1002:4383.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 1002:4383.
>   If another modem card is present, then most likely 1002:4383 does not host a modem.
>   If another modem card has not been detected, then possibilities are:
>         1) A Conexant modem chip is present on 1002:4383, 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:
>          wvdialconf  /etc/wvdial.conf
>
>   For candidate modem in PCI bus:  00:14.2
>    Class 0403: 1002:4383 Audio device: ATI Technologies Inc SB600 Azalia
>       Primary PCI_id  1002:4383
>     Subsystem PCI_id  103c:30c2
>     Softmodem codec or chipset from diagnostics:
>                                from    Archives:
>
>
>
>   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:
>
>  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 --------------
>
>  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.2
>              and the compiler used in kernel assembly: 4.1.2
>
>
>
>   Minimal compiling resources appear complete:
>    make utility - /usr/bin/make
>    Compiler version 4.1
>    linuc_headers base folder /lib/modules/2.6.18-6-amd64/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/fglrx.tar.bz2 /usr/src/ndiswrapper-source.tar.bz2
>
>  For Debian and some related distributions, a package kernel-kbuild-2.6-18 may be needed to support driver compiling
>
>
>  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 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: eth1 wlan0
>  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/alsa-base-blacklist:# Uncomment these entries in order to blacklist unwanted modem drivers
>  /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-atiixp-modem
>  /etc/modprobe.d/alsa-base-blacklist:# blacklist snd-via82xx-modem
>      Within any ancient /etc/devfs files:
>
>      Within ancient kernel 2.4.n /etc/module.conf files:
>
>  --------- end modem support lines --------
>
>
>
>  _________________________________________________________________
>  Discover the new Windows Vista
>  http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE

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

  Powered by Linux