On Friday 06 July 2007 10:38:50 am Bjorn Helgaas wrote: > > should I test the two individually? or just plan on useing both from now > > on? > > I normally disable PnP (both ISA and PCI), should I leave it enabled with > > the newer kernels and this motherboard? > > Ultimately, you should have CONFIG_ACPI=y and CONFIG_PNPACPI=y, and you > should not have to boot with "noisapnp" or "pnpacpi=off". My guess is > that you only need "pnpacpi=off" to work around the current problem. > > At http://linux.lang.hm/linux, I see dmesg logs (with tons of > kobject debug that's useless to me) from 2.6.22-rc4. It would > be useful to have the log from 2.6.22-rc4 with "pnpacpi=off" > (which I expect to work), so we could compare it with the > "2.6.22-rc4.dmesg" log, which I assume a non-working one. > > Linux PNPACPI currently doesn't manage resources quite the same way > Windows does, and that might account for this problem. You might > try this: > > - boot without "pnpacpi=off" (leave PNPACPI enabled) > - before loading the parport_pc driver, do this: > # echo "disable" > /sys/devices/pnp0/00:0a/resources > # echo "enable" > /sys/devices/pnp0/00:0a/resources Sorry, I meant: # echo "disable" > /sys/devices/pnp0/00:0a/resources # echo "clear" > /sys/devices/pnp0/00:0a/resources # echo "enable" > /sys/devices/pnp0/00:0a/resources - 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
