On Thu, 18 Feb 2010 02:19 +0100, f...@kokkinizita.net wrote:
On Wed, Feb 17, 2010 at 05:36:31PM -0600, Aaron Griffin wrote:
Isn't this what rfkill is for?
http://linuxwireless.org/en/users/Documentation/rfkill
You're right: /sys/devices/platform/eeepc/rfkill/rfkill0/state
controls the
Am 18.02.2010 02:19, schrieb f...@kokkinizita.net:
On Wed, Feb 17, 2010 at 05:36:31PM -0600, Aaron Griffin wrote:
Isn't this what rfkill is for?
http://linuxwireless.org/en/users/Documentation/rfkill
You're right: /sys/devices/platform/eeepc/rfkill/rfkill0/state
controls the wifi device.
On Thu, Feb 18, 2010 at 11:39:38AM +0100, Thomas Bächler wrote:
Use the rfkill utility from core. It will display the rfkill devices and
modify their state. As James said, using the sysfs interface is
depreacted and it will disappear soon.
(/me reads rfkill.c)
Rfkill depends on the sysfs
Well, since I don't have /etc/acpi at all it looks like this
switch works without any soft support at all. So I guess it
just can't be disabled.
unless you install acpid and acpi-eeepc-generic. acpid puts acpi
event-handling in userspace, so then you can /dev/null fn+f2.
acpi-eeepc-generic
On Thu, Feb 18, 2010 at 10:43 AM, kludge drklu...@rat-patrol.org wrote:
Well, since I don't have /etc/acpi at all it looks like this
switch works without any soft support at all. So I guess it
just can't be disabled.
unless you install acpid and acpi-eeepc-generic. acpid puts acpi
On Thu, Feb 18, 2010 at 12:25:51PM -0800, epinull wrote:
On Thu, Feb 18, 2010 at 10:43 AM, kludge drklu...@rat-patrol.org wrote:
Well, since I don't have /etc/acpi at all it looks like this
switch works without any soft support at all. So I guess it
just can't be disabled.
unless
On Thu, Feb 18, 2010 at 1:11 PM, Fons Adriaensen f...@kokkinizita.net wrote:
On Thu, Feb 18, 2010 at 12:25:51PM -0800, epinull wrote:
On Thu, Feb 18, 2010 at 10:43 AM, kludge drklu...@rat-patrol.org wrote:
Well, since I don't have /etc/acpi at all it looks like this
switch works
Mu investigations where that the BIOS controlled Fn+F2, but it could be the
kernel module which I did not suspect at the time and so have not tested.
On my EeePC 1000, bios previous to revision 1003 did not controlled Fn+F2;
acpi-eeepc-generic needed to be used to enable/disable wifi. On newer
Hello all,
A few days ago I installed Arch on an EEE-1000H. Things
work very well and I'm sort of impressed by how easy it
worked out to be (there were a few hickups but nothing
serious).
Today I discovered one possible problem.
The key combination 'Fn + F2' enables or disables the
wireless
On 02/17/2010 05:16 PM, f...@kokkinizita.net wrote:
Today I discovered one possible problem.
The key combination 'Fn + F2' enables or disables the
wireless network device. If you hit it accidentally there's
no more wifi.
that's expected behavior, as indicated by the 'wifi' icon in blue on
On Wed, Feb 17, 2010 at 05:36:31PM -0600, Aaron Griffin wrote:
Isn't this what rfkill is for?
http://linuxwireless.org/en/users/Documentation/rfkill
There are rfkill entries in /sys
I'll try, but AFAIK rfkill is for bluetooth.
Ciao,
--
FA
O tu, che porte, correndo si ?
E guerra e morte !
On Wed, Feb 17, 2010 at 05:40:44PM -0600, kludge wrote:
On 02/17/2010 05:16 PM, f...@kokkinizita.net wrote:
Today I discovered one possible problem.
The key combination 'Fn + F2' enables or disables the
wireless network device. If you hit it accidentally there's
no more wifi.
On 02/17/2010 06:03 PM, f...@kokkinizita.net wrote:
is it safe to presume you installed acpi-eeepc-generic? because it has
a configuration file that let's you customize every key combination.
If that is a package name, no. Everything seems to work
without it, including e.g. the display
On Wed, Feb 17, 2010 at 05:36:31PM -0600, Aaron Griffin wrote:
Isn't this what rfkill is for?
http://linuxwireless.org/en/users/Documentation/rfkill
You're right: /sys/devices/platform/eeepc/rfkill/rfkill0/state
controls the wifi device. Problem solved.
Thanks !
--
FA
O tu, che porte,
14 matches
Mail list logo
