Re: FreeBSD 7 AMD64 Console resolution

2008-06-27 Thread Fernando Apesteguía
On Fri, Jun 27, 2008 at 8:25 PM, Kevin Kinsey <[EMAIL PROTECTED]> wrote: > Fernando Apesteguía wrote: >> >> Hi, >> >> Is there any way of changing the console resolution in FreeBSD for AMD64? >> AFAIK, the VESA option is only available for i386. >> >

Re: FreeBSD 7 AMD64 Console resolution

2008-06-27 Thread Kevin Kinsey
Fernando Apesteguía wrote: Hi, Is there any way of changing the console resolution in FreeBSD for AMD64? AFAIK, the VESA option is only available for i386. I really hate the default mode :S... Any hints? Thanks in advance Err, isn't vidcontrol(1) helping? KDK -- Toothpaste never

FreeBSD 7 AMD64 Console resolution

2008-06-27 Thread Fernando Apesteguía
Hi, Is there any way of changing the console resolution in FreeBSD for AMD64? AFAIK, the VESA option is only available for i386. I really hate the default mode :S... Any hints? Thanks in advance ___ freebsd-questions@freebsd.org mailing list http

Re: Changing Console Resolution - Vidcontrol

2007-04-02 Thread Schiz0
Yeah, I do SSH in most of the time, but with the vmware window open, I'm always tempted to type commands in there. So I figured it'd be nice just to be able to have a nice sized window to do it in. On 4/3/07, Chris Slothouber <[EMAIL PROTECTED]> wrote: Wouldn't it be easier to ssh in Windows in

Re: Changing Console Resolution - Vidcontrol

2007-04-02 Thread Chris Slothouber
Wouldn't it be easier to ssh in Windows in to your virtual machine? This would certainly be a lot more effective at getting used to working with FreeBSD remotely, if you are indeed replacing a Linux box that you work on remotely. - Chris Slothouber Schiz0 wrote: I'd just like to be able to

Re: been buggin' me for a while now (console resolution)

2006-07-29 Thread Nikolas Britton
On 7/10/06, Peter <[EMAIL PROTECTED]> wrote: Hi, I am running 5.4-STABLE and I would like to have better resolution (more lines and columns) when I boot into console. I used to be able to issue a command once there but I have forgotten that command. I remember trying to allude to it via rc.conf

Re: been buggin' me for a while now (console resolution)

2006-07-29 Thread Igor Robul
On Tue, Jul 11, 2006 at 11:58:19AM +0300, Giorgos Keramidas wrote: > Also, please *trim* the quoted material. Having to skim again and again > through multi-hundred posts of quoted material to find out that you have > only added about 2 lines of text near the end is silly. I agree with you about l

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Parv
in message <[EMAIL PROTECTED]>, wrote Giorgos Keramidas thusly... > > On 2006-07-11 12:05, Peter <[EMAIL PROTECTED]> wrote: > >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > >> What do you see in your HOME directory with: > >> > >>$ ls -ld .*profile .*rc ... > > $ ls -ld .*profile .*rc > >

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 14:11, Peter <[EMAIL PROTECTED]> wrote: >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >> I just tested here, with the CVS mirroring account I have at this >> workstation, by: > > [snip] > >> and when I su(1) to this account, the .profile is used by bash! > > There is no question t

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-11 12:39, Peter <[EMAIL PROTECTED]> wrote: > > --- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > > > Can you please also send the output of: > > > > > > $ ls -ld .bash* .sh* .profile > > > > $ ls -ld .bash* .sh* .profile > > -rw

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 12:39, Peter <[EMAIL PROTECTED]> wrote: > --- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > > Can you please also send the output of: > > > > $ ls -ld .bash* .sh* .profile > > $ ls -ld .bash* .sh* .profile > -rw-rw 1 peter users 7.7K Jul 11 09:31 .bash_history > -rw-rw-

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > Can you please also send the output of: > > $ ls -ld .bash* .sh* .profile $ ls -ld .bash* .sh* .profile -rw-rw 1 peter users 7.7K Jul 11 09:31 .bash_history -rw-rw 1 peter users 1.6K Jul 4 15:31 .profile -rw-rw 1 pete

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 12:05, Peter <[EMAIL PROTECTED]> wrote: >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >> What do you see in your HOME directory with: >> >> $ ls -ld .*profile .*rc >> >> In my local setup here, I see something like this: >> >> $ pwd >> /home/giorgos >> $ ls -ld .b

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-11 11:18, Peter <[EMAIL PROTECTED]> wrote: > >>> I added this option but I still do not get my ~/.profile sourced > >>> (no aliases). Going '. ~/.profile' gives me my aliases. How > does > >>> aterm know what file to look for? > >> >

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 11:18, Peter <[EMAIL PROTECTED]> wrote: >>> I added this option but I still do not get my ~/.profile sourced >>> (no aliases). Going '. ~/.profile' gives me my aliases. How does >>> aterm know what file to look for? >> >> aterm doesn't care about .profile or other files. It starts

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread John Nielsen
On Tuesday 11 July 2006 08:43, Peter wrote: > --- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > > On 2006-07-10 23:32, Peter <[EMAIL PROTECTED]> wrote: > > >--- Stubborn <[EMAIL PROTECTED]> wrote: > > >> You need to recompile your kernel with below > > >> options VESA > > > > > > Allright,

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-11 09:40, Peter <[EMAIL PROTECTED]> wrote: > >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > >>On 2006-07-11 09:09, Peter <[EMAIL PROTECTED]> wrote: > >>> I have the following in my .xinitrc file: > >>> > >>> aterm -e screen & > >

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 09:40, Peter <[EMAIL PROTECTED]> wrote: >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >>On 2006-07-11 09:09, Peter <[EMAIL PROTECTED]> wrote: >>> I have the following in my .xinitrc file: >>> >>> aterm -e screen & >>> >>> What is happening is that neither /etc/profile nor ~/.pro

Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-11 09:09, Peter <[EMAIL PROTECTED]> wrote: > > I have the following in my .xinitrc file: > > > > aterm -e screen & > > > > What is happening is that neither /etc/profile nor ~/.profile are > > being read. How can I get either of the

aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 09:09, Peter <[EMAIL PROTECTED]> wrote: > I have the following in my .xinitrc file: > > aterm -e screen & > > What is happening is that neither /etc/profile nor ~/.profile are > being read. How can I get either of them to be sourced? By default, xterm, rxvt, aterm and various othe

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-11 08:43, Peter <[EMAIL PROTECTED]> wrote: > >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > >>On 2006-07-10 23:32, Peter <[EMAIL PROTECTED]> wrote: > >>>--- Stubborn <[EMAIL PROTECTED]> wrote: > You need to recompile your ker

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 08:43, Peter <[EMAIL PROTECTED]> wrote: >--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: >>On 2006-07-10 23:32, Peter <[EMAIL PROTECTED]> wrote: >>>--- Stubborn <[EMAIL PROTECTED]> wrote: You need to recompile your kernel with below options VESA >>> >>> Allright, di

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread Peter
--- Giorgos Keramidas <[EMAIL PROTECTED]> wrote: > On 2006-07-10 23:32, Peter <[EMAIL PROTECTED]> wrote: > >--- Stubborn <[EMAIL PROTECTED]> wrote: > >> You need to recompile your kernel with below > >> options VESA > > > > Allright, did that. > > > >> You need to include these in your rc

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread Giorgos Keramidas
On 2006-07-11 12:04, Stubborn <[EMAIL PROTECTED]> wrote: > [snip 312 lines of quoted material] > > Peter, > > have you tried rebooting your box and put allscreens_flags="132x25" in > your rc.conf? That won't work if his adapter doesn't support 132x25 either. Also, please *trim* the quoted materia

Re: been buggin' me for a while now (console resolution)

2006-07-11 Thread Giorgos Keramidas
On 2006-07-10 23:32, Peter <[EMAIL PROTECTED]> wrote: >--- Stubborn <[EMAIL PROTECTED]> wrote: >> You need to recompile your kernel with below >> options VESA > > Allright, did that. > >> You need to include these in your rc.conf >> allscreens_flags="132x25" > > I'm trying manually first an

Re: been buggin' me for a while now (console resolution)

2006-07-10 Thread Stubborn
Peter wrote: --- Stubborn <[EMAIL PROTECTED]> wrote: Peter wrote: Hi, I am running 5.4-STABLE and I would like to have better resolution (more lines and columns) when I boot into console. I used to be able to issue a command once there but I have forgotten

Re: been buggin' me for a while now (console resolution)

2006-07-10 Thread Peter
--- Stubborn <[EMAIL PROTECTED]> wrote: > Peter wrote: > > Hi, I am running 5.4-STABLE and I would like to have better > resolution > > (more lines and columns) when I boot into console. I used to be > able > > to issue a command once there but I have forgotten that command. I > > remember tryin

Re: been buggin' me for a while now (console resolution)

2006-07-10 Thread Peter
--- Atom Powers <[EMAIL PROTECTED]> wrote: > On 7/10/06, Peter <[EMAIL PROTECTED]> wrote: > > So does anyone know how I can automatically get smaller fonts in my > > console? > > > > This is the best I was able to do without loading the vesa driver, > which I haven't bothered to do since it's "j

Re: been buggin' me for a while now (console resolution)

2006-07-10 Thread Stubborn
Peter wrote: Hi, I am running 5.4-STABLE and I would like to have better resolution (more lines and columns) when I boot into console. I used to be able to issue a command once there but I have forgotten that command. I remember trying to allude to it via rc.conf or a startup file (rc.local?) b

Re: been buggin' me for a while now (console resolution)

2006-07-10 Thread Atom Powers
On 7/10/06, Peter <[EMAIL PROTECTED]> wrote: So does anyone know how I can automatically get smaller fonts in my console? This is the best I was able to do without loading the vesa driver, which I haven't bothered to do since it's "just" a server. cat /etc/rc.conf #Terminal settings keymap="u

been buggin' me for a while now (console resolution)

2006-07-10 Thread Peter
Hi, I am running 5.4-STABLE and I would like to have better resolution (more lines and columns) when I boot into console. I used to be able to issue a command once there but I have forgotten that command. I remember trying to allude to it via rc.conf or a startup file (rc.local?) but it did not w

Re: applying the vesa patch to stable for high console resolution

2005-06-17 Thread Didier Wiroth
L] Re: applying the vesa patch to stable for high console resolution Yet another thing to ask. I have a wide screen laptop where the VBIOS does not report correct resolutions, has the system taken steps to correct this? ~Its an Intel i915GM, 15.4", native windows o

Re: applying the vesa patch to stable for high console resolution

2005-06-17 Thread Didier Wiroth
From: Igor Pokrovsky [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 19:28 To: Didier Wiroth Cc: freebsd-stable@freebsd.org; freebsd-questions@freebsd.org Subject: [SPAM-PAL] Re: applying the vesa patch to stable for high console resolution On Mon, Jun 13, 2005 at 10:46:26PM +0200, Didier Wi

Re: applying the vesa patch to stable for high console resolution

2005-06-16 Thread Remington L
Yet another thing to ask. I have a wide screen laptop where the VBIOS does not report correct resolutions, has the system taken steps to correct this? ~Its an Intel i915GM, 15.4", native windows of 1200x800 On 6/16/05, Igor Pokrovsky <[EMAIL PROTECTED]> wrote: > > On Mon, Jun 13, 2005 at 10:4

Re: applying the vesa patch to stable for high console resolution

2005-06-16 Thread Igor Pokrovsky
On Mon, Jun 13, 2005 at 10:46:26PM +0200, Didier Wiroth wrote: > Hi, > > USE AT YOUR OWN RISK! > > this for the freebsd5 branch only How about RELENG_4? Is it possible to port it there? -ip -- Never put all your eggs in your pocket. ___ free

Re: applying the vesa patch to stable for high console resolution

2005-06-14 Thread Giorgos Keramidas
On 2005-06-13 22:06, Ted Mittelstaedt <[EMAIL PROTECTED]> wrote: >> http://people.freebsd.org/~delphij/vesa/patchset-highres.20050522 > > Has this patch beeen applied to CURRENT? So it will be in the next > release of FreeBSD? Yes. ___ freebsd-question

RE: applying the vesa patch to stable for high console resolution

2005-06-13 Thread Ted Mittelstaedt
freebsd-questions@freebsd.org >Subject: applying the vesa patch to stable for high console resolution > > >Hi, > >USE AT YOUR OWN RISK! > >this for the freebsd5 branch only > >Here is how to apply the patch to get the "long awaited" high >console

applying the vesa patch to stable for high console resolution

2005-06-13 Thread Didier Wiroth
Hi, USE AT YOUR OWN RISK! this for the freebsd5 branch only Here is how to apply the patch to get the "long awaited" high console text modes under freebsd! I actually use it on my nc6000 hp laptop with the following mode: 1400x1050x16 damm .. really nice ;-)) This patch is actually for

External Monitor console resolution black screen after exiting KDE

2005-03-01 Thread Troy
I'm having a strange problem and figured to post to the list for any insight. I have an IBM T23 ThinkPad and am running RELENG_5 (currently 5.4) branch. Everything works fine if the laptop is not connected to the KVM. I can boot up, launch KDE, exit and the console resets itself fine. When I'

Re: console resolution on a T41

2005-01-18 Thread Emanuel Strobl
Am Dienstag, 18. Januar 2005 08:07 schrieb Galanaki, Dimitrios: > I am trying to increase the console resolution on my Thinkpad T41 which has > an ATI mobility radeon card. > > >From what I read the standard step is to add the lines following lines in > > the kernel configur

console resolution on a T41

2005-01-17 Thread Galanaki, Dimitrios
I am trying to increase the console resolution on my Thinkpad T41 which has an ATI mobility radeon card. >From what I read the standard step is to add the lines following lines in the kernel configuration file: options VESA options SC_PIXEL_MODE However when I run vidcontrol -g 100

Re: Console resolution

2003-12-10 Thread Cordula's Web
> > Problem is that this notebok Toshiba, has *very* ugly system font. On > > RedHat I solved this problem, by giving higher resolution to text mode > > (which I what I would like to do here). I am wondering if this is also > > possible on freebsd. I use text mode a lot, so this is quite importa

Re: Console resolution

2003-12-08 Thread Jez Hancock
On Mon, Dec 08, 2003 at 09:10:13PM +, Jez Hancock wrote: > Note you can test those settings out from the console using kbdcontrol. My bad - that should be 'vidcontrol' of course as someone else pointed out! -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ __

Re: Console resolution

2003-12-08 Thread Jez Hancock
On Mon, Dec 08, 2003 at 09:35:57PM +0100, Aleksander Rozman - Andy wrote: > Problem is that this notebok Toshiba, has *very* ugly system font. On > RedHat I solved this problem, by giving higher resolution to text mode > (which I what I would like to do here). I am wondering if this is also > po

Re: Console resolution

2003-12-08 Thread sebastian ssmoller
try "man 1 vidcontrol" hth seb On Mon, 2003-12-08 at 21:35, Aleksander Rozman - Andy wrote: > Hi ! > > I have just installed FreeBSD onto my notebook. I am using FreeBSD for > quite some time, and now I decided to install it on my notebook (I got > tired of both RedHat and Windows 2000, which

Console resolution

2003-12-08 Thread Aleksander Rozman - Andy
Hi ! I have just installed FreeBSD onto my notebook. I am using FreeBSD for quite some time, and now I decided to install it on my notebook (I got tired of both RedHat and Windows 2000, which both didn't work as they should (I had both installed on same computer)) and remove everything else fr

freebsd console resolution vs linux console resolution

2003-02-07 Thread Didier Wiroth
Hey, 1) Are true bitmapped graphical consoles possible in freebsd, I mean at least like the resolution of the Vesafb driver in Linux? (Something like 16, 24 or even 32bpp with 1280x1024 screen resolutions) 2) If not, is a "Linux Vesafb" like driver planned for freebsd future releases? Thanks a l