Hi Michael, Michael Meskes wrote:
>> I think udev takes care of calling modprobe as needed (hence the error >> message I received), for what it’s worth. > > The init script still calls modprobe itself just in case the user is not using > udev. Oh, then the error message came from there. I was speaking nonsense; sorry. (I misinterpreted the text: | As a workaround acpi_fakekey | now sends the generated key press event through the user level input driver and | thus needs CONFIG_INPUT_UINPUT defined in the kernel and, if build as a module, | the uinput module to be loaded. I had thought this was asking the user to 'modprobe uinput', but I realize now it was just pointing out what acpi_fakekey is going to do.) Best wishes, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
