Re: FreeBSD 7 AMD64 Console resolution
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. >> >> I really hate the default mode :S... >> >> Any hints? >> >> Thanks in advance > > Err, isn't vidcontrol(1) helping? No. vidcontrol -i mode shows only one mode, the default one (80x25, font 8x16) > > KDK > > -- > Toothpaste never hurts the taste of good scotch. > > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7 AMD64 Console resolution
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 hurts the taste of good scotch. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 7 AMD64 Console resolution
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://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Changing Console Resolution - Vidcontrol
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 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 type commands without having them wrap to the > next line. Same goes to compiling software: More screen space = Less data > flying by at once = More time to read whatever's going on, let it be > errors, > warnings, whatever. > > And in my case, because I'm running it in VMWare at the moment due to the > fact that I'm new to BSD and I'd like to learn before I put it into > production, the console window barely fills the VMWare window, so I'm > wasting a whole lot of space. Half the screen is just blank. > > On 4/2/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote: >> >> >> I don't understand why people who want high resolution consoles don't run >> X. >> >> It is a *lot* faster for the vast majority of cards (ie ones which aren't >> doing VESA modes). >> >> Scrolling a screen full of text at a decent resolution using VESA == >> slideshow. >> >> > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED] " ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to " [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Changing Console Resolution - Vidcontrol
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 type commands without having them wrap to the next line. Same goes to compiling software: More screen space = Less data flying by at once = More time to read whatever's going on, let it be errors, warnings, whatever. And in my case, because I'm running it in VMWare at the moment due to the fact that I'm new to BSD and I'd like to learn before I put it into production, the console window barely fills the VMWare window, so I'm wasting a whole lot of space. Half the screen is just blank. On 4/2/07, Daniel O'Connor <[EMAIL PROTECTED]> wrote: I don't understand why people who want high resolution consoles don't run X. It is a *lot* faster for the vast majority of cards (ie ones which aren't doing VESA modes). Scrolling a screen full of text at a decent resolution using VESA == slideshow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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 or a startup file (rc.local?) but it did not work. It seems to me that I needed the following in my rc.conf as a pre-requisite: font8x8="iso-8x8.fnt" font8x14="iso-8x14.fnt" font8x16="iso-8x16.fnt" So does anyone know how I can automatically get smaller fonts in my console? I can't believe no one has told you this! Put this in the kernel: options VESA# VESA BIOS support options SC_PIXEL_MODE # Raster text (VESA graphic modes) now rebuild the kernel and add this to /etc/rc.conf: allscreens_flags="MODE_282" You will have a 1280x1024 console after you reboot if your video card has a real VESA BIOS. If that's too much console for you try MODE_279 (1024x768). For a full list of modes supported by your video card type in at the console (it won't work in an X) 'vidcontrol -i mode |grep G' the first column lists the MODE id number. To change the mode on the fly use 'vidcontrol MODE_mode'. Also try the extra cool blinking block cursor with: allscreens_flags=" -c blink MODE_282". -- BSD Podcasts @: http://bsdtalk.blogspot.com/ http://freebsdforall.blogspot.com/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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 lots of quoted text, but ... hitting "S" in mutt will jump you to next "unquoted" part of message. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 > > -rw-rw 1 peter users 767B Jul 29 2005 .cshrc > > -rw--- 1 peter users26B May 2 11:08 .dmrc > > -rw-rw 1 peter users 331B Jul 29 2005 .mailrc > > -rw-rw 1 peter users31B Jun 28 21:33 .mcoprc > > -rw-rw 1 peter users 1.6K Jul 4 15:31 .profile > > -rw-r--r-- 1 peter users 616B Jun 19 22:10 .screenrc > > -rw-rw 1 peter users 975B Jul 29 2005 .shrc > > -rw-rw 1 peter users 402B Jul 11 09:29 .xinitrc ... > Sorry for the bogus request. I meant: > > $ ls -ld .bash* .sh* .profile If Peter had a ~/.bash_profile that would have shown even with your first request. So ... relax. - Parv -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 that .profile is sourced when I log in. It is > sourced. It is only not sourced when I invoke aterm from within > .xnitrc: > > aterm -ls -e screen & Aha. I think I'm getting somewhere. If I run xterm with the -e option, regardless of -ls being present or not, the shell used to spawn the -e command is *NOT* a login shell. This way, when I run: xterm => not login shell xterm -ls => login shell xterm -e /bin/sh=> not login shell xterm -ls -e /bin/sh=> not login shell either So it's not the -ls option that is causing your aterm windows to be non-login shells, but it looks like it is the -e option that does this. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
--- 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-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 peter users 975B Jul 29 2005 .shrc > > Strange, there is no .bash_profile but you still see .profile is > unused? > > 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 that .profile is sourced when I log in. It is sourced. It is only not sourced when I invoke aterm from within .xnitrc: aterm -ls -e screen & >From before I know that this *does* result in a sourcing of the file: aterm -e login & >From the bash man page: When bash is invoked as an interactive login shell, or as a non-inter- active shell with the --login option, it first reads and executes com- mands from the file /etc/profile, if that file exists. After reading that file, it looks for ~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 1 peter users 1.6K Jul 4 15:31 .profile > -rw-rw 1 peter users 975B Jul 29 2005 .shrc Strange, there is no .bash_profile but you still see .profile is unused? I just tested here, with the CVS mirroring account I have at this workstation, by: * moving .bash_profile and .bashrc away * adding an 'echo' message in its .profile file: echo ".profile done" and when I su(1) to this account, the .profile is used by bash! gothmog# su - ncvs .profile done [EMAIL PROTECTED] ~]$ echo $SHELL /usr/local/bin/bash [EMAIL PROTECTED] ~]$ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
--- 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 peter users 975B Jul 29 2005 .shrc __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 .bash* .sh* .profile >> -rw--- 1 giorgos giorgos - 30103 Jul 11 18:47 .bash_history >> -rw-rw-r-- 1 giorgos giorgos - 318 Jul 11 17:47 .bash_profile >> -rw-rw-r-- 1 giorgos giorgos - 3742 Jul 11 18:17 .bashrc >> -rw-rw-r-- 1 giorgos giorgos - 1006 Mar 29 07:19 .profile >> -rw-rw-r-- 1 giorgos giorgos - 1433 Nov 18 2004 .shrc > > > $ ls -ld .*profile .*rc > -rw-rw 1 peter users 767B Jul 29 2005 .cshrc > -rw--- 1 peter users26B May 2 11:08 .dmrc > -rw-rw 1 peter users 331B Jul 29 2005 .mailrc > -rw-rw 1 peter users31B Jun 28 21:33 .mcoprc > -rw-rw 1 peter users 1.6K Jul 4 15:31 .profile > -rw-r--r-- 1 peter users 616B Jun 19 22:10 .screenrc > -rw-rw 1 peter users 975B Jul 29 2005 .shrc > -rw-rw 1 peter users 402B Jul 11 09:29 .xinitrc Damn :( Sorry for the bogus request. I meant: $ ls -ld .bash* .sh* .profile and I correctly used this in my own check, but then forgot to fix the one I asked you for. What you sent doesn't show any .bash* files and I still don't know if you have both a .bash_profile and a .profile file. Can you please also send the output of: $ ls -ld .bash* .sh* .profile Sorry for the confusion... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
--- 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? > >> > >> aterm doesn't care about .profile or other files. It starts a > shell, > >> based on the $SHELL environment variable and your login shell from > >> `/etc/passwd'. > >> > >> What shell are you using? > > > > $ echo $SHELL > > /usr/local/bin/bash > > > > $ grep peter /etc/passwd > > peter:*:1002:100:User &:/home/peter:/usr/local/bin/bash > > > > Do I need to set up a different file (.bashrc)? > > GNU bash will not read .profile if you also have a .bash_profile > file. > > 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 .bash* .sh* .profile > -rw--- 1 giorgos giorgos - 30103 Jul 11 18:47 > .bash_history > -rw-rw-r-- 1 giorgos giorgos - 318 Jul 11 17:47 > .bash_profile > -rw-rw-r-- 1 giorgos giorgos - 3742 Jul 11 18:17 .bashrc > -rw-rw-r-- 1 giorgos giorgos - 1006 Mar 29 07:19 .profile > -rw-rw-r-- 1 giorgos giorgos - 1433 Nov 18 2004 .shrc $ ls -ld .*profile .*rc -rw-rw 1 peter users 767B Jul 29 2005 .cshrc -rw--- 1 peter users26B May 2 11:08 .dmrc -rw-rw 1 peter users 331B Jul 29 2005 .mailrc -rw-rw 1 peter users31B Jun 28 21:33 .mcoprc -rw-rw 1 peter users 1.6K Jul 4 15:31 .profile -rw-r--r-- 1 peter users 616B Jun 19 22:10 .screenrc -rw-rw 1 peter users 975B Jul 29 2005 .shrc -rw-rw 1 peter users 402B Jul 11 09:29 .xinitrc __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 a shell, >> based on the $SHELL environment variable and your login shell from >> `/etc/passwd'. >> >> What shell are you using? > > $ echo $SHELL > /usr/local/bin/bash > > $ grep peter /etc/passwd > peter:*:1002:100:User &:/home/peter:/usr/local/bin/bash > > Do I need to set up a different file (.bashrc)? GNU bash will not read .profile if you also have a .bash_profile file. 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 .bash* .sh* .profile -rw--- 1 giorgos giorgos - 30103 Jul 11 18:47 .bash_history -rw-rw-r-- 1 giorgos giorgos - 318 Jul 11 17:47 .bash_profile -rw-rw-r-- 1 giorgos giorgos - 3742 Jul 11 18:17 .bashrc -rw-rw-r-- 1 giorgos giorgos - 1006 Mar 29 07:19 .profile -rw-rw-r-- 1 giorgos giorgos - 1433 Nov 18 2004 .shrc $ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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, did that. [snip] > I can manually get 80x60 with 'vidcontrol 80x60' and this is good > enough for me. How do I automate this at bootup? I typically can do "VGA_80x60" on most modern hardware. I can't remember what the difference between the "VGA" modes and others are, but I knew at one point and decided that "VGA" modes were better. Also, if that's not good enough for you then you can use arbitrary VESA graphics modes (as long as you're running 6.x or -CURRENT). On this machine I have: allscreens_flags="-f 8x14 cp437-8x14.fnt MODE_346" In /etc/rc.conf. On my video hardware, mode 346 is: 346 (0x15a) 0x000f G 1600x1200x32 1 8x16 0xa 64k 64k 0x8800 8000k That gives me a 1600x1200 raster display using an 8x14 font, for a console size of 85 rows and 200 columns. You can experiment with different modes (and font sizes) until you find a combination that a) works and b) you like. Use vidcontrol from the command line to experiment before modifying rc.conf, so you can switch to another virtual terminal if you switch to an unsupported mode. HTH, JN ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
--- 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 & > >>> > >>> 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 other terminal > emulators > >> start non-login shells. This means that .profile is not sourced > by > >> the > >> shell spawned by the terminal. You can enable a `login shell' > inside > >> one of these terminal emulators with the -ls option: > >> > >>aterm -ls -e screen & > >> > > > > 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 a shell, > based on the $SHELL environment variable and your login shell from > `/etc/passwd'. > > What shell are you using? $ echo $SHELL /usr/local/bin/bash $ grep peter /etc/passwd peter:*:1002:100:User &:/home/peter:/usr/local/bin/bash Do I need to set up a different file (.bashrc)? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 ~/.profile are >>> being read. How can I get either of them to be sourced? >> >> By default, xterm, rxvt, aterm and various other terminal emulators >> start non-login shells. This means that .profile is not sourced by >> the >> shell spawned by the terminal. You can enable a `login shell' inside >> one of these terminal emulators with the -ls option: >> >> aterm -ls -e screen & >> > > 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 a shell, based on the $SHELL environment variable and your login shell from `/etc/passwd'. What shell are you using? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
--- 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 them to be sourced? > > By default, xterm, rxvt, aterm and various other terminal emulators > start non-login shells. This means that .profile is not sourced by > the > shell spawned by the terminal. You can enable a `login shell' inside > one of these terminal emulators with the -ls option: > > aterm -ls -e screen & > 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? Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
aterm -e screen does not source .bashrc (was: Re: been buggin' me for a while now (console resolution))
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 other terminal emulators start non-login shells. This means that .profile is not sourced by the shell spawned by the terminal. You can enable a `login shell' inside one of these terminal emulators with the -ls option: aterm -ls -e screen & ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
--- 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 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 and it's a "no go". This is the output > of > >>> 'vidcontrol -i mode': > > > > [snip] > > > > 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k > 0x 32k > > > >> The 132x25 mode doesn't work for all video adapters, AFAIK. > >> > >> The best I have been able to use almost everywhere is 80x30. > > > > I can manually get 80x60 with 'vidcontrol 80x60' and this is good > > enough for me. How do I automate this at bootup? > > By setting your preferred mode in `/etc/rc.conf': > > allscreens_flags="80x30" > > Note that for non-default modes, you also have to set up a font in > your > `rc.conf' file, otherwise vidcontrol will refuse to change the > console > mode at bootup, so a more complete example would be: > > font8x8="iso-8x8.fnt" > allscreens_flags="80x60" > > After saving these in your `/etc/rc.conf' file you don't have to > reboot > for them to take effect, something like the following should work > too: > > hostname# /bin/sh > # vidcontrol -f 8x8 iso-8x8.fnt > # for dev in /dev/ttyv* ; do vidcontrol 80x60 < "$dev" ; done Thank you. I did it the old fashioned way (reboot). Bonus question: 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? Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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, did that. >>> You need to include these in your rc.conf allscreens_flags="132x25" >>> >>> I'm trying manually first and it's a "no go". This is the output of >>> 'vidcontrol -i mode': > > [snip] > > 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k > >> The 132x25 mode doesn't work for all video adapters, AFAIK. >> >> The best I have been able to use almost everywhere is 80x30. > > I can manually get 80x60 with 'vidcontrol 80x60' and this is good > enough for me. How do I automate this at bootup? By setting your preferred mode in `/etc/rc.conf': allscreens_flags="80x30" Note that for non-default modes, you also have to set up a font in your `rc.conf' file, otherwise vidcontrol will refuse to change the console mode at bootup, so a more complete example would be: font8x8="iso-8x8.fnt" allscreens_flags="80x60" After saving these in your `/etc/rc.conf' file you don't have to reboot for them to take effect, something like the following should work too: hostname# /bin/sh # vidcontrol -f 8x8 iso-8x8.fnt # for dev in /dev/ttyv* ; do vidcontrol 80x60 < "$dev" ; done ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
--- 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.conf > >> allscreens_flags="132x25" > > > > I'm trying manually first and it's a "no go". This is the output > of > > 'vidcontrol -i mode': [snip] 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k > The 132x25 mode doesn't work for all video adapters, AFAIK. > > The best I have been able to use almost everywhere is 80x30. I can manually get 80x60 with 'vidcontrol 80x60' and this is good enough for me. How do I automate this at bootup? Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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 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. - Giorgos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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 and it's a "no go". This is the output of > 'vidcontrol -i mode': > > 0 (0x000) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k > 1 (0x001) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k > 2 (0x002) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k > 3 (0x003) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k > 4 (0x004) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k > 5 (0x005) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k > 6 (0x006) 0x0003 G 640x200x1 1 8x8 0xb8000 32k 32k The 132x25 mode doesn't work for all video adapters, AFAIK. The best I have been able to use almost everywhere is 80x30. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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 that command. I remember trying to allude to it via rc.conf or a startup file (rc.local?) but it did not work. It seems to me that I needed the following in my rc.conf as a pre-requisite: font8x8="iso-8x8.fnt" font8x14="iso-8x14.fnt" font8x16="iso-8x16.fnt" So does anyone know how I can automatically get smaller fonts in my console? 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 and it's a "no go". This is the output of 'vidcontrol -i mode': 0 (0x000) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 1 (0x001) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 2 (0x002) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 3 (0x003) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 4 (0x004) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 5 (0x005) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 6 (0x006) 0x0003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x 32k 13 (0x00d) 0x0003 G 320x200x4 4 8x8 0xa 64k 64k 0x 256k 14 (0x00e) 0x0003 G 640x200x4 4 8x8 0xa 64k 64k 0x 256k 16 (0x010) 0x0003 G 640x350x2 2 8x14 0xa 64k 64k 0x 128k 18 (0x012) 0x0003 G 640x350x4 4 8x14 0xa 64k 64k 0x 256k 19 (0x013) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 20 (0x014) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 21 (0x015) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 22 (0x016) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 23 (0x017) 0x0001 T 40x25 8x16 0xb8000 32k 32k 0x 32k 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 32k 32k 0x 32k 26 (0x01a) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 27 (0x01b) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 28 (0x01c) 0x0003 G 320x200x8 1 8x8 0xa 64k 64k 0x 64k 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 32k 32k 0x 32k 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 32k 32k 0x 32k 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k 37 (0x025) 0x0003 G 320x240x8 4 8x8 0xa 64k 64k 0x 256k 112 (0x070) 0x T 80x43 8x8 0xb8000 32k 32k 0x 32k 113 (0x071) 0x0001 T 80x43 8x8 0xb8000 32k 32k 0x 32k 256 (0x100) 0x000f G 640x400x8 1 8x16 0xa 64k 64k 0xe000 262144k 257 (0x101) 0x000f G 640x480x8 1 8x16 0xa 64k 64k 0xe000 262144k 258 (0x102) 0x000b G 800x600x4 4 8x16 0xa 64k 64k 0x 262144k 259 (0x103) 0x000f G 800x600x8 1 8x16 0xa 64k 64k 0xe000 262144k 260 (0x104) 0x000b G 1024x768x4 48x16 0xa 64k 64k 0x 262144k 261 (0x105) 0x000f G 1024x768x8 18x16 0xa 64k 64k 0xe000 262144k 262 (0x106) 0x000b G 1280x1024x4 4 8x16 0xa 64k 64k 0x 262144k 263 (0x107) 0x000f G 1280x1024x8 1 8x16 0xa 64k 64k 0xe000 262144k 270 (0x10e) 0x000f G 320x200x16 18x8 0xa 64k 64k 0xe000 262144k 271 (0x10f) 0x000f G 320x200x32 18x8 0xa 64k 64k 0xe000 262144k 273 (0x111) 0x000f G 640x480x16 18x16 0xa 64k 64k 0xe000 262144k 274 (0x112) 0x000f G 640x480x32 18x16 0xa 64k 64k 0xe000 262144k 276 (0x114) 0x000f G 800x600x16 18x16 0xa 64k 64k 0xe000 262144k 277 (0x115) 0x000f G 800x600x32 18x16 0xa 64k 64k 0xe000 262144k 279 (0x117) 0x000f G 1024x768x16 1 8x16 0xa 64k 64k 0xe000 262144k 280 (0x118) 0x000f G 1024x768x32 1 8x16 0xa 64k 64k 0xe000 262144k 282 (0x11a) 0x000f G 1280x1024x16 1 8x16 0xa 64k 64k 0xe000 262144k 283 (0x11b) 0x000f G 1280x1024x32 1 8x16 0xa 64k 64k 0xe000 262144k 304 (0x130) 0x000f G 320x200x8 1 8x8 0xa 64k 64k 0xe000 262144k 305 (0x131) 0x000f G 320x400x8 1 8x16 0xa 64k 64k 0xe000 262144k 306 (0x132) 0x000f G 320x400x16 18x16 0xa 64k 64k 0xe000 262144k 307 (0x133) 0x000f G 320x400x32 18x16 0xa 64k 64k 0xe000 262144k 308 (0x134) 0x000f G 320x240x8 1 8x8 0xa 64k 64k 0xe000 262144k 309 (0x135) 0x000f G 320x240x16 18x8 0xa 64k 64k 0xe000 262144k 310 (0x136) 0x000f G 320x240x32 18x8 0xa 64k 64k 0xe000 26214
Re: been buggin' me for a while now (console resolution)
--- 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 trying to allude to it via rc.conf or a startup file > > (rc.local?) but it did not work. It seems to me that I needed the > > following in my rc.conf as a pre-requisite: > > > > font8x8="iso-8x8.fnt" > > font8x14="iso-8x14.fnt" > > font8x16="iso-8x16.fnt" > > > > So does anyone know how I can automatically get smaller fonts in my > > console? > 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 and it's a "no go". This is the output of 'vidcontrol -i mode': 0 (0x000) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 1 (0x001) 0x0001 T 40x25 8x8 0xb8000 32k 32k 0x 32k 2 (0x002) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 3 (0x003) 0x0001 T 80x25 8x8 0xb8000 32k 32k 0x 32k 4 (0x004) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 5 (0x005) 0x0003 G 320x200x2 1 8x8 0xb8000 32k 32k 0x 32k 6 (0x006) 0x0003 G 640x200x1 1 8x8 0xb8000 32k 32k 0x 32k 13 (0x00d) 0x0003 G 320x200x4 4 8x8 0xa 64k 64k 0x 256k 14 (0x00e) 0x0003 G 640x200x4 4 8x8 0xa 64k 64k 0x 256k 16 (0x010) 0x0003 G 640x350x2 2 8x14 0xa 64k 64k 0x 128k 18 (0x012) 0x0003 G 640x350x4 4 8x14 0xa 64k 64k 0x 256k 19 (0x013) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 20 (0x014) 0x0001 T 40x25 8x14 0xb8000 32k 32k 0x 32k 21 (0x015) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 22 (0x016) 0x0001 T 80x25 8x14 0xb8000 32k 32k 0x 32k 23 (0x017) 0x0001 T 40x25 8x16 0xb8000 32k 32k 0x 32k 24 (0x018) 0x0001 T 80x25 8x16 0xb8000 32k 32k 0x 32k 26 (0x01a) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 27 (0x01b) 0x0003 G 640x480x4 4 8x16 0xa 64k 64k 0x 256k 28 (0x01c) 0x0003 G 320x200x8 1 8x8 0xa 64k 64k 0x 64k 30 (0x01e) 0x0001 T 80x50 8x8 0xb8000 32k 32k 0x 32k 32 (0x020) 0x0001 T 80x30 8x16 0xb8000 32k 32k 0x 32k 34 (0x022) 0x0001 T 80x60 8x8 0xb8000 32k 32k 0x 32k 37 (0x025) 0x0003 G 320x240x8 4 8x8 0xa 64k 64k 0x 256k 112 (0x070) 0x T 80x43 8x8 0xb8000 32k 32k 0x 32k 113 (0x071) 0x0001 T 80x43 8x8 0xb8000 32k 32k 0x 32k 256 (0x100) 0x000f G 640x400x8 1 8x16 0xa 64k 64k 0xe000 262144k 257 (0x101) 0x000f G 640x480x8 1 8x16 0xa 64k 64k 0xe000 262144k 258 (0x102) 0x000b G 800x600x4 4 8x16 0xa 64k 64k 0x 262144k 259 (0x103) 0x000f G 800x600x8 1 8x16 0xa 64k 64k 0xe000 262144k 260 (0x104) 0x000b G 1024x768x4 48x16 0xa 64k 64k 0x 262144k 261 (0x105) 0x000f G 1024x768x8 18x16 0xa 64k 64k 0xe000 262144k 262 (0x106) 0x000b G 1280x1024x4 4 8x16 0xa 64k 64k 0x 262144k 263 (0x107) 0x000f G 1280x1024x8 1 8x16 0xa 64k 64k 0xe000 262144k 270 (0x10e) 0x000f G 320x200x16 18x8 0xa 64k 64k 0xe000 262144k 271 (0x10f) 0x000f G 320x200x32 18x8 0xa 64k 64k 0xe000 262144k 273 (0x111) 0x000f G 640x480x16 18x16 0xa 64k 64k 0xe000 262144k 274 (0x112) 0x000f G 640x480x32 18x16 0xa 64k 64k 0xe000 262144k 276 (0x114) 0x000f G 800x600x16 18x16 0xa 64k 64k 0xe000 262144k 277 (0x115) 0x000f G 800x600x32 18x16 0xa 64k 64k 0xe000 262144k 279 (0x117) 0x000f G 1024x768x16 1 8x16 0xa 64k 64k 0xe000 262144k 280 (0x118) 0x000f G 1024x768x32 1 8x16 0xa 64k 64k 0xe000 262144k 282 (0x11a) 0x000f G 1280x1024x16 1 8x16 0xa 64k 64k 0xe000 262144k 283 (0x11b) 0x000f G 1280x1024x32 1 8x16 0xa 64k 64k 0xe000 262144k 304 (0x130) 0x000f G 320x200x8 1 8x8 0xa 64k 64k 0xe000 262144k 305 (0x131) 0x000f G 320x400x8 1 8x16 0xa 64k 64k 0xe000 262144k 306 (0x132) 0x000f G 320x400x16 18x16 0xa 64k 64k 0xe000 262144k 307 (0x133) 0x000f G 320x400x32 18x16 0xa 64k 64k 0xe000 262144k 308 (0x134) 0x000f G 320x240x8 1 8x8 0xa 64k 64k 0xe000 262144k 309 (0x135) 0x000f G 320x240x16 18x8 0xa 64k 64k 0xe000 262144k 310 (0x136) 0x000f G 320x240x32 18x8 0xa 64k 64k 0xe000 262144k 317 (0x13d) 0x
Re: been buggin' me for a while now (console resolution)
--- 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 "just" a server. > > cat /etc/rc.conf > #Terminal settings > keymap="us.dvorak" > font8x14="iso-8x14" > font8x16="iso-8x16" > font8x8="iso-8x8" > allscreens_flags="80x30" How do I load the VESA driver? A basic google indicates this is somewhat experimental. Is this true? I remember the command I used in the past to manually change to smaller fonts: $ vidcontrol 80x50 In the absence of anything better (VESA?), how can I automate this upon boot time? I remember using "allscreens_flags=80x50" but it didn't work. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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?) but it did not work. It seems to me that I needed the following in my rc.conf as a pre-requisite: font8x8="iso-8x8.fnt" font8x14="iso-8x14.fnt" font8x16="iso-8x16.fnt" So does anyone know how I can automatically get smaller fonts in my console? Thanks, Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi Peter, You need to recompile your kernel with below options VESA You need to include these in your rc.conf allscreens_flags="132x25" This is what i did for my FreeBSD box. Regards, Stubborn http://www.detest.org http://www.coldlostsick.net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: been buggin' me for a while now (console resolution)
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="us.dvorak" font8x14="iso-8x14" font8x16="iso-8x16" font8x8="iso-8x8" allscreens_flags="80x30" -- -- Perfection is just a word I use occasionally with mustard. --Atom Powers-- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
been buggin' me for a while now (console resolution)
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 work. It seems to me that I needed the following in my rc.conf as a pre-requisite: font8x8="iso-8x8.fnt" font8x14="iso-8x14.fnt" font8x16="iso-8x16.fnt" So does anyone know how I can automatically get smaller fonts in my console? Thanks, Peter __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: applying the vesa patch to stable for high console resolution
Hi, Sorry but I don't know. You should ask the freebsd-current list. Regards Didier -Original Message- From: Remington L [mailto:[EMAIL PROTECTED] Sent: Thursday, June 16, 2005 21:06 To: Didier Wiroth; freebsd-stable@freebsd.org; freebsd-questions@freebsd.org Subject: [SPAM-PAL] 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 of 1200x800 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: applying the vesa patch to stable for high console resolution
Hi, I actually don't know. As far as I've read (current-list) the patch comes from dragonflybsd which is a continuation of the 4.x kernel, perhaps it already might work. You might try the syscon* patches on a freebsd4.x test box and see if it works. Didier -Original Message- 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 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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 of 1200x800 On 6/16/05, Igor Pokrovsky <[EMAIL PROTECTED]> wrote: > > 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. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > [EMAIL PROTECTED]" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: applying the vesa patch to stable for high console resolution
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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: applying the vesa patch to stable for high console resolution
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-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: applying the vesa patch to stable for high console resolution
Hi, Has this patch beeen applied to CURRENT? So it will be in the next release of FreeBSD? Ted >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] Behalf Of Didier Wiroth >Sent: Monday, June 13, 2005 1:46 PM >To: freebsd-stable@freebsd.org >Cc: 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 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 freebsd current but it works (for >me) with 5-stable and may be "release" or earlier versions (5.X) too. > >ONCE AGAIN BE WARNED!! USE AT YOUR OWN RISK!!! > >Let's go: >1) Get the patch here: >http://people.freebsd.org/~delphij/vesa/patchset-highres.20050522 > >2) Remove the lines which are not required for us and rename >the patch we will use to syscons.patch: >split -p "Index: usr.sbin" patchset-highres.20050522 && mv xaa >syscons.patch > >3) backup and patch your local (stable) sources: >(/usr/src/sys/dev/syscons - will be patched) >cp -Rp /usr/src/sys/dev/syscons /usr/src/sys/dev/BAK.syscons >cd /usr/src >patch < path_to_patch/syscons.patch > >4) recompile and install your kernel with sc_pixel_mode and >vesa support see handbook for details! >http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernel config.html 5) backup your vidcontrol sources cp -Rp /usr/src/usr.sbin/vidcontrol /usr/src/usr.sbin/BAK.vidcontrol 6) update your vidcontrol sources with the "current/HEAD" vidcontrol sources cd /usr/src cvs [EMAIL PROTECTED]:/home/ncvs co -rHEAD usr.sbin/vidcontrol 7) recompile vidcontrol and install cd /usr/src/usr.sbin/vidcontrol && make clean && make all && make install 8) reboot 9) after having rebooted with your new kernel (with sc_pixel_mode and vesa) issue a "vidcontrol -i mode" You will get lots of ouput like this: 322 (0x142) 0x000f G 1400x1050x16 1 8x16 0xa 64k 64k 0x9800 65472k Test the mode in a shell by issuying: vidcontrol MODE_322 If it works (I hope for you ;-)) but your corresponding mode in rc.conf like this: allscreens_flags="MODE_322" Voilà :-)) Long live freebsd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
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 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 freebsd current but it works (for me) with 5-stable and may be "release" or earlier versions (5.X) too. ONCE AGAIN BE WARNED!! USE AT YOUR OWN RISK!!! Let's go: 1) Get the patch here: http://people.freebsd.org/~delphij/vesa/patchset-highres.20050522 2) Remove the lines which are not required for us and rename the patch we will use to syscons.patch: split -p "Index: usr.sbin" patchset-highres.20050522 && mv xaa syscons.patch 3) backup and patch your local (stable) sources: (/usr/src/sys/dev/syscons - will be patched) cp -Rp /usr/src/sys/dev/syscons /usr/src/sys/dev/BAK.syscons cd /usr/src patch < path_to_patch/syscons.patch 4) recompile and install your kernel with sc_pixel_mode and vesa support see handbook for details! http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html 5) backup your vidcontrol sources cp -Rp /usr/src/usr.sbin/vidcontrol /usr/src/usr.sbin/BAK.vidcontrol 6) update your vidcontrol sources with the "current/HEAD" vidcontrol sources cd /usr/src cvs [EMAIL PROTECTED]:/home/ncvs co -rHEAD usr.sbin/vidcontrol 7) recompile vidcontrol and install cd /usr/src/usr.sbin/vidcontrol && make clean && make all && make install 8) reboot 9) after having rebooted with your new kernel (with sc_pixel_mode and vesa) issue a "vidcontrol -i mode" You will get lots of ouput like this: 322 (0x142) 0x000f G 1400x1050x16 1 8x16 0xa 64k 64k 0x9800 65472k Test the mode in a shell by issuying: vidcontrol MODE_322 If it works (I hope for you ;-)) but your corresponding mode in rc.conf like this: allscreens_flags="MODE_322" Voilà :-)) Long live freebsd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
External Monitor console resolution black screen after exiting KDE
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'm connected to my KVM with an external monitor, I can boot the machine up and use the console just fine. When I go to launch KDE, the external monitor works fine. Once I exit from KDE, it appears that the operating system does not reset the terminal properly and the monitor just shows a black screen as if the video mode is not supported. >From that point, I can blindly type "startx" and get back into KDE and the monitor will work properly, but I cannot get it to reset the console properly. If I toggle the video back to the laptop screen, I see vertical lines on the screen. The only way I can get it to clear is by shutting off the machine and rebooting. I recompiled my kernel with and without VESA, tried using video modes that I know work in the console but nothing will reset it back after exiting KDE. Any insight would be great. Thanks, -Troy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: console resolution on a T41
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 configuration file: > options VESA > options SC_PIXEL_MODE > However when I run > vidcontrol -g 100x37 VESA_800x600 > I still get that the mode is not supported by the device. > Is there something that I am missing here? Has anyone tried to increase > console resolution on a T41 Thinkpad or even an ATI mobility radeon laptop? Unfortunately syscons uses 800x600 with 16 colors (4 bit, mode 258) and all ATI cards I know don't support that mode, only 800x600x8 (256 colors, mode 259). You can check your card features with 'vidcontrol -i mode'. I'm no programmer, otherwise I had patched syscons to use mode 0x103 (259) instead of 0x102. Perhaps you are lucky and find somebody who corrects this. ALso, search the archives, some months ago some good guys made syscons use higher resolutions, perhaps they also implemented more sensful mode selection. -Harry > > D. > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" pgpCGMX7kRvcx.pgp Description: PGP signature
console resolution on a T41
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 100x37 VESA_800x600 I still get that the mode is not supported by the device. Is there something that I am missing here? Has anyone tried to increase console resolution on a T41 Thinkpad or even an ATI mobility radeon laptop? D. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Console resolution
> > 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 important, I > > use Xwindows only if I must... > try "man 1 vidcontrol" 1. Don't forget to "kldload vesa" for some higher resolutions. 2. Try /usr/sbin/vidfont. -- Cordula's Web. http://www.cordula.ws/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Console resolution
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/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Console resolution
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 > possible on freebsd. I use text mode a lot, so this is quite important, I > use Xwindows only if I must... You can try playing with the various /etc/rc.conf settings to tweak console display. I have this in mine: keymap="uk.cp850" keyrate="fast" font8x8="swiss-8x8" allscreens_flags="80x50" This is ok for me here in the UK - you might have to play around with different fonts if you use a different keymap. The screen flags setting just changes the display to 80x50 instead of the default 80x25. Note you can test those settings out from the console using kbdcontrol. -- Jez Hancock - System Administrator / PHP Developer http://munk.nu/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Console resolution
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 both didn't work as they > should (I had both installed on same computer)) and remove everything else > from it. > 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 important, I > use Xwindows only if I must... > > Take care. > Andy > > > ** > * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * > * [EMAIL PROTECTED] * Sentinel, BH 90210, True's Trooper, * > *[EMAIL PROTECTED] * Heller's Angel, Questie, Legacy, PO5, * > * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender* > * ICQ-UIC: 4911125 * > * PGP key available *http://www.atechnet.dhs.org/~andy/ * > ** > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Console resolution
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 from it. 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 important, I use Xwindows only if I must... Take care. Andy ** * Aleksander Rozman - Andy * Fandoms: E2:EA, SAABer, Trekkie, Earthie * * [EMAIL PROTECTED] * Sentinel, BH 90210, True's Trooper, * *[EMAIL PROTECTED] * Heller's Angel, Questie, Legacy, PO5, * * Maribor, Slovenia (Europe) * Profiler, Buffy (Slayerete), Pretender* * ICQ-UIC: 4911125 * * PGP key available *http://www.atechnet.dhs.org/~andy/ * ** ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd console resolution vs linux console resolution
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 lot Didier To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
