Linux For Cynics One user's experiences with Linux

28Feb/113

toshset: required kernel toshiba support not enabled

Toshiba Laptop

Save me!

Problem:

You updated your Toshiba machine's Ubuntu installation and now toshset, the handy command-line tool that gives us control over Toshiba's hardware interface, no longer works and simply says: "required kernel toshiba support not enabled". This problem has been diagnosed to death: The experimental toshiba patch was dropped from the kernel, with the intention to see if this breaks something for anyone. Well, it broke something for me and many others. Does that matter? No, the kernel team has pushed this responsibility onto the "driver people." What this actually means is that you, dear all-important user, has to fix it.

Solution:

The quick and dirty instructions are below, most of the instructions come from the Ubuntu KernelCustomBuild webpage. I might have missed something, please post any corrections.
1) Get ubuntu kernel source package and kernel building tools packages (I had all these installed, so I don't know what is required)
get the kernel source package:

#> sudo apt-get install linux-source-2.6.35

get the kernel building source packages:

#> sudo apt-get install kernel-package libncurses5-dev fakeroot wget bzip2

(maybe not all these packages are necessary, but I don't think it will harm to install them)
2)

#> cd /usr/src

3)

#> sudo wget http://schwieters.org/toshset/toshiba_acpi-current.patch

4)

#> sudo tar -jxf linux-source-2.6.35.tar.bz2

5)

#> cd linux-source-2.6.35

6)

#> sudo patch -p1 < ../toshiba_acpi-current.patch

7)

#> cd drivers/platform/x86/

8) I only wanted to build the toshiba_acpi module. So I commented out all the other modules from the Makefile. Using sudo make a backup copy of the Makefile, then edit the Makefile to only build the toshiba_acpi module. Just put # in front
of the other modules.
9)

sudo make -C /usr/src/linux-headers-`uname -r` M=`pwd` modules

10)

sudo make -C /usr/src/linux-headers-`uname -r` M=`pwd` modules_install

11)

sudo depmod -a

12) Driver should be into /lib/modules/*/extra/toshiba_acpi. rmmod and modprobe
to load the new module. (Rebooting should work as well)
Copy the file toshiba_acpi.ko to /lib/modules/*/extra (replace * with your current kernel version).
remove the old module:

#> sudo rmmod toshiba_acpi

and load the new module:

#> sudo modprobe toshiba_acpi

(or simply reboot)

Source: https://bugs.launchpad.net/ubuntu/+source/toshset/+bug/644898
https://help.ubuntu.com/community/Kernel/Compile

Tagged as: 3 Comments
23Feb/110

Microsoft Bans GPL From From Windows Market

Super GNU and Tux
Red Hat employee Jan Wildeboer called attention to a change in the Microsoft Application Provider Agreement in his personal blog. He notes that Microsoft has decreed ABSOLUTELY NO (GPLV3-OR-COMPAT-LICENSED) FREE SOFTWARE FOR WINDOWS PHONE AND XBOX APPS.

The license specifically mentioned is the GPL, which if allowed would put the onus on Microsoft, as the distributor, to fulfill the requirements of the license even tho it was chosen by a developer. Microsoft is covering their own back here, nothing more imho - they could be up for some serious issues if they cocked up GPL compliance, so they are just not going there.

The other way to look at this is that Microsoft is evil. Or something. Whether or not Microsoft perceives Free software as a threat, I see this as just another example of how sometimes FOSS is just not compatible with Microsoft's view of the computing world. The good news? No one gives a shit about Windows Phone. Besides, enough of this nonsense, and no one will care about Xbox "apps" either. To believe Microsoft can define the relevant landscape anymore is delusional, whether you're Microsoft's lawyers or a Red Hat employee.

Source: slashdot.org

Tagged as: , No Comments
14Feb/110

How To: ssh login without password

So you want to automate some tasks that involve logging into a remote server using ssh. Clearly, you have to be able to do so without being there to enter a password, and of course, you don't want to store the password in the shell script. Thankfully, there is a way to accomplish this.

For this post let local_machine be the machine you can actually touch, and let local_user be the user account you use on that machine. Let remote_machine be the machine you want to ssh into, and remote_user be the user account you use on that machine.

First log in on local_machine as user local_user and generate a pair of authentication keys. Do not enter a passphrase:

local_user@local_machine:~> ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/local_user/.ssh/id_rsa): 
Created directory '/home/local_user/.ssh'.
Enter passphrase (empty for no passphrase): 
Enter same passphrase again: 
Your identification has been saved in /home/local_user/.ssh/id_rsa.
Your public key has been saved in /home/local_user/.ssh/id_rsa.pub.
The key fingerprint is:
3e:4f:05:79:3a:9f:96:7c:3b:ad:e9:58:37:bc:37:e4 local_user@local_machine

Now use ssh to create a directory ~/.ssh as user remote_user on remote_machine. (The directory may already exist, which is fine):

local_user@local_machine:~> ssh remote_user@remote_machine mkdir -p .ssh
remote_user@remote_machine's password:

Finally append local_users's new public key to remote_user@remote_machine:.ssh/authorized_keys and enter remote_user's password one last time:

local_user@local_machine:~> cat .ssh/id_rsa.pub | ssh remote_user@remote_machine 'cat >> .ssh/authorized_keys'
remote_user@remote_machine's password: 

From now on you can log into remote_machine as remote_user from local_machine as local_user without password:

local_user@local_machine:~> ssh remote_user@remote_machine hostname
remote_machine
4Feb/110

How To: Use External Monitor connected to Laptop with Closed Lid

This article assumes you are running Ubuntu 9.10 - 10.10 and gnome. It may apply to other similar setups.

Problem: You want to "dock" your laptop, attach it to an external monitor, and close the lid. When you do so, the screen turns off. So you go to System>Preferences>Power Management, but you find there is no "Do Nothing" option for On Lid Close. I am pretty sure there used to be such an option, but some bonehead removed it.

Solution: The option wasn't really removed, just "hidden" by our well-meaning bonehead. Fire up our good friend the terminal, and type:

gconftool-2 --type string --set /apps/gnome-power-manager/buttons/lid_ac "nothing"