Return-Path: Received: from fiji.isa.ott.rebel.com (fiji [10.1.2.10]) by quad.rebel.com. (Netscape Messaging Server 4.15) with ESMTP id G8M8ZR00.5HU for ; Sun, 11 Feb 2001 18:23:51 -0500 Received: from gate.rebel.com (gate [10.1.1.2]) by fiji.isa.ott.rebel.com (8.9.1b+Sun/8.9.1) with SMTP id SAA03417 for ; Sun, 11 Feb 2001 18:23:50 -0500 (EST) Received: from Huntington-Beach.Blue-Labs.org ([208.179.0.198]) by gate.rebel.com via smtpd (for fiji.isa.ott.rebel.com [10.1.2.10]) with SMTP; 11 Feb 2001 23:23:13 UT Received: from blue-labs.org (david@localhost [127.0.0.1]) by Huntington-Beach.Blue-Labs.org (8.11.0/8.11.0) with ESMTP id f1BNNa103851 for ; Sun, 11 Feb 2001 15:23:39 -0800 Message-ID: <3A871EF8.40209@blue-labs.org> Date: Sun, 11 Feb 2001 15:23:36 -0800 From: David Ford User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.1-pre11 i686; en-US; m18) Gecko/20010208 X-Accept-Language: en MIME-Version: 1.0 To: Bob james Subject: Re: PCMCIA IRQ Problem In-Reply-To: <3A83F088.C4CA6124@rebel.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Bob james wrote: > David, > > I am trying to get a PCMCIA wireless card going in a desktop (2.4.0 > kernel) using a card reader. It works in my buddy's machine but not > mine. I get messages like: > > No IRQ known for interrupt pin B of device 01:02.1. Please try using > pci=biosirq. > No IRQ known for interrupt pin A of device 01:02.0. Please try using > pci=biosirq. > > I noticed that you were having a similar problem last September. Did > you ever get it resolved? Any suggestions? > > Thanks very much for your time. > > Regards, > Bob James. Yes, it was solved. It was an IRQ routing table problem and Linus solved it just before 2.4.0. I recommend you run an 'lspci -v', run the pirqdump tool from pcmcia-cs tools, and enclose a copy of your dmesg. Post it to linux-kernel@vger.kernel.org. have you tried pci=biosirq? -d