Hi Nicolas, On 06.03.20 21:33, Stefan Wahren wrote: > Hi Nicolas, > > Am 05.03.20 um 11:44 schrieb Nicolas Saenz Julienne: >> Hi Stefan, >> >> On Tue, 2020-03-03 at 20:24 +0100, Stefan Wahren wrote: >>>>>> Note: I tested this on RPi3b, RPi3a+ and RPi2b. >>>>> as i already wrote this prevent X to start on current Raspbian on my >>>>> Raspberry Pi 3A+ (multi_v7_defconfig, no u-boot). We must be careful here. >>>>> >>>>> I will take a look at the debug UART. Maybe there are more helpful >>>>> information. >>>> It seems we're seeing different things, I tested this on raspbian >>>> (multi_v7_defconfig) and on arm64. I'll try again from scratch tomorrow. >>> My modifications to the Raspbian image (from 13.2.2020) are little: >>> >>> - specify devicetree to config.txt >>> - change console to ttyS1 and remove "silent" in cmdline.txt >>> - rename all original kernel7*.img >>> - copy dtb and kernel7.img to boot partition >>> - copy kernel modules to root partition >> Would you mind retesting with the latest linux-next? I validated an image based >> on 5.6.0-rc4-next-20200305-00001-g285a7a64cd56 and a fresh raspbian download on >> RPi3a+ without X issues. > i retested with todays linux-next and the issue persists on my RPi 3A+ / > HP ZR2440w with this patch applied. I tested my display with a RPI 3B, 3B+ and a Zero W. All of them had the same issue. Btw i used this display the last years for testing the Raspberry Pi. After that i connected the RPI 3B to my TV screen and it works with the patch applied. > > I will try more hardware combinations tomorrow to see, this issue is > more board or display related. > > Best regards > Stefan > >
