SEO

Hi u all

On a gentoo ( kernel 2.6.19-r5 ), I'm trying to get lmsensors to
work.sensors-detect works fine, but when I try to load `w83627ehf' ,
I get :

"localhost lm_sensors-3.0.1 # modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.19-gentoo-r5/kernel/
drivers/hwmon/w83627ehf.ko): No such device"

in the ubuntu distro, lm-sensors works .

Here is part of sensors-detect output :
******************************************
"Some Super I/O chips may also contain 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 `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... Yes
Found `Winbond W83627DHG Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'... No
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Fintek'... No

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

Driver `w83627ehf' (should be inserted):
Detects correctly:
* ISA bus address 0x0290 (Busdriver `i2c-isa')
Chip `Winbond W83627DHG Super IO Sensors' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:
......
.....
----cut here----
# I2C adapter drivers
# Chip drivers
modprobe w83627ehf
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----end cut here----
**************************************************
and, obviously :

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

Any idea would be very welcome
Thanks a lot,

jf

jef wrote:
> Hi u all
>
> On a gentoo ( kernel 2.6.19-r5 ), I'm trying to get lmsensors to
> work.sensors-detect works fine, but when I try to load `w83627ehf' ,
> I get :
>
> "localhost lm_sensors-3.0.1 # modprobe w83627ehf
> FATAL: Error inserting w83627ehf (/lib/modules/2.6.19-gentoo-r5/kernel/
> drivers/hwmon/w83627ehf.ko): No such device"
>
> in the ubuntu distro, lm-sensors works .
>
> Here is part of sensors-detect output :
> ******************************************
> Found `Winbond W83627DHG Super IO Sensors' Success!
> (address 0x290, driver `w83627ehf')

Could be that you are using an older kernel on the Gentoo than what is on the
ububtu and those the driver don't support your hardware.


--

//Aho

Le Sat, 08 Mar 2008 19:24:58 +0100, J.O. Aho a écritÂ*:

> jef wrote:
>> Hi u all
>>
>> On a gentoo ( kernel 2.6.19-r5 ), I'm trying to get lmsensors to
>> work.sensors-detect works fine, but when I try to load `w83627ehf' , I
>> get :
>>
>> "localhost lm_sensors-3.0.1 # modprobe w83627ehf FATAL: Error inserting
>> w83627ehf (/lib/modules/2.6.19-gentoo-r5/kernel/
>> drivers/hwmon/w83627ehf.ko): No such device"
>>
>> in the ubuntu distro, lm-sensors works .
>>
>> Here is part of sensors-detect output :
>> ****************************************** Found `Winbond W83627DHG
>> Super IO Sensors' Success!
>> (address 0x290, driver `w83627ehf')
>
> Could be that you are using an older kernel on the Gentoo than what is
> on the ububtu and those the driver don't support your hardware.

Yes, maybe, ubuntu kernel is 2.6.22 , and the gentoo one is 2.6.19 . But,
since the driver exists, I thought it was ok
I'll try to get another driver .

jf

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <47d30da3$0$13888$426a74cc@news.free.fr>, jef wrote:

[snip]
> Yes, maybe, ubuntu kernel is 2.6.22 , and the gentoo one is 2.6.19 . But,
> since the driver exists, I thought it was ok
> I'll try to get another driver .

A more sensible approach would be to do an emerge --sync and upgrade your
Gentoo kernel. This would automatically bring in updates to any associated
drivers, as well as the one causing you a problem.
- --
Regards

Dave [RLU#314465]
================================================== ====
dwnoon@spamtrap.ntlworld.com (David W Noon)
Remove spam trap to reply via e-mail.
================================================== ====

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFH0xdA9MqaUJQw2MkRAocPAJsEZpiEwNQp8ebLvuNFtp 6alA08bwCfSJp3
9pSM0h3J8pb6oQm/RcrSXa4=
=RrXf
-----END PGP SIGNATURE-----

Le Sat, 08 Mar 2008 23:15:52 +0000, David W Noon a écritÂ*:

> In message <47d30da3$0$13888$426a74cc@news.free.fr>, jef wrote:
>
> [snip]
>
> A more sensible approach would be to do an emerge --sync and upgrade
> your Gentoo kernel. This would automatically bring in updates to any
> associated drivers, as well as the one causing you a problem. - --
> Regards
>
> Dave [RLU#314465]

That's what I did at first, but I have another problem with emerge --sync
( I was about to open another thread for that ) :
************************
localhost jf # emerge --sync
WARNING: usage of RSYNC_TIMEOUT is deprecated, use
PORTAGE_RSYNC_EXTRA_OPTS instead
WARNING: usage of RSYNC_RETRIES is deprecated, use PORTAGE_RSYNC_RETRIES
instead
>>> Starting rsync with rsync://64.127.121.98/gentoo-portage...
>>> Checking server timestamp ...
rsync: --filter=H_**/files/digest-*: unknown option
rsync error: syntax or usage error (code 1) at main.c(1013)

!!! Rsync has reported that there is a syntax error. Please ensure
!!! that your SYNC statement is proper.
!!! SYNC=rsync://rsync.gentoo.org/gentoo-portage
**************************

thanks again ,
jf


localhost jf #
************************************

jef wrote:
> Le Sat, 08 Mar 2008 23:15:52 +0000, David W Noon a écrit :
>
>> In message <47d30da3$0$13888$426a74cc@news.free.fr>, jef wrote:
>>
>> [snip]
>>
>> A more sensible approach would be to do an emerge --sync and upgrade
>> your Gentoo kernel. This would automatically bring in updates to any
>> associated drivers, as well as the one causing you a problem. - --
>> Regards
>>
>> Dave [RLU#314465]
>
> That's what I did at first, but I have another problem with emerge --sync
> ( I was about to open another thread for that ) :
> ************************
> localhost jf # emerge --sync
> WARNING: usage of RSYNC_TIMEOUT is deprecated, use
> PORTAGE_RSYNC_EXTRA_OPTS instead
> WARNING: usage of RSYNC_RETRIES is deprecated, use PORTAGE_RSYNC_RETRIES
> instead
>>>> Starting rsync with rsync://64.127.121.98/gentoo-portage...
>>>> Checking server timestamp ...
> rsync: --filter=H_**/files/digest-*: unknown option
> rsync error: syntax or usage error (code 1) at main.c(1013)
>
> !!! Rsync has reported that there is a syntax error. Please ensure
> !!! that your SYNC statement is proper.
> !!! SYNC=rsync://rsync.gentoo.org/gentoo-portage

Seems like you missed to update your /etc/make.conf after you last updated
portage, I suggest you start to fix the make.conf (look at the example file),
remove all custom options you set for syncing.

--

//Aho

Le Sun, 09 Mar 2008 09:58:32 +0100, J.O. Aho a écritÂ*:

> Seems like you missed to update your /etc/make.conf after you last
> updated portage, I suggest you start to fix the make.conf (look at the
> example file), remove all custom options you set for syncing.

thanks, but it doesn't work . I've even tried the example file, I still
get the same message .

jf