Menu
▾
▴
linuxconsole-dev
|
From: Zoltan B. <zb...@fr...> - 2006-06-25 12:14:46
|
Hi,
I just noticed that faketty isn't needed with Xorg 7.x.
The following section works like a charm for a keyboard,
nothing else is needed.
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "Device" "/dev/input/eventX"
Option "XkbLayout" "hu"
EndSection
The proper eventX device is registered in /proc/bus/input/devices
and as with the kbd driver, multiple sections can be listed
and assigned to the same server, e.g. the PS/2 keyboard
and the BTTV remote is assigned to one X server,
the USB keyboard's two devices (normal keyboard and
the multimedia keys are separated) are assigned to the
other server.
Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi
|
|
From: Aivils S. <ai...@un...> - 2006-06-26 08:30:50
|
On Sv=E7tdiena, 25. J=FBnijs 2006 15:14, Zoltan Boszormenyi wrote: > Hi, > > I just noticed that faketty isn't needed with Xorg 7.x. I think our task was seting up a public opinion. Now that task is done. Manner, how to we propogate that, is weird but works ;o) Aivils |
|
From: Hugo V. <hvw...@ya...> - 2006-06-27 20:59:57
|
Zoltan Boszormenyi <zb...@fr...> wrote: Hi,
I just noticed that faketty isn't needed with Xorg 7.x.
The following section works like a charm for a keyboard,
nothing else is needed.
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "Device" "/dev/input/eventX"
Option "XkbLayout" "hu"
EndSection
The proper eventX device is registered in /proc/bus/input/devices
and as with the kbd driver, multiple sections can be listed
and assigned to the same server, e.g. the PS/2 keyboard
and the BTTV remote is assigned to one X server,
the USB keyboard's two devices (normal keyboard and
the multimedia keys are separated) are assigned to the
other server.
And what is the vt set at then in gdm.conf for the other keyboards?
Hugo
---------------------------------
Yahoo! Sports Fantasy Football 06 - Go with the leader. Start your league today! |
|
From: Zoltan B. <zb...@fr...> - 2006-06-27 22:04:19
|
Hugo Vanwoerkom =EDrta: > > > */Zoltan Boszormenyi <zb...@fr...>/* wrote: > > Hi, > > I just noticed that faketty isn't needed with Xorg 7.x. > The following section works like a charm for a keyboard, > nothing else is needed. > > Section "InputDevice" > Identifier "Keyboard0" > Driver "evdev" > Option "Device" "/dev/input/eventX" > Option "XkbLayout" "hu" > EndSection > > The proper eventX device is registered in /proc/bus/input/devices > and as with the kbd driver, multiple sections can be listed > and assigned to the same server, e.g. the PS/2 keyboard > and the BTTV remote is assigned to one X server, > the USB keyboard's two devices (normal keyboard and > the multimedia keys are separated) are assigned to the > other server. > > And what is the vt set at then in gdm.conf for the other keyboards? > > Hugo Nothing, but "-sharevts" is needed. Same for faketty if I don't specify "vtX" on the parameter line and use Option "Device" "/dev/fttyN" instead. But some bug may still exist in the X evdev driver as hungarian layout doesn't work correctly. E.g. Option "XkbModel" "pc105" makes RightAlt behave as Enter and without it (e.g. working as pc104), my i-acute button doesn't work. So, XOrg is only starting to get there, I switched back to faketty for now. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
|
From: Hugo V. <hvw...@ya...> - 2006-07-07 13:03:49
|
--- Zoltan Boszormenyi <zb...@fr...> wrote:
> Hugo Vanwoerkom �rta:
> >
> >
> > */Zoltan Boszormenyi <zb...@fr...>/*
> wrote:
> >
> > Hi,
> >
> > I just noticed that faketty isn't needed with
> Xorg 7.x.
> > The following section works like a charm for a
> keyboard,
> > nothing else is needed.
> >
> > Section "InputDevice"
> > Identifier "Keyboard0"
> > Driver "evdev"
> > Option "Device" "/dev/input/eventX"
> > Option "XkbLayout" "hu"
> > EndSection
> >
> > The proper eventX device is registered in
> /proc/bus/input/devices
> > and as with the kbd driver, multiple sections
> can be listed
> > and assigned to the same server, e.g. the PS/2
> keyboard
> > and the BTTV remote is assigned to one X
> server,
> > the USB keyboard's two devices (normal
> keyboard and
> > the multimedia keys are separated) are
> assigned to the
> > other server.
> >
> > And what is the vt set at then in gdm.conf for the
> other keyboards?
> >
> > Hugo
>
> Nothing, but "-sharevts" is needed. Same for faketty
> if I don't specify "vtX" on the parameter line and
> use
> Option "Device" "/dev/fttyN" instead.
>
> But some bug may still exist in the X evdev driver
> as hungarian layout doesn't work correctly.
> E.g. Option "XkbModel" "pc105" makes RightAlt
> behave as Enter and without it (e.g. working as
> pc104),
> my i-acute button doesn't work.
>
> So, XOrg is only starting to get there, I switched
> back to faketty for now.
>
>
I just tried this with good success. But I only have 2
monitors/keybds/mice.
The keyboards are both IBM Model M's. Mine is now 13
years old and the other I bought for $57 new.
Also I only need dead keys for us-intl config.
So Faketty is gone and xorg.conf relevant parts
becomes:
...
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "Device"
"/dev/input/event0"
Option "XkbLayout" "us_intl"
EndSection
...
Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device"
"/dev/input/event1"
Option "XkbLayout" "us_intl"
EndSection
...
And the relevant parts of gdm.conf.1 are:
for the primary video console:
...
command=/usr/bin/X1 :0 -layout X1 -dpi 110
-deferglyphs 16 -isolateDevice \"PCI:0:10:0\" vt7
...
and for the alternate console:
...
command=/usr/bin/X0 :1 -layout X0 -dpi 110
-deferglyphs 16 -isolateDevice \"PCI:1:0:0\" -sharevts
...
but I don't think -sharevts is necessary because there
are none there.
It seems to work well:
xserver-xorg 7.0.22
Debian Sid (unstable)
NVIDIA-Linux-x86-1.0-8762
Regards,
Hugo
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
|
From: Hugo V. <hvw...@ya...> - 2006-07-07 13:07:10
|
--- Zoltan Boszormenyi <zb...@fr...> wrote:
> Hugo Vanwoerkom �rta:
> >
> >
> > */Zoltan Boszormenyi <zb...@fr...>/*
> wrote:
> >
> > Hi,
> >
> > I just noticed that faketty isn't needed with
> Xorg 7.x.
> > The following section works like a charm for a
> keyboard,
> > nothing else is needed.
> >
> > Section "InputDevice"
> > Identifier "Keyboard0"
> > Driver "evdev"
> > Option "Device" "/dev/input/eventX"
> > Option "XkbLayout" "hu"
> > EndSection
> >
> > The proper eventX device is registered in
> /proc/bus/input/devices
> > and as with the kbd driver, multiple sections
> can be listed
> > and assigned to the same server, e.g. the PS/2
> keyboard
> > and the BTTV remote is assigned to one X
> server,
> > the USB keyboard's two devices (normal
> keyboard and
> > the multimedia keys are separated) are
> assigned to the
> > other server.
> >
> > And what is the vt set at then in gdm.conf for the
> other keyboards?
> >
> > Hugo
>
> Nothing, but "-sharevts" is needed. Same for faketty
> if I don't specify "vtX" on the parameter line and
> use
> Option "Device" "/dev/fttyN" instead.
>
> But some bug may still exist in the X evdev driver
> as hungarian layout doesn't work correctly.
> E.g. Option "XkbModel" "pc105" makes RightAlt
> behave as Enter and without it (e.g. working as
> pc104),
> my i-acute button doesn't work.
>
> So, XOrg is only starting to get there, I switched
> back to faketty for now.
>
>
I just tried this with good success. But I only have 2
monitors/keybds/mice.
The keyboards are both IBM Model M's. Mine is now 13
years old and the other I bought for $57 new.
Also I only need dead keys for us-intl config.
So Faketty is gone and xorg.conf relevant parts
becomes:
...
Section "InputDevice"
Identifier "Keyboard0"
Driver "evdev"
Option "Device"
"/dev/input/event0"
Option "XkbLayout" "us_intl"
EndSection
...
Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device"
"/dev/input/event1"
Option "XkbLayout" "us_intl"
EndSection
...
And the relevant parts of gdm.conf.1 are:
for the primary video console:
...
command=/usr/bin/X1 :0 -layout X1 -dpi 110
-deferglyphs 16 -isolateDevice \"PCI:0:10:0\" vt7
...
and for the alternate console:
...
command=/usr/bin/X0 :1 -layout X0 -dpi 110
-deferglyphs 16 -isolateDevice \"PCI:1:0:0\" -sharevts
...
but I don't think -sharevts is necessary because there
are none there.
It seems to work well:
xserver-xorg 7.0.22
Debian Sid (unstable)
NVIDIA-Linux-x86-1.0-8762
Regards,
Hugo
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
|
From: Zoltan B. <zb...@fr...> - 2006-07-07 18:33:10
|
Hugo Vanwoerkom =EDrta: > --- Zoltan Boszormenyi <zb...@fr...> wrote: > > =20 >> Hugo Vanwoerkom =EF=BF=BDrta: >> =20 >>> */Zoltan Boszormenyi <zb...@fr...>/* >>> =20 >> wrote: >> =20 >>> Hi, >>> >>> I just noticed that faketty isn't needed with >>> =20 >> Xorg 7.x. >> =20 >>> The following section works like a charm for a >>> =20 >> keyboard, >> =20 >>> nothing else is needed. >>> >>> Section "InputDevice" >>> Identifier "Keyboard0" >>> Driver "evdev" >>> Option "Device" "/dev/input/eventX" >>> Option "XkbLayout" "hu" >>> EndSection >>> >>> The proper eventX device is registered in >>> =20 >> /proc/bus/input/devices >> =20 >>> and as with the kbd driver, multiple sections >>> =20 >> can be listed >> =20 >>> and assigned to the same server, e.g. the PS/2 >>> =20 >> keyboard >> =20 >>> and the BTTV remote is assigned to one X >>> =20 >> server, >> =20 >>> the USB keyboard's two devices (normal >>> =20 >> keyboard and >> =20 >>> the multimedia keys are separated) are >>> =20 >> assigned to the >> =20 >>> other server. >>> >>> And what is the vt set at then in gdm.conf for the >>> =20 >> other keyboards? >> =20 >>> Hugo >>> =20 >> Nothing, but "-sharevts" is needed. Same for faketty >> if I don't specify "vtX" on the parameter line and >> use >> Option "Device" "/dev/fttyN" instead. >> >> But some bug may still exist in the X evdev driver >> as hungarian layout doesn't work correctly. >> E.g. Option "XkbModel" "pc105" makes RightAlt >> behave as Enter and without it (e.g. working as >> pc104), >> my i-acute button doesn't work. >> >> So, XOrg is only starting to get there, I switched >> back to faketty for now. >> >> >> =20 > > I just tried this with good success. But I only have 2 > monitors/keybds/mice. > The keyboards are both IBM Model M's. Mine is now 13 > years old and the other I bought for $57 new. > Also I only need dead keys for us-intl config. > > So Faketty is gone and xorg.conf relevant parts > becomes: > > ... > Section "InputDevice" > Identifier "Keyboard0" > Driver "evdev" > Option "Device" =20 > "/dev/input/event0" > Option "XkbLayout" "us_intl" > EndSection > ... > Section "InputDevice" > Identifier "Keyboard1" > Driver "evdev" > Option "Device" =20 > "/dev/input/event1" > Option "XkbLayout" "us_intl" > EndSection > ... > =20 I replaced the 'Option "Device" ... ' lines with 'Option "Phys" "..."', it gives the same effect but with higher persistency. It turned out that modprobe processes race with each other and bttv and USB HID devices change their places (both /dev/fttyN and /dev/input/eventN) depending on the load order. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
|
From: Zoltan B. <zb...@fr...> - 2006-07-08 05:24:27
|
Zoltan Boszormenyi =C3=ADrta: > Hugo Vanwoerkom =C3=ADrta: > =20 >> --- Zoltan Boszormenyi <zb...@fr...> wrote: >> >> =20 >> =20 >>> Hugo Vanwoerkom =C3=AF=C2=BF=C2=BDrta: >>> =20 >>> =20 >>>> */Zoltan Boszormenyi <zb...@fr...>/* >>>> =20 >>>> =20 >>> wrote: >>> =20 >>> =20 >>>> Hi, >>>> >>>> I just noticed that faketty isn't needed with >>>> =20 >>>> =20 >>> Xorg 7.x. >>> =20 >>> =20 >>>> The following section works like a charm for a >>>> =20 >>>> =20 >>> keyboard, >>> =20 >>> =20 >>>> nothing else is needed. >>>> >>>> Section "InputDevice" >>>> Identifier "Keyboard0" >>>> Driver "evdev" >>>> Option "Device" "/dev/input/eventX" >>>> Option "XkbLayout" "hu" >>>> EndSection >>>> >>>> The proper eventX device is registered in >>>> =20 >>>> =20 >>> /proc/bus/input/devices >>> =20 >>> =20 >>>> and as with the kbd driver, multiple sections >>>> =20 >>>> =20 >>> can be listed >>> =20 >>> =20 >>>> and assigned to the same server, e.g. the PS/2 >>>> =20 >>>> =20 >>> keyboard >>> =20 >>> =20 >>>> and the BTTV remote is assigned to one X >>>> =20 >>>> =20 >>> server, >>> =20 >>> =20 >>>> the USB keyboard's two devices (normal >>>> =20 >>>> =20 >>> keyboard and >>> =20 >>> =20 >>>> the multimedia keys are separated) are >>>> =20 >>>> =20 >>> assigned to the >>> =20 >>> =20 >>>> other server. >>>> >>>> And what is the vt set at then in gdm.conf for the >>>> =20 >>>> =20 >>> other keyboards? >>> =20 >>> =20 >>>> Hugo >>>> =20 >>>> =20 >>> Nothing, but "-sharevts" is needed. Same for faketty >>> if I don't specify "vtX" on the parameter line and >>> use >>> Option "Device" "/dev/fttyN" instead. >>> >>> But some bug may still exist in the X evdev driver >>> as hungarian layout doesn't work correctly. >>> E.g. Option "XkbModel" "pc105" makes RightAlt >>> behave as Enter and without it (e.g. working as >>> pc104), >>> my i-acute button doesn't work. >>> >>> So, XOrg is only starting to get there, I switched >>> back to faketty for now. >>> >>> >>> =20 >>> =20 >> I just tried this with good success. But I only have 2 >> monitors/keybds/mice. >> The keyboards are both IBM Model M's. Mine is now 13 >> years old and the other I bought for $57 new. >> Also I only need dead keys for us-intl config. >> >> So Faketty is gone and xorg.conf relevant parts >> becomes: >> >> ... >> Section "InputDevice" >> Identifier "Keyboard0" >> Driver "evdev" >> Option "Device" =20 >> "/dev/input/event0" >> Option "XkbLayout" "us_intl" >> EndSection >> ... >> Section "InputDevice" >> Identifier "Keyboard1" >> Driver "evdev" >> Option "Device" =20 >> "/dev/input/event1" >> Option "XkbLayout" "us_intl" >> EndSection >> ... >> =20 >> =20 > > I replaced the 'Option "Device" ... ' lines with > 'Option "Phys" "..."', it gives the same effect but > with higher persistency. It turned out that modprobe > processes race with each other and bttv and USB HID > devices change their places (both /dev/fttyN and > /dev/input/eventN) depending on the load order. > =20 And for my non-working iacute button, I needed this: https://launchpad.net/distros/ubuntu/+source/xkeyboard-config/+bug/42846 I had to put this only line in /usr/share/X11/xkb/keycodes/evdev : <LSGT> =3D 94 And the only key that wasn't working before now works with evdev. Bye-bye faketty. :-) Best regards, Zolt=C3=A1n B=C3=B6sz=C3=B6rm=C3=A9nyi |
|
From: Hugo V. <hvw...@ya...> - 2006-07-08 14:19:13
|
--- Zoltan Boszormenyi <zb...@fr...> wrote: > Zoltan Boszormenyi �rta: > > Hugo Vanwoerkom �rta: > > > >> --- Zoltan Boszormenyi <zb...@fr...> > wrote: > >> > >> > >> > >>> Hugo Vanwoerkom �rta: > >>> > >>> > >>>> */Zoltan Boszormenyi <zb...@fr...>/* > >>>> > >>>> > >>> wrote: > >>> > >>> > >>>> Hi, > >>>> > >>>> I just noticed that faketty isn't needed > with > >>>> > >>>> > >>> Xorg 7.x. > >>> > >>> > >>>> The following section works like a charm > for a > >>>> > >>>> > >>> keyboard, > >>> > >>> > >>>> nothing else is needed. > >>>> > >>>> Section "InputDevice" > >>>> Identifier "Keyboard0" > >>>> Driver "evdev" > >>>> Option "Device" "/dev/input/eventX" > >>>> Option "XkbLayout" "hu" > >>>> EndSection > >>>> > >>>> The proper eventX device is registered in > >>>> > >>>> > >>> /proc/bus/input/devices > >>> > >>> > >>>> and as with the kbd driver, multiple > sections > >>>> > >>>> > >>> can be listed > >>> > >>> > >>>> and assigned to the same server, e.g. the > PS/2 > >>>> > >>>> > >>> keyboard > >>> > >>> > >>>> and the BTTV remote is assigned to one X > >>>> > >>>> > >>> server, > >>> > >>> > >>>> the USB keyboard's two devices (normal > >>>> > >>>> > >>> keyboard and > >>> > >>> > >>>> the multimedia keys are separated) are > >>>> > >>>> > >>> assigned to the > >>> > >>> > >>>> other server. > >>>> > >>>> And what is the vt set at then in gdm.conf for > the > >>>> > >>>> > >>> other keyboards? > >>> > >>> > >>>> Hugo > >>>> > >>>> > >>> Nothing, but "-sharevts" is needed. Same for > faketty > >>> if I don't specify "vtX" on the parameter line > and > >>> use > >>> Option "Device" "/dev/fttyN" instead. > >>> > >>> But some bug may still exist in the X evdev > driver > >>> as hungarian layout doesn't work correctly. > >>> E.g. Option "XkbModel" "pc105" makes RightAlt > >>> behave as Enter and without it (e.g. working as > >>> pc104), > >>> my i-acute button doesn't work. > >>> > >>> So, XOrg is only starting to get there, I > switched > >>> back to faketty for now. > >>> > >>> > >>> > >>> > >> I just tried this with good success. But I only > have 2 > >> monitors/keybds/mice. > >> The keyboards are both IBM Model M's. Mine is now > 13 > >> years old and the other I bought for $57 new. > >> Also I only need dead keys for us-intl config. > >> > >> So Faketty is gone and xorg.conf relevant parts > >> becomes: > >> > >> ... > >> Section "InputDevice" > >> Identifier "Keyboard0" > >> Driver "evdev" > >> Option "Device" > >> "/dev/input/event0" > >> Option "XkbLayout" > "us_intl" > >> EndSection > >> ... > >> Section "InputDevice" > >> Identifier "Keyboard1" > >> Driver "evdev" > >> Option "Device" > >> "/dev/input/event1" > >> Option "XkbLayout" > "us_intl" > >> EndSection > >> ... > >> > >> > > > > I replaced the 'Option "Device" ... ' lines with > > 'Option "Phys" "..."', it gives the same effect > but > > with higher persistency. It turned out that > modprobe > > processes race with each other and bttv and USB > HID > > devices change their places (both /dev/fttyN and > > /dev/input/eventN) depending on the load order. > > > And for my non-working iacute button, I needed this: > https://launchpad.net/distros/ubuntu/+source/xkeyboard-config/+bug/42846 > > I had to put this only line in > /usr/share/X11/xkb/keycodes/evdev : > > <LSGT> = 94 > > And the only key that wasn't working before > now works with evdev. Bye-bye faketty. :-) > I have set 'Option "Phys" "..."'"as you indicated. Here's the weird one *without* Faketty: 1. I run fvwm window-manager. Start either FF or Seamonkey. Activate xcompmgr to start translucent windows with the Alt+F9 key combination. It executes /usr/local/bin/xcompmgr -c. 2. Switch to vt1 with Alt+F1 3. From vt1 switch back with Alt+F7 IF IN FF OR SEAMONKEY THE HELP SCREEN WILL BE SHOWN! Turn off translucent windows (kill the xcompmgr's pid) AND EVERYTHING IS NORMAL AGAIN! Got a clue on how to avoid that? I posted to mozilla.support.seamonkey on how to disable shortcuts but not too much luck. Why run with translucent windows? Who knows, I like it, it took me a year to get it finally working. Regards, Hugo __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
|
From: Zoltan B. <zb...@fr...> - 2006-07-08 16:05:56
|
Hugo Vanwoerkom =EDrta: > --- Zoltan Boszormenyi <zb...@fr...> wrote: > > =20 >> Zoltan Boszormenyi =EF=BF=BDrta: >> =20 >>> Hugo Vanwoerkom =EF=BF=BDrta: >>> =20 >>> =20 >>>> --- Zoltan Boszormenyi <zb...@fr...> >>>> =20 >> wrote: >> =20 >>>> =20 >>>> =20 >>>> =20 >>>>> Hugo Vanwoerkom =EF=BF=BDrta: >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> */Zoltan Boszormenyi <zb...@fr...>/* >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> wrote: >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> Hi, >>>>>> >>>>>> I just noticed that faketty isn't needed >>>>>> =20 >> with >> =20 >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> Xorg 7.x. >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> The following section works like a charm >>>>>> =20 >> for a >> =20 >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> keyboard, >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> nothing else is needed. >>>>>> >>>>>> Section "InputDevice" >>>>>> Identifier "Keyboard0" >>>>>> Driver "evdev" >>>>>> Option "Device" "/dev/input/eventX" >>>>>> Option "XkbLayout" "hu" >>>>>> EndSection >>>>>> >>>>>> The proper eventX device is registered in >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> /proc/bus/input/devices >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> and as with the kbd driver, multiple >>>>>> =20 >> sections >> =20 >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> can be listed >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> and assigned to the same server, e.g. the >>>>>> =20 >> PS/2 >> =20 >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> keyboard >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> and the BTTV remote is assigned to one X >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> server, >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> the USB keyboard's two devices (normal >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> keyboard and >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> the multimedia keys are separated) are >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> assigned to the >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> other server. >>>>>> >>>>>> And what is the vt set at then in gdm.conf for >>>>>> =20 >> the >> =20 >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> other keyboards? >>>>> =20 >>>>> =20 >>>>> =20 >>>>>> Hugo >>>>>> =20 >>>>>> =20 >>>>>> =20 >>>>> Nothing, but "-sharevts" is needed. Same for >>>>> =20 >> faketty >> =20 >>>>> if I don't specify "vtX" on the parameter line >>>>> =20 >> and >> =20 >>>>> use >>>>> Option "Device" "/dev/fttyN" instead. >>>>> >>>>> But some bug may still exist in the X evdev >>>>> =20 >> driver >> =20 >>>>> as hungarian layout doesn't work correctly. >>>>> E.g. Option "XkbModel" "pc105" makes RightAlt >>>>> behave as Enter and without it (e.g. working as >>>>> pc104), >>>>> my i-acute button doesn't work. >>>>> >>>>> So, XOrg is only starting to get there, I >>>>> =20 >> switched >> =20 >>>>> back to faketty for now. >>>>> >>>>> >>>>> =20 >>>>> =20 >>>>> =20 >>>> I just tried this with good success. But I only >>>> =20 >> have 2 >> =20 >>>> monitors/keybds/mice. >>>> The keyboards are both IBM Model M's. Mine is now >>>> =20 >> 13 >> =20 >>>> years old and the other I bought for $57 new. >>>> Also I only need dead keys for us-intl config. >>>> >>>> So Faketty is gone and xorg.conf relevant parts >>>> becomes: >>>> >>>> ... >>>> Section "InputDevice" >>>> Identifier "Keyboard0" >>>> Driver "evdev" >>>> Option "Device" =20 >>>> "/dev/input/event0" >>>> Option "XkbLayout" =20 >>>> =20 >> "us_intl" >> =20 >>>> EndSection >>>> ... >>>> Section "InputDevice" >>>> Identifier "Keyboard1" >>>> Driver "evdev" >>>> Option "Device" =20 >>>> "/dev/input/event1" >>>> Option "XkbLayout" =20 >>>> =20 >> "us_intl" >> =20 >>>> EndSection >>>> ... >>>> =20 >>>> =20 >>>> =20 >>> I replaced the 'Option "Device" ... ' lines with >>> 'Option "Phys" "..."', it gives the same effect >>> =20 >> but >> =20 >>> with higher persistency. It turned out that >>> =20 >> modprobe >> =20 >>> processes race with each other and bttv and USB >>> =20 >> HID >> =20 >>> devices change their places (both /dev/fttyN and >>> /dev/input/eventN) depending on the load order. >>> =20 >>> =20 >> And for my non-working iacute button, I needed this: >> >> =20 > https://launchpad.net/distros/ubuntu/+source/xkeyboard-config/+bug/4284= 6 > =20 >> I had to put this only line in >> /usr/share/X11/xkb/keycodes/evdev : >> >> <LSGT> =3D 94 >> >> And the only key that wasn't working before >> now works with evdev. Bye-bye faketty. :-) >> >> =20 > > I have set 'Option "Phys" "..."'"as you indicated. > > Here's the weird one *without* Faketty: > > 1. I run fvwm window-manager. Start either FF or > Seamonkey. Activate xcompmgr to start translucent > windows with the Alt+F9 key combination. It executes > /usr/local/bin/xcompmgr -c. > > 2. Switch to vt1 with Alt+F1 > > 3. From vt1 switch back with Alt+F7 > > IF IN FF OR SEAMONKEY THE HELP SCREEN WILL BE SHOWN! > > Turn off translucent windows (kill the xcompmgr's pid) > AND EVERYTHING IS NORMAL AGAIN! > > Got a clue on how to avoid that? I posted to > =20 Hm, don't switch to vt1 then? :-) I guess it's a "doctor it hurts - don't do it then" type of a problem. I think it's not too fortunate to mix /dev/tty* usage with direct keyboard access. /dev/tty* will multiplex all the keyboards, because it may steal input from other devices, too. BTW the latest RawHide 2.6.18-rc1 based kernels ruined NumLock handling again, my USB keyboard controls the PS/2 keyboard's NumLock when on the console and at least the LEDs don't work on the USB keyboard after X grabbed it. > mozilla.support.seamonkey on how to disable shortcuts > but not too much luck. > > Why run with translucent windows? Who knows, I like > it, it took me a year to get it finally working. > =20 What about compiz? It works pretty fast on my Radeon 9200SE. I will try it on the Radeon 7000, too. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X