From: Christian Lamparter <chunkeey@googlemail.com>
To: "Martin Partridge" <martin_partridge@btconnect.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: help with wg511v2
Date: Sat, 30 Jul 2011 13:12:17 +0200 [thread overview]
Message-ID: <201107301312.17758.chunkeey@googlemail.com> (raw)
In-Reply-To: <op.vzexmjbnhgplxr@melanie>
On Saturday 30 July 2011 05:36:09 Martin Partridge wrote:
> I've checked everything and the WG511v2 is still not lighting up and it
> isn't showing as a network card, it is detected when plugged in:
>
> [13523.594828] pcmcia_socket pcmcia_socket0: pccard: card ejected from slot 0
> [13524.917077] pcmcia_socket pcmcia_socket0: pccard: CardBus card inserted into slot 0
> [13524.917132] pci 0000:02:00.0: [11ab:1faa] type 0 class 0x000200
> [13524.917176] pci 0000:02:00.0: reg 10: [mem 0xd0000000-0xd000ffff]
> [13524.917200] pci 0000:02:00.0: reg 14: [mem 0xc0000000-0xc000ffff]
>...
> and when the output from lspci is:
>
> 00:09.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro
> 100 (rev 09)
> 00:09.1 Serial controller: Agere Systems LT WinModem
> 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88w8335 [Libertas] 802.11b/g Wireless (rev 03)
^^^^^^^
Ah, this explains it everything. You are unfortunately a victim of Netgear's stupid
naming scam. The situation is explained at http://daemonizer.de/prism54/wg511/
The upshot is: there are two WG511 v2 versions, but only the first v2 works with
p54. The second one needs a driver from marvell.
Regards,
Chr
next prev parent reply other threads:[~2011-07-30 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 23:33 help Martin Partridge
2011-07-28 23:47 ` help Christian Lamparter
[not found] ` <op.vzexmjbnhgplxr@melanie>
2011-07-30 11:12 ` Christian Lamparter [this message]
2011-08-01 21:10 ` help with wg511v2 Pavel Roskin
2011-07-29 3:12 ` help Pavel Roskin
2011-07-29 16:32 ` help Pavel Roskin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201107301312.17758.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin_partridge@btconnect.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).