|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
||||
Console Resolution Problem
According to several nice articles, including this one, and an article in the FreeBSD wiki, the first step to getting a high console resolution is to add these to lines to the kernel configuration file:
Code:
options VESA options SC_PIXEL_MODE Code:
-------------------------------------------------------------- >>> Kernel build for BEDFORD started on Fri Jun 27 17:35:42 UTC 2008 -------------------------------------------------------------- ===> BEDFORD mkdir -p /usr/obj/usr/src/sys -------------------------------------------------------------- >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /usr/src/sys/amd64/conf; PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /usr/obj/usr/src/sys/BEDFORD /usr/src/sys/amd64/conf/BEDFORD /usr/src/sys/amd64/conf/BEDFORD: unknown option "VESA" *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I have tried it recently on 7.0-RELEASE and 8.0-CURRENT-200806 with this exact error. In both cases I had the src/base and src/sys distributions installed. Do I need more src distributions than those two to be able to get VESA working? Thanks |
|
|||
maybe if you use i386 rather than amd64 the
kernel would compile. ............ that is my vague recollection anyway. Some have said the only reason to use amd64 rather than i386 is server-intensive data processing. (another vague recollection)
__________________
FreeBSD 13-STABLE |
|
||||
VESA is not supported on AMD64 because of some BIOS communication that the 64-Bit version can't do. I ran into this issue yesterday, when I tried to compile with the VESA option. The other option should work, but it's rather useless given that you can't use VESA modes. I was able to confirm this by looking at previous mailing list entries. It was hidden deep within one of the threads. I'm not sure if there is another way of changing console resolution, but at the moment, I'm stuck with only one mode as well.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
||||
I do remember that this stopped working for me, in 32 bit no less, quite awhle ago. I don't believe I got compile errors, but what had worked simply no longer worked. It reminded me of a Windows haiku.
Yesterday it worked Today it is not working Windows is like that. But I digress. Back on topic, that hasn't worked for me in probably over a year. As I usually wind up in X anyway, running several mlterms, (my x terminal of choice in FreeBSD) I never investigated it that thoroughly. |
|
||||
I just need xterm + screen + zsh. I'll have three or four xterm + screen sessions going in xfce, if I need them. I rarely drop into console, unless I have to. My .zshrc even autostarts Xfce upon console login, if it hasn't already been started.
__________________
"UNIX is basically a simple operating system, but you have to be a genius to understand the simplicity." MacBook Pro (Darwin 9), iMac (Darwin 9), iPod Touch (Darwin 9), Dell Optiplex GX620 (FreeBSD 7.1-STABLE) |
|
|||
Quote:
Just for other folks, option VESA is working perfectly on i386. SC_PIXEL_MODE may still be usefull also look VESA800x600 in syscons(4) Anyway, all this console stuff are going to be rewritten some time in future.(they are not MPSAFE) |
|
|||
High resolution consoles are overrated, (coming from a OpenBSD user..)
|
|
||||
Yeah, there is not really much use for it except for the times when I am confined to a console and I need to read a message that is longer than can be displayed on my screen at one time.
In this case, of course, I can just log the output of the command into a file and then open it in an editor, but that can be an awful lot to do for some simple console read-outs sometimes. He he. How very lazy. |
|
|||
I just think it looks nice
|
|
|||
Quote:
i.e: % dmesg | less Now you know.. |
|
|||
Quote:
It's also not supported by OpenBSD either.. |
|
|||
It's bad to develop tendencies that are OS specific, the recommendation of more or less is a "generic" answer.
I'll go now.. |
|
||||
Note: more *is* less on FreeBSD. They are hardlinks to the same binary. The only difference is that more has -X enabled while less doesn't (and a few other niggles, but that's the main one).
This trips me up all the time switching between FreeBSD and Linux, as more on Debian is the ancient, craptastic, real more that does very very very little. And using "less -X" all the time is a pain. And aliasing more to 'less -X' causes more problems when you switch to root or connect to a system where you forget to put the alias. |
|
|||
Note: FreeBSD syscons framebuffer, including high resolutions are ported from DragonFlyBSD.
|
|
|||
Quote:
Thanks |
|
|||
http://www.freebsd.org/cgi/cvsweb.cg...cons/syscons.c search for revision 1.436
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Xorg + Xfce4 resolution problem | sniper007 | FreeBSD General | 4 | 30th April 2009 04:38 PM |
Resolution problem.. | PCBSD3000 | FreeBSD General | 5 | 13th April 2009 07:56 PM |
resolution too high!!! =| ? what? | seadog109 | Other BSD and UNIX/UNIX-like | 19 | 18th October 2008 04:25 AM |
FVWM/X11 Resolution Issue? | m4rc | OpenBSD General | 8 | 3rd July 2008 02:45 PM |
Changing resolution | Cloud | General software and network | 3 | 27th June 2008 06:03 PM |