David
The diagnostics reported under the ModemData3.txt conditions are
INDEED the 1st step to success, the modem card finally being enabled
and thus supporting ALSA diagnostics.
Carefully record what allowed you to achieve it.
The modem activation command must be:
$ sudo slmodemd -c USA --alsa modem:1
More later
MarvS
====================
Summary card and chipset information is in:
/proc/asound/cards:
0 [I82801AAICH ]: ICH - Intel 82801AA-ICH
Intel 82801AA-ICH with AD1881A at 0xd800, irq 5
1 [Modem ]: ICH-MODEM - Intel 82801AA-ICH Modem
Intel 82801AA-ICH Modem at 0xe000, irq 5
/proc/asound/pcm:
00-01: Intel ICH - MIC ADC : Intel 82801AA-ICH - MIC ADC : capture 1
00-00: Intel ICH : Intel 82801AA-ICH : playback 1 : capture 1
01-00: Intel ICH - Modem : Intel 82801AA-ICH Modem - Modem : playback
1 : capture 1
Modem interrupt assignment and sharing:
5: 31599 XT-PIC Intel 82801AA-ICH, Intel
-----------
[17188670.400000] PCI: Setting latency timer of device 0000:00:1f.6 to 64
For candidate modem in PCI bus: 00:1f.6
Class 0703: 8086:2416 Modem: Intel Corporation 82801AA AC'97 Modem
Primary PCI_id 8086:2416
Subsystem PCI_id 5349:4c21
Softmodem codec or chipset from diagnostics: SIL21, a Pctel type.
from Archives:
On Jan 22, 2008 12:02 PM, David Chandler <chandler@xxxxxxxxxxxxx> wrote:
> Hi Marv
>
> Attached are the two files I seem to have forgotten to attach before. I
> don't know why windows didn't list them on the flash drive before.
>
> I think ModemData2 was after doing the dmesg thing and then ModemData3
> after also doing the unloading. The last one looks encouraging, but then
> when I tried to follow the directions to install the driver, I got an
> error message. I will forward a copy of the email containing the error
> message in a minute, so that you don't have to look for it.
>
> It's two days later than you said. My phone line was connected to another
> computer my friend brought to the house. I was running a lot of scans on
> it, but not using it to do email.
>
> David
>
>
> On Sun, 13 Jan 2008, Marvin Stodolsky wrote:
>
> > David,
> >
> > Wait till Jan 20
> > Can't do anything while traveling.
> >
> > marv
> >
> > On 1/12/08, David Chandler <chandler@xxxxxxxxxxxxx> wrote:
> > > Hi Marv
> > >
> > > Looking at my sent-mail folder, I think I failed to attach the new files
> > > ModemData2.txt and ModemData3.txt . Furthermore, I am perplexed now
> > > because these files are shown under /media/usbdisk when I run kubuntu, but
> > > they do not appear on the flashdrive when I start windows. I did transfer
> > > the first ModemData to windows using the flashdrive, and that file appears
> > > under both systems.
> > >
> > > David
> > >
> > > On Fri, 11 Jan 2008, Marvin Stodolsky wrote:
> > >
> > > > David,
> > > >
> > > > The major problem is
> > > > ----------
> > > > [17179573.700000] 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.
> > > > --------------------
> > > > Until that disabled disappears, the modem will be unresponsive.
> > > > It is not communicating with the kernel.
> > > >
> > > > Try seqeuntially the following.
> > > >
> > > > 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".
> > > > 2c) Same as above, but use, noapci
> > > > 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.
> > > >
> > > > After each change and new bootup, run scanModem again to lool at the line like:
> > > > [17179573.700000] ACPI: PCI interrupt for device 0000:00:1f.6 disabled
> > > > The modem cannot function until "disabled" is gone.
> > > >
> > > > Read
> > > > man chmod
> > > > on chmod issues, but a+x basically all can execute.
> > > > It is OK to use the correponding numerical values.
> > > >
> > > > MarvS
> > > >
> > > >
> > > >
> > > > On Jan 11, 2008 12:15 PM, David Chandler <chandler@xxxxxxxxxxxxx> wrote:
> > > > > Hi Marv
> > > > >
> > > > > Maybe you're pretty busy during the week. I wondered whether you had some
> > > > > interpretation of the error message I sent you last.
> > > > >
> > > > > David
> > > > >
> > > > >
> > > > > On Mon, 7 Jan 2008, David Chandler wrote:
> > > > >
> > > > > > Hi Marv
> > > > > >
> > > > > > I got the following error:
> > > > > >
> > > > > > david@david-desktop:~/SLMODEMD.gcc4.1$ sudo ./slmodemd -c b5 --alsa
> > > > > > modem:1
> > > > > > error: mixer setup: attach hw:1 error: No such device
> > > > > > ALSA lib pcm.c:2017:(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'
> > > > > > david@david-desktop:
> > > > > >
> > > > > > following the direction in modemData3. The directions in the README file
> > > > > > that came with slmodem were for unzipping a file with a slightly different
> > > > > > name, not gcc.
> > > > > >
> > > > > > I ran unloading first.
> > > > > >
> > > > > > David
> > > > > >
> > > > >
> > > >
> > > >
> > >
> >
> >
