Re: PCI Modem (apparently snd_via82xx_modem): ModemData.txt

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

 



Martin,

There is a slight disagreement, my gut feeling is that
SLMODEMD.gcc.4.4-alsa-1.0.20.tar.gz should do the job and not the
slamr module which is loaded.  But the diagnostics disagree:

> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: VIA 8235 : VIA 8235 : playback 4 : capture 1
> 00-01: VIA 8235 : VIA 8235 : playback 1 : capture 1
>
> about /proc/asound/cards:
> ------------------------
>   0 [V8235          ]: VIA8233 - VIA 8235
>                        VIA 8235 with ALC202 at 0xe100, irq 5
> === Finished firmware and bootup diagnostics, next deducing cogent
> software. ===

we should see a Modem section here and it is not there?  Marv can you
please advice Matin here what to try.

 For candidate modem in:  00:11.6
   0780 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller
      Primary device ID:  1106:3068
    Subsystem PCI_id  1631:e004
    Softmodem codec or chipset from diagnostics: mc97, from a slamr test.
                               from    Archives: SIL22
       Diagnostics and the Archive data DISAGREE


 Support type needed or chipset: slmodemd

  An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-via82xx-modem
  provides Low Level support enabling contact with the modem hardware.
  For all BUT Conexant chip soft modems (using hsfmodem software)
  complementary High Level support is through a Smartlink utility:  slmodemd

  Download from http://linmodems.technion.ac.il/packages/smartlink/
  the package SLMODEMD_gcc4.4_alsa1.0.20.tar.gz having a compiled
slmodemd. Unpack under Linux with:
        $ tar zxf SLMODEMD_gcc4.4_alsa1.0.20.tar.gz
  and read instructions therein. But briefly, the modem is setup with command:
        sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
  reporting dynamic creation of ports:
        /dev/ttySL0 --> /dev/pts/N   , with N some number
  Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
through guidance.

Thanks for sending ModemData.txt.

Regards,

Antonio

On 7/2/10, Martin Ueding <mu@xxxxxxxxxxxxxxxx> wrote:
> Hello,
>
> Here is my full ModemData.txt
>
> Greetings,
>
> Martin
>
> --
>
>   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.31-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. 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,  Ubuntu ,  ALSA_version=1.0.20
> Linux version 2.6.31-14-generic (buildd@rothera) (gcc version 4.4.1
> (Ubuntu 4.4.1-4ubuntu8) ) #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009
>   scanModem update of:  2010_05_29
> The modem symbolic link is /dev/modem -> ttySL0
> Distrib_ID=Ubuntu
> DistribCodeName=karmic
> AptRepositoryStem=http://de.archive.ubuntu.com/ubuntu/
>
>
> The dkms driver upgrade utilities are installed,
>
>   There are no blacklisted modem drivers in /etc/modprobe*  files
>
>   Potentially useful modem drivers now loaded are:
>     snd_via82xx_modem       slamr
>
> slamrTest=mc97
> Attached USB devices are:
>   ID 046d:c50a Logitech, Inc. Cordless Mouse
> 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
>
> Candidate PCI devices with modem chips are:
> 00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem
> Controller (rev 80)
> High Definition Audio cards can host modem chips.
>
> For candidate card in slot 00:11.6, firmware information and bootup
> diagnostics are:
>   PCI slot	PCI ID		SubsystemID	Name
>   ----------	---------	---------	--------------
>   00:11.6	1106:3068	1631:e004	Communication controller: VIA
> Technologies, Inc. AC'97 Modem Controller
>
>   Modem interrupt assignment and sharing:
>    5:        156    XT-PIC-XT        VIA8233
>   --- Bootup diagnostics for card in PCI slot 00:11.6 ----
> [    0.067052] pci 0000:00:11.6: reg 10 io port: [0xe200-0xe2ff]
> [    8.145067] VIA 82xx Modem 0000:00:11.6: PCI INT C -> Link[LNKC] ->
> GSI 5 (level, low) -> IRQ 5
> [    8.896055] VIA 82xx Modem 0000:00:11.6: setting latency timer to 64
> [    9.400284] VIA 82xx Modem 0000:00:11.6: PCI INT C disabled
> [    9.400318] VIA 82xx Modem: probe of 0000:00:11.6 failed with error
> -13
> [    9.922224] slamr 0000:00:11.6: PCI INT C -> Link[LNKC] -> GSI 5
> (level, low) -> IRQ 5
> [    9.922256] slamr 0000:00:11.6: setting latency timer to 64
> [   10.049699] slamr 0000:00:11.6: PCI INT C disabled
>
>   The PCI slot 00:11.6 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 modem cards detected by "aplay -l"  are: None
>
>
> The /proc/asound/pcm file reports:
> -----------------------
> 00-00: VIA 8235 : VIA 8235 : playback 4 : capture 1
> 00-01: VIA 8235 : VIA 8235 : playback 1 : capture 1
>
> about /proc/asound/cards:
> ------------------------
>   0 [V8235          ]: VIA8233 - VIA 8235
>                        VIA 8235 with ALC202 at 0xe100, irq 5
> === Finished firmware and bootup diagnostics, next deducing cogent
> software. ===
>
> Predictive  diagnostics for card in bus 00:11.6:
> 	Modem chipset  detected on
> NAME="Communication controller: VIA Technologies, Inc. AC'97 Modem
> Controller "
> CLASS=0780
> PCIDEV=1106:3068
> SUBSYS=1631:e004
> IRQ=5
> SOFT=1106:3068.MC97
> CodecArchived=SIL22
> slamrTest=mc97
> IDENT=slmodemd
> SLMODEMD_DEVICE=modem:1
> Driver=snd-via82xx-modem
>
>   For candidate modem in:  00:11.6
>     0780 Communication controller: VIA Technologies, Inc. AC'97 Modem
> Controller
>        Primary device ID:  1106:3068
>      Subsystem PCI_id  1631:e004
>      Softmodem codec or chipset from diagnostics: mc97, from a slamr
> test.
>                                 from    Archives: SIL22
>         Diagnostics and the Archive data DISAGREE
>
>
> Support type needed or chipset:	slmodemd
>
>   An ALSA (Advanced Linux Sound Architecture) modem driver:  snd-
> via82xx-modem
>   provides Low Level support enabling contact with the modem hardware.
>   For all BUT Conexant chip soft modems (using hsfmodem software)
>   complementary High Level support is through a Smartlink utility:
> slmodemd
>
>   Download from http://linmodems.technion.ac.il/packages/smartlink/
>   the package SLMODEMD_gcc4.4_alsa1.0.20.tar.gz having a compiled
> slmodemd. Unpack under Linux with:
>   	$ tar zxf SLMODEMD_gcc4.4_alsa1.0.20.tar.gz
>   and read instructions therein. But briefly, the modem is setup with
> command:
>   	sudo slmodemd -c YOUR_COUNTRY --alsa modem:1
>   reporting dynamic creation of ports:
> 	/dev/ttySL0 --> /dev/pts/N   , with N some number
>   Read DOCs/Smartlink.txt and Modem/DOCs/YourSystem.txt for follow
> through guidance.
>
> Writing DOCs/Smartlink.txt
> ============ end Smartlink section =====================
>
>   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.31-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 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.
>
>
> Compressed files at: /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 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:
> 	-rwsr-xr-- 1 root dip 277352 2009-02-20 18:25 /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
>
> For guidance on FAX usage, get from
> http://linmodems.technion.ac.il/packages/
>    get faxing.tar.gz
> It has samples for a modem using port /dev/ttySL0, which must be
> changed to match your modem's port.
>
> 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:   lrwxrwxrwx 1 root root 6
> 2010-07-02 16:04 /dev/modem -> ttySL0
> slmodemd created symbolic link /dev/ttySL0:
>       Within /etc/udev/ files:
>
>       Within /etc/modprobe.conf files:
> /etc/modprobe.d/alsa-base.conf:options snd-atiixp-modem index=-2
> /etc/modprobe.d/alsa-base.conf:options snd-via82xx-modem index=-2
> /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
>       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