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 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 at 15:56
Tom
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.
add a comment |
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 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 at 15:56
Tom
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.
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 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.
– Tom
Dec 4 at 19:39
add a comment |
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 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 at 15:56
Tom
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.
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 at 15:56
Tom
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.
asked Dec 4 at 15:56
Tom
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.
asked Dec 4 at 15:56
Tom
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.
asked Dec 4 at 15:56
Tom
1217
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 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.
– Tom
Dec 4 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 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 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.
– 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
add a comment |
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
answered Dec 5 at 0:19
JdeBP
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 vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago
add a comment |
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
answered Dec 5 at 0:19
JdeBP
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 vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago
add a comment |
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
answered Dec 5 at 0:19
JdeBP
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 vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago
add a comment |
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
answered Dec 5 at 0:19
JdeBP
32.5k468152
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 at 0:19
JdeBP
32.5k468152
answered Dec 5 at 0:19
JdeBP
32.5k468152
answered Dec 5 at 0:19
JdeBP
32.5k468152
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 vesafrom the first link gives an error: sysctl_unregister_oid: failed to unregister sysctl
– Tom
2 days ago
add a comment |
I tried that already but the command lists no available modes. I will read the two linked articles. Thanks.
– Tom
2 days ago
kldload vesafrom 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
add a comment |
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.
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.
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 at 16:08
related? unix.stackexchange.com/questions/361243/… Would "mode 2" work?
– Rui F Ribeiro
Dec 4 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.– Tom
Dec 4 at 19:39