ui process terminating on booting chromiumos on rpi3

[giriflint]

dmesg.txt

ui.LATEST.txt

Xorg.0.log_with_hdmi.txt

Hi,

I am trying to boot Chromium R53 on RaspberryPi3 using the rpi-4.4.y linux kernel which has the most recent VC4 fixes.
The system boots but without the UI. Attached are the serial and X logs, the kernel config, config.txt and the cmdline.txt.
There was a modesetting failure as per the logs. Am I missing any config paramters in the config.txt or in the kernel .config, or, could it be a clash between two different drivers trying to access the same resource?
Please help.

kernel_config.txt

cmdline.txt

config.txt

var_log_messages.txt

[anholt]

[    0.000000] cma: Reserved 476 MiB at 0x1f000000

This cause intermittent crashes with 3D. Delete the gpu_mem and cma lines from your config.txt, and use the defaults that vc4-kms-v3d sets up (at least, I assume you're using vc4-kms-v3d, because I don't know how the driver would probe otherwise).

The dmesg says:

[   18.018826] vc4-drm soc:gpu: No connectors reported connected with modes
[   18.100122] [drm] Cannot find any crtc or sizes - going 1024x768

I assume this is the error you were talking about. This would be EDID failing to probe on HDMI (you're using HDMI, right?). Are you by chance using an HDMI->VGA converter?

[giriflint]

Thanks for the advice Eric. The error was actually in the Xorg.0.log where the modesetting failed.

…

On Thu, Jan 26, 2017 at 9:45 PM, Eric Anholt ***@***.***> wrote: [ 0.000000] cma: Reserved 476 MiB at 0x1f000000 This cause intermittent crashes with 3D. Delete the gpu_mem and cma lines from your config.txt, and use the defaults that vc4-kms-v3d sets up (at least, I assume you're using vc4-kms-v3d, because I don't know how the driver would probe otherwise). The dmesg says: [ 18.018826] vc4-drm soc:gpu: No connectors reported connected with modes [ 18.100122] [drm] Cannot find any crtc or sizes - going 1024x768 I assume this is the error you were talking about. This would be EDID failing to probe on HDMI (you're using HDMI, right?). Are you by chance using an HDMI->VGA converter? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#74 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AXdECrYc4AVPKBftI6fNneSrdsU2By_hks5rWRQTgaJpZM4LOb-I> .

[anholt]

OK, so we're looking at this:

[    60.934] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[    60.934] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[    60.934] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[    60.938] (II) AIGLX: Loaded and initialized vc4
[    60.938] (II) GLX: Initialized DRI2 GL provider for screen 0
[    60.977] (EE) modeset(0): Failed(EE)
Fatal server error:
[    60.978] (EE) failed to create screen resources(EE)
[    60.978] (EE)

This is a new one to me. Also, the mismatch between dmesg claiming no connectors with modes while Xorg.0.log shows an EDID being found is confusing. The failure in CSR from Xorg.0.log could be from failing to set a mode, in which case dmesg from a boot with drm.debug=0x1e on the kernel command line might be useful. But that's kind of guessing at a problem, when we would be better off using gdb to step through CreateScreenResources to see what fails.