No sensors found. Ticket: 1939

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>You must have a SiS PCI bus adapter, but possibly hidden or too new. Please 
>send
>the output of "lcpsi -v" and "lspci -n" to the sensors mailing-list.

>>Probing for ?Winbond W83627HF Super IO Sensors?
>>   Failed! (0x88)

>Could be a Winbond W83627EHF chip. Search your board for it if you have 
>physical
>access. A preliminary, limited driver exists, see our New Drivers page 
>and/or
>contact the mailing-list. We?d need hardware to complete the driver.

>Khali 2005-03-22

Hi,

This is concerning Ticket: 1939.  I do indeed have a Winbond W83627HF.  The 
most recent sensors-detect script does find it:

Probing for `Winbond W83627EHF Super IO Sensors'
  Success... found at address 0x0290

I have downloaded the patch but must admit I am new to the use of the patch 
command.  I have read the man page and am not sure as to what the -p<num> 
should be.  I receive the following:

[root at mj asus]# patch < linux-2.6.12-rc1-i2c-w83627ehf-rc1.diff
can't find file to patch at input line 4
Perhaps you should have used the -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruN linux-2.6.12-rc1/drivers/i2c/chips.orig/Kconfig 
linux-2.6.12-rc1/drivers/i2c/chips/Kconfig
|--- linux-2.6.12-rc1/drivers/i2c/chips.orig/Kconfig    2005-03-18 
12:43:11.000000000 +0100
|+++ linux-2.6.12-rc1/drivers/i2c/chips/Kconfig 2005-03-18 
15:25:49.000000000 +0100
--------------------------
File to patch:

[root at mj asus]# patch -p1 < linux-2.6.12-rc1-i2c-w83627ehf-rc1.diff
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff -ruN linux-2.6.12-rc1/drivers/i2c/chips.orig/Kconfig 
linux-2.6.12-rc1/drivers/i2c/chips/Kconfig
|--- linux-2.6.12-rc1/drivers/i2c/chips.orig/Kconfig    2005-03-18 
12:43:11.000000000 +0100
|+++ linux-2.6.12-rc1/drivers/i2c/chips/Kconfig 2005-03-18 
15:25:49.000000000 +0100
--------------------------
File to patch:

This is probably a very simple fix but as I said I have never used the patch 
command.  What am I doing wrong?  Is there another way I should be doing 
this?  Any assistance is greatly appreciated.

Regards,

Pat




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux