Raspberry Pi 3.5" Display Anzeigeprobleme in der Konsole

DMHas

Lt. Commander
Registriert
Sep. 2005
Beiträge
1.658
Hallo zusammen,

ich schlage mich schon länger mit dem Problem rum, dass das 3,5" Display (Waveshare 3.5inch RPi LCD B) bei der Verwendung im Befehlszeilen-Modus (command line). Dabei wird einfach nicht der ganze Inhalt angezeigt. Das sieht man ganz gut, wenn man "Enter" drückt. Es sieht aus als würde ein anderer Anzeigebereich kurz eingeblendet. Wenn ich den Desktop starte (startx) wird alles richtig angezeigt ohne Probleme. Auch das umschalten zwischen HDMI und 3.5" Display und Touchscreen klappt perfekt.

Probiert habe ich schon die manuelle Installation des Treibers, die Installation des Waveshare-Raspbianimages, die Auflösung manuell in der cmdline.txt und config.txt anzugeben, framebuffer_width & framebuffer_height auf 480 x 320 angepasst. Hat aber alles nichts geholfen.


Zum besseren Verständnis ein Link zu erklärung (MP4 Video):
dmhas.de/5temp/rpi-video-forum64.mp4

Vielleicht hat noch jemand von Euch eine Idee, was ich einstellen könnte?
 
Die Auflösung beträgt 480 x 320 (Breite x Höhe). Ist auch in der config.txt so hinterlegt.
hdmi_group=2
hdmi_mode=1
hdmi_mode=87
hdmi_cvt 480 320 60 6 0 0 0
hdmi_drive=2
display_rotate=0

Wie gesagt im Desktop werden die Bildschirmgrenzen perfekt übernommen. Aber testen kann ja nicht schaden.
 
Das sind aber die Einstellungen für den HDMI..
Laut dem hier müssten die Einstellungen fürs LCD woanders liegen, öffne mal mit nano die angegebene Datei und poste mal den Inhalt
Raspberry LCD Toggle LCD_HDMI.png
 
Ich habe mal den Text von LCD35B-show angehängt. Das sind die Originaldateien von Waveshare (ich habe nichts an diesen geändert).

sudo cp ./waveshare35b-overlay.dtb /boot/overlays/
sudo cp -rf ./usr/share/X11/xorg.conf.d/99-fbturbo.conf /usr/share/X11/xorg.conf.d/
if [ -b /dev/mmcblk0p7 ]; then
sudo cp ./cmdline.txt-noobs /boot/cmdline.txt
else
sudo cp ./cmdline.txt /boot/
fi

sudo cp ./inittab /etc/

if test "$#" = "0" -o "$1" = "0" -o "$1" = "90" -o "$1" = "180" -o "$1" = "270"; then
sudo reboot
echo "reboot now"
else
echo "Invalid parameter,Usage:LCD35B-show [0] [90] [180] [270]"
fi
Code:
dwc_otg.lpm_enable=0 console=tty1 console=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait fbcon=map:10 fbcon=font:ProFont6x11 logo.nologo
 
DMHas schrieb:
/usr/share/X11/xorg.conf.d/99-fbturbo.conf

Poste bitte mal dessen Inhalt.
Der Inhalt dieser wird zur neuen xorg.conf.d welche beim Einsatz des X-Servers (Desktopumgebung) geladen wird.
Darin sollte auch die Angabe der Auflösung zu finden sein evt. auch ein Overscan Problem...
Das switchen der Ausgabe (wie in deinem Video) ist nur ein Scroll des Bildschirminhalts was in dessen Framebuffer geladen ist. was auf eine zu niedrige Auflösung hinweisen könnte.

LG
 
Schonmal Danke für deine Hilfe! Mein Wissen bezüglich Linux ist sehr rudimentär.

# This is a minimal sample config file, which can be copied to
# /etc/X11/xorg.conf in order to make the Xorg server pick up
# and load xf86-video-fbturbo driver installed in the system.
#
# When troubleshooting, check /var/log/Xorg.0.log for the debugging
# output and error messages.
#The driver is made by Waveshare&Spotpear
# Run "man fbturbo" to get additional information about the extra
# configuration options for tuning the driver.

Section "Device"
Identifier "Allwinner A10/A13 FBDEV"
Driver "fbturbo"
Option "fbdev" "/dev/fb0"

Option "SwapbuffersWait" "true"
EndSection

NAME
fbturbo - video driver for Allwinner and other ARM-based devices

SYNOPSIS
Section "Device"
Identifier "devname"
Driver "fbturbo"
...
EndSection

DESCRIPTION
fbturbo is an Xorg driver for Allwinner and other ARM-based devices, derived from fbdev driver. With regard to 2D graphics, it provides a number of software optimizations on all
platforms, while letting the SIMD (ARM NEON) accelerated code from the pixman library run at full speed without any unnecessary overhead. 2D hardware acceleration using G2D is sup‐
ported on sunxi platforms. The recommended framebuffer color depths are 16 (RGB565) and 24 (XRGB8888), the other color depths may be supported too. Multi-head configurations are sup‐
ported.

SUPPORTED HARDWARE
The fbturbo driver supports all hardware where a framebuffer driver is available and uses the os-specific submodule fbdevhw(4) to talk to the kernel device driver. Currently a fbde‐
vhw module is available for linux. Additionally it is intended to use some of the display controller features from Allwinner A10/A13 SoC and provide the necessary DRI2 integration
with the proprietary OpenGL ES binary blobs for Mali400 GPU (if they are installed in the system). The part related to Mali400 GPU support is derived from the vendor provided open
source xf86-video-mali driver.

CONFIGURATION DETAILS
Please refer to xorg.conf(5) for general configuration details. This section only covers configuration details specific to this driver.

For this driver it is not required to specify modes in the screen section of the config file. The fbturbo driver can pick up the currently used video mode from the framebuffer
driver and will use it if there are no video modes configured.

The following driver Options are supported:

Option "fbdev" "string"
The framebuffer device to use. Default: /dev/fb0.

Option "ShadowFB" "boolean"
Enable or disable use of the shadow framebuffer layer. Default: off on most platforms (any hardware that supports NEON, VFP, or 2D hardware acceleration).

Option "Rotate" "string"
Enable rotation of the display. The supported values are "CW" (clockwise, 90 degrees), "UD" (upside down, 180 degrees) and "CCW" (counter clockwise, 270 degrees). Implies use
of the shadow framebuffer layer. Default: off.

Option "UseBackingStore" "boolean"
Enable the use of backing store for certain windows at the bottom of the stacking order. This allows to avoid expensive redraws caused by expose events when dragging one win‐
dow on top of another. The default heuristics tries to be "smart" and avoid backing store allocation for the active window which has keyboard focus. The purpose is to get the
best balance between performance and memory footprint without introducing full compositing overhead. Default: inverse of ShadowFB

Option "ForceBackingStore" "boolean"
Same as "UseBackingStore" option, but don't apply any heuristics and just allocate backing store for all windows.

Option "HWCursor" "boolean"
Enable or disable the HW cursor. Supported on sunxi platforms. Default: on if supported, off otherwise.

Option "DRI2" "boolean"

Option "fbdev" "string"
The framebuffer device to use. Default: /dev/fb0.

Option "ShadowFB" "boolean"
Enable or disable use of the shadow framebuffer layer. Default: off on most platforms (any hardware that supports NEON, VFP, or 2D hardware acceleration).

Option "Rotate" "string"
Enable rotation of the display. The supported values are "CW" (clockwise, 90 degrees), "UD" (upside down, 180 degrees) and "CCW" (counter clockwise, 270 degrees). Implies use
of the shadow framebuffer layer. Default: off.

Option "UseBackingStore" "boolean"
Enable the use of backing store for certain windows at the bottom of the stacking order. This allows to avoid expensive redraws caused by expose events when dragging one win‐
dow on top of another. The default heuristics tries to be "smart" and avoid backing store allocation for the active window which has keyboard focus. The purpose is to get the
best balance between performance and memory footprint without introducing full compositing overhead. Default: inverse of ShadowFB

Option "ForceBackingStore" "boolean"
Same as "UseBackingStore" option, but don't apply any heuristics and just allocate backing store for all windows.

Option "HWCursor" "boolean"
Enable or disable the HW cursor. Supported on sunxi platforms. Default: on if supported, off otherwise.

Option "DRI2" "boolean"
Enable or disable DRI2 integration for Mali GPU. Provides hardware accelerated OpenGL ES in the case if proprietary blob libMali.so is installed in the system and linux kernel
provides modules mali.ko, mali_drm.ko and ump.ko with compatible version (for example, both kernel modules and libMali.so can have revision r3p0). Default: on.

Option "DRI2HWOverlay" "boolean"
Enable the use of display controller hardware overlays (aka "layers", "windows", ...) for fully visible DRI2 backed OpenGL ES windows in order to avoid expensive memory copy
operations. That's a zero-copy solution which eliminates unnecessary CPU overhead. Default: on.

Note: the hardware overlays are automatically disabled in the case if a compositing window manager (xfwm4, kwin, ...) is used for various fancy desktop effects such as windows
translucency or shadows. Maybe some improvements are possible in this area. But if you really care about the desktop performance, then you likely don't want to enable any com‐
positing effects in your window manager anyway.

Option "SwapbuffersWait" "boolean"
This option controls the behavior of eglSwapBuffers calls by OpenGL ES applications. If enabled, the calls will try to avoid tearing by making sure the display scanline is
outside of the area to be copied before the copy occurs. If disabled, no scanline synchronization is performed, meaning tearing will likely occur. Note that when enabled, this
option can adversely affect the framerate of applications that render frames at less than refresh rate. Default: enabled.

Option "AccelMethod" "string"
Chooses between available acceleration architectures. Valid values are G2D and CPU. G2D is only available on sunxi hardware with G2D support (such as A10). The default is
G2D on supported platforms, CPU on others.

Option "XVHWOverlay" "boolean"
Enable or disable the use of display controller hardware overlays for XVideo acceleration. Only available on sunxi hardware. Default: on if supported, off otherwise.

SEE ALSO
Xorg(1), xorg.conf(5), Xserver(1), X(7), fbdevhw(4)
 
lösche mal folgendes aus der cmdline.txt

fbcon=map:10 fbcon=font:ProFont6x11

Dann sollte der VGA Treiber übernehmen sofern vorhanden, kannst du danach auch wieder eintragen falls keine Besserung.

Diese Werte beschreiben wie der Framebuffer und welcher Schriftausgabe dargestellt wird, was auch diesen Scrolleffekt beinhaltet.

hier mal die Doku zu den framebuffer switches...
https://www.kernel.org/doc/Documentation/fb/fbcon.txt
 
  • Gefällt mir
Reaktionen: DMHas
:daumen:

Perfekt! Das Löschen der beiden fbcon-Befehle hat es gelöst!

Danke!
 
  • Gefällt mir
Reaktionen: stinger2k
Zurück
Oben