looks to be CONFIG_NVME_HWMON, ill have it ready this release.
Search Criteria
Package Base Details: linux-amd
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-amd.git (read-only, click to copy) |
---|---|
Submitter: | None |
Maintainer: | None |
Last Packager: | None |
Votes: | 29 |
Popularity: | 0.022818 |
First Submitted: | 2019-11-10 15:20 (UTC) |
Last Updated: | 2024-04-29 09:32 (UTC) |
Packages (2)
Latest Comments
« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 14 15 16 .. 36 Next › Last »
<deleted-account> commented on 2022-10-03 11:32 (UTC)
FGD commented on 2022-10-02 20:11 (UTC) (edited on 2022-10-02 20:12 (UTC) by FGD)
Hello, the kernel does not recognize 2 of my 7 sensors: "nvme-pci" and "gigabyte_wmi-virtual".
Any other kernel does so far, including Zen, Mainline, my custom TKG-BMQ, etc..
Not sure what to give as info but this is what I should show with the NVME part of hwmon and sensors:
╰─λ sensors
nvme-pci-0100
Adapter: PCI adapter
Composite: +37.9°C (low = -273.1°C, high = +81.8°C)
(crit = +84.8°C)
Sensor 1: +37.9°C (low = -273.1°C, high = +65261.8°C)
Sensor 2: +49.9°C (low = -273.1°C, high = +65261.8°C)
gigabyte_wmi-virtual-0
Adapter: Virtual device
temp1: +27.0°C
temp2: +32.0°C
temp3: +32.0°C
temp4: +31.0°C
temp5: +32.0°C
temp6: +42.0°C
╰─λ ls /sys/class/hwmon/
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon0 -> ../../devices/virtual/thermal/thermal_zone0/hwmon0
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon1 -> ../../devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/hwmon/hwmon1
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon2 -> ../../devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/hwmon2
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon3 -> ../../devices/platform/it87.2624/hwmon/hwmon3
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon4 -> ../../devices/pci0000:00/0000:00:18.3/hwmon/hwmon4
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon5 -> ../../devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/DEADBEEF-2001-0000-00A0-C90629100000/hwmon/hwmon5
lrwxrwxrwx 0 root 2 Oct 15:37 hwmon6 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:406E.0005/power_supply/hidpp_battery_0/hwmon6
lrwxrwxrwx 0 root 2 Oct 15:38 hwmon7 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:4069.0004/power_supply/hidpp_battery_1/hwmon7
This is what it shows with linux-amd:
╰─λ ls /sys/class/hwmon/
lrwxrwxrwx 0 root 2 Oct 15:23 hwmon0 -> ../../devices/pci0000:00/0000:00:03.1/0000:08:00.0/0000:09:00.0/0000:0a:00.0/hwmon/hwmon0
lrwxrwxrwx 0 root 2 Oct 15:23 hwmon1 -> ../../devices/platform/it87.2624/hwmon/hwmon1
lrwxrwxrwx 0 root 2 Oct 15:23 hwmon2 -> ../../devices/pci0000:00/0000:00:18.3/hwmon/hwmon2
lrwxrwxrwx 0 root 2 Oct 15:23 hwmon3 -> ../../devices/virtual/thermal/thermal_zone0/hwmon3
lrwxrwxrwx 0 root 2 Oct 15:23 hwmon4 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:406E.0005/power_supply/hidpp_battery_0/hwmon4
lrwxrwxrwx 0 root 2 Oct 15:24 hwmon5 -> ../../devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:05:00.3/usb3/3-6/3-6.1/3-6.1:1.2/0003:046D:C52B.0003/0003:046D:4069.0004/power_supply/hidpp_battery_1/hwmon5
Missing /devices/virtual/thermal/thermal_zone0 and /devices/pci0000:00/0000:00:01.1/0000:01:00.0/nvme/nvme0/hwmon2.
Absolutely not idea how to troubleshoot this, but since all my other kernels (tried 4-5) are showing the device, I'm guessing something could be missing within linux-amd.
Thanks!
visious commented on 2022-09-16 13:42 (UTC)
@blackhole Thank you in advance.
blackhole commented on 2022-09-16 13:26 (UTC)
You must copy and paste the bash function in terminal and after type
check_march
visious commented on 2022-09-16 13:24 (UTC)
@blackhole What did you type in terminal to get this output?
blackhole commented on 2022-09-16 13:15 (UTC)
check_march() {
CPU=$(gcc -Q -march=native --help=target|grep march=|awk '{print $2}'|head -1)
MARCH=$(echo $CPU|tr '[:lower:]' '[:upper:]'&&echo)
if [[ ${MARCH} == "ZNVER1" ]]; then
MARCH="ZEN"
elif [[ ${MARCH} == "ZNVER2" ]]; then
MARCH="ZEN2"
elif [[ ${MARCH} == "ZNVER3" ]]; then
MARCH="ZEN3"
elif [[ ${MARCH} == "BDVER1" ]]; then
MARCH="BULLDOZER"
elif [[ ${MARCH} == "BDVER2" ]]; then
MARCH="PILEDRIVER"
elif [[ ${MARCH} == "BDVER3" ]]; then
MARCH="STEAMROLLER"
elif [[ ${MARCH} == "BDVER4" ]]; then
MARCH="EXCAVATOR"
elif [[ ${MARCH} == "BTVER1" ]]; then
MARCH="BOBCAT"
elif [[ ${MARCH} == "BTVER2" ]]; then
MARCH="JAGUAR"
elif [[ ${MARCH} == "AMDFAM10" ]]; then
MARCH="MK10"
elif [[ ${MARCH} == "K8-SSE3" ]]; then
MARCH="K8SSE3"
elif [[ ${MARCH} == "BONNELL" ]]; then
MARCH="ATOM"
elif [[ ${MARCH} == "GOLDMONT-PLUS" ]]; then
MARCH="GOLDMONTPLUS"
elif [[ ${MARCH} == "SKYLAKE-AVX512" ]]; then
MARCH="SKYLAKE2"
elif [[ ${MARCH} == "ICELAKE-CLIENT" ]]; then
MARCH="ICELAKE"
fi
echo $MARCH
}
visious commented on 2022-09-16 13:11 (UTC)
Hi, I have a question for you. How do I know if my cpu is znver3 or mzen3 or znver2 to pick the correct kernel?
PS: I don't have AMD cpu, it's good to know.
killajoe commented on 2022-09-01 18:42 (UTC)
awesome! makes my machine happy.
<deleted-account> commented on 2022-08-31 13:01 (UTC)
ok I removed mkinitcpio from the deps, atleast it will get rid of the conflict warning then for the dracut users.
killajoe commented on 2022-08-30 21:41 (UTC)
Indeed mkinitcpio is still the most used but optional for the kernel packages: initramfs (mkinitcpio, dracut, booster, booster) It is only that p.e. dracut is conflicting with mkinitcpio. And i can build your linux-amd without mkinitcpio installed when i remove what i badly name "runnings" in install file and inside the PKGBUILD (the parts calling mkinitcpio)
Pinned Comments
<deleted-account> commented on 2023-05-04 16:38 (UTC)
GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.
This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.
<deleted-account> commented on 2020-10-26 18:15 (UTC)
GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.
This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.
<deleted-account> commented on 2019-11-10 15:23 (UTC)
Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :