|
NetBSD General Other questions regarding NetBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
||||
It's been a while since I did anything like this, but I *think* you'll need to create, in boot.cfg, a menu item which contains the parameters you want. Looking at the boot.conf(5) man page it would be something like this:
menu=<your description>:boot gop 0 If that syntax turns out to be absurd, then maybe a modification of it consistent with the general idea being floated? |
|
||||
Quote:
Code:
menu=<entry description>:gop 0;rndseed /var/db/entropy-file;boot netbsd Quote:
Code:
option "AccelMethod" "uxa"
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„ |
|
||||
Thanks a lot for your help. With this entry in /boot.cfg gop is set to 0. Now I have the maximum resolution which my monitor is able to show.
But (there must be always a but) now I have a terrible resolution on the console (640x480). Should I additionally set the text parameter to another value? The computer with this issues is an Intel NUC 6CYAH with Intel 500 graphics. It is not too old, not older than 3 or 4 years. Regards Berni |
|
||||
Quote:
The framebuffer console should retain the resolution set by the bootloader with gop, using the generic genfb(4) driver instead of i915drmkms. I suspect (but may be wrong) kernel is attempting to load Intel DRM (thus disabling genfb), so when DRM driver fails to attach to, all you're left with is the standard resolution. What does Code:
dmesg | fgrep genfb If using genfb, with DRM disabled, it should look like: Code:
[ 1.015430] genfb0 at pci0 dev 2 function 0: vendor 8086 product 0166 (rev. 0x09) [ 1.015430] genfb0: framebuffer at 0xe0000000, size 1366x768, depth 32, stride 5504 [ 1.015430] genfb0: shadow framebuffer enabled, size 4128 KB [ 1.015430] wsdisplay0 at genfb0 kbdmux 1: console (default, vt100 emulation), using wskbd0 [ 1.015430] drm at genfb0 not configured If you find i915drmkms is not disabled, you may blacklist the module at boot time. At the bootloader prompt, pass the -c flag to the kernel: Code:
> boot -c Code:
uc> list # list all devs; look for your drmkms entry uc> disable i915drmkms # disable Intel DRM uc> quit Code:
> userconf disable i915drmkms Code:
menu=<entry description>:gop 0;rndseed /var/db/entropy-file;userconf disable i915drmkms;boot netbsd If using genfb, Xorg display driver must be set to wsfb(4) for higher resolutions to be enabled. This can be done by setting: Code:
Section "Device" Identifier "Card0" Driver "wsfb" EndSection Compared to drm dirvers, genfb/wsfb carries non-negligible limitations:
Quote:
Another option would be building a -current kernel with Riastradh's src branch, which contains updated drm/kms (ported from Linux 5.6, so much newer compared to the current ones from 4.11). This will hopefully make it into -10.* RELEASE. If you're interested in testing the new code (still pretty much experimental), clone the repository from Riastradh's GitHub and build a kernel (remember to back up the known-working one): Code:
git clone https://github.com/riastradh/netbsd-src cd netbsd-src git checkout reredrm56 Please report any panics to the GitHub repository. With Intel GPUs, the modesetting Xorg display driver must be used currently. Code:
Section "Device" Identifier "Card0" Driver "modesetting" EndSection
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„ Last edited by Sehnsucht94; 21st August 2021 at 11:33 AM. |
|
||||
Wow! Thats great Paolo! You are my hero.
I now have a menu entry which disables i915drmkms and sets gop to 0. That works perfect, thank you so much. I'm just playing with the wscons settings to get 80x50 screens on the console. If that will work I am 100% satisfied. Regards Berni |
|
||||
Have no success trying a better wscons resolution. Whatever I do in wscons.conf is ignored: uncomment the IBM font and changing the screens to 80x50. The machine starts with a small & nice console font, but during boot the font size changes to standard VGA. Any ideas?
Regards Berni |
|
||||
Quote:
Anyway, what about building a custom kernel and embedding the font in it? You can take one of the supported WSFonts, choosing among the smaller ones: Code:
# Make sure to comment the default entries # options FONT_BOLD8x16 # options FONT_BOLD16x32 # The first specified option is going to be # the default framebuffer console font options FONT_SPLEEN5x8 options FONT_SPLEEN6x12
__________________
“Mi casa tendrá dos piernas y mis sueños no tendrán fronteras„ |
|
||||
OK, I tried to compile a new kernel, using the fonts from your example.
Result: It works! Both, console as well as xorg. For xorg I still have to set gop to 0 in boot.cfg. The only problem: Now the console fonts are too small, extremely small! Looks like a resolution of 262x132 - very hard to read. What may be a good compromise for the size of the console fonts? Are vt220l8x8 and 8x16 better? |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
No user for in PXE-Boot Server environment to boot Diskless clients | dennisN86 | OpenBSD General | 10 | 13th May 2021 11:39 AM |
Invalid Signature when trying to boot Ubuntu 14.04 (Dual Boot) | bsd007 | FreeBSD General | 7 | 18th September 2014 12:37 PM |
Sun XVR-600 in 24-bit mode | Don_HH2K | OpenBSD Installation and Upgrading | 2 | 30th June 2010 08:06 PM |
no-tab-mode in mg? | Sunnz | OpenBSD General | 0 | 10th March 2010 12:10 PM |
Dual-boot laptop won't boot OpenBSD after upgrade to 4.3 | kbeaucha | OpenBSD Installation and Upgrading | 17 | 30th May 2008 02:40 PM |