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: <20080311094236.GB4344@ics.muni.cz>
Date:	Tue, 11 Mar 2008 10:42:36 +0100
From:	Lukas Hejtmanek <xhejtman@....muni.cz>
To:	"Chatre, Reinette" <reinette.chatre@...el.com>
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 Mon, Mar 10, 2008 at 05:35:32PM -0700, Chatre, Reinette wrote:
> 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?

I don't have this problem in 2.6.25-rc3 and rc4. However, it seems that the
card does not associate with AP if I set iwcofnig wlan0 essid any. Is this 
a bug or a feature? The AP does not use key and is visible.

-- 
Lukáš Hejtmánek
--
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/