roberts


Group: Members
Posts: 4983
Joined: Oct. 2003 |
 |
Posted: May 19 2006,19:40 |
 |
I have a couple of ibm thinkpads to test with. A T20 and a 240.
My hunch is that you may be experiencing IRQ conflicts. Especially when using new(er) wireless card with old(er) hardware.
If you try this:
$ dmesg | grep IRQ
then look for Sharing and the irq involved. New(er) hardware is better at irq assignments/sharing.
If you see such sharing happening then you can see what device it is by...
lspci -v | grep xx:xx.x
where the x is the device number show from the above grep of dmesg
Possible to assign different irq via BIOS or during modprobe?
I have tested ndiswrapper with four different wireless devices and all work fine. But then I don't have irq conflicts with these devices. I have one atheros card that does have such a conflict.
HTH
|