Доброго всем дня.
Не подскажете как можно определить хотя бы название модуля WiFi, если его просто не видно
[[email protected] waldy]# lspci -k
00:00.0 Host bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series SoC Transaction Register (rev 36)
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: iosf_mbi_pci
00:02.0 VGA compatible controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller (rev 36)
	DeviceName:  Onboard IGD
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: i915
	Kernel modules: i915
00:0b.0 Signal processing controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Power Management Controller (rev 36)
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: proc_thermal
	Kernel modules: processor_thermal_device
00:14.0 USB controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series USB xHCI Controller (rev 36)
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci
00:1a.0 Encryption controller: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series Trusted Execution Engine (rev 36)
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: mei_txe
	Kernel modules: mei_txe
00:1c.0 PCI bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Express Port #1 (rev 36)
	Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCU (rev 36)
	Subsystem: Intel Corporation Device 7270
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
	Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
	Kernel driver in use: r8169
	Kernel modules: r8169
На мини компьюторе был предустановлен Windows 10 OEM и понятно что все работало и WiFi и Bluetooth. Сейчас пока этого ничего нет.
[[email protected] waldy]# dmesg | grep firmware
[    0.185031] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    6.976457] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    7.328719] Bluetooth: hci0: BCM: firmware Patch file not found, tried:
[    7.649780] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.BESSTAR TECH LIMITED-Z83-F.txt failed with error -2
[    7.649841] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.txt failed with error -2
Предположительно производитель чипа Broadcom
vasek
такое впечатление, что все работает нормально и вентилятор крутится … ???
[[email protected] waldy]# echo 1 | sudo tee /sys/class/thermal/cooling_device[0-3]/cur_state
1
[[email protected] waldy]# echo 10 | sudo tee /sys/class/thermal/cooling_device[0-3]/cur_state
10
Команда может и работает, а вот вентилятор не крутится (его не слышно).
vasek
В принципе температуру можешь выводить и так, без исползования других утилит
На данный момент
[[email protected] waldy]# awk '{ print $1/1000 }' /sys/class/thermal/thermal_zone0/temp
43.6
[[email protected] waldy]# awk '{ print $1/1000 }' /sys/class/thermal/thermal_zone3/temp
51
vs220
Покажите еще вывод
[[email protected] waldy]# acpi -v
bash: acpi: команда не найдена
[[email protected] waldy]# pwmconfig
# pwmconfig version 3.6.0
This program will search your sensors for pulse width modulation (pwm)
controls, and test each one to see if it controls a fan on
your motherboard. Note that many motherboards do not have pwm
circuitry installed, even if your sensor chip supports pwm.

We will attempt to briefly stop each fan using the pwm controls.
The program will attempt to restore each fan to full speed
after testing. However, it is ** very important ** that you
physically verify that the fans have been to full speed
after the program has completed.

/usr/bin/pwmconfig: There are no pwm-capable sensor modules installed
[[email protected] waldy]# sensors-detect
# sensors-detect version 3.6.0
# System: Default string Default string [Default string]
# Board: AMI Corporation T3 MRD
# Kernel: 5.10.8-arch1-1 x86_64
# Processor: Intel(R) Atom(TM) x5-Z8350 CPU @ 1.44GHz (6/76/4)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           No
AMD Family 17h thermal sensors...                           No
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             No
Hygon Family 18h thermal sensors...                         No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no): yes
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
Probing for `IPMI BMC KCS' at 0xca0...                      Success!
    (confidence 4, driver `to-be-written')
Probing for `IPMI BMC SMIC' at 0xca8...                     Success!
    (confidence 4, driver `to-be-written')

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no): yes
Probing for `National Semiconductor LM78' at 0x290...       No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: Synopsys DesignWare I2C adapter (i2c-0)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-1)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.
Client at address 0x1a can not be probed - unload all client drivers first!

Next adapter: Synopsys DesignWare I2C adapter (i2c-2)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-3)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-4)
Do you want to scan it? (YES/no/selectively):
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-5)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: Synopsys DesignWare I2C adapter (i2c-6)
Do you want to scan it? (YES/no/selectively): yes
Adapter doesn't support all probing functions.
Some addresses won't be probed.

Next adapter: i915 gmbus ssc (i2c-7)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: i915 gmbus vga (i2c-8)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: i915 gmbus panel (i2c-9)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: i915 gmbus dpc (i2c-10)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: i915 gmbus dpb (i2c-11)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (yes/NO/selectively): n

Next adapter: AUX D/port D (i2c-13)
Do you want to scan it? (yes/NO/selectively): n
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `to-be-written':
  * ISA bus, address 0xca0
    Chip `IPMI BMC KCS' (confidence: 4)
  * ISA bus, address 0xca8
    Chip `IPMI BMC SMIC' (confidence: 4)

Driver `coretemp':
  * Chip `Intel digital thermal sensor' (confidence: 9)

Note: there is no driver for IPMI BMC KCS yet.
Check https://hwmon.wiki.kernel.org/device_support_status for updates.

Do you want to generate /etc/conf.d/lm_sensors? (YES/no): yes
Created symlink /etc/systemd/system/multi-user.target.wants/lm_sensors.service → /usr/lib/systemd/system/lm_sensors.service.
Unloading i2c-dev... OK

vasek
2. показывает ли что-нибудь и если показывает, то меняются ли цифирки в выводе
[[email protected] ~]$ while true;do cat /sys/class/thermal/thermal_zone*/temp; sleep 2; echo -e "\n"; done
37300
37350
20000
45000
46000
42000
37300
37350
20000
45000
46000
42000

[[email protected] ~]$ grep Proc /sys/class/thermal/cooling_device*/type
/sys/class/thermal/cooling_device0/type:Processor
/sys/class/thermal/cooling_device1/type:Processor
/sys/class/thermal/cooling_device2/type:Processor
/sys/class/thermal/cooling_device3/type:Processor
[[email protected] ~]$ cat /sys/class/thermal/cooling_device[0-3]/cur_state
0
0
0
0
[[email protected] ~]$ cat /sys/class/thermal/cooling_device[0-3]/max_state
10
10
10
10
[[email protected] ~]$ cat /sys/class/thermal/thermal_zone*/trip_point* | egrep 'passive|active'
passive
passive
passive
passive
passive
passive
passive
passive
[[email protected] ~]$ grep intel /sys/class/thermal/cooling_device*/type
/sys/class/thermal/cooling_device5/type:intel_powerclamp
vasek
1. пробуй прописывать параметры acpi_osi= (описание приводил выше)

я так и не понял, куда это прописывать,
сюда:
nano /boot/loader/entries/arch-uefi.conf
title    Arch Linux
linux    /vmlinuz-linux
initrd   /intel-ucode.img
initrd   /initramfs-linux.img
options  root=/dev/mmcblk0p2 rw init=/usr/lib/systemd/systemd
или сюда:
nano /boot/loader/loader.conf
default   arch-uefi
timeout   2
и не обижайтесь, что приходится по несколько раз повторятся, ведь я простой юзер а не "бородатый админ".
vasek
Также неплохо бы посмотреть и выводы, которые описал выше.
Весь файл
vasek
если стоит grub
а как сделать с bootctl
Снова установил Arch Linux на "игрушку", (кстати, для "игрушки" работает довольно-таки шустро) bootctl (не GRUB) из-за EFI, xorg и DE. Далее, установил acpica
вывод:
[[email protected] waldy]# iasl -d dsdt.dat

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20210105
Copyright (c) 2000 - 2021 Intel Corporation

File appears to be binary: found 18661 non-ASCII characters, disassembling
Binary file appears to be a valid ACPI table, disassembling
Input file dsdt.dat, Length 0xD8D0 (55504) bytes
ACPI: DSDT 0x0000000000000000 00D8D0 (v01 A1895  A1895001 00000001 INTL 20060113)
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)

Parsing completed
Disassembly completed
ASL Output:    dsdt.dsl - 467922 bytes
[[email protected] waldy]# iasl -tc dsdt.dsl

Intel ACPI Component Architecture
ASL+ Optimizing Compiler/Disassembler version 20210105
Copyright (c) 2000 - 2021 Intel Corporation

dsdt.dsl    285:         PEWS = PEWS /* \PEWS */
Warning  3023 -            ^ Duplicate value in list (Source is the same as Target)

             ..................

ASL Input:     dsdt.dsl -  467922 bytes   6257 keywords  15186 source lines
Hex Dump:      dsdt.hex -  519089 bytes

Compilation failed. 1 Errors, 47 Warnings, 182 Remarks
No AML files were generated due to compiler error(s)
не нашел спойлера, поэтому только часть вывода
1 Errors это
dsdt.dsl  13208:                         (Local1 + 0x80)
Error    6114 -                                 ^ Result is not used, operator has no effect
В выводе не нашел ничего о ASPI.
Подскажите, что делать дальше? И в каком файле мне искать описание параметров ядра?
Спасибо за советы, но у меня сейчас 2(я) смена, я ничего не могу начинать. Вот будут выходные, опять установлю Arch Linux и тогда можно будет экспериментировать. Я обещаю, обязательно отпишусь, что получилось.
nafanja
waldy-m, а в случае когда нет никакой системы вообще, охлаждение работает?
Да, работает.
P.S. Даже с установленным Arch(ем), сразу включаеся вентилятор и светодиодная подсветка, загружается BIOS, начинает загружатся Linux и все замолкает и затухает.
vasek
Wiki , но можно посмотреть и что прописано конкретно в твоих таблицах, но для этого нужно их декомпилировать - как? - прописано в той же Wiki, которую указал.
Спасибо за линк, на следующей недели займусь экспериментами, затем отпишусь. Ну а на данный момент установил снова windows, охлаждение работает, так-что проблемка действительно в Linux(e).