[fedora-arm] Unable to see 'Initial setup wizard' on Raspberry PI 3 using aarch64 images

[Ashwin Rao]

Hi,

When running the aarch64 Workstation, Server, and Minimal images I am not able to see the initial setup wizard. I can see the messages shown during boot but after some time the screen either starts to flicker or just blanks out. I tried this on 3 different raspberry Pis with different cards and the result is always the same.
The steps I followed are
1. I downloaded the aarch64 images from [ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_3_aarch64_support ] and followed the instructions mentioned on the same web page to prepare the images using xzcat.
2. I connect the HDMI cable of my monitor, and connect the keyboard and mouse. I am not connecting an Ethernet cable.
3. I can see the boot screen, and the messages showing that the device is booting.
4. After some time the screen either blanks out or starts to flicker. I have tried it with different monitors and different power supplies as well but the result is the same. I noticed that the red LED of the Raspberry Pi also starts to blink abruptly.

I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I doubt there is an issue with the card, the power supply, or with the Pis.

It would be nice if someone suggests the things I need to do, or if someone was able to troubleshoot similar issues.

Regards,
Ashwin
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to ar

[Peter Robinson]

Post by Ashwin Rao
Hi,
When running the aarch64 Workstation, Server, and Minimal images I am not able to see the initial setup wizard. I can see the messages shown during boot but after some time the screen either starts to flicker or just blanks out. I tried this on 3 different raspberry Pis with different cards and the result is always the same.
The steps I followed are
1. I downloaded the aarch64 images from [ https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_3_aarch64_support ] and followed the instructions mentioned on the same web page to prepare the images using xzcat.
2. I connect the HDMI cable of my monitor, and connect the keyboard and mouse. I am not connecting an Ethernet cable.
3. I can see the boot screen, and the messages showing that the device is booting.
4. After some time the screen either blanks out or starts to flicker. I have tried it with different monitors and different power supplies as well but the result is the same. I noticed that the red LED of the Raspberry Pi also starts to blink abruptly.
I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I doubt there is an issue with the card, the power supply, or with the Pis.
It would be nice if someone suggests the things I need to do, or if someone was able to troubleshoot similar issues.

The problem is with either the monitor or the HDMI cable, the VC4 open
driver (which neither of the other distros use yet) can be a bit
fragile with some EDID responses from some monitors or cables (yes
we've had people with issues that were fixed when they swapped the
HDMI cable). It's improved a lot since F-25 when we first started
supporting the RPi but it's not perfect yet.

On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't laoded on boot. This can be done by
adding blacklist=vc4 to the kernel command line or creating a file
/etc/modprobe.conf/vc4.conf with the line "blacklist vc4"

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

[Ashwin Rao]

Post by Ashwin Rao

Post by Ashwin Rao
Hi,
When running the aarch64 Workstation, Server, and Minimal images I am

not able to see the initial setup wizard. I can see the messages shown
during boot but after some time the screen either starts to flicker or
just blanks out. I tried this on 3 different raspberry Pis with different
cards and the result is always the same.

Post by Ashwin Rao
The steps I followed are
1. I downloaded the aarch64 images from [ https://fedoraproject.org/

wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_3_aarch64_support ] and
followed the instructions mentioned on the same web page to prepare the
images using xzcat.

Post by Ashwin Rao
2. I connect the HDMI cable of my monitor, and connect the keyboard and

mouse. I am not connecting an Ethernet cable.

Post by Ashwin Rao
3. I can see the boot screen, and the messages showing that the device

is booting.

Post by Ashwin Rao
4. After some time the screen either blanks out or starts to flicker. I

have tried it with different monitors and different power supplies as well
but the result is the same. I noticed that the red LED of the Raspberry Pi
also starts to blink abruptly.

Post by Ashwin Rao
I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I

doubt there is an issue with the card, the power supply, or with the Pis.

Post by Ashwin Rao
It would be nice if someone suggests the things I need to do, or if

someone was able to troubleshoot similar issues.
The problem is with either the monitor or the HDMI cable, the VC4 open
driver (which neither of the other distros use yet) can be a bit
fragile with some EDID responses from some monitors or cables (yes
we've had people with issues that were fixed when they swapped the
HDMI cable). It's improved a lot since F-25 when we first started
supporting the RPi but it's not perfect yet.
On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't laoded on boot. This can be done by
adding blacklist=vc4 to the kernel command line or creating a file
/etc/modprobe.conf/vc4.conf with the line "blacklist vc4"
Thank you for the suggestion. I currently do not need the graphical

interface, so I tried again with the Server image.
Adding module_blacklist=vc4 instead of blacklist=vc4 to the kernel command
line allowed me to get to the login prompt.
-- Ashwin

[Peter Robinson]

On Wed, Nov 22, 2017 at 12:58 PM, Ashwin Rao

Post by Ashwin Rao

Post by Peter Robinson

Post by Ashwin Rao
Hi,
When running the aarch64 Workstation, Server, and Minimal images I am
not able to see the initial setup wizard. I can see the messages shown
during boot but after some time the screen either starts to flicker or just
blanks out. I tried this on 3 different raspberry Pis with different cards
and the result is always the same.
The steps I followed are
1. I downloaded the aarch64 images from [
https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#Raspberry_Pi_3_aarch64_support
] and followed the instructions mentioned on the same web page to prepare
the images using xzcat.
2. I connect the HDMI cable of my monitor, and connect the keyboard and
mouse. I am not connecting an Ethernet cable.
3. I can see the boot screen, and the messages showing that the device is booting.
4. After some time the screen either blanks out or starts to flicker. I
have tried it with different monitors and different power supplies as well
but the result is the same. I noticed that the red LED of the Raspberry Pi
also starts to blink abruptly.
I am able to use Raspbian and OpenSuse using the same Raspberry Pis so I
doubt there is an issue with the card, the power supply, or with the Pis.
It would be nice if someone suggests the things I need to do, or if
someone was able to troubleshoot similar issues.

The problem is with either the monitor or the HDMI cable, the VC4 open
driver (which neither of the other distros use yet) can be a bit
fragile with some EDID responses from some monitors or cables (yes
we've had people with issues that were fixed when they swapped the
HDMI cable). It's improved a lot since F-25 when we first started
supporting the RPi but it's not perfect yet.
On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't laoded on boot. This can be done by
adding blacklist=vc4 to the kernel command line or creating a file
/etc/modprobe.conf/vc4.conf with the line "blacklist vc4"

Thank you for the suggestion. I currently do not need the graphical
interface, so I tried again with the Server image.
Adding module_blacklist=vc4 instead of blacklist=vc4 to the kernel command
line allowed me to get to the login prompt.

Yep, sorry, was replying on my mobile from memory and didn't have the
exact details to hand for the kernel cmd line :-/
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedorapro

[R P Herrold]

Post by Ashwin Rao

Post by Peter Robinson
On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't loaded on boot. This
can be done by ...

Adding module_blacklist=vc4 instead of blacklist=vc4 to the kernel command
line allowed me to get to the login prompt.

Would a more general solution be to add:
video=640x480

to the kernel command line, to try to wrestle the video
choices down into something low-res enough that a GUI install
is prevented from being offered?

-- Russ herrold
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to arm-***@lists.fedora

[Peter Robinson]

Post by R P Herrold

Post by Ashwin Rao

Post by Peter Robinson
On the case of Server and Minimal if you never want to use a graphical
interface and are happy with just the text console you can add a
blacklist so the GPU driver isn't loaded on boot. This
can be done by ...

Adding module_blacklist=vc4 instead of blacklist=vc4 to the kernel command
line allowed me to get to the login prompt.

video=640x480
to the kernel command line, to try to wrestle the video
choices down into something low-res enough that a GUI install
is prevented from being offered?

I don't see how that helps those people, which these days appear to be
the majority, who's monitors don't have any issues what so ever with
the display output.
_______________________________________________
arm mailing list -- ***@lists.fedoraproject.org
To unsubscribe send an email to ar