From: Yitzhak B. G. <yit...@ya...> - 2006-07-09 00:37:04
|
Zoltan wrote: "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." Could preloading the modules at boot time solve this? Yitzhak Bar Geva lin...@li... wrote: Send Linuxconsole-dev mailing list submissions to lin...@li... To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev or, via email, send a message with subject or body 'help' to lin...@li... You can reach the person managing the list at lin...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Linuxconsole-dev digest..." Today's Topics: 1. Re: faketty is not needed with XOrg-7.x (Zoltan Boszormenyi) 2. Re: faketty is not needed with XOrg-7.x (Hugo Vanwoerkom) 3. Re: faketty is not needed with XOrg-7.x (Zoltan Boszormenyi) From: Zoltan Boszormenyi <zb...@fr...> CC: lin...@li... To: Hugo Vanwoerkom <hvw...@ya...> Date: Sat, 08 Jul 2006 07:24:19 +0200 Subject: Re: faketty is not needed with XOrg-7.x Zoltan Boszormenyi �rta: > Hugo Vanwoerkom �rta: > >> --- Zoltan Boszormenyi wrote: >> >> >> >>> Hugo Vanwoerkom �rta: >>> >>> >>>> */Zoltan Boszormenyi /* >>>> >>>> >>> 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 : = 94 And the only key that wasn't working before now works with evdev. Bye-bye faketty. :-) Best regards, Zolt�n B�sz�rm�nyi From: Hugo Vanwoerkom <hvw...@ya...> CC: lin...@li... To: Zoltan Boszormenyi <zb...@fr...> Date: Sat, 8 Jul 2006 07:19:04 -0700 (PDT) Subject: Re: faketty is not needed with XOrg-7.x --- Zoltan Boszormenyi wrote: > Zoltan Boszormenyi �rta: > > Hugo Vanwoerkom �rta: > > > >> --- Zoltan Boszormenyi > wrote: > >> > >> > >> > >>> Hugo Vanwoerkom �rta: > >>> > >>> > >>>> */Zoltan Boszormenyi /* > >>>> > >>>> > >>> 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 : > > = 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 Boszormenyi <zb...@fr...> CC: lin...@li... To: Hugo Vanwoerkom <hvw...@ya...> Date: Sat, 08 Jul 2006 18:05:45 +0200 Subject: Re: faketty is not needed with XOrg-7.x Hugo Vanwoerkom �rta: > --- Zoltan Boszormenyi wrote: > > >> Zoltan Boszormenyi �rta: >> >>> Hugo Vanwoerkom �rta: >>> >>> >>>> --- Zoltan Boszormenyi >>>> >> wrote: >> >>>> >>>> >>>> >>>>> Hugo Vanwoerkom �rta: >>>>> >>>>> >>>>> >>>>>> */Zoltan Boszormenyi /* >>>>>> >>>>>> >>>>>> >>>>> 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 : >> >> = 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 > 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. > What about compiz? It works pretty fast on my Radeon 9200SE. I will try it on the Radeon 7000, too. Best regards, Zolt�n B�sz�rm�nyi Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Linuxconsole-dev mailing list Lin...@li... https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev |