Bug 1624750

Summary:

RPi3 serial console unusable

Product:

[Fedora] Fedora

Reporter:

Alessio <alciregi>

Component:

kernel

Assignee:

Kernel Maintainer List <kernel-maint>

Status:

CLOSED NOTABUG

QA Contact:

Fedora Extras Quality Assurance <extras-qa>

Severity:

unspecified

Docs Contact:

Priority:

unspecified

Version:

CC:

airlied, alciregi, bskeggs, dracut-maint-list, ewk, hdegoede, ichavero, itamar, jarodwilson, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, mchehab, mjg59, pbrobinson, steved, zbyszek

Target Milestone:

---

Target Release:

---

Hardware:

armv7hl

OS:

Unspecified

Whiteboard:

Fixed In Version:

Doc Type:

If docs needed, set a value

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2018-09-04 10:15:45 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Bug Depends On:

Bug Blocks:

245418

Attachments:

Description	Flags
This is the moment when strange characters start to appear.	none
Initial setup	none
config.txt	none

Description Alessio 2018-09-03 08:11:38 UTC

Description of problem:

Starting Fedora-Minimal-armhfp-29-20180901.n.0 the strange character are printed over the serial connection, like the baud rate is incorrect.
Using the same baud rate (115200), parity (8) and so on using F28 works.
I tried to use various baud rates, but it seems that this is not the problem.

Comment 1 Peter Robinson 2018-09-03 20:00:53 UTC

Have you enabled the uart in config.txt?

Comment 2 Alessio 2018-09-04 07:28:40 UTC

(In reply to Peter Robinson from comment #1)
> Have you enabled the uart in config.txt?

Actually, I didn't change anything. Serial connection in F28 works out of the box without having to enable it in config.txt, as well as in F29, isn't it?

The only difference is that, as far as I can see, at some point early in the boot process, strange characters start to appear on the serial terminal.

Comment 3 Alessio 2018-09-04 07:30:05 UTC

Created attachment 1480680 [details]
This is the moment when strange characters start to appear.

Comment 4 Peter Robinson 2018-09-04 07:45:14 UTC

Please provide the contents of config.txt

Comment 5 Alessio 2018-09-04 07:46:53 UTC

Created attachment 1480684 [details]
Initial setup

This is a screenshot of the initial setup.
Some strings are ok. 
Pressing "r" you can see the result.

Comment 6 Alessio 2018-09-04 07:48:04 UTC

(In reply to Peter Robinson from comment #4)
> Please provide the contents of config.txt

It is the default config.txt

Comment 7 Alessio 2018-09-04 07:48:51 UTC

Created attachment 1480685 [details]
config.txt

This is the config.txt
I didn't change it

Comment 8 Peter Robinson 2018-09-04 07:52:08 UTC

How did you write out the image? Did you add --adconsole to the cmd line?

If not you need to follow the details in the FAQ to properly enable the UART. 

https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi?rd=Raspberry_Pi#How_do_I_use_a_serial_console.3F

Comment 9 Alessio 2018-09-04 07:59:25 UTC

(In reply to Peter Robinson from comment #8)
> How did you write out the image? Did you add --adconsole to the cmd line?
> 
> If not you need to follow the details in the FAQ to properly enable the
> UART. 


You are right :-) Now it works.

As said, in F28 serial connection works out of the box without specifying --addconsole to arm-image-installer (or enabling it as for the FAQ), this is the reason why I opened this bug.

Thanks

Comment 10 Peter Robinson 2018-09-04 10:15:45 UTC

well the official supported method is you have to enable it in config.txt. U-Boot attempts to do some intelligence but the firmware is closed so we have the process for a reason. It might work other ways but we can't support it as such like that a the firmware is closed.