You are not logged in.
hi,
I really must say that you guys do marvelous job with this kernel
I only have two questions concerning battery issues. First - is there some kind of battery manager that would show me how much time i have left or at least percentage of charging?.
I'm running XFCE4 as my desktop environment and using xfce4-battery-plugin as the battery applet in my system tray.
Offline
dr.lulz wrote:hi,
I really must say that you guys do marvelous job with this kernel
I only have two questions concerning battery issues. First - is there some kind of battery manager that would show me how much time i have left or at least percentage of charging?.I'm running XFCE4 as my desktop environment and using xfce4-battery-plugin as the battery applet in my system tray.
Oh, I'm using Openbox, is there such program for OB ?
Offline
Oh, I'm using Openbox, is there such program for OB ?
I'm using fluxbox and I run gnome-power-manager to monitor the battery.
I think I may start a thread in the laptop subforum to see what other folks are running on their eee's. I might get an idea or two
Smarter than a speeding bullet
My Goodreads profile
Offline
Thanks. Why are we using 100 50 1 as performance FSB? My eeePC starts with "105 50 1" as it's default values.
Good question. I suggest "100 50 1" because a) that's what MY laptop starts with (go figure), and b) according to some tests/analyses Robertek and I have run, that first number roughly translates to the percentage of rated CPU speed. Since the 901s come with a 1600MHz CPU, 85 would downclock to 1360 MHz (approx), whereas 105 would overclock to 1680 MHz. 100 is full rated CPU speed of 1600MHz. This only seems to hold true for 901s, and when the divisor (second value) is 50.
I'd be interested in any tests others perform that analyze the results of setting the FSB speed, both in terms of CPU speed, performance, and battery life. I started working my way through the eee.c source code (the module was originally written for the 701, is labelled "experimental", and isn't being kept up, AFAIK), but it was mostly gibberish to me, as I spend most of my waking hours up in the application layer.
EDIT: I have no idea how Speedstep changes the overall picture. Robertek and I started testing CPU speeds with different Speedstep settings, but didn't come up with any hard-and-fast conclusions (one of the claims of the Speedstep technology is that it's on-demand, so it could be our testing environment wasn't completely controlled). Setting the FSB speed, on the other hand, makes an immediate, measurable, and predictable difference. There's a body of opinion out there that maintains Speedstep is more snake-oil than a useful tool. I don't know enough to make a call on that question.
Last edited by chori (2008-10-16 18:56:25)
Offline
hi,
I really must say that you guys do marvelous job with this kernel
I only have two questions concerning battery issues. First - is there some kind of battery manager that would show me how much time i have left or at least percentage of charging? And second - do I have to load laptop-mode module or does the "eee" module handle all the stuff related to laptop-mode?oh and by the way- I'm using zen-eee901 kernel, is there a difference with the git version? or is it only a test version from which the working stuff is transferred to zen-eee901 kernel?
EDIT- forgot to ask about Loading Modules...
when i boot kernel i have FATAL errors with modules :FATAL: Module snd_page_alloc not found FATAL: Module snd_pcm not found FATAL: Module snd_timer not found FATAL: Module snd not found FATAL: Module snd_hda_intel not found FATAL: Module soundcore not found
and i don't know why... i have alsa installed and configured...
sorry for my english.
Don't load any of the ALSA modules in your rc.conf MODULES list. They're compiled into the zen-eee901 kernel.
The zen-eee901 package is based on the latest STABLE version of the zen 2.6.26 kernel. The git release is based on the latest (more or less) release candidate version of the zen 2.6.27 kernel. What this means in real life: zen-ee901 is (theoretically) more stable, but without any of the bug fixes or optimizations in the 2.6.27-rc* branch. The git version is more cutting edge, with all that implies.
Offline
As I announced before, the zen-eee901-git is now non-rc 2.6.27-zen1. I will do some merging to stable kernel branch this weekend, to have stable 27.
Offline
Gringo wrote:dr.lulz wrote:hi,
I really must say that you guys do marvelous job with this kernel
I only have two questions concerning battery issues. First - is there some kind of battery manager that would show me how much time i have left or at least percentage of charging?.I'm running XFCE4 as my desktop environment and using xfce4-battery-plugin as the battery applet in my system tray.
Oh, I'm using Openbox, is there such program for OB ?
I use conky, and there have anything system related, so even the battery status and remaining time.
Offline
1. Thanks for solving my sound problem, "alsa" was really missing in rc.conf.
2. Is there any way to use all the nice hints about the FSB on an 1000H? Since the module eee doesn't seems to run on my machine, I alwass get a segmentation fault.
3. On an 1000H the hot Fn+F7 is to turn off the backlight but I get "Volume On". Is there a way to set this right?
When I press Fn+F7 I get in the everything.log this message:
Oct 16 23:45:41 proton logger: ACPI hotkey undefined: ATKD 00000016 00000005
Last edited by tehabe (2008-10-16 21:48:41)
Offline
Is there any way to use all the nice hints about the FSB on an 1000H? Since the module eee doesn't seems to run on my machine, I alwass get a segmentation fault.
Short of rewriting eee.c, I think you're out of luck. Have you googled FSB and 1000H, to see what others have done?
3. On an 1000H the hot Fn+F7 is to turn off the backlight but I get "Volume On". Is there a way to set this right?
This key event is hard-coded to generate a volume toggle icon in the asusosd binary distributed with acpi-eee901. Ideally, asusosd would be written to make the icons that get displayed when a key is pressed configurable at runtime; that wouldn't be a very difficult task, but it's not one I'm going to tackle anytime soon. You can edit the key events in /etc/acpi/eee/eee-handler.sh to execute any command you want when that key is pressed, however.
Offline
I'm using the zen-eee kernel right now, would it be too much of a problem to add joystick drivers to the next release? I can't be the only eee user that plays games on it, especially emulators.
Offline
tehabe wrote:Is there any way to use all the nice hints about the FSB on an 1000H? Since the module eee doesn't seems to run on my machine, I alwass get a segmentation fault.
Short of rewriting eee.c, I think you're out of luck. Have you googled FSB and 1000H, to see what others have done?
If I had the knowledge to write eee1k, I would like to try. But I don't habe the knowledge. :-(
This key event is hard-coded to generate a volume toggle icon in the asusosd binary distributed with acpi-eee901. Ideally, asusosd would be written to make the icons that get displayed when a key is pressed configurable at runtime; that wouldn't be a very difficult task, but it's not one I'm going to tackle anytime soon. You can edit the key events in /etc/acpi/eee/eee-handler.sh to execute any command you want when that key is pressed, however.
Most keys work like they should do, well the special keys above the keyboard don't and F9 doesn't succesfully start htop.
Offline
I use conky, and there have anything system related, so even the battery status and remaining time.
could you post the script for remaining time and battery status for conky, please?
Offline
inf wrote:eee-kernel901 isn't maintained anymore i think, so use zen-eee
Is that true ? I still use eee-kernel901 and waiting for 2.6.27. Will it be release ?
ighea sold his EEE, so he won't be updating the kernel anymore. Waste of time like he said it to me
Offline
ik0 wrote:inf wrote:eee-kernel901 isn't maintained anymore i think, so use zen-eee
Is that true ? I still use eee-kernel901 and waiting for 2.6.27. Will it be release ?
ighea sold his EEE, so he won't be updating the kernel anymore. Waste of time like he said it to me
Waste of time updating the kernel? Or the EEE is a waste of time?
Depends on how you define "waste", I guess... but time, yes, there's definitiely a lot of that wasted, er, spent on it.
I'll update the wiki to make it robertek-centric. Thanks, @ighea, wherever you are, for making the initial kernel from which the zen-eee901 is derived.
Offline
When I press Fn+F7 I get in the everything.log this message:
Oct 16 23:45:41 proton logger: ACPI hotkey undefined: ATKD 00000016 00000005
You'll need to edit /etc/acpi/eee/eee-handler.sh to execute the proper command when this key is pressed. Make sure you make a backup copy of eee-handler.sh after you edit it, since it will get overwritten the next time you update acpi-eee901.
Last edited by chori (2008-10-16 22:18:07)
Offline
tehabe wrote:When I press Fn+F7 I get in the everything.log this message:
Oct 16 23:45:41 proton logger: ACPI hotkey undefined: ATKD 00000016 00000005
You'll need to edit /etc/acpi/eee/eee-handler.sh to execute the proper command when this key is pressed. Make sure you make a backup copy of eee-handler.sh after you edit it, since it will get overwritten the next time you update acpi-eee901.
I will update that in next release, it seems like there will be no collision with eee 901.
Offline
Is anyone having trouble with the 1000H's wireless? I tried using zen-eee901 and zen-eee901-git (right now using 2.6.27-rc7-zen3eee). iwlist shows networks, but I cannot connect to my WPA-encrypted network. I turned off encryption and it still would not connect. I tried using netcfg, manually setting the options with iwpriv, and creating the RT2860STA.dat file.
I noticed someone earlier in the thread was having the same problem (netcfg spitting out "Wireless association failed"), but I never saw a resolution after that. I'm using the same profile that works on another laptop (except I changed the interface to ra0).
Can anybody provide step-by-step instructions to get it to work? Thanks.
Offline
chori,
I think I read somewhere in a ASUS forum that it is best to do step the frequency and voltage up to the "normal" values before going into suspend. I was just on battery, implying low voltage / frequency and suspended. When trying to wake up, the computer didnt get back to X.
I made the following changes to the fsb.sh, after which everything worked fine (suspend on battery):
autosuspend )
if [ $AUTO -eq 0 ]
then
exit 0;
fi
getfreq > $statefile || exit 1;
VOLTAGE=$NVOLT
if [ $FREQ -lt $HIPERF ]
then
stepup $FREQ $HIPERF
else
stepdown $FREQ $HIPERF
fi
;;
Had to put HIPERF=105 (on my machine).
Cheers,
Blind
Offline
chori,
I think I read somewhere in a ASUS forum that it is best to do step the frequency and voltage up to the "normal" values before going into suspend. I was just on battery, implying low voltage / frequency and suspended. When trying to wake up, the computer didnt get back to X.
I made the following changes to the fsb.sh, after which everything worked fine (suspend on battery):autosuspend ) if [ $AUTO -eq 0 ] then exit 0; fi getfreq > $statefile || exit 1; VOLTAGE=$NVOLT if [ $FREQ -lt $HIPERF ] then stepup $FREQ $HIPERF else stepdown $FREQ $HIPERF fi ;;
Had to put HIPERF=105 (on my machine).
Cheers,
Blind
Thanks. I'll update the FSB script to include that change.
Offline
could you post the script for remaining time and battery status for conky, please?
Hi, look hat the default conky script in /usr/share/conky/... (hope it's right, not on my eee now) or the manpage of conky.
its something like $battery_percent i think.
Offline
dr.lulz wrote:could you post the script for remaining time and battery status for conky, please?
Hi, look hat the default conky script in /usr/share/conky/... (hope it's right, not on my eee now) or the manpage of conky.
its something like $battery_percent i think.
I will post my config later, I have my eee home now.
Offline
I have a problem with the new ACPI package and hibernation. I can get into hibernation mode without problems. I'm not getting back to my X console automatically, though. When I press CTRL+ALT+F7 to go to the X console I get back, but going to virtual terminal 1 results in getting back to X console (virtual terminal 7) again. It is only then that my brightness settings I had before going into hibernation mode are restored.
EDIT: Problem solved. eee.conf was updated again. Scripts are using fgconsole for getting the X console number, rather than hardcoding it in eee.conf...
Last edited by Gringo (2008-10-17 14:01:55)
Offline
I ended up after the last update with my sound not working anyore. The device is correctly identified and if I use alsaconf it configures it, but then tells me that there is no device found. Any suggestions? Alsa was starting fine before the update. lspci shows the soundcard.
Offline
I have a problem with the new ACPI package and hibernation. I can get into hibernation mode without problems. I'm not getting back to my X console automatically, though. When I press CTRL+ALT+F7 to go to the X console I get back, but going to virtual terminal 1 results in getting back to X console (virtual terminal 7) again. It is only then that my brightness settings I had before going into hibernation mode are restored.
EDIT: Problem solved. eee.conf was updated again. Scripts are using fgconsole for getting the X console number, rather than hardcoding it in eee.conf...
Hm... Seems like the problem persist. I have to manually get back to tty7 to get back to X
Offline
I ended up after the last update with my sound not working anyore. The device is correctly identified and if I use alsaconf it configures it, but then tells me that there is no device found. Any suggestions? Alsa was starting fine before the update. lspci shows the soundcard.
Are you referring to the latest update of the acpi-eee901 package?
Offline