Ticket #377 (reopened defect)

Opened 2 years ago

Last modified 11 months ago

kismac don't load D-link DWA-110 driver

Reported by: kewouin Owned by: gkruse
Priority: critical Milestone:
Component: driver subsystem Version: 0.3
Keywords: kismac 0.3 d-link DWA-110 DWA 110 rt73 rt 73 driver mac os X osx Cc:

Description

i'm using a Macbook unibody ( 2009 october version ) model number : MacBook5,1 Mac OSX 10.6.2 Official Kismac 0.3 i use d-link DWA-110 with rt73 chipset

i have tried to start scan after plug the dwa-110 and configure it in kismac but it says the following thing :

Could not instantiate Driver. KisMAC was able to load the driver backend for USB RT73 device, but it was unable to create an interface. Make sure your capture device is properly plugged in. If you think everything is correct, you can try to restart your computer. Maybe your console.log and system.log show more details.

i don't know how to post my kismac log..

first time i've tried to run scan withouth d-link driver and many time after i've tried to install driver and it don't work. i've uninstalled d-link driver

thank for your help

and sorry for my poor english ( i'm french )

Change History

comment:1 Changed 2 years ago by fish

  • Status changed from new to closed
  • Resolution set to invalid
  • Component changed from build to driver subsystem

Please don't post both a ticket and in the forum.

Uninstall the OS drivers, as well-covered on the FAQ. Information on finding the console.log is also in the FAQ.

The information IS out there. Thanks.

comment:2 Changed 19 months ago by remolinero

  • Status changed from closed to reopened
  • Resolution invalid deleted

This report is valid. In Kismac 0.3, the vendorID:ProductID of DWA-110 are changed. They are 15367:2001. They should be 2001:15367 (compared to Kismac 0.2.99 wich works)

The file containing this data is:

KisMAC.app/Contents/Resources/UsbVendorsRT73.plist

The D-LINK DWA-111 vendorID:ProductID seems to have the same problem.

comment:3 Changed 18 months ago by fish

  • Priority changed from major to critical

If this is correct, possible duplicate tickets are: #379 and #391.

comment:4 Changed 11 months ago by davir6

that worked for me.

Note: See TracTickets for help on using tickets.