linux-kernel - RE: Recent driver in linux kernel 2.6.25-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <D936D925018D154694D8A362EEB0892003DB2DC5@orsmsx416.amr.corp.intel.com>
Date:	Mon, 10 Mar 2008 17:35:32 -0700
From:	"Chatre, Reinette" <reinette.chatre@...el.com>
To:	"Lukas Hejtmanek" <xhejtman@....muni.cz>
Cc:	<ipw3945-devel@...ts.sourceforge.net>,
	<linux-kernel@...r.kernel.org>, <linux-wireless@...r.kernel.org>
Subject: RE: Recent driver in linux kernel 2.6.25-rc2

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/