From owner-freebsd-stable@FreeBSD.ORG Thu Apr 5 22:31:47 2007 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E1EF516A408 for ; Thu, 5 Apr 2007 22:31:46 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 8F17413C4B0 for ; Thu, 5 Apr 2007 22:31:46 +0000 (UTC) (envelope-from michael.schuh@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so866110ana for ; Thu, 05 Apr 2007 15:31:46 -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:cc:in-reply-to:mime-version:content-type:references; b=mi9dn0ADSy8xjRQBPfy6++BxfrVEDcYk8v24DCxjzUqpUlTuBtaQ1x6Wbr4Ww7K851lhrDTgFkQh0C64kTJdYWf3JbvGu/I+Y2wH1NErF595EkK/VS0qweAo6jiNGcb3K9rNsktt0yq7STiWI6RkrWDshqqaHkbhC72bzeGZvu4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=NoSkOUxcdgJ83juzNrQanIaD6GftCwvispzodCOmxT/eFFbsGl2zkG0YgTJP3ffirnGES5JCDsKrr2MQ79MADO22tNCZ0tVIw/4KXppQyOa3akknWuHI0KR3UZni2yNT5eV6owbdU+awdraasZdDrCUogWWMJ7gp9WAfDvspMNY= Received: by 10.100.33.14 with SMTP id g14mr1718628ang.1175812305791; Thu, 05 Apr 2007 15:31:45 -0700 (PDT) Received: by 10.100.174.20 with HTTP; Thu, 5 Apr 2007 15:31:45 -0700 (PDT) Message-ID: <1dbad3150704051531m59b5342fof2036ec6f5484a73@mail.gmail.com> Date: Fri, 6 Apr 2007 00:31:45 +0200 From: "Michael Schuh" To: "Kevin Oberman" In-Reply-To: <20070405221226.9EF6F45055@ptavv.es.net> MIME-Version: 1.0 References: <1dbad3150704050357i6b973118q260265644665b405@mail.gmail.com> <20070405221226.9EF6F45055@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Stable , schiz0phrenic21@gmail.com Subject: Re: Changing Console Resolution - Vidcontrol X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2007 22:31:47 -0000 Hi Kevin, hi @list, ok losing data in output is not really nice, in my experiences i don't lose lines, they get not displayed, if i use scroll-lock and pg-up, i can see the lines they was on the screen before i change the mode. If you need more lines in buffer (esp. to supress losing lines) you can change the default (200 lines) in your kernels. take a look at /usr/src/sys/conf/NOTES and /usr/src/i386/conf/NOTES, search "SC*BUFFER" but keep in mind this can make a "slideshow" like teleporting on your console :-D (remembers me to ego-shooters and jump'n'run games) (only to be complete..) Yes i agree with they peoples that mentoid to using X and/or ssh/xterms, but i could understand the needs for getting more data and less confusion on starting up the servers. Sometimes, proably in testing, we sitting directly on the console(sometimes up on the box :-D) and we woul= d see whats going on on boot time, so we can interrupt something more quickly..... And yes, i stay very close to those who say X or graphical UI has nothing to search on a server, it uses some ressources they are assigned to services..... cheers michael 2007/4/6, Kevin Oberman : > > > Date: Thu, 5 Apr 2007 12:57:09 +0200 > > From: "Michael Schuh" > > Sender: owner-freebsd-stable@freebsd.org > > > > Hi, > > > > first i understand your need's right! More Text on screen at boot time, > > but i have never get this working at boot time, but directly after boot= . > > > > In my case my Kernels would be compiles with: > > options SC_PIXEL_MODE > > > > and in /boot/loader.conf > > vesa_load=3D"YES" > > > > and in /etc/rc.conf something like this: > > keymap=3D"german.iso" > > font8x16=3D"iso15-8x16" > > font8x14=3D"iso15-8x14" > > font8x8=3D"iso15-8x8" > > allscreens_flag=3D"MODE_280" > > > > In my case with german keyboard, change these things to > > your needs. > > The allscreens_flag you could get as mentoided in other answers with > > vidcontrol -i mode, i remember that someone has tell you to use > > MODE_279, but i doesn't know if this is the best case for all cards. > > > > For a single test you can set the mode from one terminal (like ttyv0) > > after logging in with > > vidcontrol MODE_280 > > or that likes to your modes for your Graphiccard. > > > > If anyone else knows how we can set the vid-mode at boot-time so that > the > > bootmessages are every time in such a mode tell me please how it > > works. In the Kernel NOTEs i have only found a line like > > options VGA_WIGTH90, but thi is not my desired resolution. > > I used to do this, but I discovered that my scrollback buffer "lost" th > 24 lines in the screen when the mode changes and I couldn't live with > that. > > It would be nice to have the display at boot time, but, if I did not > lose data, I would be happy to have it from when it starts. > > In any case, I figure that people who want X, will go with X. Some folks > still like a plain old command-line console. I use X, but I don't start > with xdm, kdm, or any other. I still like to see what is happening and > enter 'startx' when I am good and ready. Sometimes I am not ready for the > entire session. I don't always want all of X sitting between me and my > CLI. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 > > --=20 =3D=3D=3D michael-schuh.net =3D=3D=3D Michael Schuh Preu=DFenstr. 13 66111 Saarbr=FCcken phone: 0681/8319664 mobil: 0177/9738644 @: michael.schuh@gmail.com =3D=3D=3D Ust-ID: DE251072318 =3D=3D=3D