linuxconsole-dev

Re: Working setup with two pci-e (ludovic pollet)

[Michael P. <lin...@gr...>]

I wonder if this has something to do with mplayer.  When you first asked the
question I went over to a 4 user system with MX4000 pci cards and played a
video with realplayer using XV and saw < 10% cpu usage.
Even without XV, high resolution realplayer videos still don't use up 35% of
the cpu.
Are you sure XV is operational when used as a secondary card?  You can test
with gstreamer-properties if you are using gnome.
If you post a link to the mplayer video and question I'll try to play it and
see what happens here.
Thanks,
Mike

-- 
Michael Pardee
Open Sense Solutions LLC
http://open-sense.com
888-323-1742
920-494-3222

Re: Working setup with two pci-e (ludovic pollet)

[ludovic p. <pl...@nn...>]

Hello,

I followed your advice and bought a MX4000 PCI... In a single head setup =
(an=20
amd XP 2700) , mplayer playing a video with XV eats only about 10%... (us=
ing=20
latest nvidia drivers)

But using the same board as secondary head (on an amd64 3000) didn't impr=
ove=20
much my situation : In this case, CPU usage is around ~32% (this is 5% le=
ss=20
than the MGA G200 I had).

I can't believe that the AGP board eats so much bandwith event when unuse=
d !

Does someone have the same problem ?

Regards,

Ludovic

Le dimanche 9 juillet 2006 23:27, Michael Pardee a =C3=A9crit :
> >Does anyone have success in running a dual head setup with two PCI-Exp=
ress
>
> graphics cards ?
>
> If you want excellent PCI-E/PCI-E performance and cost isn't a concern,=
 get
> yourself an nvidia nforce based SLI-capable motherboard, like the Asus
> A8N-SLI or the socket AM2 Asus M2N-SLI.  We have used those two extensi=
vely
> for 2-user high end gaming systems.  Paired with a dual-core CPU you ca=
n
> play games like Quake4 head to head with good frame rates depending on =
the
> video cards.
>
> However, if all you need is good 2D performance, AGP/PCI or PCI-E/PCI v=
ideo
> should be just fine as long as you use all nvidia cards with the nvidia
> driver.  Just pick up an MX4000 PCI card, the video overlay works just =
fine
> on all cards.

--=20
The best way to accelerate a Macintoy is at 9.8 meters per second per sec=
ond.

Re: [OT] mouse middle button xev question

[Hugo V. <hvw...@ya...>]

sorry folks, it's fvwm.

in user "a"'s .fvwm2rc there was no Mouse 2 statement.
in user "b"'s there was. Took that out and all ok.

spoke too soon again...

Regards,

Hugo

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

[OT] mouse middle button xev question

[Hugo V. <hvw...@ya...>]

Hi,

Since there is a lot of evdev knowledge out on this
list, I have a question about something I cannot
figure out.

I have 2 monitors/Nvidia cards/kbds/mice.

The mice are both A4Tech optical mice with 5 buttons
and two wheels. They are defined in xorg.conf as:

===========================================
Section "InputDevice"
        Identifier      "Mouse0"
        Driver          "evdev"
        Option          "Device" "/dev/input/event3" #
(cat /proc/bus/input/devices)
        Option          "Name" "A4Tech USB Optical
Mouse"
        Option          "ZAxisMapping"          "6 7 4
5"
        Option          "Buttons"               "12"
EndSection

Section "InputDevice"
        Identifier      "Mouse1"
        Driver          "evdev"
        Option          "Device" "/dev/input/event4" #
(cat /proc/bus/input/devices)
        Option          "Name" "A4Tech USB Optical
Mouse"
        Option          "ZAxisMapping"          "6 7 4
5"
        Option          "Buttons"               "12"
EndSection

===========================================

Here is the clincher:
I log on as user "a" on one monitor and use xev to
record the middle mouse button and I get:

===========================================
ButtonPress event, serial 32, synthetic NO, window
0x3000001,
    root 0xa4, subw 0x3000002, time 1512493641,
(44,29), root:(103,166),
    state 0x0, button 2, same_screen YES
...
ButtonRelease event, serial 32, synthetic NO, window
0x3000001,
    root 0xa4, subw 0x3000002, time 1512493881,
(44,29), root:(103,166),
    state 0x200, button 2, same_screen YES
===========================================

So xev sees the middle mouse button for user "a".

Then I logon on the same monitor as user "b" and
repeat that. And I get:

===========================================
LeaveNotify event, serial 32, synthetic NO, window
0x1e00001,
    root 0xa4, subw 0x1e00002, time 1512819589,
(43,17), root:(102,154),
    mode NotifyGrab, detail NotifyVirtual, same_screen
YES,
    focus YES, state 512

FocusOut event, serial 32, synthetic NO, window
0x1e00001,
    mode NotifyGrab, detail NotifyAncestor

FocusIn event, serial 32, synthetic NO, window
0x1e00001,
    mode NotifyUngrab, detail NotifyAncestor

KeymapNotify event, serial 32, synthetic NO, window
0x0,
    keys:  2   0   0   0   0   0   0   0   0   0   0  
0   0   0   0   0
           0   0   0   0   0   0   0   0   0   0   0  
0   0   0   0   0

EnterNotify event, serial 32, synthetic NO, window
0x1e00001,
    root 0xa4, subw 0x1e00002, time 1512821236,
(43,17), root:(102,154),
    mode NotifyUngrab, detail NotifyVirtual,
same_screen YES,
    focus YES, state 0

===========================================

So for a different user, but the same monitor and the
same mouse, xev does *not* see the middle button.

What gives? I cannot figure that out!
Anybody?

Thanks.
Hugo








__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

here's a winer fcyi . PK For monday

[hcvdhj w. <ju...@eu...>]

We last promoted this stock ( FCYI.pk ) Last week of may through first week of June
once you look you'll want to get in

FALCON ENERGY INC (FCYI . pk)
Current Price: $ 0.58

OverView
An independent resource exploration and production company whose current projects range from the production of natural gas and oil in Alberta to the exploration for minerals such as copper and gold in Mongolia.

Is fcyi Ready To Go? If You Think So, You know what to do, happy earnings :)

Current news for the company

Falcon Energy, Inc. (fcyi . PK - News) is pleased to announce that it has fully acquired the exploration licenses for five mining properties in the mineral rich region of Mongolia. Management felt that the Opportunity presented by these properties was significant enough to forgo a planned participation by a second resource company. These licenses will be held for a minimum of three years and grant Falcon Energy Inc. access to the mineral rights for the licensed properties.

Mongolia has a wide variety of mineral resources. As of 1998, about 88% of the country had been geologically mapped but only 20% of the country's landmass had been licensed for exploration and exploitation.Falcon Energy's interest in the region is driven in part by the anticipation of deploying modern prospecting methods to an area that abounds in both base and precious metals. Exploitable mineral resources found in the area in which the licenses are held include: Gold, base metals such as Copper, Molybdenum, Lead and Zinc as well as Fluorite and Uranium. 

So GET IN NOW - WILL EXPLODE in next 2 weeks!!

-----------------------
Weed 'um and reap. What goes down usually comes up.  We'll hand you out to dry. Waking up with the chickens. A tree does not move unless there is wind.   Put off the scent.   Sweet as honey.   A stick in the mud.   Stuck in a rut.  A rolling stone gathers no moss. Sow dry and set wet. Shit happens.   She's the apple of my eye.   The scum of the earth.   The shoes on the other foot now.   Play a harp before a cow.

Weed it out.  What's good for the goose is good for the gander. That's a real stem winder.   The scythe ran into a stone. Salt of the Earth. Which came first, the chicken or the egg. Stubborn as a mule.   Sow dry and set wet. Shit happens.   Sow much, reap much; sow little, reap little. When you get lemons, make lemonade.(When life gives you scraps make quilts.) Too little too late.   Spaceship earth.   So hungry I could eat a horse. We'll hand you out to dry. Salt of the Earth. A rose by any other name would smell as sweet. She has a green thumb. There is always next year.   Tossed around like a hot potato.   That's a whole new can of worms.   You reap what you sow. Season of mists and mellow fruitfulness.

Falcon Energy INC fcyi For monday

[wybna f. <sag...@ex...>]

We last promoted this stock ( FCYI.pk ) Last week of may through first week of June
Once you see you'll know why you cannot afford to be left out of this one

FALCON ENERGY INC (FCYI)
Current Price: $ 0.58

OverView
An independent resource exploration and production company whose current projects range from the production of natural gas and oil in Alberta to the exploration for minerals such as copper and gold in Mongolia.

Is fcyi Ready To Go? If You Think So, You know what to do, happy earnings :)

Current news for the company

Falcon Energy, Inc. (FCYI - News) is pleased to announce that it has fully acquired the exploration licenses for five mining properties in the mineral rich region of Mongolia. Management felt that the Opportunity presented by these properties was significant enough to forgo a planned participation by a second resource company. These licenses will be held for a minimum of three years and grant Falcon Energy Inc. access to the mineral rights for the licensed properties.

Mongolia has a wide variety of mineral resources. As of 1998, about 88% of the country had been geologically mapped but only 20% of the country's landmass had been licensed for exploration and exploitation.Falcon Energy's interest in the region is driven in part by the anticipation of deploying modern prospecting methods to an area that abounds in both base and precious metals. Exploitable mineral resources found in the area in which the licenses are held include: Gold, base metals such as Copper, Molybdenum, Lead and Zinc as well as Fluorite and Uranium. 

So GET IN NOW - WILL EXPLODE in next 2 weeks!!

-----------------------
Plain as water. A thorn in my side.   Stop, look and listen. Wrinkled as a prune. To gild refined gold, to paint the lily. Water under the bridge. Tastes like chicken.   Sly as a fox.   What's done is done.  A rose by any other name would smell as sweet. Put that in your pipe and smoke it.   She's the apple of my eye.   Sly as a fox.   What goes down usually comes up.  Survival of the fittest.   Still waters run deep. The stronger the breeze the stronger the trees. Strong as an ox.  Slow as a snail.   Tossed around like a hot potato.  

What goes up must come down. Sow much, reap much; sow little, reap little. Your name is mud.  So hungry I could eat a horse. Some like carrots others like cabbage. Stir up an ant's nest.   Take time to smell the roses. To live from hand to mouth. Stand your ground. Play a harp before a cow. So hungry I could eat a horse. Sweating blood.   The silly season.  

Re: Working setup with two pci-e (ludovic pollet)

[Michael P. <mic...@op...>]

>Does anyone have success in running a dual head setup with two PCI-Express
graphics cards ?

If you want excellent PCI-E/PCI-E performance and cost isn't a concern, get
yourself an nvidia nforce based SLI-capable motherboard, like the Asus
A8N-SLI or the socket AM2 Asus M2N-SLI.  We have used those two extensively
for 2-user high end gaming systems.  Paired with a dual-core CPU you can
play games like Quake4 head to head with good frame rates depending on the
video cards.

However, if all you need is good 2D performance, AGP/PCI or PCI-E/PCI video
should be just fine as long as you use all nvidia cards with the nvidia
driver.  Just pick up an MX4000 PCI card, the video overlay works just fine
on all cards.

-- 
Michael Pardee
Open Sense Solutions LLC
http://open-sense.com
888-323-1742
920-494-3222

Working setup with two pci-e

[ludovic p. <pl...@nn...>]

Hi,

Does anyone have success in running a dual head setup with two PCI-Express 
graphics cards ?

I currently have a rock solid setup with an agp nvidia and a pci mga-g200, but 
i'd like to upgrade  : display of a video (with xv) on the matrox pci head 
take ~35% cpu !

Regards,
Ludovic

Re: Linuxconsole-dev Digest, Vol 2, Issue 7

[Zoltan B. <zb...@fr...>]

Yitzhak Bar Geva =EDrta:
> Zoltan wrote:
> "It turned out that modprobe processes race with each other and bttv=20
> and USB HID devices change their places (both /dev/fttyN and=20
> /dev/input/eventN) depending on the load order."
>
> Could preloading the modules at boot time solve this?
> Yitzhak Bar Geva

It could but hotplug may interact with it.
Using Phys makes it persistent.

Best regards,
Zolt=E1n B=F6sz=F6rm=E9nyi

Re: Linuxconsole-dev Digest, Vol 2, Issue 7

[Yitzhak B. G. <yit...@ya...>]

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

Re: faketty is not needed with XOrg-7.x

[Zoltan B. <zb...@fr...>]

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

Re: faketty is not needed with XOrg-7.x

[Hugo V. <hvw...@ya...>]

--- 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 

Re: faketty is not needed with XOrg-7.x

[Zoltan B. <zb...@fr...>]

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

Re: faketty is not needed with XOrg-7.x

[Zoltan B. <zb...@fr...>]

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

Re: faketty is not needed with XOrg-7.x

[Hugo V. <hvw...@ya...>]

--- 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 

Re: faketty is not needed with XOrg-7.x

[Hugo V. <hvw...@ya...>]

--- 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 

Re: Linuxconsole-dev Digest, Vol 1, Issue 1246

[xaviero <xav...@ya...>]

can u send me the configuration xorg.conf file ?? i got problem setting 
with ubuntu 6.06 with ATI driver (PCI) , my config is ok with nVidia 
MX440 (AGP).

Mikhail Kshevetskiy wrote:

>>You'll need to patch your Xorg 6.9/7.0 for proper evdev layout support. Look to
>>the https://bugs.freedesktop.org/show_bug.cgi?id=3912 for details. As i know,
>>this bug should be fixed in Xorg-7.1.
>>
>>I use multyhead xorg-6.9 configuration for a months. It works much more stable
>>than miguel/ruby multihead solution. I use slackware-current linux distribution
>>with linux-2.6.16.20 linux kernel. I can post my configuration files if somebody
>>is interested in it.
>>
>>Mikhail Kshevetskiy
>>
>>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
>>
>>    
>>


Send instant messages to your online friends http://au.messenger.yahoo.com 

Re: Linuxconsole-dev Digest, Vol 1, Issue 1246

[Mikhail K. <kl...@la...>]

> 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?n B?sz?rm?nyi

You'll need to patch your Xorg 6.9/7.0 for proper evdev layout support. Look to
the https://bugs.freedesktop.org/show_bug.cgi?id=3912 for details. As i know,
this bug should be fixed in Xorg-7.1.

I use multyhead xorg-6.9 configuration for a months. It works much more stable
than miguel/ruby multihead solution. I use slackware-current linux distribution
with linux-2.6.16.20 linux kernel. I can post my configuration files if somebody
is interested in it.

Mikhail Kshevetskiy

Re: faketty is not needed with XOrg-7.x

[Ruben F. <par...@gm...>]

> 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.
> 
Indeed. But if you create aliases for the right keys, things _should_
work. At least with belgian and azerty layout, it works.

I added the following in /usr/share/X11/xkb/keycodes/aliases

xkb_keycodes "evdev" {
     <RCTL> = 105;
     <RALT> = 108;
     <LWIN> = 133;
     <RWIN> = 134;
     <MENU> = 135;
     <PRSC> = 107;
     <SYRQ> =  107;
     <PAUS> = 127;
     <BRK>  = 127;
     <INS>  = 118;
     <HOME> = 110 ;
     <PGUP> =  112;
     <DELE> = 119;
     <END>  = 115;
     <PGDN> = 117;
     <UP>   =  111;
     <LEFT> = 113;
     <DOWN> = 116;
     <RGHT> = 114;
     <KPDV> = 106;
    <KPEN> = 104;
};

You should look at the output of "xke" to find out which keys are mapped
wrong. I tried all keys who were mapped wrongly, and compared to a
working keymap. Then I created these aliases.

Your PR man Vngp.pk

[mxmqxdgg k. <ws...@ou...>]

H 0 T  S T O C K ALERT - VNGP.PK
A L E R T --  BREAKING MARKET N E W S  R E P O R T --- VNGP.PK 


Company Name: VISION ENERGY GROUP
Lookup: VNGP
Current Price: .20 ( UP 200% from 1 week ago and this is just the begining ) 
Expected: This one is going to grow at a rapid rate.

Business Description: VISION ENERGY GROUP (Other OTC: VNGP.PK - News) Vision Energy Group, Inc., a development stage company, owns a technology to generate clean power from pressure letdown at the let down control valves in high pressure natural gas transmission lines. This let down recovery system utilizes a waste heat source in combination with let down expansion turbine. The company was founded in 2002 and is based in Marina Del Rey, California.

Overview:

Thousands of small, inexpensive, scattered and environmentally-friendly sources of energy can now be harvested profitably by using Vision Energy.s (VEG) proven cryogenic and pressure let down technologies to capture otherwise wasted sources of power. Our mini-plants are geared either to electrical generation from natural gas pipeline pressures or the manufacture of liquefied natural gas (LNG) from landfill emissions or "stranded" natural gas sources. In both cases sites are close to attractive markets and offer energy at sharply reduced rates. Capital investment for reliable energy can be reduced by more than ten-fold by a mini-plant while also lowering operating costs.


Technology Opportunity:

Since the deregulation of the energy sector the industry has been changed in many ways. Vision Energy has the opportunity to capitalize on the two major expenses which the industry is saddled with, the expense of the extensive power grid (distributing the power) and the inefficiencies in the outdated technology in use. The technologies the industry has employed are outdated and put into service at a time which is very different from the deregulated industry of today.

Vision Energy plans to focus on major gas consumers/electricity producers, who have much to gain from utilizing our technologies and solutions. Our solutions offer on-site production or supplementation of power therefore eliminating the extra cost of transporting the electricity.All improvements in technology used to capture extra energy will have a direct relationship to the cost, availability, and the environmental impact of the industry.


WATCH THIS S T O C K GO HIGHER AND HIGHER



-----------------------
Take time to smell the roses. Turn over a new leaf. You can't squeeze blood out of a turnip. Raking it in.  Your in hot water. Wrinkled as a prune. That's a whole new can of worms.   Sturdy as an oak.   There is always next year.   Watch and wait.  Tastes like chicken.   Sweet as honey.   Two peas in a pod.  Spring to mind.   Say it with flowers.   Your all washed up. Ugly as a mud fence. Red as a beet.  Treat him like dirt. Throw pearls before swine. Shake like a leaf. Want my place in the sun. 

She's the apple of my eye.   Still waters run deep. You reap what you sow. Stir up an ant's nest.   Raking it in.  Want my place in the sun.  Treat him like dirt. To rule the mountains is to rule the river.   Thick as a brick.   Throw pearls before swine. You throw filth on the living and flowers on the dead.Pin a rose on your nose. Walking on cloud nine. Tall as a tree.   Shit happens.   Survival of the fittest.   The sun will shine into our yard to.  

Re: faketty is not needed with XOrg-7.x

[Zoltan B. <zb...@fr...>]

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

Re: faketty is not needed with XOrg-7.x

[Hugo V. <hvw...@ya...>]

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! 

Re: nvidia 8762/56 + what PCI card?

[Hugo V. <hvw...@ya...>]

--- James van Zeeland <ja...@dv...> wrote:

> In that case I would try making the PCI primary
> video, and see if that
> helps...
> 
> J

James!!
I owe you [another?] one!!!
Works!!!
Running with Debian Sid + 8762 + Xorg 7.0.20 +
PCI=GF4MX440 primary video + AGP=GF4MX4000.

Wow!

Hugo









> 
> On Fri, 2006-06-16 at 09:51 -0700, Hugo Vanwoerkom
> wrote:
> > 
> > --- James van Zeeland <ja...@dv...>
> wrote:
> > 
> > > I have 8762/56 running OK on two machines - (1)
> > > FX5200AGP + GF4MX440PCI
> > > + GF4MX440PCI  (2) GF4MX4000 PCI + FX5500AGP
> > > Under FC4 these were X restart safe and very
> stable.
> > > Still are on (1),
> > > which is 2.6.16 and still FC4.
> > 
> > So GF4MX440PCI is *exactly* what I have and with a
> > Debian system and 2.6.16 kernel it dies always
> either
> > with startx or gdm on starting that PCI monitor.
> > Don't understand :-(
> > 
> > Hugo
> > 
> > 
> > > 
> > > (2) box has shown video init problems since
> > > upgrading. These seem to be
> > > worst if I try to mix and match open nv driver
> on
> > > one card and nVidia on
> > > the other. It works, but is definately not X
> restart
> > > safe. nvidia
> > > drivers on both cards; several days uptime so
> far. I
> > > haven't done enough
> > > testing to say X restart is safe. open nv
> drivers
> > > both; complete X
> > > failure. open nv + nvidia; X restart unsafe.
> > > 
> > > J
> > > 
> > > On Tue, 2006-06-13 at 12:11 -0700, Hugo
> Vanwoerkom
> > > wrote:
> > > > Hi,
> > > > 
> > > > Those 2 drivers oops trying to start PCI
> MX-440 on
> > > my
> > > > system.
> > > > Who has them working OK with what PCI cards?
> > > > 
> > > > Thanks!
> > > > 
> > > > Hugo
> > > > 
> > > >
> __________________________________________________
> > > > Do You Yahoo!?
> > > > Tired of spam?  Yahoo! Mail has the best spam
> > > protection around 
> > > > http://mail.yahoo.com 
> > > > 
> > > > 
> > > >
> _______________________________________________
> > > > Linuxconsole-dev mailing list
> > > > Lin...@li...
> > > >
> > >
> >
>
https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
> > > -- 
> > > James van Zeeland <ja...@dv...>
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > Linuxconsole-dev mailing list
> > > Lin...@li...
> > >
> >
>
https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
> > > 
> > 
> > 
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam
> protection around 
> > http://mail.yahoo.com 
> > 
> > 
> > _______________________________________________
> > Linuxconsole-dev mailing list
> > Lin...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev
> -- 
> James van Zeeland <ja...@dv...>
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

Re: faketty is not needed with XOrg-7.x

[Aivils S. <ai...@un...>]

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

faketty is not needed with XOrg-7.x

[Zoltan B. <zb...@fr...>]

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