FreeBSD 11.2 - Default resolution on console windowUsing native 1366 x 768 resolution in a Lenovo...
What things do I only get a limited opportunity to take photos of?
Does WiFi affect the quality of images downloaded from the internet?
Are there any rules for identifying what spell an opponent is casting?
How can religions without a hell discourage evil-doing?
A Tale of Snake and Coffee
Should I worry about having my credit pulled multiple times while car shopping?
Is there a risk to write an invitation letter for a stranger to obtain a Czech (Schengen) visa?
Why doesn't Mathematica completely draw the fit?
Does anyone recognize these rockets, and their location?
Must a CPU have a GPU if the motherboard provides a display port (when there isn't any separate video card)?
The last tree in the Universe
How to address players struggling with simple controls?
My parents claim they cannot pay for my college education; what are my options?
How to know whether to write accidentals as sharps or flats?
Should I email my professor to clear up a (possibly very irrelevant) awkward misunderstanding?
How to remove multiple elements from Set/Map AND knowing which ones were removed?
Can an escape pod land on Earth from orbit and not be immediately detected?
How can Caller ID be faked?
Can an open source licence be revoked if it violates employer's IP?
How many times to repeat an event with known probability before it has occurred a number of times
Do items with curse of vanishing disappear from shulker boxes?
What is the color associated with lukewarm?
Is there a term for someone whose preferred policies are a mix of Left and Right?
Someone who is granted access to information but not expected to read it
FreeBSD 11.2 - Default resolution on console window
Using native 1366 x 768 resolution in a Lenovo IdeapadFreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer infoFreeBSD 11.2: how to resize the boot options menu on a UEFI/GPT/ZFS machine?FreeBSD 11.2 - 256 color support in console window
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I installed FreeBSD 11.2 on my DELL Latitude E7470 with UEFI (might be important). By default it does not install a GUI and that is fine by me (for now). Using the <Alt>+<Fn> keys I can switch between different virtual terminals.
I'm stuck with a 1920x1080 screen resolution
This results in way too small characters for me to read comfortably.
- I tried enterind
mode 0in /boot/loader.conf to switch to 800x600 mode but that does not work. It does work however when I press the<Esc>key during boot and enter it at the boot prompt. - Using
gop set <n>crashes the laptop, i.e. the screen goes black and the laptop does not respond to any keys anymore.
Anyone has any ideas on how to fix this?
freebsd console
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I installed FreeBSD 11.2 on my DELL Latitude E7470 with UEFI (might be important). By default it does not install a GUI and that is fine by me (for now). Using the <Alt>+<Fn> keys I can switch between different virtual terminals.
I'm stuck with a 1920x1080 screen resolution
This results in way too small characters for me to read comfortably.
- I tried enterind
mode 0in /boot/loader.conf to switch to 800x600 mode but that does not work. It does work however when I press the<Esc>key during boot and enter it at the boot prompt. - Using
gop set <n>crashes the laptop, i.e. the screen goes black and the laptop does not respond to any keys anymore.
Anyone has any ideas on how to fix this?
freebsd console
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
mode 2doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, settingmodealso prevents the commands behind it from executing. Since I had my WLAN config in the file behind themodecommand, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.
– Tommiie
Dec 4 '18 at 19:39
add a comment |
I installed FreeBSD 11.2 on my DELL Latitude E7470 with UEFI (might be important). By default it does not install a GUI and that is fine by me (for now). Using the <Alt>+<Fn> keys I can switch between different virtual terminals.
I'm stuck with a 1920x1080 screen resolution
This results in way too small characters for me to read comfortably.
- I tried enterind
mode 0in /boot/loader.conf to switch to 800x600 mode but that does not work. It does work however when I press the<Esc>key during boot and enter it at the boot prompt. - Using
gop set <n>crashes the laptop, i.e. the screen goes black and the laptop does not respond to any keys anymore.
Anyone has any ideas on how to fix this?
freebsd console
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
I installed FreeBSD 11.2 on my DELL Latitude E7470 with UEFI (might be important). By default it does not install a GUI and that is fine by me (for now). Using the <Alt>+<Fn> keys I can switch between different virtual terminals.
I'm stuck with a 1920x1080 screen resolution
This results in way too small characters for me to read comfortably.
- I tried enterind
mode 0in /boot/loader.conf to switch to 800x600 mode but that does not work. It does work however when I press the<Esc>key during boot and enter it at the boot prompt. - Using
gop set <n>crashes the laptop, i.e. the screen goes black and the laptop does not respond to any keys anymore.
Anyone has any ideas on how to fix this?
freebsd console
freebsd console
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
asked Dec 4 '18 at 15:56
TommiieTommiie
158210
158210
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 58 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
mode 2doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, settingmodealso prevents the commands behind it from executing. Since I had my WLAN config in the file behind themodecommand, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.
– Tommiie
Dec 4 '18 at 19:39
add a comment |
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
mode 2doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, settingmodealso prevents the commands behind it from executing. Since I had my WLAN config in the file behind themodecommand, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.
– Tommiie
Dec 4 '18 at 19:39
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
mode 2 doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, setting mode also prevents the commands behind it from executing. Since I had my WLAN config in the file behind the mode command, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.– Tommiie
Dec 4 '18 at 19:39
mode 2 doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, setting mode also prevents the commands behind it from executing. Since I had my WLAN config in the file behind the mode command, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.– Tommiie
Dec 4 '18 at 19:39
add a comment |
1 Answer
1
active
oldest
votes
The way to change the resolution of the kernel virtual terminals is the vidcontrol command. The -i mode option causes it to display a table of available video modes. Make the chosen mode setting be applied at bootstrap by setting the allscreens_flags variable in /etc/rc.conf.
Further reading
- "Changing Console Video Modes". FreeBSD Handbook.
- FreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer info
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tommiie
Dec 5 '18 at 7:18
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485936%2ffreebsd-11-2-default-resolution-on-console-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The way to change the resolution of the kernel virtual terminals is the vidcontrol command. The -i mode option causes it to display a table of available video modes. Make the chosen mode setting be applied at bootstrap by setting the allscreens_flags variable in /etc/rc.conf.
Further reading
- "Changing Console Video Modes". FreeBSD Handbook.
- FreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer info
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tommiie
Dec 5 '18 at 7:18
add a comment |
The way to change the resolution of the kernel virtual terminals is the vidcontrol command. The -i mode option causes it to display a table of available video modes. Make the chosen mode setting be applied at bootstrap by setting the allscreens_flags variable in /etc/rc.conf.
Further reading
- "Changing Console Video Modes". FreeBSD Handbook.
- FreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer info
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tommiie
Dec 5 '18 at 7:18
add a comment |
The way to change the resolution of the kernel virtual terminals is the vidcontrol command. The -i mode option causes it to display a table of available video modes. Make the chosen mode setting be applied at bootstrap by setting the allscreens_flags variable in /etc/rc.conf.
Further reading
- "Changing Console Video Modes". FreeBSD Handbook.
- FreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer info
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
The way to change the resolution of the kernel virtual terminals is the vidcontrol command. The -i mode option causes it to display a table of available video modes. Make the chosen mode setting be applied at bootstrap by setting the allscreens_flags variable in /etc/rc.conf.
Further reading
- "Changing Console Video Modes". FreeBSD Handbook.
- FreeBSD - best way to set console vidcontrol mode from boot without disrupting scrollback buffer info
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
answered Dec 5 '18 at 0:19
JdeBPJdeBP
40.1k484196
40.1k484196
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tommiie
Dec 5 '18 at 7:18
add a comment |
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tommiie
Dec 5 '18 at 7:18
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tommiie
Dec 5 '18 at 7:06
kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl– Tommiie
Dec 5 '18 at 7:18
kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl– Tommiie
Dec 5 '18 at 7:18
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f485936%2ffreebsd-11-2-default-resolution-on-console-window%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Interesting question, unfortunately I can't say I have a direct answer, but it does appear you are looking in the right place (i.e. loader.conf). Check out the bottom of this bug report and see what the users' resolution was, hopefully it can help. Possibly add "mode 0" to /boot/loader.rc.local (you may have to create that file)? forums.freebsd.org/threads/kernel-boot-resolution.53150
– bgregs
Dec 4 '18 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 '18 at 17:17
mode 2doesn’t work either. The file /boot/loader.rc.local is not referenced anywhere. The file /boot/loader.conf.local is though. But that file is no different than the one I was already using. In addition, settingmodealso prevents the commands behind it from executing. Since I had my WLAN config in the file behind themodecommand, my wifi card stopped working. So FreeBSD clearly doesn’t like the command.– Tommiie
Dec 4 '18 at 19:39