233 replies to this topic

[elmurato]

INFO: These scripts are very old. The Intrepid-scripts are now updated to support 8.04, so it`s recommended to install them if you still use Hardy:

http://forum.eeeuser...ic.php?id=49081

___________________________________________________________________

In this thread you can see the development of the Ubuntu-support-project for Ubuntu 8.04. First of all there is Adamm`s custom-kernel, which provides all the needed drivers/modules to get the EeePCs working. And then there are the ACPI scripts, which will provide the support for the Fn-keys and the the new hotkey bar.
If you have other ideas please let us know! Help is very appriciated.

Supported models:

* EeePC 900A
* EeePC 901
* EeePC 1000
* EeePC 1000H

Keymappings and their functions:

Note: These are the keymappings of the 900A/901. The keymappings of the 1000/1000H is a bit different.
* Fn+F1 Standby
* Fn+F2 WLAN-toggle
* Fn+F3/F4 Brightness
* Fn+F5 VGA-toggle
* Fn+F6 Taskmanager
* Fn+F7/F8/F9 Volume

* 1. new hotkey Display-toggle (internal)
* 2. new hotkey Bluetooth-toggle
* 3. new hotkey CPU frequency control or user-defined
* 4. new hotkey Webcam-toggle or user-defined
(*Fan control also available, but it must be enabled manually in the actions-file. Also the modules i2c-i801 and eee must be loaded before)


HowTo install:

1.) Download these files to an external memory (USB-stick, SD-card, ...):

Adams kernel & modules (See nr. 2)
ACPI scripts v1.3 by me

2.) Open a terminal and change into the directory of the drive with the downloaded files and install the new kernel and the ACPI scripts:

sudo dpkg -i linux-image*.deb linux-ubuntu-modules*.deb

Important: If you want to receive updates of the eeepc-kernel, you have to follow the steps on this site: http://array.org/ubuntu/setup.html

tar xfvz Hardy_ACPI_scripts-EeePC_900A_901_1000.tar.gz
cd Hardy_ACPI_scripts-EeePC_900A_901_1000/
chmod +x install.sh
sudo ./install.sh

3.) Reboot, select the new kernel in the bootmenu


Known issues:

To avoid screen flickering when changing the brightness the script moves a script to the backup folder. But this script is needed by the power-manager for "dim-on-idle". See this thread for more information: http://forum.eeeuser...ic.php?id=43400

____________________________________


Old text:

Quote

Hey guys,

yesterday I started to write a script to fix all the problems with Ubuntu 8.04 on the EeePC 901/1000/1000H. But the problem is that I don`t have a 901 yet. In Germany it will be available on 18.08.08. So I need your help.
There are many Linux-Newbies who wants an as-easy-as-possible way to fix Ubuntu. So I thought I could begin. I put all the different scripts and packages that I found together and wrote a little installer. But there is still something to do. And also it needs to be checked if it`s all right (fn-key-codes, etc.)... Maybe Adam could make a package and add it in his repository if we are ready with the script ;)

So please have a look at it and improve it. You can find the current version here:

Download

Note: PLEASE DO NOT INSTALL IT YET! (Except if you want to test it of course)

Currently implemented (but not tested!):

- Adam`s kernel
- Fn+F2 -> WiFi-and-BT-toggle (thx to Merkmal)
- Fn+(F3&F4) -> Brightness control (without OSD)
- Fn+F5 -> VGA toggle (from the wiki)
- Fn+F6 -> Gnome-System-Monitor
- Fn+(F7-F9) -> Volume Control
- Gnome tweaks (smaller fontsizes, etc.)

Edited by elmurato, 10 February 2009 - 06:18 PM.

[WillW]

Ah, competing solutions! For those of you not following the main thread about Adamms kernels, I am currently in the process of rewriting the whole hotkey handling process in Python (and wxPython), including a GUI for adjusting the keymappings, knowledge of keymappings for all eee models (suggestions as to how to autodetect welcome but not an urgent priority), pretty popups at appropriate moments etc.

Plan is to put it all in a proper .deb package so that it pulls in all the appropriate requirements (e.g. eepc-acpi and all of my dependencies) and automatically installs everything to the appropriate location, putting an icon in the System->Preferences Menu. Generally going for the Right Answer™ in terms of user friendliness.

The theory is that it would be nice if an eeepc running ubuntu could be made to work simply by installing a few pacckages from the repositories, adamm has taken a massive step in this direction with his kernel, and I'm just doing my bit.

[elmurato]

As I said in the other thread, your ideas sounds very nice! Espacially the GUI. Unfortunately I have no experiences with python, so I can`t help you. If there`s anything else I can do for you please let me know.

Auto-detect: Hmm that`s a goog question. First I thought a simple "cat /proc/cpuinfo" would do it, but the 900A is coming, and thats a 900 with atom, so you can`t differentiate the models. But could you try this:

cat /proc/acpi/info

This gives me "version: 20070126"...

Edited by elmurato, 09 August 2008 - 11:36 PM.

[il1019]

@elmurato: I get the same code, and I have a 901, so that won't work.

@WIIIW: I think this would be nice. What kind of GUI are you going to do? I was looking into doing something like this, but haven't gotten anywhere I wanted to try and leverage what is used for volume, but I have no idea on how to go about that. A GUI would be nice, but OSD would be awesome. I'd like to have a consistent look. I'd be interested to see where you take this.

[elmurato]

Thanks for the Test. There must be a way :S

A nice OSD would be really great.

@ WillW

Did you start already with the work?

Edited by elmurato, 10 August 2008 - 11:32 AM.

[gobion]

@elmurato and WillW: Yeah a custom python OSD would be really be awesome :)
@Pox (from previous thread): Your artwork looks great :)

[Pox]

OK, here's a complete set in the three styles, I think I've got everything we need... the icons (with the exception of the brightness, which I drew myself) are from the gnome-icon-set, so this is GPL'd.

http://pox.cerebrojd...eeosdart.tar.gz

The source svg and the batch-exported images are in there, though the pngs have the random names Inkscape gave them - I can't be bothered renaming them at the moment.
I'm still not sure on the volume/brightness, might add a spot for a progress-bar-esque meter...hopefully programmatically rendered and not with seventeen thousand different images as the asusosd has, though. ;)

[elmurato]

Oh man they`re looking beautiful! Thank you so much. Now only Will needs to start the project :P

[Chonnawonga]

Just a suggestion: as long as you're setting up toggling for wifi, bluetooth, and webcam, why not set up a toggle for the trackpad? I find when I have a mouse plugged in it's nice to be able to turn the trackpad off so that I avoid accidentally brushing it with my thumb or the base of my hand and screwing something up. Alternatively (though this may be more complicated) you could give the user the option of automatically turning off the trackpad when a mouse is plugged in.

Again, I really like the ideas (and artwork!) that are going into this so far. Count me in for testing on the 1000, spelling and grammar checking, and moral support!

[Pox]

Chonnawonga: a good idea, though I'm not sure on how to implement it: the touchpad isn't exposed in ACPI, and I think it's actually an internal USB device... it's certainly possible, but it would need a bit of research.

[Chonnawonga]

Quote

Chonnawonga: a good idea, though I'm not sure on how to implement it: the touchpad isn't exposed in ACPI, and I think it's actually an internal USB device... it's certainly possible, but it would need a bit of research.

Hrmm. On my old laptop I used to control the trackpad through synclient commands, but that doesn't seem to work on this. I get "Can't access shared memory area. SHMConfig disabled?" even though I've enabled SHMConfig in my xorg.conf.

[WillW]

Will give some consideration to supporting 'plug-ins' to allow expansion to cope with anything, but given you'll be able to tell it what command to run in response to a keypress you could just write a script that does the function and call that script. I'll ponder whether there is anything to be gained by doing anything more complicated.

FYI, have started the project - had a bit of a session last night/this morning (its great to be able to code in bed - yet another wonderful thing about the eee). Basic osd done, retireving of key bindings from config file. Vague roadmap:
Putting in the scripts for the standard commands (volume, wifi toggle etc)
Setting up proper subprocess/spawn a new thread style launching for running arbitrary commands

Should be done tonight/tomorrow. Will get us to the same stage we're at at the moment, with the addition of a built in osd, and a separate config file for the keymappings. Will probably then make it available for testing while I do the next bit:

GUI to set the keymappings (effectively a timesaving/easy way to edit the config file). Will know about the different key mappings on each eee, so it can call the buttons something human readable, and set sensible defaults. Can choose the various options from a dropdown box (wifi toggle, bluetooth toggle,4 way toggle, webcam toggle, vol up, vol down, mute, run command). This will probably take another couple of days, (more if I'm busy). Then, if thats pretty much working I'll learn about deb packaging.

[elmurato]

Yes :D Very good news! You`re the man, can`t wait to test it out. Will update the first post...

EDIT: Does anyone know how to edit the title of a thread? I didn`t find anything.

Edited by elmurato, 10 August 2008 - 09:03 PM.

[Pox]

WillW: progress so far sounds great! Oh how I love rapid development.

[Chonnawonga]

Quick report back on the trackpad, in case anyone's interested:

Asus isn't actually using a Synaptic pad; it's from ElanTech. Sadly, ElanTech doesn't offer Linux support and there hasn't been a whole lot of open source work on it (yet). However, there's an easy, brute-force way to turn it on and off. The pad simulates a PS/2 mouse, so you can switch it off and on with "sudo rmmod psmouse" and "sudo modprobe psmouse". From what WillW says, this should be easy to patch into his upcoming Python program. As for more advanced control of the trackpad (multi-touch settings, sensitivity, etc. etc.) there seems to be some useful work going on over here, but as it's a driver issue, it should probably be resolved by Adamm at the kernel level.

[WillW]

Normally being a C/C++ developer everyting takes way less time than I expect when working in Python, which makes the whole experience rather pleasant.

Pretty much there for part 1, just clearing up a couple of final issues (notably that any process launched is launched as root, which is a very bad thing if you want to run arbitrary programs. I can tell it to launch the program a any specific user, I'm just trying to figure out how to tell what user to launch it as).

[WillW]

Presumably to rmmod psmouse isn't going to affect any plugged in mice (which will be usb)? Will build it in in a moment. I could go for a bit of a google to find out, but can anybody summarise for me what the deal with webcam activation/deactivation is?

[elmurato]

Nice to hear that the work is going on ;)

Dont know if it works, but you could try it:

disable:

sudo rmmod uvcvideo
sudo echo 0 > /proc/acpi/asus/camera

enable:

sudo modprobe uvcvideo
sudo echo 1 > /proc/acpi/asus/camera

EDIT: Just tried it with my 701... "rmmod" fails. It says that the module is in use. But disabling the device is working (but my command is wrong, I had first to "sudo su" and then "echo 0 > /proc/acpi/asus/camera". Maybe you know my fault?)...

Edited by elmurato, 11 August 2008 - 04:50 PM.

[Chonnawonga]

Quote

Presumably to rmmod psmouse isn't going to affect any plugged in mice (which will be usb)?

Correct. (At least, it works for me.)

Edited by Chonnawonga, 11 August 2008 - 04:41 PM.

[jbooth]

Quote

As I said in the other thread, your ideas sounds very nice! Espacially the GUI. Unfortunately I have no experiences with python, so I can`t help you. If there`s anything else I can do for you please let me know.

Auto-detect: Hmm that`s a goog question. First I thought a simple "cat /proc/cpuinfo" would do it, but the 900A is coming, and thats a 900 with atom, so you can`t differentiate the models. But could you try this:

cat /proc/acpi/info

This gives me "version: 20070126"...

dmidecode | grep "Product Name"

I get two results, but they're both 901 (the model I have) rather than part of a date string (2007/01/26).