From: "legolas558@users.sourceforge.net" <legolas558@users.sourceforge.net>
To: linux-kernel@vger.kernel.org
Cc: Len Brown <lenb@kernel.org>
Subject: Re: Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c
Date: Sat, 24 Nov 2007 20:14:01 +0100 [thread overview]
Message-ID: <474877F9.3050901@users.sourceforge.net> (raw)
In-Reply-To: <200711232327.33622.lenb@kernel.org>
Len Brown ha scritto:
> On Sunday 21 October 2007 05:43, legolas558@users.sourceforge.net wrote:
>> have emerged lm_sensors but can't get it running - it keeps saying "No
>> sensors found!" and complaining about kernel drivers not properly setup.
>> I have attached the output of sensors-detect, from which it seems that
>> the kernel is OK.
>>
> In this case, getting sensors installed is the opposite of what you want to do.
> The idea is to simplify the system until it works, then figure out what
> simplification made it work.
>
> ie. disable sensors entirely by building a kernel with CONFIG_HWMON=n
>
> If that makes things work, then it is a clue.
> If that was disabled already, then just keep it disabled.
>
It is disabled since when I abandoned the lm_sensors approach; I
remember that I did some more testing with lm_sensors and got almost all
chips identified, although didn't know how to use lm_sensors to generate
some useful logs.
I agree with you that we have to simplify the system down.
Note: when I built kernel 2.6.24-rc3 to see if it is still affected by
bug #9147, CONFIG_HWMON was enabled instead (and the problem was
verified anyway). I don't recall how that setting got enabled, however I
did not enable it manually and I was not enabling lm_sensors support.
Best regards,
--
Daniele C.
> cheers,
> -Len
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2007-11-24 19:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 21:42 [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c legolas558
2007-10-11 8:04 ` Laptop keyboard unusable when ACPI is active was " legolas558
2007-10-12 11:52 ` Laptop keyboard unusable when ACPI is active legolas558
2007-11-22 7:24 ` legolas558
2007-11-24 4:21 ` Len Brown
2007-11-24 19:08 ` legolas558
2007-10-18 19:52 ` Laptop keyboard unusable when ACPI is active was Re: [2.6.22] i8042, ACPI, ipw2100 and issues reported by psmouse.c atkbd.c Pavel Machek
2007-10-20 11:47 ` legolas558
2007-10-20 18:33 ` Pavel Machek
2007-10-21 9:43 ` legolas558
2007-11-24 4:27 ` Len Brown
2007-11-24 19:14 ` legolas558 [this message]
2007-10-21 11:07 ` legolas558
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=474877F9.3050901@users.sourceforge.net \
--to=legolas558@users.sourceforge.net \
--cc=lenb@kernel.org \
--cc=linux-kernel@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.