Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3278 - Add Gnome Power Manager to Arch

Attached to Project: Arch Linux
Opened by Eugenia Loli-Queru (Eugenia) - Monday, 03 October 2005, 18:02 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 24 January 2006, 12:06 GMT
Task Type Feature Request
Category Packages: Extra
Status Closed
Assigned To arjan timmerman (blaasvis)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Please add Gnome Power Manager to Arch, as it is close to impossible to get it working by simply compiling it ourselves or by using a third party pkg. ACPI stuff and Dbus/hal stuff need to be configured properly, and that's a bit mind-boggling atm. SuSE just added the app too, as Gnome Power Manager is the most popular third party utility today (according to gnomefiles).

I tried to compile it myself, but I couldn't get it compiled, because it tries to specifically find .la files to link with. I contacted the developer and told him about the lack of .la files on Arch, and he was at a loss, he doesn't know how to fix it.
This task depends upon

Closed by  arjan timmerman (blaasvis)
Sunday, 01 October 2006, 13:10 GMT
Reason for closing:  Implemented
Comment by arjan timmerman (blaasvis) - Monday, 03 October 2005, 20:14 GMT
i just compiled it working today, there wasn't any problem at all.
i used a PKGBUILD from the aur, try that.
Comment by Eugenia Loli-Queru (Eugenia) - Monday, 03 October 2005, 20:19 GMT
Please provide me a url with pkgbuild so I can try it. Maybe the errors I see is another bug..
Comment by Eugenia Loli-Queru (Eugenia) - Monday, 03 October 2005, 20:46 GMT
ok, I found that pkgbuild and used it and I STILL gives me the same errors:

libtool: link: cannot find the library `/usr/lib/libdbus-glib-1.la'

If I create that .la file it asks me, I still get the same errors for libdbus-la, libglib.la, libgobject.la and libopt.la. What is wrong here? Why is that app in particular asks me for .la files?
Comment by Jan de Groot (JGC) - Monday, 03 October 2005, 21:14 GMT
It's because you compiled many things yourself. Your system is full of libraries with .la files referencing the ones we removed from most official packages. If a library is not a KDE library, you should do the same.
To find out which library is the one causing problems:

grep -l 'libdbus-glib-1.la' /usr/lib/*.la
grep -l 'libdbus-glib-1.la' /opt/gnome/lib/*.la

Comment by Eugenia Loli-Queru (Eugenia) - Monday, 03 October 2005, 21:46 GMT
I have never installed dbus by myself. This is what I get btw:

eugenia@lc2430:~> grep -l 'libdbus-glib-1.la' /usr/lib/*.la
/usr/lib/libnotify.la

I *think* I had to install manually libnotify a few months ago in order to get Beagle to work. Anyways, it's fixed now, thanks.
Comment by Jan de Groot (JGC) - Monday, 03 October 2005, 21:53 GMT
Thanks for the bugreport, libnotify needs to get .la files killed :P
It's a miracle that gnome-applets actually compiles.

Edit: seems the system I tested had used my gnome 2.12 prerelease repository, the libnotify lib over there did contain .la files.
Comment by arjan timmerman (blaasvis) - Tuesday, 24 January 2006, 12:18 GMT
it will soon be added but it will go to unstable at first...
Suspend to ram and standby aren't too fool proof yet...

See http://bbs.archlinux.org/viewtopic.php?t=18179 for more info on it.
It still needs a lot of testing before i can say it is stable ;)
Comment by Eugenia Loli-Queru (Eugenia) - Tuesday, 24 January 2006, 19:02 GMT
We are talking about suspend-to-RAM, right? I wouldn't care less about suspsend-to-disk. For laptop users, suspend-to-RAM is what's important.
Comment by arjan timmerman (blaasvis) - Tuesday, 24 January 2006, 21:57 GMT
yeah suspend to ram, i have been working a day or two to get powersave of novell running on archlinux.
It works on my desktop just fine, but it probably will need some tinkering before the chance percentage will go up, i think it will be around 40% chance atm that it will work.

Even distro's like ubuntu still have issues with this, it will probably take a year or two before it is somewhat perfect
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 25 January 2006, 03:31 GMT
Doesn't work here:

[root@lc2430 Downloads]# /etc/rc.d/powersaved start
:: Starting Powersave Daemon [DONE]
[root@lc2430 Downloads]# hal-system-power-suspend
Cannot connect to powersaved. Is the daemon running? (dbus error)

(dbus and hal are all running btw). Also, this is a bit inconvenient to try to suspend the laptop through a command. It should do it automatically when closing the lid of the laptop.
Comment by arjan timmerman (blaasvis) - Wednesday, 25 January 2006, 03:45 GMT
hmmm strange... you could try running powersave -u ?
also i am not in favor of adding the suspend to ram, when closing the lid.
This is something the user himselft should configure, The main reason for this is far from every laptop works perfect with suspend to ram, it might crash your system and make you lose data. That's a bad bad thing.
Adding it to gdm and getting gnome-power-manager to work with this is probably a cleaner solution for now, until 99.9% of all systems do this right ;)
also i do not want my laptops to goto suspend to ram when i close them, i hate this in mac os X you can't turn this "feature" off :/
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 25 January 2006, 05:04 GMT
:: Starting Hardware Abstraction Layer [BUSY]
[root@lc2430 eugenia]# /etc/rc.d/powersaved start
:: Starting Powersave Daemon [DONE]
[root@lc2430 eugenia]# powersave -u
Cannot connect to powersaved. Is the daemon running? (dbus error)

HAL doesn't seem to load for some reason (i had to kill it). But the powersave deamon loads and then it says that the daemon doesn't run.

Regarding the lid thing: if you are not going to add it by default, at least please implement it and then create a /etc/acpi/acpi.conf file or something, where people easily can turn on/off things like this easily, maybe just by making a 0 to 1 or something.
Comment by arjan timmerman (blaasvis) - Wednesday, 25 January 2006, 05:13 GMT
well you need hal and dbus running, also your user needs to be in the "power" group.
i am not in charge of the acpi thing, i might look into it one day. It is far for high priority for me.
all other things in life also eat my time, school, work etc...
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 25 January 2006, 05:33 GMT
ok, i rebooted and this time hal, dbus and powersave are loaded. Now, it DOES go to sleep. BUT, it never wakes up properly. The disks and cpu restart for example (i can hear them coming back to life), but the screen never comes up. I am using an ATi 9000 on this laptop using the XOrg drivers at 1440x1024x16bit. I tried suspending from both inside X11 and framebuffer (vga=773), but none comes back to life.

BTW, here is a script I used to use in the past, it might give you some clues how to turn on the screen back on and integrate it to your scripts:

#!/bin/sh

echo "Going to sleep at `date`"
##Let's go to Terminal 1 (Ctrl+Alt+1)
echo "* chvt 1"
/usr/bin/chvt 1
#Save Video State
echo "* save vbestate"
/usr/sbin/vbetool vbestate save > /etc/acpi/vbestate
echo "* writing to /sys"
hdparm -y /dev/hda
echo -n "mem" > /sys/power/state


sleep 4


hdparm -a1024 -c3 -d1 -m16 /dev/hda
echo "Back from sleep at `date`"

##Restore the state of the Video
echo "* restore vbestate"
/bin/cat /etc/acpi/vbestate | /usr/sbin/vbetool vbestate restore

##Lets restore the clock
echo "* restore clock"
/sbin/hwclock --hctosys

##Lets get back to Xorg (Ctrl+Alt+1)
echo "* chvt 7"
/usr/bin/chvt 7
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 25 January 2006, 08:00 GMT
I just tried the scripts on my other laptop, a PII-mobile 333 Mhz with a Neomagic 2.25 MBs of VRAM and 128 MBs of RAM. The scripts worked better on this laptop. The laptop went to sleep and it managed to wake up on both the framebuffer and under X11. HOWEVER, the networking was not restored and any attempt to reload the network service it would not work (PCMCIA orinoco WiFi card on a WEP-encrypted network). I reloaded the pcmcia and tried to reload the networking service manually to no avail. The little light on the WiFi orinoco card would stay ON but it wouldn't handshake with my hotspot as it usually does.

So, at that older laptop, it works better than with the ATi card on the newer one, but still, something goes wrong during the wake up...
Comment by arjan timmerman (blaasvis) - Wednesday, 25 January 2006, 09:34 GMT
well i remerber reading something about newer frglx can suspend, so you probably will have to update these.
the networking thing, can you please send me your /var/log/suspend2ram.log ? probably the orinoco driver also needs unloading on suspend to ram and loading on resume.
Comment by Eugenia Loli-Queru (Eugenia) - Wednesday, 25 January 2006, 09:44 GMT
I am using the standard XOrg drivers from Arch. If the new ones are better, please update the packages. I won't mess with X drivers again all by myself. ;-)
I will send you the log tomorrow, I am on the powerbook atm. Thx.
Comment by Eugenia Loli-Queru (Eugenia) - Thursday, 26 January 2006, 03:37 GMT
Here you are, this is the log of the newer laptop that its gfx card doesn't wake up. I will get the log from the other, older, laptop later.
Comment by Eugenia Loli-Queru (Eugenia) - Saturday, 28 January 2006, 01:40 GMT
Here you are, the second log, from the older laptop where the gfx wakes up, but the network never comes back.
Comment by arjan timmerman (blaasvis) - Saturday, 28 January 2006, 11:32 GMT
well new release commin up, for the gfx problem i add vbestate, but it seems the network problem is related to not reloading /etc/rc.d/network ....
Comment by Eugenia Loli-Queru (Eugenia) - Sunday, 29 January 2006, 23:11 GMT
No, it's not it, because i reloaded manually the service, and the card FAILS to connect, while it does have power and the driver is loaded. Here is the error message it produces on dmesg when trying to reload the networking after coming back from suspend2ram:
ADDRCONF(NETDEV_UP): eth1: link is not ready

Additionally, adding the vbetool was a good and bad choice at the same time. Now this old laptop continues to come back successfully from suspend when in X11, but when in vga=773 framebuffer on the command line the screen DOES NOT come back anymore. Before you added vbetool, the screen would come back in command line on this 333 mhz laptop no matter if i was in x11 or in command line. Now it comes back only when in X11. If a try to shut off the machine with "halt", the screen does come back about 2 seconds before the machine turns off. So there is something in last few services that are closing that brings video back to life.
Comment by arjan timmerman (blaasvis) - Sunday, 12 February 2006, 17:24 GMT
ok new version, try it and report back plz, it seem the prism54 was causing trouble.
also vbetool does no longer always turn off monitors it needs to be configured.
Comment by arjan timmerman (blaasvis) - Wednesday, 12 July 2006, 19:21 GMT
ok, this will need to wait some time, my system is somewhat broken.

Dead elco's so testing would unreliable, i hope to buy a new computer in a few weeks, if i get enough money ;)

Loading...