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
FireFox317 has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
FireFox317 has joined #asahi
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi
chadmed has quit [Read error: No route to host]
le0n has quit [Quit: see you later, alligator]
le0n has joined #asahi
tomtastic has joined #asahi
tomtastic_ has quit [Ping timeout: 480 seconds]
chadmed has joined #asahi
Emantor has quit [Quit: ZNC - http://znc.in]
Emantor has joined #asahi
le0n has quit [Quit: see you later, alligator]
le0n has joined #asahi
Techcable has joined #asahi
PhilippvK has quit [Ping timeout: 480 seconds]
coolshaurya[m] is now known as coolshaurya
kov has quit [Quit: Coyote finally caught me]
kov has joined #asahi
jmr2 has quit [Quit: Page closed]
abbas_faiz[m] has joined #asahi
<abbas_faiz[m]> Hey everyone. How do I get started with the tethered USB boot? I can also try to update the documentation once it works for me
<tpw_rules> what system do you have? have you done anything on it before or does it only have macos now?
<abbas_faiz[m]> fresh MacBook Air. Done nothing so far
<tpw_rules> it's possible to do a non-tethered boot on those if you are interested. do you have access to another linux machine with either an aarch64 or x86_64 cpu?
<abbas_faiz[m]> Yes I do
<tpw_rules> what OS do you have on it currently?
<tpw_rules> the macbook
<abbas_faiz[m]> just macos
<tpw_rules> which version
<abbas_faiz[m]> the latest one. Monterey
<tpw_rules> 12.1?
<abbas_faiz[m]> 12.1
<tpw_rules> okay cool.
<tpw_rules> you'll first have to shrink the APFS partition to make space for linux. 20GB should be enough for a complete system
<tpw_rules> have you used diskutil before?
<chadmed> im going to fix up/write a new developer quickstart (Developer VERY Quickstart?) in a few minutes since the old guide is very intimidating and can be mostly replaced with the installer script
<abbas_faiz[m]> not on MacOS. But I can probably figure out how
<tpw_rules> okay
<tpw_rules> `diskutil list /dev/disk0` should give you the list of partitions on the nvme
<tpw_rules> iirc disk0s2 is the main one, it should be the biggest
<tpw_rules> then you can do `diskutil apfs resizeContainer disk0s2 500GB` if you want the container to be 500GB and the rest to be for linux.
Lucy[m]1 has joined #asahi
<abbas_faiz[m]> tpw_rules: ok my overall disk is 500 GB so I'll probably shrink it down to 450
<tpw_rules> did that work?
<abbas_faiz[m]> just did it. its in progress
<tpw_rules> okay, while that's going you'll need to extract the wifi firmware in another terminal by running this command: curl -sL tg.st/u/fwx.sh | sh
<abbas_faiz[m]> so we are planning to boot from the internal storage for all stages? Or is it that the boot loader will be there but kernel is over USB
<tpw_rules> that should create a /tmp/linux-firmware.tar which you'll need to copy to your linux system
<tpw_rules> yes, you can put everything on the internal storage
<chadmed> everything can be booted from the nvme, but for a tethered boot (the default currently) you supply a kernel to m1n1 via USB from a host machine
<chadmed> because u-boot supports the M1 SoC you can however set up a fully functioning untethered boot since it brings up pcie automatically, something m1n1 does not do
jx0 has quit [Quit: poof!]
<abbas_faiz[m]> chadmed: Kernel is supplied over USB DFU? Does m1n1/U-boot support MacBook Air (with type C port being there)?
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi
chadmed has quit []
<abbas_faiz[m]> tpw_rules: ok I'll take a look at your script and run it in some time. Do you have the script in a repo somewhere? Not sure if I should directly run a curl | sh command with an unknown script.
chadmed has joined #asahi
<chadmed> the kernel is uploaded to the Apple Silicon device over a serial interface m1n1 exposes on boot
<tpw_rules> abbas_faiz[m]: that's just for the wifi. the main installer is: curl -L https://mrcn.st/alxsh | sh and that repo is here: https://github.com/AsahiLinux/asahi-installer
<abbas_faiz[m]> ok I have the /tmp/linux-firmware.tar and about 50GB empty space after the Container
<abbas_faiz[m]> faizabbas@Faizs-MacBook-Air ~ % diskutil list /dev/disk0... (full message at https://matrix.org/_matrix/media/r0/download/matrix.org/HxpLSRtCNCoDkoQJxDvcQuQY)
<tpw_rules> okay. now you can run: diskutil addPartition disk0s2 apfs Linux 4G
<tpw_rules> to make the linux stub partition. then run the asahi install script and follow the directions
jx0 has joined #asahi
<tpw_rules> and once that is done, you can do whatever linux setup you like. i recommend my nixos tutorial: https://github.com/tpwrules/nixos-m1/blob/main/docs/uefi-standalone.md
<abbas_faiz[m]> got it. Thanks for the help. I will continue this once I am back besides my linux PC
<notyou[m]> Is it currently possible to do a non tethered boot on the m1 Macbook Pro?
<Glanzmann> abbas_faiz[m]: Untethered quickstart: https://github.com/AsahiLinux/docs/wiki/Debian Tethered quickstart: https://tg.st/u/asahi.txt
<Glanzmann> notyou[m]: What kind of macbook pro (2020 or current?)
<notyou[m]> 2020
<Glanzmann> notyou[m]: So if you have an old one (release 2020), you can use u-boot. On the new ones you can also using m1n1 but you will lack wifi until marcan has merges SMC.
<Glanzmann> notyou[m]: Than you're good. Just follow these guides https://github.com/AsahiLinux/docs/wiki/Debian
<notyou[m]> great thanks
<Glanzmann> If you don't want Debian, than use the live system, create an efi partition, one root partition and extract the desired root fs of the Distribution you want.
<Glanzmann> Install a kernel, grub and extract the wifi firmware and you're good to go.
<Glanzmann> notyou[m]: If you want Debian it is hopefully easy now with the Videos.
<Glanzmann> Sorry for the small font size, maybe I'll redo them.
<notyou[m]> cool, looks pretty fine to me
<notyou[m]> font size
<Glanzmann> notyou[m]: If you want to build your own kernel. Have a look at that, or use my config or any of the other known to work configs: https://github.com/AsahiLinux/docs/wiki/DesktopKernel
<notyou[m]> looks great
<Glanzmann> notyou[m]: See here for supported features on your model (that is not upstream but on the asahi branch with the patches from the DesktopKernel secction): https://github.com/AsahiLinux/docs/wiki/Feature-Support
<notyou[m]> great documentation, I've been putting off playing with this cause there was 0 documentation for so long
<notyou[m]> nice work
<Glanzmann> notyou[m]: If you find something in the documentation that is unclear or wrong, please fix it in the wifi or report it to me, so that i can fix it.
<notyou[m]> sure
mjg59 has quit [Remote host closed the connection]
the_lanetly_052 has joined #asahi
<chadmed> https://github.com/AsahiLinux/docs/wiki/Developer-Quickstart-2.0 anyone wanna proofread this? I've tried to simplify the dev quickstart guide and bring it up to date, incorporating the installer script to cut out having to manually create the macos stub etc
jx0 has quit []
<VinDuv> chadmed: nitpick: in step 3, the “Loading startup options...” message might not be visible on 12.0+ Mac mini, and may be localized. The boot menu itself is also localized. Maybe add something like “do not let go until you see Loading startup options... appear under the Apple logo, or a cog icon appear on the screen”?
<jannau> I've updated the minimal required macos version to 12.0.1, mostly to prevent issues if the system recovery is 12.1 or later
<VinDuv> Also I’m not sure if it’s safe to install 12.0+ m1n1 on a <12.0 Mac. My understanding is that the macOS installer upgrades iBoot automatically when 12.0+ is installed, but I’m not sure if that happens when m1n1 is installed
<jannau> the installer can not install macos stub which is newer than the newest installed macOS, it checks the system iboot version
<notyou[m]> @Glanzman in the uboot page ```d click Next.
<notyou[m]> 1. Click on the Utilities menu and select Terminal.
<notyou[m]> 1. Type the following command and follow the prompts:
<notyou[m]> 1. Click on the Utilities menu and select Terminal.
<notyou[m]> 1. Type the following command and follow the prompts:
<notyou[m]> 1. Type the following command and follow the prompts:
<notyou[m]> [201~and click Next.
<notyou[m]> 1. Click on the Utilities menu and select Terminal.
<notyou[m]> [201~and click Next.
<notyou[m]> 1. Click on the Utilities menu and select Terminal.
<notyou[m]> [201~and click Next.
<notyou[m]> [201~and click Next.
<notyou[m]> 1. Type the following command and follow the prompts:
<notyou[m]> 1. Type the following command and follow the prompts:
<notyou[m]> 1. Click on the Utilities menu and select Terminal.
<notyou[m]> whoops sorry, (new to gomuks)
<notyou[m]> I don't even know how that happened. anyway you've cropped the instruction to run step2.sh, so it's unclear if you're suppose install m1n1 or not
<notyou[m]> s/Glanzman/Glanzmann/, s/```d click Next./:/
<jannau> chadmed: thanks, once people have looked over it, it probably makes sense to move "Developer Quickstart" to "Developer Quickstart (obsolete)" and replace it
<jannau> I created a pull request to remove 11.x and 12.0 beta versions from the installer
<chadmed> VinDuv: that makes sense, wasnt actually aware that the boot menu was localised that specifically
<chadmed> jannau: i did intend on replacing the old guide but wanted to get some feedback first in case i missed anything
<notyou[m]> when I try to run bputil -nc -v "$VGID" in step2.sh from recovery I get an error something like this "boot object update failed error 401, failed to create local policy ap boot mode 11"
<notyou[m]> also " kmutil configure-boot -c u-boot.bin --raw --entry-point 2048 --lowest-virtual-address 0 -v "$system_dir" errors, saying configure-boot can only be run from recovery mode, but it is recovery mode?..
<chadmed> you must be in the wrong recovery mode
<chadmed> how did you get to recovery mode?
<notyou[m]> I used the installer to select the linux boot disk, it shutdown and i pressed the power button, then it bootlooped 3 or 4 times before booting to recovery
<ChaosPrincess> shut it down entirely, then boot it up holding power button
<notyou[m]> cheers
<mps> ChaosPrincess: this could be added to quickstart guide, I come to this 'by experience'
<chadmed> yeah thats the wrong recovery, you need to hold the power button down until it prompts you with boot options. you could probably try following the new guide i linked above
<notyou[m]> cool
<ChaosPrincess> you can catch it correctly on reboot, if you entered wrong recovery, you probably mistimed the power button hold
<ChaosPrincess> holding it from complete shutdown is the easiest way
<mps> ChaosPrincess: and safe
dianshi has joined #asahi
___nick___ has joined #asahi
___nick___ has quit []
___nick___ has joined #asahi
chadmed has quit [Quit: Konversation terminated!]
chadmed has joined #asahi
malvo has joined #asahi
espo has joined #asahi
Misthios1 has joined #asahi
Misthios has quit [Ping timeout: 480 seconds]
Misthios1 is now known as Misthios
Misthios has quit []
Misthios has joined #asahi
gladiac is now known as Guest1023
gladiac has joined #asahi
Guest1023 has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi
chengsun has joined #asahi
the_lanetly_052 has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
GenbuchanPS5[m] is now known as Genbuchan[m]
<Glanzmann> # Wait for the system to shutdown and the LEDs turn off. Than wait another 5
<Glanzmann> # seconds. Now press and do _not_ let go of the power button for 15 seconds.
<Glanzmann> # terminal execute:
<Glanzmann> # In the boot picker, select 'Options' and select Utilities > Terminal. In this
<Glanzmann> Fuck, that was the wrong paste.
<povik> > Fuck, that was the wrong paste.
<povik> don't think that will be a valid command :-p
<Glanzmann> chadmed: About the Developer Quickstart 2.0. Build Dependencies from m1n1 are missing, m1n1 needs to be checked out recursive, The stub should be 12.1, has someone crated a pull request for 12.2 or tested it?
<Glanzmann> And while reviewing your quickstart I noticed that I need to add the build dependencies to mine as well.
Techcable has quit [Ping timeout: 480 seconds]
<Glanzmann> chadmed: I would put the m1n1 chainloaded thing in a seperate article like untethered m1n1 or so. Because from my point of view that has nothing to do with 'developer quickstart' and more to do with I want a desktop the m1n1. But currently it is not practical because m1n1 can't enable PCIe and without PCIe you don't have wifi. And the Pro/Max machines are all notebooks. And you don't want a desktop
<Glanzmann> without Internet, of course you could use a wifi or ethernet dongle.
<Glanzmann> chadmed: For the kernel you can reference the [[DesktopKernel]]. I'll add my recomendations, if you don't like them undo that.
<Glanzmann> But I'll not remove the untethered boot.
<Glanzmann> chadmed: DesktopKernel was already referenced so I only added the --recursive flag to the git clone for m1n1.
Gaspare has joined #asahi
<Glanzmann> Has someone already checked with 12.1 fixes the iBoot hdmi initialization?
<Glanzmann> For the mini?
M1bn3mar[m] has joined #asahi
jx0 has joined #asahi
joske has joined #asahi
<joske> Hi all, I've manually applied the patch of sven in the dev channel onto current asahi, and with that I have now 4k pages, wifi, keyboard, USB, everything seems to work!
Gaspare has quit [Ping timeout: 480 seconds]
<joske> so now chromium & vs code run fine on asahi linux :-D
<joske> now only missing is some kind of battery percentage (smc?)
<Glanzmann> joske: Can you send a link to the patch?
<joske> on top of this of course the audio patch and the input patch...
<Glanzmann> Rehosted here for easier download: https://tg.st/u/iommu.patch
<Glanzmann> joske: I see. Maybe I'll try that. joske Did you also play with the x86 simulation stuff?
<joske> no
<joske> I just wanted to get vs code working :-)
<Glanzmann> I see, I use vim. :-) And Debian Testing seems to still have no chromium. So at the moment I have nothing I need it for.
<joske> well, all the electron stuff also only works on 4k pages (balena etcher, whatsapp app, ...)
<joske> as electron uses chromium underneath
<joske> Glanzmann: it's beyond me why anyone would *want* to run debian out of free will :-P
<Glanzmann> joske: I do it because I like a stable Linux distribution.
<Glanzmann> joske: What are you using?
<joske> manjaro
<joske> well, yes stable, but at the cost of ancient versions of everything
<Glanzmann> That is the definition of stable.
<joske> not sure what you are doing on the bleeding edge with asahi then ;-)
<joske> disclaimer: I used to run gentoo for long time, so I'm quite used to bleeding edge
<opticron> I also run Debian, I've found that even "Sid" (unstable) is relatively stable and useful
<Glanzmann> joske: Because it interests me. And I'm using testing on Debian that is bleeding edge enough for me. :-)
<mps> joske: so potentially f2f2 could also work with above iommu patch
<Glanzmann> mps: Probably.
<joske> mps: no idea
<joske> try it out
<joske> I don't have any f2fs filesystem
<mps> joske: sure, will do
<joske> Glanzmann: I'm even using manjaro testing, so latest everything ;-)
<mps> I have a lot of mmc cards and ssd disks with f2f2 fs on them
<Glanzmann> Oh chromium is back in testing. Now I have to try it.
<mps> joske: I'm using alpine edge (development release) on all workstations and testing systems, only use stable release on servers
<joske> Glanzmann: it's working here, so it should for you too
<mps> and I don't see much difference in stability between them
<joske> manjaro has been pretty stable for me too, rolling distros are nice
<mps> if I want really stable OS probably would use openBSD
<joske> balena etcher also works now with this patch
<mps> joske: yes, alpine edge is practically rolling release, though not called so
<Glanzmann> :Who is Balena Etcher?
<joske> Glanzmann: this is a tool to write ISO images to flash drives
<Glanzmann> Ah, I see.
<Glanzmann> joske: I use dd.
<joske> hahaha
<Glanzmann> For real.
<joske> yes I believe you ;-)
<joske> it's just funny
hspak has quit []
<Glanzmann> Or if I have slow flash drive and want to see progress, I use pv, it gives you real time stats.
<mps> heh, 'cat image.iso > /dev/sda'
<Glanzmann> mps: To small blocksize, I always do bs=8M, only on my macos videos I don't because you can't use 'M' and write out the number.
hspak has joined #asahi
<mps> Glanzmann: yes yes, I'm just kidding, also I use dd only
<joske> dd doesn't work for windows ISOs though
<Glanzmann> joske: It does if you have the right bios.
<mps> joske: last time (about 5 years ago) when I used it worked
<Glanzmann> But to be honest, I mostly install Windows over the network.
<joske> with PXE boot?
<Glanzmann> joske: Yep.
<joske> well, that's nice and dandy if you have all that setup, most people don't
<mps> I had to buy windows first time in my life for my $job and after some time I found that I actually don't need
<joske> I have it installed, but never boot i
<joske> t
<Glanzmann> joske: Like that: https://pbot.rmdir.de/wCs2lGQHcGqwc1UHNhCBMg Or I dd it using clonezilla or graml.
<joske> using linux since 1996
* Glanzmann since 93 or 94. Do not remeber.
<Glanzmann> Before 1.0. But barely.
<mps> this was one of the worst day in my life, 'give money to microsoft' was a really bad feeling
<Glanzmann> So 93.
<tpw_rules> Glanzmann: you can use "8m" with dd on macos
<tpw_rules> but not linux
<Glanzmann> tpw_rules: And you're telling me now.
<Glanzmann> tpw_rules: On Linux you can do bs=8M . I always do it.
<tpw_rules> i'm saying you can't do 8m on linux
<tpw_rules> the M has to be lower case for macos dd and uppercase for linux dd. no idea why
<nsklaus> i heard it was possible to follow a procedure to ask for refund
<Glanzmann> I think it is 1024 vs. 1000.
<nsklaus> mps
<tpw_rules> it's not
<Glanzmann> tpw_rules: I see, in diskutil it is.
<tpw_rules> yes but diskutil isn't dd
<mps> nsklaus: thanks, but I will not try, five years already passed
<Glanzmann> tpw_rules: I once created a partition a few bytes to small because of this and dded a slightly bigger image over it.
<Glanzmann> tpw_rules: Anyhow good to know updating my instructions now. THis saves a few seconds.
<Glanzmann> or ms.
<nsklaus> my last experience with windows was with 98se
<nsklaus> ;)
<Glanzmann> I need it for work way to often.
<nsklaus> personaly i refused all jobs that wanted me to use windows, and did not allow me to install my own linux distro on the companies's laptop
<nsklaus> i typically ask that during the interview
<mps> dd in coreutils use M for 1024 and M for 1000
<Glanzmann> nsklaus: I see. Well I also ended up installing Linux on all my work systems, but did not ask during interview.
<nsklaus> and also , my other question is: "when all job is done and well done for the day, is it acceptable for me to just surf, or work on my own project ?" if answer is no then i refuse the job
<mps> nsklaus: also I never used windows
<Glanzmann> Btw. does someone know if 16k pages give me performance benefits on tlb misses on arm?
<Glanzmann> Like on amd64 with large pages?
<mps> nor macos, except as boot loader for qemu in autumn last year for about two months :)
<Glanzmann> mps: Your hard core.
<Glanzmann> mps: Did it work out with all your keybindings?
<mps> Glanzmann: yes and no, I was impressed by announces for win NT 3.50 (iirc) and when my coworker got it I looked and tried with him for 3 days
<mps> and I then learned what marketing means, i.e. damned lies. never looked again
<mps> on the other side macos could be usable to me but I don't needed it because everything was ready on *BSD and linux
<nsklaus> s/macos/prisonbsd
<Glanzmann> mps: I went the other road, I installed firefox, iterm2, gpg agent, iina on macos and could consume with it and work in a terminal, for real work I switched to a thinkpad.
<mps> nsklaus: :-)
<mps> right
<Glanzmann> Now with wifi, I can do almost anything on the macbook air.
___nick___ has quit [Ping timeout: 480 seconds]
<mps> I own (my son bought to me) MBP intentionally to install asahi on
<mps> else I will don't accept it
<mps> s/don't/not/
<Glanzmann> mps: I bought the macbook because I wanted to try the architecture. And was hoping I have linux soon.
<mps> Glanzmann: heh, and thanks for all developers we have it \o/
<Glanzmann> Yep. :-)
<Glanzmann> Btw. does soemone know if ublock works correctly on chromium?
<joske> seems to work fine
le0n has quit [Quit: see you later, alligator]
le0n has joined #asahi
<tpw_rules> Glanzmann: does pcie work on it?
<joske> well, wifi works, that is via pcie?
<tpw_rules> i think so. what patches?
<tpw_rules> sven's series?
waagrr has quit [Ping timeout: 480 seconds]
<tpw_rules> Glanzmann: i don't see a 4k kernel script in your git?
jx0 has quit []
joske has quit [Remote host closed the connection]
Techcable has joined #asahi
waagrr has joined #asahi
<povik> marcan: hey this needs to be cleared in GUARD_SILENT: https://github.com/AsahiLinux/m1n1/blob/main/src/exception.c#L191
chadmed has quit [Read error: Connection reset by peer]
chadmed has joined #asahi
<chadmed> Glanzmann: thanks for picking up on the lack of --recursive in m1n1. As for the untethered booting, i think it should stay in. the point of the guide is to get developers into a kernel, and being able to do that untethered is a part of that
<chadmed> most people wont even read that far down tbh, as soon as the they get penguins theyre going to close the page :D
jx0 has joined #asahi
<mini> as a more generic m1 pro/max question - do we know why the other half of the neural engine seems to be disabled?