linux-kernel - Re: Weird behaviour on iwl3945 module

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] [day] [month] [year] [list]

Message-ID: <490B1AC6.1030705@gmail.com>
Date:	Fri, 31 Oct 2008 14:48:38 +0000
From:	Iain <selsinork@...il.com>
To:	Carsten Niehaus <cniehaus@....de>
CC:	Rafael Cunha de Almeida <almeidaraf@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Weird behaviour on iwl3945 module

Carsten Niehaus wrote:
> Moin
> 
> Is that the same issue as the one I reported agains 2.6.27 on Ubuntu 8.10?
> 
>   https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/290820
> 
> Carsten
> 

The rfkill messages in dmesg are probably meaningless. I see them too and they don't stop the card from working.

What do you get if you type 'ip link' in a shell ?
I think you'll see something like:
wlan0: <NO-CARRIER,BROADCAST,MULTICAST>

You want
wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP>

to have any hope of getting any further.

On my HP laptop, it's impossible to bring the card up with 'ip link set up dev wlan0' when the hardware button is set to disable the 
wireless interfaces during boot, on at least 2.6.[25,26,27]. However once you press the button and enable the interface you can then 
bring the card up and it'll stay up when you press the button again.

The real problem for me with this is that normally the button is turned off during boot, so the startup scripts can't bring the card 
up and everything else falls apart from there.

Previously I've just been doing 'ip link set up dev wlan0' in an xterm after enabling via the button first time I need to use it, 
having done that, everything works fine.

With 2.6.27 the hp-wmi driver means that I get rfkill uevents over netlink and can use those to bring the card up automatically when 
the button is pressed. Perhaps there's a similar option on your laptops.

FWIW, I'm not using Debian/Ubuntu, or hal/dbus/NetworkManager,  but it was fairly trivial to find lots of discussion of this 
elsewhere, seemingly mostly related to Debian/Ubuntu:
<https://bugs.launchpad.net/ubuntu/intrepid/+source/linux/+bug/193970>
<https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267875>
<https://wiki.ubuntu.com/IntrepidReleaseNotes#Cannot%20reactivate%20Intel%203945/4965%20wireless%20if%20booting%20with%20killswitch%20enabled>

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