Thanks all,
At 2020-09-24 00:25:44, "Michael Olbrich" wrote:
>Hi,
>
>On Wed, Sep 23, 2020 at 04:58:57PM +0800, ZhouPeng wrote:
>> I find that boot with the 'rescue' option, then exit 'rescue' mode, then
>> I can login to the ttyPS0, as below
&
ut how boot directly normally.
Thanks all,
At 2020-09-23 16:37:48, "ZhouPeng" wrote:
>Thank you very much. ' udevadm info -a /dev/ttyPS0' output:
>
>
>bash-4.4# udevadm info -a /dev/ttyPS0
>
>Udevadm info starts with the device specified by the devpath and then
=="(null)"
looking at parent device '/devices/platform':
KERNELS=="platform"
SUBSYSTEMS==""
DRIVERS==""
bash-4.4# ls /dev/ttyPS0 -lh
crw-rw 1 root dialout 254, 0 Jan 28 16:05 /dev/ttyPS0
Thanks,
On Wed, Sep 23, 2020, 15:34，&q
something
like 'mknod /dev/ttyPS0 c 248 0' for systemd or udev pls? If needed, where is
the proper place to add this action pls?
>What does "udevadm info -a /dev/ttyPS0" output?
I can not get a console from ttyPS0, so I can not run "udevadm info -a
/dev/ttyPS0" in
Hi all,
When I use Fedora image as rootfs on Xilinx PYNQ-Z2, I encountered the issue
when use the /dev/ttyPS0.
I think the issue is because systemd and udev on fedora can didn't detect
ttyPS0 properly. Do I need to install any other package or do some special
configuration?
**systemd version
