New application's coming: Samsung Tools!

[Dominator]

Please try to force the reinstallation of the 'easy-slow-down-manager' package, as it was explained in a post above. This should fix the problem.

I did that but it didn't work. Toggling wireless never worked for me so far.

[voria]

Please use these commands in a terminal:

Code: Select all

echo 0 | sudo tee /proc/easy_slow_down_manager

Code: Select all

sudo rfkill block wifi

They should disable the wireless.
If they work, use these commands to reenable the wireless:

Code: Select all

echo 1 | sudo tee /proc/easy_slow_down_manager

Code: Select all

sudo rfkill unblock wifi

Please attach here the output of the commands.

[Dominator]

Unfortunately it didn't work.
There's no output from rfkill.

It doesn't even seem to "see" the wireless card, only bluetooth:

Code: Select all

$ rfkill list all
0: hci0: Bluetooth
	Soft blocked: yes
	Hard blocked: no

[voria]

What instead about the commands to the 'easy-slow-down-manager' interface?
Do they work?

At the moment 'Samsung Tools' manages the wireless by using both the 'esdm' interface and the 'rfkill' command. They are both mandatory, if only one of them does not work as intended, the wireless control is not available (as you already noticed).
The 'rfkill' command is not really needed for managing wireless, I added it because it's able to "inform" applications like 'NetworkManager' that the wireless status has changed, so they get updated instantly.
If needed I can make the 'rfkill' command to be optional in order to have the wireless control working even when 'rfkill' is not available.

[Dominator]

The commands to the esdm interface only return either 0 or 1, but I suppose that's only the echo. Should there be more output?

[voria]

No, this is normal. No output means no errors.
By looking at the frontal LED of your netbook, is the wireless really toggled when the commands are used? When you turn off the wireless (ie, write the '0' to the 'esdm' interface), are you yet able to load a new web page?

[voria]

Sorry, I had a slip and I did a mistake.
The correct commands for toggling wireless are:

Code: Select all

echo 0 | sudo tee /proc/easy_wifi_kill

Code: Select all

echo 1 | sudo tee /proc/easy_wifi_kill

Please try them and post the results.

[Dominator]

Yes, those commands work!

But that doesn't explain why it doesn't work with Fn + F9...
Possibly a problem with privileges?

[voria]

Please install the latest 'samsung-tools' from the repository, it fixes the problem.

[Dominator]

It's fixed! Thank you very much!

But now I'm curious of what the problem was

[voria]

As I said, with older version of 'Samsung Tools' the wireless control was available only if both the 'esdm' interface and the 'rfkill' command were working as expected.
Since 'rfkill' don't work for you, the whole wireless control was reported as not working.

Now instead only the 'esdm' interface is really required.
'Samsung Tools' tries to use the 'rfkill' command: if it fails, the error is simply ignored.

[OphiuchuS]

Reinstalled Lucid due to Kdesudo problems on my n140 today, performing all updates including kernel x.32-21 from the voria archive ppa (freeze is gone , and after installing samsung-tools I get this error at reboot:

"Your System encountered a serious Kernel Problem. Your System might become unstable now and might need to be restarted"

However nothing bad happens after clicking away the message. I'don't think bluetooth is really shut down however, the icon doesn't grey out like before and powertop is saying that bluetooth is still active.

[voria]

after installing samsung-tools I get this error at reboot:
"Your System encountered a serious Kernel Problem. Your System might become unstable now and might need to be restarted"
However nothing bad happens after clicking away the message

I got it too, but it's not related to 'samsung tools'. I think the problem will be fixed at the time Lucid will be officially released.

. I'don't think bluetooth is really shut down however, the icon doesn't grey out like before and powertop is saying that bluetooth is still active.

Please try to block/unblock bluetooth by using the 'rfkill' command line utility and post here the results:

Code: Select all

rfkill block bluetooth
rfkill unblock bluetooth

Anyway, for a complete power management, you have to install 'laptop-mode-tools' and configure it through the 'Samsung Tools Preferences' window.

[Dominator]

Is undervolting supposed to work for Atom N450?

It doesn't matter if I enter the lowest possible VID - the stability and battery life seem to be unaffected.

[OphiuchuS]

without the 'sudo' command I get this output

Code: Select all

Can't open RFKILL control device: Permission denied

and with sudo there's no output or any status changing at all (as far as I can tell)