FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 03-21-2010, 11:19 PM
Harry Putnam
 
Default lm_sensors and w83627hf not loadable

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?
 
Old 03-22-2010, 12:10 AM
Harry Putnam
 
Default lm_sensors and w83627hf not loadable

Harry Putnam <reader@newsguy.com> writes:

Forgot to give kernel version:
uname -r
2.6.33-gentoo

> 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?

Sorry about the second printing just to show kernel version
 
Old 03-22-2010, 07:59 AM
Helmut Jarausch
 
Default lm_sensors and w83627hf not loadable

On 21 Mar, Harry Putnam wrote:
> Harry Putnam <reader@newsguy.com> writes:
>
> Forgot to give kernel version:
> uname -r
> 2.6.33-gentoo
>
>> 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?

I can only report that I've built a 2.6.33-gentoo kernel with
the device (sensors) Winbond W83627EHF/EF/EHG/EG
built in (not just a module), then ran sensors-detect
and now, xsensor works just fine (on a Phenom-II)

Helmut.

--
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
 
Old 03-22-2010, 12:42 PM
Harry Putnam
 
Default lm_sensors and w83627hf not loadable

Helmut Jarausch <jarausch@igpm.rwth-aachen.de> writes:

> On 21 Mar, Harry Putnam wrote:
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> Forgot to give kernel version:
>> uname -r
>> 2.6.33-gentoo
>>
>>> 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.
>>>

[...]

>
> I can only report that I've built a 2.6.33-gentoo kernel with
> the device (sensors) Winbond W83627EHF/EF/EHG/EG
> built in (not just a module), then ran sensors-detect
> and now, xsensor works just fine (on a Phenom-II)

In my version of 2.6.33-gentoo I don't see that as a choice in
make menuconfig... none of the winbond lines match what you show
above. The last one below is closest and as you see I have built it
in.

| | < > Winbond W83781D, W83782D, W83783S, Asus AS99127F | |
| | < > Winbond W83791D | |
| | < > Winbond W83792D | |
| | < > Winbond W83793 | |
| | < > Winbond W83L785TS-S | |
| | < > Winbond W83L786NG, W83L786NR | |
| | <*> Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF | |
| | <*> Winbond W83627EHF/EHG/DHG, W83667HG

But as you can see I've built in the last two.

After installing that kernel and reboot

The tail of:
sensors-detect

[...]

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627hf':
* ISA bus, address 0x290
Chip `Winbond W83627THF/THG Super IO Sensors' (confidence: 9)

Warning: the required module w83627hf is not currently installed
on your system. If it is built into the kernel then it's OK.
Otherwise, check http://www.lm-sensors.org/wiki/Devices for
driver availability.

No modules to load, skipping modules configuration.

Unloading i2c-dev... OK

And following with:

# sensors

No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.

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

What motheboard are you running:

Here is what `lshw', followed `hwinfo' had to say about my motherboard
Or at least I think thats what this output is:

from lswh:
reader
description: Desktop Computer
product: MS-6728
vendor: MICRO-STAR INC.
version: 2.00
serial: 00000000
width: 32 bits
capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
configuration: chassis=desktop cpus=1
*-core
description: Motherboard
product: MS-6728
vendor: MICRO-STAR INC.
physical id: 0
version: 2.00
serial: 00000000
*-firmware
description: BIOS
vendor: American Megatrends Inc.
physical id: 0
version: V3.A (09/29/2004)
size: 64KiB
capacity: 448KiB
capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification

------- --------- ---=--- --------- --------
from hwinfo:

01: None 00.0: 10105 BIOS
[Created at bios.190]
Unique ID: rdCR.lZF+r4EgHp4
Hardware Class: bios
BIOS Keyboard LED Status:
Scroll Lock: off
Num Lock: on
Caps Lock: off
Serial Port 0: 0x3f8
Serial Port 1: 0x3e8
Parallel Port 0: 0x378
Base Memory: 639 kB
PnP BIOS: @@@0000
MP spec rev 1.4 info:
OEM id: "INTEL"
Product id: "I865G/GE/PE"
1 CPUs (0 disabled)
BIOS32 Service Directory Entry: 0xfdb60
SMBIOS Version: 2.3
BIOS Info: #0
Vendor: "American Megatrends Inc."
Version: "V3.A"
Date: "09/29/2004"
Start Address: 0xf0000
ROM Size: 512 kB
Features: 0x0137000000006fcbde90
ISA supported
PCI supported
PnP supported
APM supported
BIOS flashable
BIOS shadowing allowed
ESCD supported
CD boot supported
Selectable boot supported
BIOS ROM socketed
EDD spec supported
360kB Floppy supported
1.2MB Floppy supported
720kB Floppy supported
2.88MB Floppy supported
Print Screen supported
8042 Keyboard Services supported
Printer Services supported
CGA/Mono Video supported
ACPI supported
USB Legacy supported
AGP supported
LS-120 boot supported
ATAPI ZIP boot supported
BIOS Boot Spec supported
System Info: #1
Manufacturer: "MICRO-STAR INC."
Product: "MS-6728"
Version: "2.00"
Serial: "00000000"
UUID: undefined
Wake-up: 0x04 (Modem Ring)
Board Info: #2
Manufacturer: "MICRO-STAR INC."
Product: "MS-6728"
Version: "2.00"
Serial: "00000000"
 
Old 03-22-2010, 03:10 PM
Helmut Jarausch
 
Default lm_sensors and w83627hf not loadable

Hi Harry,

first of all,
have you enabled
Device-Drivers/Hardware monitoring support/
AMD Phenom/Sempron/Turion/Opteron temperature sensor ?

and then
Winbond W83627EHF/EHG/DHG, W83667HG

I have an ASRock M3A790GXH/128M board.

I'm running the 2.6.33-gentoo kernel, as well.
(It's the first one to support the Phenom (K10) temperature
sensor.)

Helmut.




On 22 Mar, Harry Putnam wrote:
> Helmut Jarausch <jarausch@igpm.rwth-aachen.de> writes:
>
>> On 21 Mar, Harry Putnam wrote:
>>> Harry Putnam <reader@newsguy.com> writes:
>>>
>>> Forgot to give kernel version:
>>> uname -r
>>> 2.6.33-gentoo
>>>
>>>> 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.
>>>>
>
> [...]
>
>>
>> I can only report that I've built a 2.6.33-gentoo kernel with
>> the device (sensors) Winbond W83627EHF/EF/EHG/EG
>> built in (not just a module), then ran sensors-detect
>> and now, xsensor works just fine (on a Phenom-II)
>
> In my version of 2.6.33-gentoo I don't see that as a choice in
> make menuconfig... none of the winbond lines match what you show
> above. The last one below is closest and as you see I have built it
> in.
>
> | | < > Winbond W83781D, W83782D, W83783S, Asus AS99127F | |
> | | < > Winbond W83791D | |
> | | < > Winbond W83792D | |
> | | < > Winbond W83793 | |
> | | < > Winbond W83L785TS-S | |
> | | < > Winbond W83L786NG, W83L786NR | |
> | | <*> Winbond W83627HF, W83627THF, W83637HF, W83687THF, W83697HF | |
> | | <*> Winbond W83627EHF/EHG/DHG, W83667HG
>
> But as you can see I've built in the last two.
>
> After installing that kernel and reboot
>
> The tail of:
> sensors-detect
>
> [...]
>
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
>
> Driver `w83627hf':
> * ISA bus, address 0x290
> Chip `Winbond W83627THF/THG Super IO Sensors' (confidence: 9)
>
> Warning: the required module w83627hf is not currently installed
> on your system. If it is built into the kernel then it's OK.
> Otherwise, check http://www.lm-sensors.org/wiki/Devices for
> driver availability.
>
> No modules to load, skipping modules configuration.
>
> Unloading i2c-dev... OK
>
> And following with:
>
> # sensors
>
> No sensors found!
> Make sure you loaded all the kernel drivers you need.
> Try sensors-detect to find out which these are.
>
> ------- --------- ---=--- --------- --------
>
> What motheboard are you running:
>
> Here is what `lshw', followed `hwinfo' had to say about my motherboard
> Or at least I think thats what this output is:
>
> from lswh:
> reader
> description: Desktop Computer
> product: MS-6728
> vendor: MICRO-STAR INC.
> version: 2.00
> serial: 00000000
> width: 32 bits
> capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp
> configuration: chassis=desktop cpus=1
> *-core
> description: Motherboard
> product: MS-6728
> vendor: MICRO-STAR INC.
> physical id: 0
> version: 2.00
> serial: 00000000
> *-firmware
> description: BIOS
> vendor: American Megatrends Inc.
> physical id: 0
> version: V3.A (09/29/2004)
> size: 64KiB
> capacity: 448KiB
> capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification
>
> ------- --------- ---=--- --------- --------
> from hwinfo:
>
> 01: None 00.0: 10105 BIOS
> [Created at bios.190]
> Unique ID: rdCR.lZF+r4EgHp4
> Hardware Class: bios
> BIOS Keyboard LED Status:
> Scroll Lock: off
> Num Lock: on
> Caps Lock: off
> Serial Port 0: 0x3f8
> Serial Port 1: 0x3e8
> Parallel Port 0: 0x378
> Base Memory: 639 kB
> PnP BIOS: @@@0000
> MP spec rev 1.4 info:
> OEM id: "INTEL"
> Product id: "I865G/GE/PE"
> 1 CPUs (0 disabled)
> BIOS32 Service Directory Entry: 0xfdb60
> SMBIOS Version: 2.3
> BIOS Info: #0
> Vendor: "American Megatrends Inc."
> Version: "V3.A"
> Date: "09/29/2004"
> Start Address: 0xf0000
> ROM Size: 512 kB
> Features: 0x0137000000006fcbde90
> ISA supported
> PCI supported
> PnP supported
> APM supported
> BIOS flashable
> BIOS shadowing allowed
> ESCD supported
> CD boot supported
> Selectable boot supported
> BIOS ROM socketed
> EDD spec supported
> 360kB Floppy supported
> 1.2MB Floppy supported
> 720kB Floppy supported
> 2.88MB Floppy supported
> Print Screen supported
> 8042 Keyboard Services supported
> Printer Services supported
> CGA/Mono Video supported
> ACPI supported
> USB Legacy supported
> AGP supported
> LS-120 boot supported
> ATAPI ZIP boot supported
> BIOS Boot Spec supported
> System Info: #1
> Manufacturer: "MICRO-STAR INC."
> Product: "MS-6728"
> Version: "2.00"
> Serial: "00000000"
> UUID: undefined
> Wake-up: 0x04 (Modem Ring)
> Board Info: #2
> Manufacturer: "MICRO-STAR INC."
> Product: "MS-6728"
> Version: "2.00"
> Serial: "00000000"
>
>

--
Helmut Jarausch

Lehrstuhl fuer Numerische Mathematik
RWTH - Aachen University
D 52056 Aachen, Germany
 
Old 03-22-2010, 06:49 PM
Harry Putnam
 
Default lm_sensors and w83627hf not loadable

Helmut Jarausch <jarausch@igpm.rwth-aachen.de> writes:

> Hi Harry,
>
> first of all,
> have you enabled
> Device-Drivers/Hardware monitoring support/
> AMD Phenom/Sempron/Turion/Opteron temperature sensor ?
>
> and then
> Winbond W83627EHF/EHG/DHG, W83667HG
>
> I have an ASRock M3A790GXH/128M board.
>
> I'm running the 2.6.33-gentoo kernel, as well.
> (It's the first one to support the Phenom (K10) temperature
> sensor.)

Well since I asked about a problem now to occur with a different
driver all together:

From OP:
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

Then the fact that you were able to get yours to work is not really relevant
to the question.

Thanks for the input... but may not be very useful here.

I'm hoping someone else has hit the problem I posted about and has
worked out some way to get it to work.
 

Thread Tools




All times are GMT. The time now is 05:23 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org