#
…

2021-08-18

00:29os has quit [Server closed connection]
00:30os has joined #asahi
00:35citizen1[m]hello, i am wondering if Asahi is successful it won't be any use as all linux software was not made to run on M1/ARM . Am wrong or right?
00:39alyssavirtually all linux software works fine on arm, M1 included
00:49Serentty[m]citizen1: For running x86 software, most of the concern would be about running Windows software.
00:50Serentty[m]Oh, and Linux native games.
00:50Serentty[m]But other than that, nearly everything can just be recompiled.
00:59maximus65 has quit [Server closed connection]
00:59maximus64 has joined #asahi
01:00marcanthere's https://github.com/FEX-Emu/FEX which is basically like Rosetta, for software that cannot
01:08radex has quit [Server closed connection]
01:09radex has joined #asahi
01:23chadmedthat looks like a decent hassle to get set up with a root overlay or chroot, but that would probably make it faster/more compatible than just using qemu-user right?
01:49riker77_ has joined #asahi
01:54riker77 has quit [Ping timeout: 480 seconds]
01:54riker77_ is now known as riker77
01:57citizen1[m]<Serentty[m]> "But other than that, nearly ever" <- so you just put the same source code in a compiler choose ARM and it pops out and ARM version that works on m1/arm chip?
01:58chadmedcode that is optimised for x86 specifically with compiler hints and the like may need some rewriting, but most software packages simply work when being compiled for armv7+ with no changes
01:58chadmedbig binary distros like debian (and its derivatives) will have enormous repos of arm binaries too so i dont think you have anything to worry about
02:01chadmedthere was only one piece of software that gcc didnt like for me. i cant remember what it was but it was because it had some inline assembly written with apple conventions rather than standard armv8, so i just built it with clang instead and it worked fine. i had an entire gentoo/kde plasma user space running on a pi 4 8gb and everything worked as expected
02:07marcanchadmed: qemu-user also needs a chroot
02:07marcanthere's no way around needing an x86 environment, modulo thunked stuff, to run x86 apps
02:07marcanmacos is the same
02:07marcanit'sjust they use fat libs instead of a separate root
02:12yuyichao has joined #asahi
02:17chadmedah yeah i knew it needed the libs, just wasnt sure on the chroot
02:17chadmed(as a separate environment)
02:17jix has quit [Server closed connection]
02:17jix has joined #asahi
02:35PhilippvK has joined #asahi
02:37phiologe has quit [Ping timeout: 480 seconds]
02:53tsida has quit [Server closed connection]
03:03Erus_Iluvatar has quit [Server closed connection]
03:34citizen1[m]ok thanks for the info. I dont understand it all but looks like it wont be problem, because i remember Apple switching to Intel was not this easy
03:35citizen1[m]from reading from the website Asahi achievements will be shared with other Linux distro so they too will work on M1. Am I correct?
03:36grange_c has quit [Server closed connection]
03:37grange_c has joined #asahi
03:53bradfier has quit [Server closed connection]
03:53bradfier has joined #asahi
03:55marvin24_ has joined #asahi
03:58marvin24 has quit [Ping timeout: 480 seconds]
04:12linearcannoncitizen1[m]: most major linux distributions already have very mature 64-bit arm support. the important kernel changes from asahi are being shared upstream, so any linux distribution that wants to will be able to easily add support for M1 macs in the future.
05:12Mary has quit [Server closed connection]
05:13Mary has joined #asahi
05:39VinDuv has quit [Server closed connection]
05:39VinDuv has joined #asahi
06:06arahael has quit [Ping timeout: 480 seconds]
06:07svenalyssa: xnu calls it like that in strings
06:10Xesxen has quit [Server closed connection]
06:10Xesxen has joined #asahi
06:11Erus_Iluvatar has joined #asahi
06:11arahael has joined #asahi
07:01VinDuv has left #asahi [#asahi]
07:10chadmed has quit [Quit: Konversation terminated!]
07:24roxfan has quit [Server closed connection]
07:24roxfan has joined #asahi
07:25bps has quit [Ping timeout: 480 seconds]
07:25izica has quit [Server closed connection]
07:25izica has joined #asahi
07:57besmirich[m] has quit [Server closed connection]
07:57besmirich[m] has joined #asahi
07:59bps has joined #asahi
08:08gabuscus has quit [Server closed connection]
08:09gabuscus has joined #asahi
08:15chadmed has joined #asahi
08:56elosant[m] has quit [Server closed connection]
08:56elosant[m] has joined #asahi
09:03akemin_dayo has quit [Server closed connection]
09:03akemin_dayo has joined #asahi
09:05yrlf has quit [Server closed connection]
09:06yrlf has joined #asahi
09:31smvg[m] has joined #asahi
09:47gladiac has quit [Server closed connection]
09:47gladiac has joined #asahi
10:03Raito_Bezarius has quit [Server closed connection]
10:03Raito_Bezarius has joined #asahi
10:30bdju has quit [Read error: Connection reset by peer]
10:30bdju has joined #asahi
12:04eta has joined #asahi
13:19yuyichao has quit [Ping timeout: 480 seconds]
13:20psydroid[m] is now known as psydroid
13:45yuyichao has joined #asahi
13:45alyssasven: Got it.
14:24yuyichao has quit [Ping timeout: 480 seconds]
14:30svenhttps://github.com/asahilinux/linux/tree/nvme/new still pretty rough and i'm not yet happy with the rtkit stuff, but this at least fixes the "uncleanShutdown" issue
14:31sventurns out that i just forgot to hook up the common nvme shutdown code to the platform driver
15:06alyssasven: whoops?
15:06citizen1[m]<linearcannon> "citizen1: most major linux..." <- Great! I thought Asahi will be the only working distro on M1. I guess I should donate
15:07alyssasven: let me know if you want eyeballs / testing / both / etc
15:08alyssa...what is compat mbox shim?
15:09alyssasven: + *val = readl(to_apple_nvme_dev(ctrl)->nvme_mmio + off);
15:09alyssa+ return 0;
15:12svenalyssa: uh, yeah, that main .c file is essentially pci.c with lots of stuff removed like the maintainers suggested. it's not done yet
15:12alyssaduly noted 👍
15:13svenand that compat shim is because i splitted the rtkit stuff from the mailbox. i used that initially during testing to make sure e.g. smc still works
15:13svenalyssa: that line is actually correct though
15:13alyssasplitting to support SEP down the line?
15:14svenyeah, and because marcan suggested that rtkit library and i wanted to see how that would work out
15:14alyssaergh why won't m1n1 usb come up today
15:15alyssathere we go
15:23krbtgtasahi isn't really a distro. i believe short term is the raw parts, medium term provide a termporary distro with all the mac-specific bits ready to try, and long term germinate it across all other distros
15:31marcanpretty much
15:32marcanwe'll probably be a ready to go distro with bleeding edge stuff ~forever since there will always be newer hardware to support though
15:41tophevich[m]And it will be called NYRA (Not Yet Ripe Asahi) :P
15:42tophevich[m]NYRA Linux (Arch btw.)
15:45* alyssawill just be running stock debian
15:45alyssa(with a kernel and mesa I build myself)
15:49j_eysven: why not #define NVME_MAX_KB_SZ PAGE_SIZE?
15:50sven<sven> uh, yeah, that main .c file is essentially pci.c with lots of stuff removed like the maintainers suggested. it's not done yet
15:51alyssawill alyssa get back to work finally? the world may never know
15:51j_eysven: I thought that comment was yours :)
15:51sveni'm not sure i added even a single comment
15:51j_eysven: mentioned page sizes and sg allocations..
15:52j_eyso you can see how I thought it was yours ;)
15:52svenhehe, sure :)
15:55alyssaoh no it's a regression!
16:04alyssai sure hope it's not what i th-- ah shoot
16:29bps has quit [Ping timeout: 480 seconds]
16:35mlq_ has joined #asahi
16:35mpaq has joined #asahi
16:41mlq has quit [Ping timeout: 480 seconds]
16:42mpaq_ has quit [Ping timeout: 480 seconds]
16:56bps has joined #asahi
17:26kettenissrc/main.c:27:34: error: initializer element is not constant
17:27kettenis const char *const m1n1_version = version_tag + 12;
17:27j_eyclang?
17:28kettenisaarch64-linux-gnu-gcc (Linaro GCC 7.4-2019.02) 7.4.1 20181213
17:30alyssaold version
17:53landscape15[m]marcan: Do you plan to compile asahi-installer into a binary mac app when released?
18:00marcanlandscape15[m]: it's not a binary mac app, it's a shellscript you curl|sh
18:00marcanyou can already curl -L https://mrcn.st/alxsh|sh for the test version, though only use it if you know what you're doing
18:02landscape15[m]Ok thanks. But you need python installed right?
18:04j_eylandscape15[m]: no it comes with python
18:05landscape15[m]Oh sorry. So it is bundled. Thanks again
18:05marcaneverything is bundled, it even runs from recovery mode
18:05marcanthat was a design constraint from the start
18:05j_eyapparently you cant view https://marcan.st/alxsh in a browser
18:05j_ey"You really, really shouldn't be here." :o
18:05marcanj_ey: mrcn.st, not marcan.st
18:06marcandifferent places :)
18:06marcanmrcn.st is a shortener, marcan.st isn't
18:06j_eyoh, you wrote mrcn.st :P
18:06marcanalx.sh is an even cooler shortener though, one character shorter!
18:06bps has quit [Ping timeout: 480 seconds]
18:06marcan(glad I got that one)
18:07marcanon alx.sh I'll have some user agent shenanigans so curl gets served a direct (no redirects) bootstrap for the installer
18:07marcanso -L isn't necessary
18:08j_eyOhhh I know what happened now, I visited "https://mrcn.st/alxsh|sh", took me to "https://marcan.st/alxsh%7Csh", and then I deleted the '%7Csh'
18:08landscape15[m]I think i will try it with caution. So for the end user only a script will be needed.
18:08marcanj_ey: ahh yeah :)
18:08marcanthere's a dumb default for the shortener that just sends you to marcan.st
18:09marcanlandscape15[m]: yes, and there will be an easier "do the typical install for me" mode too
18:09marcanthe goal of the current script was to prototype the bootstrap installation process to get rid of the horrible developer guide mess with installing a whole copy of macos, but niceties like guided resizing and installing a rootfs will come later
18:11landscape15[m]Sounds good :) Then other Linux distributions will easily implement that.
18:13marcanI don't really expect other distros to implement Apple Silicon installers themselves, though of course they can if they want to
18:14marcaninstead the idea is you use our installer to install m1n1+u-boot, which gives you a UEFI/DT environment which you can then use to boot a distro installer (as long as it has an up to date kernel) off of USB or whatever and do it the normal way
18:14marcanbut we'll provide images of distros preconfigured directly in our installer to avoid the separate step of booting the installer, where it makes sense
18:15kettenisin that case the asihi installer doesn't even have to worry about creating a rootfs partition
18:15marcanyeah, but it still has to make space for it by resizing the macOS APFS
18:15soreardoes apple silicon use GPT?
18:15kettenisjust leave space free and let the distro installer handle creating the linux partitions and filesystems
18:16marcanthat's the only thing missing from the current installer, a mode that does resize + everything else it does now
18:16kettenisalready works with the openbsd installer ;)
18:16marcan(well, that and shipping a m1n1 with u-boot built in)
18:19sorearso you'd have an apfs volume with boot firmware, m1n1, and u-boot, and u-boot would then load the final kernel from a Linux filesystem via USB or NVMe?
18:20marcanthat's the plan in all cases
18:20marcansince you need that to be able to upgrade your kernel without going through 1TR, which would be ridiculous
18:20marcanI expect to have a standard EFI partition we let distros install into
18:21kettenisfor most distros it would probably load grub from usb/nvme and grub would load linux
18:21marcanthough nothing stops you from doing it another way directly from u-boot as long as it's a filesystem it supports
18:21kettenisdon't the linux installers create an EFI partition if one doesn't exist?
18:21j_eysorear: and that needs partition is ~2.5GB
18:22marcankettenis: probably, but I wouldn't trust them to do it right in this weirdo case
18:22marcanfor our arch-based install, I expect to have a layout like [macOS for dualboot] [2.5G m1n1 bootstrap] [512M EFI part] [/ ext4] or so
18:23j_eymarcan: how much free space is on that 2.5GB?
18:23marcanwith the kernel in /boot, and GRUB in the EFI part; alternatively you could make the EFI part /boot, I've seen both setups fairly commonly
18:23marcanj_ey: 1G or so
18:23marcanbut APFS kind of wants that
18:23j_eywould be annoying if recovery got bigger
18:23marcan2G is not enough, I tried
18:23marcanwe're not using APFS compression though
18:23marcanapple does
18:23marcanif we can figure out how to do that sanely we save a bunch of space
18:23j_eyoh yeah, I remember that from the stream
18:23marcanso I'll consider that our out if recovery gets bigger
18:24sorearconversely, this setup means that you can nuke the asahi partition and reinstall it from scratch through 1TR without touching the distro rootfs or the distro-created files in the ESP?
18:24marcanwhich is also a feature
18:25marcanand e.g. in the "oh shit recovery got bigger" case, if it comes to that: just shrink macOS a tiny bit more and remake the asahi partition a bit bigger
18:26* alyssalikes debian
18:26marcandebian is a fine distro, I use it on my other Mac! (the PowerPC one :p)
18:27sorearwasn't there discussion earlier of not even needing to change partition sizes for that, because iboot is apfs-subvol-aware?
18:27marcanwe could reuse the macOS container instead of making a new one, but it doesn't really buy us much at this stage
18:27marcanonce linux can actually boot and run stably off of APFS, it suddenly makes a lot more sense because you can have a fully shared disk
18:28marcanbut until then, even though we could avoid the 2.5G stub partition and use volumes in the primary container, I feel a lot safer having our own GPT slice and not touching macOS
18:28marcanmuch easier to nuke and redo
18:29marcanso this is probably going to be one of those user safety executive decisions I make (i.e. the advanced menu of the installer will let you do this, but it won't be the default flow for a while) ;)
18:49kettenisalyssa: now that I'm back home and behind a real keyboard I'll try to give some feedback to the pci series
18:49kettenisthe MSI discussion will probably continue in the earlier thread though
19:08FireFox317 has joined #asahi
19:09FireFox317marcan: will you be streaming tomorrow? :D
19:33tophevich[m]FireFox317: which tomorrow do you mean, his or yours. His is in ~19 1/2 hours as it is 04:33 am in Tokyo
19:34alyssakettenis: Alrighty
19:34alyssakettenis: Warning: I do not know what I'm doing with PCIe.
19:35alyssaLike I still don't know what PCI even stands for
19:35alyssa"Peripheral Component Interconnect"
19:35alyssathx wikipedia
19:47FireFox317tophevich[m]: well today then xd
20:42arekm has quit [Remote host closed the connection]
20:47arekm has joined #asahi
20:48bps has joined #asahi
21:16FireFox317 has quit [Remote host closed the connection]
21:57kettenis has quit [Ping timeout: 480 seconds]
22:49jeffmiw has quit [Ping timeout: 480 seconds]
…