From: Frans Pop <elendil@planet.nl>
To: Christian =?iso-8859-1?q?Kr=E4mer?= <christian@kraemer-eu.de>
Subject: Re: yenta_socket: PCMCIA-Cards are not recognised by kernel
Date: Thu, 3 Sep 2009 20:35:08 +0200
User-Agent: KMail/1.9.9
Cc: linux-kernel@vger.kernel.org, linux-pcmcia@lists.infradead.org
References: <200909021856.29565.christian@kraemer-eu.de> <200909031927.19590.elendil@planet.nl> <200909032007.18484.christian@kraemer-eu.de>
In-Reply-To: <200909032007.18484.christian@kraemer-eu.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 8BIT
Content-Disposition: inline
Message-Id: <200909032035.10342.elendil@planet.nl>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1264
Lines: 29

On Thursday 03 September 2009, Christian Kr?mer wrote:
> On Thursday 03 September 2009 19:27:18 Frans Pop wrote:
> > Christian: what is the PCI ID of the device? You can find out using
> > 'lspci -H1 -nn'.
>
> The device class is 0200 and the PCI ID is 168c:0013.
>
> Here is the line lspci -H1 -nn shows for the card:
> 01:00.0 Ethernet controller [0200]: Atheros Communications Inc.
> AR5212/AR5213 Multiprotocol MAC/baseband processor [168c:0013] (rev 01)

That means that the card should be supported by the ath5k wireless driver 
if it was correctly initialized by the cardbus drivers.

I happen to have a similar PCMCIA card (from a different vendor: Trust) 
that has the same PCI ID and works without problems.

I don't think I can help you any further. Hopefully one of the PCMCIA 
developers can. One last suggestion could be to enable the PCMCIA_DEBUG 
option in the kernel and activate that as documented in the Kconfig help 
for that option. Suggest you use a current kernel if you do that.

Good luck,
FJP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/