public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] lm_sensors and w83627hf not loadable
Date: Sun, 21 Mar 2010 19:19:50 -0500	[thread overview]
Message-ID: <87iq8pnr6h.fsf@newsguy.com> (raw)

I see lots of bug reports about this in several linux OSs but not able
to see a solution.

I've make the propers kernel settings and the w83627hf modules is
built and available in /lib/modules/*
I tried rebuilding the kernel with that stuff built-in.  but then
lm_sensors couldn't even find tools to work with when running
 sensors-detect

  So calling `sensors' just in case it would work:
    # sensors
  No sensors found!
  Make sure you loaded all the kernel drivers you need.
  Try sensors-detect to find out which these are.

Back to a modular kernel:
lm_sensors tells me that w83627hf is the one to load in
/etc/conf.d/lm_sensors.

But any attempt to load it meets with this result (wrapped for mail):
modprobe w83627hf
  FATAL: Error inserting w83627hf 
  (/lib/modules/2.6.33-gentoo/kernel/drivers/hwmon/w83627hf.ko):
   Device or resource busy

Looking at dmesg after running the above command, I find lines like
these (repeated several times):
 [ 1321.715673] w83627hf: Found W83627THF chip at 0x290

 [ 1321.715712] ACPI: I/O resource w83627hf [0x295-0x296] conflicts
 with ACPI region HWMT [0x295-0x296]

 [ 1321.715716] ACPI: If an ACPI driver is available for this device,
 you should use it instead of the native driver

-------        ---------       ---=---       ---------      -------- 

So anyone know what is wrong here?




             reply	other threads:[~2010-03-22  0:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  0:19 Harry Putnam [this message]
2010-03-22  1:10 ` [gentoo-user] Re: lm_sensors and w83627hf not loadable Harry Putnam
2010-03-22  8:59   ` Helmut Jarausch
2010-03-22 13:42     ` Harry Putnam
2010-03-22 16:10       ` Helmut Jarausch
2010-03-22 19:49         ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87iq8pnr6h.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox