public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tom Rymes <trymes@rymes.com>
To: development@lists.ipfire.org
Subject: rfkill
Date: Mon, 16 Dec 2019 18:52:55 -0500	[thread overview]
Message-ID: <4639465b-d23c-2a80-1b0c-d756ec09aace@rymes.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]

Folks,

I have been having this issue for quite some time, and though it isn't a 
major issue, it is keeping me from using some older hardware that is, 
due to the Intel vulnerabilities, perversely more secure (it's 32-bit).

The long story short is that I have devices with wireless cards that use 
the b43 driver, and they refuse to come up because they see the rfkill 
switch as being on. These devices worked fine before Core 105 was 
released. Nothing we do seems to resolve this, and IPFire doesn't 
include the rfkill utility (it does include the rfkill kernel module).

How difficult would it be to include the rfkill utility? That would 
allow me to use it to try and override the switch.

https://mirrors.edge.kernel.org/pub/software/network/rfkill/

Here's an old forum thread we posted when this became an issue back with 
core 105: https://forum.ipfire.org/viewtopic.php?t=17398

Tom

PS: After I wrote this, I downloaded an rfkill RPM for a different 
architecture and extracted the binaries. It runs and it allowed me to 
unblock the device and get it working. I do think it would be a helpful 
addition to the distribution.

             reply	other threads:[~2019-12-16 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-16 23:52 Tom Rymes [this message]
2019-12-18 12:21 ` rfkill Michael Tremer
2019-12-19 17:09 ` [PATCH] rfkill: New package Stefan Schantl
2019-12-19 17:56   ` Michael Tremer

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=4639465b-d23c-2a80-1b0c-d756ec09aace@rymes.com \
    --to=trymes@rymes.com \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox