[solved] UDEV kills Toshiba FN-Keys

[Manu311]

Hi,

I know google spits out millions of results, but I've checked most of them! (I'm at it since 8 hours now) So I more or less give up and ask for help here.
I've got a new Notebook, namely a: Toshiba Satellite Pro L770-14N which is currently hurting my head.
Not a single one of my fn-keys are working - well I should say the volume keys (up and down - NOT mute!!) are working - at least xev recognizes them (they're not bound yet).
Those I'm more serious about are the brighteness Hotkeys (FN-F6 and FN-F7) since the fucking notebook is so bright it hurts my eyes and I have no idea how to turn this lower.
The good thing is the (very old) fnfx is at least recognizing the brightenesslevel and prints it after initialisation - sadly that's all this tool does .
I've compiled every driver I found inside the kernel source (3.3.8-gentoo) and a lot of acpi drivers as well. Sadly all I realy can do is modprobe them and check if xev recognizes them (not that I don't want to do more, I simply don't know what).
So I've got one more thing to say, there are 3 files: keys, lcd and version inside of /proc/acpi/toshiba but I haven't been able to manage how to change the values in there.
And I don't know if they're just dummy values, since my display realy looks like 100% while the lcd says:

[Manu311]

Now I'm surprised. At the end, before I'm going to bed (just now) I thought, well fuck it, I'm going to compile every toshiba driver into the kernel instead of a module and recompile the kernel again.
Well I, rebooted the system to make sure it's still running - pressed the fn-keys and they worked.
Like seriously? I've been working on this shit for 12 hours now, and THAT's the solution? -.-

[Manu311]

Looks like something else caused my "fix".
I've compiled my kernel now again and again and got 2 versions - one with all the drivers I need and one with the fn keys running.
My "complete" version does run even with fn_keys, as long as I do NOT start udev. Sadly I've got no experience with udev and do not realy have a clue how I should track which of the actions udev does causes this.
I've switched the report level of udev to "info" which spammed like 5M of log (actually over 8000 lines).
My kernels do not differ much - so I don't realy have a clue why this happens.
I uploaded the udev-log (actually messages with grep udev) so you can read through what may cause this:
http://tinypaste.com/b1402198

I'm not sure if I need everything that is loaded - much of it is since I thought something is missing - now it looks more like something is too much.
I'll post any information required - just ask.

//EDIT:
I removed all those modules which I thought may help me (including the toshiba_acpi) and tada everything is working.