Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1624750 - RPi3 serial console unusable
Summary: RPi3 serial console unusable
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 29
Hardware: armv7hl
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2018-09-03 08:11 UTC by Alessio
Modified: 2018-09-04 10:15 UTC (History)
20 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 10:15:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
This is the moment when strange characters start to appear. (154.85 KB, image/png)
2018-09-04 07:30 UTC, Alessio 		no flags Details
Initial setup (112.96 KB, image/png)
2018-09-04 07:46 UTC, Alessio 		no flags Details
config.txt (1.15 KB, text/plain)
2018-09-04 07:48 UTC, Alessio 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.