[01:10] <Kano> also one of my kanotix users had a strange issue: ipw2200 just stopped working from one day to the other, but win still worked with it
[12:03] <kraut> moin
[02:45] <Whoopie> hi, I have the following problem: when gnome-power-manager changes the brightness, there're also acpi events generated (asus_acpi used on my Samsung laptop). but these events are bound to KEY_BRIGHTNESS_UP/DOWN so that the display starts flickering all the time.
[02:45] <Whoopie> the only solution is to kill gnome-power-manager
[02:46] <Whoopie> as the generic backlight device is used, I wonder why these acpi events are generated.
[02:50] <Whoopie> I didn't see this behaviour on feisty, as asus_acpi didn't have backlight support there.
[05:39] <andy_111> hi all
[05:40] <andy_111> can anyone help on kernel modules (a driver for dvb-c)?
[07:03] <Whoopie> anybody /join #ubuntu-laptop
[07:03] <Whoopie> sorry
[07:04] <Whoopie> I'm wondering why echoing something in /sys/class/backlight/asus/brightness generates an "hotkey ATKD" ACPI event? shouldn't these events only be there when the keys are pressed by the user?
[07:24] <mjg59> I assume that the firmware is mad
[07:28] <Whoopie> mjg59: hmm, ok. the samsung DSDT is quite different from other asus DSDTs.
[09:31] <superm1_> kylem, ping.  i had some other info for you regarding unionfs suspicions 
[09:33] <superm1_> kylem, well for when you get back then at least as i'm going to step out for a bit: http://paste.ubuntu-nl.org/39180/  I was able to reproduce the freeze at other times by launching multiple apps on the disk at the same time that ubiquity was actively copying over files.  So that pastebin is my dmesg
[10:31] <Whoopie> mjg59: is it perhaps possible to suppress such events?
[10:33] <mjg59> Whoopie: Probably not trivially. 
[10:33] <Whoopie> mjg59: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=872d83d00f67021e036d75aab3b7c6e3fc7e29ee
[10:34] <Whoopie> this was once the solution the suppress the power button press on S3 resume. Could I use something like this?
[10:34] <mjg59> Not easily
[10:34] <mjg59> In that case the GPE has been fired already - the code just clears it before allowing events to be processed again
[10:34] <mjg59> That's possible in the suspend/resume case, because you have a period where the kernel isn't executing tasks
[10:36] <Whoopie> hmm, ok.