On 04/17/2013 06:33 PM, King Beowulf wrote: > Yes, lm_sensors uses libsensors to expose sensor kernel modules to > various apps. Some apps don't use it and read the data directly from > /proc/* > > Make sure you have libsensors installed. It drives me nuts that Debian > and clones split packages into <name> and <name>-dev. Idiots.
man libsensors reports no manual entry for libsensors. Synaptic shows libsensors4 is installed but not libsensors4-dev. After installing libsensors4-dev I get a man page for libsensors, but that didn't change the output of lsmod. > >> NOTE: you do not usually run sensors-detect in a terminal with X active. >> Get thee to a proper command line! Didn't know about that. I'll have to try that. > >> Okay, I've done some googling, and found a few things. According to >> Gateway's web site[1], the motherboard in your box is an Intel >> D945GPBG1. > That mobo is a 945G chipset with ICH7- very common and very well Linux > supported, iirc. ICH7 is the I/O chip and should be similar to the ICH5 > and ICH9 I have floating around (I do mostly AMD style and Slackware...) > "lsmod" should show something similar to: > > Module Size Used by > lm85 14453 0 > hwmon_vid 2304 1 lm85 > i915 372988 1 > processor 23020 0 > thermal_sys 12122 2 processor,video > hwmon 1033 2 thermal_sys,lm85 > i2c_algo_bit 4543 1 i915 > i2c_i801 6952 0 > i2c_core 16454 6 i2c_i801, i2c_algo_bit, drm, \ > drm_kms_helper, i915, lm85 > > Now, "lm85" was detected by sensors-detect for my thermal chip, and I > added it via /etc/modprobe.d as it is not autodetected. You will have a > different one. "i915" for on-board video since this a small server. > The rest should be similar to yours. > > hwmon, processor (or something related to CPU), i2c_core (linked to > i2c_*) are absolutely essential. i2c_801 is for my mobo, there shodl be > something similar for yours. > > Now, note also that sensors-detect will try to load some modules, such > as "i2c-dev" and "cpuid" so these must be present in your kernel modules > package. Once everything is loaded, using the default config files, run > "sensors -s" ONCE as root (or *ugh* sudo) and then you can run "sensors" > to display all the goodies. I don't see the modules you listed. rsteff@Gateway-32-E-4500D:~$ lsmod Module Size Used by pci_stub 12550 1 vboxpci 22911 0 vboxnetadp 13328 0 vboxnetflt 27240 0 vboxdrv 252188 3 vboxpci,vboxnetadp,vboxnetflt vesafb 13516 1 bnep 17830 2 rfcomm 38139 0 bluetooth 158479 10 bnep,rfcomm nvidia 10286823 30 snd_emu10k1_synth 13007 0 snd_emux_synth 33455 1 snd_emu10k1_synth snd_seq_virmidi 13309 1 snd_emux_synth snd_seq_midi_emul 13526 1 snd_emux_synth snd_hda_codec_hdmi 31775 4 snd_emu10k1 133257 3 snd_emu10k1_synth snd_ac97_codec 110213 1 snd_emu10k1 usbhid 41937 0 ac97_bus 12642 1 snd_ac97_codec snd_hda_intel 32719 2 snd_hda_codec 109562 2 snd_hda_codec_hdmi,snd_hda_intel snd_util_mem 13821 2 snd_emux_synth,snd_emu10k1 hid 77428 1 usbhid snd_pcm 80916 5 snd_hda_codec_hdmi,snd_emu10k1,snd_ac97_codec,snd_hda_intel,snd_hda_codec snd_hwdep 13276 3 snd_emux_synth,snd_emu10k1,snd_hda_codec snd_seq_midi 13132 0 snd_rawmidi 25424 3 snd_seq_virmidi,snd_emu10k1,snd_seq_midi snd_seq_midi_event 14475 2 snd_seq_virmidi,snd_seq_midi snd_seq 51592 5 snd_emux_synth,snd_seq_virmidi,snd_seq_midi_emul,snd_seq_midi,snd_seq_midi_event snd_timer 28931 3 snd_emu10k1,snd_pcm,snd_seq snd_seq_device 14172 5 snd_emu10k1_synth,snd_emu10k1,snd_seq_midi,snd_rawmidi,snd_seq snd 62218 21 snd_emux_synth,snd_seq_virmidi,snd_hda_codec_hdmi,snd_emu10k1,snd_ac97_codec,snd_hda_intel,snd_hda_codec,snd_pcm,snd_hwdep,snd_rawmidi,snd_seq,snd_timer,snd_seq_device ppdev 12849 0 emu10k1_gp 12570 0 snd_page_alloc 14108 3 snd_emu10k1,snd_hda_intel,snd_pcm mac_hid 13077 0 psmouse 86520 0 soundcore 14635 1 snd gameport 15060 2 emu10k1_gp serio_raw 13027 0 parport_pc 32114 1 binfmt_misc 17292 1 lp 17455 0 parport 40930 3 ppdev,parport_pc,lp floppy 60184 0 tg3 141414 0 rsteff@Gateway-32-E-4500D:~$ I recognize all the ones with snd and emu10k1 as being related to my Sound Blaster Live card. > To summarize your reboot issue: > > 1. Something fishy with your Ubuntu install - or Canonical buggered your > kernel (no messages or syslog? The Horror!) > 2. CPU or chipset overheating > > AND..we haven't even gotten to these yet: > > 3. Bad power supply. lm_sensors will read the voltages.....or sheck with > voltmeter. > 4. Bad RAM. One module may be flaky. Clean or swap. > > Easy check of RAM: Pull them out, check for discoloration, deformities > on the chips. Dust out the sockets with compressed air. Then clean the > RAM module pins either with a PCB cleaner, or rub gently with a rubber > eraser. I use a Staedtler Mars Plastic eraser brick Ive had for decades. > Firmly but carefully reseat the modules. I learned to clean card edges with a Pink Pearl eraser when I started working at Prime Computer long ago. I think I still have one. > If you are local, this might be a task for PLUGs Sunday Q&A if there is > one this week. That's right. It's the third Sunday already. > Have fun. Thanks. I will. And thanks for all your ideas. -- Regards, Dick Steffens _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
