On 3/6/07, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
On Tue, 6 Mar 2007 02:43:12 -0500 Dave Jones <davej@xxxxxxxxxx> wrote: > 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 I thought it might be something like that. I'm a bit surprised that we can't get at the DMI stuff from userspace, or export it from the kernel. But whatever.
I have a question: why can't we get at the DMI stuff from userspace since "dmidecode" is a tool in userspace? Thanks, Forrest - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
