#
#asahi · 2025-02-03 10:32
fl0_idthx. yeah I'm doing efi. For the raspi image I have been working with an ubuntu server iso, which I assume is similar to debian (like to chroot into the raspi image)
#asahi · 2025-02-03 10:30
r0nigentoo-kernel configs work for me and i use a slackware system in vmware fusion. but I have to manually manage the grub.cfg but it works perfectly
#asahi · 2025-02-03 10:28
chaos_princesslook for "System Ready" images or guides for Ampere servers
#asahi · 2025-02-03 10:28
r0niand yeah efi like a pc install
#asahi · 2025-02-03 10:28
r0niwhat i'd do is install debian vm, and create your pop-os from there as another hdd and add it to grub
#asahi · 2025-02-03 10:27
chaos_princessfor vms you do EFI, not u-boot or whatever vendor nonsense
#asahi · 2025-02-03 10:26
fl0_id the raspberry pi kernel and grub only boots manually for some reason. (Despite having also moved the kernel to the efi part just to be sure)
#asahi · 2025-02-03 10:26
fl0_idr0ni I'm trying to create a pop-os boot image, which is based on debian/ubuntu. also testing with vmware fusion. They have a public iso creation thing, but so far only have an incomplete branch for some snapdragon-x-elite. This did work for me, but somehow it doesn't continue from grub. Before I somewhat successfully booted a raspberry pi based image after installing a generic kernel into it, but that one is annoying because it always wants to switch to
#asahi · 2025-02-03 10:22
r0niif you can obtain a rootfs for distro you want to use, I suggest using the gentoo arm64 boot media
#asahi · 2025-02-03 10:21
r0nigrub works for me with vmware fusion but outside of debian or fedora you have to make your own system from scratch basically
#asahi · 2025-02-03 10:20
r0nifl0_id: what you trying to do?
#asahi · 2025-02-03 10:17
fl0_iddoes anybody know what is required for arm bootable isos? (specifically for vms) I created one and it shows the grub boot screen, but then it just goes to black without any output.
#asahi · 2025-02-02 21:50
vlad2305mUnfortunately GitHub doesn't index non-default branches for search
#asahi · 2025-02-02 21:30
j`eythat's only for pmgr :)
#asahi · 2025-02-02 21:30
vlad2305mMy hope is 'pmgr_adt2dt.py'
#asahi · 2025-02-02 21:29
j`ey*not* the dts
#asahi · 2025-02-02 21:29
j`eywhat you get from m1n1 is the adt
#asahi · 2025-02-02 21:28
vlad2305mWill definitely try getting the dts from m1n1 to start U-boot tomorrow. Thank you very much!
#asahi · 2025-02-02 21:26
vlad2305mThe only problem I had in the installer for IPSW 14.3 is that it splits on _ in wifi names like java_gen, and there are a lot of *_gen's
#asahi · 2025-02-02 21:24
jannauI didn't deal with the installer and just used a second macos install with manually installed m1n1
#asahi · 2025-02-02 21:22
vlad2305mI only managed to feed the installer 14.2-14.4 For newer it chokes at a wifi file that doesn't exist but is symlinked to. `paradise` or something like that
#asahi · 2025-02-02 21:22
jannaumy devicetree for m3 (j504) might be helpful: https://github.com/jannau/linux/tree/t8122-j504
#asahi · 2025-02-02 21:21
jannauon dts side the nvme will not work with the firmware from macos 15.x
#asahi · 2025-02-02 21:19
jannauvlad2305m: I'm not sure if the structure from M1 and M2 Pro/Max transfers to M3 Pro / T6030. To some degree it looks more like a predecessor of M4 with 2 additional performance cores (without)
#asahi · 2025-02-02 21:17
j`eythere must be some dtb somewhere for m3s, people have run some linux on them
#asahi · 2025-02-02 21:16
vlad2305mThanks!
#asahi · 2025-02-02 21:12
j`eythis python script can dump the adt https://github.com/AsahiLinux/m1n1/blob/main/proxyclient/m1n1/adt.py
#asahi · 2025-02-02 21:10
fl0_idvlad2305m afaik you cannot use a wrong device tree. if I remember correctly you can extract them from firmware / update images and maybe someone already did that. but not sure where
#asahi · 2025-02-02 16:27
vlad2305mway to download Apple Device Tree, but I barely know how macs work.
#asahi · 2025-02-02 16:27
vlad2305mHello! I have an M3 Pro, Target: J516s, Chip-ID: 0x6030. So far I managed to make the tethered setup working, but now I'm stuck because there is no devicetree for M3 yet. Can somebody point me in the right direction? Would maybe t6020-j416s.dts be forward-compatible, or is the new generation too different? Is it even safe to use the wrong device three, and if not, what has the procedure been for making them? I don't seem to find a
#asahi · 2025-02-02 09:33
j`eyanyone using wlroots master branch?
#asahi · 2025-02-01 23:52
poniesthere are some reports on fedoraproject from last year. this seems accurate -- but doesn't require NM or connman to reproduce: https://discussion.fedoraproject.org/t/iwd-on-asahi-sometimes-disconnects-and-cannot-connect-again-for-a-few-minutes/126392
#asahi · 2025-02-01 23:49
poniesdose anybody experience occassional wifi dropouts with iwd (M2)?
#asahi · 2025-02-01 11:58
sonneany asahi devs in fosdem?
#asahi · 2025-02-01 11:55
jannauaustriancoder: ^^^
#asahi · 2025-02-01 11:55
jannaufixed m1n1 for fedora 40/41 is available. `dnf --refresh upgrade` will install the fixed m1n1-1.4.21-1.fc41.aarch64 (This affects only M2 Pro and M2 Max Macbooks Pros)
#asahi · 2025-02-01 08:16
jannaunicolas17: yes
#asahi · 2025-02-01 01:30
nicolas17jannau: M2 should be fine too?
#asahi · 2025-01-31 23:17
jannauPSA: m1n1 1.4.19 is broken on M2 Pro/Max Macbook Pros (desktop are unaffected). please downgrade m1n1 with `dnf downgrade m1n1` if m1n1-1.4.19-1 is lready installed
#asahi · 2025-01-31 23:14
jannauhttps://github.com/AsahiLinux/m1n1/pull/434
#asahi · 2025-01-31 23:08
jannauin m1n1
#asahi · 2025-01-31 23:08
jannauno need to. I found the issue
#asahi · 2025-01-31 22:59
Tramtristno kernel in a while
#asahi · 2025-01-31 22:58
Tramtristthere was an m1n1 update a couple days ago
#asahi · 2025-01-31 22:58
austriancoderare there any dnf logs to stare at?
#asahi · 2025-01-31 22:57
austriancoderokay.. then I am to 80% sure that it was just the m1n1 update
#asahi · 2025-01-31 22:41
jannauwhen was the last update before. the last kernel update was ~2 weeks ago
#asahi · 2025-01-31 22:29
austriancoderjannau: good question
#asahi · 2025-01-31 22:26
jannauaustriancoder: was only m1n1 updated or the kernel as well?
#asahi · 2025-01-31 21:56
jannaunot really, looks like it is in kboot* after the atc tunables

plus ›