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
<zamadatix> I'll never get over how fast this thing is for being silent
<j`ey> zamadatix: did you see hid_apple.fnmode=2?
<zamadatix> J`ey: Yeah testing that out now, got distracted :)
<marcan> alright, this might just be it
<marcan> compressing image...
<marcan> I threw in the entire KDE app set
<tpw_rules> so are we about to graduate from pre-alpha to alpha
<marcan> yup
<tpw_rules> wheeee
<zamadatix> 🎉
<marcan> now I guess I need to test this on all the machines don't I :p
<Dcow[m]1> yey! congrats everyone! big thanks to marcan!
<Dcow[m]1> so, when it hit the twitter?
<zamadatix> J`ey: works, thanks
<marcan> I need to write the announcement post
<marcan> and it will be pushed to the proper alx.sh URL
<marcan> just please test it first :p
<j`ey> zamadatix: great. kov ^
<Dcow[m]1> sure, I am wrapping up with my $WORK and going to test new asahi after that
<marcan> alright, it's pushed. reminder: curl -L https://alx.sh/dev | sh
<marcan> installing here...
<tpw_rules> marcan: i wonder if you should label plasma as GUI and core as CLI
<zamadatix> Testing on t6001
<j`ey> need a family photo of plasma on all the machines!
<marcan> tpw_rules: might be a better idea
<marcan> let's say Arch Linux Desktop and Arch Linux Minimal
<marcan> how's that?
<_alice> also i guess it's probably time to nix the "This isn't even remotely ready yet." part of the readme. ^^
<tpw_rules> meh i figured just put it in the parens as Arch Linux ARM + KDE Desktop or so
<tpw_rules> but that does sound nice
<Dcow[m]1> I think for people who gonna use it now it doesn't really matter
<Dcow[m]1> they should be aware of what they installing already
<marcan> er I meant Asahi Linux Desktop / Minimal
<marcan> I'm tired okay
<marcan> it's 9AM
<zamadatix> I like Asahi Linux Desktop / Minimal
<Dcow[m]1> a little confusing, maybe s/DESKTOP/KDE ?
<marcan> happy? :>
<_alice> cool ^^
<j`ey> haha
<marcan> got a CRC error on install, I *think* that was the CDN lagging on the invalidate (okay, tells me I really need to rotate filenames)
<marcan> hm, again
<marcan> wtf
<marcan> let me rename it
<Dcow[m]1> "zlib.error: Error -3 while decompressing data: invalid block type" ?
<Dcow[m]1> that? hit this too
<marcan> wait no
<marcan> I'm dumb
<marcan> yeah
<marcan> sorry
<Dcow[m]1> wrong tar format?)
<marcan> actually I don't know what happened
<tpw_rules> cosmic rays
<dan[m]123> It’s probably obvious for a lot of people but you should show the default root credentials somewhere
<marcan> the minimal image has the ALARM ones; the desktop image does not have any (well, it does as a fallback, but the root password gets disabled upon successful completion of the first run wizard)
<marcan> might make sense to have a "image readme" type feature in the installer so OS images can show specific info like that?
<tpw_rules> can you also write down somewhere how to clear out whatever storage area makes bputil slow? it's getting kind of agonizing on this machine
<zamadatix> Yeah, something for images to display first run info is probably needed at some point.
<_alice> does the installer stream root.img from the CDN the same way it does for firmware components from the .ipsw files?
<marcan> curl -L https://mrcn.st/cleanbp.sh | sh
<marcan> _alice: yes
<_alice> "Extracting root.img into diskXsY partition..." is taking forever w
<_alice> might just be WiFi slowness
<tpw_rules> marcan: can that be done from macOS or does it have to be 1TR?
<tpw_rules> also does the non-expert mode ever let you select which firmware version
<marcan> you need to disable SIP for it to work from macOS
<marcan> it does not
<marcan> I think the new image isn't borked :)
<marcan> let's see if it boots... still copying...
<_alice> aw, got "Connection reset by peer"
<marcan> it didn't retry?
<marcan> it should retry up to 5 times
<_alice> it's retrying it seems
<marcan> flaky network?
<_alice> probably
<_alice> activity monitor shows speeds on the order of kilobytes
<marcan> heh
<marcan> damn, I remember when these all-the-things distro images fit on a damn *CD*
<tpw_rules> oh excellent, the bless gets rid of that scary loop with the startup disk preferences
<tpw_rules> a what now?
<marcan> this is 3.3 GB compressed, that's almost a full DVD and it's just KDE!
<marcan> tpw_rules: yes, that's why I went straight for 12.3
<marcan> it's too much of a liability
<marcan> people were going to hate that
<_alice> i think in the future, a progress bar plus network throughput/ETA information would be nice
<marcan> and I ran into a failed race at least once, other people have too
<_alice> although that's annoying to do without pulling in python dependencies iirc
<marcan> _alice: we take PRs :>
<marcan> but yeah I need to think about how to implement that
<j`ey> marcan: that was on stream i think
<marcan> might be
<kit_ty_kate> marcan: what are you using for the compression?
<marcan> zip
<marcan> I just changed it to level 1 because it's not much better than the default and the default already takes ages to compress the image
<marcan> *much worse
<tpw_rules> good news the UEFI only option still works on mac mini
<marcan> install done
<marcan> yay, it worked :>
<marcan> now I just need to figure out how to make Firefox the default browser by default, instead of Konqueror :p
<kit_ty_kate> maybe using xz could help (not for compression but for downloading, for the users at least)
<marcan> I'm using zip because Python has built in support and I can stream it
<marcan> and we already use that for IPSWs
<_alice> i wonder if it would be better to just do a traditional download for the package zip file, since there's no need to pick out specific files from it, is there?
<_alice> the weird thing is that i don't think it's entirely my flaky network, because downloading the 12.3 OTA update went just fine at 300-400Mbps
<_alice> oh it finally finished root.img
jmr2 has joined #asahi
<marcan> the problem with traditional download is that we need staging space
<tpw_rules> marcan: not sure if it matters (it doesn't for my purposes) but `cat /proc/device-tree/chosen/asahi,efi-system-partition` has a NULL byte at the end of it
<_alice> would `mktemp` not work?
<_alice> wow this setup wizard is pretty
<tpw_rules> so is usb3 expected to work in this kernel? is my config messed up? i have that option set from earlier
<_alice> wow, it actually detects JIS layout
<_alice> this is a first for Linux on a JIS keyboard Mac for me w
jmr2 has quit [Quit: Page closed]
<tpw_rules> seems no, we are still on usb2
<zamadatix> geez, weren't kidding about this image taking its time :p
<chadmed> M1bn3mar[m], j`ey: that repo will be fixed up at some point, but its still pretty useless since the kernel on gentoo's arm install image is so old it wont boot on these machines at all. once that is rectified ill start working on it again. i left it in a ridiculous state on purpose so no one would be tempted to use it :P
<chadmed> the portage overlay works fine though which is really the main thing, like if you can get gentoo on these machines at the current level of support i presume you are capable enough to install and sync that up manually anyway
<chadmed> i need to turbo-nuke my j314s and start fresh, one of the recovery partitions disappeared so now it wont apply updates. once i sort all that out though i might make that gentoo support project a little less silly over the weekend
<chadmed> i have a neurology paper to write too though, so no promises :)
<marcan> tpw_rules: that is expected
<marcan> _alice: that was one of the last things I added a couple hours ago
<marcan> details matter!!!
<tpw_rules> marcan: the null? okay
<_alice> :)
<marcan> :D
<chadmed> oh hey we have names for the CPUs new neat
<chadmed> s/new/now
<_alice> it's kinda weird how lscpu doesn't show the part model though
<chadmed> i just get 10x Unknown so youre still doing better than my machine lmao
<_alice> upstream has the values for icestorm/firestorm: https://github.com/util-linux/util-linux/blob/master/sys-utils/lscpu-arm.c#L156
<_alice> (unless i'm silly and that isn't the actual upstream for lscpu)
<zamadatix> Getting around 20 kbps while extracting root.img for some reason but it's still going so we'll see where it ends up
<_alice> i wonder if that's a CDN issue or just a streaming zip downloader issue…
<_alice> i started my install before marcan pushed the "Bump zip file names" commit, so hm
yuyichao has quit [Ping timeout: 480 seconds]
PaterTemporalis has quit [Ping timeout: 480 seconds]
creechy has joined #asahi
abrasive has joined #asahi
kreechy has quit [Ping timeout: 480 seconds]
<_alice> i think i'll chalk it up to CDN stuff… downloading asahi-plasma-20220317-1.zip from cdn.asahilinux.org via a browser (over ethernet) only gets me ~4-5 MB/s at most, while de.mirror. easily gets up to 20+ MB/s
<marcan> that is... bizarre
<marcan> ok, I'm falling asleep... I think I need to take a nap
<_alice> have a nice nap ^^
<_alice> activity monitor was showing 300-500 KB/s when i was running the installer on the laptop, sometimes jumping to 1-2 MB/s momentarily… (but also i don't think activity monitor is the most accurate thing for instrumenting this)
<_alice> i don't see any obvious bottleneck in urlcache.py, so… hm
<marcan> it downloads in 10MB chunks, but unless your latency is terrible that shouldn't be too bad...
creechy has quit [Ping timeout: 480 seconds]
<zamadatix> Ridiculously faster running it a second time so "CDN weirdness" seems to be past. Enjoy some rest
<_alice> yeah, maybe it needs some time/activity to warm the caches or something (not sure how BunnyCDN in particular works)
chadmed has quit [Quit: Konversation terminated!]
zamadatix has quit [Quit: Leaving]
<marcan> it might've just been the CDN having a backend bottleneck, and once it was in the local node it's fast
rqou_ has joined #asahi
<rqou_> hi, trying to compile the asahi linux kernel and run it on my m1 max machine, but somehow i can't seem to figure out how to get the framebuffer to show up. starting with the https://tg.st/u/config-2022-02-19 config
<rqou_> i can tell the kernel is definitely booting, because if i boot the kernel under the m1n1 hypervisor, i can get all the console output
<rqou_> it even successfully boots to an initramfs
<rqou_> but i can never get the laptop screen itself to show anything except the asahi linux logo
<rqou_> i assume there's a kernel config somewhere that i'm missing?
<tpw_rules> https://github.com/tpwrules/nixos-m1/blob/main/nix/m1-support/kernel/config this is my config. have you updated your m1n1 and device trees recently? there's been a lot of flux in that area recently
<rqou_> i'm using the devicetree built by the "asahi" branch of https://github.com/AsahiLinux/linux
<rqou_> which i cloned a few hours ago
<tpw_rules> that should be good then
<rqou_> the kernel itself is running, i just can't get the framebuffer to work
<tpw_rules> it looks like you have the options i can recall necessary set.
<rqou_> is there something i have to pass on the kernel command line?
<rqou_> the console appears if i use the m1n1 hypervisor
<tpw_rules> no, it should have all the information passed by m1n1
<tpw_rules> is your m1n1 old?
<rqou_> it's m1n1 installed by https://mrcn.sh/alxsh as of this morning
<tpw_rules> hm, that should be good too then
<marcan> that is outdated as of a few hours ago
<marcan> oh wait, I did redirect it I think?
<marcan> then it's ok
* marcan -> sleep
zamadatix has joined #asahi
<rqou_> unfortunately i don't really have any idea where to start debugging this?
<rqou_> kernel itself works
<tpw_rules> i would start by trying my config
<tpw_rules> or posting the dmesg you get from the hypervisor
<rqou_> here's my dmesg https://pastebin.com/QKtbw6X1
<rqou_> going to try the config you posted
<tpw_rules> here is the official config too: https://github.com/AsahiLinux/PKGBUILDs/tree/main/linux-asahi but mine should be faster to compile and is known good too
<zamadatix> Hmm when I do the new installer desktop option after the "press enter to shutdown" it seems to actually do a reboot, then fail a bunch, instead of shutdown and allow me to long press the power button.
<zamadatix> That said manually shutting down at that point then long pressing the power button seems to have let stage 2 finish fine
yuyichao has joined #asahi
<zamadatix> but a note for marcan when he wakes back up
burner67665[m] has joined #asahi
<dan[m]123> I’ve had 0 issues on a 2020 MBP doing a minimal install
<zamadatix> minimal install worked fine for me about an hour prior to this new installer, haven't tried it again yet since the desktop option was added though.
<zamadatix> Also KDE display configuration is showing 60hz as the only refresh rate, though that may be intended given the lack of GPU acceleration at this stage. When I was in minimal I'm pretty sure Sway was seeing 120 (albeit having a hard time hitting it)
<zamadatix> But otherwise Desktop seems to be working great, Wi-Fi and all now :)
<burner67665[m]> Amazing
<burner67665[m]> Props to everyone that has contributed and/or seen the journey up to this point, trult magnificent
KirkByers[m] has joined #asahi
zamadatix has quit [Quit: Leaving]
<tpw_rules> how many rows of +s am i supposed to get for the asahi linux desktop
<tpw_rules> almost up to three and getting impatient...
<clover[m]> alxsh
<tpw_rules> the answer is about 4.6
<tpw_rules> sorry, 3.6
<tpw_rules> nit: the "asahi linux support" button opened a firefox that's stuck behind the installer window. also it requires internet to load
<tpw_rules> bigger-ish nit: u-boot's "boot the /chosen/asahi esp" patch from jannau is not in yet so multiple OSes doesn't really work
creechy has joined #asahi
<tpw_rules> smaller-ish nit: sometimes i get this weird bug on m1n1 where three asahi linux logos show up, but two of them are stretched weird horizontally and in the top left quadrant
<clover[m]> doing the installer now
<rqou_> tpw_rules: your config works, so i guess the https://tg.st/u/config-2022-02-19 one is broken
<rqou_> Somebody(TM) might want to mark that as such
<tpw_rules> rqou_: where did you get it? do you remember the wiki page?
<tpw_rules> if it was the wiki?
<tpw_rules> ahh...
<rqou_> so, before i curse myself with impossible-to-debug issues: does that 4k page size patch work?
<tpw_rules> yes
<tpw_rules> (let me diff it against mine to be sure...)
<rqou_> oh it doesn't apply cleanly, but i managed to fix it
<tpw_rules> yeah, they look the same
<tpw_rules> except for that bit you fixed
<clover[m]> wow 'Shrinking APFS data structures" step takes a minute
<tpw_rules> updated the nixos guide and installer for all of today's exciting changes: https://github.com/tpwrules/nixos-m1/blob/main/docs/uefi-standalone.md
<clover[m]> cool
creechy has quit [Ping timeout: 480 seconds]
PhilippvK has joined #asahi
fortelling[m] has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
kov has quit [Quit: Coyote finally caught me]
<clover[m]> holy moly the asahi installer worked! i was pretty nervous but i, a total noob, just pulled it off.
<tpw_rules> hm, my mini just reset itself while compiling a bunch of stuff
<tpw_rules> but in fairness i was compiling both firefox and webkitgtk at the same time
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
<clover[m]> maybe ran out of RAM?
<tpw_rules> possibly, but i wouldn't think that would crash it. i didn't see it reboot, i just heard it
<rkjnsn> I've had builds of Chromium completely lock up my system not infrequently if I have other memory-hungry processes running at the same time. I imagine the watchdog on the M1 would turn that into a reboot.
<tpw_rules> yeah. i wonder if there's a way to log that
<rqou_> question: does booting via m1n1->uboot->grub->linux work right now?
<rqou_> i have m1n1->uboot->grub working, but i am not clear on the (distro-specific?) glue needed to make grub->linux work
<rqou_> er, i seem to have gotten it to "work" but with only one core, is this also a known issue?
creechy has joined #asahi
<tpw_rules> rqou_: maybe device tree related? m1n1 has to see and munge the device tree that eventually makes it to the kernel, so neither u-boot or grub can load one without things breaking
<tpw_rules> aside from that, if your kernel is supported, grub provides a standard enough UEFI environment and you should be able to load whatever
<tpw_rules> the official installer installs an m1n1 that chainloads another m1n1 from the ESP so you can change device trees easily
<tpw_rules> right now i think the official asahi linux stuff installs device trees from their u-boot repo, but they should be identical to the ones in linux
<tpw_rules> s/grub/u-boot/
<tpw_rules> heck, nixos uses systemd-boot instead of grub and works fine
chadmed has joined #asahi
<tpw_rules> the only wrinkle is that EFI variables are not supported, so you'll have to make sure your EFI executable gets put in the removable path \EFI\BOOT\BOOTAA64.EFI for u-boot to find it. `efibootmgr` also won't be able to do anything useful
<rqou_> ahh ok that makes sense
<rqou_> i was trying to load the devicetree using grub's `devicetree` command
<rqou_> if i just... don't do that, then it does work
<rqou_> other than distro glue(?) not detecting the kernel
<tpw_rules> idk what you mean by distro glue. there is absolutely nothing distro or m1 specific in grub
<rqou_> grub-mkconfig isn't generating an entry for the kernel i built
<tpw_rules> ah, well that is between your distro and you, yes
<chadmed> name your kernel vmlinuz-linux and associated initramfs initramfs-linux.img and then rename the default ones to something else and try again
<chadmed> those are grub's default names and it will ALWAYS pick up kernels and initrds named that regardless of whatever the distro's config does
<rqou_> chadmed: worked, thanks!
creechy has quit [Ping timeout: 480 seconds]
jakebot has joined #asahi
chadmed has quit [Quit: Page closed]
<Glanzmann> rqou_: I need to Update the DesktopKernel thing. Here you find my current build instructions for the kernel: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob_plain/refs/heads/master:/bootstrap.sh
<Glanzmann> rqou_: I updated the wiki page.
rikkaa has joined #asahi
<Glanzmann> Oh boy 20 Debian installs this morning.
gladiac has quit [Quit: k thx bye]
gladiac has joined #asahi
gladiac has quit []
gladiac has joined #asahi
gladiac has quit []
gladiac has joined #asahi
sleepygoose has joined #asahi
sleepygoose_ has joined #asahi
rikkaa has quit [Remote host closed the connection]
eroux has joined #asahi
sleepygoose has quit [Ping timeout: 480 seconds]
opticron has quit [Remote host closed the connection]
sleepygoose_ has quit [Remote host closed the connection]
opticron has joined #asahi
rikkaa has joined #asahi
<rqou_> is there a kernel option that makes the function keys perform the function key function by default without pressing the fn modifier?
<rqou_> er, that was probably very confusing
<rqou_> is there something that does what "options hid_apple fnmode=2" does on x86 macbooks?
rikkaa has quit [Remote host closed the connection]
<rqou_> oh lol it outright still uses hid_apple on m1
<rqou_> nvm
the_lanetly_052 has joined #asahi
chadmed has joined #asahi
<chadmed> well im definitely stress testing the theory that these machines are unbrickable today
<chadmed> apple configurator is such a pile of crap
<marcan> < zamadatix> Hmm when I do the new installer desktop option after the "press enter to shutdown" it seems to actually do a reboot
<marcan> that is weird
<marcan> we literally do `shutdown -h now`... if it reboots at that point that has to be a macOS bug :/
<marcan> < tpw_rules> bigger-ish nit: u-boot's "boot the /chosen/asahi esp" patch from jannau is not in yet so multiple OSes doesn't really work <- that *should* be in there unless I screwed up?
<marcan> didn't test it though so I might've
<Glanzmann> marcan: I tried the installer yesterday two times, it was working quiet well.
<marcan> Glanzmann: ~100 people have run the official installer since I put it on alx.sh/dev fwiw
<Glanzmann> I also now know what I did wrong when I ended up in recovery os instead of 1tr. I have to press the key until I see the wheel and not until 'loading options'.
<marcan> no, that's not it
<marcan> you probably pressed it twice or too late
rikkaa has joined #asahi
<marcan> it's not about holding more, it's about what happened in the beginning
<marcan> once you see "loading options" it doesn't matter any more
<marcan> I've had it happen by accident too, it's just finicky and it's easy to accidentally release it momentarily, even if the button doesn't outright click
<Glanzmann> marcan: Strange. I'm pretty sure that I never let go. But now I hold until options and I don't have the issue. This happened to me on two airs and the mini. Anyway the installer works perfect.
<Glanzmann> And it happened at least 20 times to me.
rikkaa has quit [Remote host closed the connection]
chadmed has quit [Remote host closed the connection]
the_lanetly_052 has quit [Remote host closed the connection]
the_lanetly_052 has joined #asahi
the_lanetly_052 has quit [Ping timeout: 480 seconds]
<Glanzmann> marcan: Regarding the bunny cdn, I tested it from Germany, Ascona and Virginia. The first download was dog slow, the second was okay (like 20 MB/s) - all were on Gbit/s or faster. And one time it hanged for me.
<Glanzmann> marcan: Regarding streaming. tpw_rules used the following to stream a dd and I did, too. Never had an issue: curl -L https://tg.st/u/m1.tgz | tar -xOz | dd of=/dev/$identifier bs=8m
<Glanzmann> marcan: Wow, you added the Debian. Btw. The Debian image is behind a 10 Gbit/s link in Germany at Hetzner (not Falkenstein like your server, but Nuremberg). If it becomes a bottle neck I can add another 10 Gbit/s from Falkenstein/Hetzner within 10 minutes.
<Glanzmann> But since my image is only 349 MB, I don't expect an issue.
<Glanzmann> Oh you did not add the Debian, it was a local change.
<Glanzmann> marcan: In case you want to add it before the release, here is an updated patch (drops volume_id and makes it clear that is a user provided image - rename it like ever it fits for you).
<Glanzmann> And if anyone knows a parallel compressor for 'zip' please let me know. zip -9ing my 1.1 GB image takes too long.
<Glanzmann> marcan: Here is the patch I mentioned above: https://tg.st/u/0001-Entry-for-Debian-bookworm.patch
joske has joined #asahi
<joske> since 2 weeks or so, booting asahi linux now takes 5 seconds to initialize the crng. No idea why, and can't seem to fix it. Anyone has any idea why that is?
<joske> this wasn't the case before, booting in 2 seconds. I also didn't see it in marcan's video
<Glanzmann> joske: This my dmesg, can you paste yours? https://pbot.rmdir.de/Gylgt6iTbUXIDJW808I_KQ
<joske> Glanzmann: so for you it takes 2 seconds
<joske> before it would not do that at all, and boot straight to lightdm
guillaume_g has joined #asahi
joske_ has joined #asahi
joske_ has quit []
giskard has joined #asahi
<Glanzmann> joske: Strange. You also have an air and the same kernel version. And also Debian, but your hangs, mine does not.
<as400[m]> Glanzmann: pigz
<as400[m]> I believe it's in Debian repos
<mps_> we don't have hw rng driver, I think
<joske> Glanzmann: it's not running debian ;-)
<joske> just used debian pastebin
phiologe has joined #asahi
PhilippvK has quit [Ping timeout: 480 seconds]
<trouter> this is very exciting folks; I couldn't bear to wait so I'm giving the installer a go! Good tip in the apfs resize error message about APFS snapshots, I had over 100GB of them! Install is in progress now.
<trouter> What is the best place for feedback / bug reports etc? Or are you not quite ready for that yet? (I don't have anything specific right now just anticipating...)
PhilippvK has joined #asahi
MajorBiscuit has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
<marcan> mps_: we do have the bootloader seeding entropy though, which worked when I first set it up ages ago
irth has joined #asahi
<marcan> but I do recall seeing the CRNG init stuff pop up later recently, so maybe something has changed
<marcan> might be related to the RNG changes in Linux recently?
<marcan> I need to write up a page about feedback, but basically, pick the right project under https://github.com/AsahiLinux
PhilippvK has quit [Ping timeout: 480 seconds]
<marcan> for "general high level distro stuff/wishlist/etc" you can file under https://github.com/AsahiLinux/docs
<kettenis> the EFISTUB really wants the EFI RNG protocol to be implemented
<marcan> actually we do need a lot more documentation, so if anyone wants to start writing out docs... I'm putting together an announcement blog but the wiki could use some love
<marcan> also not just writing, also removing
<j`ey> 2ad310f93ec3d7062bdb73f06743aa56879a0a28
<marcan> I'm happy with folks going through pages and outright deleting stuff that is woefully obsolete or confusing
<kettenis> one solution would be to have a PRNG in U-Boot that gets seeded by rng-seed from the DT
<j`ey> 'In the past we didn't want the boot process to deadlock, which was understandable. But now, in the worst case, a second goes by, and the problem is resolved.'
<j`ey> joske: you could try revert 2ad310f93ec3d7062bdb73f06743aa56879a0a28 if you wanted a quick test
<kettenis> but my quick survey of appropriately licensed PRNG code didn't yield something suitable for inclusion in u-boot
<j`ey> joske: no idea if it reverts cleanly though
chadmed has quit [Remote host closed the connection]
<joske> j`ey: I'll try
<mps_> marcan: yes, I know, just wanted to ask 'somewhat rhetorical question'. hope RNG will be improved in next mainline kernel, I read that Jason Donefeld worked on it in latest -next series
<marcan> fwiw I'm not even sure if we know anything about the RNG in these machines, if there is one?
<marcan> it's not in the device tree
<marcan> the SEP driver does pull some randomness out of SEP on init, though
<sven> yeah, SEP has some "get random bytes" function
<mps_> would be strange if there is no HW RNG in apple machines
<marcan> I would *expect* the hardware to just have an RNG block somewhere accessible directly to the AP, it would seem very silly not to have that for apple
<marcan> but if there is one XNU doesn't seem to use it?
<sven> i also vaguely remember something about an RNG block but I can't recall any details :/
<marcan> FWIW there is a lot of hardware in these chips that we just know nothing about because XNU doesn't use it
<marcan> mps_: SEP *definitely* has a hardware RNG of some sort
<mps_> hwrng exists in my more than 10 years old macbook
<Sobek[m]> Would it be reasonable for the RNG to be in the SEP, to keep it further away from side channel attackers etc ?
<marcan> I would expect it to just have two
<marcan> one for SEP and one for AP
<mps_> it could be in TPM, but I don't know
<sven> yeah, i'd expect the AP to have a RNG somewhere as well
<sven> just like both SEP and AP have an aes engine
<Sobek[m]> mps_: A TPM in Apple Silicon ? Is that a thing ?
<mps_> Sobek[m]: have no idea, tbh
<sven> SEP does what you'd usually use a TPM for
<mps_> sven: makes sense
apg has joined #asahi
<sorear> feat_rng?
<marcan> the cpu does not have that
<marcan> no
<marcan> that is not implemented
<marcan> if there is a TRNG it'd be MMIO
<marcan> they definitely don't *use* an AP TRNG if it exists
<joske> j`ey: reverts cleanly, building
<sven> not sure we could actually find an AP TRNG if it exists though
<henje[m]> marcan: How could one find such an RNG, if the only way to understand the hardware is to look what macOS does?
<sven> we found DAPF and how it works even though it's not really used by XNU, but there we had a rough idea what it does
<sven> if you have a rough idea and some way to observe changes you can figure those things out by changing register values and checking what happens
<sven> I guess we could look at some of the older SEPOS that can be decrypted, figure out how the TRNG works there and just assume that if an AP TRNG existed it would use the same interface
<Sobek[m]> What's DAPF ?
joske has quit [Quit: Leaving]
<sven> some DART extension that allows to configure which areas of address space go to DART and which are identity mapped to some other place
<sven> it's a separate MMIO space that exists just after some DARTs. it's used by iBoot for DCP but there's another one for the aes engine and other stuff that's not used by anything
joske has joined #asahi
<joske> with that commit revert, much faster: https://paste.debian.net/1234804/
<j`ey> well good that we found it, bad that.. that might be hard to solve!
<joske> yes as it's an upstream change?
<j`ey> yeah
myon9821 has quit [Ping timeout: 480 seconds]
<sven> ah, I remember now, apparently there’s a command you can send to seprom that generates 4 bytes of random data
<Glanzmann> as400[m]: pigz can only compress a single file.
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
kov has joined #asahi
chadmed has joined #asahi
<mps_> if I enable CONFIG_DRM_FBDEV_EMULATION=y kernel hangs on boot when switches to framebuffer :|
* j`ey has that enabled
myon98 has joined #asahi
<mps_> j`ey: iirc you use mbp (j293 model)
<j`ey> j313
<j`ey> so air
<mps_> hmm
LuEvers[m] has joined #asahi
<sven> >>> s.get_rng()
<sven> SEPMessage(EP=0xff, TAG=0x0, TYPE=0x74, PARAM=0x0, DATA=0xe7fa6e0c)
<sven> yup.
<sven> SEPROM supports a simple "get random bytes" message
<sven> it's also relatively simple to implement and doesn't need any handover, etc. if the actual OS wants to support SEP in the future
PaterTemporalis has joined #asahi
<povik> we can use the lower bits of the temperature sensors :p
chadmed has quit [Remote host closed the connection]
<povik> there's plenty of them
<povik> btw AOP has DAPF, and i thought that coprocessor is set up by XNU
<sven> iirc uninitialized DAPF just means everything goes through DART
<sven> or maybe iBoot configures them like that
<povik> it's not uninitialized though
<sven> but XNU doesn't have a DAPF driver iirc
chadmed has joined #asahi
<sven> or, well, it does, but it's never created in the device tree
<povik> there are entries, let's see if iboot leaves them there
<sven> maybe it changed with 12.x, but 11.x XNU never wrote to any DAPF
<povik> this is 11.x i am still running
joske has quit [Ping timeout: 480 seconds]
<sven> pretty sure that XNU never touched DAPF
<sven> there's no dapf,t8020 in the device tree
trevyn2[m] has joined #asahi
<povik> yeah, AOP's DAPF is unitialized before XNU runs, initialized once it starts
<povik> not that it means much
<sven> that's.. weird
<sven> what initializes it?
<povik> i can trace it but without symbols don't know how much it's worth
<sven> oh god...
<sven> i think i know what apple did
<chadmed> "always on" except for when its not, which is seemingly a lot of the time
<sven> there's filter-data-instance-0 in the DART node
<sven> wanna bet they hacked the DART driver to just initialize DAPF with that?
<sven> that's so much more fun than using the actual driver they have!
<povik> ha, can confirm filter-data-instance-0 is it
<sven> lol
Ry_Darcy has joined #asahi
<Ry_Darcy> Thomas Glanzmann produced a (youtube) video in February 2022 outlining steps to install Linux on an apple M1. Is this video still current and up to date?
<kettenis> no
<Ry_Darcy> I already have the M1 running Debian native using Pipcet's instructions. However, wireless is not working and my subjective view is that the NVME throughput rate is somewhat slow. I would prefer to try the Asahi installer at this stage.
megalokafes has joined #asahi
<Ry_Darcy> no what?
<kettenis> it is not current and up to date
<j`ey> Ry_Darcy: https://tg.st/u/debian_asahi_installer.mp4 this is a video from yesterday
<Ry_Darcy> Merci.
<Ry_Darcy> @kettenis - thank you.
apg has quit [Quit: Leaving]
<j`ey> pipcet went on their own path, and his stuff is definitely going to conflict when asahi's changes are in
<Ry_Darcy> He disappeared from my radar at the end of December 2021. Have not heard from him since. I am currently running a hacked 5.15 kernel on the M1. I think I will try the Asahi way. Thanks for the information.
<j`ey> Ry_Darcy: and there is a change in asahi's nvme code that should help a bit with flush speed
<j`ey> (.. by not flushing everytime)
<Ry_Darcy> All good stuff. Thanks.
<bluetail[m]> Wasn't there a thing mac does wrong with flushing and making data losses more pronounced on loss of power?
<bluetail[m]> I forgot
<bluetail[m]> I cant give details :/
<Ry_Darcy> My M1 is currently running mac os 12.1 - I presume this is new enough to be compatible with the latest Asahi installer?
<j`ey> Ry_Darcy: upgrade to 12.3
<Ry_Darcy> I will have to see what is in the update queue. I rarely if ever use mac os. As long as they do not want to bump me to 12.4...
<mps_> Glanzmann: using you kernel config i got text console, so I must have something really stupid^Wstrange in my config
<j`ey> Ry_Darcy: 12.4 isnt a thing yet :)
<Ry_Darcy> Am on the road at the moment. Will update this evening. Thank you for the heads up.
<j`ey> Ry_Darcy: no offense to pipcet, but the way he was doing stuff was not really upstreamable
<Ry_Darcy> https://tg.st/u/debian_asahi_installer.mp4 Are there any written instructions (caveats/tips etc.) for this video?
kameks has joined #asahi
<giskard> hi, assuming I'll run |
<giskard> curl ... | sh -- how much will it differ tomorrow when the installer gets released
<giskard> (sorry I thought I had it in my clipboard..)
<Ry_Darcy> https://tg.st/u/debian_asahi_installer.mp4 I see Thomas is now running an RC kernel (5.17). Will I be able to update this subsequently or will I be stuck with rc6? Can I also put a normal (xfce, lxwt) desktop on top of this when the install is finished?
<Ry_Darcy> Pardon lxqt.
<kov> Ry_Darcy, note that the debian installation is not formally supported by the asahi team, but I have used everything with success
<j`ey> Ry_Darcy: yes everything debian will just work (probably)
<kov> Ry_Darcy, we're now at -rc7, you can't upgrade with upstream kernels yet as not enough is upstreamed, but you can upgrade with new releases from the asahi branch
<j`ey> giskard: unlikely anything will change
<Ry_Darcy> Perfect!
<Ry_Darcy> At some stage, I presume I will be able to compile my own kernels also?
<kov> Ry_Darcy, and yeah like j`ey said it's just debian otherwise, you just need to keep in mind the hardware stuff that is not yet supported - gpu acceleration is not yet supported, for instance, so you will get software rendering
<kov> Ry_Darcy, you can already, you just need to use the asahi branch, the wiki has more information
<kov> you can use the config from the debian package after the install as the base
<giskard> j`ey thanks -- will give it a shot today -- hopefully i wont bork stuff
<j`ey> giskard: pretty unlikely :)
<Ry_Darcy> Thanks. I am not a gamer or eye-candy fethist. I can live with the software acceleration.
<Ry_Darcy> Fetishist. Mea culpa.
<j`ey> Ry_Darcy: its not just about that, GPU will also mean the CPU does less rendering and can do more useful stuff :P
<immychan[m]> Ry_Darcy: You’d be surprised lol
<Ry_Darcy> Quite.
<kov> I am both a gamer and a fetishist =(
<immychan[m]> Even stuff like playing full screen video is a no go without GPU drivers
<Ry_Darcy> Best of both worlds :)
<j`ey> immychan[m]: no? it works fine
<immychan[m]> Not for me, it lagged like crazy when I tired
<kov> works fine for me as well, these cpus are quite fast and the memory bandwidth is crazy
<immychan[m]> I’ve never had it work
<dottedmag> on m1?
<immychan[m]> Maybe it’s because I’m trying it with a 4.5k iMac display though lol
LiteChen[m] has joined #asahi
<kov> btw I was so surprised with how well it scrolled pages on firefox, I spent so much time working on tiled backing stores and accelerated compositing to make these things smooth with GPUs, and here's this CPU delivering ;D
<brentr123[m]> Yeah the M1 cpu is godlike
<Ry_Darcy> The documentation - https://github.com/AsahiLinux/docs/wiki/Debian indicates a USB stick is needed initially, I presume I will be able to boot from the NVME at the end of the initial install?
<j`ey> a usb stick isnt needed
<j`ey> the installer can install an image onto the nvme
<mofux[m]> hellp helpfull people and thanks for all the work. what's the best way to undo what an previous installer did? i want to reinstall with the newest installer.
<j`ey> mofux[m]: erase all the partitions with diskutil
<j`ey> assuming you dont care about any of the data
<chadmed> https://github.com/chadmed/asahi-audio <- ok so this actually works now plus it sounds significantly better than it did when it didnt work anyway, so if anyone would like to test this on their 14 or 16 inch MBPs, thatd be nice
<opticron> oooh
<chadmed> i cracked the code on the subwoofers, turns out the "primary" drivers are actually the subs :P
<opticron> lol
<opticron> I'll have time to give it a try this afternoon (currently 8am here)
<chadmed> apologies to anyone who went to try it last time and it didnt work. that was just me being stupid and not doing QA
<dan[m]123> Does it work for 2020 MBP?
<j`ey> no
<chadmed> no sorry, trying to put together some money to buy more machines and do them. i only have a 14" mbp, and 16" support only comes by way of them having very very similar speaker arrays
<giskard> chadmed if there is something special you want me to test on a 16inch let me know
<chadmed> just if it sounds good, really
<giskard> assuming I can install debian on it today
<chadmed> yeah, just chmod +x the shell script and run it as root
<opticron> I bet Glanzmann will get there before I do :D
<j`ey> chadmed: you probably can work with markan rather than buying a m1 2020
<chadmed> oh and i need to add a step to the readme because pipewire does even less than i exected it to, you need to set the hardware device to the "Pro Audio" profile for it to work properly
<chadmed> shame i got no nibbles on that feature proposal :(
<Ry_Darcy> Not wanting to be pedantic, the docs state that a USB stick is needed for the installation. Maybe I have overlooked something?
<chadmed> j`ey: yeah ill write up a SOP at some point so that marcan (or anyone else who thinks theyve got the ears for it :P) can help but im just a bit swamped with other stuff at the moment to be writing technical manuals
<chadmed> like 90% of the time i spent on this was bumbling around with alsa, jack and pipewire too heh
<Ry_Darcy> @j`ey had nott seen/read this. Thanks.
<Ry_Darcy> not
lep[m] has joined #asahi
<Sobek[m]> Will this sort of configuration be integrated in the installer eventually, (or at least some safe setting), so that out of the box a asahi linux install won't blow up its speakers unless someone overrides the audio settings ?
<povik> of course
<povik> it's like this only because it's work in progress
<chadmed> marcan, povik and i would like to see pipewire gain some new functionality (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2210) to make this so transparent that all we have to do is ship a package
<chadmed> but we cannot work under the assumption that this will happen, so yeah i would guess that we will have to ship this sort of stuff as part of an installer until pipewire gains this functionality
<mofux[m]> j`ey: this is my current distkutil list layout. i'm not sure what to delete here. any help is very appreciated: https://pastebin.com/zdyRxwNS
<chadmed> not to mention that pipewire having this functionality would fix thousands upon thousands of other types of devices too and make audio in linux userspace SIGNIFICANTLY nicer than it is today
<chadmed> which is why it wont happen ;)
PhilippvK has joined #asahi
<povik> oh the 'linux can't have nice audio' rule
<povik> i think that's merely a myth :p
<chadmed> well depends how you look at it imo
<chadmed> if you have the time and knowledge to set it up properly, its fantastic
<chadmed> but the OOBE is utterly atrocious and getting to a stage where you have sufficient knowledge to make it better is basically impossible for the average user
<Sobek[m]> chadmed: Anything one can do to help you with this (as a user, I have way too many thing on my todo list rn (including improving a async-signal safe, non mallocing snprintf function to make it suitable for general use))
<j`ey> mofux[m]: read the help when you run 'diskutil apfs erasePartition' first, but you want to erase disk0s5 and disk0s4 and disk0s3
<mofux[m]> will do, thx alot!
<chadmed> Sobek[m]: pretty much just testing unfortunately. i have some pretty specialised and equipment and specific set of skills which make doing this efficiently and correctly possible so its not something you can really reproduce unless you have a calibration mic, certain software, a "real" audio interface, etc
<chadmed> feedback is good though! what i think sounds good may not be to everyones tastes, so knowing what people want to hear is beneficial
<Sobek[m]> I was talking about the pipewire feature request side of things
<chadmed> ohhhhhh
<chadmed> we could brigade the pipewire devs :P
<Sobek[m]> (One of those day, I'll spend some time to give penguins a foothold on my computer, but I need to deal with backups first)
<chadmed> nah i think the best thing to do would be complain about the things i list in the feature proposal
<chadmed> as i said, so many devices like this are going to be coming to market and as people flee windows theyre going to wonder why their laptop has started sounding like shit all of a sudden
<chadmed> but id we rather fix the problem before that happens
PhilippvK has quit [Ping timeout: 480 seconds]
phiologe has joined #asahi
<mps_> meh, looks like I found what was issue with my text console. my local patch for terminus 12x24 fonts which worked with previous kernels doesn't work now
<j`ey> oh :|
<mps_> I have to repeat my lecture number one: always start with clean tree and add thingies later
<daniels> marcan: looks like you're getting opinions on keyboards :)
<mofux[m]> twp_rules: thx, this worked!
Tom[m]12345678910 has joined #asahi
YJSNPI has quit [Quit: ARRRRRRRRRRRGH]
YJSNPI has joined #asahi
<spokv[m]> Hi to all! Sorry for maybe posting in the wrong place but...I'm a skilled embedded software engineer with some reverse capabilities, and would like to contribute to this project. Please let me know if & how I can help...BR.
<zv> spokv[m]: do you have m1 mac hardware?
<spokv[m]> Yep
<spokv[m]> Macbook air m1
Tom[m]12345678910 is now known as ping_47
yuyichao has quit [Ping timeout: 480 seconds]
<kov> spokv[m], the wiki on the topic is probably a good place to start, it has a bunch of docs on what is already known and guides for getting m1n1 working to explore the hardware and linux installed
chadmed has quit [Remote host closed the connection]
<giskard> but apparently my drive is locked? (even tho I "logged in") https://paste.debian.net/hidden/9b74b65f/
<spokv[m]> If any of you can guide me for a specific task I'm sure I could contribute, just need a kickstart...
YJSNPI has quit [Quit: ARRRRRRRRRRRGH]
phiologe has quit [Ping timeout: 480 seconds]
<spokv[m]> OK I'll try starting there.. Tx
YJSNPI has joined #asahi
<kov> spokv[m], I'll tell you what I'd like to see soon, webcam support ;D I guess it's the main thing remaining for a full work from home setup hehe
<kov> and I don't think there's anyone looking into that yet
<M1bn3mar[m]> Hey, does this mean that it doesn't have backlight or what??
<M1bn3mar[m]> MacBook Pro (13-inch, M1, 2020)
<M1bn3mar[m]> Backlight unsupported
<j`ey> M1bn3mar[m]: correct
<kov> M1bn3mar[m], the backlight can currently be turned off
<kov> but brightness cannot be set
JonathanBuchholz[m] has joined #asahi
<tpw_rules> giskard: are you logged in with an administrator account? try rebooting and running it soon after
<M1bn3mar[m]> j`ey: kov so it turns on just like ubuntu right?
<kov> M1bn3mar[m], yeah, you get a working screen, and you get power savings when the screen is turned off
<giskard> tpw_rules, yeah there is only one account, and I'm running it from Terminal from the recovery partition
<tpw_rules> giskard: oh, try your main macOS install
<kov> so you can close the lid and it'll be using less power
<tpw_rules> giskard: also that partition size question is asking what size you want to reduce your macOS partition to. do you really want to make it as small as possible?
<M1bn3mar[m]> kov: ok thx, that's good enough 4 me.
<kov> but you get a headache if you use it for too long in a dark room ;D
<M1bn3mar[m]> @kov yeah sure
<spokv[m]> <kov> "spokv, I'll tell you what I'd..." <- OK I'll start by bringing up my setup...
<tpw_rules> giskard: i wonder also, do you have filevault set up?
<giskard> yep I do
<giskard> filevault, ok, so the resize is the other way around
<M1bn3mar[m]> Hey, is it possible to just install a minimal distro like gentoo, for a guy who just know's how to install linux with a gui
<tpw_rules> giskard: ah, that might be the problem. the recovery partition wouldn't be able to touch your macOS install without loading the keys and evidently diskutil doesn't know how to ask for them
<M1bn3mar[m]> s/a gui/cli/
<tpw_rules> i would run the install script from your man macOS install. it's safe to run the resize live, although other stuff might freeze temporarily if it tries to access the disk while the resize is in progress
<tpw_rules> and yeah, if you only want to take away 50GB for linux, answer 944GB to that question
<giskard> might be my poor command of the english language but maybe should be rephrased? maybe it was totally me
yuyichao has joined #asahi
<tpw_rules> i agree, i don't think it's made clear
<j`ey> M1bn3mar[m]: the asahi installer offers to install a minimal archlinux based distro
<j`ey> with no gui
<tpw_rules> well i think it's clear, but that the user isn't expecting the question that way so it's hard to process. i'm not sure what the solution is
<Glanzmann> M1bn3mar[m]: You can choose between arch and debian at the moment. Also there is a debian live which allows you to install most distributions which have a rootfs.
<tpw_rules> (you can also choose nixos)
<j`ey> or openbsd etc :P
<giskard> tpw_rules make it clear. "This is the space that will be reserved to the MacOS installation"
<Glanzmann> j`ey: OpenBSD has been ready for end users since ages. I need to do a video and put it on the wiki.
<Glanzmann> It even has my favourite window manager as default.
<Glanzmann> Only thing missing from OpenBSD is firefox, but they have chrome.
<M1bn3mar[m]> ok, if choose to install it through a live env what should i replace from the wiki like the pm 4 exp
<spokv[m]> Does using fedora 35 as host/build machine recommended?
<j`ey> should be fine
<giskard> tpw_rules running it not from the recovery partition seems to work fine.
<tpw_rules> giskard: good to know
<M1bn3mar[m]> *gentoo wiki
<tpw_rules> yeah, i am pretty sure now that it's because your filevault volume was not mounted in the recovery OS. it probably would have worked if you had gone into disk utility and manually mounted it and entered your password
<giskard> re-reading the messages after what you said made it clear. Still I believe it should be in bold, is this the installer right? should I open a issue?
<j`ey> open an issue, it cant hurt
<giskard> tpw_rules FWIW recovery asks you to unlock the hdd and from the utility I could see it (although not mounted)
<tpw_rules> about the filevault or the partition wording?
<giskard> both?
<tpw_rules> probably wouldn't hurt
<giskard> OOC: Enter a name for your OS -- that's not the final hostname right?
<giskard> is just labeling the partition?
<j`ey> yep
<tpw_rules> yeah, that's what it will show up as in the boot picker
<tpw_rules> once you boot it it will ask for a hostname during the installer flow
<M1bn3mar[m]> hey, if manually install gentoo, should i only replace m1n1 with grub and the kernel and that's it?
<tpw_rules> m1n1 is independent of grub and shouldn't be touched
<tpw_rules> install whatever UEFI-compatible boot loader you want with gentoo, there's nothing specific to m1 there. just make sure it does not load a device tree
<j`ey> M1bn3mar[m]: you dont replace m1n1 with grub
<tpw_rules> and that is installed in the removable path, i.e. \EFI\BOOT\BOOTAA64.EFI
<j`ey> u-boot loads grub
<trouter> I couldn't find in the wiki if adjusting the screen brightness is supposed to work. Under both KDE and Gnome, if I turn it down from max the screen immediately goes black. Is that expected?
<j`ey> it isnt
<j`ey> it isnt supposed to work
<trouter> gotcha, thanks
<trouter> on the plus side the keyboard brightness keys work :D
<j`ey> heh
<trouter> "Backlight" in https://github.com/AsahiLinux/docs/wiki/Feature-Support - does that mean keyboard backlight or display? Guessing keyboard; I can add an entry for display brightness there perhaps?
<giskard> \o/ good job folks
<giskard> and thank you Glanzmann for the base image I guess I have to trust you no keylogger has been installed :)
<j`ey> trouter: add it to feature support, Tasks is old
<trouter> j`ey: sure, will do
creechy has joined #asahi
bisko has joined #asahi
tweets_so_fresh_ has quit [Quit: Connection closed for inactivity]
<Glanzmann> giskard: There is no keyloger or any other malicious code in my image, but better test yourself: https://pbot.rmdir.de/XSXJqOvhfrlCTeakrleh4A
<Glanzmann> giskard: This is the script that I used to build the image, you can also build it yourself: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/blob_plain/refs/heads/master:/bootstrap.sh
<giskard> btw is quickstart.txt meant to be accurate?
<j`ey> no
<j`ey> oh .txt
<giskard> that was meant for Glanzmann, it's in /root/quickstart.txt
kameks has quit [Ping timeout: 480 seconds]
creechy has quit [Ping timeout: 480 seconds]
<Glanzmann> giskard: It covers multiple things (live and installed) systems. A lot of stuff is obosolete.
<Glanzmann> giskard: At some point I'll clean it up.
<giskard> :) btw the whole thing is great I just had to update wpa_supplicant and ifup ... and it works
<giskard> wonder if debian (I should know) provides geoip ready mirrors
<Glanzmann> giskard: Maybe https://deb.debian.org/
<Glanzmann> there is also a cdn from aws and azure.
<Glanzmann> giskard: Btw. wpa_supplicant is very easy to configure, but iwd might give you better performacne especially if you have a fast internet connection and 5ghz wifi.
<giskard> oh thanks for letting me know
bisko has quit [Ping timeout: 480 seconds]
<Glanzmann> giskard: So personally I use iwd after mps introduced me to it. And I prefer the 5ghz wifi over the 2ghz. But I only started to care after I got a fibre connection at home (before 10 MB/s) was enough for me.
<giskard> Im lucky enough to have fiber and a 5ghz network so I would love to take advantage of it
creechy has joined #asahi
bisko has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
<mofux[m]> Got Asahi reinstalled! Awesome work on the installer in such a short amount of time. everything worked flawlessly (M1 Air). Thanks a lot folks!
creechy has joined #asahi
AlbertoBasaglia[m] has joined #asahi
<Glanzmann> giskard: Find the iwd instructions for iwd at the end of the new quickstart.txt https://tg.st/u/quickstart.txt
bisko has quit [Ping timeout: 480 seconds]
the_lanetly_052 has joined #asahi
<Glanzmann> giskard: I improved the quickstart further: https://tg.st/u/quickstart.txt
<Glanzmann> And cleaned out the irrelevant stuff.
leo60228- has joined #asahi
leo60228 has quit [Ping timeout: 480 seconds]
<giskard> thank you!
<Glanzmann> giskard: So about the filevault note. Did it work for you from the macos live system (1tr)?
<Glanzmann> Or did you disable filevault?
<giskard> I didn't disable filevault. When I rebooted into recovery mode first thing was asking for my password to unlock filevault. I guess that when I exited the "Recovery.app" into Terminal it got locked / unmounted
<dottedmag> marcan: russian layout (code=1f) needs a variant 'mac'. Also, ru layout does not include English, shouldn't it be added as a second layout?
<giskard> although the installer found the disk et all so :shrug:
<Glanzmann> giskard: Because the Debian soon to be asahi installer guide tells you to boot into 1tr. So if you're saying it is working in 1tr, than we don't need the note. That is why I'm asking.
<dottedmag> marcan: Also, forked xkeyboard-config repo has issues disabled
guillaume_g has quit []
<giskard> I wish I could be 100% sure I did it. I think I did. Should be safe to retry right?
<Glanzmann> giskard: If you know what you're doing. So you need to delete all the partitions. Maybe I'll try it myself and update the wiki accordingly.
<giskard> I need to delete the "Debian" labeled partition right?
<giskard> and then re-use that existing space
Ry_Darcy_ has joined #asahi
ckie has joined #asahi
<tpw_rules> Glanzmann: everything works fine from macOS
<tpw_rules> i would suggest doing that
<giskard> true
<tpw_rules> because it means you are certain the partition is mounted, you are in the right OS, have the right credentials, etc.
<Glanzmann> giskard: I added a section at the end of the quickstart which tells you what you need to do: https://tg.st/u/quickstart.txt
<tpw_rules> the only pitfall i've found is that the system gets cranky if you try to do things while diskutil is busy because i think it locks the disk to itself. so stuff starts freezing trying to access the disk
<giskard> you can't have the cake and eat it too I guess
<Glanzmann> giskard: Or, as tpw_rules says, use his guide to do it from macos: https://github.com/tpwrules/nixos-m1/blob/main/docs/uefi-standalone.md
<Glanzmann> giskard: I always prefer doing it from Linux, because it is faster.
<giskard> tpw_rules (et all) https://github.com/AsahiLinux/asahi-installer/pull/27 feel free to discard it but I guess it would help
<j`ey> giskard: you need to add a 'signed-off-by' in your commit
<ckie> seeing the progress in here makes me wish my thinkpad /wouldn't/ last like 5 more years
<LuEvers[m]> xD
<LuEvers[m]> well i didn't expect it worked so gooood
<LuEvers[m]> i just reinstalled from mac-os using the alarm rootfs, and it feels even better
Ry_Darcy_ has quit [Quit: Page closed]
<tpw_rules> ckie: you could do what i did with my old macbook and spill water all over it... (rip)
<ckie> tpw_rules: never had a mac before :P
<tpw_rules> they aren't waterproof yet
<ckie> always thought apple isn't worth it until they did this
<threerik[m]> hey all, does asahi support booting from linux installs on external drives (provided m1n1 is installed on the system disk of course as iBoot doesnt)? i tried looking at the wiki and couldnt find much, but i also suck at finding things haha
<j`ey> threerik[m]: yes u-boot can boot off a usb drive
<ckie> has anyone tried to get nixos working with asahi yet?
<tpw_rules> i spent a healthy amount of time on it and imo it works really well
<threerik[m]> j`ey: oh thats really cool. i have a 512gb mac so having linux on my external ssd would be great to save space. Thanks a lot
<tpw_rules> threerik[m]: do note that at this time the fastest access you'll get is USB 2.0
<ckie> tpw_rules: nice.. now I just need a mac XD
<threerik[m]> tpw_rules: oh... yeah that could be a bit rough
<Glanzmann> tpw_rules: Btw. the mini has USB 3.1 on the usb-a ports.
<Glanzmann> And also sven posted some output of usb 3.1 on usb-c so maybe we have that soon, too.
<nilsi[m]> Is there any instructions now on how to install the alpha with the arch distro?
<sven> yeah, plan for this weekend is to prepare the nvme submission and clean up the atcphy code for usb 3 support on the type c ports
<j`ey> Glanzmann: but uboot cant use those currently!
<tpw_rules> nilsi[m]: just follow the prompts, really
<Sobek[m]> https://github.com/AsahiLinux/docs/wiki/%22When-will-Asahi-Linux-be-done%3F%22 <- I laughed, my congratulations to whoever wrote this great piece of an answer !
<nilsi[m]> Alright just thought I missed something, since it seems like people are installing it now
<Glanzmann> j`ey: Good argument, but you could use the old u-boot which can or have the boot partition on usb-c and than boot from usb-a. :-)
<tpw_rules> nilsi[m]: there will be official instructions very shortly. but it really is pretty simple. boot into macOS, log into an administrator account, open Terminal.app, and run: curl -L https://alx.sh/dev | sh
<tpw_rules> then follow the prompts
<Glanzmann> nilsi[m]: 11:38 <marcan> new installer is up: curl -L https://alx.sh/dev | sh
<Glanzmann> And ollow the prompts. Okay I'm toooo slow.
<nilsi[m]> Ah, great! Thanks!
<Sobek[m]> Speaking of the keayboard thing, the french keyboard also use a mac layout, but I don't know off the top of my head which, and my Intel laptop died a few weeks before apple announced the M1Max MacBookPro from which I'm writting those lines. (And the Mac variant of the French keyboard is definitely better than normal Fr layout)
* Glanzmann uses us keyboard since about 21 years. :-)
bisko has joined #asahi
bisko has quit [Ping timeout: 480 seconds]
<Sobek[m]> Now, how do you write Paté, Garçon, and all the other cool French word with the proper accents, even when shouting ? (ÀÉÈÊÇ is not a word, but all these letters are easy to type on a proper Fr(mac) layout :P)
<Glanzmann> Sobek[m]: I use 'de_se_fi' which allows me to use the left meta key + aeous to produce äöüß.
<giskard> j`ey fixed...
<maz> A compose key sorts this out pretty easily. I write in French often enough, and yet have standardised on a UK keyboard for... too long.
<LuEvers[m]> hey guys, where could encryption be implemented?
<LuEvers[m]> in the partitioning of the installer?
<marcan> the installer is unlikely to implement encryption any time soon, you'd have to reimplement LUKS in python or something, or drag around more tools
<tpw_rules> or just boot off a live USB and do it yourself
<marcan> for people who want more complex storage setups the expectation is they will boot a normal distro installer from USB using the UEFI image
<tpw_rules> ^
<Sobek[m]> Anyway once you have U-boot, you can setup everything as you would any other linux on ARM system.
<marcan> I might look into supporting encryption in the installer once we have SEP and all that fun stuff, since at that point it will be worth having and supporting properly
<marcan> could also do one of those "self-reencrypt on first boot" things like android used to
<LuEvers[m]> cool!
<M1bn3mar[m]> hey guy's i tried gentoo using qemu in macos it sometime's fail's to compile some package's like webkit-gtk & llvm would this be a problem with asahi?
<LuEvers[m]> speaking of FDE i think it will be very difficult
<marcan> that sounds like a RAM issue
<Sobek[m]> Lu Evers: why that ?
<LuEvers[m]> you'd have to recreate the LUKS container on a completely fresh partition. so it would need a second partition / image containing a small rootfs with the needed tools (cryptsetup) to boot at first (after creating the apfs container for asahi), boot that, create the luks + boot + efi partition, and extract the ashai image to it
<LuEvers[m]> or do the procedure inside macos with docker (or any osx tool to create luks)
<Glanzmann> LuEvers[m]: You can use the Debian installer.
<Glanzmann> LuEvers[m]: Or Debian live system.
<sven> i mean... pretty much any distro installer can do FDE
<j`ey> marcan: the new -C parma for run_guest.py, it's just a number? -C4 for 4 CPUs
<sven> and i also remember some tool that allowed in-place encryption for LUKS
<j`ey> (not for CPU4)
<LuEvers[m]> yep, im talking about alarm, where no real live cd exists :D
<LuEvers[m]> (and that was the i installed it with the asahi script)
<Glanzmann> So basically you do what is mentioned in the tg.st/u/quickstart.txt and just run 'cryptsetup luksFormat $DEV_CRYPT' and 'cryptsetup open $DEV_CRYPT $CRYPT_NAME'
<Glanzmann> LuEvers[m]: You can install alarm also using the debian live system.
<Sobek[m]> So it depends what you are trying to encrypt, but I'd say, you'd have U-boot hand over to a cryptsetup et al partition, that can then prompt for the password and unlock the LUKS, as any boot process does. You just need to make sure everyone is using the right kernel (and drivers).
<Glanzmann> Everything you need it to fetch the arm rootfs.
<marcan> j`ey: it's a list
<LuEvers[m]> ahh yes that is true
<marcan> like 1-2,5,6-7
<j`ey> marcan: oh
<marcan> starts at 0
<marcan> though you always want to include 0
<Jamie[m]1> I had a dumb idea and had to implement it: using http range requests and DEFLATE trickery to download Wifi firmware from Apple's CDN with only 18MB of transfer (out of a 13GB ipsw) http://github.com/JJJollyjim/firmware-abomination
<marcan> Jamie[m]1: that is already what we're doing
<Glanzmann> Jamie[m]1: \o/
<marcan> except we have to download the whole recovery image anyway
<marcan> but not the rest of the ipsw
<Jamie[m]1> marcan: ah neat lol
<Jamie[m]1> didn't notice that :P
<marcan> we only download ~1GB or so
<Jamie[m]1> still, 18MB < 1.8GB :P
<marcan> see urlcache.py
<marcan> well sure
<marcan> but I mean we need the whole 1.x GB anyway
<Jamie[m]1> yeah fair
<tpw_rules> Jamie[m]1: also the problem is that the wifi firmware is kind of specific to the 1.x GB downloaded recovery image
<Jamie[m]1> i'm thinking of a specific nixos usecase
<tpw_rules> i looked into doing something like yours for my guide but i think pulling it manually from the ESP is a better move
<Glanzmann> tpw_rules: The wifi firmware 12.1 worked for me for the 12.3 stub without an issue.
<Jamie[m]1> tpw_rules: definitely a better move lol
<sven> iirc the apple firmware files are also renamed to something linux will understand
<marcan> yes
<Jamie[m]1> yeah, i'm gonna run wifi.py on this directory afterwards
<marcan> but also, I'm not sure I see what is more "pure" about downloading the firmware from apple's CDN vs grabbing it from the ESP
<marcan> in both cases you're relying on third parties ;)
<marcan> as long as you hash check it what's the difference?
<tpw_rules> Jamie[m]1: did you see my nixos guide?
<Glanzmann> marcan: And also, you can't download it if you don't have wifi at least in most models. :-)
<Jamie[m]1> actually i'm not sure if nix's build sandbox allows local filesystem access for fixed-output derivations
<marcan> heh
<Jamie[m]1> but it's purer in the sense that it can be built on any machine
<marcan> sure
<tpw_rules> Glanzmann: that's why i said "kind of". it's not guaranteed to remain compatible
<marcan> Jamie[m]1: I'm going to save that trick though, because if we ever end up needing something from the *macOS* image, that's when it'll come in handy
<marcan> it does have more firmware than recovery mode, but I don't *think* we need any of that
<Glanzmann> sven: Yesterday you appeared to be on your mobile phone (from your comments) - what do you use to chat from a mobile phone on irc?
<j`ey> argh usb is cursing me today :<
<sven> usb is *always* cursing everyone everyday. you just sometimes don't notice.
<Glanzmann> j`ey: Turn it off and on again.
<sven> Glanzmann: uh, just some web client
<Glanzmann> sven: Ah you use znc from your username, I see.
<j`ey> sven: but some days it works fine, otherdays.. not at all.. why??
<sven> the usb curse works in mysterious ways!
<Sobek[m]> Speaking of the SEP - FDE vague idea, what would using SEP bring, and at which point in the process would it get used ?
<Sobek[m]> (Would that require only Linux kernel support, or is his something where m1n1 would be dealing with the SEP and the encryption stuff ?)
<sven> j`ey: so what exactly doesn't work?
<Jamie[m]1> Sobek: (speaking in general terms) it allows you to use a weaker password or biometric auth, and the SEP ratelimits password/biometric attempts and releases the encryption key when it likes what it sees
<j`ey> sven: it's just that my host doesnt see m1n1's ttyACM* devices
<Jamie[m]1> that's how you can decrypt your phone without a 4-digit pin without someone easily brute-forcing it in 10000 attempts
<Jamie[m]1> s/without/with/
<j`ey> sven: or they show, then disappear!
<sven> ah :D
<marcan> it also allows you to tie the encryption to the hardware, to resist offline attacks
<marcan> and it also has a backdoor key channel to the NVMe controller, which means even *Linux* doesn't have the decryption key so malware can't steal your FDE key
<marcan> (it'd have to outright steal all the data)
<Sobek[m]> On the other hand this means that if your hardware dies you can't the data out, but that's already the case anyway with M1 macs ?
<marcan> pretty much
<Glanzmann> j`ey: For me this happens most of the time when my air tries to charge over these cables.
<marcan> of course, it doesn't mean you *have* to use all these features
<Sobek[m]> marcan: This would mean you would not be doing LUKS, but a Apple Silicon SEP specific thing ?
<marcan> you could not rely on the back channel, and then Linux would control the volume key so it could have a key recovery mechanism
george147 has joined #asahi
george14_ has joined #asahi
<marcan> well, I think the encryption is probably compatible with some dm-crypt mode anyway
<marcan> but yeah, you could use it in different ways
<marcan> you could use it purely to unlock LUKS keys
<marcan> or you could offload the encryption and then it's kind of academic what algorithm is used because you don't have the key anyway
<Sobek[m]> One would hope so, or that it can be reversed engineered so that dm-crypt can implement the specific variation used.
<george14_> Any idea when a possible release date might be? Getting very excited from the twitter posts... I'm happy to beta test/do extra setup to get it soon
<marcan> there's probably some way of provisioning raw keys
<marcan> which would allow us to use it as a dm-crypt accelerator without changing any semantics
<Glanzmann> george14_: Yesterday.
<george14_> Yesterday?
<marcan> it's not officially announced yet
<Glanzmann> It was planned, but delayed due to lack of sleep.
<Glanzmann> george14_: curl -L https://alx.sh/dev | sh
<marcan> due to lack of sleep, github going down, building images taking longer than I expected, making stupid mistakes, ...
<marcan> :p
<Glanzmann> lack of sleep is the root cause, rest is just symptoms. :-)
<tpw_rules> marcan can take down github?
<marcan> good to know my ^ yeah that
<george14_> Great, brilliant job. Thanks!
<Glanzmann> tpw_rules: He dosed github yesterday.
<Sobek[m]> Wait, how did that happened ? Sound like an interesting mistake to do.
<Glanzmann> Sobek[m]: github just was down a for a few minutes.
<Sobek[m]> This make more sense, but one never knows with bad mistakes.
<Sobek[m]> (Like say screw up the mirror replication and turn all the mirror into an unwitting botnet hammering github requesting over and over again a file. Github probably has some mitigation in place fortunately)
<Glanzmann> marcan: How do you make your keyboard blink?
<marcan> ?
george14_ has quit []
<marcan> also it was like an hour
<Glanzmann> marcan: You said you make your keyboard blink once an hour to remind you to drink some water, I wonder how you do that.
bdju_ has joined #asahi
<marcan> oh I have some LEDs on my keyboard
<marcan> it's lighting up my desk
george147 has quit [Ping timeout: 480 seconds]
<Glanzmann> marcan: I see, I have a keychron keyboard. There I can press a button and it turns the leds on and off. But I don't know how to do that from my machine, I thought you have a fancy one-liner.
<marcan> the LEDs have nothing to do with the keyboard itself
<marcan> they're just connected to a smart plug
<Glanzmann> Ah, I see.
bdju has quit [Ping timeout: 480 seconds]
MajorBiscuit has quit [Ping timeout: 480 seconds]
<j`ey> sven: it worked for about 10mins, I can see the ttyACM* now, but all I get is 'm1n1.proxy.UartTimeout: Expected 1 bytes, got 0 bytes' D:
<sven> <3 usb
<j`ey> it might be a good idea to reboot my host too..
<sven> yeah, at least inside m1n1 the usb2 phy should be configured correctly
<j`ey> blah, guess usb is forcing me to take a break for a bit :)
gsieben[m] has joined #asahi
<gsieben[m]> Hello, I'm Gabriel. I just wanted to chime in and say that I was able to install Asahi Linux using the curl method above on a FileVault-enabled Mac by running the installer from Recovery, and by opening Disk Utility > Expanding "Macintosh HD" > Selecting locked volume > Clicking "Mount" beforehand. It works completely fine, dual-boot works, and FileVault was never disabled in the process.
<tpw_rules> gsieben[m]: cool, thanks for trying
k4czp3r[m] has joined #asahi
<Glanzmann> gsieben[m]: Thank you for letting us know, I updated the Debian Wiki entry: https://github.com/AsahiLinux/docs/wiki/Debian
bisko has joined #asahi
<gsieben[m]> Glanzmann: Cool, thanks for adding that. A little more information: If you run the installer without "mounting" the locked disk using Disk Utility from Recovery beforehand, it will crash with "error -1" on the filesystem resize operation. Perhaps in a future installer release, that error could be caught and it would provide instructions for unlocking the disk. For some reason, the disk is not automatically unlocked when you sign into
<gsieben[m]> recoveryOS if you have FileVault on. 🤷 I don't know how running the installer from macOS instead of recoveryOS with FileVault on works - but potentially, a future installer could catch that you have FileVault on and tell you to try it from recoveryOS after unlocking.
<tpw_rules> did you not run it from macOS? i thought you said you did
<tpw_rules> or was that on a different computer?
<gsieben[m]> I ran it from recoveryOS. Full shut down -> Options -> Disk Utility -> Unlock Disc -> Close Disk Utility, Open Terminal -> Run Curl command.
<gsieben[m]> I could also try from macOS if you would like.
<tpw_rules> i thought we talked earlier and you did it from macOS.
<gsieben[m]> I don't think so? My first message here was 15 minutes ago.
<gsieben[m]> I think that was someone else.
<tpw_rules> ok. then it was someone else with a very similar nick
<tpw_rules> as i said earlier imo Glanzmann it's better to recommend that the installer runs from macOS
<gsieben[m]> Does FileVault-enabled installation work from macOS? Or do we not know that?
<tpw_rules> yes, that's what the other person did
<tpw_rules> they got the same weird error trying to do it from recoveryOS, so i advised them to try it from macOS and it worked
<tpw_rules> well maybe it was a slightly different weird error; it told them the disk was locked
<gsieben[m]> Oh OK - then the only thing I guess I've added is that if you choose to use recoveryOS, open Disk Utility first and unlock. Then it will stop telling them the disk is locked and the installation will work.
<tpw_rules> ye
<tpw_rules> s
<tpw_rules> i thought that might be the case. thank you for giving it a try and telling us
<jannau> marcan: ESP selection works fine, two old installations after updating m1n1-uboot to m1n1 and uboot-asahi and fresh desktop installation
<marcan> awesome :)
<tpw_rules> yeah i tested that too, but u-boot still doesn't find the right rootfs
<marcan> rootfs? u-boot does not look for rootfs
<marcan> grub does
<tpw_rules> sorry, ESP
<jannau> tpw_rules: only efi is supported
<tpw_rules> on account of PR #3
<Glanzmann> marcan: Do you agree with tpw_rules that the installer should run from macos instead of 1tr?
<marcan> both are designed to work
<Glanzmann> I thought we prefer to run it from 1tr due to no phoning home or something.
<marcan> 1TR is more future-proof due to no phoning home, yes
<marcan> I don't really care how people do it
<marcan> especially now that the boot picker nonsense is gone
<marcan> that worked better from 1TR
<marcan> of course running it from 1TR will be necessary for a hypothetical future mode where we replace macOS
<tpw_rules> my reasoning is that in macOS you are sure which OS you are entering the credentials for
<marcan> sure
<marcan> you can always try again though :)
<jannau> > 90% will have just one OS
sting[m] has joined #asahi
<tpw_rules> yeah it's not like a massive problem
<tpw_rules> jannau: oh, i missed the separate branch. why?
<tpw_rules> i might switch nixos to that branch then. is that the same branch you'd get if you installed it using asahi linux itself?
<marcan> because kettenis is in charge of asahi and i don't push to that
<marcan> but I sometimes need to get something in for the package before he has a chance to merge it :)
bisko has quit [Ping timeout: 480 seconds]
gsaker147 has joined #asahi
<gsaker147> Do I need to run the installer script in recovery mode?
<milek7> no
<gsieben[m]> gsaker147: You can, but not necessary.
<gsaker147> Thanks
gsaker147 has quit [Remote host closed the connection]
<fortelling[m]> I just followed the installer guide but when I got to the Mac OS version selection, it only gave me the option to select Mac OS 12.1.
<j`ey> what guide?
<fortelling[m]> Soon to be release
<j`ey> fortelling[m]: running curl -L https://alx.sh/dev | sh ?
<gsieben[m]> I think he is referring to Glanzmann's customized Debian install guide at https://github.com/AsahiLinux/docs/wiki/Debian even though the first alpha release is targeting Arch.
<gsieben[m]> So he is using curl -sL tg.st/d | sh
<fortelling[m]> j`ey: Oh no, curl -sL. uh oh
<gsieben[m]> I did the Debian install earlier this morning - you probably want to use Arch instead. The Debian install doesn't come with a GUI... or good scaling.
<gsieben[m]> Yet.
<gsieben[m]> It also doesn't get that nice Out-Of-Box Setup wizard.
<fortelling[m]> Oh ok so can I just restart and use that other curl command and be good to go?
<gsieben[m]> Did you install Debian with the first script already?
<gsieben[m]> Or how far along are you?
<fortelling[m]> no
<Glanzmann> fortelling[m]: One second, I fix that.
<fortelling[m]> I quit when it didn't give an option for 12.3
<fortelling[m]> disk is resized
<gsieben[m]> Try running curl -L https://alx.sh/dev | sh then from either macOS or recoveryOS.
<Glanzmann> fortelling[m]: Can you quit and run it again, please?
<Glanzmann> fortelling[m]: I fixed the debian installer_data.json.
<fortelling[m]> Yah i'll go test that before I install Arch. brb
<gsieben[m]> Debian is curl -sL tg.st/d | sh (previously 12.1, now 12.3)
<gsieben[m]> Arch is curl -L https://alx.sh/dev | sh (12.3)
<gsieben[m]> Take your pick.
<Glanzmann> fortelling[m]: I modified the supported versions after I thought I spot a usb bug with 12.3 firmware bug that was just be booting with the wrong dtb and than not powering off the machine completly before loading the new one.
screen_persona[m] has joined #asahi
roxfan2 has joined #asahi
<fortelling[m]> Debian installer showing both 12.1 and 12.3 now, thanks you guys
<Glanzmann> Perfect.
<gsieben[m]> I wonder if Apple will ever update their license to allow redistribution of some blobs. One can dream.
roxfan has quit [Ping timeout: 480 seconds]
zamadatix has joined #asahi
<zamadatix> Is there a user toggle to enable full resolution (i.e. over the notch)? The Asahi Desktop only exposes a single resolution in the Plasma selector
<clover[m]> is getting linux on the M1 iPads feasible? if so, is it out of scope for asahi project?
<immychan[m]> Seems doubtful
<immychan[m]> The iPads have a locked boot loader
<gsieben[m]> clover: M1 iPads will never be supported. Asahi Linux works on Macs because macOS has a whole "Boot Policy" system to allow booting alternative and fully-untrusted operating systems, whereas iOS bootloaders do not have such a system and are hardware-root-of-trust locked to only booting iOS.
<gsieben[m]> Exceptions are when flaws are found in iOS's bootloader, such as the checkra1n exploit in the A10 and older chips which could fool iBoot into loading unsigned code, though this was patched in A11 and newer and no exploit like it has been found.
<jn> if someone else sorts out the boot chain (with an appropriate exploit), much of the linux-side work should be reusable for ipads and iphones
<gsieben[m]> Right, but anything iOS/iPadOS would require an exploit, and not be a permitted thing like on Macs.
<jn> exactly
<clover[m]> ok, got it. that's too bad. linux on an ipad would be OP
<TheLink> does linux have a good touch ui desktop environment besides android?
winter has joined #asahi
<gsieben[m]> TheLink: Depends on what you define "good" as. ;)
<mini_> we could revive GPE or Opie :)
<TheLink> yeah, scratch the good part
<TheLink> that's very subjective
<mini_> but seriously, there's plasma mobile for instance
<clover[m]> Ubuntu Touch by UBPorts, Plasma Mobile by KDE, and Phosh by Purism
Techcable has quit [Remote host closed the connection]
Techcable has joined #asahi
<TheLink> is one of those used on this linux phone thing?
<gsieben[m]> They are all options for Pinephone and Librem 5, which are the Linux smartphones broadly available. Phosh is IMHO the most polished... but they're still a long way from Android.
<LuEvers[m]> yep
<LuEvers[m]> +1 for phosh. plasma mobile had beed behaving very strange on postmarketos
<TheLink> seems like plasma mobile is used now
<clover[m]> there is also sailfishOS
<LuEvers[m]> gnome on wayland also works with 3 finger gestures. touchpad is behaving pretty well
<LuEvers[m]> (m1 air)
<clover[m]> how are the gnome animations
<LuEvers[m]> they are okay. you see frame sync issues (no vsync), and they are sub 30 fps.
<LuEvers[m]> i may say my work-machine (i7-8xxx thinkpad, iGPU) behaves the same just without tearing🤣
<immychan[m]> clover[m]: Smooth enough
george147 has joined #asahi
<george147> It's installing now
<bluetail[m]> asahi goes gaming is still a long way :D
<george147> It's been quite a while on Extracting root.img into disk0s7 partition...
<as400[m]> Guys, I think you need to move this discussion about crap from p64 to offtopic.
<george147> I'm not seeing a lot of disk access
<j`ey> george147: its 3gb
<george147> But it is downloading a lot
george147 has quit [Remote host closed the connection]
linuxgemini9 has joined #asahi
nepeat has quit [Read error: Connection reset by peer]
zamadatix has quit [Quit: Leaving]
nepeat has joined #asahi
m6wiq has joined #asahi
linuxgemini has quit [Ping timeout: 480 seconds]
bisko has joined #asahi
gsaker147 has joined #asahi
gsaker147 has quit [Remote host closed the connection]
<j`ey> all 4 USB ports on the rpi, and both USB ports on the m1, and nothing works :/
<sven> at least you understand my pain now :D
<sven> I don’t think it ever this bad for me though
<sven> +was
<j`ey> I should have bought a $1800 uart cable :P
<sven> shush.
<sven> also, mine was only like 700$
<j`ey> ;)
<j`ey> I dunno if it's the rpi or what. it's usually not this bad. just occasionally it.. refuses to work, for a period of time, but starts working again
<bluetail[m]> j`ey: wtf
<bluetail[m]> Why are they so expensive?
<j`ey> bluetail[m]: oh, the joke is buying a second m1 to use as a ""cable"" :P
<bluetail[m]> oh :D
<j`ey> with m1<->m1 you can use a special USB PD mode, that you cant do with a normal cable
<sven> yeah, and I got mine before I wrote that dwc3 driver that allows you to use a regular usb cable
<jannau> also access to the hw uart
<sven> i don’t really use that hw uart very often at this point
<sven> and most of my code these days doesn’t lock the machine up so badly that the hv dies :D
<bluetail[m]> sven: I keep seeing people complaining nvme over thunderbolt would only work for short bursts or otherwise the drive would eject, not just throttle. Can you confirm that nvme over thunderbolt is not suited for 24/7 NAS / heavy IO usage?
<sven> uhhh… no idea, depends on the enclosure I guess
<bluetail[m]> I've seen one with a tiny fan, but no noise for me. Otherwise I would have it stored in a different room...
<sven> I don’t know why the device would eject though unless you tug on the cable or something
<bluetail[m]> I see
<bluetail[m]> Perhaps they were having a power issue
<bluetail[m]> I only had that happen when power wasnt sufficient
<bluetail[m]> the macmini ports arent exactly powering much
<sven> or unless it overheats so badly it goes into thermal shutdown
<sven> but this is all off topic anyway
<bluetail[m]> but you arent in offtopic
<bluetail[m]> I cant ask you there
<j`ey> maybe there's a reason he isnt in there :P
bisko has quit [Ping timeout: 480 seconds]
<bluetail[m]> Cause hes annoyed from all those noobz, right?
<bluetail[m]> UberL33T...
<sven> 🤨
bisko has joined #asahi
jaime10[m] has joined #asahi
aenfgiuaebueargb[m] has joined #asahi
<jaime10[m]> Hey, just wanted to say thanks. I installed it on my M1 air and its working surprisingly smoothly. However after playing video for a while it starts getting pretty hot (More than on heavy loads with MacOs). Is there a threshold for the temp?
<bluetail[m]> doesnt linux has power governors? Using tuned adm right now on my non-mac machine. Should work on mac, too, right? But maybe not, cause asahi is different
<aenfgiuaebueargb[m]> hello, noob here. I followed the Arch installation, going with the "Minimal" option. I realized I was in to deep when I couldn't figure out wifi and what-not. I tried running the installer again but it wouldn't allow me to resize my Asahi install, only my Mac OS install (which is only around 100gb because its all on the minimal install). I want to reinstall to this space.. Any help would be much appreciated
bisko has quit [Ping timeout: 480 seconds]
<kettenis> jaime10: as far as I know the "hardware" will automatically clock down the CPUs to keep things within the thermal envelope
<opticron> aenfgiuaebueargb[m], you'll probably want to go back to macos recovery mode and blow away the partitions that contain the linux and EFI partitions from the terminal
<aenfgiuaebueargb[m]> opticron: Ok, thank you
<opticron> I guess there needs to be some docs on the wiki that either make that easier or explain the process
<opticron> or maaaaybe part of the installer "remove all traces of asahi"
<jaime10[m]> kettenis: Okay thanks. Maybe I just got a bit worried too soon.. Cant wait for GPU acceleration tho:)
<opticron> hmmm...
<bluetail[m]> I was wondering before. What does
<bluetail[m]> do?
<bluetail[m]> for i in ????????-????-????-????-????????????; do
<tpw_rules> loop through all the UUID-formatted-named folders
<bluetail[m]> ty
<bluetail[m]> does that also work with filenames?
<tpw_rules> sure
<jaime10[m]> My trackpad scrolls way too fast. Im on gnome/wayland. I only found https://github.com/tkkcc/libinput_patch, but it doesnt compile on arm. Does anyone know how to adjust it?
<bluetail[m]> tpw_rules: I love you. Thanks.
<psykose> does it compile without the patch
<LuEvers[m]> i had to go to the recovery partition, and delete the whole APFS Container there. (diskutil apfs deleteContainer xxx)
<LuEvers[m]> diskutil is pretty powerful imo
<psykose> jaime10[m]: you should also perhaps post some logs of what fails
<psykose> from a quick test i can compile it fine with and without the patch on 1.20.0 libinput :)
<jaime10[m]> psykose: yay says that libinput-multiplier isnt compatible with my architecture.
<mps_> jaime10[m]: 1.20.0 libinput works fine for me on xorg
<psykose> could you post any output at all and what you're doing and how you set things up
<mps_> psykose: you ask me?
<psykose> because that patch cannot tell you anything about your architecture, it doesn't touch the libinput build system
<psykose> mps_: no, the other person :)
<mps_> ok
<jaime10[m]> I also have libinput, but wanted to install libinput-multiplier to adjust the speed
<mps_> `xinput -set-prop 'MacBook Force Touch trackpad' 'libinput Accel Speed' 0.7`
<psykose> if you mean you tried to install ''libinput-multiplier'' from the AUR
<psykose> then yes, it is marked as x86_64 only (because most things on the AUR are)
<psykose> you have to actually build it yourself
<psykose> it does build, the patch works fine
<jaime10[m]> mps_: Thanks thats exactly what i need, but doesnt work on wayland:(
<psykose> if you fetch the pkgbuild, you can just edit the arch= line
<psykose> then makepkg -si it
<psykose> or something
<mps_> jaime10[m]: ah, sorry then
<psykose> assuming you are on arch
<jaime10[m]> psykose: okay thanks ill try. It tries to replace libinput though. Should I say yes?
<psykose> it is libinput with an extra patch, so yes
mps_ is now known as mps
<jaime10[m]> Ohh okay i see. Thank you
gsaker147 has joined #asahi
george147 has joined #asahi
<george147> Any tips on getting audio working?
<george147> Everything else works great
<Glanzmann> george147: Which m1 device do you have?
<george147> Macbook air
<Glanzmann> george147: Than you just plug something in the audio jack and it works.
<george147> Didn't seem to
<george147> I can only see analog audio output
bisko has joined #asahi
<Glanzmann> george147: There are also instructions to enable the speakers, but they're dangerous at the moment because they might damage your speakers.
<Glanzmann> george147: Do you have pavucontrol ?
<george147> Yes
<Glanzmann> do you have alsamixer?
<george147> I think so
<Glanzmann> So here are two screenshots from me: alsautils > F6 > default:0 ...
<george147> I'll have to quickly reboot to linux as I haven't installed an IRC client there yet
<Glanzmann> k
george147 has quit []
<dan[m]123> There’s no support for hibernation/suspend yet right?
<gsaker147> Well I've got some output now
<gsaker147> But it's super loud and distorted
<j`ey> dan[m]123: no, pcie has issues
<gsaker147> They're very cheap headphones so not too worried about that
<Glanzmann> gsaker147: Just turn the volume a bit down.
Chainfire has joined #asahi
<M1bn3mar[m]> hey how to clear system data??
bisko has quit [Ping timeout: 480 seconds]
<gsaker147> It's on minimum
<gsaker147> I can hear the headphones loud from a metre away
<gsaker147> Interestingly it still outputs when I set the gain to 0 in alsamixer
Guest2509 has joined #asahi
<Glanzmann> gsaker147: Try to adopt it using pavucontrol.
<Glanzmann> I put it to 25%.
<Glanzmann> pactl set-sink-volume @DEFAULT_SINK@ 25%
creechy has quit [Ping timeout: 480 seconds]
<Guest2509> Didn't seem to change anything unfortunately
gsaker147 has quit [Ping timeout: 480 seconds]
Guest2509 has left #asahi [#asahi]
<jaime10[m]> Update on Touchpad scrolling speed adjustment: I cant get libinput-multiplier patch to work. Apparently libinput doesnt support this setting on X or Wayland.
<jaime10[m]> If anyone finds a solution please share
creechy has joined #asahi
bisko has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
amarioguy has joined #asahi
bisko has quit [Ping timeout: 480 seconds]
<clover[m]> are yall putting macOS keybindings on yalls asahi profiles or sticking with linux e.g., ctrl+c to copy instead of cmd+c
amarioguy has quit [Remote host closed the connection]
amarioguy has joined #asahi
amarioguy has quit [Remote host closed the connection]
bisko has joined #asahi
chengsun has quit [Quit: Quit]
chengsun has joined #asahi
<mps> clover[m]: I remaped caps-lock to control
creechy has joined #asahi
bisko has quit [Ping timeout: 480 seconds]
bisko has joined #asahi
<mps> povik: is it possible to have both output, speakers and jack, at the same time (with switch in alsaconf maybe)
<mps> and amixer, ofc
bisko has quit [Ping timeout: 480 seconds]
<mps> if I enable speakers then jack doesn't work
Felipe[m]1 has joined #asahi
Felipe[m]1 has left #asahi [#asahi]
joske has joined #asahi
<povik> sure. at alsa level both outputs are there: hw:0,0 would be speakers, hw:0,1 jack
<povik> pulseaudio doesn't know the sound card so it defaults to hw:0,0 only
<mps> povik: I use plain alsa, not pulseaudio
<mps> so it is enough to remove comment from dts to get both?
<povik> yes
<mps> thanks (how I missed this :) )
<Chainfire> Thanks for the effort, people. Just installed Asahi Desktop and running great on my MBP Max 16" so far.
<brentr123[m]> wait what
<brentr123[m]> the script isnt working
<marcan> brentr123[m]: you don't have the cool version
<marcan> ok, new kernel is pushed to the repos, should fix everything people asked for last minute (:p)
<marcan> new m1n1 with the random stuff too
<marcan> I'm going to launch an image build and take a shower meanwhile. folks with existing installs: please test
<tpw_rules> yay
<mps> marcan: already building :)
<marcan> what's in the repo is what's going in the release once I test on the iMac (I think nobody tested that)
<tpw_rules> is the non /dev link any different? i patched out the exit but then it 404'd
<marcan> mps: I mean the arch repo
<marcan> i.e. arch users please pacman -Syu
<marcan> tpw_rules: it goes to different places
<marcan> which I'll push to once it's done
<mps> marcan: ah, ok. but I see in last 20 minutes few merges in kernel
bisko has joined #asahi
<marcan> yes, the ones I just built and pushed to the pacman repo
<marcan> :p
<marcan> (because people kept sending me "one more thing")
* povik guilty
<mps> that will never end ;)
<sven> soooo…. What if I push usb3 now? :-P
<povik> :p
<mps> I will build it :)
<sven> (no worries, I broke it while cleaning it up and won’t get back to that until tomorrow ;))
<marcan> :p
kita99 has joined #asahi
bisko has quit [Ping timeout: 480 seconds]
<clover[m]> yey new kernel
PaterTemporalis has quit [Ping timeout: 480 seconds]
the_lanetly_052 has quit [Ping timeout: 480 seconds]
bisko has joined #asahi
joske has quit [Quit: Leaving]
joske has joined #asahi
creechy has quit [Ping timeout: 480 seconds]
<marcan> ok, pushed everything to dev
<marcan> going to test on the iMac
<LuEvers[m]> marcan: kernel works fine
<joske> marcan: new kernel working well (with 4k iommu patch - and speakers enabled) on air
<marcan> oh right, macos update lol
<marcan> I guess that's another hour :')
<j`ey> :|
<marcan> unless I just DFU this
<marcan> that would be faster
<marcan> screw it, DFU it is
<LuEvers[m]> xD dfu has been so slow the only time i restored my mac
<LuEvers[m]> like 2x the time of restoring an iphone 5
<tpw_rules> i am having problems suddenly with the asahi,efi-system,partition variable not showing up
<marcan> it's faster than a normal update!
<marcan> and it used to be faster but apple downgraded it to usb2 :<
<marcan> tpw_rules: did you update m1n1 manually?
<LuEvers[m]> D: bad
<marcan> stage1?
<tpw_rules> marcan: i used the dev installer. let me retry now that you just updated it
<tpw_rules> either i'm building m1n1 and u-boot wrong, or there's a heisenbug
bisko has quit [Ping timeout: 480 seconds]
<marcan> are you compressing u-boot before appending it to m1n1?
<tpw_rules> no?
<marcan> there's your problem.
<tpw_rules> but i'm installing it as ESP, which is stage2, right?
<marcan> yes, but kernel payloads do not have a reliable size
<marcan> which means m1n1 can't find payloads after them
<marcan> which includes chainload variables
<marcan> so stage1 appends the var and then stage2 can't find it
<tpw_rules> the stage2 m1n1 + u-boot i've built can't find that variable from the official stage1
<tpw_rules> ah, ok. i wonder how that worked before
<marcan> you might've gotten lucky with the size padding
<tpw_rules> do i just gzip u-boot-nodtb.bin?
<marcan> yes
<tpw_rules> ok. are the device trees already padded i guess?
<marcan> those have a reliable size
<marcan> I should just remove support for uncompressed kernels, this is going to bite people
<LuEvers[m]> how is pushing kernel changes to other unofficial distros working? seems you have to rebuild it every time?
<LuEvers[m]> like NixOS and debian
<marcan> that's pretty much how it goes, yes
<marcan> I can't make kernels for everyone :p
<tpw_rules> i mean that's the same with arch too
<LuEvers[m]> i could try to build some pipeline and package it in some different repositories
<LuEvers[m]> well you only distribute the kernel over the pacman repo so idk if that's useful
<marcan> distros should probably be in the loop of kernel updates
<marcan> since dtb issues can need to be handled differently
<marcan> and you can't just default your old .config always
<LuEvers[m]> yeah different per distro
<LuEvers[m]> how long do you think it'l take getting current changes upstreamed? and having at least non stable builds of common distros to contain your changes
<marcan> some things have already been upstreamed
<tpw_rules> yeah that's all on the feature status page
<LuEvers[m]> yeah saw that
<j`ey> LuEvers[m]: some months
eroux has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<tpw_rules> ok, the compressed u-boot works. and i can power off without the kernel warning
eroux has joined #asahi
<gsieben[m]> Kernel updated through Arch and works fine on 7 GPU Core 16GB RAM A2337 MBA.
<mps> build first asahi kernel without any patch and it works \o/
bisko has joined #asahi
joske has quit [Quit: Leaving]
creechy has joined #asahi
bisko has quit [Ping timeout: 480 seconds]
kgarrington has joined #asahi
<marcan> lol, u-boot and grub look ridiculous on the iMac
<j`ey> they look small already on the laptops :p
kgarrington has quit [Remote host closed the connection]
<fortelling[m]> I want people to be aware of, when attempting to change brightness in KDE, it makes the screen completely black. Anyone else experience?
<tpw_rules> that's to be expected. your two backlight brightness choices right now are "on" or "off"
<j`ey> fortelling[m]: its not supported yet
<fortelling[m]> oh lol, thanks
<LuEvers[m]> at least the buttons work :)
<LuigyLeon[m]> tpw_rules: is there a new step if updating from yesterdays release?
<fortelling[m]> :)
<LuEvers[m]> i remeber just getting the Fn brightness to work on hackintosh was a pain
<LuEvers[m]> * Fn brightness buttons to work
<LuigyLeon[m]> "Device 0: unknown device" on boot
<tpw_rules> LuigyLeon[m]: for nixos? no, there shouldn't be. i added instructions at some point on installing the repo as a channel.
<tpw_rules> if u-boot doesn't work now i would recreate the stub partition.
kgarrington has joined #asahi
<winter> Can I use the Asahi installer at alx.sh by just removing the exit currently there?
<tpw_rules> then wait a bit for the new installer to finish building
<tpw_rules> winter: no, i tried already :(
<LuigyLeon[m]> odd
<winter> ah :(
<LuigyLeon[m]> all the previous updates went fine till today
<tpw_rules> maybe you updated before i actually pushed and got the commit where u-boot was broken cause it wasn't compresssed
kgarrington has quit [Remote host closed the connection]
<LuigyLeon[m]> oh that might be it
<tpw_rules> but either way now that we have the release m1n1 you should recreate the stub and install it just to avoid future issues
<winter> tpw_rules: do you think that once things stabilize a bit, we should try to get the needed parts of the NixOS configs into nixos-hardware?
<tpw_rules> there's a section on the guide on recovering (basically just remount your partitions, copy the modules over again, then run nixos-install --no-root-password)
kgarrington has joined #asahi
<threerik[m]> how do i update the kernel in my arch install? is it just a regular pacman upgrade?
<j`ey> yes
m6wiq has quit []
<winter> yes
<threerik[m]> btw its been working great so far :-)
<threerik[m]> thanks both
kgarrington has quit [Remote host closed the connection]
<tpw_rules> winter: that could definitely be an option. probably when the upstream kernel can build a workable install image
<winter> yeah
<winter> threerik[m]: which URL for the installer did you use?
<threerik[m]> winter: https://alx.sh/dev
<threerik[m]> a couple hours ago
<winter> ah
leon_kernan[m] has joined #asahi
<winter> where is that linked, threerik[m]? i only see mrcn.st/alxsh on the wiki
<winter> which seems to redirect to the same thing
<winter> just curious :D
<j`ey> just on irc
<tpw_rules> it was new as of like yesterday
<threerik[m]> winter: oh i forgot where i found the link haha
<threerik[m]> i think someone mentioned it here?
<winter> ah
<winter> guess i’ll just wait for the alx.sh one to go live by this point
<LuEvers[m]> is there any ide working with 16k page size?
<tpw_rules> any that aren't based on chromium
<aenfgiuaebueargb[m]> So i used Asahi KDE for a while now and everything worked so well. One thing I noticed was my machine (macbook air) got pretty warm when I had a lot of firefox tabs open.
<tpw_rules> that's probably expected, nothing is accelerated yet
<LuEvers[m]> tpw_rules: :( i'll miss vscode
<LuigyLeon[m]> tpw_rules: so turns out all it took was a "run distroboot" (don't quite remember the exact message) as it prompted and it's booted fully now
<winter> <winter> guess i’ll just wait for the alx.sh one to go live by this point <— or would the /dev one work fine
<aenfgiuaebueargb[m]> That makes sense. It is so smooth for only using CPU. Wow
<j`ey> LuEvers[m]: use the 4k kernel then!
<tpw_rules> winter: the dev one would work fine, but patience IS a virtue :)
<winter> meh :^)
<winter> here we go, then!
<winter> just curl | sh right?
<winter> as non-root?
<tpw_rules> yeah, booted into macOS and logged in as an adminstrator
<tpw_rules> you don't have to do sudo in Terminal.app
<tpw_rules> LuigyLeon[m]: ah ok. i am informed that the new iso image is ready
<brentr123[m]> the % partition thing is too confusing for me
<tpw_rules> brentr123[m]: what do you mean? i think the phrasing has been updated, not sure if that's live
<brentr123[m]> like 80% of macos, i just wanna be able to type in "50 gb to asahi"
<LuEvers[m]> j`ey: any link to information? is it a patch? or different kernel config?
<threerik[m]> brentr123[m]: on the first one enter the new space for the mac disk
<threerik[m]> partition*
<brentr123[m]> oh for the mac partition
<winter> » New size (50%): 90%
<winter> Resizing will free up 49.44 GB of space.
<winter> that doesn't seem right!
<threerik[m]> yeah i have no idea how the percentages work either lol
<tpw_rules> it's saying the macOS size will be 90% of its previous size
<threerik[m]> ohhh right
<tpw_rules> so presumably you have the "512GB" mac
<winter> yeah but the resizing part doesn't make sense
<winter> why would it free up space
<tpw_rules> it will make that much free space on the disk
<threerik[m]> i resized my mac partition to 420G leaving about 70 for asahi
<brentr123[m]> so if i have the 256 gb mac i just do 256- whatever i want to give to asahi
<brentr123[m]> and then put that?
<tpw_rules> yes
<brentr123[m]> i am beyond confused
<brentr123[m]> i have 128.57 left on macos
<brentr123[m]> that -50 = 78.57
<winter> uhhh, looks like the resizing froze the system
<tpw_rules> winter: it will freeze while it's busy because nothing can access the disk
<winter> ah
<tpw_rules> brentr123[m]: time machine reserves free space, essentially. https://appleinsider.com/articles/21/06/26/how-to-delete-time-machine-local-snapshots-in-macos
<brentr123[m]> tpw_rules: I have *never* used time machine
<LuEvers[m]> winter: disk utility (GUI) puts it's window into foreground and blurs / blocks the whole OS while doing such operations, to mitigate the issue
<LuEvers[m]> s/it's/its/
<tpw_rules> brentr123[m]: hm. i'm not really sure how to help you then. i guess apfs can't rearrange the disk. i still think there are snapshots made on system upgrades. can you check like it says on the page?
<tpw_rules> specifically the "tmutil listlocalsnapshots /"
<winter> The new OS will be allocated 44.39 GB of space,
<winter> hmm, why the few KB left? i put `max` at the prompt
<winter> leaving 86.02 KB of free space.
<tpw_rules> there's some rounding and partition alignment requirements
<tpw_rules> note also that diskutil uses decimal sizes
<winter> why does that matter here?
<tpw_rules> well it explains how you get weird decimals
tomtastic has quit [Quit: ZNC - https://znc.in]
<winter> ah
<winter> you mean the .02?
<tpw_rules> yes
<tpw_rules> that's exactly 21 sectors
tomtastic has joined #asahi
<tpw_rules> LuigyLeon[m]: bah, something went wrong with the iso reproducibility. i think it's the new gzip i added. i'm force pushing to fix that shortly once i confirm. the life of a reproducibilist is never easy :(
<brentr123[m]> tpw_rules: says not a valid disk when i try to remove it with sudo tmutil deletelocalsnapshots 2289385E1A6FCCF05D444673FB1FEB06DDCF82A4C723EAD53AF1F3E08872CE0F
<LuEvers[m]> you can create a new exfat partition in disk utility, with your given size... and then do 'diskutil eraseVolume free free disk0sX' on that partition, and the installer will recognize it as free space, giving you your preferred size
<brentr123[m]> oh
<LuigyLeon[m]> tpw_rules :) thanks
<tpw_rules> brentr123[m]: the page says that command expects dates?
<LuigyLeon[m]> I've been trying to get context on what is going on with my build. So I'm not sure how the nixos-install is differnt than the nixos-rebuild I did? Is that under the impression that the m1-support I used was out outdated?
<brentr123[m]> god this is confusing i dont wanna go through all this bullshit just to install linux
<tpw_rules> brentr123[m]: that's why it's (not even yet) alpha
<winter> ^^ :D
<tpw_rules> LuigyLeon[m]: can you be a little more specific? if you do nixos-rebuild or nixos-install, the m1-support module will install a new m1n1/u-boot blob into the ESP
<tpw_rules> so either the m1n1 on the stub partition is incompatible with that one, or that one has the bug where sometimes it's misaligned and can't get the ESP info to boot correctly
<LuigyLeon[m]> so I have a symlink to m1-support that my configuration.nix imports so it's always in sync. I updated to the latest and after a nixos-rebuild now on start I have the issue I mentioned earlier :). Now I'm trying to sort out what went wrong and now that I have been able to boot my actual nixos is there something different I can do that doesn't require the image?
<tpw_rules> you can roll back, then do /run/current-system/bin/switch-to-configuration switch to install the older working m1n1/u-boot
<threerik[m]> obviously the OS wouldnt boot but for the hell of it i tried booting the windows arm bootloader. Im curious as to why it wouldnt load, as I was under the impression that all EFI executables worked wherever the architecture matched and uefi was implemented properly. after all a random arm compiled efi shell loaded fine
<threerik[m]> does anyone know?
<tpw_rules> but like i said, what i would do is delete the stub partition and ESP, reinstall a new UEFI environment using the dev or release installer, then redo nixos-install with today's image that will be ready in a few minutes
<tpw_rules> threerik[m]: can you be a bit more specific than "not load"? maybe it barfs that EFI variables are not available, or its config files on the ESP
<tpw_rules> ok, the new fixed iso is ready
<threerik[m]> it just aborts right away and resets the cpu. ill try to get a picture of the output, it shows up for a split second
<tpw_rules> you could try running it under the hypervisor if so equipped
<threerik[m]> oh i have no idea how to do that haha
<threerik[m]> more importantly though i think since the kernel upgrade my battery indicator has disappeared 🤔
<threerik[m]> ill reboot and double check
<threerik[m]> * my battery percentage indicator has
creechy has quit [Ping timeout: 480 seconds]
<LuigyLeon[m]> tpw_rules: final question: to summarize, it's not always possible to update through nixos-rebuild alone; sometimes it will require some extra steps outside of nixos control? in this case things related to stub area getting out of date
<tpw_rules> LuigyLeon[m]: correct. if you need to install a new stub partition then you'll have to delete it and rerun the asahi linux installer.
<tpw_rules> i think there are plans to make that updateable from linux
<tpw_rules> but those are more down the road
<LuigyLeon[m]> Oh I see, thanks! that makes more sense now :)
<tpw_rules> but that shouldn't really need to be done frequently. the only possible trigger is macos updates, and even then only if that affects hardware support
tomtastic has quit [Quit: ZNC - https://znc.in]
tomtastic has joined #asahi
<tpw_rules> (i think)
tomtastic has quit []
eroux has quit [Read error: No route to host]
<sven> or bug fixes (say they fix DCP for some monitors)
tomtastic has joined #asahi
<opticron> woooo!
marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | https://asahilinux.org/2021/12/asahi-linux-alpha-release/ | 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
<LuigyLeon[m]> 🎉
<winter> !!
<winter> anyone know why diskutil apfs resizeContainer would say that the volume is locked?
<winter> trying to resize my macOS part from 1TR
<tpw_rules> do you have filevault and are in recovery mode?
<winter> yup
<winter> guess i need to boot into the system to do this?
<tpw_rules> open disk utility, then right click on the macos volume in the sidebar, mount it, and enter your password
<j`ey> marcan: gg
<winter> ah
<winter> the data one, right tpw_rules?
<tpw_rules> i think so?
<winter> yu
<winter> p
<winter> that worked
<winter> thanks
marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | https://asahilinux.org/2022/03/asahi-linux-alpha-release/ | 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
<marcan> how do you even date
<marcan> *facepalm*
<j`ey> tinder
<fridtjof[m]> marcan: I typed out the link manually (multiple devices...), didn't look close enough and now my post to /r/linux is broken on arrival :D
<marcan> lol
<marcan> I'm sorry T_T
<fridtjof[m]> all fine, yanked and reposted :)