All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Richard Purdie <rpurdie@rpsys.net>, linux-acpi@vger.kernel.org
Subject: Re: backlight mystery
Date: Tue, 6 Mar 2007 02:43:12 -0500	[thread overview]
Message-ID: <20070306074312.GC23955@redhat.com> (raw)
In-Reply-To: <20070305233037.0c5727e7.akpm@linux-foundation.org>

On Mon, Mar 05, 2007 at 11:30:37PM -0800, Andrew Morton wrote:
 > 
 > I always get stuff like this coming out when I boot my x86_64 machine:
 > 
 > asus_acpi: Unknown symbol backlight_device_unregister
 > asus_acpi: Unknown symbol backlight_device_register
 > ibm_acpi: Unknown symbol backlight_device_unregister
 > ibm_acpi: Unknown symbol backlight_device_register
 > toshiba_acpi: Unknown symbol backlight_device_unregister
 > toshiba_acpi: Unknown symbol backlight_device_register
 > video: Unknown symbol backlight_device_unregister
 > video: Unknown symbol backlight_device_register
 > 
 > This is a nocoma server, not a laptop.  I'm not sure how those modules are
 > even getting loaded.  The distro is FC4, which might be doing something
 > peculiar.  

I covered this on the list last week.  There's no way to
have a module autoload based on dmi strings or the like,
(Which is the only sane way these modules can determine
 if they need to run).

Given the absense of mechanism, there's a pretty gross hack
in Fedora's rc.sysinit which loads every module in drivers/acpi/*/*
that it finds.  Shameful I know.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-03-06  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06  7:30 backlight mystery Andrew Morton
2007-03-06  7:43 ` Dave Jones [this message]
2007-03-06  7:48   ` Andrew Morton
2007-03-06  7:58     ` Zhao Forrest
2007-03-06 17:10       ` Dave Jones
2007-03-08 16:57         ` Thomas Renninger
2007-06-20  4:35           ` backlight mystery (PATCH to fix asus_acpi loading when no device) Len Brown

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=20070306074312.GC23955@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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.