Re: Changing Console Resolution - Vidcontrol
Stefan Lambrev wrote: All those things work only under i386 right ? There is no option VESA in amd64 ? Right. Calling function in the VESA BIOS (which is 32bit i386 code) is not supported under FreeBSD/amd64. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd What is this talk of 'release'? We do not make software 'releases'. Our software 'escapes', leaving a bloody trail of designers and quality assurance people in its wake. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Oops, I was mistaken. 800x600x4 (MODE_258) is what I'm using. 800x600x8 returns Operation not supported when trying to switch to it, as do both 4 and 8 bit 1024x768 modes. 16-bit and 32-bit modes work at the higher resolution but they're slow as molasses so I don't use them(1). No Matter what I try, I get cannot open raster device, inapropriate ioctl for this device. I have made sure that I have VESA loaded, etc. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Sat, Apr 07, 2007 at 03:31:40PM +, John Walthall wrote: No Matter what I try, I get cannot open raster device, inapropriate ioctl for this device. I have made sure that I have VESA loaded, etc. This sounds like your kernel is not compiled with options SC_PIXEL_MODE. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Friday 06 April 2007 02:43, Kevin Oberman wrote: I always run a 2000 line scrollback buffer. 200 won't make it to the start of my boot. And, it's SC_HISTORY_SIZE. I'm unclear as to what you refer to as 'slideshow like teleporting', though. in case someone want colourful console options SC_HISTORY_SIZE=1000 options SC_NORM_ATTR=(FG_LIGHTGREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_BLACK) options SC_KERNEL_CONS_ATTR=(FG_LIGHTBLUE|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_LIGHTRED|BG_BLACK) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Hi list, All those things work only under i386 right ? There is no option VESA in amd64 ? Andrei Kolu wrote: On Friday 06 April 2007 02:43, Kevin Oberman wrote: I always run a 2000 line scrollback buffer. 200 won't make it to the start of my boot. And, it's SC_HISTORY_SIZE. I'm unclear as to what you refer to as 'slideshow like teleporting', though. in case someone want colourful console options SC_HISTORY_SIZE=1000 options SC_NORM_ATTR=(FG_LIGHTGREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_BLACK) options SC_KERNEL_CONS_ATTR=(FG_LIGHTBLUE|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_LIGHTRED|BG_BLACK) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- Best Wishes, Stefan Lambrev ICQ# 24134177 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Date: Fri, 06 Apr 2007 15:13:33 +0300 From: Stefan Lambrev [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] Hi list, All those things work only under i386 right ? There is no option VESA in amd64 ? Andrei Kolu wrote: On Friday 06 April 2007 02:43, Kevin Oberman wrote: I always run a 2000 line scrollback buffer. 200 won't make it to the start of my boot. And, it's SC_HISTORY_SIZE. I'm unclear as to what you refer to as 'slideshow like teleporting', though. in case someone want colourful console options SC_HISTORY_SIZE=1000 options SC_NORM_ATTR=(FG_LIGHTGREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_BLACK) options SC_KERNEL_CONS_ATTR=(FG_LIGHTBLUE|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_LIGHTRED|BG_BLACK) Please don't top post! I don't think you need VESA for any of these...certainly not the SC_HISTORY_SIZE. You do need it for SC_PIXEL_MODE to get more modes on systems that lack that capability (like my T43 laptop). If you can set it to a mode that makes you happy, those commands should work, but some systems offer very few modes without VESA. The T43 offers four...all 80 characters wide from 25 to 60 lines. :-( -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpPMLSLFdx1M.pgp Description: PGP signature
Re: Changing Console Resolution - Vidcontrol
On Thu, Apr 05, 2007 at 04:27:46PM +0200, Oliver Fromme wrote: I think 800x600x4 would be even quicker, because no VESA calls are required at all for screen output. Oops, I was mistaken. 800x600x4 (MODE_258) is what I'm using. 800x600x8 returns Operation not supported when trying to switch to it, as do both 4 and 8 bit 1024x768 modes. 16-bit and 32-bit modes work at the higher resolution but they're slow as molasses so I don't use them(1). I'd rather use 4-bit anyway as IMO there's very few reasons to have more than 16 colors in console mode. elinks is the only program I know of that claims to be able to use more and syscons may not even support the control codes it's using. (All x4 modes use a planar layout. If such a bitplane is larger than 64K, so-called bank switching is required to access all of the video memory, because the VGA address space allows only a 64K window for access at once. VESA calls are required to perform the bank switching. As yes, I'm having flashbacks to the good ol' days right now :) I mostly stuck to tweaking the VGA registers at the lower resolution modes as VESA support was pretty spotty on most hardware at the time. I do remember using bank switching on occasion though. I think FreeBSD's syscons supports it via flags 0x80 for the sc device in the kernel config file. See the section Driver Flags in the sc(4) manual page. Thanks for the tip, but this doesn't work for me. Setting that flag in device.hints results in a blank screen and only a single virtual terminal (ALT+F? just beep). I _am_ able to log in blind and issue commands however. Checking dmesg over ssh didn't show any errors or clues. In any case, allscreens_flags works acceptably for my needs. Strange that it works but the 0x80 flag doesn't. (1) Interesting data point, syscons apparently doesn't use VESA very efficiently. 1024x768x16 mode is very slow -- I can see the screen redrawing line by line in something like top. However, I'm currently using the VESA driver for X at the moment as the trident driver has some problems with the chip in this laptop. 1024x768x16 mode using VESA is fast in X, almost as fast as the accelerated driver. So I know the hardware is capable of it. Unfortunately X has some other issues on this machine, like a weird kkeybooardd ssstutteringg problem when Xkb is enabled, so I tend to use the console a lot. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
JoaoBR [EMAIL PROTECTED] wrote: On Wednesday 04 April 2007 00:05, you wrote: Console is not intended for everyday use! You should login to your FreeBSD box with ssh-client of your choise and from the OS of your choise (preferably from graphic mode). please stay on topic the question is not what one should or not but to hook into your talk, if there is a console it can be used as wanted He is perfectly on topic. Normally you shouldn't have to use syscons at all. On desktop machines, you install X and run it at your favourite resolution. Server machines usually run headless anyway, and you connect to them via ssh or via a serial terminal server. Having to go to a server and work at the syscons console would be an exception (e.g. in case of emergency, when you're not even able to get the box up in single-user mode on the serial console). Of course there are exceptions to those rules. But that's what they are: exceptions. If you need to work on a server regularly at its physical display, it's probably a good idea to install X, as if it was a desktop machine. In fact, if you do work there regularly, then it acts partially as a desktop machine or workstation, so it deserves to run X. If installed and configured properly, the overhead of starting and running the X server is low. Having said that, FreeBSD's syscons _does_ support higher resolutions if you really want to have them (see the pixel mode support and the VESA options in the vindcontrol(8) manpage). If that's still not enough, well, then you have to write code yourself and submit it. The fact that nobody has done that so far indicates that not too many people are in need for more than what's already there. 1024x768 is more than enough for 120x50 virtual terminals. may be for you, for me and lot of other users it is definitly not How did you get the number of lot of other users? From the discussion so far it rather seems to be a small minority. p.s. Or you just trolling? RH is rather professional, but definitely not because of graphics in console... :-\ don't try to be smart with me Admittedly your style of writing looks a lot like trolling. (But I assume anyway that you're not intentionally trolling, otherwise I wouldn't reply at all and instead add you to my killfile.) nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer I rather agree with Peter Jeremy here. FreeBSD's boot looks more professional than a colorful but less informative graphical boot like the one on RH or SuSE (or even Windows). Of course, that matters only if you're a professional yourself. If you're not, then I certainly believe that you prefer the graphical boot. FWIW, most of the time machines boot without _anyone_ watching anyway. If you need to see the boot messages, you ssh into the box and type dmesg -a or look at the file /var/run/dmesg.boot (and /var/log/console.log which can be enabled via /etc/syslog.conf). Best regards Oliver PS: Please respect the Reply-To header. I do read the list and do not want to get additional copies of mails. -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd (On the statement print 42 monkeys + 1 snake:) By the way, both perl and Python get this wrong. Perl gives 43 and Python gives 42 monkeys1 snake, when the answer is clearly 41 monkeys and 1 fat snake.-- Jim Fulton ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Thu, Apr 05, 2007 at 09:25:46AM +0200, Oliver Fromme wrote: FWIW, most of the time machines boot without _anyone_ watching anyway. If you need to see the boot messages, you ssh into the box and type dmesg -a or look at the file /var/run/dmesg.boot (and /var/log/console.log which can be enabled via /etc/syslog.conf). Yes, and usually if I'm standing in front of a server watching it boot it's because there's something wrong, so I _WANT_ to see the boot messages in order to diagnose it :) bootsplash is kind of fun for desktops, but not really necessary and it wastes kernel memory that you never get back. That being said, I can see a place for SC_PIXEL_MODE, especially on laptops that don't stretch to native resolution so your console ends up being a tiny box in the middle of the screen. I only wish 1024x768x4 worked right as (on most cheap video hardware anyway) pushing all the data for 16-bit modes though VESA is quite slow. As it's mostly an IO bandwidth issue, the planar modes should be faster. I can get 800x600x8 working and it's definitely quicker than 800x600x16. Craig ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Craig Boston wrote: [...] I only wish 1024x768x4 worked right as (on most cheap video hardware anyway) pushing all the data for 16-bit modes though VESA is quite slow. As it's mostly an IO bandwidth issue, the planar modes should be faster. I can get 800x600x8 working and it's definitely quicker than 800x600x16. I think 800x600x4 would be even quicker, because no VESA calls are required at all for screen output. (All x4 modes use a planar layout. If such a bitplane is larger than 64K, so-called bank switching is required to access all of the video memory, because the VGA address space allows only a 64K window for access at once. VESA calls are required to perform the bank switching. For a resolution of 800x600, a bitplane is 60K, so no bank switching is required, and the whole video memory can be accessed directly.) I think FreeBSD's syscons supports it via flags 0x80 for the sc device in the kernel config file. See the section Driver Flags in the sc(4) manual page. Best regards Oliver PS: It should be noted that all of that VESA stuff only works for FreeBSD/i386. FreeBSD/amd64 isn't capable of performing calls into the 32bit VESA BIOS. -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd A language that doesn't have everything is actually easier to program in than some that do. -- Dennis M. Ritchie ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Date: Thu, 5 Apr 2007 12:57:09 +0200 From: Michael Schuh [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] 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=YES and in /etc/rc.conf something like this: keymap=german.iso font8x16=iso15-8x16 font8x14=iso15-8x14 font8x8=iso15-8x8 allscreens_flag=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: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp9NjEJHB9IE.pgp Description: PGP signature
Re: Changing Console Resolution - Vidcontrol
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 would 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 [EMAIL PROTECTED]: Date: Thu, 5 Apr 2007 12:57:09 +0200 From: Michael Schuh [EMAIL PROTECTED] Sender: [EMAIL PROTECTED] 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=YES and in /etc/rc.conf something like this: keymap=german.iso font8x16=iso15-8x16 font8x14=iso15-8x14 font8x8=iso15-8x8 allscreens_flag=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: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 -- === michael-schuh.net === Michael Schuh Preußenstr. 13 66111 Saarbrücken phone: 0681/8319664 mobil: 0177/9738644 @: [EMAIL PROTECTED] === Ust-ID: DE251072318 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
Date: Fri, 6 Apr 2007 00:31:45 +0200 From: Michael Schuh [EMAIL PROTECTED] 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. Are you sure? On my T43, I lose exactly 23 lines at the point my screen switches from it's default mode. Note that I need to use VESA and SC_PIXEL_MODE on this system. That may relate to the problem. 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) I always run a 2000 line scrollback buffer. 200 won't make it to the start of my boot. And, it's SC_HISTORY_SIZE. I'm unclear as to what you refer to as 'slideshow like teleporting', though. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgprMuq6pnNa5.pgp Description: PGP signature
Re: Changing Console Resolution - Vidcontrol
Hi Kevin, yes you are right my systems also loses lines, i believe that the mechanics in vidcontrol or in the kernels syscons device are the sources of this behaviour ...because through the init ( blanks screen and set mode ).. About the buffer at this time I am not really sure, but in the kernel's NOTES files it is setted per default to 200. I think you are right with the scrollback buffer that was the thing that i mean. you could have a slideshow or teleporting effect on some slow graphic cards, or on cards that not fully supports vesa while you scrolling through the screens, because if you use the vesa driver the output could be slower while having more overhead.. ...read also the postings in the stable-list ( I think from oliver fromme).. hmmm, if this behavior (losing lines) could not turned out by options or configuring the mode directly after loading the vesa module, I think it is a bug and we should enter it to the GNATS bugtracker but first we call help in the list :-) Could anyone, that is deeper in the woods, shed us some light on this behavior and eventually a possible solution? cheers michael -- === michael-schuh.net === Michael Schuh Preußenstr. 13 66111 Saarbrücken phone: 0681/8319664 mobil: 0177/9738644 @: [EMAIL PROTECTED] === Ust-ID: DE251072318 === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On 2007-Apr-03 14:27:00 -0300, JoaoBR [EMAIL PROTECTED] wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM I don't understand why displaying a silly graphic whilst hiding the boot messages is professional. If you really need eye-candy to make your FreeBSD box look like it's running MS Windows, see splash(4) -- Peter Jeremy pgpdDT36PjJg7.pgp Description: PGP signature
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 00:05, you wrote: Console is not intended for everyday use! You should login to your FreeBSD box with ssh-client of your choise and from the OS of your choise (preferably from graphic mode). please stay on topic the question is not what one should or not but to hook into your talk, if there is a console it can be used as wanted 1024x768 is more than enough for 120x50 virtual terminals. may be for you, for me and lot of other users it is definitly not p.s. Or you just trolling? RH is rather professional, but definitely not because of graphics in console... :-\ don't try to be smart with me nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer that is very easy to understand, look: A/ fits much more info on one screen B/ line wraps do not complicate orientation on screen both points are very usefull debugging any kind of problem or tailing logs -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 04:49, Peter Jeremy wrote: On 2007-Apr-03 14:27:00 -0300, JoaoBR [EMAIL PROTECTED] wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM I don't understand why displaying a silly graphic whilst hiding the boot messages is professional. If you really need eye-candy to make your FreeBSD box look like it's running MS Windows, see splash(4) uuuhf man, my example of RH's graphical boot is *not* about a picture and this wasn't at all a comparism to any graphics in picture form, you should pay more attention to the whole thread instead of junking in here this thread is about displaying *text console* in 1024x768 and so I compared RH 8x8 boot text to fbsd's 16x16 mode and it is not about professional looking even if it was one of the points as example, it is extremely useful to get more information on one screen and still more usefull not having linewraps and I do not even get why this is beeing fight because it is natural having bigger screens and smaller letter to see more at once, unless you have disabilities and need the big letters but that is another point of view -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Wednesday 04 April 2007 19:35, [EMAIL PROTECTED] wrote: On 04/04/07, JoaoBR [EMAIL PROTECTED] wrote: don't try to be smart with me nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer Don't try to play dumb with us. You implied that it was when you wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM yeahh but did you read it really, all??? I guess not, at least it seems you didn't understood the sense, only a word and another and glued it together as you wanted in order to make some noise And both premises are patent nonsense, since they are both predicated on some bollocks notion of professionalism which likely started with the first school to sell MBAs via post. talk to the hand :) -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On 04/04/07, JoaoBR [EMAIL PROTECTED] wrote: On Wednesday 04 April 2007 00:05, you wrote: Console is not intended for everyday use! You should login to your FreeBSD box with ssh-client of your choise and from the OS of your choise (preferably from graphic mode). please stay on topic the question is not what one should or not but to hook into your talk, if there is a console it can be used as wanted Ther are always going to be limitations. If you are not writing the code you are not going to have very much control over those limitations. 1024x768 is more than enough for 120x50 virtual terminals. may be for you, for me and lot of other users it is definitly not Well, perhaps you have something wrong if you cannot run 120x50 at 1024x768? p.s. Or you just trolling? RH is rather professional, but definitely not because of graphics in console... :-\ don't try to be smart with me nobody said that RH is professional because of it's graphics in console I said that for example RH looks professional with the graphic boot they offer Don't try to play dumb with us. You implied that it was when you wrote: simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM And both premises are patent nonsense, since they are both predicated on some bollocks notion of professionalism which likely started with the first school to sell MBAs via post. -- -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 05:45 pm, Daniel O'Connor wrote: On Tuesday 03 April 2007 06:24, Freddie Cash wrote: 1024x768 is a pretty standard VESA mode used on a lot of people's text consoles. :) On most videocards, MODE_279 will be 1024x768 w/16 bpp colour. Check the output of vidcontrol -i. You'll see a lot of different modes, some text, some raster/bitmap/VESA/whatever-you-call-it. This has nothing to do with X or any GUI. I don't understand why people who want high resolution consoles don't run X. Why should we run X on a server just to get a larger text console? Or on a laptop that we don't always want to wait for X to load? Sometimes, it's nice to be able to use the entire screen without having to load up a lot of unneeded software, like the entire X stack. 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. Not in my experience on a Toshiba laptop using a Radeon 7000 chipset. In VMWare, scrolling a 1024x768 screen during a port compile is chunky. But doing so on my laptop I see no difference between the text console and a tab in Konsole. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 12:18, Freddie Cash wrote: I don't understand why people who want high resolution consoles don't run X. that is very easy to understand, look: A/ fits much more info on one screen B/ line wraps do not complicate orientation on screen both points are very usefull debugging any kind of problem or tailing logs also, there are people out who say FreeBSD is very perfect for remotecontrol, the letters are so big you can see them from far away :) simply consider RH graphical boot in 1024x768 has a very professional look while Freebsd still looks like Gate's MsDos before selling it to IBM -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 10:27 am, JoaoBR wrote: On Tuesday 03 April 2007 12:18, Freddie Cash wrote: Just a note that the above should read: On Monday 02 April 2007 05:45 pm, Daniel O'Connor wrote: As I am not the one who wrote the following line, but Daniel is. :) I don't understand why people who want high resolution consoles don't run X. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 15:02, Freddie Cash wrote: On Tuesday 03 April 2007 10:27 am, JoaoBR wrote: On Tuesday 03 April 2007 12:18, Freddie Cash wrote: Just a note that the above should read: On Monday 02 April 2007 05:45 pm, Daniel O'Connor wrote: As I am not the one who wrote the following line, but Daniel is. :) sorry, no bad intention I might have highlighted the right quote in th ewrong msg before hitten the reply button I don't understand why people who want high resolution consoles don't run X. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 01:55:45 pm Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? Without recompiling your kernel, you should be able to do modes like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x60 If you add options VGA_WIDTH90 to your kernel you can do things like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x60 (note that not all hardware likes the 90-column modes) And if you add options VESA and options SC_PIXEL_MODE to your kernel you can use any fontsize (of the three: 8x16, 8x14, 8x8) with any VESA video mode supported by your hardware. You get a list of modes by running vidcontrol -i mode from a virtual terminal. On my machine mode 279 is 1024x768x16. If I wanted to use that with an 8x14 font I'd do this: # vidcontrol -f 8x14 cp437-8x14.fnt MODE_279 JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Mon, 2 Apr 2007, Schiz0 wrote: Hey, I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? You're question does not quite make sense. Console is more or less the FreeBSD word for boss text-mode terminal. It has nothing to do with what a terminal window might look like in a GUI such as Windows or X. The first question is what *text* modes does your hardware support. I don't know of video hardware that supports 1024x768 raster text. If your hardware supports it and you want the VESA modes, you can compile VESA support into the kernel (which you should do if you use it just about all the time) or it can be load dynamically (see man 4 vga). Ditto for 90 column VGA. Most of the console modes are regular vga text modes and they are usually expressed in terms of lines(high) x columns(wide), for example the standard 25x80. I suspect you do not really want a console resolution of 1024x768 (px). I suspect you want 1024x758 in a GUI, in which case you need to be researching X as vidcontrol has nothing to do with that. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Monday 02 April 2007 12:07 pm, Lars Eighner wrote: On Mon, 2 Apr 2007, Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? You're question does not quite make sense. Console is more or less the FreeBSD word for boss text-mode terminal. It has nothing to do with what a terminal window might look like in a GUI such as Windows or X. The first question is what *text* modes does your hardware support. I don't know of video hardware that supports 1024x768 raster text. If your hardware supports it and you want the VESA modes, you can compile VESA support into the kernel (which you should do if you use it just about all the time) or it can be load dynamically (see man 4 vga). Ditto for 90 column VGA. Most of the console modes are regular vga text modes and they are usually expressed in terms of lines(high) x columns(wide), for example the standard 25x80. I suspect you do not really want a console resolution of 1024x768 (px). I suspect you want 1024x758 in a GUI, in which case you need to be researching X as vidcontrol has nothing to do with that. 1024x768 is a pretty standard VESA mode used on a lot of people's text consoles. :) On most videocards, MODE_279 will be 1024x768 w/16 bpp colour. Check the output of vidcontrol -i. You'll see a lot of different modes, some text, some raster/bitmap/VESA/whatever-you-call-it. This has nothing to do with X or any GUI. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Changing Console Resolution - Vidcontrol
On Tuesday 03 April 2007 06:24, Freddie Cash wrote: 1024x768 is a pretty standard VESA mode used on a lot of people's text consoles. :) On most videocards, MODE_279 will be 1024x768 w/16 bpp colour. Check the output of vidcontrol -i. You'll see a lot of different modes, some text, some raster/bitmap/VESA/whatever-you-call-it. This has nothing to do with X or any GUI. 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. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpSNL3vYdRSw.pgp Description: PGP signature
Re: Changing Console Resolution - Vidcontrol
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]
Re: Changing Console Resolution - Vidcontrol
That cleared it up. I needed to enable some stuff in my kernel, which was why vidcontrol wasn't working. I thought it was an error on my behalf. Thanks. On 4/2/07, John Nielsen [EMAIL PROTECTED] wrote: On Monday 02 April 2007 01:55:45 pm Schiz0 wrote: I'm wondering how you can increase the resolution of the console in FreeBSD stable. I have read the man page on vidcontrol and googled around a bit, but I'm still confused about what to do. I'm currently running FreeBSD in VMWare on a windows machine (But that'll change as soon as I learn enough to put it up my server, which currently runs linux). I'd like to have something like 1024x768 resolution or so. Also, the man pages mention something about VESA modules. What exactly is this, and do I need it? My kernel is currently compiled without support for it. Would I need to recompile my kernel again? Without recompiling your kernel, you should be able to do modes like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_80x60 If you add options VGA_WIDTH90 to your kernel you can do things like: # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x50 # vidcontrol -f 8x8 cp437-8x8.fnt VGA_90x60 (note that not all hardware likes the 90-column modes) And if you add options VESA and options SC_PIXEL_MODE to your kernel you can use any fontsize (of the three: 8x16, 8x14, 8x8) with any VESA video mode supported by your hardware. You get a list of modes by running vidcontrol -i mode from a virtual terminal. On my machine mode 279 is 1024x768x16. If I wanted to use that with an 8x14 font I'd do this: # vidcontrol -f 8x14 cp437-8x14.fnt MODE_279 JN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
