fit-IoT Users Forum

On recent kernels, the old max_cstate parameter might have no effect. I have been using processor.max_cstate=2 for some time. Now, on 2.6.37, I use processor.max_cstate=2 processor_idle.max_cstate=3 intel_idle.max_cstate=3 (yes, this is overkill) This is related to a new config option that I selecte...

processor.max_cstate=2

seems to work for me

kernel is 2.6.31-rc8-rt9-00499-ge8e8f56

I don't know. From what I could find out, scaling and C-states don't seem to depend on each other. Did anyone ever try processor.max_cstate=2 ? Update: scaling seems to work for me, with cpufreqd and fixed configuration (eliminate all unneeded rules, use ondemand governor, and see in syslog how tric...

I'm now trying processor.max_cstate=1 as boot parameter. It seems to work so far (2 hours). For this, I have compiled "Power management..." / "ACPI" / "Processor" (CONFIG_ACPI_PROCESSOR) into the kernel (not a module). There is a way to supply the parameter to the module (no recompiling), but I didn...

With vnc4server (not vncserver), everything seems to work. I tried shift, numeric, non-alphanumeric and national characters. Even vino-server, when started from a vnc4server+gnome, seems to work. I connected vinagre to tightvncserver before, and it had the same keyboard problems, so I think it is se...

I plan to use applications for which ssh is not sufficient. Not only national characters, but also most non-alphanumeric characters are garbled. When connecting to vino (gnome desktop sharing), shift is filtered out, everything is converted to lowercase. In Gentoo, and (years ago) LFS, vnc to vnc co...

I don't intend to use a monitor, so I installed tightvnc and tried vino-server (remote desktop). The keyboard on my laptop does not have "us" layout, and (very unusual for VNC) the keys go through garbled and filtered. With plain tightvnc, all keys are garbled, with gnome and vino-server on top of i...