Re: Intel HDA, Si3054 and ALSA

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

 



Codec: Generic 11c1 Si3054
Address: 1
Vendor Id: 0x11c11040
Subsystem Id: 0x11c10001
Revision Id: 0x100200
Modem Function Group: 0x1

 The audio card hosts a softmodem chip with Vendor ID:  0x11c11040

 The softmodem chip 0x11c11040 is NOT YET  supported under Linux.
 Code must be developed by manufacture LSI Inc.
 See details in
http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00915.html

See Info General.txt about alternatives

Condolences

MarvS

On Nov 22, 2007 1:29 PM, Peter Skensved <peter@xxxxxxxxxxxxxxxxxx> wrote:
> On Thu, Nov 22, 2007 at 01:32:04AM -0500, Marvin Stodolsky wrote:
> > Peter,
> >
> > The entire ModemData.txt  output from scanModem is needed, please.
> > Si3054 is a base on which further processing to diverse modem chips is done,
> > Some supported and some not.
> >
> > Note that to compile an ALSA competent slmodemd, there must first be
> > installed a package libasound2-dev
> > The compile must be done within the modem/ subfolder with commands
> >   make clean
> >   make SUPPORT_ALSA=1
> >
> > MarvS
>
>
>    ok here it is :
>
>
> --------------------------  System information ----------------------------
> CPU=i686,  CentOS release 5 (Final)
> Kernel
> Linux version 2.6.18-8.1.14.el5 (mockbuild@xxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20070105 (Red Hat 4.1.1-52)) #1 SMP Thu Sep 27 18:58:54 EDT 2007
>  scanModem update of:  20071109
>
>
>  There are no blacklisted modem drivers in /etc/modprobe*  files
>  ---ALSA bootup diagnostics ---
>
> The Advanced Linux Sound Architecture (ALSA) packages providing audio support on your System,
> also includes drivers for some modems. High Definition Audio (HDA) cards can themselves host
> a softmodem chipset, with both audio+modem supported by a snd-hda-intel driver.
> The ALSA diagnostics are written during bootup to /proc/asound/ folders.
>
>
>  The modem codec file for the the HDA card is: /proc/asound/card0/codec#1
> --------------------------------------------------------
> Codec: Generic 11c1 Si3054
> Address: 1
> Vendor Id: 0x11c11040
> Subsystem Id: 0x11c10001
> Revision Id: 0x100200
> Modem Function Group: 0x1
>
>  The audio card hosts a softmodem chip with Vendor ID:  0x11c11040
>
>  The softmodem chip 0x11c11040 is not yet supported under Linux.
>  Code must be developed by manufacture LSI Inc.
>  See details in http://linmodems.technion.ac.il/bigarch/archive-seventh/msg00915.html
>  Read InfoGeneral.txt about alternatives modem hardware.
> Summary card and chipset information is in:
> /proc/asound/cards:
>  0 [Intel          ]: HDA-Intel - HDA Intel
>                       HDA Intel at 0xb0000000 irq 50
>
> /proc/asound/pcm:
> 00-06: Si3054 Modem : Si3054 Modem : playback 1 : capture 1
> 00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1
>
>  A copy of /proc/asound had been copied to Modem/ALSAroot.tgz
>  PCI slot 00:1b.0 has a High Definition Audio Card
> USB modem not detected by lsusb
>
> For candidate card, firmware information and bootup diagnostics are:
>
>  PCI slot       PCI ID          SubsystemID     Name
>  ----------     ---------       ---------       --------------
>  00:1b.0        8086:27d8       17aa:2066       Audio device: Intel Corporation 82801G
>
>  Modem interrupt assignment and sharing:
>  50:      84017      82962   IO-APIC-level  HDA Intel
>  --- Bootup diagnostics for card in PCI slot 00:1b.0 ----
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> ACPI: PCI interrupt for device 0000:00:1b.0 disabled
> PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was 100006, writing 100000)
> PCI: Enabling device 0000:00:1b.0 (0000 -> 0002)
> ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 50
> PCI: Setting latency timer of device 0000:00:1b.0 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 Bootup.txt about possible fixes.
>  Send dmesg.txt along with ModemData.txt to discuss@xxxxxxxxxxxxx
>  if help is needed.
>
>
>  === Finished modem firmware and bootup diagnostics section. ===
>  === Next deducing cogent software ===
>
>   The High Defintion Audio card with PCI ID 8086:27d8 may host a soft modem chip.
>
> There is candidate modem software.
>
>  For candidate modem in PCI bus:  00:1b.0
>    Class 0403: 8086:27d8 Audio device: Intel Corporation 82801G
>       Primary PCI_id  8086:27d8
>     Subsystem PCI_id  17aa:2066
>     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: Agere_11c11040_chip_is_not_supported
>
>
> Writing Intel.txt
>
>  Completed candidate modem analyses.
>
>  The base of the UDEV device file system is: /dev/.udev
>
>  Versions adequately match for the compiler installed: 4.1.1
>              and the compiler used in kernel assembly: 4.1.1
>
>
>
>  Minimal compiling resources appear complete:
>    make utility - /usr/bin/make
>    Compiler version 4.1
>    linuc_headers base folder /lib/modules/2.6.18-8.1.14.el5/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.
>
>
>
> 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 pacakage
> 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:
>         -r-xr-xr-x 1 root root 312236 Mar 14  2007 /usr/sbin/pppd
>
> In case of an "error 17" "serial loopback" problem, see:
>     http://phep2.technion.ac.il/linmodems/archive-sixth/msg02637.html
>
> To enable dialout without Root permission do:
>         $ su - root  (not for Ubuntu)
>          chmod a+x /usr/sbin/pppd
> or under Ubuntu related Linuxes
>          chmod a+x /usr/sbin/pppd
>
> Checking settings of:   /etc/ppp/options
> lock
>
> 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 eth1
> 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:
> /etc/udev/rules.d/50-udev.rules:KERNEL=="modems/mwave*",        NAME="%k", GROUP="uucp", MODE="0660"
>      Within /etc/modprobe.conf files:
>
>      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