From: Aivils S. <ai...@un...> - 2005-08-31 10:43:14
|
On Otrdiena, 30. Augusts 2005 19:39, Hugo Vanwoerkom wrote: > --- Aivils Stoss <ai...@un...> wrote: > > On Otrdiena, 30. Augusts 2005 13:21, Hugo Vanwoerkom > > > > wrote: > > > --- Aivils Stoss <ai...@un...> wrote: > > > > Hi , All! > > > > > > > > Don't like patched kernel. Ok try out vanilla! > > > > > > In trying this out on vanilla 2.6.11 the installs > > > > went > > > > > more or less OK given some differences between > > > > linux > > > > > versions. > > > > > > But the start of faketty gives no messages. Those > > > ftty[0-9] have to be allocated because they don't > > > exist. > > > > Seems i should add some message. i forgot . > > > > major is INPUT_MAJOR == 13 > > minor is FTTY_MINOR_BASE == 128 > > crw-rw---- 1 root root 13, 128 aug 30 13:54 > > /dev/ftty0 > > owner, group, mode depends from hobbyhorse of system > > operator > > Does the trick. > > But the keyboards are backwards. I.e. the one in front > of monitor1 works on monitor2 and vv. The mice work > correctly. faketty.c code is borowed from evdev.c mostly 1:1. I suppose first registered keyboard have ftty0. However You are not forced to use stright links like /dev/tty50 -> /dev/ftty0 Instead create that symbolic link in runtime. In case of udev usage, You can create new udev rule. You can use old best /dev/ttyXX for 1st X server and old best text mode too. > I changed /etc/hotplug/kbd.conf (vanilla Debian now) > but that seemed to have no effect. cat Yes. Just like evdev, faketty have not runtime steering interface. Just like evdev faketty have mess with replugged USB devices. > /proc/bus/input/devices shows: > /Tue Aug 30-10:49:48HDA8# cat /proc/bus/input/devices > > Also the mouse on monitor1 (=TNT2 AGP with Nvidia > driver and evdev protocol) traces garbage. The mouse > on monitor 2 does not (=MX-440 PCI) faketty should not have any influence to another input interfaces like kbd,mouse,event. It register new input handler only. > > Looks like an elegant solution. > Time shows. Aivils |