I'm trying to create a petalinux image using the petalinux SDK. After I start a build I get an error when the process tries to build the system.dtb The error is "(phandle references): Reference to non-existent node or label "ps7_scugic_0" - which is relayed twice. I believe this is some sort of interrupt device used in the ZYNQ SoC and is visible and mapped in the xml file used to generate parts of this build. How can I create this node? Do I have to edit the dts and dtsi files?

I am working on petalinux, Linux for xilinx FPGAs. The source code is here This Linux is having 3.x kernel, and I have been asked to change the kernel to some earlier release version. What are the general steps for replacing the kernel? I have downloaded an eralier version form kernel.org. What is the next step?

I have a Petalinux board (a Trenz Electronic with an AMD/Xilinx Zynq UltraScale+ MPSoC) which boots up with a wrong network connection config (no DHCP). It has no configs in /etc:

$ ls /etc/NetworkManager/system-connections/
$

After configuring the connection with sudo nmcli con mod eth0 ... it works fine. (I modify the ipv4 and ipv6 config, like [here on stackoverflow](https://stackoverflow.com/questions/60654764/switch-from-static-ip-to-dhcp-using-nmcli/60668424#60668424).) And it creates a permanent config file in /etc:

/etc/NetworkManager/system-connections/eth0.nmconnection

But, after a reboot NetworkManager creates a new /run config, which somehow takes precedence over my connection in /etc:

$ nmcli -f TYPE,FILENAME,UUID,NAME,DEVICE connection
TYPE      FILENAME                                                  UUID                                  NAME  DEVICE 
ethernet  /run/NetworkManager/system-connections/eth0.nmconnection  99e39a32-c0ab-4b3f-be16-75a9bdff1277  eth0  eth0   
loopback  /run/NetworkManager/system-connections/lo.nmconnection    5d84c484-4214-47e4-8f00-01f7730200b3  lo    lo     
ethernet  /etc/NetworkManager/system-connections/eth0.nmconnection  fb365147-6ad9-47a0-a5c8-fbea10080ece  eth0  --

Here, the rogue 99e39a32 from /run got connected to the eth0 device, and my /etc connection config fb365147 stays idle. How to correctly and permanently save a connection config in NetworkManager, or make it use /etc config as the only template for the eth0 connection? Where does it even get the configs for /run? How come it does not use /etc to create /run configs? There are posts saying the NetworkManager creates connections per user. I.e. the suggestion was something like /etc is root and somehow other connections get used for my user. But I don't think that's the case here. nmcli does not let me modify a connection without root permissions. There is a number of similar questions on the internet: (https://unix.stackexchange.com/questions/501260/where-does-network-manager-store-settings) (I don't have /etc/netplan file which is mentioned in a comment there), (https://stackoverflow.com/questions/77558991/how-to-stop-network-manager-creating-connections-under-run-networkmanager-syste) , (https://superuser.com/questions/1404124/how-do-i-make-persistent-changes-with-nmcli-in-non-interactive-mode) . But they don't help in my case. **Update:** There is some info how the /run config comes about thanks to the log journalctl -u NetworkManager after booting the computer with [loggin] level=TRACE in /etc/NetworkManager/NetworkManager.conf:

NetworkManager:   [1734374462.9312] device (eth0): carrier: link connected
NetworkManager:  [1734374462.9313] ethtool: ETHTOOL_GSET, eth0: success
NetworkManager:  [1734374462.9317] device[e5c0e28febbc1b13] (eth0): unmanaged: flags set to [platform-init,!user-settings=0x4/0x14/unmanaged/unrealized], set-managed [user-settings=0x10])
NetworkManager:  [1734374462.9318] device[e5c0e28febbc1b13] (eth0): unmanaged: flags set to [!platform-init,!user-settings=0x0/0x14/managed/unrealized], set-managed [platform-init=0x4])
NetworkManager:  [1734374462.9318] device[e5c0e28febbc1b13] (eth0): unmanaged: flags set to [!sleeping,!platform-init,!user-settings=0x0/0x15/managed/unrealized], set-managed [sleeping=0x1])
NetworkManager:  [1734374462.9319] dbus-object[e5c0e28febbc1b13]: export: "/org/freedesktop/NetworkManager/Devices/2"

NetworkManager:   [1734374462.9329] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
NetworkManager:  [1734374462.9349] settings: auto-default: cannot create auto-default connection for device eth0: already has a profile
 [1734374462.9356] Connection 'eth0' differs from candidate 'eth0' in ipv4.addresses, ipv4.gateway, ipv4.method
NetworkManager:  [1734374462.9357] manager: (eth0): assume: generated connection 'eth0' (b807ebb2-d7a5-4b26-82c1-c321a6e7d5ba)
NetworkManager:  [1734374462.9357] device[e5c0e28febbc1b13] (eth0): assume-state: set guess-assume=0, connection=(null)
NetworkManager:  [1734374462.9370] keyfile: commit: b807ebb2-d7a5-4b26-82c1-c321a6e7d5ba (eth0) added as "/run/NetworkManager/system-connections/eth0.nmconnection" (nm-generated,volatile,external)

I guess the question now is what it means by Connection 'eth0' differs from candidate 'eth0' ... - what is that candidate? I.e. probably there is some more config for the eth0 device itself, and when the /etc config conflicts with that one, NetworkManager creates a new one? I tried adding this file with no change in the behavior (it's probably deprecated):

$ cat /etc/network/interfaces
auto eth0
iface eth0 inet dhcp

**Update 2:** Just to point out, I have tried adding no-auto-default config, but it made no difference in this case:

/etc/NetworkManager/NetworkManager.conf

[main]
no-auto-default=*
# or no-auto-default=eth0

And adding the connection in /etc/network/interfaces also did not help:

# Wired interfaces
auto eth0
iface eth0 inet dhcp
	hwaddress ether

I think, as @telcoM suggested, it is a Petalinux-specific behavior. You define the settings for the eth0 device when the image is built (and apparently NetworkManager can somehow read settings from the device or what?), and [you cannot modify ethernet settings in Petalinux after the image has been built](https://adaptivesupport.amd.com/s/question/0D54U000089gXtiSAE/how-can-i-change-the-network-ip-address-in-the-running-petalinux-on-zynq-mpsoc?language=en_US) . Probably, there is nothing that you can modify in uboot ZynqMP> console either. So, what I ended up doing is: [rename my connection](https://wrightrocket.blogspot.com/2018/11/network-manager-nmcli.html) to eth0dhcp and add a systemd unit that connects it after the boot.

sudo nmcli c mod fb365147-6ad9-47a0-a5c8-fbea10080ece con-name eth0dhcp

The connection config looks like: $ sudo cat /etc/NetworkManager/system-connections/eth0.nmconnection [connection] id=eth0dhcp uuid=fb365147-6ad9-47a0-a5c8-fbea10080ece type=ethernet autoconnect=false interface-name=eth0 timestamp=1734377647 [ethernet] mac-address= [ipv4] method=auto [ipv6] addr-gen-mode=default method=auto [proxy] And the one-shot systemd unit: [Unit] Description=UP the eth0dhcp for eth0 after boot After=network.target Requires=network.target [Service] Type=oneshot RemainAfterExit=yes User=root ExecStart=nmcli con up eth0dhcp SuccessExitStatus=0 Restart=on-failure RestartSec=20 StartLimitInterval=300 StartLimitBurst=5 [Install] WantedBy=multi-user.target It's enough of a workaround in my case. Later we'll just build images with whatever settings that are needed.

I am trying to set up a development environment using QEMU to emulate a Zynq UltraScale+ MPSoC ZCU102. I have a Petalinux image that I am able to run with QEMU and now I want to pass in and mount file system containing an executable and required .so files that I made with mkfs.jffs2. I tried passing several different arguments to QEMU through the petalinux-boot --qemu command, but I have never been able to find the file system after booting into Linux. Arguments I've tried: -drive file=/PATH/TO/JFFS2/FILESYSTEM,format=raw,if=pflash,id=foo,unit=1 -drive file=/PATH/TO/JFFS2/FILESYSTEM,format=raw,if=mtd,id=foo -device loader,file=/PATH/TO/JFFS2/FILESYSTEM,addr=0x4240000 -drive file=/PATH/TO/JFFS2/FILESYSTEM,format=raw,id=foo -device nand,drive=foo I admit that I do not have any real experience with QEMU and my googling lead to the unsuccessful attempts above, so this post may be lacking some important details I am not aware of, if you need any additional information please let me know and I will provide it. Thank you

When i plug in my usb device I get the following errors: usb 1-1: new high-speed USB device number 2 using xhci-hcd usb 1-1: device descriptor read/64, error -71 usb 1-1: device descriptor read/64, error -71 usb 1-1: new high-speed USB device number 3 using xhci-hcd usb 1-1: device descriptor read/64, error -71 usb 1-1: device descriptor read/64, error -71 usb 1-1: new high-speed USB device number 4 using xhci-hcd usb 1-1: Device not responding to setup address. usb 1-1: Device not responding to setup address. usb 1-1: device not accepting address 4, error -71 usb 1-1: new high-speed USB device number 5 using xhci-hcd usb 1-1: Device not responding to setup address. usb 1-1: Device not responding to setup address. usb 1-1: device not accepting address 5, error -71 usb usb1-port1: unable to enumerate USB device NOTE: But when I fatload image.ub from U-boot command line using the following commands : usb start fatload usb 0 0x20000000 image.ub bootm 0x20000000 and don't remove my usb after loading image.ub. It works properly upon boot & i am able to read/write to the device. But after i disconnect and reconnect the usb device i get the same errors -71 as mentioned above. From the following behavior, i noticed : 1) That the usb drivers have been loaded, otherwise the fatloading image.ub from u-boot wouldn't have been possible 2) The process of flashing image.ub is an interaction between the board and usb, which might have initialized something before kernel boots up. Hence the usb works after that. I have configured the system-user.dtsi file with : /include/ "system-conf.dtsi" / { }; &dwc3_0 { dr_mode = "host"; phy-names = "usb3-phy"; }; Also enabled xHCI HCD(3.0) USB Mass storage support Designware USB3 DWC mode -> Dual Role mode using petalinux-config -c kernel . Edit: Since it is a custom board, i can tell u that, we are using Zynq UltraScale+ MPSoC. And I have attached Startup logs and device tree for more information. system.dts & startup-logs

I made a petalinux project with Xilinx 2018.3 sdk environment. I built my project upon a zcu102 Xilinx board, and a PCIe card attached to that board. I debug my code for some time without error, until it crashes. it happens after I run external simulator that send data to the pci card. see the photo. I get endless massages: > [ 1845.777165] nwl-pcie fd0e0000.pcie: Non-Fatal Error Detected The error is running on my console continuously and by that time sdk [eclipse] is also stuck and I need to power cycle the board. What does this error mean? I will provide more details if necessary. Can you suggest a way to debug this error and get to the root cause?

I'm looking for ideas to get over this hurdle. I have a linux kernel module that takes in high rate data from the PL side of a Xilinx Zynq MPSOC device. The kernel module is based off dma-proxy example (https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/1027702787/Linux+DMA+From+User+Space+2.0) but i modified it slightly to to only use one buffer. Our DMA implemenation uses a single channel, Rx only, non scatter gather implementation of the IP. I am moving the data to the dmam_alloc_coherent memory space just fine within the driver. However, when i map to this same space (as in the example driver) I cannot write this data to the userspace file that has been opened with the O_DIRECT option. When i attempt to do so, the write() call perrors out with "bad address". I can however write to the file directly without the O_DIRECT option just fine. However as this data rate is far too low for the incoming data from the PL. The next thing i tried was to do a second copy from the dmam_alloc_coherent() memory area to a userspace posix_memalign(512) allocated area, then in turn write the data to the O_DIRECT opened file. This dramatically increased performand by about 5x. But its still not as fast as it could be. Scenerio Performance Summary of my code... (kernel)dmam_alloc_coherent() -> (userspace)file(O_DIRECT) = "bad address" (kernel)dmam_alloc_coherent() -> (userspace)file() = 272 MB/second (kernel)dmam_alloc_coherent() -> (userspace)posix_memalign(512) -> (userspace)file(O_DIRECT) = 1323 MB/second (userspace)posix_memalign(512) -> (userspace)file(O_DIRECT) = 2200 MB/sec (no actual PL data, just dumping memcontents to disk) I believe if i can find a way to get this to work without performing a second copy to posix_memalign area, I should be close to 2000 MB/sec. My actual target rate is 1600 MB/sec. Does anyone have any clue how i can perform this without the second copy? How do i set up the dma memory to allow reading from and writeing to O_DIRECT file without the intermediate copy? lol i believe this is called zero copy .... Thanks in advance for all your help on this, i've been banging my head against the wall for a while on it.... Cheers! PS. Other info.... MPSOC setup: Petalinux on MPSOC development board with 2 NVME drives configured in a ext4 LVM stripe setup. other dd testing to disk: 1.dd if=/dev/zero of=tt/test.bin bs=20M count=50 50+0 records in 50+0 records out 1048576000 bytes (1.0 GB, 1000 MiB) copied, 4.37955 s, 239 MB/s 2.dd if=/dev/zero of=tt/test.bin bs=20M count=50 oflag=direct 50+0 records in 50+0 records out 1048576000 bytes (1.0 GB, 1000 MiB) copied, 0.489777 s, 2.1 GB/s 3.dd if=/dev/zero of=tt/test.bin bs=30M count=1000 oflag=direct 1000+0 records in 1000+0 records out 31457280000 bytes (31 GB, 29 GiB) copied, 13.7039 s, 2.3 GB/s

I have a Debian rootfs as a tar file. I would like to specify it as the initramfs source in Kconfig (using PetaLinux), but the source must be a cpio archive. How can I convert the .tar to .cpio, maintaining its structure, permissions, etc.?

I am using PetaLinux (or Yocto) as my systems OS. I built the image and have dnf as my package manager. However, when I try to install something, I get the error message: > Error: There are no enabled repos. So this means, my repo list is empty, I suppose. The question is, I want to be able to just install packages easily without always adding a repo or the url to the repo to install it. So is there some kind of URL I could source or add to my configuration file, where many common packages are linked with repo? I want to be able to just do something like sudo dnf install python3. Is this somehow possible? What do I have to do to get there? Thank you very much in advance! ## Edit ## I tried installing yum on my Ubuntu and then checking the repolist, but it is also empty. Where do I get standard repos from, so I can access many different packages?

Using a Yocto distribution with NetworkManager and NetworkManager-nmcli installed, I am not able to have my wifi wlan0 device leaving the unavailable state. The error message I have is: device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') My question is how could I know which program is managing the device? I uninstalled and removed all sysvinit scripts that could create the network device and still have the same issue. I narrowed it down to the fact that when NetworkManager is started, it creates the wlan0 device and then switches it to unavailable as explained above. This is my /etc/network/interfaces # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback This is my /etc/NetworkManager/NetworkManager.conf [main] plugins=keyfile,ifupdown rc-manager=symlink dns=dnsmasq [ifupdown] managed=true The /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf [keyfile] unmanaged-devices=*,except:type:wifi From my (probably poor) understanding, all these seem fine. I do not get why the wlan0 is still in "unavailable"?? Any help would be greatly appreciated! Thanks **EDIT** Folowing @thaller suggestion, I enabled the trace level log Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6226] platform-linux: do-change-link: success changing link: success Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6227] platform: (wlan0) link: setting hardware address to 02:42:58:70:A1:F9 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6231] platform-linux: do-request-link: 3 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6231] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 0: 3: wlan0 mtu 1500 arp 1 wifi? not-init addrgenmode none addr 02:42:58:70:A1:F9 brd FF:FF:FF:FF: Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6232] platform: (wlan0) signal: link changed: 3: wlan0 mtu 1500 arp 1 wifi? init addrgenmode none addr 02:42:58:70:A1:F9 brd FF:FF:FF:FF:FF:FF driver rtl8821au rx:78, Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6233] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 19: 3: wlan0 mtu 1500 arp 1 wifi? not-init addrgenmode none addr 02:42:58:70:A1:F9 brd FF:FF:FF:FF Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6234] platform-linux: do-change-link: success changing link: success Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6234] device[8ad453a3b5b754fb] (wlan0): hw-addr: hardware address now 02:42:58:70:A1:F9 Mar 10 13:12:33 nclab-kol-2021 daemon.info NetworkManager: [1646917953.6240] device (wlan0): set-hw-addr: set MAC address to 02:42:58:70:A1:F9 (scanning) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6242] device[8ad453a3b5b754fb] (wlan0): bringing up device 3 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6242] platform: (wlan0) link: setting up Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6243] platform-linux: link: change 3: flags: set 0x1/0x1 ([up] / [up]) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6244] platform-linux: do-request-link: 3 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6245] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 0: 3: wlan0 mtu 1500 arp 1 wifi? not-init addrgenmode none addr 02:42:58:70:A1:F Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6245] platform: (wlan0) signal: link changed: 3: wlan0 mtu 1500 arp 1 wifi? init addrgenmode none addr 02:42:58:70:A1:F9 brd FF:FF:FF:FF:FF:FF drive Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6247] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 21: 3: wlan0 mtu 1500 arp 1 wifi? not-init addrgenmode none addr 02:42:58:70:A1: Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6247] platform-linux: do-change-link: success changing link: success Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6248] device[8ad453a3b5b754fb] (wlan0): ip4-config: update (commit=1, new-config=(nil)) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6248] device[8ad453a3b5b754fb] (wlan0): ip4-config: clear IP Config instance (/org/freedesktop/NetworkManager/IP4Config/1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6253] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6255] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6255] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6256] dbus-object[db112265116d3c2f]: unexport: "/org/freedesktop/NetworkManager/IP4Config/1" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6258] device[8ad453a3b5b754fb] (wlan0): ip6-config: update (commit=1, new-config=(nil)) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6259] device[8ad453a3b5b754fb] (wlan0): ip6-config: clear IP Config instance (/org/freedesktop/NetworkManager/IP6Config/1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6263] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6265] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6265] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6266] dbus-object[5827083ac52f43c8]: unexport: "/org/freedesktop/NetworkManager/IP6Config/1" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6285] supplicant: (wlan0): creating new supplicant interface Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6289] device[8ad453a3b5b754fb] (wlan0): add_pending_action (2): 'waiting-for-supplicant' Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6290] device[8ad453a3b5b754fb] (wlan0): device not yet available for transition to DISCONNECTED Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6313] device[8ad453a3b5b754fb] (wlan0): connectivity state changed from UNKNOWN to NONE Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6316] manager: connectivity checking indicates NONE Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6323] dispatcher: (2) dispatching action 'connectivity-change' Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6327] device[8ad453a3b5b754fb] (wlan0): connectivity state changed from UNKNOWN to NONE Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6335] device[8ad453a3b5b754fb] (wlan0): remove_pending_action (1): 'in-state-change' Mar 10 13:12:33 nclab-kol-2021 daemon.info nm-dispatcher: req:2 'connectivity-change': new request (0 scripts) Mar 10 13:12:33 nclab-kol-2021 daemon.debug nm-dispatcher: req:2 'connectivity-change': environment: CONNECTIVITY_STATE=NONE Mar 10 13:12:33 nclab-kol-2021 daemon.debug nm-dispatcher: req:2 'connectivity-change': environment: NM_DISPATCHER_ACTION=connectivity-change Mar 10 13:12:33 nclab-kol-2021 daemon.info nm-dispatcher: req:2 'connectivity-change': completed: no scripts Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6347] create NMVpnManager singleton (6588803e3521b96d) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6347] manager: creating virtual devices... Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6348] setting up local loopback Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6349] platform: (lo) link: setting up Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6349] platform-linux: link: change 1: flags: set 0x1/0x1 ([up] / [up]) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6350] platform-linux: do-request-link: 1 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6352] platform-linux: event-notification: RTM_NEWLINK, flags 0, seq 23: 1: lo mtu 65536 arp 772 loopback? not-init addrgenmode eui64 addr 00:00:00:00:0 Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6353] ethtool: ETHTOOL_GDRVINFO, lo: failed: Operation not supported Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6354] platform-linux: do-change-link: success changing link: success Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6366] firewall: D-Bus name for firewalld has no owner (firewall stopped) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6370] dns-sd-resolved[93c36e7af7f93bfa]: D-Bus name for systemd-resolved has no owner Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6384] dispatcher: (1) succeeded but no scripts invoked Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6390] dispatcher: (2) succeeded but no scripts invoked Mar 10 13:12:33 nclab-kol-2021 daemon.info NetworkManager: [1646917953.6397] ovsdb: Could not connect: No such file or directory Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6398] ovsdb: disconnecting from ovsdb, retry 0 Mar 10 13:12:33 nclab-kol-2021 daemon.info NetworkManager: [1646917953.6399] supplicant: wpa_supplicant stopped Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6402] device[53bb033d9641aa44] (lo): ip4-config: update (commit=0, new-config=0xaaaaf2bb8130) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6402] dbus-object[e01a38d512fcba77]: export: "/org/freedesktop/NetworkManager/IP4Config/2" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6408] device[53bb033d9641aa44] (lo): ip4-config: set IP Config instance (/org/freedesktop/NetworkManager/IP4Config/2) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6418] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6420] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6420] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6422] platform-linux: sysctl: reading '/proc/sys/net/ipv6/conf/lo/disable_ipv6': '0' Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6423] device[53bb033d9641aa44] (lo): ip6-config: update (commit=0, new-config=0xaaaaf2b9f370) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6424] dbus-object[d1948f7b92c13977]: export: "/org/freedesktop/NetworkManager/IP6Config/2" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6429] device[53bb033d9641aa44] (lo): ip6-config: set IP Config instance (/org/freedesktop/NetworkManager/IP6Config/2) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6434] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6436] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6436] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6437] device[c503cba53b9e71c5] (sit0): ip4-config: update (commit=0, new-config=0xaaaaf2bb84c0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6438] dbus-object[db112265116d3c2f]: export: "/org/freedesktop/NetworkManager/IP4Config/3" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6443] device[c503cba53b9e71c5] (sit0): ip4-config: set IP Config instance (/org/freedesktop/NetworkManager/IP4Config/3) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6448] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6450] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6450] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6452] platform-linux: sysctl: reading '/proc/sys/net/ipv6/conf/sit0/disable_ipv6': '0' Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6453] device[c503cba53b9e71c5] (sit0): ip6-config: update (commit=0, new-config=0xaaaaf2b9f7b0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6453] dbus-object[2c07d4e5110af889]: export: "/org/freedesktop/NetworkManager/IP6Config/3" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6457] device[c503cba53b9e71c5] (sit0): ip6-config: set IP Config instance (/org/freedesktop/NetworkManager/IP6Config/3) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6463] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6464] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6465] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6466] device[c1055a26277ac48d] (usb0): ip4-config: update (commit=0, new-config=0xaaaaf2bb85f0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6467] dbus-object[9d6eaa32c97d075e]: export: "/org/freedesktop/NetworkManager/IP4Config/4" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6472] device[c1055a26277ac48d] (usb0): ip4-config: set IP Config instance (/org/freedesktop/NetworkManager/IP4Config/4) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6483] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6485] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6485] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6487] platform-linux: sysctl: reading '/proc/sys/net/ipv6/conf/usb0/disable_ipv6': '0' Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6488] device[c1055a26277ac48d] (usb0): ip6-config: update (commit=0, new-config=0xaaaaf2b9fae0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6489] dbus-object[f2d73358dc9003e5]: export: "/org/freedesktop/NetworkManager/IP6Config/4" Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6495] device[c1055a26277ac48d] (usb0): ip6-config: set IP Config instance (/org/freedesktop/NetworkManager/IP6Config/4) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6501] dns-mgr: (device_ip_config_changed): queueing DNS updates (1) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6502] dns-mgr: (device_ip_config_changed): DNS configuration did not change Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6503] dns-mgr: (device_ip_config_changed): no DNS changes to commit (0) Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6506] manager: (lo): assume: don't assume because not managed Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6507] manager: (sit0): assume: don't assume because not managed Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6507] manager: (usb0): assume: don't assume because not managed Mar 10 13:12:33 nclab-kol-2021 daemon.debug NetworkManager: [1646917953.6508] manager: startup complete is waiting for device 'wlan0' (waiting-for-supplicant) I do not know what really to do with it. It seems that the network manager is creating the device than...

I am trying to ssh/scp from one machine on my network to another. The problem is that when I execute an ssh/scp command (ssh user@ip_machine_2) it is only "working" when I am logged in to the root account on machine_1. When sending this command as root I am prompted for the user' password on machine_2 and then I can access the account/transfer a file without any issues. If I log into the user account on machine_1 and repeat the command I am now getting an error: "Host key verification failed." Does any one have any idea on what could be causing this when not logged into the root account? I checked the permissions for both ssh and scp and they seem fine, so I think the user account might be missing some permissions for something critical in the network stack in order for ssh to work under this account.

i want to do petalinux cross-compilation at ubuntu on vm-ware and offline. so, i downloaded all needed packages and installed them. and then i tried to restart ubuntu. but, unfortunately, ubuntu not run. vm-ware version is 15.x, ubuntu version is 16.04 here, my errors : help me, please. sorry my mistake. this is my install packages list without their dependencies.

iproute2 gcc g++ net-tools libncurses5-dev zlib1g:i386 libssl-dev flex bison libselinux1 xterm autoconf libtool texinfo zlib1g-dev gcc-multilib build-essential screen pax gawk python3 python3-pexpect python3-pip python3-git python3-jinja2 xz-utils debianutils iputils-ping libegl1-mesa libsdl1.2-dev pylint3 cpio chrpath socat tftp tftpd

**Sorry,dear everyone. For this question, i tried and fixed the errors. so, i tried to install one-by-one. And the problem is libdbus-..--.deb package. if it had been installed, system breaked. What is libdbus package's function? and why we use it? if not install, what problem ? if install, why this problem happens? Now, i have not installed it, but not any problem. thanks .**

I'm using Ubuntu 16.04.5, 64 bit. While installing Petalinux (2019.1), I'm getting this error: ./petalinux-v2019.1-final-installer.run ../Petalinux INFO: Checking installation environment requirements... ./petalinux-v2019.1-final-installer.run: line 183: /tmp/tmp.0rr2YrEdc6/petalinux-env-check: cannot execute binary file: Exec format error WARNING: Please install required packages. How can I resolve this Error?

I cross compiled Linux-PAM and OpenLDAP for my linux embedded system (with ARM architecture) and copied the compiled files and folders into it. I create a /etc/pam.d/ folder and i put inside of it the files common-auth, common-password and common-account. How can i make sure it authenticates with PAM? For example from the command line when I digit: su user1 how can I make sure the system authenticate only with passwd or with PAM? This are the files I put inside the /etc/pam.d folder: common-account: account sufficient /usr/lib/security/pam_ldap.so account required /lib/security/pam_unix.so try_first_pass common-auth: auth sufficient /usr/lib/security/pam_ldap.so auth required /lib/security/pam_unix.so nullok_secure try_first_pass common-password: password sufficient /usr/lib/security/pam_ldap.so password required /lib/security/pam_unix.so nullok obscure min=4 max=8 md5 try_first_pass Thanks for your help.

I am using a bash script with the shutdown command to halt my system. I know that shutdown can print a message as an argument. Here's my current command: shutdown -h now "Shutdown complete. You may now unplug the power." However, this prints my message *before* the shutdown command does its thing, and so I see a ton of other messages afterwards, such as "INIT: Sending processes the TERM signal" and "Unmounting local filesystems..." I want to print a final message at the end of the halt, so that the user knows when it is safe to unplug the power. How can I do this? (I am on an embedded system running Petalinux 2019.1.)

I have two devices which uses petalinux as OS. They are custom devices to use on some projects. Their purpose is to act as routers with cabled connection (not ethernet). Devices are connected with cable and with special protocol. So they can not use ethernet interface. I need them to act as a switch. Devices have WEB GUI to configure them. Also they listen some udp sockets and process data. But I also want to transmit all Ethernet packets to other device. So far I tried this : Device 1 IP : 10.0.0.4/24 IP forwarding enable Route 192.168.0.0 via ppp0 Device 2 IP : 192.168.0.5 IP Forwarding enable Route 10.0.0.0 via ppp0 This way devices have a connection and i can transmit packets to other side. But I can not use other IP domains. Both devices need to act as a switch. When I am connected to Device 1's network, I need to access Device 2's WEB GUI. I could not figure out what kind a ip route I should use. What could be the solution?

I am working on RedPitaya FPGA board and want to use Asymmetric MultiProcessing on it. CPU0 will be running Linux and CPU1 will be running Baremetal or freeRTOS. For that I need to change the Kernel Load address so that the application/FreeRTOS running on CPU1 can have access to memory. Does anyone know how to change the Kernel Load address? I believe we will need to make changes in some configuration files, device tree and the address to which u-boot loads the kernel(not sure about this one). I think I can figure our the rest but I am having a hard time figuring out what to change in Kernel Configs or Source. P.S: With PetaLinux SDK its done as described by OpenAMP Framework for Zynq Devices Page 17. I just need to figure out how to do it without using PetaLinux. Cheers. Waqar Rashid

Me and my team are currently working with Yocto and Petalinux Tools ( from Xilinx) to develop a distribution based on the Xilinx Linux kernel. At first glance both look the same and there is little to differentiate between the two(but that could be due to our inexperience) One thing we know is that Petalinux uses packages from Yocto project at its centre and uses it for kernel config and distribution development. So what is it that is so different about them and are there advantages to use either of them ?

I want to try the following things : 1. Modify the booting arguments of u-boot of my Petalinux project which is currently using the Xilinx Kernel. I want to modify it such that it runs DHCP during booting of the u-boot itself to acquire an IP address for itself and the IP for TFTP server from our central IT infrastructure. I know this is possible to do with x86_64 processors running a CentOS grub during the boot process, as thats what systems in our office use. The Wiki page for DHCP also says additional options for acquiring IP address for TFTP server can be added in the DHCP packet. I want to simply try this for ARM processors. This has been mentioned in the following link : https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol 2. As you guessed, along with modification of boot arguments to add DHCP in the boot process, I want to modify the DHCP command script to add the TFTP option (if possible for the Petalinux DHCP) This should essentially look like this , 1. U-boot starts booting 2. It calls DHCP in the process to obtain its own and TFTP server IP from central DHCP server 3. This DHCP command then along with obtaining its own IP also obtains TFTP server IP

For Device Tree Blob it says several boards can use one SoC so the SoC level information is included in board level in order not to be duplicated(DTSI is included in DTS). So 1.What is considered to be BOARD and PLATFORM(difference)? 2. Is there a usable board without any SoC, FPGA or stuff like that? 3. How can several boards be connected to each other? (pins or ..??)