http://bugs.freedesktop.org/show_bug.cgi?id=12567
------- Comment #5 from [EMAIL PROTECTED] 2007-09-26 14:16 PST ------- (In reply to comment #4) > If you don't have any apci modules loaded then I suspect the bios is > banging on the HW directly when it gets a lid event. Since these are > thinkpads, I'd suggest loading the thinkpad acpi modules and setting > the event mask to produce only events rather than calling the bios > methods. Obviously something is trashing the state and it's not the > driver (it doesn't get any acpi events), so it's probably the bios. This was my first thought too and I checked this and it doesnt work. I thought it is a driver problem because the driver gets "something" which leads to a new output probe (see the attached log files, the second is taken directly after opening the lid and the driver was triggered by "something"). I have not yet understood how output changes are recognized by the server but something triggers this (without changing the xrandr-visible configuration, the output of xrandr did not change after opening the lid. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. _______________________________________________ xorg-driver-ati mailing list [email protected] http://lists.x.org/mailman/listinfo/xorg-driver-ati
