Hello Marvin,
This is what I get, I don't know how to fix it.
I am attaching some txt files from ./scanModem results.
Thanks for your help.
# slmodemd -c URUGUAY --alsa modem:1
error: mixer setup: attach hw:1 error: No such device
ALSA lib pcm.c:2014:(snd_pcm_open_conf) Invalid type for PCM modem:1
definition (id: modem, value: cards.pcm.modem)
error: alsa setup: cannot open playback device 'modem:1': Invalid argument
error: cannot setup device `modem:1'
# slmodemd -c URUGUAY --alsa hw:0,6
error: mixer setup: Off-hook switch not found for card hw:0
error: alsa setup: cannot open playback device 'hw:0,6': No such file or
directory
error: cannot setup device `hw:0,6'
On Friday 16 March 2007 21:25, you wrote:
> Re: slmodemd -c URUGUAY --alsa hw:0,6
>
> The slmodemd supported modems are in two categories.
> The newer and increasingly prevalant are HDA (High Definition Audio)
> controller which can host softmodem subsystems. These use the command
> format: slmodemd -c URUGUAY --alsa hw:0,N
> when N is usually 1 or 6
> If there are no System problems
> ./scanModem
> will be able to report whixh N to use.
>
> The older type are the older AC'97 type SoftModem Controller cards.
> For all of these but the Conexant chip subtype requiring hsfmodem
> software
> , the command is like:
> slmodemd -c URUGUAY --alsa modem:1
>
> To deal with System problems blocking a full scanModem diagnostic
> I long ago set a default output:
> slmodemd -c COUNTRY --alsa modem:1
> because it was usually correct.
>
> But with the increasing prevalance of HDA hosted modems,
> I'll have to chamge that default. In the meantme
> MUCH THANKS
> for all you who are helping out, and just remember that if it is a HDA
> based modem
> the needed command syntax is like
> slmodemd -c URUGUAY --alsa hw:0,N
>
> If some coming guidance, I'll illustrate how to recognize this amon
> the scanModem outputs.
>
> MarvS
>
> On 3/16/07, Antonio Olivares <olivares14031@xxxxxxxxx> wrote:
> > Ok,
> >
> > maybe this is one of those cases in which you need
> > to update alsa to a newer version and recompile. Or
> > instead of --alsa modem:1, try something like
> > # slmodemd -c URUGUAY --alsa hw 0:6, I am not sure
> >
> > or could be that the modem card is disabled in the
> > bootup process as the lines show,
> >
> > The PCI slot 00:1f.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 Bootup.txt about possible fixes.
> > Send dmesg.txt along with ModemData.txt to
> > discuss@xxxxxxxxxxxxx if help is needed.
> >
> > When you do
> > # slmodemd -c URUGUAY --alsa modem:1
> > open up another terminal and run dmesg and send to
> > discuss@xxxxxxxxxxxxx for further help.
> >
> > Regards,
> >
> > Antonio
> >
> > --- Daniel Stonek <daniel@xxxxxxxxxx> wrote:
> > > Hi Antonio,
> > > I have installed slmodemd (and removed hsfmodem)
> > > but
> > > # slmodemd -c URUGUAY --alsa modem:1
> > > error: mixer setup: attach hw:1 error: No such
> > > device
> > > ALSA lib pcm.c:2014:(snd_pcm_open_conf) Invalid type
> > > for PCM modem:1
> > > definition (id: modem, value: cards.pcm.modem)
> > > error: alsa setup: cannot open playback device
> > > 'modem:1': Invalid argument
> > > error: cannot setup device `modem:1'
> > >
> > > Thank you,
> > > Daniel
> > >
> > > On Friday 16 March 2007 11:16, you wrote:
> > > > Daniel,
> > > >
> > > > The following tells you what you need to do.
> > > >
> > > > Support type needed or chipset: slmodemd
> > > >
> > > > An ALSA (Advanced Linux Sound Architecture) modem
> > > > driver:
> > > > snd-intel8x0m
> > > > 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.1.tar.gz having a
> > >
> > > compiled
> > >
> > > > slmodemd. Unpack
> > > > under Linux with:
> > > > $ tar zxf SLMODEMD.gcc4.1.tar.gz
> > > > and read instructions therein. But briefly, the
> > >
> > > modem
> > >
> > > > is setup with
> > > > command:
> > > > slmodemd -c YOUR_COUNTRY --alsa modem:1
> > > > reporting dynamic creation of ports:
> > > > /dev/ttySL0 --> /dev/pts/N , with N some
> > > > number
> > > > Read Smartlink.txt and Modem/YourSystem.txt for
> > > > follow through
> > > > guidance.
> > > >
> > > > Regards,
> > > >
> > > > Antonio
> > > >
> > > > --- Daniel Stonek <daniel@xxxxxxxxxx> wrote:
> > > > > Please tell me how to install a working driver.
> > > > > Thank you. Daniel
> > > > >
> > > > > > Only plain text email is forwarded by the
> > > > >
> > > > > DISCUSS@xxxxxxxxxxxxx List Server.
> > > > > Do use the following as the email Subject Line:
> > > > > SomeName, YourCountry Mandriva Linux
> > > > > release 2007.0 (Official) for i586
> > > > > Kernel 2.6.17-5mdv on an i686 / kernel
> > >
> > > 2.6.17-5mdv
> > >
> > > > > This will alert cogent experts, and
> > >
> > > distinguish
> > >
> > > > > cases in the Archives.
> > > > > YourCountry will enable Country Code guidance.
> > > > > Occassionally responses are blocked by an
> > >
> > > Internet
> > >
> > > > > Provider mail filters.
> > > > > So in a day, also check the Archived responses
> > >
> > > at
> > >
> > > > > http://www.linmodems.org .
> > > > > Local Linux experts can be found through:
> > > > > http://www.linux.org/groups/index.html
> > > > > -------------------------- System information
> > > > > ----------------------------
> > > > > CPU=i686, Mandriva Linux release 2007.0
> > >
> > > (Official)
> > >
> > > > > for i586
> > > > > Kernel 2.6.17-5mdv on an i686 /
> > > > > Linux version 2.6.17-5mdv
> > >
> > > (rtp@xxxxxxxxxxxxxxxxxxxx)
> > >
> > > > > (gcc version 4.1.1 20060724 (prerelease)
> > > > > (4.1.1-3mdk)) #1 SMP Wed Sep 13 14:32:31 EDT
> > >
> > > 2006
> > >
> > > > > scanModem update of: 2007_March_05
> > > > > The modem symbolic link is /dev/modem ->
> > >
> > > ttySHSF0
> > >
> > > > > USB modem not detected by lsusb
> > > > >
> > > > > Modem or host audio card candidates have
> > >
> > > firmware
> > >
> > > > > information:
> > > > >
> > > > > PCI slot PCI ID SubsystemID Name
> > > > > ---------- --------- --------- --------------
> > > > > 00:1f.6 8086:24c6 1025:003d Modem: Intel
> > > > > Corporation 82801DB/DBL/DBM
> > > > >
> > > > > Modem interrupt assignment and sharing:
> > > > > 10: 33802 XT-PIC uhci_hcd:usb1,
> > > > > uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4,
> > > > > ohci1394, yenta, Intel 82801DB-ICH4, eth0, eth2,
> > > > > i915@pci:0000:00:02.0
> > > > >
> > > > > --- Bootup diagnositcs for card in PCI slot
> > >
> > > 00:1f.6
> > >
> > > > > ----
> > > > > ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link
> > >
> > > [LNKB]
> > >
> > > > > -> GSI 10 (level, low) -> IRQ 10
> > > > > ACPI: PCI interrupt for device 0000:00:1f.6
> > >
> > > disabled
> > >
> > > > > ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link
> > >
> > > [LNKB]
> > >
> > > > > -> GSI 10 (level, low) -> IRQ 10
> > > > > PCI: Setting latency timer of device
> > >
> > > 0000:00:1f.6 to
> > >
> > > > > 64
> > > > > ACPI: PCI interrupt for device 0000:00:1f.6
> > >
> > > disabled
> > >
> > > > > hsfich: probe of 0000:00:1f.6 failed with error
> > >
> > > -5
> > >
> > > > > The PCI slot 00:1f.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
> > >
> > > 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 ===
> > > > >
> > > > > ALSAversion 1.0.12
> > > > > The audio card is not a modem hosting type.
> > > > > Bootup diagnostic HSF: ERROR: SILICON
> > >
> > > Laboratories
> > >
> > > > > or LUCENT AC97 modem detected!<3>
> > > > > HSF: ERROR: This driver only supports CONEXANT
> > > > > devices<3>
> > > > > HSF: ERROR: not a Conexant modem<3>
> > > > > For candidate modem in PCI bus: 00:1f.6
> > > > > Class 0703: 8086:24c6 Modem: Intel
> > >
> > > Corporation
> > >
> > > > > 82801DB/DBL/DBM
> > > > > Primary PCI_id 8086:24c6
> > > > > Subsystem PCI_id 1025:003d
> > > > > Softmodem codec or Vendor from diagnostics:
> > > > > from Archives:
> > > > > SIL27, an AgereSystems type.
> > > > >
> > > > >
> > > > > 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: slmodemd
> > > > >
> > > > > An ALSA (Advanced Linux Sound Architecture)
> > >
> > > modem
> > >
> > > > > driver: snd-intel8x0m
> > > > > 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.1.tar.gz having a
> > > > > compiled slmodemd. Unpack under Linux with:
> > > > > $ tar zxf SLMODEMD.gcc4.1.tar.gz
> > > > > and read instructions therein. But briefly, the
> >
> > === message truncated ===
> >
> >
> >
> >
> > _________________________________________________________________________
> >___________ Be a PS3 game guru.
> > Get your game face on with the latest PS3 news and previews at Yahoo!
> > Games. http://videogames.yahoo.com/platform?platform=120121
A modem device/card may be disabled at bootup, due to a variety of causes.
Look at the bootup diagnostics record dmesg.txt written out through:
$ dmesg > dmesg.txt
and try to garner some understanding from it. Possibilities therein are too
diverse to be automagically processed by scanModem. A line including the PCI
bus slot 00:1f.6 of your modem, and "disable" or "disabling" predicts problems,
though sometimes corrected later in the bootup. Similarly a line with "@"
in the interrupt (IRQ) for your 00:1f.6 slot is predictive of problems.
Possible corrections are:
0) Get unloading.gz from http://phep2.technion.ac.il/linmodems/packages/
This script unloads excess drivers which may be competing for resources.
Before trying to set up the modem, do:
$ gunzip unloading.gz
$ chmod +x unloading
$ su - root
# ./unloading
Or for Ubuntu related Distros
$ sudo ./unloading
1) Within the boot up BIOS, change from a Windows to a non-PNP/Other Operating System type.
Instructions for accessing BIOS are at:
http://linmodems.technion.ac.il/resources.html within: Additional Resourcces.
2a) Add an option "pci=routeirq" to the kernel boot up line.
Here is an example paragraph from /boot/grub/menu.lst :
title Ubuntu, kernel 2.6.15-26-686
root (hd0,6)
kernel /boot/vmlinuz-2.6.15-26-686 root=/dev/hda7 ro pci=routeirq
initrd /boot/initrd.img-2.6.15-26-686
savedefault
2b) Same as above, but use "pollirq" instead of "pci=routeirq".
3) Within some BIOS setups, IRQ assignments can be changed.
4) On non-laptop systems, moving the modem card to another slot has helped.
5) Sometimes upgrading the kernel solves the problem.
6) Sometimes downgrading the kernel solves the problem.
7) Sometimes changing the Linux distribution solves the problem.
PCIDEV=8086:24c6
CLASS="Class 0703: 8086:24c6"
NAME="Modem: Intel Corporation 82801DB/DBL/DBM "
Vendor=8086
Device=24c6
SUBSYS=1025:003d
SUBNAME=" Acer Incorporated [ALI] Unknown device 003d"
SUBven=1025
IRQ=10
Test="./scanModem test 8086:24c6 1025:003d"
SOFT=8086:24c6
SLMODEMD_DEVICE=modem:1
PORT="modem:1"
Driver=snd-intel8x0m
DRIVER_=snd_intel8x0m
KDRIVER=SND_NTEL8X0M
MPLACE=
ASOUND=
CODECp=SIL27
CODEC=
COD=
HDA=
IDENT=slmodemd
TST=
CPU0
0: 1450932 XT-PIC timer
1: 2720 XT-PIC i8042
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 38100 XT-PIC acpi
10: 425606 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4, ohci1394, yenta, Intel 82801DB-ICH4, eth0, eth2, i915@pci:0000:00:02.0
12: 123562 XT-PIC i8042
14: 31864 XT-PIC ide0
15: 17020 XT-PIC ide1
NMI: 0
LOC: 0
ERR: 990
MIS: 0
Linux version 2.6.17-5mdv (rtp@xxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #1 SMP Wed Sep 13 14:32:31 EDT 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000001eff0000 (usable)
BIOS-e820: 000000001eff0000 - 000000001effffc0 (ACPI data)
BIOS-e820: 000000001effffc0 - 000000001f000000 (ACPI NVS)
BIOS-e820: 00000000ffb80000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
0MB HIGHMEM available.
495MB LOWMEM available.
On node 0 totalpages: 126960
DMA zone: 4096 pages, LIFO batch:0
Normal zone: 122864 pages, LIFO batch:31
DMI 2.3 present.
ACPI: RSDP (v000 OID_00 ) @ 0x000e6010
ACPI: RSDT (v001 INSYDE RSDT_000 0x00000001 _CSI 0x00010101) @ 0x1effa5b0
ACPI: FADT (v001 COMPAL DCL51_00 0x00000100 _CSI 0x00010101) @ 0x1efffb00
ACPI: BOOT (v001 INSYDE BOOT_000 0x00000001 _CSI 0x00010101) @ 0x1efffb90
ACPI: DBGP (v001 INSYDE DBGP_000 0x00000001 _CSI 0x00010101) @ 0x1efffbc0
ACPI: SSDT (v001 INSYDE GV3Ref 0x00002000 INTL 0x20021002) @ 0x1effa5f0
ACPI: DSDT (v001 ACER TM290 0x00000006 MSFT 0x0100000e) @ 0x00000000
ACPI: PM-Timer IO Port: 0x1008
Allocating PCI resources starting at 20000000 (gap: 1f000000:e0b80000)
Built 1 zonelists
Kernel command line: auto BOOT_IMAGE=linux root=301
Local APIC disabled by BIOS -- you can enable it with "lapic"
mapped APIC to ffffe000 (013ea000)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 8192 bytes)
Detected 1299.063 MHz processor.
Using pmtmr for high-res timesource
Console: colour VGA+ 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 498088k/507840k available (2426k kernel code, 8652k reserved, 756k data, 244k init, 0k highmem, 0k BadRAM)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 2600.24 BogoMIPS (lpj=5200496)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: a7e9f9bf 00000000 00000000 00000000 00000180 00000000 00000000
CPU: After vendor identify, caps: a7e9f9bf 00000000 00000000 00000000 00000180 00000000 00000000
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
CPU: After all inits, caps: a7e9f9bf 00000000 00000000 00000040 00000180 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 16k freed
checking if image is initramfs... it is
Freeing initrd memory: 355k freed
ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found.
ACPI: setting ELCR to 0200 (from 0c20)
CPU0: Intel(R) Pentium(R) M processor 1300MHz stepping 05
SMP motherboard not detected.
Local APIC not detected. Using dummy APIC emulation.
Brought up 1 CPUs
migration_cost=0
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xe9824, last bus=1
Setting up standard PCI resources
ACPI: Subsystem revision 20060127
ACPI: Interpreter enabled
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
Boot video device is 0000:00:02.0
PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
PCI quirk: region 1300-133f claimed by ICH4 GPIO
PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #02 (-#05) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB_._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKB] (IRQs 10) *5
ACPI: PCI Interrupt Link [LNKC] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 10) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKF] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKG] (IRQs 10) *11
ACPI: PCI Interrupt Link [LNKH] (IRQs *10)
ACPI: Embedded Controller [EC0] (gpe 28) interrupt mode.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
pnp: PnP ACPI: found 10 devices
PnPBIOS: Disabled
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
PCI: Ignore bogus resource 6 [0:0] of 0000:00:02.0
PCI: Bus 2, cardbus bridge: 0000:01:04.0
IO window: 0000c400-0000c4ff
IO window: 0000c800-0000c8ff
PREFETCH window: a0000000-a1ffffff
MEM window: e2000000-e3ffffff
PCI: Bridge: 0000:00:1e.0
IO window: c000-dfff
MEM window: e0000000-efffffff
PREFETCH window: a0000000-afffffff
PCI: Setting latency timer of device 0000:00:1e.0 to 64
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 8192)
TCP reno registered
Simple Boot Flag at 0x37 set to 0x1
apm: BIOS not found.
audit: initializing netlink socket (disabled)
audit(1174135912.736:1): initialized
Total HugeTLB memory allocated, 0
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12ac
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
serial8250: ttyS3 at I/O 0x2e8 (irq = 3) is a 16550A
ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt for device 0000:00:1f.6 disabled
RAMDISK driver initialized: 16 RAM disks of 32000K size 1024 blocksize
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ICH4: IDE controller at PCI slot 0000:00:1f.1
PCI: Enabling device 0000:00:1f.1 (0005 -> 0007)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
ICH4: chipset revision 3
ICH4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1100-0x1107, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x1108-0x110f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: TOSHIBA MK4021GAS, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 78140160 sectors (40007 MB), CHS=65535/16/63, UDMA(33)
hda: cache flushes supported
hda: hda1 hda2 < hda5 hda6 >
PNP: PS/2 Controller [PNP0303:KBC0,PNP0f13:MSE0] at 0x60,0x64 irq 1,12
i8042.c: Detected active multiplexing controller, rev 1.1.
serio: i8042 AUX0 port at 0x60,0x64 irq 12
serio: i8042 AUX1 port at 0x60,0x64 irq 12
serio: i8042 AUX2 port at 0x60,0x64 irq 12
serio: i8042 AUX3 port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
mice: PS/2 mouse device common for all mice
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39
TCP bic registered
NET: Registered protocol family 1
Using IPI No-Shortcut mode
ACPI wakeup devices:
ELAN USB1 USB2 USB3 EUSB MODM
ACPI: (supports S0 S1 S3 S4 S5)
BIOS EDD facility v0.16 2004-Jun-25, 1 devices found
Freeing unused kernel memory: 244k freed
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
input: AT Translated Set 2 keyboard as /class/input/input0
input: PS/2 Mouse as /class/input/input1
input: AlpsPS/2 ALPS GlidePoint as /class/input/input2
kjournald starting. Commit interval 5 seconds
EXT3-fs: hda1: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 251470
ext3_orphan_cleanup: deleting unreferenced inode 251325
ext3_orphan_cleanup: deleting unreferenced inode 251531
ext3_orphan_cleanup: deleting unreferenced inode 251327
ext3_orphan_cleanup: deleting unreferenced inode 753742
EXT3-fs: hda1: 5 orphan inodes deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
ts: Compaq touchscreen protocol output
usbcore: registered new driver usbfs
usbcore: registered new driver hub
USB Universal Host Controller Interface driver v3.0
ACPI: PCI Interrupt 0000:00:1d.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.0 to 64
uhci_hcd 0000:00:1d.0: UHCI Host Controller
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:1d.0: irq 10, io base 0x00001200
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1d.1[B] -> Link [LNKD] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.1 to 64
uhci_hcd 0000:00:1d.1: UHCI Host Controller
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: irq 10, io base 0x00001600
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ACPI: PCI Interrupt 0000:00:1d.2[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.2 to 64
uhci_hcd 0000:00:1d.2: UHCI Host Controller
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: irq 10, io base 0x00001700
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 10
ACPI: PCI Interrupt 0000:00:1d.7[D] -> Link [LNKH] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1d.7 to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 4
ehci_hcd 0000:00:1d.7: debug port 1
PCI: cache line size of 32 is not supported by device 0000:00:1d.7
ehci_hcd 0000:00:1d.7: irq 10, io mem 0xf0080000
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb4: configuration #1 chosen from 1 choice
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 6 ports detected
ieee1394: Initialized config rom entry `ip1394'
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 10
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKE] -> GSI 10 (level, low) -> IRQ 10
ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[10] MMIO=[e0001800-e0001fff] Max Packet=[2048] IR/IT contexts=[4/8]
Non-volatile memory driver v1.2
hw_random: RNG not detected
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 855 Chipset.
agpgart: Detected 16252K stolen memory.
agpgart: AGP aperture is 128M @ 0xb0000000
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: PCI Interrupt 0000:01:04.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
Yenta: CardBus bridge found at 0000:01:04.0 [1025:003d]
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:01:04.0, mfunc 0x00111c12, devctl 0x46
ieee1394: Host added: ID:BUS[0-00:1023] GUID[00023f38440038b5]
Yenta: ISA IRQ mask 0x0860, PCI irq 10
Socket status: 30000006
pcmcia: parent PCI bridge I/O window: 0xc000 - 0xdfff
cs: IO port probe 0xc000-0xdfff: clean.
pcmcia: parent PCI bridge Memory window: 0xe0000000 - 0xefffffff
pcmcia: parent PCI bridge Memory window: 0xa0000000 - 0xafffffff
cs: IO port probe 0x100-0x3af: excluding 0x230-0x237 0x378-0x37f
cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7
cs: IO port probe 0x820-0x8ff: clean.
cs: IO port probe 0xc00-0xcf7: clean.
cs: IO port probe 0xa00-0xaff: clean.
device-mapper: 4.6.0-ioctl (2006-02-17) initialised: dm-devel@xxxxxxxxxx
EXT3 FS on hda1, internal journal
Adding 4088500k swap on /dev/hda5. Priority:-1 extents:1 across:4088500k
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda6, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
loop: loaded (max 8 devices, max 1 partitions per device)
hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.20
ACPI: AC Adapter [ACAD] (on-line)
ACPI: Battery Slot [BAT1] (battery present)
ACPI: Power Button (FF) [PWRF]
ACPI: Lid Switch [LID]
ACPI: Power Button (CM) [PWRB]
ACPI: Sleep Button (CM) [SLPB]
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (3967 buckets, 31736 max) - 224 bytes per conntrack
Using specific hotkey driver
ACPI: Video Device [GFX0_PCI0] (multi-head: yes rom: yes post: no)
Removing netfilter NETLINK layer.
ACPI Error (psargs-0353): [PBST] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0517): Method parse/execution failed [\_SB_.PCI0.LPC0.BAT1._BST] (Node def027e0), AE_NOT_FOUND
ACPI: PCI Interrupt 0000:00:1f.5[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
PCI: Setting latency timer of device 0000:00:1f.5 to 64
NET: Registered protocol family 17
intel8x0_measure_ac97_clock: measured 55403 usecs
intel8x0: clocking to 48000
8139too Fast Ethernet driver 0.9.27
ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 10
ACPI: PCI Interrupt 0000:01:01.0[A] -> Link [LNKF] -> GSI 10 (level, low) -> IRQ 10
eth0: RealTek RTL8139 at 0xdfc54000, 00:02:3f:bb:5d:c6, IRQ 10
eth0: Identified 8139 chip type 'RTL-8101'
eth0: link down
ieee80211_crypt: registered algorithm 'NULL'
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@xxxxxxxxxxxxxxx>
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2
ipw2100: Copyright(c) 2003-2006 Intel Corporation
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
ACPI: PCI Interrupt 0000:01:02.0[A] -> Link [LNKG] -> GSI 10 (level, low) -> IRQ 10
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection
spurious 8259A interrupt: IRQ7.
eth2: Reseting on mode change.
ip_tables: (C) 2000-2006 Netfilter Core Team
Installing knfsd (copyright (C) 1996 okir@xxxxxxxxxxxx).
NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
NFSD: starting 90-second grace period
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
ADDRCONF(NETDEV_UP): eth0: link is not ready
IPv6 over IPv4 tunneling driver
Netfilter messages via NETLINK v0.30.
ip_conntrack version 2.4 (3967 buckets, 31736 max) - 224 bytes per conntrack
ClusterIP Version 0.8 loaded successfully
ipt_recent v0.3.1: Stephen Frost <sfrost@xxxxxxxxxxx>. http://snowman.net/projects/ipt_recent/
eth2: no IPv6 routers present
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LNKA] -> GSI 10 (level, low) -> IRQ 10
[drm] Initialized i915 1.4.0 20060119 on minor 0
PCI: Enabling device 0000:00:02.1 (0000 -> 0002)
[drm] Initialized i915 1.4.0 20060119 on minor 1
eth1394: eth1: IEEE-1394 IPv4 over 1394 Ethernet (fw-host0)
netfilter PSD loaded - (c) astaro AG
IFWLOG: register target
floppy0: no floppy controllers found
Bluetooth: Core ver 2.8
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
floppy0: no floppy controllers found
SCSI subsystem initialized
ACPI Error (psargs-0353): [PBST] Namespace lookup failure, AE_NOT_FOUND
ACPI Error (psparse-0517): Method parse/execution failed [\_SB_.PCI0.LPC0.BAT1._BST] (Node def027e0), AE_NOT_FOUND
Only plain text email is forwarded by the DISCUSS@xxxxxxxxxxxxx List Server.
Do use the following as the email Subject Line:
SomeName, YourCountry Mandriva Linux release 2007.0 (Official) for i586
Kernel 2.6.17-5mdv on an i686 / kernel 2.6.17-5mdv
This will alert cogent experts, and distinguish cases in the Archives.
YourCountry will enable Country Code guidance.
Occassionally responses are blocked by an Internet Provider mail filters.
So in a day, also check the Archived responses at http://www.linmodems.org .
Local Linux experts can be found through: http://www.linux.org/groups/index.html
-------------------------- System information ----------------------------
CPU=i686, Mandriva Linux release 2007.0 (Official) for i586
Kernel 2.6.17-5mdv on an i686 /
Linux version 2.6.17-5mdv (rtp@xxxxxxxxxxxxxxxxxxxx) (gcc version 4.1.1 20060724 (prerelease) (4.1.1-3mdk)) #1 SMP Wed Sep 13 14:32:31 EDT 2006
scanModem update of: 2007_March_05
USB modem not detected by lsusb
Modem or host audio card candidates have firmware information:
PCI slot PCI ID SubsystemID Name
---------- --------- --------- --------------
00:1f.6 8086:24c6 1025:003d Modem: Intel Corporation 82801DB/DBL/DBM
Modem interrupt assignment and sharing:
10: 425603 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2, uhci_hcd:usb3, ehci_hcd:usb4, ohci1394, yenta, Intel 82801DB-ICH4, eth0, eth2, i915@pci:0000:00:02.0
--- Bootup diagnositcs for card in PCI slot 00:1f.6 ----
ACPI: PCI Interrupt 0000:00:1f.6[B] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10
ACPI: PCI interrupt for device 0000:00:1f.6 disabled
The PCI slot 00:1f.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 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 ===
ALSAversion 1.0.12
The audio card is not a modem hosting type.
For candidate modem in PCI bus: 00:1f.6
Class 0703: 8086:24c6 Modem: Intel Corporation 82801DB/DBL/DBM
Primary PCI_id 8086:24c6
Subsystem PCI_id 1025:003d
Softmodem codec or Vendor from diagnostics:
from Archives: SIL27, an AgereSystems type.
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: slmodemd
An ALSA (Advanced Linux Sound Architecture) modem driver: snd-intel8x0m
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.1.tar.gz having a compiled slmodemd. Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.1.tar.gz
and read instructions therein. But briefly, the modem is setup with command:
slmodemd -c YOUR_COUNTRY --alsa modem:1
reporting dynamic creation of ports:
/dev/ttySL0 --> /dev/pts/N , with N some number
Read Smartlink.txt and Modem/YourSystem.txt for follow through guidance.
The diagnostic outputs for this softmodem section have their raw information in
folders and text files under /proc/asound/ which you can browse. The information
is from files:
/proc/asound/pcm
-------------------------------
00-04: Intel ICH - IEC958 : Intel 82801DB-ICH4 - IEC958 : playback 1
00-03: Intel ICH - ADC2 : Intel 82801DB-ICH4 - ADC2 : capture 1
00-02: Intel ICH - MIC2 ADC : Intel 82801DB-ICH4 - MIC2 ADC : capture 1
00-01: Intel ICH - MIC ADC : Intel 82801DB-ICH4 - MIC ADC : capture 1
00-00: Intel ICH : Intel 82801DB-ICH4 : playback 1 : capture 1
/proc/asound/modules
-------------------------------
0 snd_intel8x0
and from the command:
aplay -l | grep -i modem
----------------end Softmodem section --------------
Writing Intel.txt
Writing Smartlink.txt
============ end Smartlink section =====================
Completed candidate modem analyses.
The base of the UDEV device file system is: /dev/.udev
/dev/.udevdb
Versions adequately match for the compiler installed: 4.1.1
and the compiler used in kernel assembly: 4.1.1
Kernel-header resources needed for compiling are not manifestly ready!
If compiling is necessary packages must be installed, providing:
kernel-source-2.6.17-5mdv
Checking settings of: /etc/ppp/options
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 eth2
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.conf:install snd-via82xx-modem /bin/true
/etc/modprobe.conf:install snd-atiixp-modem /bin/true
Within any ancient /etc/devfs files:
Within ancient kernel 2.4.n /etc/module.conf files:
--------- end modem support lines --------
Modem Type Readout and Supporting Software Identification.
-------------------------------------------------------
Most add on cards to motherboards (including modems) adhere to a PCI standard, for
which there is firmware on the card which can be readout, providing setup parameters
and specification of the required software. This works under Linux provided that
drivers are resident. Herein is the practical problem. During the evolution of
modems, some of the complementing software components became Proprietary and
Closed Source. A consequence is that for reasons of Legality and/or Principle,
many Linux distributions do not distribute such modem drivers with the regular
releases, even when the modem chipset designer does provide Linux support code.
Without the drivers, additional assistance is needed to identify the modem
chipset and its complementing software.
The scanModem script includes four routines to determine the software required:
1) Read outs with a lspci tool accessing firmware on PCI cards.
2) A test using modem drivers already on your system as part of the ALSA (Advanced Linux
Sound Architecture) software package. See Smartlink.txt for details.
3) Comparison of Primary+Subsystem PCI IDs with others historically gathered, and
then archived within scanModem.
4) A test requiring the SmartLink slamr.ko driver. See Smartlink.txt for details.
Should these not be adequate, there are directions below for doing diagnostics during
an alernate Microsoft Windows bootup.
Stop here on a first reading, and just run
./scanModem
Read on later if you are interested in details, OR
need instructions for doing modem diagnostics under Microsoft.
Using MicroSoft(MS) Windows:
-----------------------------
MS installations do generally have adequate diagostic capability. Try the following
routine 1), beginning with mouse clicks on:
1) 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.
2) Open a COMM console. Send ATI commands to the modem (ATI, ATI1, ATI2, etc)
which may elicit chipset and driver information. Here is an example:
ATI3 - Agere SoftModem Version 2.1.22
ATI5 - 2.1.22, AMR Intel MB, AC97 ID:SIL REV:0x27
successfully identifying an Agere SoftModem chipset, both by name and through
the softmodem SIL ID: AC97 ID:SIL REV:0x27
The IBM mwave modem:
This has a DSP chip usually seated on the motherboard. Not carried on a PCI card
it cannot be detected by scanModem. However, the mwave driver is included in
2.6.n kernel releases.
So try:
# modprobe mwave
Either the module will load or the absence of the modem will be indicated by:
FATAL: Error inserting mwave (/lib/modules/2.6.10-1-
686/kernel/drivers/char/mwave/mwave.ko): Input/output error
See http://www.linuxdocs.org/HOWTOs/mini/ACP-Modem/ for details on this modem.
Modem evolution:
----------------
Here is a very abbreviated history on how modem evolutionary development. The
earliest modems (MOdulate and DEModulate signals for phone lines transmission)
managed all signal proceesing on the modem card through actions of expensive
Controllers chipsets with DSP (digital signal processing) capability. Copyrighted
Vn.nm compression routines were also encoded in the chipset. Under Linux, an Open
Source serial driver was the minimal complementing software. This generation of
Controller chipset modems placed minimal burden on the early slow central
processing unips (CPU) of personal computers, such as the Intel 386.
As CPUs became faster, it was feasible to transfer some modem functions to
the CPU. A 2nd generation of modems retained a DSP chip, but Controller functions
were software driven on the CPU. A benefit was that modem hardware became cheaper.
But sadly the supporting software was Proprietary. Worst, some Intellectual Property
components were Closed Source to protect large investment in code development. Such
Controller free modems include the Conexant HCF, Intel-537EP and Mars chipset
modems from Lucent or its later subsidary, Agere Systems Inc.
As CPUs became even faster, even DSP functions could be software code driven on
the CPU. This third generation of modems are commonly called "softmodems". Their
complementing software is comparable in sizeto that of the Linux kernel itself. The
residual "modem chip" is very cheap, but the development of the complementing
software is a large investment on the part of the chip designer/maker.
Modem chipset determination under Linux:
---------------------------------------
The chipset of a modem determines which complementing software is required.
The Manufacturer and Model of an assembled modem are often inadequate to identify
the chipset. But sometimes there is an easy chipset identification. There is
a "lspci" utility provided in the Linux pciutils package. It reports the PCI
identifiers (IDs hereafter) or the Primary card, its Subsystem, and some setup
parameters written in firmware. For example, there is a softmodem in the
PCI bus of address 00:11.6 on my laptop. Shown below is firmware information
acquired by two lspci commands:
$ lspci -s 00:11.6
00:11.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller
$ lspci -s 00:11.6 -nv
00:11.6 0780: 1106:3068 (rev 80)
Subsystem: 14ff:100b
Flags: medium devsel, IRQ 193
I/O ports at e000 [size=256]
The translation is: The card inserted into PCI bus slot 00:11.6 is named
"Communication controller: VIA Technologies, Inc. AC'97 Modem Controller". The
modem was assembled by a Vendor with ID identification code 1106 . Among 1106's
products, it has a Device ID of 3068 in its 80th revison. This usually provides
adequate information, to get software from the Vendor designated by 1106 (VIA
Technologies, Inc. in this case) for their device designation 3068. The parameters
Flags: medium devsel, IRQ 193
I/O ports at e000 [size=256]
are determining by the environment of the host computer as reading modem firmware.
It may change if other hardware is added/removed from the host computer, or
under a change or Operating System (OS) kernel.
The problem for softmodems is that additional information is needed for the software
specification. The Subsystem Vendor_ID identifies only the assembler company. But
the modem chip housed in the Subsystem could be of a variety of types, each requiring
different support software. In general, a single Subsystem assembler could use a
variety of different softmodem chips. The Subsystem firwmare information on the chipset
is not accessible to lspci. Rather it requires usage of a modem driver, if one first had
some competent modem driver for minimal diagnositcs.
Fortunately there are the software tools and drivers of the ALSA (Advanced Linux
Sound Architecture) suite. This includes modem drivers lacking COMM proficiency by
themselves, but enough capability to readout the Subsystem firmware. For the VIA
modem above, the encoded modem codec is SIL22, reporting that the softmodem chip was
made by SmartLink Inc.
It is important to emphasis, that AC'97 Modem Controllers are made by a variety
of companies, and each may house many different Subsystem modem chips. There is
an Archive within scanModem of those with previously identified codecs. For example,
the table for the 1106:3068 AC'97 Controller is:
codec SubSystems_with_codec ------------>
CXT 104d:8143 104d:80f6 1025:0030
SIL27 1102:0033 1025:0046 1025:0033 1734:1078 1509:2870 1025:0046
SIL22 1743:1032 10cf:118e 1734:1054 1462:309e 1631:e004 1543:4c22 161f:2032 and_more
SIL21 10cf:118e 13bd:1022 1543:4c21 1071:8375 1019:0c04 1458:1543 1019:b320
MOT66 1734:109b
Because of hardware configuration issues, the ALSA tools may initially fail. Then this
Archive is a fall back reporting the codec, and therefrom the needed software. For reasons
obscure, a single Subsystem ID may have different codecs under different Primary
controllers. Thus the pair Primary+Subsystem IDs must BOTH be retained to record
the codec.
In addition to the Modem Controllers adhering to the AC'97 specifications, softmodem
Subsystems may be hosted by High Definition Audio (HDA) cards such as the:
8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller
These lack a softmodem codec. Instead the softmodem chip information acquired with ALSA
tools is within a folder: /proc/asound/card0/codec#1/
and includes the Vendor ID of the softmodem chip, such as 14f1 corresponding to Conexant.
The software support:
---------------------
The CXT designation above is an abbreviation of CXT_some_number, for Conexant HSF softmodem
codecs. These now number some 41 (perhaps more) CXT. Fortunately, all these codecs are
supported by a single hsfmodem software package provided through http://www.Linuxant.com
The trial package is free, but locked to speeds of 14,400 K. A software key must be
purchased to enable full speed support, with future software updates free. There is NO
freeware alternative for the hsfmodem software. But Linuxant does provide pre-compiled
drivers for the more common Linux kernels, and their support services are good.
In the Table below, there are currently some 13 other softmodem codecs. Fortunately
all are supported by a combination of the ALSA modem drivers, the ALSA audio drivers
the modem drivers depend on, and a very smart helper utility from Smartlink Inc.,
the slmodemd helper. Sasha Kharposky wrote the Linux slmodemd utility and remains its
volunteer maintainer. It provides the cleverness to interface between the low level
ALSA modem driver and the pppd package communications codes. For details do:
$ slmodemd --help
and read associated documentation. The slmodemd is provided with some Linux distributions,
and can also be downloaded in SLMODEMD packages from:
http://linmodems.technion.ac.il/packages/smartlink/
Subsystems of AC'97 Modem Controllers
---------------------------------------
Subsystems for softmodems are primarily made by Silicon Labs (SIL) under
contract to companies like Intel, Agere Systems, Motorola etc. In the Table
below, ChipMadeBy does NOT imply software support directly from that
manufacturer. The chart of information below is largely harvested from messages
to discuss@xxxxxxxxxxxxxx
A codec_indent such as REV:0x27 is reported by diagnostics under Microsoft, as
illustrated above. The matching designations such as SIL27 are translations
under Linux, which are output by a diagnostic of the slamr.ko driver from the
SmartLink slmodem software.
SIL is an abbreviation for Silicon Laboratories Inc., which provides Subsystems
on order to many modem assemblers.
SML is used below as abbreviation for SmartLink Inc. with official driver
resources at http://www.smlink.com/main/index1.php?ln=en&main_id=40 . BUT use
updated resources at http://linmodems.technion.ac.il/packages/smartlink/.
ALSA+SML means use an ALSA modem driver plus the Smartlink slmodemd helper,
with the particular driver depending on the AC'97 or HDA host controller.
ID was originally a hexadecimal readout from 7c and 7e registers of the SubSystem,
but are translated into "english", as done automatically by the slamr driver.
ID chip_maker driver/helper sources
---------------- ----------------------
CXTnm Conexant hsfmodem package from http://www.linuxant.com with several hsf* drivers.
nm - a number
SIL25 Intel ALSA+SML or INTEL-537EP supported AA variant
INT65 Intel ALSA+SML or INTEL-537EP supported EA variant
SIL26 SML SML, slamr driver plus slmodemd
SIL27 AgereSystems ALSA+SML
SIL2F " ALSA+SML
MOT66 " ALSA+SML
AGR01 " ALSA+SML
AGR02 " ALSA+SML
SIL21 PCTel ALSA+SML
SIL23 PCTel ALSA+SML
SIL22 SML ALSA+SML
SIL24 Broadcom ALSA+SML
BCM64 Broadcom ALSA+SML, under Intel ICH family, AC'97 controllers.
----------------------------------------------
Subsystems with the above characteristics could reside under any of
the primary softmodem controllers listed below. Ignore the stuff after the > .
It serves during parsing of the Table by scan modem
Primary
PCI_IDs Name Possible support by:
--------------- ----------------------------- -------------------------
8086:2416 82801AA ICHAA AC97 Modem Controller> + A a p c .
8086:2426 82801AB ICHAB AC97 Modem Controller> + A a .
8086:7186 > c .
8086:7196 82440MX Banister AC97 Modem Controller > + A a c .
8086:2446 82801BA/BAM ICH2 AC97 Modem Controller > + A a p c .
8086:2486 82801CA/CAM ICH3 AC97 Modem Controller > + A a p c i .
8086:24c6 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)1DB ICH4 AC97 Modem Controller> + A a c i b .
8086:25a7 6300ESB AC97 Modem Controller NEW >
8086:24d6 82801EB/ER ICH5/ICH5SR AC97 Modem Controller> + A c i .
8086:8280 1EB ICH6 AC97 Modem Controller> + A c .
8086:2668 Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller> H c .
8086:266d Intel Corp. 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC97 Modem Controller >
8086:2669 631xESB/632xESB AC97 Modem Controller NEW >
8086:27d8 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller HDA > .
8086:27dd (ICH7 Family) AC97 Modem Controller NEW >
8086:xxxx types above are from Intel>
1039:7013 SIS 630 > + a p c i .
1039:7018 SIS 960 > + i .
10de:01c1 Nvidia Corp > + i .
10de:00d9 Nvidia Corp > A c .
1106:3068 VIA > + a p c i .
1022:7446 AMD AC_LINK > + .
10b9:5450 ALI 5450 >
10b9:5451 ALI 5451 > + a c .
10b9:5453 ALI 5453 AC-Link > p c .
1025:5453 ALI 5453 AC-Link > c .
10b9:5457 ALI 5457 AC-Link > + p c i .
1025:5457 ALI 5457 AC-Link > c . .
1002:434d ATI > T a c i .
1002:437b ATI Audio device: ATI Technologies Inc SB450 HDA Audio a .
1002:4378 ATI > c .
1543:3052 SI3052 >
Class 0403, High Definition Audio Controllers (HDA)
-----------------------------------------------------
8086:2668 Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) HDA Controller
8086:27d8 Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller
1002:437b Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)
10de:026c nVidia Corporation MCP51 High Definition Audio
----------------------------------------------------
are the members of this family encountered as of September 2006.
From the file /proc/asound/card0/codec#1/, there are the following Subsystem chips:
Vendor IDs Chip maker Support type
---------- ---------- -------------
0x14f12bfa Conexant hsfmodem , not slmodemd compatible
0x11c13026 AgereSystems snd-hda-intel, slmodemd
0x163c3055 Smartlink " "
0x163c3155 " " "
0x10573055 Motorola " "
0x10573155 " " "
This file should NOT be sent to Discuss@xxxxxxxxxxxxx
It has common guidance for modem usage after setup.
Complementation of snd-intel8x0m, slmodemd and a dialer utility
---------------------------------------------------------
THe ALSA (Advanced Linux Sound Architecture} modem driver snd-intel8x0m
provides ONLY a low level access to the hardware. The complementing HIGH
level support for ALSA modem drivers is through a Smartlink utility: slmodemd
An ALSA compatible and compiled slmodemd is in the package SLMODEMD.gcc4.1.tar.gz
with download from http://linmodems.technion.ac.il/packages/smartlink/
Unpack under Linux with:
$ tar zxf SLMODEMD.gcc4.1.tar.gz
and read instructions therein.
Typically the driver snd-intel8x0m will be autoloaded on most Systems.
Then a Root permission command:
slmodemd -c YOUR_COUNTRY --alsa modem:1
will announce creation of ports
/dev/ttySL0 --> /dev/pts/N , N some number
The /dev/ttySL0 is a symbolic link to the true modem port /dev/pts/N
USA is the YOUR_COUNTRY default. See other Country alternatives by:
slmodemd --help
slmodemd --countrylist
Should there be a failure report like:
--------
ALSA lib pcm_hw.c:1305:(_snd_pcm_hw_open) Invalid value for card
error: alsa setup: cannot open playback device modem:1 No such device
error: cannot setup device modem:1
--------
First verify that packages providing ALSA audio support are installed.
Names vary with the Linux distribution but they are like "alsa-base"
and "alsa-utilities". In these are installed,
Next try as Root unloading and loading the driver:
modprobe -r snd-intel8x0m
modprobe snd-intel8x0m
Then retest the:
slmodemd -c YOUR_COUNTRY --alsa modem:1
slmodemd MUST be kept running throughout a dial out session.
Note that mere loading does NOT establish that snd-intel8x0m is the correct
driver, rather than hsfmodem drivers for Conexant chipset modems. But
snd-intel8x0m may still support readout of Subsystem information.
--------------------------------------------------------------------------
A dialer utility such as wvdial (perferable) is still needed for dialout.
slmodemd MUST be kept running throughout a dialout session.
On some Systems, putting the slmodemd process in the background with an &:
slmodemd -c USA --alsa modem:1 &
causes subsequent dialout failures.
Read Testing.txt for follow through details and Smartlink.txt
for additional information.
Interfererce with browser naviagation:
-------------------------------------
Other COMM channels can interfere with browsing under dialout.
Suspect channels set during your scanModem run were shown by: ifconfig
eth0 Link encap:Ethernet HWaddr 00:02:3F:BB:5D:C6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0x4000
eth2 Link encap:Ethernet HWaddr 00:04:23:6B:E7:46
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::204:23ff:fe6b:e746/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11159 errors:0 dropped:0 overruns:0 frame:0
TX packets:7781 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8943103 (8.5 MiB) TX bytes:927573 (905.8 KiB)
Interrupt:10 Base address:0xa000 Memory:e0000000-e0000fff
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:67 errors:0 dropped:0 overruns:0 frame:0
TX packets:67 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5294 (5.1 KiB) TX bytes:5294 (5.1 KiB)
A block with "lo" is an internal loopback test and harmless.
However, other COMM channels such as ethernet "eth0" will block browser function
through dialout connections. Domain Name Services (DNS) needed for browsing
will be blocked by an ineffective default usage of the eth0 assigned DNS.
If is wisest to disable bootup establishment of alternate channels in your Control Center.
Depending on your Linux distribution,
one of the following root/admin commands may alternatively be effective:
# ifdown eth0
# ifconfig eth0 down
# /etc/init.d/network stop
# /etc/init.d/networking stop
Be wary that some Systems will periodically try to re-establish internet.
So if browsing should suspiciously fail, recheck with
ifconfig
---------------------------- end COMM Channels --------------------------
If the Mandrake installation disks do not include the dialer utility wvdial.rpm,
then get instructions from http://linmodems.technion.ac.il/archive-fifth/msg01480.html
The Modem/DriverCompiling.txt is a MUST READ,
if you are not experienced in configuring kernel-source/
or get "unresolved symbols" upon driver insertion.
Most recent WinModem fixes are in: http://linmodems.technion.ac.il/FAQ.html
(4) For guidance on automation see http://linmodems.technion.ac.il/archive-fourth/msg03734.html
and the scripts in the slmodem-2.9.n/scripts folder/
