I had no problems with my 7" 1024x600 non-touch dipslay.
But recently I built my first mobile Pi ZeroW and used it in 40x15 console mode on 320x240 SPI LCD.
Most was fine, and most importantly "vi" (I use since 28 years) is cool.
But "sudo raspi-config" did display stuff outside the visible area.
So I had to ssh into the Pi ZeroW in order to run "sudo raspi-config" there.
Today I wanted to add that 320x240 console for Raspberry foundation controlled "raspi-config" has problems.
But I tried to tell Raspbian first that I have a 320x240 LCD (running console via /boot/cmdline.txt appended "fbcon=map:10").
Code: Select all
hdmi_group=2
hdmi_mode=87
hdmi_cvt=320 240 60 1 0 0 0
did not make a difference. In fact the custom mode seems not to work because "tvservice -m DMT" says DMT group has 0 modes. But then I added
Code: Select all
framebuffer_width=320
framebuffer_height=240
to /boot/config.txt and immediately saw a difference: the console is now 40x30. And "sudo raspi-config" works fine now (although some texts are still too long as the headlines). So for console 320x240 is fine for me now with the programs I use:
P.S:
Just found what the little square in boot log messages means.
This is displayed
for this too long for 40 character with console message:
Code: Select all
Started Regular background program processing daemon.
P.P.S:
The problem with "sudo raspi-config" occurs with VGA8x16 font an only 15 console lines on 320x240 LCD. Using VGA8x8 is the solution. There are other fonts listed I would like to try (eg. 6x10 or ProFont6x11), which is not possible with my LCD because of the stated "Note, not all drivers can handle font with widths not divisible by 8, such as vga16fb.":
https://www.kernel.org/doc/Documentation/fb/fbcon.txt