linuxconsole-dev

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

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

Hi,
first: Thanks for your work to get this killer feature running.

I'm trying to get the local-multiconsole up but am still running into
problems:

I installed the debian kernel-sources from schuldei. Build them
installed them, everything's fine:
cat /proc/bus/console/*/*
isa0060/serio0/input0

usb-0000:00:02.2-1.4/input0

It seems my 2nd keyboard is on vt18. vt17 is ...?

I've got a NVIDIA 5600xt. This card has two vga out, but only one
PCIbusID: PCI:2:0:0 (AGP).

My XF86Config looks like this:

...
Section "Device"
     #DFP (converter)
     Identifier  "nvidia0"
     VendorName  "nvidia"
     BoardName   "asus"
     Driver "nvidia"
     Option "NvAGP" "3"
     Option "NoLogo" "true"
     Option "ConnectedMonitor" "CRT-0"
     Screen 0
EndSection


Section "Device"
     #CRT
     Identifier  "nvidia1"
     VendorName  "nvidia"
     BoardName   "asus"
     Driver "nvidia"
     Option "NvAGP" "3"
     Option "NoLogo" "true"
     Option "ConnectedMonitor" "CRT-1"
     Screen 0
EndSection
...
Section "ServerLayout"
     Identifier "sesam0"
     Screen "sesam0"
#    Screen 1 "sesam1" rightof "sesam0" <--this works if enabled!


     InputDevice "logitech0"
     InputDevice "keyboard0"
#    Option "SingleCard" "true"  ???meaning
#    Option "PrefBusID" "PCI:2:0:0" ???meaning
EndSection


Section "ServerLayout"
     Identifier "sesam1"
     Screen "sesam1"
     InputDevice "logitech1"
     InputDevice "keyboard1"
#    Option "SingleCard" "true"
#    Option "PrefBusID" "PCI:2:0:0"
EndSection

I downloaded the deb packges for X from schuldei (compiling X is a
horror), did two links X0 and X1 to XFree86. Modified my gdm.conf:

0=Standard0 -layout sesam0 vt7
1=Standard1 -layout sesam1 vt18

[server-Standard0]
name=Standard server0
command=/usr/local/bin/X0  -deferglyphs 16 -nolisten tcp -audit 0
flexible=true

          [server-Standard1]
name=Standard server 1
command=/usr/local/bin/X1  -deferglyphs 16 -nolisten tcp -audit 0
flexible=true

BUT!!! If I start gdm following happens:
sesam0 on CRT-0 gets started (got picture every thing's fine)
but if sesam1 is started the first console goes into sleepmode and the
second console is fired up (on wich everything's fine). So I can't work
on both console at the same time :-(((.
I got exactly the same behavior on an unpatched kernel (though I could
switch between vt7 and vt8 and switched from one console to the other).

What did I do wrong?
What do the X options PrefBusID, SingleCard exactly mean?
Could this be a flaw in the Nvidia drivers? Though it works if used with 
  two screens and "LeftOf".

BTW: I'm not useing framebuffer, just VGA.

Took me 4 days to get this far...don't tell me it's not working :-)
Thanks for help, and sorry for the long posting.

Peter

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

[Svetoslav S. <sv...@gm...>]

Hi :-)
> Hi,
> first: Thanks for your work to get this killer feature running.
> 
> I'm trying to get the local-multiconsole up but am still running into
> problems:
> 
> I installed the debian kernel-sources from schuldei. Build them
> installed them, everything's fine:
> cat /proc/bus/console/*/*
> isa0060/serio0/input0
> 
> usb-0000:00:02.2-1.4/input0
> 
> 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 ...?

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

> My XF86Config looks like this:
> 
> ...
> Section "Device"
>      #DFP (converter)
>      Identifier  "nvidia0"
>      VendorName  "nvidia"
>      BoardName   "asus"
>      Driver "nvidia"
>      Option "NvAGP" "3"
>      Option "NoLogo" "true"
>      Option "ConnectedMonitor" "CRT-0"
>      Screen 0
> EndSection
> 
> 
> Section "Device"
>      #CRT
>      Identifier  "nvidia1"
>      VendorName  "nvidia"
>      BoardName   "asus"
>      Driver "nvidia"
>      Option "NvAGP" "3"
>      Option "NoLogo" "true"
>      Option "ConnectedMonitor" "CRT-1"
>      Screen 0
> EndSection
> ...
> Section "ServerLayout"
>      Identifier "sesam0"
>      Screen "sesam0"
> #    Screen 1 "sesam1" rightof "sesam0" <--this works if enabled!
> 
> 
>      InputDevice "logitech0"
>      InputDevice "keyboard0"
> #    Option "SingleCard" "true"  ???meaning
> #    Option "PrefBusID" "PCI:2:0:0" ???meaning
> EndSection
> 
> 
> Section "ServerLayout"
>      Identifier "sesam1"
>      Screen "sesam1"
>      InputDevice "logitech1"
>      InputDevice "keyboard1"
> #    Option "SingleCard" "true"
> #    Option "PrefBusID" "PCI:2:0:0"
> EndSection
> 
> I downloaded the deb packges for X from schuldei (compiling X is a
> horror), did two links X0 and X1 to XFree86. Modified my gdm.conf:
> 
> 0=Standard0 -layout sesam0 vt7
> 1=Standard1 -layout sesam1 vt18
> 
> [server-Standard0]
> name=Standard server0
> command=/usr/local/bin/X0  -deferglyphs 16 -nolisten tcp -audit 0
> flexible=true
> 
>           [server-Standard1]
> name=Standard server 1
> command=/usr/local/bin/X1  -deferglyphs 16 -nolisten tcp -audit 0
> flexible=true

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

> BUT!!! If I start gdm following happens:
> sesam0 on CRT-0 gets started (got picture every thing's fine)
> but if sesam1 is started the first console goes into sleepmode and the
> second console is fired up (on wich everything's fine). So I can't work
> on both console at the same time :-(((.
> I got exactly the same behavior on an unpatched kernel (though I could
> switch between vt7 and vt8 and switched from one console to the other).

that's the standard Xfree behaviour, only one X server can run at a time
 you should use
> What did I do wrong?
> What do the X options PrefBusID, SingleCard exactly mean?

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


> Could this be a flaw in the Nvidia drivers? Though it works if used with 
>   two screens and "LeftOf".
> 
> BTW: I'm not useing framebuffer, just VGA.
> 
> Took me 4 days to get this far...don't tell me it's not working :-)
hm don't know what to say :-( 
it'll will work with two cards, but with one ?

> Thanks for help, and sorry for the long posting.

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 ?

best,

svetljo

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?

-- 
+++ Mailpower für Multimedia-Begeisterte: http://www.gmx.net/topmail +++
250 MB Mailbox, 1 GB Online-Festplatte, 100 FreeSMS. Jetzt kostenlos testen!

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?

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

[Svetoslav S. <sv...@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)

:-)
probably not unless you want also to use  multiple framebuffer
consoles( in case your card is supported by rivafb driver )
but i think this won't be possible with this card without adding additional
one

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

right, it looks so,
but i'm tottaly puzled why it doesn't lock up completely
to the kernel/ Xfree it's a single card
both XFree instancies are talcking to the same memmory,
to the same device check your XFree logs, it's a single device, with single
bus id,
with the same memmory size /* your card doesn't have 256Mb memory, does it
*/
( i assume also same registers and memmory addresses)

i really doubt it will work with only one card of this type,
and i totally don't understand why it doesn't freeze  
> ...
> > 
> > 
> > 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

OK

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

it must work or freeze 
/* that's the problem with this aproach, on some combinations
 * it works, on others it does hang the system, where as using
 * prefbusid fixes most of the problematic combinations of graphic cards
 */

it must be that the nvidia driver is doing some  deep dark magic.
the only one that can give some info on the problem is Nvidia support team,
(and i'm not sure they'll be willing to :( )

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

not sure about that :(

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

it's probably not X but the nvidia driver itself, and i really doubt 
someone ( except Nvidia )  can hack it

sorry, but i really think you'll need an aditional card :(

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

the prefbusid needs a diffenerent BusID, in your case with a single BusID
it can not accompilsh anything

> Peter
> 
> PS: Why was PreferBusId introduced? Wasn't BusId enough?
> 
BusID is an standard XFree Option to be used with Xinerama

PrefBusID is a hack, which tells XFree to use the card with specified
BusID, and to ignore (not to disable) other present graphic cards

best,

svetljo

-- 
+++ Mailpower für Multimedia-Begeisterte: http://www.gmx.net/topmail +++
250 MB Mailbox, 1 GB Online-Festplatte, 100 FreeSMS. Jetzt kostenlos testen!

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

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

I'm on my way again....

I bought a NVIDIA RIVA TNT2 Model 64 PCI Card
and set up my XF86Config-4 (see attachment).
My first card is still a 5600XT.

I tried with and without echo "1" > ...hackvideo
I'm running the 2.6.0-ruby debian source package, with the debian 4.3 
XServer. Nvidia driver 5336.

# cat /proc/bus/console/*/*
isa0060/serio0/input0
usb-0000:00:02.2-1.4/input0

I created links X0 and X1 to /usr/X11R6/bin/XFree86
My startup commands are:
X1 :1 -layout sesam1 vt17
X0 :0 -layout sesam0 vt7

If I'm starting X1  I got something like a freeze: on the console I get 
the ouput of the start then the console freezes (but I can reeboot). 
remote admin is working,too.

The log of a test with X1 :0 -layout sesam1 vt17 is attached.
My configuration works with Xinerama flawlessly.

Thanks for your help

Peter

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

[James S. <jsi...@in...>]

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

Gerg Knorr just updated the IRC kernel drivers to the input api. So 
remotes now use the input api. We need to write a stronger keyboard 
detecting alogrithm.

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

[Svetoslav S. <sv...@gm...>]

> 
> > > 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)
> 
> Gerg Knorr just updated the IRC kernel drivers to the input api. So 
> remotes now use the input api. We need to write a stronger keyboard 
> detecting alogrithm.

meening ?

it's nice in the current configuration that using hotplug
you can assign the ir-keyboard to a dumb console
and start X with e.g. MythTV  and use the remote
with it, without  the remote interacting with the other displays

best,

svetljo

-- 
GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++

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

[James S. <jsi...@in...>]

> > Gerg Knorr just updated the IRC kernel drivers to the input api. So 
> > remotes now use the input api. We need to write a stronger keyboard 
> > detecting alogrithm.
> 
> meening ?
> 
> it's nice in the current configuration that using hotplug
> you can assign the ir-keyboard to a dumb console
> and start X with e.g. MythTV  and use the remote
> with it, without  the remote interacting with the other displays

Meaning we don't end up with joysticks acting a keyboards for the console. 
I think we need a certain set of keys present to consider it a "keyboard".
What do you think?

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

[Svetoslav S. <sv...@gm...>]

> 
> > > Gerg Knorr just updated the IRC kernel drivers to the input api. So 
> > > remotes now use the input api. We need to write a stronger keyboard 
> > > detecting alogrithm.
> > 
> > meening ?
> > 
> > it's nice in the current configuration that using hotplug
> > you can assign the ir-keyboard to a dumb console
> > and start X with e.g. MythTV  and use the remote
> > with it, without  the remote interacting with the other displays
> 
> Meaning we don't end up with joysticks acting a keyboards for the console.
> 
> I think we need a certain set of keys present to consider it a "keyboard".
> What do you think?

you are right,
the ir-keyboards IMO are easily fixable
just don't bind kbd's with PHYS=pci-......
but i think it would be good to retain the
possibility to do it manually( from userspace)

best,

svetljo

-- 
GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++

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

[James S. <jsi...@in...>]

> > I think we need a certain set of keys present to consider it a "keyboard".
> > What do you think?
> 
> you are right,
> the ir-keyboards IMO are easily fixable
> just don't bind kbd's with PHYS=pci-......
> but i think it would be good to retain the
> possibility to do it manually( from userspace)

Of course. I was thinking about a fix for the USB keyboards that show as 
two devices :-( We might have to keep track of the PHYS so we don't 
register the same device twice.

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

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

Here the logs: