You are not logged in.
Dammit your right... From acpid's website:
ACPID is a completely flexible, totally extensible daemon for delivering ACPI events. It listens on a file (/proc/acpi/event) and when an event occurs, executes programs to handle the event. The programs it executes are configured through a set of configuration files, which can be dropped into place by packages or by the admin.
Now I need to find something else!
Offline
Dammit your right... From acpid's website:
http://acpid.sourceforge.net/ wrote:ACPID is a completely flexible, totally extensible daemon for delivering ACPI events. It listens on a file (/proc/acpi/event) and when an event occurs, executes programs to handle the event. The programs it executes are configured through a set of configuration files, which can be dropped into place by packages or by the admin.
Now I need to find something else!
I wouldn't worry about it so much yet...seems like there is still demand for this
Offline
Their seems to be a branch of acpid with netlink support:
http://www.tedfelix.com/linux/acpid.html
http://sourceforge.net/tracker/index.ph … tid=407341
Offline
I have uploaded to AUR the official extra/acpid packages updated to use the netlink branch from the previous links. See here:
http://aur.archlinux.org/packages.php?ID=23827
Edit: changed pkg name
Last edited by big_gie (2009-02-11 20:18:20)
Offline
Oh, way cool!
Now I can switch it off in the kernel again!
Thanks!
Offline
It seems AUR can't have pkgbuild with same name as official ones. I moved the acpid to acpid-ted1:
http://aur.archlinux.org/packages.php?ID=23827
Offline
Running the new acpid as "sudo acpid -n -d -f" does not detect the keys... Using 2.6.28.4-ARCH
Need more testing...
Offline
I have updated the buttons-eee901 package...still far from being as good as acpi-eee-generic, but definitely an improvement
Help appreciated (where are those dbus-python hackers when you need them )
Offline
Thank you for acpi-eee-generic. I like the kde4-integration. Nice work.
And maybe the wiki-article should be updated, because of the aur-link of acpi-eee.
And this "rt2860sta" hint isn't necessary anymore, because the PKGBUILD-file was updated.
Last edited by ChemBro (2009-03-05 18:18:45)
Offline
many thanks Big_gie , for your work in the acpi for my 1000h!!!!!
Offline
@eljoprin I'm glad you like it
@ChemBro I'll check the wiki some day... still quite busy. When you say rt2860sta is not needed anymore... why? Blind is providing it by using the staging driver patch. This patch should be the same as the rt2860sta package from AUR... If you don't use Blind's kernel, then you need it...
Offline
When you say rt2860sta is not needed anymore... why?
Because this driver is already in the vanilla-kernel integrated. (now)
Another question: I had the EEE PC Interface/On Screen Display with the Arch Linux EEE packages from robertek (I think, it was the OSD from Asus). Do you know, how I can enable them on my eee with your acpi-eee-script? I saw KDE-Notification-Support and the one for Gnome, but the EEE PC OSD would be nice (and it worked faster, at least for me, in terms of manipulating the volume for example).
Offline
big_gie wrote:When you say rt2860sta is not needed anymore... why?
Because this driver is already in the vanilla-kernel integrated. (now)
I'm pretty sure it is not. The rt2860sta driver is crappy as hell. There is no way kernel devs would include it in the kernel. I might be as a staging driver though...
Another question: I had the EEE PC Interface/On Screen Display with the Arch Linux EEE packages from robertek (I think, it was the OSD from Asus). Do you know, how I can enable them on my eee with your acpi-eee-script? I saw KDE-Notification-Support and the one for Gnome, but the EEE PC OSD would be nice (and it worked faster, at least for me, in terms of manipulating the volume for example).
I did not included the OSD from asus because I did not liked it. You have access to the code, so I've taken a look. It is badly written. Basically, it is not only listening to acpi events (by connecting directly to /.../events) but its also changing some stuff (the volume I think) when that should go in your acpi script. Why an OSD program should change the volume??? I don't like it. And the OSD is uggly.
So if you want to take a peak at the code and patch it, your free to go. I did not wanted to go that way. I prefer using tools which already exists, instead of reinventing the wheel (in a bad way).
Offline
ChemBro wrote:big_gie wrote:When you say rt2860sta is not needed anymore... why?
Because this driver is already in the vanilla-kernel integrated. (now)
I'm pretty sure it is not. The rt2860sta driver is crappy as hell. There is no way kernel devs would include it in the kernel. I might be as a staging driver though...
The only thing I know is, that I didn't installed rt2860sta (or anything like this), but only kernel 2.6.29 and my wireless-lan works without any problem.
So if you want to take a peak at the code and patch it, your free to go. I did not wanted to go that way. I prefer using tools which already exists, instead of reinventing the wheel (in a bad way).
I would, if I could. I'm not a developer or something like that, only a user. I only dislike that it takes so long to change the volume, because of the slow notification system (also it, I dunno how to say, but my screen is full of notifications, if I change the volume).
Offline
ChemBro wrote:big_gie wrote:When you say rt2860sta is not needed anymore... why?
Because this driver is already in the vanilla-kernel integrated. (now)
I'm pretty sure it is not. The rt2860sta driver is crappy as hell. There is no way kernel devs would include it in the kernel. I might be as a staging driver though...
I think that ChemBro is correct here. The Arch stock kernel has the staging drivers compiled, as far as I saw. This is why I have updated my kernel package to 2.6.30-rc's. There is no good point in competing with the stock kernel - even though it is not optimized.
Plus - it gives me the opportunity to play with NILFS2, which has been a really nice experience on the 'slow' 901 SSD (some tweaks needed, though). ext4 without journal works well, too (on the 'fast' SSD).
Nevertheless, I copy big_gie on the reluctance to use ASUS OSD stuff. Looking at bad, untransparent and undocumented code is a pain in the neck, ChemBro - it seems you don't have much experience with something like that.
Wasn't there a notify parameter that tells it to only have one notification open at the same time?
Kind regards,
Blind
Offline
Wasn't there a notify parameter that tells it to only have one notification open at the same time?
Which OSD this applied to? I'd like to know if there is such an option, at least for KDE notification.
Just before I switched to KDE on my eee, I was using XFCE 4.6. I installed an svn pre-release and I had the same "problem" of notifications piling up. But when 4.6 came out, I dumped the svn packages for the official Arch packages, and the notifications changed, by default. Instead of piling up, they appeared on top of each other, replacing the previous one. I was really glad it changed to that behaviour. But then I switched to KDE...
Offline
Hello. I have built zen-kernel-2.6.29 for eeepc 901. I have applied gregkh staging patch and jumpy cursor patch. The touchpad works just fine and wireless seems alright, although I have not tested it for WEP/WPA. The eee module (for fsb management) has been built as a module and it works fine on my eee pc (still running older bios). It feels just like the original robertek kernel. If you guys are interested,
arch package:
http://zen-kernel-eee-901-arch.googleco … pkg.tar.gz
sources and PKGBUILD:
http://zen-kernel-eee-901-arch.googleco … ces.tar.gz
Offline
ChemBro - it seems you don't have much experience with something like that.
As I said, I'm only user, not developer. I don't understand the code. And I like the EEE-OSD, the look and feel, better than the piling notification-system.
I'm using libnotify and not knotify (or how it is called), because the kde(4)-version is a lot slower (and also piling). Again, for me, EEE-OSD looks better for me, I have no idea, how it works. The only thing I knew was: it worked, but not how.
Offline
The program "acpid" listen to the button you press, and the handler script will interpret these events with something to do. The script can do whatever you want. It will mainly launch programs. This program can be an OSD, like knotify or libnotify.
My work has mostly been on the mapping of special keys to a certain function. This is what the handler script... handles. As a plus, I added the possibility for OSD. But the OSD is only superficial: it does not affect the mapping of keys to programs.
The Asus OSD program is mainly for OSD, but then it also reacts to some keys and modify the machine state, which is IMO bad. And OSD should only OSD, nothing else.
Now if you find another OSD program that simply popup an image and some text, let me know. Maybe I can integrate my package with it. You can also change the duration of the OSD, or disable it completely.
Offline
Hello. I have built zen-kernel-2.6.29 for eeepc 901. I have applied gregkh staging patch and jumpy cursor patch. The touchpad works just fine and wireless seems alright, although I have not tested it for WEP/WPA. The eee module (for fsb management) has been built as a module and it works fine on my eee pc (still running older bios). It feels just like the original robertek kernel. If you guys are interested,
arch package:
http://zen-kernel-eee-901-arch.googleco … pkg.tar.gzsources and PKGBUILD:
http://zen-kernel-eee-901-arch.googleco … ces.tar.gz
PLEASE, iḿ very interested in the module eee, to control the fsb, but i have my own custom kernel, because i use extra hardware which is unsupported (the modules are not compiled) on zen kernel, so, can you tell where i can found the eee module???
many thanks!!!
Offline
PLEASE, iḿ very interested in the module eee, to control the fsb, but i have my own custom kernel, because i use extra hardware which is unsupported (the modules are not compiled) on zen kernel, so, can you tell where i can found the eee module???
many thanks!!!
You can get the code for eee here:
http://code.google.com/p/eeepc-linux/downloads/list
if you are using newer kernel (2.6.29), you can change eee.c in the following way:
line: 399
- eee_proc_rootdir = proc_mkdir("eee", &proc_root);
+ eee_proc_rootdir = proc_mkdir("eee", NULL);
line: 433
- remove_proc_entry("eee", &proc_root);
+ remove_proc_entry("eee", NULL);
line: 442
- remove_proc_entry("eee", &proc_root);
+ remove_proc_entry("eee", NULL);
Offline
thanks ashishp, i've compiled the version 0.2 of eee, changing the lines you said, but when i load the module it says : segment violation (in spanish-> violacion de segmento), and the folder /proc/eee not appear, so i think that the module is loaded, but not working.. ( if i try to rmmod eee, it says: busy..)..
so, i download the version 3.1 (its a little unofficial), compiled, and that module loads very well, and generates the folder /proc/eee/ with all the files (fsb, fan....)..
The problem is that if i cat /proc/eee/fsb it says 0 0 1, (it is not normal), ive searched google, and recompiled my kernel with the module i2c_i801, but, the same result with both modules loaded, any idea?
********
i've read that eee module verion 0.2 its not compatible with 1000h so, i need to use the asus_eee!.. but my problem still is there!
Last edited by eljoprin (2009-05-01 18:35:53)
Offline
Are you using older bios? The newer bios is not compatible. Have you compiled eeepc_laptop module ? It seems eee depends on eeepc_laptop.
Offline
please, tell me the correct bios!!! i´m using the latest bios avaliable... and yes i have the eeepc_laptop module!
many thanks!
Last edited by eljoprin (2009-05-02 06:16:05)
Offline
see the discussion in this thread for information on bios:
Offline