Message-ID: <3EBE75D5.7000301@terra.com.br>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030313
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Date: Sun, 11 May 2003 12:09:51 est5edt
Sender: os2-wireless_users-owner <os2-wireless_users-owner@2rosenthals.com>
Reply-To: os2-wireless_users@2rosenthals.com
From:  DoC <os2-wireless_users@2rosenthals.com>
To:  os2-wireless_users@2rosenthals.com
Subject: OS/2 Wireless Users List: Orinoco mini-PCI


Hello everybody... just knew about this list.

I just got a mini-PCI 802.11b card for my Toshiba notebook, with a 
Lucent/Agere Orinoco chipset. It's working perfectly on Linux and (gasp) 
WinXP, now I need to make it work under OS/2 if possible...

I know there's another card in the market (PCMCIA) from a company called 
Artem that uses the same chipset and has a driver for OS/2. I downloaded 
it, and got the Artem driver initializing the hardware, but not 
configuring it entirely. (e.g. no warnings at boot time). All I had to 
do was alter the .NIF file to accept another I/O range (in my case, 
FF40-FF7F), but the driver appears to still have a few hardcoded 
addresses: the interface appears as lan1 as expected, and I can even 
assign an IP address to it via ifconfig. But no communication... I even 
scanned the net on a friend's notebook, it appears to have its radio 
turned off (not broadcasting the SSID).

The card appears as an extra PCMCIA slot. Actually this machine has two 
distinct PCMCIA controllers (from lspci):
02:00.0 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
02:00.1 CardBus bridge: O2 Micro, Inc. OZ6933 Cardbus Controller (rev 01)
02:0b.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus 
Controller (rev 01)

I managed to get the Texas controller (the one the mini-PCI is attached 
to) recognized by PC Card Director using Daniela's hacked driver. 
Haven't tried enabling both, don't think PC Card Director will allow it?

I reckon the driver is looking for the card's ID and giving up without 
allocating all the resources (PC Card director IDs it, but shows as not 
ready). Any suggestions?

-- DoC


=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

To unsubscribe from this list, send a message to
steward@2rosenthals.com with the command
"unsubscribe os2-wireless_users" in the body
(omit the quotes).

For help with other commands, send a message
to steward@2rosenthals.com with the command
"help" in the body (omit the quotes).

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=