LKML Archive on
help / color / mirror / Atom feed
From: "Chatre, Reinette" <>
To: "Lukas Hejtmanek" <>
Cc: <>,
	<>, <>
Subject: RE: Recent driver in linux kernel 2.6.25-rc2
Date: Mon, 10 Mar 2008 17:35:32 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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 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



  reply	other threads:[~2008-03-11  0:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-19 15:39 Lukas Hejtmanek
2008-02-19 22:28 ` Chatre, Reinette
2008-02-19 22:44   ` Lukas Hejtmanek
2008-03-11  0:35     ` Chatre, Reinette [this message]
2008-03-11  9:42       ` Lukas Hejtmanek
2008-03-11 11:30         ` Tomas Winkler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='RE: Recent driver in linux kernel 2.6.25-rc2' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).