Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
* Marco d'Itri <[EMAIL PROTECTED]> [2006-03-09 00:53]: > modprobe -r mousedev > # set udev_log="debug" in /etc/udev/udev.conf > /etc/init.d/udev restart > echo add > /sys/class/input/input2/uevent > # restore udev.conf Okay, again. I did this and the mouse showed up in /dev/hotplug.log, but /dev/

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
For the record: 00:45 you need to comment the line starting with ENV{PHYSDEVDRIVER} in /etc/udev/hotplug.rules 00:45 I will ask Kay about how to fix this properly 00:47 you're right! 00:47 When I dod that, the module gets loaded after "echo add > /sys/..." 00:48 yes, I know that it works :-)

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
* Marco d'Itri <[EMAIL PROTECTED]> [2006-03-09 00:53]: > > $ modprobe -n -v --first-time > > input:b0011v0002p0001e-e0,1,2,k110,111,112,r0,1,amlsfw > > So why does it say it's loading mousedev.ko when it's not? > Because you used -n. So module would have been loaded. Okay, it loads the module

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Marco d'Itri
On Mar 09, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > $ modprobe -n -v --first-time > input:b0011v0002p0001e-e0,1,2,k110,111,112,r0,1,amlsfw > So why does it say it's loading mousedev.ko when it's not? Because you used -n. So module would have been loaded. Next try: modprobe -r mousedev

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
* Marco d'Itri <[EMAIL PROTECTED]> [2006-03-08 23:26]: > For the next test, remove the module and then try to manually load with > modprobe the $MODALIAS string. Okay, that's pretty interesting. I did: $ modprobe -n -v --first-time input:b0011v0002p0001e-e0,1,2,k110,111,112,r0,1,amlsfw WARN

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
* Martin Michlmayr <[EMAIL PROTECTED]> [2006-03-06 21:58]: > # modprobe -n -v --first-time input:b0011v0002p0001e-e0,1,2,k110,111, BTW, I think this command line was cut off. The full string is: input:b0011v0002p0001e-e0,1,2,k110,111,112,r0,1,amlsfw When I use the string above, I get

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Marco d'Itri
On Mar 08, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > echo add > /sys/class/input/input2/uevent This one is enough, we just need a random mouse. What you write to the file is not important. > and nothing happens, i.e. /dev/input still doesn't exist. So now we know that the problem is not trans

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-08 Thread Martin Michlmayr
* Marco d'Itri <[EMAIL PROTECTED]> [2006-03-07 01:29]: > So you need to understand why the modules is not being loaded at boot > time. Okay, so I reboot and do: echo add > /sys/class/input/input0/uevent echo add > /sys/class/input/input1/uevent echo add > /sys/class/input/input2/uevent echo add >

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-06 Thread Marco d'Itri
On Mar 06, Martin Michlmayr <[EMAIL PROTECTED]> wrote: > 21:53 < Md> tbm: so the alias is there, but it's not matching. please > send to the BTS the output of modprobe and grep > > [at this point I had loaded mousedev manually already] > > # modprobe -n -v --first-time input:b0011v0002p0001e

Bug#355626: 2.6.16 needs load_input_modules too

2006-03-06 Thread Martin Michlmayr
21:53 < Md> tbm: so the alias is there, but it's not matching. please send to the BTS the output of modprobe and grep [at this point I had loaded mousedev manually already] # modprobe -n -v --first-time input:b0011v0002p0001e-e0,1,2,k110,111, WARNING: Not loading blacklisted module evbug insm