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.
Have you enabled the uart in config.txt?
(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.
Created attachment 1480680 [details] This is the moment when strange characters start to appear.
Please provide the contents of config.txt
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.
(In reply to Peter Robinson from comment #4) > Please provide the contents of config.txt It is the default config.txt
Created attachment 1480685 [details] config.txt This is the config.txt I didn't change it
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
(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
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.