Not sure if it is a bug, but I have the experience twice when changing from Super Performance mode to Power Save Mode, system crash, and have to hold the power botton 8 seconds to reboot the machine...(EEEBUNTU NBR 3.0.01 on EEEPC 901)

Does the screen go crazy! Mine has done this twice when I have changed CPU mode, the screen becomes a mess of pixels and i have to reset. Now I just dont touch the CPU speed thing, I'm hoping a fix will appear soon.

On a seperate but related note, why isnt the CPU mode remembered for the next time I log on?

Does this happen when you're on battery power and not on external power ??

I have only tried it on battery, I will see what happens on AC tonight.

Reason I ask is because it's been reported before as a battery-only. May be a bug.

Moving to ACPI issues forum.

This has been covered in the forum a few times, the scaletest diagnostic should be able to tell you your scale threshold.

http://www.statux.org/wiki/index.php?ti ... _Utilities

I'm working on a new CPU module that will hopefully eliminate this.

Hi Fewt thanks for the response. Sorry to be a bit dim but why is this an issue for me in 3.0 and was not in 2.0 where I could swap between modes using eee-ctl (i think) and it didnt crash. As far as I can tell it has always happened jumping from Super Mode (which appears to be default) to powersaver.

If i run the diagnostic, what do I do with the information, post it here or use it to configure something on my eeepc?

What you can do is to first switch to reduced mode and then switch to powersave.

The reason for crash is not software I believe, it is reported that a dramatic change in FSB would crash your system. In super performance, the fsb is "100, 50, 1", it has high voltage and 100 as the front bus speed. And I believe in powersave, it is "85, 50, 0", low voltage and 85. I think you would try to avoid the situation that front bus change over 10 and at the same time change the voltage. So you should first use reduced performance and then powersave.

Scaling is coded to occur in increments of -1 from 100 to 85 with a .5 second pause between steps.

The issue is most likely the Eee doesn't support scaling back 15%, most do but a few (especially those with upgraded memory) don't.

Ahhh yes, the original Xandros would cycle between CPU settings and even then there was a quite a delay between the changes. That makes sense. Many thanks.

How do i get NBR3.0 to remember my preferred setting (powersave)?

It happens on both battery and external power.



No it makes no difference it still crashed even going to reduced mode first.

Got same problem here on my 901.. works perfectly in windows, so no hardware issue for sure..

Please run the scale test, or set the scale to 10 and see if it stops crashing.

I did something else, as i was setting up a multiboot between win xp pro, win 7 and eeebuntu, i ended up doing a reinstall, now when i boot the un-updated freshly installed eeebuntu, switching thru all three modes works flawlessly, even jumping from super to power save. I notice im booting a .11 kernel now and earlier with the fully updated one i was booting a .12 kernel.. May there be something new in the .12 that messes up the ACPI on the 901? or, is it that scaling is simply disabled in .11 kernel, so i dont notice the problem on that one? i tried to disable cpu scaling before i reinstalled, and that fixed the crashing issue...

try accepting the updated kernel now and see if the issue persists.... if it does u can easily boot back into the old kernel by hitting esc at the grub loading screen and selecting the desired kernel.

then you can uninstall the new one if u wish