Re: System monitoring tool for AMD64

On Thu, Mar 19, 2009 at 11:03:38PM +, T o n g wrote: > On Thu, 19 Mar 2009 15:40:11 -0700, Phillip Pi wrote: > > > Did you run sensors-detect as root/sudo before? Then, add the lines it > > detected. Here's mine: > > Thanks for the instruction, and the example

Re: System monitoring tool for AMD64

ensor = thermistor CPU Temp:+29.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUX Temp:+41.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor cpu0_vid: +1.350 V On Thu, Mar 19, 2009 at 10:35:17PM +, T o n g wrote: > On Thu, 19 Mar 2009 10:36:29 -0700, Phillip

Re: System monitoring tool for AMD64

On Thu, Mar 19, 2009 at 04:50:18PM +, T o n g wrote: > On Thu, 19 Mar 2009 15:29:54 +, T o n g wrote: > > > Thank you thveillon.debian for the comment, and Dave for the detailed > > explanation. > > > > . . . > > Having enabled my kernel ondemand cpufreq governor, . . . > > What are the

KVM switches (VGA+PS2) and stuck Scroll Lock key in Debian

Hello. I have two old Belkin OmniCube KVMs (2-ports and 4-ports using VGA and PS2) from 2000 or so between Windows and Debian/Linux boxes. In Linux/Debian, I noticed sometimes my xscreensaver will not start (stuck scroll lock confirmed with its debugging logs and the developer) and console/termina

Upgraded Debian packages this morning, and now Samba is broken (coredumping).

Earlier, I did an apt-get update and apt-get upgrade. Then, i noticed my Samba was not working in Windows XP Pro. SP3. Explorer said: "\\192.168.0.46 is not accessible..." I tried stopping, restarting, Samba, but it did not work. I investigated and found Samba coredumping: # ls -all /var/log/s