[Kernel-packages] [Bug 2084945] Re: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image
@Talha this issue is similar or identical with the one I reported with the previous image AFTER installing the Ubuntu Desktop package. I can also reproduce the same issue that Sagar highlighted on my kv260 board with the x04 image. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2084945 Title: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: I booted latest Ubuntu 24.04 Image drop https://oem- share.canonical.com/partners/limerick/share/kria-24.04/classic-24.04-x04/ on KR260 with Ethernet Cable connected to GEM0 PS ethernet(top - eth1) connected to DHCP address. At first boot, it does not get a DHCP address. When I swap the ethernet cable from GEM0 PS to GEM1 PS(bottom eth0), eth0 gets a DHCP address. Keeping the cable connected, if I issue a "sudo reboot", this time around eth0 also does not get an IP and when I swap the cable again to eth1, it gets an IP. Issue here is that IP address is not persistent across reboots. Similar is observed on KV260. Workaround is as follows: 1. Initial ifconfig ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet6 fe80::3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 20 bytes 3286 (3.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7 bytes 630 (630.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 404 bytes 28928 (28.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 404 bytes 28928 (28.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 2. On every boot run the following to get the uuid of the connected eth port ubuntu@kria:~$ nmcli connection show NAMEUUID TYPE DEVICE eth163b15f62-c30a-4ed4-a52e-8e7656587990 ethernet eth1 lo 82707ca4-9673-4854-a692-b8e1478832a1 loopback lo 3. Copy the uuid value for eth1(I have cable connected to GEM0 PS) and run the following ubuntu@kria:~$ sudo nmcli connection down 63b15f62-c30a-4ed4-a52e-8e7656587990 [sudo] password for ubuntu: Connection 'eth1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) 4. Run ifconfig to get an IP on eth1 ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet 10.0.0.73 netmask 255.255.255.0 broadcast 10.0.0.255 inet6 2601:647:4200:6870::1ba1 prefixlen 128 scopeid 0x0 inet6 fe80::a1b7:248d:f617:c55b prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:1c7:5ea4:d982:8f1f prefixlen 64 scopeid 0x0 inet6 2601:647:4200:6870:98aa:48c3:fb1:395c prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 79 bytes 11997 (11.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 5964 (5.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 732 bytes 52396 (52.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 732 bytes 52396 (52.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2084945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpa
[Kernel-packages] [Bug 2084945] Re: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image
@Luca this is the bug where I brought up a similar issue before: https://bugs.launchpad.net/limerick/+bug/2063225 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2084945 Title: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: I booted latest Ubuntu 24.04 Image drop https://oem- share.canonical.com/partners/limerick/share/kria-24.04/classic-24.04-x04/ on KR260 with Ethernet Cable connected to GEM0 PS ethernet(top - eth1) connected to DHCP address. At first boot, it does not get a DHCP address. When I swap the ethernet cable from GEM0 PS to GEM1 PS(bottom eth0), eth0 gets a DHCP address. Keeping the cable connected, if I issue a "sudo reboot", this time around eth0 also does not get an IP and when I swap the cable again to eth1, it gets an IP. Issue here is that IP address is not persistent across reboots. Similar is observed on KV260. Workaround is as follows: 1. Initial ifconfig ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet6 fe80::3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 20 bytes 3286 (3.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7 bytes 630 (630.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 404 bytes 28928 (28.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 404 bytes 28928 (28.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 2. On every boot run the following to get the uuid of the connected eth port ubuntu@kria:~$ nmcli connection show NAMEUUID TYPE DEVICE eth163b15f62-c30a-4ed4-a52e-8e7656587990 ethernet eth1 lo 82707ca4-9673-4854-a692-b8e1478832a1 loopback lo 3. Copy the uuid value for eth1(I have cable connected to GEM0 PS) and run the following ubuntu@kria:~$ sudo nmcli connection down 63b15f62-c30a-4ed4-a52e-8e7656587990 [sudo] password for ubuntu: Connection 'eth1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) 4. Run ifconfig to get an IP on eth1 ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet 10.0.0.73 netmask 255.255.255.0 broadcast 10.0.0.255 inet6 2601:647:4200:6870::1ba1 prefixlen 128 scopeid 0x0 inet6 fe80::a1b7:248d:f617:c55b prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:1c7:5ea4:d982:8f1f prefixlen 64 scopeid 0x0 inet6 2601:647:4200:6870:98aa:48c3:fb1:395c prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 79 bytes 11997 (11.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 5964 (5.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 732 bytes 52396 (52.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 732 bytes 52396 (52.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2084945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2084945] Re: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image
@Luca Also, i believe this was supposed to be filed under limerick, not sure if it can be moved over or if it matters... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2084945 Title: PS Ethernet does not get a DHCP address at boot with latest Ubuntu 24.04 Image Status in linux-xilinx-zynqmp package in Ubuntu: New Bug description: I booted latest Ubuntu 24.04 Image drop https://oem- share.canonical.com/partners/limerick/share/kria-24.04/classic-24.04-x04/ on KR260 with Ethernet Cable connected to GEM0 PS ethernet(top - eth1) connected to DHCP address. At first boot, it does not get a DHCP address. When I swap the ethernet cable from GEM0 PS to GEM1 PS(bottom eth0), eth0 gets a DHCP address. Keeping the cable connected, if I issue a "sudo reboot", this time around eth0 also does not get an IP and when I swap the cable again to eth1, it gets an IP. Issue here is that IP address is not persistent across reboots. Similar is observed on KV260. Workaround is as follows: 1. Initial ifconfig ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet6 fe80::3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:3864:9bff:fe9e:1b6d prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 20 bytes 3286 (3.2 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 7 bytes 630 (630.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 404 bytes 28928 (28.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 404 bytes 28928 (28.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 2. On every boot run the following to get the uuid of the connected eth port ubuntu@kria:~$ nmcli connection show NAMEUUID TYPE DEVICE eth163b15f62-c30a-4ed4-a52e-8e7656587990 ethernet eth1 lo 82707ca4-9673-4854-a692-b8e1478832a1 loopback lo 3. Copy the uuid value for eth1(I have cable connected to GEM0 PS) and run the following ubuntu@kria:~$ sudo nmcli connection down 63b15f62-c30a-4ed4-a52e-8e7656587990 [sudo] password for ubuntu: Connection 'eth1' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/2) 4. Run ifconfig to get an IP on eth1 ubuntu@kria:~$ ifconfig eth0: flags=4099 mtu 1500 ether 00:0a:35:10:37:f9 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 42 eth1: flags=4163 mtu 1500 inet 10.0.0.73 netmask 255.255.255.0 broadcast 10.0.0.255 inet6 2601:647:4200:6870::1ba1 prefixlen 128 scopeid 0x0 inet6 fe80::a1b7:248d:f617:c55b prefixlen 64 scopeid 0x20 inet6 2601:647:4200:6870:1c7:5ea4:d982:8f1f prefixlen 64 scopeid 0x0 inet6 2601:647:4200:6870:98aa:48c3:fb1:395c prefixlen 64 scopeid 0x0 ether 3a:64:9b:9e:1b:6d txqueuelen 1000 (Ethernet) RX packets 79 bytes 11997 (11.9 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 51 bytes 5964 (5.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 41 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 732 bytes 52396 (52.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 732 bytes 52396 (52.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2084945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2083466] Re: xilinx-tsn: fix ptp sync failure
@Luca, @Portia I assume this verification action item is on us. Please confirm. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu. https://bugs.launchpad.net/bugs/2083466 Title: xilinx-tsn: fix ptp sync failure Status in linux-xilinx-zynqmp package in Ubuntu: Fix Committed Status in linux-xilinx-zynqmp source package in Noble: Fix Committed Bug description: Please pick up the following tsn driver patch which fixes the ptp feature required for the kr260 and kd240 tsn app: https://github.com/Xilinx/linux- xlnx/commit/24f6801ff536cd674269fd9d6e560160b0aa5f04 this patch is needed due to changes in kernel and user-space going from 22.04 to 24.04. --- External link: https://warthogs.atlassian.net/browse/PEL-1115 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-xilinx-zynqmp/+bug/2083466/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
