2012/11/29(Thu)D945GCLF2でlm_sensorsを動かす

2012/11/29 23:47 Software::Linux
タイトルそのままです。
最近のPCになるほど、lm_sensorsが一発でsensors-detectで動いてくれなくて困る…orz

# さらに5ヶ月前のことで、メモが不十分で記憶が曖昧…

環境

まずはお約束の。

マザボ:Intel D945GCLF2
ディストリ:Fedora 16 i386
sensors-detect:revision 5984 (2011-07-10 21:22:53 +0200)

この当時のuname -rを控え忘れたので……2012/7時点での最新です

とりあえずsensors-detect

まあ、一発でうまくは認識してくれない。
# yes | sensors-detect

# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# Board: Intel Corporation D945GCLF2

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): 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 15h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM 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): Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     Yes
Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors'         Success!
    (address 0x680, driver `smsc47m1')
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): Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

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): 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): Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus vga (i2c-3)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 GPIOA (i2c-4)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively):
Next adapter: SDVO DDC proxy (i2c-14)
Do you want to scan it? (YES/no/selectively):
Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `smsc47m1':
  * ISA bus, address 0x680
    Chip `SMSC LPC47M15x/192/997 Super IO Fan Sensors' (confidence: 9)

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

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Unloading i2c-dev... OK

# sensors

coretemp-isa-0000
Adapter: ISA adapter
Core 0:        +5.0 C  (crit = +90.0 C)
Core 1:        +7.0 C  (crit = +90.0 C)
一応、coretempモジュールを探してきてsensorsの結果に現れるものの、明らかに値がおかしい。
しかも、このとき/var/log/messagesに怪しげなlogが……
おそらく何かバグってるんですな。
[ 2622.865972] i2c /dev entries driver
[ 2630.628037] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.680035] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.732036] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.784035] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.836035] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.888034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.940034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2630.992034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.044034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.096062] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.148038] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.200035] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.252034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.304034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.356034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.408042] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.460034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.512034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.564034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.616034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.668034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.720034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.772034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.824034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 2631.876034] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
...

解決策

ポッキーの日だけにFedora11!(でもlm_sensorsのit87が有効にならない→解決)の記事より、カーネルオプションを変更。

acpi_enforce_resources=laxというのをカーネルオプションに足します。他のオプションはお好みで。*1
その後、grub2-mkconfigでコンフィグを反映。/boot/grub2/grub.cfgを直接弄ると、次にカーネルの更新をインストールしたとき等に上書きされてしまうので注意。
ちなみに、acpi_enforce_resources=laxが何を示しているかは、末尾を参照。
# vim /etc/default/grub

(中略)
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 LANG=ja_JP.UTF-8  KEYTABLE=jp106 biosdevname=0 acpi_enforce_resources=lax"

(中略)

# grub2-mkconfig -o /boot/grub2/grub.cfg

# reboot

*1 : NICをp3p1表記ではなくeth0で使いたいからbiosdevname=0とかね。

解決後

coretempモジュールは相変わらずなものの、マザボ側のチップを検出できて、きちんと温度が見えるようになった。
# sensors-detect

# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# Board: Intel Corporation D945GCLF2

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): ^C
[root@pumice ~]# yes | sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# Board: Intel Corporation D945GCLF2

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): 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 15h power sensors...                             No
Intel digital thermal sensor...                             Success!
    (driver `coretemp')
Intel AMB FB-DIMM 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): Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     Yes
Found `SMSC LPC47M15x/192/997 Super IO Fan Sensors'         Success!
    (address 0x680, driver `smsc47m1')
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): Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

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): 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): Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801G ICH7
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus vga (i2c-3)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 GPIOA (i2c-4)
Do you want to scan it? (YES/no/selectively): Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 No
Probing for `EDID EEPROM'...                                Yes
    (confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively):
Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively):
Next adapter: SDVO DDC proxy (i2c-14)
Do you want to scan it? (YES/no/selectively):
Next adapter: SMBus I801 adapter at 2000 (i2c-15)
Do you want to scan it? (YES/no/selectively): Client found at address 0x2d
Probing for `Myson MTP008'...                               No
Probing for `National Semiconductor LM78'...                No
Probing for `National Semiconductor LM79'...                No
Probing for `National Semiconductor LM80'...                No
Probing for `National Semiconductor LM85'...                No
Probing for `National Semiconductor LM96000 or PC8374L'...  No
Probing for `Analog Devices ADM1027'...                     No
Probing for `Analog Devices ADT7460 or ADT7463'...          No
Probing for `SMSC EMC6D100 or EMC6D101'...                  No
Probing for `SMSC EMC6D102'...                              No
Probing for `SMSC EMC6D103'...                              No
Probing for `SMSC EMC6D103S or EMC2300'...                  No
Probing for `SMSC EMC6W201'...                              No
Probing for `Winbond WPCD377I'...                           No
Probing for `Analog Devices ADT7473'...                     No
Probing for `Analog Devices ADT7476'...                     No
Probing for `Analog Devices ADT7490'...                     No
Probing for `Andigilog aSC7611'...                          No
Probing for `Andigilog aSC7621'...                          No
Probing for `National Semiconductor LM87'...                No
Probing for `Analog Devices ADM1024'...                     No
Probing for `National Semiconductor LM93'...                No
Probing for `National Semiconductor LM94'...                No
Probing for `Winbond W83781D'...                            No
Probing for `Winbond W83782D'...                            No
Probing for `Winbond W83783S'...                            No
Probing for `Winbond W83791D'...                            No
Probing for `Winbond W83792D'...                            No
Probing for `Winbond W83793R/G'...                          No
Probing for `Nuvoton W83795G/ADG'...                        No
Probing for `Winbond W83627HF'...                           No
Probing for `Winbond W83627EHF'...                          No
Probing for `Winbond W83627DHG/W83667HG/W83677HG'...        No
Probing for `Asus AS99127F (rev.1)'...                      No
Probing for `Asus AS99127F (rev.2)'...                      No
Probing for `Asus ASB100 Bach'...                           No
Probing for `Winbond W83L784R/AR/G'...                      No
Probing for `Winbond W83L785R/G'...                         No
Probing for `Genesys Logic GL518SM'...                      No
Probing for `Genesys Logic GL520SM'...                      No
Probing for `Genesys Logic GL525SM'...                      No
Probing for `Analog Devices ADM9240'...                     No
Probing for `Dallas Semiconductor DS1780'...                No
Probing for `National Semiconductor LM81'...                No
Probing for `Analog Devices ADM1026'...                     No
Probing for `Analog Devices ADM1025'...                     No
Probing for `Philips NE1619'...                             No
Probing for `Texas Instruments AMC6821'...                  No
Probing for `Analog Devices ADM1029'...                     No
Probing for `Analog Devices ADM1030'...                     No
Probing for `Analog Devices ADM1031'...                     No
Probing for `Analog Devices ADM1022'...                     No
Probing for `Texas Instruments THMC50'...                   No
Probing for `VIA VT1211 (I2C)'...                           No
Probing for `ITE IT8712F'...                                No
Probing for `ALi M5879'...                                  No
Probing for `SMSC LPC47M15x/192/292/997'...                 Success!
    (confidence 6, driver `smsc47m192')
Probing for `SMSC DME1737'...                               No
Probing for `SMSC SCH5027D-NW'...                           No
Probing for `Fintek F75373S/SG'...                          No
Probing for `Fintek F75375S/SP'...                          No
Probing for `Fintek F75387SG/RG'...                         No
Probing for `Winbond W83791SD'...                           No
Client found at address 0x50
Probing for `Analog Devices ADM1033'...                     No
Probing for `Analog Devices ADM1034'...                     No
Probing for `SPD EEPROM'...                                 Yes
    (confidence 8, not a hardware monitoring chip)
Probing for `EDID EEPROM'...                                No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:
Driver `smsc47m1':
  * ISA bus, address 0x680
    Chip `SMSC LPC47M15x/192/997 Super IO Fan Sensors' (confidence: 9)

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

Driver `smsc47m192':
  * Bus `SMBus I801 adapter at 2000'
    Busdriver `i2c_i801', I2C address 0x2d
    Chip `SMSC LPC47M15x/192/292/997' (confidence: 6)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): Unloading i2c-dev... OK

# sensors

coretemp-isa-0000
Adapter: ISA adapter
Core 0:        +5.0°C  (crit = +90.0°C)
Core 1:        +5.0°C  (crit = +90.0°C)

smsc47m1-isa-0680
Adapter: ISA adapter
fan1:        2560 RPM  (min = 1280 RPM, div = 4)
fan2:        5715 RPM  (min = 1280 RPM, div = 4)

smsc47m192-i2c-15-2d
Adapter: SMBus I801 adapter at 2000
in0:          +2.54 V  (min =  +0.00 V, max =  +3.32 V)
Vcore:        +1.15 V  (min =  +0.00 V, max =  +2.99 V)
  1. 3.3V: +3.23 V (min = +2.97 V, max = +3.63 V)
  2. 5V: +4.95 V (min = +4.50 V, max = +5.50 V)
  3. 12V: +11.88 V (min = +10.81 V, max = +13.19 V)
VCC: +3.23 V (min = +2.97 V, max = +3.63 V) in6: +1.58 V (min = +0.00 V, max = +1.99 V) in7: +1.77 V (min = +0.00 V, max = +2.39 V) SIO Temp: +35.0°C (low = -127.0°C, high = +127.0°C) temp2: +49.0°C (low = +43.0°C, high = +50.0°C) temp3: +41.0°C (low = -127.0°C, high = +127.0°C) cpu0_vid: +2.050 V
ちなみに、sysconfigはこんな感じ
$  cat /etc/sysconfig/lm_sensors


# Generated by sensors-detect on Thu May  3 20:19:00 2012
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="coretemp smsc47m1 smsc47m192"

# For compatibility reasons, modules are also listed individually as variables
#    MODULE_0, MODULE_1, MODULE_2, etc.
# You should use BUS_MODULES and HWMON_MODULES instead if possible.

MODULE_0=coretemp
MODULE_1=smsc47m1
MODULE_2=smsc47m192

Fedora 17

そのままFedora 17に上げてみると、coretempモジュールも正しく認識出来ている模様。
fan2は確か静音化のためにファンをすっこぬいたので(冬だし)、0RPMになっているが一応動いている。
temp2が以前よりも5度程度上昇しているが、ファン回した方がいいかなあ…。
$ sensors

coretemp-isa-0000
Adapter: ISA adapter
Core 0:       +46.0°C  (crit = +125.0°C)
Core 1:       +50.0°C  (crit = +125.0°C)

smsc47m1-isa-0680
Adapter: ISA adapter
fan1:        2824 RPM  (min = 1280 RPM, div = 4)
fan2:           0 RPM  (min = 1280 RPM, div = 4)  ALARM

smsc47m192-i2c-7-2d
Adapter: SMBus I801 adapter at 2000
in0:          +2.54 V  (min =  +0.00 V, max =  +3.32 V)
Vcore:        +1.15 V  (min =  +0.00 V, max =  +2.99 V)
  1. 3.3V: +3.23 V (min = +2.97 V, max = +3.63 V)
  2. 5V: +4.97 V (min = +4.50 V, max = +5.50 V)
  3. 12V: +11.81 V (min = +10.81 V, max = +13.19 V)
VCC: +3.23 V (min = +2.97 V, max = +3.63 V) in6: +1.58 V (min = +0.00 V, max = +1.99 V) in7: +1.77 V (min = +0.00 V, max = +2.39 V) SIO Temp: +37.0°C (low = -127.0°C, high = +127.0°C) temp2: +54.0°C (low = +53.0°C, high = +60.0°C) temp3: +48.0°C (low = -127.0°C, high = +127.0°C) cpu0_vid: +0.000 V

おまけ: acpi_enforce_resources=laxとは?

Linux Kernel 3.6のDocumentation/kernel-parameters.txtより引用すると…
acpi_enforce_resources= [ACPI]
        { strict | lax | no }
        Check for resource conflicts between native drivers
        and ACPI OperationRegions (SystemIO and SystemMemory
        only). IO ports and memory declared in ACPI might be
        used by the ACPI subsystem in arbitrary AML code and
        can interfere with legacy drivers.
        strict (default): access to resources claimed by ACPI
        is denied; legacy drivers trying to access reserved
        resources will fail to bind to device using them.
        lax: access to resources claimed by ACPI is allowed;
        legacy drivers trying to access reserved resources
        will bind successfully but a warning message is logged.
        no: ACPI OperationRegions are not marked as reserved,
        no further checks are performed.
ということで、ACPI経由のデバイスリソースアクセスを許容するという、これまでのデフォルトに戻すためにlaxを指定する必要があるのでした。
近頃はちゃんとドライバ経由でアクセスしなさいってことなのかな…?
OK キャンセル 確認 その他