On Tuesday, February 19, 2008 2:44 PM, Lukas Hejtmanek wrote: > On Tue, Feb 19, 2008 at 02:28:58PM -0800, Chatre, Reinette wrote: >>> as of pre 2.6.25 kernels, kismet monitoring tool does not work with >>> the message: # kismet Launching kismet_server: >>> //usr/bin/kismet_server >>> Suid priv-dropping disabled. This may not be secure. >>> No specific sources given to be enabled, all will be enabled. >>> Non-RFMon VAPs will be destroyed on multi-vap interfaces (ie, >>> madwifi-ng) Enabling channel hopping. >>> Enabling channel splitting. >>> Source 0 (iwl4965): Enabling monitor mode for iwl4965 source >>> interface wlan0 channel 6... FATAL: Failed to set channel 6 >>> 5:Input/output error >> >> Please load the driver with debugging enabled (debug=0x43fff) and >> send us the log capturing during this kismet startup. > > the log is attached. sorry for the delay - please do submit a bug at bughost.org to enable us to track this problem. The error you get is strange - the reason why the channel could not be set was because the device is not considered to be ready. Yet, from your debug log all the required steps appear to have completed successfully. Could you please add a print to the function iwl4965-base.c:iwl4965_is_ready to see what the value of priv->status is? Thanks Reinette -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
