11g wireless card does not word in Linu

Hi, all

I had a 3Com OfficeConnect wireless 11g Pc card. I download the wireless
module from www.prism54.org and installed it. However, when I use
iwconfig to config the wireless network, it report:

eth1 NOT READY! ESSIDff/any
Mode:Managed Channel:0 Access Point: 00:00:00:00:00:00
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption keyff
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0


I use cardctl ident to checnk my card, it is

Socket 0:
product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
manfid: 0x01bf, 0x4301
function: 254 ((null))

On the card's cover, it is 3CRWE154G72.

Can anybody give me some suggestions on solving this problem?

Thanks.

Andy

> I use cardctl ident to checnk my card, it is
>
> Socket 0:
> product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
> manfid: 0x01bf, 0x4301
> function: 254 ((null))

I have the exact same problem! Just bought the card yesterday and I haven't
been able to make it work (prism54). Tried a zillion things.

My card says "3CRWE154G72 version 2.0" on the cover. I suspect that these
2.0 cards are rebrands or different from the original somehow.

I'm pretty pissed, because everywhere on the net it said that the
3CRWE154G72 was Linux compatible. How would I know, that it now comes in a
new version that doesn't :-(

On Fri, 27 Aug 2004 12:47:41 +0200, Line wrote:

>> I use cardctl ident to checnk my card, it is
>>
>> Socket 0:
>> product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
>> manfid: 0x01bf, 0x4301
>> function: 254 ((null))
>
> I have the exact same problem! Just bought the card yesterday and I haven't
> been able to make it work (prism54). Tried a zillion things.
>
> My card says "3CRWE154G72 version 2.0" on the cover. I suspect that these
> 2.0 cards are rebrands or different from the original somehow.
>
> I'm pretty pissed, because everywhere on the net it said that the
> 3CRWE154G72 was Linux compatible. How would I know, that it now comes in a
> new version that doesn't :-(

You might give Ndiswrapper a try with the card's XP driver. I'm using
Ndiswrapper and an XP driver on a Broadcom 54G which has absolutely no
native Linux drivers. Ndiswrapper + XP driver works very well, haven't
tried it in 802.11G mode but in 802.11B mode everything works including
WEP. My old laptop had a Prism based 802.11b card and the Prism driver
never worked very well, it sort of worked if WEP was disabled but if you
enabled WEP it would hang the card and only a cold reboot would fix it.

On Fri, 27 Aug 2004 12:47:41 +0200, Line wrote:
> > I use cardctl ident to checnk my card, it is
> >
> > Socket 0:
> > product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
> > manfid: 0x01bf, 0x4301
> > function: 254 ((null))
>
> I have the exact same problem! Just bought the card yesterday and I haven't
> been able to make it work (prism54). Tried a zillion things.
>
> My card says "3CRWE154G72 version 2.0" on the cover. I suspect that these
> 2.0 cards are rebrands or different from the original somehow.
>
> I'm pretty pissed, because everywhere on the net it said that the
> 3CRWE154G72 was Linux compatible. How would I know, that it now comes in a
> new version that doesn't :-(

I've got a version 1.0 card of this one and got it working immediately.
The version 2.0 card I've just picked up is something else entirely, and
I'm wondering whether it's a faulty card or a faulty design.

Pushing it in nothing triggers the hotplug in my SuSE 9.1. What I'm
wondering is whether you get the same as me when you (as root) issue
'cardctl ident' and 'cardctl info' to get some information on the card:

dyret:~ # cardctl status
Socket 0:
no card
Socket 1:
3.3V CardBus card
function 0: [ready]
dyret:~ # cardctl ident
Socket 0:
no product info available
Socket 1:
no product info available
dyret:~ # cardctl info
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255
PRODID_1=""
PRODID_2=""
PRODID_3=""
PRODID_4=""
MANFID=0000,0000
FUNCID=255

That is to say, I'm getting nothing from the card at all, on
four different laptops. No problem with other cards, cardbus
or not. Are you getting a different output from me to your
cardctl commands?

Bjørn
--
Bjørn Tore Sund "When in fear, and when in doubt;
(E-Mail Removed) Run in circles, scream and shout!"
Interaction! - Anonymous
http://www.interaction.worldcon.org.uk/

On 27/8/04 5:28 pm, in article (E-Mail Removed),
"General Schvantzkoph" <(E-Mail Removed)> wrote:

> On Fri, 27 Aug 2004 12:47:41 +0200, Line wrote:
>
>>> I use cardctl ident to checnk my card, it is
>>>
>>> Socket 0:
>>> product info: "3Com", "3CRSHPW15496 Wireless PC Card", "-", "-"
>>> manfid: 0x01bf, 0x4301
>>> function: 254 ((null))
>>
>> I have the exact same problem! Just bought the card yesterday and I haven't
>> been able to make it work (prism54). Tried a zillion things.
>>
>> My card says "3CRWE154G72 version 2.0" on the cover. I suspect that these
>> 2.0 cards are rebrands or different from the original somehow.
>>
>> I'm pretty pissed, because everywhere on the net it said that the
>> 3CRWE154G72 was Linux compatible. How would I know, that it now comes in a
>> new version that doesn't :-(
>
> You might give Ndiswrapper a try with the card's XP driver. I'm using
> Ndiswrapper and an XP driver on a Broadcom 54G which has absolutely no
> native Linux drivers. Ndiswrapper + XP driver works very well, haven't
> tried it in 802.11G mode but in 802.11B mode everything works including
> WEP. My old laptop had a Prism based 802.11b card and the Prism driver
> never worked very well, it sort of worked if WEP was disabled but if you
> enabled WEP it would hang the card and only a cold reboot would fix it.


Yer ndiswrapper! I just bought a belkin wireless card expecting for it to
work (duh), tried everything but nothing done it for me except installing
ndiswrapper with the xp driver. Use ndiswrapper 7 though, it is the only
version that didn¹t lock my machine up. Try 8 through 10 but if your comp
becomes unresponsive and the caps lock light flashes on the keyboard when
you modprobe you know why, just stick with v7 or 0.7 whatever.