All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doru Petrescu <pdoru@evox.ro>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] asus_atk0110 not detecting anything on P5LD2EB-DHS
Date: Mon, 26 Apr 2010 14:27:53 +0000	[thread overview]
Message-ID: <1272292073.21942.607.camel@localhost> (raw)
In-Reply-To: <k2r68676e01004260718y3c0c397bpcf1892a7ae30b9f5@mail.gmail.com>

atk0110 doesn't add anything in /sys/class/hwmon
the only thing there (hwmon0) is provided by eeepc_laptop module.

I will try a newer kernel.

thx
D>



On Mon, 2010-04-26 at 17:18, Luca Tettamanti wrote:
> Please keep the list in CC
> 
> On Sun, Apr 25, 2010 at 11:33 PM, Doru Petrescu <pdoru@evox.ro> wrote:
> > I have an ASSUS EEE PC (mini desktop) B202, dmidecode say "P5LD2EB-DHS"
> > for motherboard. it used to work with w83627ehf.
> 
> CPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region
> HWRE [0x290-0x299]
> ACPI: If an ACPI driver is available for this device, you should use
> it instead of the native driver
> 
> This is expected.
> 
> > now I tried asus_atk0110 and it doesn't detect anything, it doesn't
> > complain of anything. completly silent.
> 
> The driver used to be silent if everything went well (and debug was disabled).
> Is there anything under /sys/class/hwmon?
> 
> > i'm sending you the DSDT tables and dmidecode. maybe you can figure it
> > out.
> 
> The interface is there; you should try a newer kernel: I've fixed a
> few detection bugs since .31.
> If possible enable HWMON_DEBUG_CHIP
> 
> Luca


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2010-04-26 14:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26 14:18 [lm-sensors] asus_atk0110 not detecting anything on P5LD2EB-DHS Luca Tettamanti
2010-04-26 14:27 ` Doru Petrescu [this message]
2010-04-26 14:44 ` Luca Tettamanti

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=1272292073.21942.607.camel@localhost \
    --to=pdoru@evox.ro \
    --cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.