[fedora-arm] F25: black monitor on RPi 2

[Sylvain Pasche]

Hi,

I tried to run Fedora 25 Server and Minimal images on a Raspberry Pi 2 device (images Fedora-Server-armhfp-25_Beta-1.1-sda.raw and Fedora-Minimal-armhfp-25-20161019.n.0-sda.raw).

I can see output on the connected monitor during boot. At the end of the boot, it looks like the resolution changes and the monitor turns black (there is still a signal sent as it doesn't enter standby). Even if I switch to VT2 and press enter to fill the screen with login prompts, nothing is visible.

I tried the same image on a Pi 3 device and it works fine.

Is there a parameter that could be used to prevent this behavior at the end of the boot?

Cheers,
Sylvain
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists

[Peter Robinson]

Post by Sylvain Pasche
Hi,
I tried to run Fedora 25 Server and Minimal images on a Raspberry Pi 2 device (images Fedora-Server-armhfp-25_Beta-1.1-sda.raw and Fedora-Minimal-armhfp-25-20161019.n.0-sda.raw).
I can see output on the connected monitor during boot. At the end of the boot, it looks like the resolution changes and the monitor turns black (there is still a signal sent as it doesn't enter standby). Even if I switch to VT2 and press enter to fill the screen with login prompts, nothing is visible.
I tried the same image on a Pi 3 device and it works fine.
Is there a parameter that could be used to prevent this behavior at the end of the boot?

Having booted it on a RPi3 do you already have a user setup on it? If
so can you ssh in and get a dump of the dmesg? Easiest way to do this
is with fpaste ("dnf install -y fpaste") and then do "dmesg | fpaste"
and provide the link.

Also are you running the latest kernel, or the one shipped with beta?
4.8.1 has some fixes so might be better.

The accelerated driver is a little new and we've seen some issues with
some of the EDID monitor detection, we're trying to get as much debug
before the final release so we can fix as many of these issues as
possible.

Peter
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email t

[Sylvain Pasche]

Post by Peter Robinson
Having booted it on a RPi3 do you already have a user setup on it? If
so can you ssh in and get a dump of the dmesg? Easiest way to do this
is with fpaste ("dnf install -y fpaste") and then do "dmesg | fpaste"
and provide the link.
Also are you running the latest kernel, or the one shipped with beta?
4.8.1 has some fixes so might be better.
The accelerated driver is a little new and we've seen some issues with
some of the EDID monitor detection, we're trying to get as much debug
before the final release so we can fix as many of these issues as
possible.
Peter

Hi,

I booted the image on the RPi3 to update packages and create a user.

Here's the dmesg from the RPi2, using kernel 4.8.3:

https://paste.fedoraproject.org/459288/77249221/

Indeed it seems to complain about EDID:

[ 18.045539] fb: switching to vc4drmfb from simple
[ 18.049239] Console: switching to colour dummy device 80x30
[ 18.059757] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 18.059819] [drm] Driver supports precise vblank timestamp query.
[ 18.072356] EDID block is all zeroes
[ 18.072414] vc4-drm soc:gpu: HDMI-A-1: EDID block 0 invalid.
[ 18.072458] vc4-drm soc:gpu: No connectors reported connected with modes
[ 18.072510] [drm] Cannot find any crtc or sizes - going 1024x768
[ 18.078752] Console: switching to colour frame buffer device 128x48
[ 18.098709] vc4-drm soc:gpu: fb0: frame buffer device

I tried with 3 different monitors and they all show the black output
symptoms.

Sylvain
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an emai

[Peter Robinson]

Post by Sylvain Pasche

Post by Peter Robinson
Having booted it on a RPi3 do you already have a user setup on it? If
so can you ssh in and get a dump of the dmesg? Easiest way to do this
is with fpaste ("dnf install -y fpaste") and then do "dmesg | fpaste"
and provide the link.
Also are you running the latest kernel, or the one shipped with beta?
4.8.1 has some fixes so might be better.
The accelerated driver is a little new and we've seen some issues with
some of the EDID monitor detection, we're trying to get as much debug
before the final release so we can fix as many of these issues as
possible.
Peter

Hi,
I booted the image on the RPi3 to update packages and create a user.
https://paste.fedoraproject.org/459288/77249221/
[ 18.045539] fb: switching to vc4drmfb from simple
I tried with 3 different monitors and they all show the black output
symptoms.

Can you provide details of the three monitors and their resolutions,
and how you connect them.

In good news I think we might have a kernel that fixes them. Can you
try 4.8.4-301 from koji [1] (or it'll be in updates-testing RSN)

[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=812331
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists

[Sylvain Pasche]

Post by Peter Robinson
Can you provide details of the three monitors and their resolutions,
and how you connect them.
In good news I think we might have a kernel that fixes them. Can you
try 4.8.4-301 from koji [1] (or it'll be in updates-testing RSN)
[1] http://koji.fedoraproject.org/koji/buildinfo?buildID=812331

Unfortunately the new new kernel didn't fix the issue [1].

The monitors I tried:
* Philips 190b4cs, 1280 x 1024, using a HDMI to DVI adapter
* Philips V-Line 243V5LSB, 1920 x 1080, using a HDMI to DVI adapter
* LG 34UC88-B, 3440 x 1440, connected directly to HDMI input

My current workaround is just to blacklist vc4 (if that can help someone):
echo blacklist vc4 > /etc/modprobe.d/blacklist-vc4.conf

Sylvain

[1] https://paste.fedoraproject.org/460935/77421958/
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedor

[Richard Ryniker]

Post by Sylvain Pasche
echo blacklist vc4 > /etc/modprobe.d/blacklist-vc4.conf

That gives me a console on my RPi3, eliminates the "i2c-bcm2835
3f805000.i2c: i2c transfer failed: 100" messages from syslog, and even
permits X to start (I executed xinit by non-privileged user, ran emacs
and gkrellm), but graphical.target has problems and software rendering is
certainly undesirable.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send

[Richard Ryniker]

Bruce Jerrick filed this as: https://bugzilla.redhat.com/show_bug.cgi?id=1387733
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.f