Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: Ошибка запуска службы lm_sensors

  1. #1

    Default Ошибка запуска службы lm_sensors

    Добрый день.
    Не могу завести lm_sensors на openSUSE 13.1
    Code:
    uname -a
    Linux it-suse-mon.studio-41.home 3.11.6-4-default #1 SMP Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) i686 i686 i386 GNU/Linux
    Устанавливаю zypper in sensors , делаю sensors-detect:
    Code:
    it-suse-mon:/ # sensors-detect
    # sensors-detect revision 6170 (2013-05-20 21:25:22 +0200)
    # Board: Gigabyte Technology Co., Ltd. 8IG1000P-G
    
    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):
    Module cpuid loaded successfully.
    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
    AMD Family 16h power sensors...                             No
    Intel digital thermal sensor...                             No
    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'...                                     No
    Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
    Trying family `ITE'...                                      Yes
    Found `ITE IT8712F Super IO Sensors'                        Success!
        (address 0x290, driver `it87')
    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):
    
    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 82801EB ICH5
    Module i2c-dev loaded successfully.
    
    Next adapter: i915 gmbus ssc (i2c-0)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: i915 gmbus vga (i2c-1)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: i915 gmbus panel (i2c-2)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: i915 gmbus dpc (i2c-3)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: i915 gmbus dpb (i2c-4)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: i915 gmbus dpd (i2c-5)
    Do you want to scan it? (yes/NO/selectively):
    
    Next adapter: SMBus I801 adapter at 1400 (i2c-6)
    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 `it87':
      * ISA bus, address 0x290
        Chip `ITE IT8712F Super IO Sensors' (confidence: 9)
    
    Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
    Copy prog/init/lm_sensors.service to /lib/systemd/system
    and run 'systemctl enable lm_sensors.service'
    for initialization at boot time.
    Unloading i2c-dev... OK
    Unloading cpuid... OK
    Из кода видно, что модуль найден.
    Но команда sensors выдает, что
    Code:
    it-suse-mon:/ # sensors
    No sensors found!
    Make sure you loaded all the kernel drivers you need.
    Try sensors-detect to find out which these are.
    В Yast разрешаю запуск lm_sensors, пытаюсь запустить службу:
    HTML Code:
    it-suse-mon:/ # /etc/init.d/lm_sensors start
    redirecting to systemctl start lm_sensors
    Job for lm_sensors.service failed. See 'systemctl status lm_sensors.service' and 'journalctl -xn' for details.
    Служба не запускается, смотрю журнал и вижу ошибку:
    Code:
    it-suse-mon:/ # journalctl -xn
    -- Logs begin at Пн 2014-01-27 20:55:58 YEKT, end at Пн 2014-01-27 22:18:32 YEKT. --
    янв 27 22:18:32 it-suse-mon.studio-41.home kernel: it87: Found IT8712F chip at 0x290, revision 5
    янв 27 22:18:32 it-suse-mon.studio-41.home kernel: it87: Beeping is supported
    янв 27 22:18:32 it-suse-mon.studio-41.home kernel: ACPI Warning: 0x00000295-0x00000296 SystemIO conflicts with Region \IP__ 1 (20130517/utaddress-251)
    янв 27 22:18:32 it-suse-mon.studio-41.home kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: No sensors found!
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: Make sure you loaded all the kernel drivers you need.
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: Try sensors-detect to find out which these are.
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: Failed to start Initialize hardware monitoring sensors.
    -- Subject: Unit lm_sensors.service has failed
    -- Defined-By: systemd
    -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
    -- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
    --
    -- Unit lm_sensors.service has failed.
    --
    -- The result is failed.
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: Unit lm_sensors.service entered failed state.
    it-suse-mon:/ #
    Code:
    it-suse-mon:/ # systemctl status lm_sensors.service
    lm_sensors.service - Initialize hardware monitoring sensors
       Loaded: loaded (/usr/lib/systemd/system/lm_sensors.service; enabled)
       Active: failed (Result: exit-code) since Пн 2014-01-27 22:18:32 YEKT; 7min ago
      Process: 2277 ExecStart=/usr/bin/sensors -s (code=exited, status=1/FAILURE)
      Process: 2274 ExecStart=/sbin/modprobe -qab $BUS_MODULES $HWMON_MODULES (code=exited, status=0/SUCCESS)
     Main PID: 2277 (code=exited, status=1/FAILURE)
    
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: Starting Initialize hardware monitoring sensors...
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: No sensors found!
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: Make sure you loaded all the kernel drivers you need.
    янв 27 22:18:32 it-suse-mon.studio-41.home sensors[2277]: Try sensors-detect to find out which these are.
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: Failed to start Initialize hardware monitoring sensors.
    янв 27 22:18:32 it-suse-mon.studio-41.home systemd[1]: Unit lm_sensors.service entered failed state.
    it-suse-mon:/ #

    Поиск по форуму и "гугление" ничего не дало.
    Помогите разобраться...
    Last edited by Minton; 27-Jan-2014 at 10:21.

  2. #2
    Join Date
    Aug 2009
    Location
    Russia
    Posts
    2,247

    Default Re: Ошибка запуска службы lm_sensors

    А просто sensors (пакет sensors)? Без всякой возни со службами.

  3. #3
    Join Date
    Nov 2008
    Location
    Saint-Petersburg, Russia
    Posts
    1,146

    Default Re: Ошибка запуска службы lm_sensors

    Quote Originally Posted by joneone View Post
    А просто sensors (пакет sensors)? Без всякой возни со службами.
    Читайте внимательнее:
    it-suse-mon:/ # sensors
    No sensors found!
    Make sure you loaded all the kernel drivers you need.
    Try sensors-detect to find out which these are.

    ivanimpuls, а сам модуль it87 точно загружен?
    "Лучше молчать и прослыть дураком, чем открыть рот и развеять все сомнения." Марк Твен.

  4. #4

    Default Re: Ошибка запуска службы lm_sensors

    Добрый день,
    похоже, что нет:
    HTML Code:
    it-suse-mon:/ # modprobe it87
    FATAL: Error inserting it87 (/lib/modules/3.11.6-4-default/kernel/drivers/hwmon/it87.ko): Device or resource busy
    Это похоже на вот эту ошибку:

    HTML Code:
         FAQ: Why did my sensors stop working in F-11 / with kernel 2.6.31 ?  
       Hi all,
    
    In  the 2.6.29 kernel in F-11 and in the mainline 2.6.31 kernel, there is a  change which causes hardware monitoring (also called sensors) to no  longer work on some motherboards. If this is happening for your  motherboard, then when the lm_sensors service is starting you are  probably getting an error like this:
    FATAL: Error inserting it87
    (/lib/modules/2.6.29-15.fc11.x86_64/kernel/drivers/hwmon/it87.ko): Device or
    resource busy
    And if you look at the kernel messages (using the dmesg command in  a terminal for example)  you will probably see something like this:
    ACPI: I/O resource it87 [0x295-0x296] conflicts with ACPI region IP__
    [0x295-0x296]
    ACPI: Device needs an ACPI driver
    With previous kernels hwmon drivers used to drive IO ranges which  were potentially used by the ACPI code  in your BIOS (which is active  not only during but also after boot), we now explicitly check for this  and if the ACPI code claims the IO-ports used by the hwmon chip, we no  longer allow the hwmon driver to load. 
    
    Banging IO-ports of a  chip from 2 different drivers, the Linux hwmon driver and the ACPI code  is a *really* bad idea and can cause all sort of issues (including  things like changing CPU / RAM voltage or clock speed). So the old  behaviour was a really bad idea.
    
    So even though  this change in behaviour makes some people unhappy as to old behaviour  happened to work without problems in their case (by sheer luck really),  this change is really for the best!
    
    If you want to restore the  old behaviour (which might be dangerous) add:  "acpi_enforce_resources=lax" to the kernel cmdline when booting (or add  it in grub.conf to make this permanent).
    
    
    p.s.
    
    Note  that this change actually first appeared in the mainline 2.6.30 kernel,  but due to a bug in 2.6.30, it didn't take effect until 2.6.31, see:
    http://bugzilla.kernel.org/show_bug.cgi?id=13967
    Взято отсюда : http://hansdegoede.livejournal.com/7932.html

    Но тут про другое ядро речь.

    Все-таки попытался вернуть "старое поведение", добавил строчку
    HTML Code:
    GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
    в /etc/default/grub
    после этого обновил grub командой
    HTML Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    Перезагрузка ничего не дала. Поведение то же самое.

    Может быть я grub неправильно обновил?
    В debian есть команда update-grub2, в suse такой команды нет.
    Погугил, нашел вышеуказанную команду.
    Может она не обновляет grub?

  5. #5
    Join Date
    Nov 2008
    Location
    Saint-Petersburg, Russia
    Posts
    1,146

    Default Re: Ошибка запуска службы lm_sensors

    Quote Originally Posted by ivanimpuls View Post
    после этого обновил grub командой
    HTML Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    Перезагрузка ничего не дала. Поведение то же самое.

    Может быть я grub неправильно обновил?
    В debian есть команда update-grub2, в suse такой команды нет.
    Погугил, нашел вышеуказанную команду.
    Может она не обновляет grub?
    Да, она не обновляет grub, она обновляет только его конфигурационный файл. Нужно ещё произвести установку загрузчика с этим обновлённым конфигом с помощью grub2-install, но искренне советую все модификации проводить в модуле "Загрузчик" из состава YaST, он же и обновит всё правильно.
    "Лучше молчать и прослыть дураком, чем открыть рот и развеять все сомнения." Марк Твен.

  6. #6

    Default Re: Ошибка запуска службы lm_sensors

    Попробовал через загрузчик добавить строку
    Code:
    acpi_enforce_resources=lax
    в Yast. Перезагрузился. Никакого эффекта.

  7. #7

    Default Re: Ошибка запуска службы lm_sensors

    Вобщем, так проблему и не решил...
    Снес lm_sensors. "Ниасилил"
    Попробую conky поставить...

  8. #8
    Join Date
    Jan 2011
    Location
    Vladivostok
    Posts
    679

    Default Re: Ошибка запуска службы lm_sensors

    Quote Originally Posted by ivanimpuls View Post
    Вобщем, так проблему и не решил... Снес lm_sensors. "Ниасилил" Попробую conky поставить...
    коньки без сенсоров ничего ж не покажут а по сабжу, сам модуль загружен/загружается?

    modprobe it87

    проверить:

    lsmod

    sensors


    и после sensors-detect он должен был прописаться в /etc/sysconfig/lm_sensors

  9. #9

    Default Re: Ошибка запуска службы lm_sensors

    Ага, про conky, только сейчас почитал, действительно без lm_sensors ничего работать не будет.

    По сабжу - нет не загружается, пишет

    Code:
    it-suse-mon:/etc/sysconfig # modprobe it87
    FATAL: Error inserting it87 (/lib/modules/3.11.6-4-default/kernel/drivers/hwmon/it87.ko): Device or resource busy
    Здесь
    в /etc/sysconfig/lm_sensors
    все прописано.

  10. #10

    Default Re: Ошибка запуска службы lm_sensors

    ЕСТЬ!!!

    в /etc/default/grub

    добавил

    Code:
    GRUB_CMDLINE_LINUX="acpi_enforce_resources=lax"
    и закомментировал

    Code:
    GRUB_CMDLINE_LINUX=""
    Потом обновил grub

    Code:
    grub2-mkconfig -o /boot/grub2/grub.cfg
    После перезагрузки сделал

    Code:
    modprobe it87
    и модуль загрузился!

    Потом в Yast в Управление службами сделал lm_sensors - Enabled и Active.

    И вуаля:
    HTML Code:
    it-suse-mon:~ # sensors
    it8712-isa-0290
    Adapter: ISA adapter
    in0:          +1.57 V  (min =  +0.00 V, max =  +4.08 V)
    in1:          +2.64 V  (min =  +0.00 V, max =  +4.08 V)
    in2:          +3.41 V  (min =  +0.00 V, max =  +4.08 V)
    in3:          +2.61 V  (min =  +0.00 V, max =  +4.08 V)
    in4:          +3.07 V  (min =  +0.00 V, max =  +4.08 V)
    in5:          +1.50 V  (min =  +0.00 V, max =  +4.08 V)
    in6:          +1.28 V  (min =  +0.00 V, max =  +4.08 V)
    in7:          +3.06 V  (min =  +0.00 V, max =  +4.08 V)
    Vbat:         +3.28 V
    fan1:        3515 RPM  (min =    0 RPM, div = 8)
    fan2:           0 RPM  (min =    0 RPM, div = 8)
    fan3:           0 RPM  (min =    0 RPM, div = 8)
    temp1:        +25.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
    temp2:        +25.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermistor
    temp3:        +28.0°C  (low  = +127.0°C, high = +127.0°C)  sensor = thermal diode
    cpu0_vid:    +1.525 V
    intrusion0:  ALARM

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •