Re: I'm half on my way...to get it going. (long)

[Peter S. <pet...@gm...>]

Svetoslav Slavtchev wrote:
>>It seems my 2nd keyboard is on vt18. vt17 is ...?
> 
> 
> IMO that's rather strange, the second keyboard(no matter PS2 or USB)
> should be bound to vt17 ( /proc/bus/console/01/keyboard ) if the first one
> is PS2, but if you can start X on vt18 and use the second keyboard ...?

found vt17 is assinged to the IR of my dvb card. (do I hae to care)

> 
> 
>>I've got a NVIDIA 5600xt. This card has two vga out, but only one
>>PCIbusID: PCI:2:0:0 (AGP).
> 
> 
> hm
> i really doubt it'll work with only one card in case it have only one BusID
> the only possibility would be to use framebufers + XFree driver "fbdev"
> what's confusing me is that you manage to start X on both heads
> (and got the standard XFree behaviour, only 1 Xserver can run at a time)

The nvidia driver seems to manage the two heads by the
ConnectedMonitor option CRT-0 and CRT-1.
(just my explanation of the behaviour)

...
> 
> 
> i'm not sure is related,but  i use/ would use
> -----------------
>           [server-Standard1]
>  name=Standard server 1
>  command=/usr/local/bin/X1  :1 -deferglyphs 16 -nolisten tcp -audit 0
> -layout sesam1 vt18
> -----------------
I checked the cmdline in /proc they look ok. sesam0 vt7 :0 and sesam1
vt18 :1

> 
> 
> 
> as you are using a single card with only one BusID does Options can not be
> used :(
> you should use "echo 1 >  /proc/bus/pci/hackvideo"
> and if it does work, you'll probably want to add it to your init scripts :-)

No. It doesn't work.

> long posting is not a prob :-)
> but some essential info is missing, what about posting
> dmesg, XFree logs , ....
>  the kernel from Andreas is based ? ruby ? bruby?  which version ?
kernel is 2.6.0-ruby.
sorry: see attached logs
> 
> PS.
> please take a lbref look at my howto
> http://tldp.org/HOWTO/XFree-Local-multi-user-HOWTO/index.html
> at least the following section i think could answer some of your questions
> 2.1. Known Limitations
> 4.1. Do I need a modified X server?
2.1 : the heads have to be explicitly addressable
They are CRT-0,CRT-1 (I know that's not the right way but Nvidia uses it)
4.1 : I can start both servers and they don't complain about locked 
cards or something. hmm...

It seems the X server still thinks that it has to disable the console on 
a console switch. strange...

I think I should have a look at the preferedbusid patch. Perhaps i can 
use that to solve my problem. One should ba able to tell X witch virtual 
consoles are on witch real consoles. Right?
Any hints?

Peter

PS: Why was PreferBusId introduced? Wasn't BusId enough?