marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | Not ready for end users / self contained install yet. Soon. | General project discussion | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<marcan>
j`ey: there is some APFS compression thing in use, but I don't know how to turn it on when copying the file out in the installer
<tpw_rules>
is the dmg signed or something? they support compression internally
Dcow has joined #asahi
<marcan>
it's APFS and signed at that level I think?
<marcan>
not entirely sure at what layer their hash tree stuff works
<marcan>
landscape15[m]: s/1TR/system recovery/
<marcan>
1TR is not "the fallback recovery"
<marcan>
1TR is "any signed recovery you booted asserting physical presence"
<marcan>
I conflated these two in the past since 11.x always used the global one, and now everyone is confused :<
yuyichao has quit [Ping timeout: 480 seconds]
riker77_ has joined #asahi
snek has joined #asahi
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Dcow has joined #asahi
yuyichao has joined #asahi
<amw>
Booted wifi/take5 on my MBA - everything working including wifi - but I get a USB WARN msg when I unplug the USB cable I boot the mba over - see https://paste.debian.net/1224994/
chadmed has joined #asahi
<amw>
I think it is do with the kernel trying to use the USB cable as a gadget for a serial or something?
<amw>
It seems harmless so I'm happy with my set up on the MBA - just waiting for the battery + u-boot NVME booting now
<tpw_rules>
u-boot nvme booting works fine
<tpw_rules>
well i haven't tested it with the wifi linux branch
<tpw_rules>
or on a not macbook mini
<tpw_rules>
air >_>. only tested it on the mac mini
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<amw>
tpw_rules: I thought it left the nvme running which linux didn't like when it started
<tpw_rules>
that was fixed
<tpw_rules>
i've pretty much exclusively been using it that wauy
<tpw_rules>
it doesn't work with the new nvme branch for whatever reason
<amw>
I have the default boot to m1n1 so if I bundle that with u-boot I can boot to linux.
<tpw_rules>
you might also have to futz with device trees. not sure if u-boot has the necessary stuff for the wifi, or can use linux's versions
Dcow has quit [Ping timeout: 480 seconds]
<amw>
Myh expeience with u-boot was that you can use it to load the dtb and kernel image into memory from the disk - so hopefully I just need to put it in the right spot (/boot) on the nvme and all should be good - what could go wrong :-)
phiologe has joined #asahi
PhilippvK has quit [Ping timeout: 480 seconds]
Dcow has joined #asahi
caef^ has quit [Remote host closed the connection]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi
the_lanetly_052__ has joined #asahi
Dcow has quit [Ping timeout: 480 seconds]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
darkapex has joined #asahi
darkapex4 has quit [Ping timeout: 480 seconds]
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
Dcow has joined #asahi
Dcow has quit [Ping timeout: 480 seconds]
<marcan>
amw: I think there's something dodgy about gadget mode, yeah; I wouldn't worry too much about it for now
<marcan>
amw: loading DTBs from u-boot is not supported
<marcan>
m1n1 needs to process the dtb before it can be used
<marcan>
bypassing that will break a bunch of things
mps has quit [Ping timeout: 480 seconds]
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
darkapex1 has joined #asahi
mps has joined #asahi
darkapex has quit [Ping timeout: 480 seconds]
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
malvo has quit [Ping timeout: 480 seconds]
<amw>
marcan: Ok - you process the dtb with stuff from the Apple EFI or something?
<amw>
Is it possible to use the python to pre-process the .dtb so that it can be saved in the NVME partition and uboot can pick it up as normal?
<j`ey>
not EFI, but from Apples device tree
squags has quit [Ping timeout: 480 seconds]
malvo has joined #asahi
squags has joined #asahi
<sven>
no, the device tree will always come from m1n1
<sven>
putting it into nvme separate from m1n1 will result in a lot of headaches eventually
<marcan>
amw: no, the dtb has to be processed with *runtime* information from your machine
<marcan>
we already make everything that can be static static
<marcan>
device trees are designed to be updated by bootloaders with runtime information
<marcan>
static DTs only work for very simple machines; these machines aren't simple
<marcan>
there are things that change every boot
<j`ey>
even then, bootloaders can update them with kernel args etc
<j`ey>
kaslr seed too
<marcan>
yes, kaslr changes the SEPFW address on every boot
<marcan>
and the memory base potentially
<amw>
Wow - nothing's ever easier...
<marcan>
and the framebuffer address can change depending on what monitor you have plugged in, or could until apple broke it on the mini entirely
<marcan>
I really need to start making a pile of "don't do that" patches for linux/u-boot/etc - something that gives you big "don't do that" warnings every time someone tries to do something that won't work, like load a dtb :p
squags has quit [Ping timeout: 480 seconds]
<amw>
I think a u-boot page might be useful spot?
<amw>
on the wiki
<marcan>
nobody reads wikis :p
<marcan>
better have some warnings in the actual code
<marcan>
this is distro-level stuff; I don't mind maintaining some trivial downstream patches like that just to save us headaches when people come here for support
<amw>
There's only one Asahi Wiki page - but many clones of u-boot...
chadmed has quit [Quit: Konversation terminated!]
squags has joined #asahi
squags has quit [Ping timeout: 480 seconds]
Dcow has joined #asahi
squags has joined #asahi
Dcow_ has joined #asahi
Dcow has quit [Remote host closed the connection]
Dcow_ has quit []
Dcow has joined #asahi
boardwalk has quit [Quit: Ping timeout (120 seconds)]
boardwalk has joined #asahi
jeffmiw has joined #asahi
<jeffmiw>
amw: if you want to boot directly to linux, you can just use the m1n1 direct payload method : just cat m1n1 with dtb and kernel image (and initrd if needed) and install this with kmutil (See wiki/developer-quickstart=> Direct payload booting)
Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<landscape15[m]>
is it safe to use fdisk to initialize a FAT partition created on macOS? I will install Linux on it then.
kgarrington has joined #asahi
kgarrington has quit [Remote host closed the connection]
Dcow has joined #asahi
Dcow has quit []
squags has quit [Ping timeout: 480 seconds]
aleasto has joined #asahi
aleasto has quit [Remote host closed the connection]
aleasto has joined #asahi
aleasto has quit [Remote host closed the connection]
aleasto has joined #asahi
squags has joined #asahi
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
joske has joined #asahi
<joske>
jeffmiw: how do you pass the rootfs/boot arguments in that case?
<mps>
joske: https://tpaste.us/kxg9 this is my POC script to install alpine on usb, look at 'cat ....' part
<mps>
on top of script I defined 'model' variable and put value for my machine `model='j293'` but it intended be changed for users who install to set their model there
<joske>
Image.gz and dtb are working when booting from m1n1
<joske>
mps: yes I understand, but I didn't run your script, I just used the cat line to create the macho binary from my m1n1 + kernel etc
<joske>
I already have a working linux
<mps>
joske: I remember
<joske>
just want to have it boot directly
<mps>
joske: what you mean by 'directly'
<joske>
from reboot
<joske>
not boot to m1n1 and use another PC to boot kernel
<mps>
joske: this what i posted is for that, i.e. boot directly
<joske>
yes, but it doesn't work (installed with kmutil)
<joske>
it says no valid payload found
<j`ey>
joske: if you have something that works with chainload, it should work with kmutil
<mps>
aha, maybe somewhere is bug then
<joske>
the boot args go directly after m1n1??
<mps>
I don't have time now to check it again
<joske>
that's what your script does
<mps>
yes, that's ok
<mps>
maybe your shell messed bootargs
<joske>
I tested with a test file to see if the <$() works
<kettenis>
marcan: maybe you should look into what happens with the Linux device tree; I think we want to prevent it from being installed and/or shipped by distros as part of their device tree package
yrwm^ has quit [Remote host closed the connection]
Dcow has joined #asahi
darkapex1 has quit [Ping timeout: 480 seconds]
joske has quit [Ping timeout: 480 seconds]
hollister has quit [Ping timeout: 480 seconds]
joske has joined #asahi
joske has quit [Remote host closed the connection]
malvo has joined #asahi
joske has joined #asahi
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
squags has quit [Ping timeout: 480 seconds]
malvo has quit [Read error: Connection reset by peer]
malvo has joined #asahi
squags has joined #asahi
squags has quit [Ping timeout: 480 seconds]
squags has joined #asahi
rose_ has joined #asahi
<rose_>
hey im back with more problems - im trying to get some output from u-boot to prove it works since upgrading to 12.1 (turns out i shouldn't have done that so eagerly lol) and i've heard that since 12.1, iboot no longer inits the framebuffer, which is why u-boot isn't displaying anything. apparently, there are people here who know the incantations
<rose_>
needed to get video output from u-boot even with this update?
<rose_>
ehh i gtg for a while but i'll check the logs later
<tpw_rules>
i mean you can run it under the hypervisor
<tpw_rules>
and it will talk on the serial console. not sure about video
<rose_>
by "the hypervisor" you mean m1n1? i already am
<tpw_rules>
then what do you mean by "prove it works"?
<rose_>
hmm.. it doesn't talk on serial
<rose_>
we have no output from u-boot at all, and back in big sur we had video
<tpw_rules>
use run_guest.py or whatever and then open /dev/ttyACM1 (before you start run_guest) and it should come up on console
<tpw_rules>
yeah you won't get video output. but if you just want proof u-boot is booting
<rose_>
yeah long term we're trying to boot netbsd, i dont really understand which scripts do what so we've mostly been using wrangled versions of linux.py
<tpw_rules>
if you do cat m1n1.bin u-boot.dtb u-boot-nodtb.bin > blah.bin then run_guest that it should work
<tpw_rules>
more or less
<rose_>
btw, where do people tend to build u-boot from? from the logs earlier it seems there are a few forks, but idk which ones the most likely to work
<rose_>
thanks though i'll look into run_guest, and like i said i gtg but i'll check the logs