There seems to be a fix for this bug in the madwifi-trac ticket. It involves commenting out a few lines in the driver and an updated version of vmware. Could we maybe get it fixed?
There seems to be a fix for this bug in the madwifi-trac ticket. It involves commenting out a few lines in the driver and an updated version of vmware. Could we maybe get it fixed?