Brightness control from Linux using grub parameter

Brightness on my HP Probook 4740s requires a Grub parameter to work properly.
Edit /etc/defaults/grub to add "acpi_backlight=vendor acpi_osi=Linux" to the GRUB_CMDLINE_LINUX_DEFAULT line.
Then run "grub-update".
Thanks:
http://forums.opensuse.org/showthread.php/485869-OpenSUSE-brightness-control-problem-on-HP-ProBook-4740s

Re: FAQ(16): Using HTTP protocol in SDM - HP Enterprise Business Community

Re: FAQ(16): Using HTTP protocol in SDM - HP Enterprise Business Community:

This post explains how to force the use of HTTP with HP SoftPaq Download Manager (SDM) instead of the default passive FTP.

Use the switch /FORCEHTTP.

This solved the errors I was getting with SDM saying it could not access ftp.hp.com with v3.4.10.0.
It immediately downloaded v3.4.11.0, so maybe it's fixed in this version anyway?

Wireshark showed the passive FTP failing with v3.4.10.0.

'via Blog this'

How-to Seti@Home on Cloud Ubuntu CLI

I needed to test the performance of a bunch of cloud machines this weekend, and what better way to do that then by running up a whole load of Seti@Home instances.

I did this by following these steps:

1. sudo apt-get update - Some cloud images were out of date and produced errors if this wasn't run before installing any software.
2. sudo apt-get install boinc-client - Some Clouds had 12.04 which needed about 350MB of downloads, some had 11.10 which only needed about 250MB.
3. sudo /etc/init.d/boinc-client restart - Not sure this was really required, but it was a nice check to see that it was installed correctly and would stop and start again.
4. boinccmd --lookup_account http://setiathome.berkeley.edu email@address password - This returns the authentication code which you need for the next step.
5. boinccmd --project_attach http://setiathome.berkeley.edu/ authentication_code - This attaches the client to the project. Use a different URL for a different project. This also assumes you have a project username which you used in the previous step.
6. boinccmd --set_network_mode always - Allows transfers to happen any time. Not sure if this is persistent.
7. boinccmd --set_run_mode always - Allows the client to run all the time. Again, not sure if persistent.
8. boinccmd --get_state | more - Make sure that the project has been registered correctly, and that it is getting work-units and tasks.
9. sudo apt-get dist-upgrade - Most cloud images seemed to have an out-of-date kernel and needed some other stuff after the large download earlier.
10. sudo reboot - After all that patching, make sure the machines are clean. All the cloud images I was testing had persistent images, so no problems restarting them.

I now have 35 cloud instances of Seti@Home running in addition to my small local server. It was very apparent how much difference there was in each instances performance, with some virtual machines taking 3 time longer to set-up than others.

I've been using the remainder of the £50 credit I got for Infiniserv, and 3 beta instances on the HP cloud.

Have you guys had and differing experiences?

Windows 7 on an HP DV9000 (DV9292EU)

I've been having a bit of an install fest this weekend with Windows 7 Ultimate on my HP DV9292EU, Windows 7 Enterprise on my Work laptop and Android (!) on my trusty ASUS eeePC 701. All went fine except the HP laptop which had three unknown devices in device manager after the install.

One was labeled as a co-processor. I don't know what it was, but downloading the NVidia Nforce 430 drivers from here solved it:
http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Select Legacy, NForce 4 and then one of the 430 drivers. It downloaded this file which worked for me:
15.49_nforce_winvista_win7_32bit_international_whql.exe

The two other device were labeled Base System Devices and proved to be some sort of Ricoh devices.
Downloading the Windows 7 drivers from the Lenovo site fixed these for me!
http://www-307.ibm.com/pc/support/site.wss/WIN7-BETA.html#rmcr

It now all looks good!