On Wed, 26 Apr 2017 18:52:58 +1000, Ralph wrote in message
<d67b7404-6f6b-0cff-bca3-a4582ab9d36f@???>:
>
>
> Arnt Karlsen wrote on 26/04/17 17:26:
> > On Wed, 26 Apr 2017 12:08:48 +1000, Ralph wrote in message
> > <2fab2208-e0dc-27f5-dd3d-f9d7156bbaa7@???>:
> >
> >>
> >>
> >> Arnt Karlsen wrote on 26/04/17 11:18:
> >>> [cut]
> >>
> >> I believe keyboard and mouse needs the "evdev" module to be loaded
> >> before something; certainly before starting X.
> >
> > ..aye: root@box:~# lsmod |grep evdev
> > evdev 24576 26
> > root@box:~# lsmod |grep vdev |grep -v evdev
> > root@box:~# lsmod |grep dev |grep -v evdev
> > input_polldev 16384 1 lis3lv02d
> > ipmi_devintf 20480 0
> > ipmi_msghandler 49152 3
> > ipmi_devintf,ipmi_poweroff,ipmi_watchdog ppdev
> > 20480 0 parport 49152 3 lp,parport_pc,ppdev
> > videodev 180224 3
> > uvcvideo,videobuf2_core,videobuf2_v4l2 media
> > 40960 2 uvcvideo,videodev joydev 20480 0
> > root@box:~#
>
> Yeah, you would do "lsmod | grep -w evdev" only, and apparently it's
> loaded, so probably not the issue. You can check inside initrd image
> that "evdev" is mentioned in the "conf/modules" file to ensure/verify
> that it happens early enough.
>
> Note that "vdev" itself is not a module, but is present in a number
> of pre-pivot init scripts, the vdevd daemon, and its configuration
> files. The vdevd daemon is run twice: once pre-pivot, then that one
> is killed and another is started via the /etc/init.d/vdev script.
>
> >> [cut]
>
> Perhaps /var/log/Xorg.0.log tells something.
..3 of them here:
https://pastebin.com/qsNGW8G0
> And I have this vague
> memory of being in that same situation, but I can't remember the
> resolution.
>
> Ralph.
..aye, had I remembered what I did last time around... ;oD
--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
::
Re: [DNG] ..vdev input in X, was:..…
