LKML Archive on
help / color / mirror / Atom feed
From: Iain <>
To: Carsten Niehaus <>
Cc: Rafael Cunha de Almeida <>,
Subject: Re: Weird behaviour on iwl3945 module
Date: Fri, 31 Oct 2008 14:48:38 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Carsten Niehaus wrote:
> Moin
> Is that the same issue as the one I reported agains 2.6.27 on Ubuntu 8.10?
> 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:

You want

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:


  reply	other threads:[~2008-10-31 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 11:01 Carsten Niehaus
2008-10-31 14:48 ` Iain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-10-31  7:39 Rafael Cunha de Almeida
2008-11-01 22:57 ` Rafael Almeida

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: Weird behaviour on iwl3945 module' \

* 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).