FreeBSD 11.2 - Default resolution on console window











up vote
1
down vote

favorite












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 0 in /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







share|improve this question







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • 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 at 16:08










  • related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
    – Rui F Ribeiro
    Dec 4 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.
    – Tom
    Dec 4 at 19:39















up vote
1
down vote

favorite












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 0 in /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







share|improve this question







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




















  • 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 at 16:08










  • related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
    – Rui F Ribeiro
    Dec 4 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.
    – Tom
    Dec 4 at 19:39













up vote
1
down vote

favorite









up vote
1
down vote

favorite











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 0 in /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







share|improve this question







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











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 0 in /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






share|improve this question







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked Dec 4 at 15:56









Tom

1217




1217




New contributor




Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Tom is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












  • 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 at 16:08










  • related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
    – Rui F Ribeiro
    Dec 4 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.
    – Tom
    Dec 4 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 at 16:08










  • related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
    – Rui F Ribeiro
    Dec 4 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.
    – Tom
    Dec 4 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 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 at 16:08












related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 at 17:17






related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 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.
– Tom
Dec 4 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.
– Tom
Dec 4 at 19:39










1 Answer
1






active

oldest

votes

















up vote
0
down vote













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






share|improve this answer





















  • I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
    – Tom
    2 days ago










  • kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
    – Tom
    2 days ago











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',
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
});


}
});






Tom is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















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








up vote
0
down vote













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






share|improve this answer





















  • I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
    – Tom
    2 days ago










  • kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
    – Tom
    2 days ago















up vote
0
down vote













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






share|improve this answer





















  • I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
    – Tom
    2 days ago










  • kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
    – Tom
    2 days ago













up vote
0
down vote










up vote
0
down vote









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






share|improve this answer












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







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 5 at 0:19









JdeBP

32.5k468152




32.5k468152












  • I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
    – Tom
    2 days ago










  • kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
    – Tom
    2 days ago


















  • I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
    – Tom
    2 days ago










  • kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
    – Tom
    2 days ago
















I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tom
2 days ago




I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tom
2 days ago












kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago




kldload vesa from the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago










Tom is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Tom is a new contributor. Be nice, and check out our Code of Conduct.













Tom is a new contributor. Be nice, and check out our Code of Conduct.












Tom is a new contributor. Be nice, and check out our Code of Conduct.
















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.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • 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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

Accessing regular linux commands in Huawei's Dopra Linux

Image
4 Backstory: I have a Huawei HG8245 router in my house and I want to change the default username/password. I've tried following this guide but the config file always gets reset. My ISP isn't helping either so I'm looking for other ways to accomplish this. The router has telnet access so this seems like a way to change the credentials. The first shell I gain access to looks like this: WAP> Pressing "?" gives me a list of available commands which I've pasted here, the two interesting ones are "su" and "shell". I can't seem to get su access, even after logging in as root (challenge password prompt, and then nothing happens), but shell gives me a proper linux shell. WAP>shell BusyBox v1.18.4 (2017-12-26 17:06:34 CST) built-in shell (ash) Enter 'hel...
Read more

Can't connect RFCOMM socket: Host is down

Image
up vote 3 down vote favorite I have bluez 5.4.3 and I am attempting to communicate with a ble device through minicom. These two deceives (my computer and a bluno nano) are alreadt paired and this has been my method so far. #bluetoothctl # pair xx:xx:xx:xx:xx:xx # exit Everything is working well so far then... #sudo rfcomm connect /dev/rfcomm0 xx:xx:xx:xx:xx:xx 1 & [1] 3665 Can't connect RFCOMM socket: Host is down Does anyone know how to resolve this issue? Any help would be very much appreciated. bluetooth bluez share | improve this question asked Feb 9 '17 at 18:46 Brandon Knape 46 2 ...
Read more

Kernel panic - not syncing: Fatal Exception in Interrupt

Image
0 Every day this error occured on my pc, kernel panic error on interrupt, what will be the problem? linux-mint share asked 6 mins ago Vinod Selvin Vinod Selvin 1 1 New contributor Vinod Selvin is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct. add a comment ...
Read more