linux-kernel - Re: yenta_socket: PCMCIA-Cards are not recognised by kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 Sep 2009 20:35:08 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Christian Krämer <christian@...emer-eu.de>
Cc:	linux-kernel@...r.kernel.org, linux-pcmcia@...ts.infradead.org
Subject: Re: yenta_socket: PCMCIA-Cards are not recognised by kernel

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/