2024-04-29
07:00kaazoo has joined #ubuntu-asahi
07:03kaazootobhe: Hi, you mentioned you created a dummy network device to work around the boot delay. Can you post an example please? My ethernet interface is on a USB-C hub, which seems to not be ready when systemd-networkd expects it.
07:16kaazoo has quit [Quit: Leaving.]
07:19kaazoo has joined #ubuntu-asahi
07:24kaazooMeanwhile, I used "sudo systemctl edit systemd-networkd-wait-online.service" to only wait for loopback interface, which seems to get rid of the delay:
07:33kaazooWhat's strange is that cloud-init seems to have generated /etc/netplan/50-cloud-init.yaml which won't get updated since I disabled cloud-init.
07:36kaazoo has quit [Quit: Leaving.]
07:36kaazoo1 has joined #ubuntu-asahi
07:36kaazoo1 has quit []
07:37tobhe[m]unfortunately I didn't really have a solution. I previously had a custom netplan config to add a dummy interface. deleting that fixed my issues
07:37kaazoo has joined #ubuntu-asahi
07:37kaazoo has quit []
07:38kaazoo has joined #ubuntu-asahi
07:38tobhe[m]but that is on my laptop where i don't really use ethernet. on the m1 mini there doesn't seem to be any issue
07:41kaazooI moved /etc/netplan/50-cloud-init.yaml to a new filename and added "renderer: NetworkManager", like in the other wifi-related yaml files in that directory.
07:41kaazoo has quit []
07:52kaazoo has joined #ubuntu-asahi
07:54kaazooOK, I still see "systemd-networkd[1861]: eth0: Could not process link message: No such device or address" in the logs, but there is no boot delay anymore. The interface is brought up and everything seems to work, so good enough for me now.
08:08tobhe[m]after the latest package update everyone should have a /etc/apt/sources.list.d/ubuntu-asahi.sources which is pinned at 1001 prio and a /etc/update-manager/release-upgrades.d/ubuntu-asahi.cfg that make sure it survives a release upgrade
08:13kaazoo has quit [Quit: Leaving.]
08:15tobhe[m]perfect. something I didn't want to do automatically at this point is removing the old ~tobhe/asahi ppa
08:15tobhe[m]but at this point I expect everything to go through the ~ubuntu-asahi team on launchpad instead
11:01tobhe_ has quit [reticulum.oftc.net helix.oftc.net]
11:01moon127 has quit [reticulum.oftc.net helix.oftc.net]
11:01tobhe[m]1 has quit [reticulum.oftc.net helix.oftc.net]
11:01popey[m] has quit [reticulum.oftc.net helix.oftc.net]
11:01john-cabaj[m] has quit [reticulum.oftc.net helix.oftc.net]
11:01wildwestrom[m] has quit [reticulum.oftc.net helix.oftc.net]
11:03moon127 has joined #ubuntu-asahi
11:03tobhe[m]1 has joined #ubuntu-asahi
11:03john-cabaj[m] has joined #ubuntu-asahi
11:03wildwestrom[m] has joined #ubuntu-asahi
11:03tobhe_ has joined #ubuntu-asahi
11:03popey[m] has joined #ubuntu-asahi
11:09sespiros[m] has quit [Ping timeout: 485 seconds]
11:09eslerm[m] has quit [Ping timeout: 480 seconds]
11:09jcverdie[m] has quit [Ping timeout: 480 seconds]
11:09Saviq[m] has quit [Ping timeout: 480 seconds]
11:09jmeosbn[m] has quit [Ping timeout: 480 seconds]
11:09throwaway02020[m] has quit [Ping timeout: 480 seconds]
11:09tobhe[m] has quit [Ping timeout: 480 seconds]
11:09GarethWoolridge[m] has quit [Ping timeout: 480 seconds]
11:11popey[m] has quit [Ping timeout: 607 seconds]
11:11tobhe[m]1 has quit [Ping timeout: 607 seconds]
11:11john-cabaj[m] has quit [Ping timeout: 592 seconds]
11:11wildwestrom[m] has quit [Ping timeout: 607 seconds]
11:13tim[m]12 has quit [Ping timeout: 480 seconds]
14:16john-cabaj[m] has joined #ubuntu-asahi
14:16john-cabaj[m]do-release-upgrade isn't finding a new Ubuntu release for me
14:16tobhe[m] has joined #ubuntu-asahi
14:16john-cabaj[m]That found it
14:16tobhe[m]https://github.com/UbuntuAsahi/ubuntu-asahi/issues/112#issuecomment-2082281936 for reference
14:17john-cabaj[m]tobhe[m]: Yep, this is what I'm following
14:17john-cabaj[m]I hardly ever update my main machine, so the do-release-upgrade intricacies are lost on me
14:18tobhe[m]I think it will at some point work without -d but is currently blocked to fix some last bugs. 22.04 will only go to 24.04 once 24.04.1 is out
14:47john-cabaj[m]Upgrade complete - looking good.
14:47john-cabaj[m]Think I'll keep my MacBook as my forward devel machine and work computer on LTS
14:53tobhe[m]keeping the mac up-to-date sounds like a good idea 🙂 especially when you're building new kernels
14:54john-cabaj[m]I'm definitely forced to keep it up to date. The above was just more rationale for why my Thinkpad stays behind.
14:55tobhe[m]I am very bad in sticking to LTSs. Usually the mac stays on the latest release and the desktop goes to development release as soon as it is feasible
14:57john-cabaj[m]Now that Asahi is on 6.8, I really hope they work to figure out this idle power issue. My computer died over the weekend on suspend
14:57arcticp[m] has joined #ubuntu-asahi
14:59popey[m] has joined #ubuntu-asahi
14:59popey[m]My MBA isn't heavily used now I have a work M3 MBP. So if there's anything anyone wants me to test, or leave running or whatever on the m1, lemme know
15:13tobhe[m]eslerm: added more contect to the protection-domain-mapper bug report https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2062667
15:23eslerm[m] has joined #ubuntu-asahi
15:24eslerm[m]V wants a specific file that could be disabled, which is likely the service file you mention
15:47tobhe[m]vorlon might have resolved the libreoffice issue. looks like launchpad just failed to publish them for some reason
15:47john-cabaj[m]That actually makes perfect sense
15:51GarethWoolridge[m] has joined #ubuntu-asahi
15:51GarethWoolridge[m]ah nice - I just purged libreoffice and then installed the snap after d-r-u.
15:51GarethWoolridge[m]Im sure I'll regret that given how large that snap seems to be and how long it takes to download, but hey "the future".
15:55tobhe[m]GarethWoolridge[m]: > <@moon127:ubuntu.com> ah nice - I just purged libreoffice and then installed the snap after d-r-u.... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/eLHWruNxKDusATQeixjXsAMi>)
17:10eslerm[m]<john-cabaj[m]> "Think I'll keep my MacBook as my..." <- currently, we only support ubuntu releases for 9 months
17:11john-cabaj[m]I don't think we can always support the most recent LTS for the same reason we couldn't support Jammy
17:12john-cabaj[m]I don't think it's so much a kernel limitation as it is the package dependencies
17:14john-cabaj[m]The problem with Jammy was continuing to support new versions of rust
17:14john-cabaj[m]And I think there was the wireplumber issues or something, too
17:16eslerm[m]maybe it is better to keep our current support window, and (after 9 months) keep offering LTS as an unsupported EXPERT=1 install option
17:20john-cabaj[m]I can keep copying the kernel binaries to the latest LTS release no problem
17:46tobhe[m]imo ROS is still a bit of a non issue. Nothing forces you to run the same release bare metal when there are vms and containers
17:47tobhe[m]we are probably in a nicer place now because we can just freeze noble in terms of features at some point
20:46john-cabaj[m]Yeah, they're outpacing noble right now
20:47john-cabaj[m]Makes it tricky to figure out the actual patchsets
20:48tobhe[m]now what do I do next. Fix a bug I found in 22.04, figure out why update manager segfaults on 23.10 or try to build installer images
21:27john-cabaj[m]We need to develop a regular cadence or something
21:28john-cabaj[m]Take any updates from the previous week. Prep on Friday and let build over the weekend. Test on weekend (if people can) or Monday. Release Monday/Tuesday