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
>
>You're using a custom kernel, right? Please check
On Mi, 23.09.20 18:25, Michael Olbrich (m.olbr...@pengutronix.de) wrote:
> 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
>
> You're using a custom kernel, right? Please
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
You're using a custom kernel, right? Please check the README in the systemd
source tree. Specifically the kernel config
I find that boot with the 'rescue' option, then exit 'rescue' mode, then I can
login to the ttyPS0, as below
bash-4.4# exit // *here exit rescue mode*
exit
Reloading system manager configuration
Starting default target
[ 1708.91] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[
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
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
On Wed, Sep 23, 2020, 09:21 ZhouPeng wrote:
>
> Thank you very much for you great suggestions.
>
> I chroot the rootfs and tried to the 3 methods in '/usr/lib/udev/rules.d'
> respectively:
>
> try 1) add a line of ACTION!="remove", KERNEL=="ttyPS0", TAG+="systemd"
> below the line of
Thank you very much for you great suggestions.
I chroot the rootfs and tried to the 3 methods in '/usr/lib/udev/rules.d'
respectively:
try 1) add a line of ACTION!="remove", KERNEL=="ttyPS0", TAG+="systemd" below
the line of "ACTION=="remove", GOTO="systemd_end"" in file 99-systemd.rules
On Di, 22.09.20 15:34, Andrei Borzenkov (arvidj...@gmail.com) wrote:
65;6003;1c
> On Tue, Sep 22, 2020 at 2:53 PM Mantas Mikulėnas wrote:
> >
> > On Tue, Sep 22, 2020 at 1:46 PM Andrei Borzenkov
> > wrote:
> >>
> >> On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
> >> >
> >> > Hi all,
> >> >
>
On Tue, Sep 22, 2020 at 2:53 PM Mantas Mikulėnas wrote:
>
> On Tue, Sep 22, 2020 at 1:46 PM Andrei Borzenkov wrote:
>>
>> On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
>> >
>> > Hi all,
>> >
>> > When I use Fedora image as rootfs on Xilinx PYNQ-Z2, I encountered the
>> > issue when use the
On Tue, Sep 22, 2020 at 1:46 PM Andrei Borzenkov
wrote:
> On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
> >
> > 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
On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
>
> 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
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
12 matches
Mail list logo
