Re: pcmcia support (fwd)

[Federico Carminati]

Hello,
  trying to follow this thread. I am an absolute beginner. I bought a
laptop clone, PIV 2.4GHz and installed 7.3RH. The sound does not work and
I have the impression that this is because the sound system and the modem
share an IRQ (9?), which I have the impression is not supported by Linux,
while it works with windows. From the message below you can see that I was
suggested to write to the linux kernel list which I am doing now. The
chipset is VIA VT8233. I installed the OSS sound system, and it works
erratically. Any help would be appreciated. Thanks in advance. Fed

                                            Federico Carminati

==============================================================================
|| Federico Carminati             ||  Tel.: [phone]                 ||
|| CERN-EP                        ||  Fax.: [phone]                 ||
|| 1211 Geneva 23                 ||                                        ||
|| Switzerland                    ||                                        ||
==============================================================================

---------- Forwarded message ----------
Date: Wed, 7 Aug 2002 22:29:04 -0700
From: dhinds <[e-mail]>
To: Federico Carminati <[e-mail]>
Subject: Re: pcmcia support

On Thu, Aug 01, 2002 at 11:50:53PM +0200, Federico Carminati wrote:
> The laptop has no brand, as it is an assembled clone. The yenta messages are 
> there:
> 
> 
> Aug  1 00:36:27 localhost kernel: Yenta IRQ list 00b8, PCI irq0
> Aug  1 00:36:27 localhost kernel: Socket status: 30000410
> Aug  1 00:36:27 localhost kernel: Yenta IRQ list 02b8, PCI irq0
> Aug  1 00:36:27 localhost kernel: Socket status: 30000006
> 
> Trying to install sound i discovered that some IRQ's are shared, which does 
> not help. Thanks, Fed

I'm afraid the problem is in the PCI subsystem and I have no other
workaround if pci=biosirq does not help.  The yenta driver relies on
the PCI subsystem to find the interrupt assignment for the cardbus
bridge device, and doesn't work properly if the interrupt can't be
determined.

You can try reporting the bug to the PCI subsystem maintainer or to
the linux-kernel mailing list.  I don't know enough about PCI to try
to track it down.

-- Dave