GPU frequency scaling?

[arlenn]

Is this going to find its way into a linux driver at any point?

it would be really nice for us notebook people to get similar battery life in linux that we were experiencing with windows.

even if its just a modified "cool bits" that will only detune the card, any kind of power saving extension added to the divers would be great!

thanks

(and yes, i could just use cool bits, but i would be nice if there was no way to screw it up, and accidentally over clock coming back up to full power, maybe 3 presets, even if it is manual solution as a temporary stop-gap until something more dynamic could be added. ATI is doing it, its a not a very good implementation, but it is something)

[netllama]

1.0-9746 already provides a means to underclock mobile GPUs via the Coolbits option. See the driver README for more details.

Thanks,
Lonni

[arlenn]

Thanks for the help...

basicly i have two sliders, 2d, 3d? but what is a suitable detune? any change for the next version of the driver to have say 3 presets? so we may detune w/o thinking? like check boxed for max, med, min; and the detuning done that way?

does nvidia offer any info on what suitable detune values should be?

thanks for the quick reply.

[cellstije]

Originally Posted by netllama

1.0-9746 already provides a means to underclock mobile GPUs via the Coolbits option. See the driver README for more details.

Thanks,
Lonni

Lonni,

I just tried to use Coolbits to underclock a gf go 6200TC (ubuntu feisty).
It does not work. I modify the values (2d/3d) trough the sliders but, when i click apply, it just resets to the default values.

Moreover I notice on dmesg

[ 957.144000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 0 at 1:00.0] forgot to specify physical device; fix it!
[ 957.148000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 1 at 1:00.0] forgot to specify physical device; fix it!
[ 957.148000] **WARNING** I2C adapter driver [NVIDIA i2c adapter 2 at 1:00.0] forgot to specify physical device; fix it!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[ 1008.508000] NVRM: Xid (0001:00): 3, C 0000001e SC 00000002 M 00000184 Data dada9703
[ 1008.512000] NVRM: Xid (0001:00): 30, L1 -> L0

nvidia-bug-report.log attached

P.S.
nvclock works

c.

[netllama]

Are you using the latest BIOS?

[arlenn]

I think it worked for my 6600go, with ubuntu 6.10, but i would hardly call this a suitable solution in the long term. it really cant be that much work to modify the gui and add the look (if not identical funtion) of the 'power miser' features of the windows driver.

[cellstije]

Originally Posted by netllama

Are you using the latest BIOS?

Do you mean gpu bios?
I do not know where download it and how to update it.

There is a newer bios for the laptop (vaio fs115m) but it is only in windows format.
I do not have it installed...

If you believe that it is a motherboard bios issue i'll spend sometime to install win and do the update

cheers

c.

[netllama]

arlenn, the source for nvidia-settings is released under the GPL . You're welcome to make the modifications that you desire.

cellstije, I was referring to the system BIOS. I can't say for certain whether updating would help as I do not have your Sony notebook here.

Thanks,
Lonni

[cellstije]

Originally Posted by netllama

cellstije, I was referring to the system BIOS. I can't say for certain whether updating would help as I do not have your Sony notebook here.

Thanks,
Lonni

ok, I'll give it a try in the next few days

Cheers

c.

[arlenn]

you may be able to do it with a 'freedos' bootdisk instead of loading windows.

[cellstije]

Originally Posted by netllama

cellstije, I was referring to the system BIOS. I can't say for certain whether updating would help as I do not have your Sony notebook here.

Thanks,
Lonni

Lonni,

I updated the bios, but the situation got worse!
Not only the behaviour is the same (no gpu scaling) and same Xid in dmesg:

[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: os_map_kernel_space: can't map 0xe0008000, invalid context!
[  520.688000] NVRM: Xid (0001:00): 3, C 0000001e SC 00000002 M 00000184 Data dada9703
[  520.688000] NVRM: Xid (0001:00): 30,  L1 -> L0

But if I switch to a tty, it looks very weird: it has a green background - kinda 8bit gradient from light green in the bottom and dark green in the top.

Now?!?! Sould I re-install win and down grade the bios?!?!?

P.S.
I just rechecked the tty and it has anoder background color, grey on the sides and blue in the middle!!!

help anybody?

c.