Enabling Sensors on ASUS motherboards
Re: Enabling Sensors on ASUS motherboards
OK, I was just hoping that the Liquorix kernel would support it--did you happen to run "sudo sensors-detect" before "sensors", though? Just checking...
-
Eadwine Rose
- Administrator
- Posts: 15298
- Joined: Wed Jul 12, 2006 2:10 am
Re: Enabling Sensors on ASUS motherboards
Alrighty.. I am back with my report.
In short: nope, does not support.
Long blahblah with code:
QSI on this install (did not do a QSI on the Liquorix system, saw no need, I checked the versions to make sure it was nvidia 440.59 and all, it worked out):
All installs went fine, nvidia went without a hitch to 440.59
Output of sensors before kernel upgrade:
Ran sensors detect and replied yes to everything.
There was no change in the output of the sensors command.
Then installed the Liquorix kernel:
Booted into that and:
Now it sees even less! 
Sensors-detect with yes on everything again (it was done MUCH faster this time):
Ran sensors again, same result.
Installing that it87 thing I mentioned before in this thread renders this output on my system in this install (the one I posted the QSI of):
Maybe in the next kernel then....
In short: nope, does not support.
Long blahblah with code:
QSI on this install (did not do a QSI on the Liquorix system, saw no need, I checked the versions to make sure it was nvidia 440.59 and all, it worked out):
Code: Select all
System: Host: eadwineMX19 Kernel: 4.19.0-6-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-6-amd64
root=UUID=c7f614c9-c448-4560-93c2-9e9748b4ae8f ro quiet
Desktop: Xfce 4.14.2 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm4 dm: LightDM 1.26.0
Distro: MX-19.1_x64 patito feo October 21 2019 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: ASUSTeK model: TUF B450-PLUS GAMING v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 1607 date: 06/17/2019
Battery: Device-1: hidpp_battery_0 model: Logitech MX Ergo Multi-Device Trackball
serial: <filter> charge: 100% (should be ignored) rechargeable: yes
status: Discharging
CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+
family: 17 (23) model-id: 8 stepping: 2 microcode: 800820C L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 102207
Speed: 1419 MHz min/max: 1550/3200 MHz boost: enabled Core speeds (MHz): 1: 1385
2: 1463 3: 1462 4: 1619 5: 4024 6: 1769 7: 1806 8: 3455 9: 1398 10: 1882 11: 4059
12: 1807 13: 1803 14: 2400 15: 1375 16: 1380
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: ASUSTeK driver: nvidia v: 418.74
bus ID: 08:00.0 chip ID: 10de:1c82
Display: x11 server: X.Org 1.20.4 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 1050 Ti/PCIe/SSE2 v: 4.6.0 NVIDIA 418.74
direct render: Yes
Audio: Device-1: Conexant Systems CX23887/8 PCIe Broadcast Audio and Video Decoder with 3D
Comb
vendor: Hauppauge works driver: cx23885 v: 0.0.4 bus ID: 07:00.0 chip ID: 14f1:8880
Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus ID: 08:00.1 chip ID: 10de:0fb9
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus ID: 0a:00.3 chip ID: 1022:1457
Device-4: Logitech QuickCam E 3500 type: USB driver: snd-usb-audio,uvcvideo
bus ID: 1-7:3 chip ID: 046d:09a4 serial: <filter>
Sound Server: ALSA v: k4.19.0-6-amd64
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK
driver: r8169 v: kernel port: f000 bus ID: 03:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Ralink MT7601U Wireless Adapter type: USB driver: mt7601u bus ID: 1-1:2
chip ID: 148f:7601 serial: <filter>
IF: wlan0 state: down mac: <filter>
Drives: Local Storage: total: 1.82 TiB used: 101.06 GiB (5.4%)
ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-2: /dev/sdb vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 2B6Q scheme: GPT
ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT
ID-4: /dev/sdd type: USB vendor: Seagate model: ST1000LM035-1RK172 size: 931.51 GiB
block size: physical: 512 B logical: 512 B rotation: 5400 rpm serial: <filter>
rev: 0109 scheme: MBR
ID-5: /dev/sde vendor: Samsung model: SSD 860 EVO 250GB size: 232.89 GiB block size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s serial: <filter> rev: 3B6Q scheme: GPT
Partition: ID-1: / raw size: 58.59 GiB size: 57.42 GiB (98.00%) used: 10.28 GiB (17.9%) fs: ext4
dev: /dev/sdc1
ID-2: /home raw size: 166.48 GiB size: 162.87 GiB (97.83%) used: 18.39 GiB (11.3%)
fs: ext4 dev: /dev/sdc3
ID-3: swap-1 size: 7.81 GiB used: 0 KiB (0.0%) fs: swap swappiness: 15 (default 60)
cache pressure: 100 (default) dev: /dev/sdc2
Sensors: System Temperatures: cpu: 41.5 C mobo: 27.0 C gpu: nvidia temp: 36 C
Fan Speeds (RPM): cpu: 504 mobo: 168750 fan-2: fan-3: 0 fan-4: 747 fan-6: 0
gpu: nvidia fan: 25%
Voltages: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.27
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian/ buster-updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian/ buster main contrib non-free
2: deb http://deb.debian.org/debian-security/ buster/updates main contrib non-free
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/keeper.list
1: deb [arch=amd64] https://keepersecurity.com/desktop_electron/Linux/repo/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/megasync.list
1: deb https://mega.nz/linux/MEGAsync/Debian_10.0/ ./
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxrepo.com/mx/repo/ buster main non-free
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/slack.list
1: deb https://packagecloud.io/slacktechnologies/slack/debian/ jessie main
No active apt repos in: /etc/apt/sources.list.d/slacktechnologies_slack.list
Active apt repos in: /etc/apt/sources.list.d/spotify.list
1: deb http://repository.spotify.com/ stable non-free
No active apt repos in: /etc/apt/sources.list.d/various.list
Info: Processes: 394 Uptime: 9m Memory: 31.41 GiB used: 3.06 GiB (9.7%) Init: SysVinit
v: 2.93 runlevel: 5 default: 5 Compilers: gcc: 8.3.0 alt: 8 Shell: bash v: 5.0.3
running in: quick-system-in inxi: 3.0.36
All installs went fine, nvidia went without a hitch to 440.59
Output of sensors before kernel upgrade:
Code: Select all
$ sensors
asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPM
nouveau-pci-0800
Adapter: PCI adapter
fan1: 871 RPM
temp1: +32.0°C (high = +95.0°C, hyst = +3.0°C)
(crit = +105.0°C, hyst = +5.0°C)
(emerg = +135.0°C, hyst = +5.0°C)
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +33.4°C (high = +70.0°C)
Tctl: +33.4°C Ran sensors detect and replied yes to everything.
Code: Select all
Driver `to-be-written':
* ISA bus, address 0x290
Chip `ITE IT8665E Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 17h thermal sensors' (confidence: 9)
Note: there is no driver for ITE IT8665E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.
No modules to load, skipping modules configuration.
Unloading i2c-dev... OK
Unloading cpuid... OKThen installed the Liquorix kernel:
Code: Select all
Hit:1 http://nl.mxrepo.com/mx/repo buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://deb.debian.org/debian buster InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Reading package lists...
Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian-security buster/updates InRelease
Hit:4 http://nl.mxrepo.com/mx/repo buster InRelease
Get:5 http://mxrepo.com/mx/testrepo buster InRelease [4,972 B]
Get:6 http://mxrepo.com/mx/testrepo buster/test amd64 Packages [431 kB]
Get:7 http://mxrepo.com/mx/testrepo buster/test i386 Packages [424 kB]
Fetched 860 kB in 2s (437 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
linux-headers-5.5.0-5.1-liquorix-amd64 linux-image-5.5.0-5.1-liquorix-amd64
Suggested packages:
linux-doc-5.5 crda
Recommended packages:
irqbalance
The following NEW packages will be installed:
linux-headers-5.5.0-5.1-liquorix-amd64 linux-headers-liquorix-amd64
linux-image-5.5.0-5.1-liquorix-amd64 linux-image-liquorix-amd64
ndiswrapper-dkms
0 upgraded, 5 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 71.3 MB of archives.
After this operation, 377 MB of additional disk space will be used.
Do you want to continue? [Y/n]
y
Get:1 http://nl.mxrepo.com/mx/repo buster/non-free amd64 broadcom-sta-dkms all 6.30.223.271-10mx19+1 [2,207 kB]
Get:2 http://nl.mxrepo.com/mx/repo buster/main amd64 ndiswrapper-dkms all 1.62-0.1~mx19+2 [158 kB]
Get:3 http://mxrepo.com/mx/testrepo buster/test amd64 linux-headers-5.5.0-5.1-liquorix-amd64 amd64 5.5-8~mx19+1 [9,016 kB]
Get:4 http://mxrepo.com/mx/testrepo buster/test amd64 linux-image-5.5.0-5.1-liquorix-amd64 amd64 5.5-8~mx19+1 [59.7 MB]
Get:5 http://mxrepo.com/mx/testrepo buster/test amd64 linux-headers-liquorix-amd64 amd64 5.5-8~mx19+1 [156 kB]
Get:6 http://mxrepo.com/mx/testrepo buster/test amd64 linux-image-liquorix-amd64 amd64 5.5-8~mx19+1 [156 kB]
Fetched 71.3 MB in 6s (12.3 MB/s)
(Reading database ... 325379 files and directories currently installed.)
Preparing to unpack .../0-broadcom-sta-dkms_6.30.223.271-10mx19+1_all.deb ...
-------- Uninstall Beginning --------
Module: broadcom-sta
Version: 6.30.223.271
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
depmod...
update-initramfs.......
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Unpacking broadcom-sta-dkms (6.30.223.271-10mx19+1) over (6.30.223.271-10mx19+1) ...
Selecting previously unselected package linux-headers-5.5.0-5.1-liquorix-amd64.
Preparing to unpack .../1-linux-headers-5.5.0-5.1-liquorix-amd64_5.5-8~mx19+1_amd64.deb ...
Unpacking linux-headers-5.5.0-5.1-liquorix-amd64 (5.5-8~mx19+1) ...
Selecting previously unselected package linux-image-5.5.0-5.1-liquorix-amd64.
Preparing to unpack .../2-linux-image-5.5.0-5.1-liquorix-amd64_5.5-8~mx19+1_amd64.deb ...
Unpacking linux-image-5.5.0-5.1-liquorix-amd64 (5.5-8~mx19+1) ...
Selecting previously unselected package ndiswrapper-dkms.
Preparing to unpack .../3-ndiswrapper-dkms_1.62-0.1~mx19+2_all.deb ...
Unpacking ndiswrapper-dkms (1.62-0.1~mx19+2) ...
Selecting previously unselected package linux-headers-liquorix-amd64.
Preparing to unpack .../4-linux-headers-liquorix-amd64_5.5-8~mx19+1_amd64.deb ...
Unpacking linux-headers-liquorix-amd64 (5.5-8~mx19+1) ...
Selecting previously unselected package linux-image-liquorix-amd64.
Preparing to unpack .../5-linux-image-liquorix-amd64_5.5-8~mx19+1_amd64.deb ...
Unpacking linux-image-liquorix-amd64 (5.5-8~mx19+1) ...
Setting up ndiswrapper-dkms (1.62-0.1~mx19+2) ...
Loading new ndiswrapper-1.62 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
ndiswrapper.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
DKMS: install completed.
Building initial module for 5.5.0-5.1-liquorix-amd64
Done.
ndiswrapper.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
Setting up broadcom-sta-dkms (6.30.223.271-10mx19+1) ...
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Backing up initrd.img-4.19.0-6-amd64 to /boot/initrd.img-4.19.0-6-amd64.old-dkms
Making new initrd.img-4.19.0-6-amd64
(If next boot fails, revert to initrd.img-4.19.0-6-amd64.old-dkms image)
update-initramfs.......
DKMS: install completed.
Building initial module for 5.5.0-5.1-liquorix-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
DKMS: install completed.
Setting up linux-headers-5.5.0-5.1-liquorix-amd64 (5.5-8~mx19+1) ...
/etc/kernel/header_postinst.d/dkms:
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Error! Bad return status for module build on kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.2/build/make.log for more information.
Setting up linux-image-5.5.0-5.1-liquorix-amd64 (5.5-8~mx19+1) ...
I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.19.0-6-amd64
I: /initrd.img.old is now a symlink to boot/initrd.img-4.19.0-6-amd64
I: /vmlinuz is now a symlink to boot/vmlinuz-5.5.0-5.1-liquorix-amd64
I: /initrd.img is now a symlink to boot/initrd.img-5.5.0-5.1-liquorix-amd64
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.2/build/make.log for more information.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.5.0-5.1-liquorix-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
I: The initramfs will attempt to resume from /dev/sde2
I: (UUID=1f9b9bf2-b877-4e3f-bb9d-3e50a6ad0e24)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/linen/theme.txt
Found linux image: /boot/vmlinuz-5.5.0-5.1-liquorix-amd64
Found initrd image: /boot/initrd.img-5.5.0-5.1-liquorix-amd64
Found linux image: /boot/vmlinuz-4.19.0-6-amd64
Found initrd image: /boot/initrd.img-4.19.0-6-amd64
Found mtest-64.efi image: /boot/uefi-mt/mtest-64.efi
Found Windows Boot Manager on /dev/sda1@/EFI/Microsoft/Boot/bootmgfw.efi
Found MX 18.3 Continuum (18.3) on /dev/sda2
Found MX 19.1 patito feo (19.1 ) on /dev/sdc1
Adding boot menu entry for EFI firmware configuration
done
Setting up linux-image-liquorix-amd64 (5.5-8~mx19+1) ...
Setting up linux-headers-liquorix-amd64 (5.5-8~mx19+1) ...
-------- Uninstall Beginning --------
Module: broadcom-sta
Version: 6.30.223.271
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
depmod...
update-initramfs.......
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: broadcom-sta
Version: 6.30.223.271
Kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
wl.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
depmod...
update-initramfs.........
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Backing up initrd.img-4.19.0-6-amd64 to /boot/initrd.img-4.19.0-6-amd64.old-dkms
Making new initrd.img-4.19.0-6-amd64
(If next boot fails, revert to initrd.img-4.19.0-6-amd64.old-dkms image)
update-initramfs.......
DKMS: install completed.
Building initial module for 5.5.0-5.1-liquorix-amd64
Done.
wl.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down
Backing up initrd.img-5.5.0-5.1-liquorix-amd64 to /boot/initrd.img-5.5.0-5.1-liquorix-amd64.old-dkms
Making new initrd.img-5.5.0-5.1-liquorix-amd64
(If next boot fails, revert to initrd.img-5.5.0-5.1-liquorix-amd64.old-dkms image)
update-initramfs.........
DKMS: install completed.
-------- Uninstall Beginning --------
Module: ndiswrapper
Version: 1.62
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates': Directory not empty
/usr/sbin/dkms: line 2060: echo: write error: Broken pipe
/usr/sbin/dkms: line 2062: echo: write error: Broken pipe
depmod...
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: ndiswrapper
Version: 1.62
Kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
ndiswrapper.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates': Directory not empty
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 1.62
completely from the DKMS tree.
------------------------------
Done.
Loading new ndiswrapper-1.62 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
ndiswrapper.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
Building initial module for 5.5.0-5.1-liquorix-amd64
Done.
ndiswrapper.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
-------- Uninstall Beginning --------
Module: nvidia-current
Version: 440.59
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
nvidia-current.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
/usr/sbin/dkms: line 2060: echo: write error: Broken pipe
/usr/sbin/dkms: line 2062: echo: write error: Broken pipe
nvidia-current-modeset.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
rmdir: failed to remove 'updates/dkms': Directory not empty
- Use the dkms install command to reinstall any previous module version.
/usr/sbin/dkms: line 2060: echo: write error: Broken pipe
/usr/sbin/dkms: line 2062: echo: write error: Broken pipe
nvidia-current-drm.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
/usr/sbin/dkms: line 2060: echo: write error: Broken pipe
/usr/sbin/dkms: line 2062: echo: write error: Broken pipe
nvidia-current-uvm.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/dkms/
- Original module
rmdir: failed to remove 'updates/dkms': Directory not empty
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
/usr/sbin/dkms: line 2060: echo: write error: Broken pipe
/usr/sbin/dkms: line 2062: echo: write error: Broken pipe
depmod...
DKMS: uninstall completed.
-------- Uninstall Beginning --------
Module: nvidia-current
Version: 440.59
Kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
nvidia-current.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
nvidia-current-modeset.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
nvidia-current-drm.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
nvidia-current-uvm.ko:
- Uninstallation
- Deleting from: /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates/dkms': Directory not empty
depmod...
DKMS: uninstall completed.
------------------------------
Deleting module version: 440.59
completely from the DKMS tree.
------------------------------
Done.
Loading new nvidia-current-440.59 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
nvidia-current.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
nvidia-current-modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
nvidia-current-drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
nvidia-current-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
Building initial module for 5.5.0-5.1-liquorix-amd64
Done.
nvidia-current.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
nvidia-current-modeset.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
nvidia-current-drm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
nvidia-current-uvm.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.5.0-5.1-liquorix-amd64/updates/dkms/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
-------- Uninstall Beginning --------
Module: virtualbox-guest
Version: 6.1.2
Kernel: 4.19.0-6-amd64 (x86_64)
-------------------------------------
Status: Before uninstall, this module version was ACTIVE on this kernel.
vboxguest.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
- Original module
- Archived original module found in the DKMS tree
- Moving it to: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
vboxsf.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
- Original module
- No original module was found for this module on this kernel.
- Use the dkms install command to reinstall any previous module version.
rmdir: failed to remove 'updates': Directory not empty
vboxvideo.ko:
- Uninstallation
- Deleting from: /lib/modules/4.19.0-6-amd64/updates/
- Original module
- Archived original module found in the DKMS tree
- Moving it to: /lib/modules/4.19.0-6-amd64/updates/
rmdir: failed to remove 'updates': Directory not empty
depmod...
Removing original_module from DKMS tree for kernel 4.19.0-6-amd64 (x86_64)
DKMS: uninstall completed.
------------------------------
Deleting module version: 6.1.2
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-guest-6.1.2 DKMS files...
Building for 4.19.0-6-amd64 5.5.0-5.1-liquorix-amd64
Building initial module for 4.19.0-6-amd64
Done.
vboxguest.ko:
Running module version sanity check.
- Original module
- Found /lib/modules/4.19.0-6-amd64/updates/vboxguest.ko
- Storing in /var/lib/dkms/virtualbox-guest/original_module/4.19.0-6-amd64/x86_64/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
vboxsf.ko:
Running module version sanity check.
- Original module
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
vboxvideo.ko:
Running module version sanity check.
- Original module
- Found /lib/modules/4.19.0-6-amd64/updates/vboxvideo.ko
- Storing in /var/lib/dkms/virtualbox-guest/original_module/4.19.0-6-amd64/x86_64/
- Archiving for uninstallation purposes
- Installation
- Installing to /lib/modules/4.19.0-6-amd64/updates/
depmod...
System has not been booted with systemd as init system (PID 1). Can't operate.
DKMS: install completed.
Failed to connect to bus: Host is down
Building initial module for 5.5.0-5.1-liquorix-amd64
Error! Bad return status for module build on kernel: 5.5.0-5.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.1.2/build/make.log for more information.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
linux-headers-liquorix-amd64 linux-image-liquorix-amd64
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 326 kB disk space will be freed.(Reading database ... (Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%
(Reading database ... 354304 files and directories currently installed.)Removing linux-headers-liquorix-amd64 (5.5-8~mx19+1) ...Removing linux-image-liquorix-amd64 (5.5-8~mx19+1) ...
Hit:1 http://nl.mxrepo.com/mx/repo buster InRelease
Hit:2 http://deb.debian.org/debian buster-updates InRelease
Hit:3 http://deb.debian.org/debian buster InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Reading package lists...Booted into that and:
Code: Select all
$ sensors
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +33.1°C (high = +70.0°C)
Tctl: +33.1°C Sensors-detect with yes on everything again (it was done MUCH faster this time):
Code: Select all
Driver `to-be-written':
* ISA bus, address 0x290
Chip `ITE IT8665E Super IO Sensors' (confidence: 9)
Driver `k10temp' (autoloaded):
* Chip `AMD Family 17h thermal sensors' (confidence: 9)
Note: there is no driver for ITE IT8665E Super IO Sensors yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.
No modules to load, skipping modules configuration.
Unloading i2c-dev... OK
Unloading cpuid... OKRan sensors again, same result.
Installing that it87 thing I mentioned before in this thread renders this output on my system in this install (the one I posted the QSI of):
Code: Select all
$ sensors
it8665-isa-0290
Adapter: ISA adapter
in0: +1.43 V (min = +0.00 V, max = +2.76 V)
in1: +2.52 V (min = +0.67 V, max = +1.27 V) ALARM
in2: +2.02 V (min = +1.19 V, max = +1.18 V) ALARM
in3: +2.00 V (min = +1.37 V, max = +2.29 V)
in4: +0.03 V (min = +0.47 V, max = +2.74 V) ALARM
in5: +0.03 V (min = +0.86 V, max = +0.96 V) ALARM
in6: +0.03 V (min = +2.02 V, max = +2.23 V) ALARM
3VSB: +3.36 V (min = +4.95 V, max = +2.73 V) ALARM
Vbat: +3.27 V
+3.3V: +3.36 V
fan1: 508 RPM (min = 28 RPM)
fan2: 711 RPM (min = 17 RPM)
fan3: 0 RPM (min = 839 RPM)
fan4: 720 RPM (min = -1 RPM)
fan6: 0 RPM (min = -1 RPM)
temp1: +38.0°C (low = -111.0°C, high = -77.0°C) ALARM
temp2: +27.0°C (low = -81.0°C, high = -44.0°C) ALARM sensor = disabled
temp3: +31.0°C (low = +62.0°C, high = -17.0°C) ALARM sensor = disabled
temp4: +31.0°C (low = +110.0°C, high = +109.0°C) sensor = disabled
temp5: +31.0°C (low = -34.0°C, high = -27.0°C) ALARM sensor = disabled
temp6: +31.0°C (low = -17.0°C, high = -2.0°C) ALARM sensor = disabled
intrusion0: ALARM
k10temp-pci-00c3
Adapter: PCI adapter
Tdie: +36.4°C (high = +70.0°C)
Tctl: +36.4°C
asus-isa-0000
Adapter: ISA adapter
cpu_fan: 0 RPMMaybe in the next kernel then....
MX-23.6_x64 July 31 2023 * 6.1.0-39amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Re: Enabling Sensors on ASUS motherboards
Thanks for the exhaustive testing! 
-
Eadwine Rose
- Administrator
- Posts: 15298
- Joined: Wed Jul 12, 2006 2:10 am
Re: Enabling Sensors on ASUS motherboards
You're welcome. :)
MX-23.6_x64 July 31 2023 * 6.1.0-39amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
-
freebird54
Re: Enabling Sensors on ASUS motherboards
According to Phoronix (etc) the next kernel (5.6) may well have better sensor capabilities - and even fold hddtemp into hwmon as well. Worth rechecking then I guess.
Freeebird54
Freeebird54
Re: Enabling Sensors on ASUS motherboards
But it is not all about kernels & sensors the drivers are needed too. Plus better support for new CPU's & Video cards overall.
I would like to see the below drivers on the MX repo. But I don't I thing will bother asking.
https://aur.archlinux.org/packages/asus ... -dkms-git/ main site https://github.com/electrified/asus-wmi-sensors
https://aur.archlinux.org/packages/it87-dkms-git/ main site https://github.com/a1wong/it87
https://www.phoronix.com/forums/forum/h ... processors
https://forum.manjaro.org/t/asus-x370-p ... ors/71489
Asus B450-I board users a ITE IT8665E Super IO sensor with ISA bus address 0x290
I would like to see the below drivers on the MX repo. But I don't I thing will bother asking.
https://aur.archlinux.org/packages/asus ... -dkms-git/ main site https://github.com/electrified/asus-wmi-sensors
https://aur.archlinux.org/packages/it87-dkms-git/ main site https://github.com/a1wong/it87
https://www.phoronix.com/forums/forum/h ... processors
https://forum.manjaro.org/t/asus-x370-p ... ors/71489
Asus B450-I board users a ITE IT8665E Super IO sensor with ISA bus address 0x290
Main : MX 19.1-AHS (i3) 5.4.13-1~mx19+1, Asus B450-i AMD 5 3600 , 32gb Hyper-X 3200 , GTX970 . 
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)
-
Eadwine Rose
- Administrator
- Posts: 15298
- Joined: Wed Jul 12, 2006 2:10 am
Re: Enabling Sensors on ASUS motherboards
I have NO idea what sensor is on my board *shrug* :)
Slightly different board here, hence.
Slightly different board here, hence.
MX-23.6_x64 July 31 2023 * 6.1.0-39amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
-
SwampRabbit
- Posts: 3602
- Joined: Tue Jun 14, 2016 2:02 pm
Re: Enabling Sensors on ASUS motherboards
What sorta comment is that?KoO wrote: Fri Feb 28, 2020 5:39 pm I would like to see the below drivers on the MX repo. But I don't I thing will bother asking.
We can't read minds. I think some of those should or will be included in newer kernels from the looks of it.
The first one looks like a good candidate for packaging for MX.
But one of them has a take down notice on their GitHub though, not sure of the stability.
I have been unable to meet support demands for this driver, resulting
in unpleasant experience and frustration for everyone involved.
Consequently, the driver will be removed from github, effective
August 1, 2018. Interested parties are encouraged to clone the driver
before that time and to start maintaining it on their own.
NEW USERS START HERE FAQS, MX Manual, and How to Break Your System - Don't use Ubuntu PPAs! Always post your Quick System Info (QSI) when asking for help.
Re: Enabling Sensors on ASUS motherboards
@Eadwine Rose
Pretty sure your board has the same sensor chip.
But it is not the end of the world. How long have you had the board without even knowing about this anyway..The only way found out about it in the first place, was because of conky and the hwmon command not working the way it did with my old setup.
@SwampRabbit
Yes I read this too but the fact is it still on github. And has been adopted by arch linux on their aur. But if you read the list of supported sensors IT8665E is not in the list anyway.. It was only a suggestion
Pretty sure your board has the same sensor chip.
But it is not the end of the world. How long have you had the board without even knowing about this anyway..The only way found out about it in the first place, was because of conky and the hwmon command not working the way it did with my old setup.
@SwampRabbit
Yes I read this too but the fact is it still on github. And has been adopted by arch linux on their aur. But if you read the list of supported sensors IT8665E is not in the list anyway.. It was only a suggestion
SwampRabbit wrote: Fri Feb 28, 2020 6:03 pm
But one of them has a take down notice on their GitHub though, not sure of the stability.I have been unable to meet support demands for this driver, resulting
in unpleasant experience and frustration for everyone involved.
Consequently, the driver will be removed from github, effective
August 1, 2018. Interested parties are encouraged to clone the driver
before that time and to start maintaining it on their own.
Main : MX 19.1-AHS (i3) 5.4.13-1~mx19+1, Asus B450-i AMD 5 3600 , 32gb Hyper-X 3200 , GTX970 .
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)
Lenovo T430 : Debian10 antiX17 (i3) , 4.20.12 , i5 , 12gb .
Lenovo X220 : Test Machine (ATM)
-
Eadwine Rose
- Administrator
- Posts: 15298
- Joined: Wed Jul 12, 2006 2:10 am
Re: Enabling Sensors on ASUS motherboards
I have had the board for a while.. it was just interested to know how you found out it was this chip. Through a command or google work?
I have working sensors so it isn't a biggie.
I have working sensors so it isn't a biggie.
MX-23.6_x64 July 31 2023 * 6.1.0-39amd64 ext4 Xfce 4.20.0 * 8-core AMD Ryzen 7 2700
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030
Asus TUF B450-Plus Gaming UEFI * Asus GTX 1050 Ti Nvidia 535.247.01 * 2x16Gb DDR4 2666 Kingston HyperX Predator
Samsung 870EVO * Samsung S24D330 & P2250 * HP Envy 5030