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. > The debug UART works fine, maybe the dmesg gives us a hint: [...] > [ 8.451520] vc4_hdmi 3f902000.hdmi: vc4-hdmi-hifi <-> 3f902000.hdmi > mapping ok > [ 8.451541] vc4_hdmi 3f902000.hdmi: ASoC: no DMI vendor name! > [ 8.465617] vc4-drm soc:gpu: bound 3f902000.hdmi (ops vc4_hdmi_ops > [vc4]) > [ 8.466033] vc4-drm soc:gpu: bound 3f806000.vec (ops vc4_vec_ops [vc4]) > [ 8.466159] vc4-drm soc:gpu: bound 3f004000.txp (ops vc4_txp_ops [vc4]) > [ 8.466292] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_hvs_ops [vc4]) > [ 8.466649] vc4-drm soc:gpu: bound 3f206000.pixelvalve (ops > vc4_crtc_ops [vc4]) > [ 8.466889] vc4-drm soc:gpu: bound 3f207000.pixelvalve (ops > vc4_crtc_ops [vc4]) > [ 8.467154] vc4-drm soc:gpu: bound 3f807000.pixelvalve (ops > vc4_crtc_ops [vc4]) > [ 8.467262] vc4-drm soc:gpu: bound 3fc00000.v3d (ops vc4_v3d_ops [vc4]) > [ 8.467272] checking generic (1e330000 8ca000) vs hw (0 ffffffff) > [ 8.467278] fb0: switching to vc4drmfb from simple > [ 8.473639] Console: switching to colour dummy device 80x30 > [ 8.473714] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > [ 8.473718] [drm] Driver supports precise vblank timestamp query. > [ 8.476777] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 0 > [ 8.534359] Console: switching to colour frame buffer device 90x30 > [ 8.550245] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device I get the exact same results as you here. Regards, Nicolas
Attachment:
signature.asc
Description: This is a digitally signed message part
