From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 03:37:02 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F087516A474 for ; Tue, 5 Jun 2007 03:37:02 +0000 (UTC) (envelope-from saltmiser@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.181]) by mx1.freebsd.org (Postfix) with ESMTP id 9D8C413C457 for ; Tue, 5 Jun 2007 03:37:02 +0000 (UTC) (envelope-from saltmiser@gmail.com) Received: by py-out-1112.google.com with SMTP id a29so2753028pyi for ; Mon, 04 Jun 2007 20:37:01 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UQi4Sm3obmIdu17p2G1Xg3ChgLXyEgeS/oKsHbqFSKuZ6obiVh0u3F4twVUbsR1jO7YJAsN06kk0KfwW2lgGe54GcQaoiRI/7QlTjlSX4IakOjVBUTHqb8Iuy1WtcIw+HflWX9eqMlMxlsCi61WDI83NqAAmf/uJygdH7pMrv5k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=TXrth26pejJl2vEKgeADw7SKM2tEA0ZmOjK8JOUAi2UISxxj+8FKq+rKO6m3NDIIjX9H9ER4jiZmoiVl/WXRHHaRbh1tpwdv/WZ44FvNcwg5ZWnXBHzCddut4fTHBN2M7zy0cq1Lma4+P8XghSxevSglSgmcuaT+LzFcy3kIXOg= Received: by 10.65.95.12 with SMTP id x12mr8105716qbl.1181014621469; Mon, 04 Jun 2007 20:37:01 -0700 (PDT) Received: by 10.64.76.14 with HTTP; Mon, 4 Jun 2007 20:37:01 -0700 (PDT) Message-ID: <37f72b1f0706042037y6b84ff5drfe74ede445ab22f6@mail.gmail.com> Date: Mon, 4 Jun 2007 23:37:01 -0400 From: "Jim Capozzoli" To: freebsd-questions@freebsd.org In-Reply-To: <37f72b1f0706042036n43340d1cid0e121af137ae410@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <37f72b1f0706021126g3347c683u37a87d3145e6e571@mail.gmail.com> <37f72b1f0706040829l338c4c7fr5229e8807705daed@mail.gmail.com> <37f72b1f0706040830g3f3414cet30ea686e0a325c9@mail.gmail.com> <200706041424.37437.lists@jnielsen.net> <37f72b1f0706042036n43340d1cid0e121af137ae410@mail.gmail.com> Subject: re: X11 & console setup X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 03:37:03 -0000 On 6/4/07, John Nielsen wrote: > On Monday 04 June 2007 11:30:03 am Jim Capozzoli wrote: > > On 6/4/07, John Nielsen wrote: > > > On Saturday 02 June 2007 04:00:57 pm Kevin Kinsey wrote: > > > > Jim Capozzoli wrote: > > > > > Hello list, > > > > > > > > > > I have 3 monitors and 3 video cards. However, one videocard and > > > > > monitor isn't very "X11 friendly." (X11 barely starts on it). I was > > > > > wondering if it would be possible to have X11 running on two of the > > > > > monitors, and then have a full screen console (like a ttyv0) on the > > > > > third monitor (so I could constantly leave top or something sweet > > > > > running on there :D). This is all with FreeBSD 6.2/i386 and Xorg 6.9 > > > > > or 7.2. Any suggestions? Thanks. > > > > > > > > It should do "do-able", perhaps somewhat easily. > > > > /usr/ports/x11-servers/x2x is what comes to mind --- IIRC, Greg > > > > "groggy" Lehey of "The Complete FreeBSD" fame uses this for several > > > > displays, and has notes on his setup in her personal pages at > > > > www.lemis.com. > > > > > > That link is here: http://www.lemis.com/grog/hardware.html > > > > > > However, I'm not sure x2x is relevant to the OP--It can be used to allow > > > one mouse and keyboard to be used on multiple X servers, but doesn't have > > > anything to do with console mode. > > > > > > I don't know if the setup the OP wants is possible or not, but here are > > > some notes: > > > > > > The FreeBSD console always runs on the "primary" display as determined by > > > the BIOS. Most systems give you a choice between using AGP or PCI as the > > > primary display. If you have multiple PCI cards it is usually the first > > > one on the bus (physically this is often the one closest to the CPU). Not > > > sure how ISA figures in. You will want to make your "bad" videocard and > > > monitor the primary display. > > > > > > Once you have that, I'd just run an "Xorg -configure" to get started. If > > > X comes up at all using the config generated from that then it will be a > > > good starting point. Try commenting out the device and screen sections > > > (and possibly also a line under ServerLayout) for your "bad" display and > > > see if X comes up on the other two. By default it expects to be running > > > on the console so I'm not sure what will happen here. You also want it to > > > grab the keyboard and mouse unless you have a second keyboard. Some trial > > > and error and further research are probably required. Play with startx vs > > > xdm, see what happens when you press ctrl-alt-f1, etc. I'm assuming > > > you'll want to use Xinerama to join the two X displays and allow > > > window-dragging between them, etc. > > > > > > If you don't get acceptable results using your original plan, you can > > > always hack together your own "console" to run on the weakest display > > > under X (using the vesa driver if necessary). If possible (not sure it > > > is), don't make it part of your Xinerama display. Then don't run a window > > > manager on it. Use xsetroot as part of your X init script to control > > > what's on the background. This will apply to your entire display but the > > > WM will probably take over once it starts on the "good" screens. You > > > could make one or more scripts to run things on your "bad" screen by > > > doing something like this: > > > > > > #!/bin/sh > > > DISPLAY=:0.1 #might also be :0.2 or :0.0 > > > export DISPLAY > > > xterm -r -geometry 120x60 /usr/bin/top > > > > > > Experiment with the geometry settings to see what fills your screen > > > appropriately. You might also want to get a nice bitmap font to give the > > > xterm more of a terminal "feel". I have one I stole from bochs or > > > somewhere that's not bad (I use it for Nethack). E-mail me off-list if > > > you want it. > > > > > > That should just about do it. Do write back to the list to tell us what > > > you learn and what works the best. > > > > > > JN > > > > I like the not making it a part of the Xinerama display..that would be > > interesting, because I'm sure a very basic X11 background with a xterm > > would work on there. If X starts on there, then yeah great but the > > problem is I don't ever recall getting it to work properly. > > If the card functions at all then I'm sure you could get the vesa driver > running at 800x600x8 at least.. > > > What I had in mind however, is say having the weak monitor/card as the > > 'default' display that the BIOS picks up, and then leaving a console > > on there BUT having X11 on the two other monitors. Then I'd run top > > on it or something, so I"d have a command like... > > > > $ startxfce4 & top -s 1 > > > > And then on the 'default' BIOS chosen display, you would see top > > running in console mode, and then pretty xfce with nice 1280x1024 ver > > monitor resolution on the other two (using Xinerama). I wouldn't need > > to have keyboard/mouse control on the 'default' console then, I'd just > > look at it to see which process is eating the machine, load averages, > > etc. > > My suggestion for running the weak display under X was conditional on not > getting results you liked with your original idea. Re-read the first part of > my first reply. > > JN > Ah yes you're right, it managed to start what looks like 640x480...of course the only problem now is I lost 24 bit color but I can live without that. :P Thanks for all the help guys. -- Jim Capozzoli D6499626857801B6065013E3645A6B75