Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #190407
| From | Michael Fothergill <michael.fothergill@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: lm-sensors doesn't see the cpu rpm..... |
| Date | 2017-12-28 17:00 +0100 |
| Message-ID | <v1IL8-2cF-13@gated-at.bofh.it> (permalink) |
| References | <v1Fax-8gH-9@gated-at.bofh.it> <v1FDz-8rd-7@gated-at.bofh.it> <v1G6H-vq-25@gated-at.bofh.it> <v1GzE-J8-17@gated-at.bofh.it> <v1GT0-QQ-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
On 28 December 2017 at 13:55, Greg Wooledge <wooledg@eeg.ccf.org> wrote: > On Thu, Dec 28, 2017 at 01:11:56PM +0000, Michael Fothergill wrote: > > root@bong:/boot# sudo modprobe coretemp > > modprobe: ERROR: could not insert 'coretemp': No such device > > > > > > This is odd because coretemp is set as a module option in the config > file: > > > > CONFIG_SENSORS_CORETEMP=m > > > > Comments appreciared > > Well, it *should* work with a standard Debian kernel and applicable > hardware. > If you look here: https://askubuntu.com/questions/748615/lm-sensors-not-returning-cpu-temp-it87 it says that You need to append acpi_enforce_resources=lax at the end of > the line GRUB_CMDLINE_LINUX > in /etc/default/grub to make e.g. the it87 module work for the FX8350 chip AFAICT BUT If you look at my /etc/default/grub: root@bong:/etc/default# more grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=10 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet" GRUB_CMDLINE_LINUX="initrd=/install/initrd.gz" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" root@bong:/etc/default# I don't have any acpi command in there but lsmod does list it87 as a module for my install: root@bong:/etc/default# lsmod | grep it87 it87 57344 0 hwmon_vid 16384 1 it87 Does it need to have a 1 not a zero in there for the it87 to actually be working even if it is installed? Cheers MF > > wooledg:~$ /sbin/modinfo coretemp > filename: /lib/modules/4.9.0-4-amd64/kernel/drivers/hwmon/coretemp. > ko > license: GPL > description: Intel Core temperature monitor > author: Rudolf Marek <r.marek@assembler.cz> > alias: cpu:type:x86,ven0000fam*mod*:feature:*01C0* > depends: > intree: Y > vermagic: 4.9.0-4-amd64 SMP mod_unload modversions > parm: tjmax:TjMax value in degrees Celsius (int) > > Your "No such device" error sounds like it probed for hardware and didn't > find any. If the module itself were missing from the file system, then > I would have expected "FATAL: Module coretemp not found in directory ...". > > It says "Intel" in the description. Are you using an Intel CPU? > >
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 13:10 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 13:40 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 14:10 +0100
Re: lm-sensors doesn't see the cpu rpm..... Greg Wooledge <wooledg@eeg.ccf.org> - 2017-12-28 15:00 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:00 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:10 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:20 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 16:40 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 17:00 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 18:00 +0100
Re: lm-sensors doesn't see the cpu rpm..... deloptes <deloptes@gmail.com> - 2017-12-28 19:20 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 19:50 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 20:00 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 20:20 +0100
Re: lm-sensors doesn't see the cpu rpm..... Michael Fothergill <michael.fothergill@gmail.com> - 2017-12-28 21:20 +0100
csiph-web