Ubuntu
linux-source-2.6.20 package

w83627ehf driver does not work on ICH8-based motherboards

Bug #90265 reported by Fastguy
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Hi,

I'm running the latest packages of Ubuntu-Feisty as of March 6th, 2007. Kernel is the default one of this date:
====================================================
root@xen:/etc# uname -a
Linux xen 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
====================================================

I installed lm_sensors package to get some info about what's going on on my harfware. I then used sensors-detect to see which chips I have. Here's the summary output.

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

Driver `eeprom' (should be inserted):
  Detects correctly:
  * Bus `SMBus I801 adapter at 0400'
    Busdriver `i2c-i801', I2C address 0x50
    Chip `eeprom' (confidence: 6)
  * Bus `SMBus I801 adapter at 0400'
    Busdriver `i2c-i801', I2C address 0x52
    Chip `eeprom' (confidence: 6)

  EEPROMs are *NOT* sensors! They are data storage chips commonly
  found on memory modules (SPD), in monitors (EDID), or in some
  laptops, for example.

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:

To make the sensors modules behave correctly, add these lines to
/etc/modules:

#----cut here----
# I2C adapter drivers
i2c-i801
# Chip drivers
eeprom
w83627ehf
#----cut here----

Do you want to add these lines to /etc/modules automatically? (yes/NO)
root@xen:/etc#
===============================================

Then I used modprobe to probe the modules:

==============================
root@xen:/etc# modprobe i2c-i801
root@xen:/etc# modprobe eeprom
root@xen:/etc# modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.20-9-generic/kernel/drivers/hwmon/w83627ehf.ko): No such device
root@xen:/etc#
==============================

As you see, the w83627ehf module should have found the onboard sensor chip, but it doesn't. The end result is that I don't have any sensor info.

I read in some newsgroups that there's a patch for this driver to work OK on P5B's, which was in 2.6.18 mm tree of the kernel. I don't know if it was merged into this 2.6.20 ubuntu kernel. Please let me know if I'm missing something here.

Best regards,

Emre

Revision history for this message
Mark Reitblatt (mark-reitblatt) wrote :

Just to be clear, the name of your computer is xen, but you are not running a xen kernel on this, and this is not running in a xen VM, correct?

Changed in linux-source-2.6.20:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Fastguy (erenoglu) wrote :

Hi Mark,

You're right. the name of the machine is Xen but the kernel is stock Ubuntu Feisty kernel. I will use this machine as Dom0 for my future Xen install.

In fact, I already have Xen 3.0.4 with 2.6.19-4 kernel on this machine, but I didn't mention it to keep things simple. Nevertheless, I have the exact same problem for that kernel also. (I'm using Cedric's repositories for higher version of Xen, i.e. http://cedric.gabriello.fr/ubuntu/ , as original feisty repo has 3.0.3 which is not good for me.

A good place to look for this issue is:
http://lists.lm-sensors.org/pipermail/lm-sensors/2007-February/018798.html

Best regards,

Emre

Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
assignee: nobody → ubuntu-kernel-team
status: Needs Info → Confirmed
Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

I am also trying to use lm-sensors on an Asus P5B Dlx board with the same Winbond chip. I've been getting the same results using the latest Feisty kernel, 2.6.20-14-generic.

I've taken the patch file referenced and applied it to a custom kernel build based on the current linux-source-2.6.20 source package and the '.config' file from the 2.6.20-14-generic kernel. The driver file patched without error, but the patch failed on the Documentation file. I ignored the error and compiled anyway. The patched driver does now recognize the chip and the modprobe returns no erros. All 3 required drivers from sensors-detect appear in lsmod.

I still haven't gotten ls-sensors working, but it doesn't appear to be a driver issue anymore. Now I just neat to play with the configuration.

Let me know if I can be of help getting this into the final release kernel.

Chris

Revision history for this message
aMUSEd (masterofdisharmony) wrote :

On P5B Deluxe the same prob with 2.6.20-15 release kernel
Waiting since 6.10 for this fix :-))
Thx!

Revision history for this message
Gioele Barabucci (gioele) wrote :

Same problem here with a MSI G965MDH-FI motherboard (ICH8DH based) and Feisty amd64

  $ sudo modprobe i2c-i801
  $ sudo modprobe eeprom
  $ sudo modprobe w83627ehf
  FATAL: Error inserting w83627ehf (/lib/modules/2.6.20-15-generic/kernel/drivers/hwmon/w83627ehf.ko): No such device

Revision history for this message
Gioele Barabucci (gioele) wrote :

Shouldn't the description of this bug be changed to something more generic and less Asus-specific?

Revision history for this message
Fastguy (erenoglu) wrote :

I agree with Gioele,

As this chip can also be found on other mainboards, maybe the bug name shall be changed. However, I don't know who can do it. :)

Btw, we are waiting since march for someone to fix this, and i see that some of our fellow users are waiting since 6.10. That's not good!

Best regards,

Emre

Revision history for this message
Gioele Barabucci (gioele) wrote :

Seems like "Edit description" works for this bug report ;)

Revision history for this message
aMUSEd (masterofdisharmony) wrote :

i just found the link with a kernel patch..
http://lists.lm-sensors.org/pipermail/lm-sensors/2006-December/018509.html

maybe this helps...

kind regards!

Revision history for this message
Richie Ward (richies) wrote :

I have Ubuntu 7.10 and I can confirm this bug..
richie@richie-desktop:~$ sudo modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.20-15-generic/kernel/drivers/hwmon/w83627ehf.ko): No such device

Revision history for this message
Richie Ward (richies) wrote :

Also, My motherboard is Asus P5B

(Vanilla one not deluxe)

Revision history for this message
aMUSEd (masterofdisharmony) wrote :

any news about that?

Revision history for this message
Fastguy (erenoglu) wrote :

The only solution I found is to upgrade to kernel 2.6.21 or later.

Emre

Revision history for this message
Kelson (emmanuel-engelhart) wrote :

I confirm this bug too.

Revision history for this message
xfiler (ciccettino) wrote :

idem: feisty on p5b-e

Revision history for this message
srg (lonnman) wrote :

Is this confirmed to work on kernel 2.6.21+ ?

Revision history for this message
Toni Filgueras (toni-fiz) wrote :

Same problem here on an asus p5b running 2.6.20-16-generic
#modprobe w83627ehf
FATAL: Error inserting w83627ehf (/lib/modules/2.6.20-16-generic/kernel/drivers/hwmon/w83627ehf.ko): No such device

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

This was fixed on whichever Ubuntu version went to a Kernel more recent that 2.6.21. I believe 7.10, but definitely fixed by 8.04. This should be closed.

Revision history for this message
wactuary (launchpad-nosnhoj) wrote :

Fixed in versions of Ubuntu that have kernels 2.6.21 or higher.

Changed in linux:
status: Incomplete → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.