linux-kernel - Re: iwl3945 not working properly.

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: <20080218154713.GC3098@tuxdriver.com>
Date:	Mon, 18 Feb 2008 10:47:13 -0500
From:	"John W. Linville" <linville@...driver.com>
To:	Wael Nasreddine <mla@...reddine.com>
Cc:	LKML <linux-kernel@...r.kernel.org>, reinette.chatre@...el.com,
	yi.zhu@...el.com
Subject: Re: iwl3945 not working properly.

On Mon, Feb 18, 2008 at 05:54:25AM +0100, Wael Nasreddine wrote:
> Hello,
> 
> I have a Toshiba Satellite A135-S4427 with and Intel 3945ABG card, the
> driver is not working properly.
> 
> When I turn on my PC it works fine, but If I ever bring the interface
> down, I no longer can associate it with any AP without rebooting, even
> the one I was using, I tried rmmod/modprobe iwl3945, didn't do
> anything,
> 
> iwconfig shows that the wlan0 has the radio turned off, and
> 
> $ cat /sys/bus/pci/drivers/iwl3945/0000:04:00.0/rf_kill
> 1
> 
> Even If I echo 0 > /sys/bus/pci/drivers/iwl3945/0000:04:00.0/rf_kill
> whenever I try to associate the interface with an AP it turns back to
> 1, I tried both iwconfig and NetworkManager, same problem.
> 
> There's a button on my laptop for Radio SoftKill (fn+F8) but it's not
> working, the soft kill is being enabled/disabled without my
> interference.
> 
> I tried it on kernel-2.6.24 and kernel-2.6.25-rc2 same result...
> 
> Any help is appreciated...
> 
> P.S: Please Cc to me, I am not subscribed to the mailing list.

This sounds similar to the bug here:

	https://bugzilla.redhat.com/show_bug.cgi?id=432264

The OP in that bug reports that the problem continues even after
reverting to older kernels that worked previously.

Hopefully part of the Intel crew will have some clue as to what is
happending here?

John
-- 
John W. Linville
linville@...driver.com
--
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/