On Fri, Jul 10, 2009 at 09:08:53PM +0200, Bastian Blank wrote:
Thanks for your quick response,
> This means that nvclock access some address space, which have no valid
> definition. As it runs with root priviledges, it may do so via /dev/mem.
> Access to PCI resources is now handled via
> /sys/b
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-2
Severity: normal
As to be seen below, this behaviour still continues after upgrading to latest
version 2.6.30-2
- every run of nvclock results in a bunch of logfile entries complaining about
'freeing invalid
memtype'
Regards,
Edgar
-- Pa
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-1
Severity: normal
As my plain old NVidia graphics card operates its fan normally at full fan
speed, I use a small script to set fanspeed temperature dependent via 'nvclock
-f -F' once per minute. When using kernel 2.6.30-1-amd64, every script
Package: kernel-image-2.6.11-1-k7
Version: 2.6.11-7
Severity: normal
Hi there,
today I upgraded my system from the sarge kernel 2.6.8-2-k7 to actual
testing kernel 2.6.11-1-k7 and recognized after rebooting and
reinstalling nvidia graphics driver that the special keys on my IBM
Rapid Access III k
4 matches
Mail list logo
