|
Bugzilla – Full Text Bug Listing |
| Summary: | Raspberry Pi 3B console video fails using DSI interface | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Lawrence Kearney <lawrence.kearney> |
| Component: | Kernel | Assignee: | openSUSE Kernel Bugs <kernel-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | afaerber, guillaume.gardet, ivan.ivanov, jslaby, lawrence.kearney, mbrugger, ptesarik, tiwai, tzimmermann, yousaf.kaukab |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | aarch64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Lawrence Kearney
2019-04-14 11:07:00 UTC
Hi Lawrence would you mind sharing your config.txt file. It should be available at /boot/efi/config.txt. The simplest test you can do is blacklist the vc4 kernel module. For instance by adding "modprobe.blacklist=vc4" to the kernel command line in grub. It should work out of the box with that, but you'll lose any access to vc4. An alternative is to use vc4, to do so you need to create a device-tree overlay using this as a reference: https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/display/panel/raspberrypi,7inch-touchscreen.txt I tested it myself some time ago and it was working fine, yet it's a little cumbersome to prepare. (In reply to Nicolas Patricio Saenz Julienne from comment #1) > Hi Lawrence would you mind sharing your config.txt file. It should be > available at /boot/efi/config.txt. # Get more options/information on http://elinux.org/RPiconfig # or on https://www.raspberrypi.org/documentation/configuration/config-txt.md # # !!!!! This file will get overwritten by updates. Please use !!!!! # !!!!! extraconfig.txt if you want to set additional !!!!! # !!!!! configuration options or add dt overlays. !!!!! # Our kernels are located on a Linux partition. Chainload U-Boot to load them. kernel=u-boot.bin # Use 32 MB for GPU for all RPis (Min 16 - Max 192 MB) # We don't need that much memory reserved for it, because we drive most hardware # from Linux, not the VPU OS gpu_mem=32 # Turbo mode: 0 = enable dynamic freq/voltage - 1 = always max force_turbo=0 # Start in turbo mode for 30 seconds or until cpufreq sets a frequency initial_turbo=30 # DO NOT overvoltage manually to not void warranty! over_voltage=0 # Fix mini UART input frequency, and setup/enable up the UART. enable_uart=1 # Disable warning overlays as they don't work well together with linux's graphical output avoid_warnings=1 # This overlay fixes divergences between the RPi device tree and what # upstream provides dtoverlay=upstream dtoverlay=upstream-aux-interrupt [pi1] # Max ARM freq (default 700 MHz) arm_freq=840 # Max core (GPU) freq (default 250 MHz) core_freq=375 # SDRAM freq (default 400) sdram_freq=400 [pi3] [all] # Allow u-boot to set arm_control include ubootconfig.txt # Allow user overrides of config options include extraconfig.txt (In reply to Nicolas Patricio Saenz Julienne from comment #2) > The simplest test you can do is blacklist the vc4 kernel module. For > instance by adding "modprobe.blacklist=vc4" to the kernel command line in > grub. It should work out of the box with that, but you'll lose any access to > vc4. > > An alternative is to use vc4, to do so you need to create a device-tree > overlay using this as a reference: > https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/ > bindings/display/panel/raspberrypi,7inch-touchscreen.txt I tested it myself > some time ago and it was working fine, yet it's a little cumbersome to > prepare. This does enable console output to the display and permit keyboard interactive login. This test does seem to indicate where the issue lies. Lawrence, in the future please share full logs and config files as attachments, to keep comments readable. And please clear the needinfo flag after providing it. I wonder whether this unfinished -dt submission might be related? https://build.opensuse.org/request/show/684245 (In reply to Andreas Färber from comment #9) > I wonder whether this unfinished -dt submission might be related? > https://build.opensuse.org/request/show/684245 It is now in Factory. Is this bug still occurring? (In reply to Guillaume GARDET from comment #11) > (In reply to Andreas Färber from comment #9) > > I wonder whether this unfinished -dt submission might be related? > > https://build.opensuse.org/request/show/684245 > > It is now in Factory. Is this bug still occurring? Hopefully? |