Also tested under armhf and arm64 on Raspberry Pi models 3B, 3A+, and
3B+. Results are the same as for bdmurray's tests with armhf on the 3B
above.
My initial suspicion was that this was related to the wifi chipset used
on the 3B (the BCM43430) to the 4B (the BCM43455). However, given the
3A+ and 3B+ also use the BCM43455 (same as the 4B) it's definitely not
that.
Given that the only error ("DHCP4 CLIENT: Failed to attach event...")
occurred in systemd-networkd I attempted to downgrade from version 245.2
to 244.3 (the prior release on Ubuntu). This fixes the issue on the 3B
and 3A+ under armhf and arm64 (I skipped checking the 3B+ for time at
this point).
At this point I'm reasonably confident it's an issue in systemd
introduced sometime between 244.3 and 245.2 - and that it may be timing
sensitive given that the 4B (which is significantly faster than the 3,
3A+ or 3B+) doesn't show the same symptoms but shares a wifi chipset
with the 3A+ and 3B+.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1870410
Title:
wireless does not work on boot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1870410/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
