Next-in-Thread Next Message

News The problem is in Cardmgr! 

Forum: PCMCIA Wireless Network Adapter Issues
Re: Question Windows-2-Linux communication problems (Andrew Fernandes)
Date: 2000, Aug 28
From: Andrew Fernandes <>


After an intense weekend of debugging, I've discovered that the Lucent driver actually (sort-of) DOES work!

The scenario: all cards and OSes have the 21-July release of Lucent's drivers and firmware. The wvlan_cs driver loads up, starts the net device, but can't talk to windows boxes. The wavelan2_cs driver won't even load up.

It turns out that the reason the wavelan2_cs driver doesn't load is because cardmgr dies BEFORE it can send the device a DS_BIND_DEVICE ioctl! Stepping through cardmgr with a debugger, it shows all the signs of classic memory corruption. Harmless calls like "syslog" lock up forever, and previously valid instructions cause "illegal instruction" and "segmentation fault" errors.

So... when using the wavelan2_cs driver: if I jump over all the "syslog" calls, which should theoretically not make any difference, the net device is correctly brought up by the module. Yay!

I still can't talk to the windows box, but there may still be something funny going on. Even thought I delicately stepped through cardmgr with my debugger (and things inside it were corrupted), it reported several "could not adjust resource" (memory and I/O errors).

So, until I (or David!) can track down the corruption in cardmgr, it may be possible to use Lucent's driver with the latest firmware to talk to windows boxes...



Next-in-Thread Next Message

Select this message: The problem is in Cardmgr!

Messages Inline: 1 All Outline: 1 2 3

1. More 'Twas a buffer overflow error... by Andrew Fernandes, 2000, Aug 31

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.

If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination

If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages

Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

Members Subscribe No Admin Mode Show Frames Help for HyperNews at 1.10
[ Edit This Forum ]