![]() How is 'Manjaro' Pronounced? As in Mount Kilimanjaro, which was the inspiration for the name. as well as a selection of realtime kernels. There are builds for ARM devices like Raspberry Pi, Odroid etc. Community releases include Enlightenment (E17), OpenBox, Mate, FluxBox, Cinnamon, LXDE, LXQt, & Deepin. Official releases include Xfce, KDE & Gnome as well as a minimal net-edition. It provides all the benefits of a rolling release distro and includes a user-friendly installer, tested updates that try very hard to not break your system and a community of friendly users for support. Search for lm85-i2c-0-2e and you'll realise that you're not alone in facing this issue.Manjaro is a GNU/Linux distribution based on Arch Linux. They are the experts, and they appear to be incredibly helpful. I'd suggest you check your system's hardware specs to determine the chip that's actually present, and separately open a ticket on the lm-sensors site detailing your problems. This chip should use the lm83 driver module according to lm-sensors, not lm85.Īt this point, I'm not sure if you can get any more meaningful help outside of the lm-sensors team. In fact, from your comment ( "lm82 0-002e: Starting monitoring") it appears your system detected the lm82 chip at boot. Look through this very similar bug report on the lm-sensors site. It appears that you might not actually have an lm85 chip.įrom reading reports of other users who reported similar errors, it appears that your chip is either being wrongly detected or is disabled. It should be present in a block with a comment at top that says the entry was added by sensors-detect: # Generated by sensors-detect on xxxx In case you're thinking of re-running sensors-detect, I'd first remove the /etc/modules entries added by the previous run. Note, lm-sensors project also provides a standalone script version of sensors-detect that is likely to be newer than the packaged version, and might better detect sensors on your machine. If there's a problem getting the sensor values for the CPU fan and CPU, then you should check support for your particular device at the lm-sensors devices support page. sudo apt-get -purge remove sensors-applet If it successfully gives you sensor readings, I'd just reinstall sensors-applet. If this is true, run the sensors command in the terminal to check if this works fine. Not everything reported by the applet is provided by lm_sensors, so first ensure the problem is with a sensors output. Right-click the sensor-applet and look at the Sensors tab. And those sensors reported by the applets I choosed (and renamed, 'cos "CPU Fan" is better than "cpu_fan") by it's Preferences dialog. What's happening? All modules are correctly loaded, I presume. Those applets keep saying " Error updating sensor XXX", like " An error occurred while trying to update the value of the sensor CPU Fan located at sensor://lm85-i2c-3-2e/20", and sensor 'CPU' at sensor://lm82-i2c-3-2e/32. Typing sensors at terminal simply gives me zeroed values, except for cpu0_vid (always +2.050V), and coretemp-isa-00 (always 42☌). I added also those nice applets to my upper Gnome panel.īut it couldn't get any info. It edited my /etc/modules so the needed modules ( lm85, i2c-i801 and coretemp) would get loaded during startup. I've installed lm-sensors and ran sensors-detect successfully.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |