I've taken the current CVS version and older version of ndis.c. Just run
cvs co ndiswrapper
cvs up -r 1.61 driver/ndis.c
Then you have to modify ndis.h - add following line to declaration of
struct work_struct bh;
I've also modified Makefile to include CC=gcc32 since kernel in Fedora
Core is compiled by this one, not gcc (3.3).
Now you can install the driver as described in INSTALL file. Hopefully
it will work for you too.
Scott Robertson wrote:
> Can you let mw know when you get that problem fixed? I have the exact
> same problem on my T40. I've tried the latest CVS and the older 3.0
> version. Plus I've also tried 3 different versions of Pro/Wireless 2100
> drivers. It still locks up after a bit of time and the caps lock starts
> blinking. I am also running Fedora w/ the 2.4.22 kernel.
> --On Thursday, January 08, 2004 6:07 PM +0100 Martin Frydl
> <martin.frydl@...> wrote:
>> I've got the Centrino wifi to work, but I still experience some
>> problems. My config:
>> IBM ThinkPad R40
>> Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
>> ASUS driver
>> Fedora Core 1
>> Kernel 2.4.22-1.2129.nptl
>> When I try the CVS version (or 0.4) of ndiswrapper, the module very
>> quickly locks the computer. The caps lock led starts blinking and
>> computer stops responding and redrawing screen. There is no message in
>> syslog. The only possibility is reboot.
>> I've tried revision 1.61 of ndis.c with the rest up to date. In this
>> configuration, it runs with more or less problems. I've got just single
>> crash during second resume (first try was OK) and some during module
>> Looking at differences between 1.61 and current revision (1.69), it
>> seems like the problem is in timer spinlocks and IRQ handling. This may
>> be the similar problem as reported by Navindra Umanee
>> since the IRQ is shared (/proc/interrupts):
>> 11: 1172861 XT-PIC usb-uhci, usb-uhci, usb-uhci,
>> ehci_hcd, ohci1394, Texas Instruments PCI1510 PC card Cardbus
>> Controller, radeon@..., ndiswrapper, Intel ICH4
>> I haven't tried any USB disabling or so.
>> I have also another problem with the device - it seems to randomly
>> enter power saving state. I guess this because the activity led goes off
>> and the network is unreachable. After some time, it is up again. I've
>> started to constantly ping one of computers on network and this reduced
>> the turn offs much. However, there is a problem with getting the device
>> up and configured since I cannot run ping prior to getting into network.
>> Has anyone experienced similar behavior?
>> This SF.net email is sponsored by: Perforce Software.
>> Perforce is the Fast Software Configuration Management System offering
>> advanced branching capabilities and atomic changes on 50+ platforms.
>> Free Eval! http://www.perforce.com/perforce/loadprog.html
>> Ndiswrapper-general mailing list
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> Ndiswrapper-general mailing list