O2 Joggler Forum

When running Xubuntu 11.10 and checking the /proc/cpuinfo all of my Jogglers show "cpu MHz : 800.00". I've added thermal.psv=80 to grub and have verified that none of them have reached over 70 degrees using acpi -V (Which also shows all of the thermal set points; none of which have been hit).

Does anyone have any idea as to why Linux would force these into 800mhz mode instead of 1.33ghz?

Thanks for anyone's help!

Alright, even more confusing. Despite using the same USB stick to boot either device, acpi -V shows different set points for each joggler. Also, one joggler shows temps as always 26.8 C wheres the others are all in the 60s-70s.

Wow, I need to collect my thoughts and make ONE post!

Furthermore, I've disabled ondemand in linux and that has no changed a thing. I've briefly seen a blip (couple minutes) on ONE joggler where it went to 1333.00 but then went back down to 800 afterwards. Load is still low and temp is under 60 C.

Even "weirder" though is that running windows XP this joggler is at 1.33 at all times. I've confirmed this with cpu-z.

So what you're saying is: Windows > Linux ;P

Grrr, even more. cpufreq-info shows hardware limit 800 to 1.07 but no higher on this ONE joggler. I've even modified the max and min thresholds as well as tried "over clocking" using cpufreq-set but it never rises above 800mhz

I think disabling acpi will be my only choice. I suspect this joggler is "Broked"

Mevi wrote:So what you're saying is: Windows > Linux ;P

Then get that new build of XP out!

heh heh. Tomorrow, I think.

i have cpu frequency scaling enabled on my builds (ondemand governor). there is no problem with that. why should it be clocked at 1.3ghz if it is mostly idle. if you want to force the cpu to be clocked at max speed, use the performance governor, or disable acpi-cpufreq module.

in regards to you saying you disabled ondemand, i can only think you did it wrong if the cpu is still scaling. note the joggler cpu has hyperthreading, so the cpu appears as having two cores.

Thanks for the reply Buzz. The issue is that the CPU NEVER scaled. The MAX setting for cpu shows as 1.07 vs the 1.3 of my other joggler (though dmesg identifies them both as 1.33Ghz processors) and it never scaled over 800mhz running xbmc or anything processor intensive. My other joggler scaled appropriately after modifying some settings using cpufreq-set.

I think you must be mistaken. i cant say for sure why you are getting max frequency limited on one joggler (its not impossible there are some hardware differences perhaps, or you are misinterpreting the information), but the scaling does work . what is the output of

sudo cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq

and for example run cpuburn or something and then do in a terminal

sudo watch cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq

joggler@joggler:/sys/devices/system/cpu/cpu0/cpufreq$ cat cpuinfo_max_freq
1068000
joggler@joggler:/sys/devices/system/cpu/cpu1/cpufreq$ cat cpuinfo_max_freq
1068000

Idle:
sudo cat cpuinfo_cur_freq
800000

Cpuburn running for 6 minutes:
sudo cat cpuinfo_cur_freq
800000

cpufreq-info showing wrong maximum:
hardware limits: 800 MHz - 1.07 GHz
available frequency steps: 1.07 GHz, 1.07 GHz, 800 MHz

acpi -V showing possibly bad thermal sensor?? :hermal 0: ok, 26.8 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 85.0 degrees C
Thermal 0: trip point 1 switches to mode passive at temperature 95.0 degrees C
Thermal 0: trip point 2 switches to mode active at temperature 55.0 degrees C
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10

might be worth seeing the output of dmesg compared to the other joggler. perhaps it does have some sort of fault then or it is of different build. and the other joggler, that scales properly? (as I read before that scaling wasn't working on any of yours). also output of lsmod, and lspci -v, and dmidecode. its also possible it has a corrupt efi, and as such acpi is broken, which could also cause this. I had efi corruption (non booting joggler in my case), and had to hotswap the efi and rewrite it (in your case you dont need to hotswap since the machine boots and could dump and compare the efi with your other joggler(s), check on the wiki for obtaining a dump).

manxam wrote:joggler@joggler:/sys/devices/system/cpu/cpu0/cpufreq$
Cpuburn running for 6 minutes:
sudo cat cpuinfo_cur_freq
800000

ps, did you run this after running cpuburn for 6 mins? it should be run during cpu burn. doesnt need to be run for 6 mins. just run cpu burn in the background and check the cpu freq. as soon as cpu burn is quit the processor would clock down, so it makes no difference the amount of time it is run for. ps rather than cding so a single folder use the commandlines i gave which will output both temps. also use "watch" with an update frequency of 0.5 seconds etc so you can better check if the value changes.

Sorry Buzz, throttling/scaling wasn't working on any of the devices as, for some reason, on demand wasn't being loaded. Also, as you state, the processor VERY quickly returns to 800mhz so I wasn't seeing the speed change with the cat command.

Once I loaded ondemand and used watch during forced high-load I saw the scaling on all but one device.

On this device cpuburn was running for 6 mins as I was watching the thermal sensor to see how it responded (which it didn't -- still 26.8 degrees).

I've attached a dmesg via paste bin of the "broken" joggler: http://pastebin.com/dvJBi8n3

EDIT: Here's a dmesg of a working joggler: http://pastebin.com/mtqQ2iaL

I did a diff and there are a tonne of differences though i'm not sure what do read into it..

Thanks for your help Buzz!

I've attached a colourized diff file showing the differences. Broken Joggler on left and Working Joggler on right.

The differences are: broken joggler has no thermal capabilities and missing lots of acpi code.

Ideas?

DIFF HERE: http://dl.dropbox.com/u/11778503/joggdiff.htm

corrupt efi is my likely guess.

Can one reflash EFI on these devices?

Edit: found the debricking efi info on the wiki. I'll dump from one Joggler and write to another see what happens!

Cheers!

yep.. see http://www.jogglerwiki.com/wiki/Recover ... ricked_EFI - first of all before writing it. dump both the good efi and the badefi and have a look to make if one looks bad or blank in places or just is a different version. perhaps post them up here also and i can compare with my own efi dump.

Thanks for all of your help Buzz. It was a bad EFI and I reflashed it using an EFI dumped from another. Not only did scaling start working but also the thermal sensor.

Cheers!

excellent. glad to be of help. I think it is only fair I mentioned now in reply to earlier.. that actually this thread has proved that

linux > windows