On Sat, 10 Mar 2018 14:34:31 -0600 Bruce Dubbs <[email protected]> wrote:
> Ken Moffat wrote: > > On Sat, Mar 10, 2018 at 02:38:57AM +0000, Hans Malissa wrote: > >> I've finished compiling LFS 8.2-systemd without problems, and now I'm > >> starting to work on BLFS. > >> > >> > >> I have a question regarding the "Setting a smaller screen size in grub" > >> section in chapter 3: I've tried several screen size settings for the > >> 'video=' parameter in the grub command line, but none of them seem to have > >> an effect, and I always end up with an old fashioned 80x25 text display. I > >> know that in another Linux distribution running on the same computer, the > >> screen resolution is 1440x900, so it's not a hardware issue. I'm assuming > >> that I need a particular kernel module to get this working, but I can't > >> figure out which one. > >> > >> > >> Thanks a lot, > >> > > > > Probably whichever framebuffer your video card uses - I think I > > used to use video= on my servers, but I've now switched those to > > using a larger font (14x28). For the kernel video is going to need video=radeonfb:1440x900-32 (radeon as example, could be nvidiafb matroxfb, etc) > > On a radeon which will be using Xorg, > > CONFIG_DRM_RADEON works - if it is a server, one of the CONFIG_FB > > devices is probably the right choice. Depending on how you want your device to work, it took me a while with radeon. While video= used to be fine with the kernel, the grub option for video resolution gets passed to the video driver as a payload. I think it is gfxmode that does it. For me I had to use CONFIG_DRM=y and CONFIG_DRM_RADEON=y. I do not know if the KMS helper and KMS_FB helper are required. Also, you'll need frame buffer in kernel as CONFIG_FB=y. I wouldn't select the framebuffer radeon driver. Use the DRM radeon driver. I've been using that since A4-3400 days. It works fine with the current A8-3800. Similar with other GPU's, use the DRM driver if it is available. Keep adjusting the config until something works. > > On my test server with an old radeon I also dropped back to 80x25 > > when I upgraded to 8.2, and failed to load the intended large font. > > That was because my notes suggested I only needed a few of the > > radeon firmware blobs : in fact, on my previous build I had dropped > > all of them into /lib/firmware - adding a few more made the large > > font work, so if you are on radeon or amdgpu then you might need the > > firmware to get a framebuffer console working. > Yes the required firmware will be required for certain graphics devices. Especially radeon. Look at the kernel messages to make sure the firmware was loaded. If not, you should see messages that firmware was not loaded because it wasn't found. What I do is load the firmware into the kernel as blobs: CONFIG_FW_LOADER=y # CONFIG_FIRMWARE_IN_KERNEL is not set CONFIG_EXTRA_FIRMWARE="radeon/SUMO_me.bin radeon/SUMO_pfp.bin radeon/SUMO_rlc.bin radeon/SUMO_uvd.bin rtl_nic/rtl8168f-2.fw" CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware" > For me it depends on the font I want to use. On a sysV system I have > terminus fonts installed and set FONT=ter-128n. Of course that doesn't > come into effect until the console init script is run during boot. > > I do not know how to do the same thing in systemd, but the simple command > is 'setfont $FONT' where FONT is located in /usr/share/fonts. I do not > think setfont understands ttf fonts, but see the man page for details. There are ways to put the font you want into the kernel itself during compile time, but the tools are sparse. For SystemD: /etc/vconsole.conf: FONT=Lat2-Terminus16 (as an example) FONT="ter-v32n" for another example Sincerely, William Harrington -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
