#
…

2021-12-02

00:33bgb has joined #asahi
00:35bgb_ has quit [Ping timeout: 480 seconds]
00:53g0d0h0 has joined #asahi
00:53g0d0h0weird link.. a guy used a 400$ scanner to scan his body for radio frequencies and found bio technology in a human being https://www.youtube.com/watch?v=E1ZqRhe4lZE
00:54g0d0h0 has left #asahi [#asahi]
01:20bgb_ has joined #asahi
01:21bgb has quit [Ping timeout: 480 seconds]
01:37chadmed has joined #asahi
01:47darkapex1 has joined #asahi
01:52darkapex has quit [Ping timeout: 480 seconds]
02:08yuyichao has quit [Ping timeout: 480 seconds]
02:09chadmed has quit [Quit: Konversation terminated!]
02:26kode54cool, first time I've seen bot spam here
02:40yuyichao has joined #asahi
03:06PhilippvK has joined #asahi
03:06chadmed has joined #asahi
03:09phiologe has quit [Ping timeout: 480 seconds]
03:52kov has quit [Quit: Coyote finally caught me]
03:52kov has joined #asahi
04:03phiologe has joined #asahi
04:07PhilippvK has quit [Ping timeout: 480 seconds]
04:14marvin24 has joined #asahi
04:17marvin24_ has quit [Ping timeout: 480 seconds]
04:22darkapex1 is now known as darkapex
04:27artemist has quit [Quit: artemist]
04:37chamomile has quit [Ping timeout: 480 seconds]
04:57artemist has joined #asahi
05:19chadmed has quit [Remote host closed the connection]
05:36chamomile has joined #asahi
06:13sailorek1234 has joined #asahi
06:23d0p1__ has quit [Ping timeout: 480 seconds]
06:24VinDuv has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
06:25VinDuv has joined #asahi
06:46hspak has joined #asahi
07:08bgb has joined #asahi
07:10bgb_ has quit [Ping timeout: 480 seconds]
07:24bgb has quit [Remote host closed the connection]
07:25bgb has joined #asahi
07:30tertu2 has joined #asahi
07:30chamomile has quit [Ping timeout: 480 seconds]
07:33tertu has quit [Ping timeout: 480 seconds]
08:19bgb_ has joined #asahi
08:22bgb has quit [Ping timeout: 480 seconds]
08:56bgb_ has quit [Ping timeout: 480 seconds]
09:20mpskettenis: latest apple-m1-m1n1-nvme works on machine where macos 12.0 is installed, booted it with efi prepared usb stick and grub-efi
09:21mpsI have to test later if it can boot using simple config with extlinux.conf
09:23mpsnot sure should be the dtb from kernel or from u-boot used when creating u-boot.macho
09:23mpsin first try I user one from u-boot
09:25mpsbut with it and booted from usb stick I don't see nvme detected by kernel
10:25ar has quit [Ping timeout: 480 seconds]
10:26chamomile has joined #asahi
10:30as400 has joined #asahi
10:31as400mps: I'm also trying to compile u-boot but I get errors. Which gcc version are you using ?
10:32mpsas400: gcc (Alpine 11.2.1_git20211128) 11.2.1 20211128
10:32mpsthis is on current alpine development branch
10:33as400hmmm - same here - 11.2
10:33as400strange
10:33mpsas400: what error you get
10:34chamomile has quit [Ping timeout: 480 seconds]
10:39ar has joined #asahi
10:44kettenisinstall a cross-compiler and make sure you set the CROSS_COMPILE environment variable properly
10:45mpsas400: did you cloned git repo and checkout apple-m1-m1n1-nvme branch or downloaded zip file
10:45kettenismps: does the nvme disk now show up in u-boot?
10:46mpskettenis: yes, if usb stick is not inserted
10:47mpsit even found /extlinux/extlinux.conf but says can't load kernel, I have to look did I created it properly
10:48mpsif the usb stick inerted it doesn't show nvme is found
10:50chamomile has joined #asahi
10:50as400I do "make ARCH=arm CROSS_COMPILE=arm-none-eabi-" and I cloned the branch with git
10:51mpsas400: shouldn't it be ARCH-aarch64
10:51mpss/-/=/
10:51_jannau_does the dtb yes, also in cross comple
10:52marcandefinitely not going to work compiling for 32-bit arm :-)
10:53_jannau_s/does the dtb//
10:54mpskettenis: just restarted, u-boot says Invalid pxeadress: /extlinux/extlinux.con trying to boot from nvme
10:56mpsand later lines says it can't recongnize filesystems, and at the end 'no EFI system partition' (which is true, I didn't created EFI partition)
10:58mpskettenis: so, good progress, thank you
10:58chamomile has quit [Ping timeout: 480 seconds]
11:00mpsOT question, but anyone here knows how to increase character size on screen for u-boot (I tried with utf8 option but got blank screen)
11:01kettenisnot sure the "legacy" boot path works; I've only tested the EFI boot path
11:01mpsI plan to convert nvme boot partition to efi today anyway
11:01kettenisthe kernel might not see the nvme driver because u-boot already initialized the coprocessor
11:02ketteniss/driver/drive/
11:02mpsand keyboard also
11:02kettenisI think sven is working on making that a little bit more robust
11:03marcankettenis: u-boot should perform the shutdown sequence though
11:03svenyeah, that'll be fixe
11:03sven*fixed
11:03mpsI have little experience with grub
11:03marcanbut yes we can kick it with the reset bit too
11:04kettenismarcan: well, OpenBSD currently relies on u-boot starting the corporcessor
11:04mpsnot sure is it possible to pass 'FDT' parameter with grub
11:05marcankettenis: that's... not ideal :-)
11:05marcanmps: the devicetree is passed from m1n1, before u-boot; it is not something you specify later
11:06kettenisI want to change it eventually, but I'm waiting on sven to settle on the rtkit/sart/nvme bindings ;)
11:06sventhat's what vacations are for! just need to work for two more weeks and then i'll have time to do that ;)
11:07mpsmarcan: ah, that is why it doesn't found keyboard, I created u-boot with its dtb
11:07marcanthe internal keyboard is not supported in u-boot
11:08kettenisthe spi and keyboard bindings in that tree are what I currently use in openbsd
11:08mpsI know, but it also doesn't work later when kernel boots
11:08kettenisbecause the correllium compatibles make no sense
11:08kettenisyou can either change your kernel to use the ones in "my" device tree
11:08* marcanwishes people wouldn't be so impatient that they insist on using known-bad-and-obsolete code...
11:09the_lanetly_052 has joined #asahi
11:09kettenisor change the device tree to match what the corellium drivers use
11:09kettenismarcan: heh
11:09marcanor just wait until we have a proper SPI driver :p
11:09marcanseriously though, people testing known-bad code doesn't really help anyone...
11:09sventhat kinda applies to my nvme code as well :-P
11:09mpsI just testing things and report here what I find
11:10marcanI'm going to rename the t6k branch to something more useful
11:11marcansven: maybe, but at least it's on the way and built on a sane RTKit WIP
11:11marcanI mean, compare that with what corellium did for NVMe...
11:36jkm has joined #asahi
11:52the_lanetly_052 has quit [Ping timeout: 480 seconds]
11:59as400I want to help testing kernel changes. Which branch should I use ? Is there a proper config somewhere ?
12:01svenjannau’s branch or arch package or I guess the asahi branch now
12:03as400Does it also include that unfortunate corellium code that marcan insisted not to test ?
12:03as400I mean pkgbuild is very handy for me.
12:04mpsI think it does, keyboard part
12:04svenHrm, was maintaining that thing with individual patches too annoying?
12:06marcanhonestly with all the rebasing and DT conflicts going on, patches seems painful right now
12:08as400So maybe this pkgbuild should be pointed to asahi branch - so people test things that are useful to you guys ?
12:17kettenisthe hard reality is that it probably isn't very useful to test something that deviates significantly from that branch
12:19darkapex1 has joined #asahi
12:24darkapex has quit [Ping timeout: 480 seconds]
12:53jannauhandling 76 or so patches became annoying. the single patch is not strictly a single patch but a mbox created by `git format-patch --stdout`
12:54Dcow_marcan: regarding the installer: I think it is no reason to change from python at least right now. Once it will be closer to "production ready" state, I may work on wrapper or the machine readable CLI to make a calls from GUI.
12:55Dcow_what are the requirements to run under 1TR?
12:55marcangood question :-)
12:55marcanthere are fewer tools/frameworks available, but obviously they have quite a bit
12:55marcanyou just need to test it I guess
12:57Dcow_what do you want from the installer UI?
12:57Dcow_disk partition tool, selection the macos source to copy the fw, what else ?
13:11marcanthe FW isn't copied from an existing macos, it's downloaded from Apple so it would be choosing a version from those we support / are usable on this machine
13:11marcanalso choosing what distro/image to install (optionally)
13:18Dcow_what about FW that forged into MacOS drivers?
13:20Dcow_like AVD or the second usb's for m1 iMAC
13:20yuyichao has quit [Ping timeout: 480 seconds]
13:27marcanthat comes from the kernelcache that's already being downloaded
13:27marcanall the firmwares will come from the chosen IPSW, we do not mix and match with the running system
13:27Dcow_I see thanks
13:28Dcow_is there anyone who can work on some-kind of UI mockups?
13:40landscape15[m]Dcow_: Which GUI framework do you want to use?
13:44yuyichao has joined #asahi
13:44Gaspare has joined #asahi
13:55Dcow_Not sure yet. Might Be Qt or Flutter
13:55Dcow_of those won't work on 1TR then gonna learn some swift ui
14:01marcanQt would be nice, since it has nice Python bindings and can make it easier to test on Linux, though it might be a bit heavy to ship
14:01marcanbut then again we're already downloading 1GB for the installs anyway
14:03robher_ has quit []
14:03robher has joined #asahi
14:06Dcow_Flutter on linux also work good. Personally I prefer it over Qt. But we need to decide what suit better.
14:06Dcow_p.s. Canonical working on Flutter installer for Ubunty
14:11the_lanetly_052 has joined #asahi
14:12aleasto has joined #asahi
14:20landscape15[m]Dcow_: I think any type of UI doesn’t work good in 1TR. It is very limited.
14:22matthewayers[m]Sorry, what is 1TR?
14:24landscape15[m]matthewayers: One True Recovery. It’s the APFS container for the macOS recovery.
14:30marcanthey run Safari in there, they obviously have all the core stuff
14:31matthewayers[m]Are those sites limited to basic HTML/CSS/JS/TS functionality?
14:33jnhm, a web UI viewed in Safari would be an interesting solution for the installer
14:34matthewayers[m]I know that some companies use a web UI for setting up iPads on-device, so it’s definitely possible
14:40matthewayers[m]I also just remembered that my work MacBook Pro literally requires me to sign into Microsoft in order to log in
14:41woutermarcan: didn't see your brain dump last night until now :-)
14:41woutermarcan: Debian has traditionally had a "this is everything you need" download on their site
14:41woutermarcan: I think we want to keep things that way (yes, "we", I'm wouter@debian.org ;-)
14:42woutermarcan: we've also had a "w32installer" thing which downloads the netinstall under Windows and then modifies the boot system to include "Install Debian" in the Windows boot menu
14:42wouterI could imagine something similar to be written for M1 macs
14:42wouteranyway, all that are just wild thoughts
14:43jkm has quit []
14:50marcanwouter: well, the process involves at least two mandatory reboots, and to make it as user friendly as possible you need to do streaming partial ZIP file fetches from Apple's CDN, firmware cutting and filename munging, manually creating a macOS stub partition with all the Preboot directory structure (which involves parsing and understanding Apple's manifest plists), also you need to race to kill ...
14:50marcan... Apple's boot picker before it reboots because we don't have proper tools to do that programmatically yet, etc
14:50marcanif you *really* want to re-implement all that for Debian, I won't stop you... but I imagine most distros will be perfectly happy telling people to `curl alx.sh | sh` from recovery mode, follow the prompts, then plug in some EFI USB install media :-)
14:53marcanfwiw the current installer does not have an offline option, but it's trivial to implement with the caveat that you need to tell people to download the entire ipsw from Apple, and that means 14+GB instead of the ~1GB of partial contents the installer will normally download
14:53marcan(and it means you need to figure out *what* ipsw they need ahead of time using documentation instead of having the installer magically work it out)
14:54woutermarcan: that, or ship it as part of the install media?
14:55woutermarcan: I'm sure you can do "sh /Volumes/debian/alx.sh" or some such, too
14:55marcanyou can't ship Apple's IPSWs, they are not redistributable
14:55marcanso that part is either online or tell people to download it on another machine and copy it to the install media, or similar
14:55wouterno, but we can ship your script I would hope? ;-)
14:55marcanof course
14:55wouterthat's what I meant
14:56marcanyeah, you can ship the installer and I'm also happy to make it more modular than it already is (it's python fwiw) in case people want to wrap it in their own UI or whatever
14:56wouterd-i doesn't ship with python, and adding that is going to be complicated I would guess
14:56marcanthis runs under macos
14:57marcanwe ship python with the installer
14:57wouteroh right
14:57the_lanetly_052 has quit [Ping timeout: 480 seconds]
14:57wouterof course it would be awesome if apple just added their firmware to LVDS... but meh, I guess that's not going to happen
14:58marcanit's not just that
14:58wouterI realize that
14:58wouterbut if it was there, then there are tools already written
14:58marcanthe way this works is that the OS demarcation point is *not* the unsigned code demarcation point
14:59marcanthat means that any third-party OS needs to first install the signed boot components from Apple, *then* install itself as the next stage, all within its own OS container
14:59wouterso that could make it easier to extend installers to download the necessary firmware? or something
14:59marcanand because they don't keep firmware ABIs stable, all that comes as one bundle including signed firmwares loaded by the prior components that expose an unstable ABI to the OS
14:59marcanso part of this whole dance is picking macOS versions to bless as "Linux is compatible with these ABIs"
14:59wouteranyway, again just wild thoughts and I can't say I have a lot of knowledge on the subject, other than you, so feel free to ignore if I sound stupid ;-)
15:00marcangetting the firmware bits that Linux itself needs is easy, you can re-do that if you really want to using some other script; the hairy bit is setting up what is essentially a macOS install minus the root filesystem
15:01marcanwhere we then replace the XNU kernel with our bootloader that bridges into U-Boot and EFI services
15:01wouterand yes, obviously not-stable ABIs makes things more complicated... I remember similar things from way back when I had a powerbook running Linux as my primary laptop
15:01marcaneffectively the Asahi Linux installer is... a macOS installer, for all practical purposes
15:01marcanit just doesn't do the "copy out the rootfs bit"
15:01marcanyou could literally just... do that instead of running step2.sh as it tells you, and end up with a functional macOS install (ish, there's the signed system volume thing to deal with, but you get the idea)
15:02wouter right, I do
15:03matthewayers[m]marcan: would something like this be helpful for finding a way to kill the boot picker? https://developer.apple.com/documentation/kernel/kernel_functions
15:03wouterdo you think it is likely you'll be able to reduce the dependency on unstable firmware stuff at some undefined point in the future, or do you think this is how things will have to be for the foreseeable future of apple silicon ARM chips?
15:03marcanmatthewayers[m]: those are kernel functions, we can't run kernel code
15:04marcanwouter: this is their design, I don't see them changing it. however, as long as we can pick a macOS version to pin to, we don't have to support all possible ABIs
15:04marcanso we only need to upgrade when there are important bugs fixed or new machine support
15:04marcanthis does *not* limit what macOS versions the user can have installed, it's just what "macOS" our partition is based on
15:04marcan(as long as system firmware is equal or newer)
15:04wouteroh, right
15:07marcan(I still haven't figured out how to do upgrades, fwiw; I think that would involve another couple reboots and re-provisioning our bootloader, but I need to run some tests)
15:08marcanthis is relatively cumbersome in part because Apple's secureboot requires users to assert physical presence (via long pressing power) before they can install a third-party bootloader, and *that* action, since 12.x, has to happen in a paired recoveryOS for the OS you're trying to mess with, which means it has to happen *after* you've already installed the boot components
15:08marcanso right now the installer does its thing, then drops a .sh file and tells users to boot holding down power, go to options, pull up the terminal, then run it and follow the last few prompts
15:09marcanand that will finally install m1n1 as the "macOS" kernel
15:09sailorek1234 has quit []
15:11marcanI should also do an offline install test (truly offline, i.e. no phoning home by Apple's stuff); I think that won't work right now but I know how to make it work
15:12wouterdo I understand correctly that it won't be possible to upgrade apple firmware for Linux, then? Or is that something that might theoretically be possible but you just haven't gotten around to it yet?
15:13marcanI'm not sure, actually; it's uncharted territory.
15:13wouterfair enough
15:13wouteryou've got plenty of other stuff to do, I guess :)
15:14marcanin principle once we figure out SEP, we could access the services that make this possible, but we wouldn't be able to provision a new m1n1 because that only works from recovery mode; however, I don't know if we'd be able to update the boot policy with a new NSIH (the hash of the apple boot stuff) while preserving the existing m1n1
15:14marcanthat's a long way out though, and would also involve re-inventing more of Apple's process
15:14Gaspare has quit [Quit: Gaspare]
15:16marcanright now the installer uses a hybrid approach where we copy all the "raw" files from the installation image, which Apple's magic bootability code (which runs when the user selects the volume to boot, or if we use bputil) then copies and personalizes into the actual boot directory that the first-stage bootloader will use
15:16Retr0idRE: possibly using safari as an installer UI: I just tested, you can visit a locally-running httpd from 1TR's safari, although I couldn't get it to actually visit localhost for some reason - I had to use a public domain that resolves to 127.0.0.1
15:16marcanI mostly know how all that works, but haven't attempted to do it myself
15:17wouterokay, thanks for the info
15:17marcanRetr0id: I wasn't actually thinking about that, but... that might not actually be a bad idea, bottle.py and some HTML/CSS/JS is a lot lighter weight than any UI framework we might choose
15:17wouterI was thinking of doing the minimal bits necessary to make debian-installer work on an m1 mac, but I guess it's just too early for that ATM...
15:18wouterbesides, I'm way too busy with other projects already anyway, so I really shouldn't be taking on yet another project :-D
15:18marcanyeah, I'd recommend lurking for a bit as we put together something end-user-approachable for the installer :)
15:18marcanI plan on doing an Arch Linux ARM remix as a reference, which will also give an idea of what bits and pieces have to change
15:19marcanmostly the firmware copying stuff and such
15:19wouteryeah, I think I'll do that for the time being
15:19wouter(well, I am already doing that on twitter, but hey)
15:20marcanI'm also going to write a spec for the prebuilt distro images as part of that, in case you're interested in shipping like that too (i.e. as an option in our installer, bypassing d-i and just dumping out a rootfs, more like the typical cloud imaging stuff)
15:21wouterthe downside of that is that it makes certain configuration options inside d-i unavailable
15:21marcanyes, of course, it's limited
15:21woutere.g., do you want full-disk encryption, LVM, some other device-mapper stuff, etc
15:22wouterso while that can work initially, eventually you'll want to be able to boot d-i at some point
15:22marcanfor people who want that they'd want to run a proper installetr
15:22wouterbut it could be a way to get things working intially, sure
15:22marcanthough as I said I would expect most EFI-compatible installers to work out of the box, modulo kernel, as far as the general flow is concerned
15:23marcanwe could also give users the option of "installing" the installer as a netinstall ramdisk or whatever, and then have that run on first boot and install the real distro
15:23wouterwell, yes
15:24wouterbut I think the advantage of having a "this is everything you need to download" on a distribution's site is not to be underestimated
15:24wouteryou don't want to confuse users with "yes you can install Debian, but you need to also download this other thing from this other site here"
15:24wouterintegrating things into one package is what distributions *do*
15:25marcanwell, the way I see it is that our curl|sh makes your Mac into something Linux capable, then you can just boot whatever installer you want from USB :-)
15:25kettenisexactly; it is more like a BIOS update ;)
15:25wouterthe way I see it is, Debian ships a USB image, which comes with the curl|sh thing that you run from macOS, then you reboot into d-i and get going
15:26marcanbut you can certainly ship our script, it just needs a bit of coordination since I want to avoid significant divergence (especially since people will want to be able to upgrade with the curl|sh method or some other download... we don't want to end up with divergent installers somehow getting confused by each other's output)
15:26wouter(except it won't be "curl|sh", just "sh" of course)
15:26marcanalso one advantage of the curl|sh method is that when Apple ships new machines we can support with just DT changes, we do that on our end and magically all distros work already, no re-building install images ;)
15:27etaI wonder whether you could even have the debian USB do the fancy macOS thing where the disk opens with a background image that tells you what to do
15:27eta(like disk images on macOS do with the "drag this into the applications folder" imagery)
15:27marcanI'm not sure if that works from recoveryOS
15:27woutereta: that's actually very easy, it just ships with a hidden file in the directory that finder sees
15:27* wouter<- does that for work
15:28woutermarcan: well, probably not, but it would still be useful if you had it for the initial "install this" USB thing
15:28marcanyou *can* run the installer from macOS but it comes with one caveat: that way requires phoning home to Apple and Apple can (and probably will) cut off old macOS versions from this method at some point, for security reasons
15:28marcanso at least for our normal docs I'll tell people to boot and run our installer from 1TR, since it eliminates that variable
15:29marcan(and either way you still need to do a reboot into the new 1TR recoveryOS and run step2.sh, regardless of what initial environment you chose)
15:29woutermy point is, the "background image" that eta talks about is easy to add to an "install image", and that image can then just give you instructions to reboot into 1TR and then run the script
15:29marcanoh sure, that works
15:30wouteranyway, time to go home now
15:30marcanand I should sleep :)
15:30woutergood luck with that then :)
15:46chamomile has joined #asahi
15:50jkm has joined #asahi
15:54chamomile has quit [Ping timeout: 480 seconds]
15:56matthewayers[m]I agree that Safari should be used as a UI if possible because it would make for a much more elegant solution than trying to load some other UI instead.
15:58aleasto has quit [Quit: Konversation terminated!]
16:02aleasto has joined #asahi
16:08as400 has left #asahi [#asahi]
16:15Retr0idI'm currently trying to figure out how to launch safari with a localhost url, programatically (among other things, `open` does not exist in 1TR)
16:16___nick___ has joined #asahi
16:17___nick___ has quit []
16:18___nick___ has joined #asahi
16:19matthewayers[m]Would it be possible to bundle a command similar to “open” with the installer?
16:20matthewayers[m]…such as asahi-open?
16:20matthewayers[m]* Retr0id: Would it
16:23Retr0idI suppose. I will do some research into how `open` actually functions
16:24matthewayers[m]I might decompile it in Ghidra to see what it relies on. I honestly wouldn’t be surprised if it’s basically a wrapper around a system command
16:27Retr0idinvoking the Safari binary directly, with a local file path "works", but it spawns a file picker dialogue asking you to confirm your choice, which is a bit janky
16:27Retr0id(the local .html file can then redirect to localhost)
16:32matthewayers[m]I had trouble finding `open` so I'm terrorizing my computer instead...
16:34marcan`which` is your friend
16:34marcanalso it's like 300kB and calls into a pile of frameworks... also I'm pretty sure whatever API it uses is documented
16:36matthewayers[m]Noted. `grep` just finished running.. haha
16:41matthewayers[m]marcan: Thanks for the suggestion! I found it in my output but it truncated to ./bin/open instead of /usr/bin/open, so `which` saved me a lot of headache there
16:46chamomile has joined #asahi
16:47chamomile has quit [Remote host closed the connection]
16:52NightRaven[m]Like is there a way i can boot asahilinux on my mac i dont really care about the gpu acceleration yet since i won't be playing games. Just running it on bare metal
16:58j_eyNightRaven[m]: yes the wiki has some steps, although its maybe a bit out of date
16:59marcanRetr0id: the file picker is because of the sandbox
17:00Retr0idah - is there a sandbox-friendly path I can drop an html file in?
17:00marcanif you drop the HTML file in /var/root/Library/Containers/com.apple.Safari/Data/foo.html and open it as Safari foo.html it works
17:00marcanno picker or anything weird
17:00matthewayers[m]marcan: I decompiled using Binary Ninja and I'm seeing what you're referring to for `open`. Do you think we could bundle something similar to this to the installer to launch the web UI in Safari?
17:01marcan^^ just use an HTML file
17:01marcanonly annoying issue is it spawns behind the terminal
17:02NightRaven[m]j_ey: oh ok thx : )
17:04qw4q has joined #asahi
17:05matthewayers[m]marcan: I wonder if there's some way we can get around that.. some sort of manipulation of the window manager?
17:05Retr0idcan confirm that an html file with a meta redirect to localhost works as expected
17:06matthewayers[m]Retr0id: Does that launch in front of or behind the terminal?
17:06marcanmatthewayers[m]: probably, but at that point it would involve writing a helper tool most likely
17:06Retr0idbehind terminal still
17:06Retr0idcould kill the terminal I suppose
17:06marcanosascript can do that in macos, we could just invoke the relevant APIs ourselves
17:07marcankilling the terminal is probably a bad idea, because it'd bring back the recovery menu
17:09d0p1__ has joined #asahi
17:09matthewayers[m]What about hiding the terminal, similar to what CMD+H does? Does that even exist in recovery mode?
17:10marcanwe're probably going to wind up needing a helper app to do some macos interactions like this anyway, might as well bite the bullet
17:10marcanthat should also be able to launch safari with a URL properly without hacks
17:12qw4qhi guys, sorry for the basic question, I've been googling this for days: Does Asahi linux work well inside VMs on an M1, since I'm guessing that there does not need to be M1 specific kernel support when run inside a VM?
17:13qw4qor is there huge work ahead to get lots of packages compiled on arm64
17:13j_eyqw4q: no m1 support needed inside a VM on m1
17:13etaqw4q: you don't need Asahi Linux for that
17:14qw4qi need to be running a distro compiled for arm64 though right?
17:14qw4qor is qemu x64 emulation good?
17:15j_eyqw4q: are you talking about on macos or?
17:15qw4qi'm just wondering how hard it'd be to get a VM set up with chrome browsing on an M1, which had good enough gpu acceleration support to be snappy
17:15qw4qj_ey yes macos on an M1
17:17qw4qi noticed, for example, that ubuntu don't have an arm64 desktop edition, and instead you need to install the arm64 server edition and then install the desktop package
17:17qw4qso i'm wondering that's because it's all a bit broken
17:18j_eyno that should work fine
17:18qw4qs/wondering/wondering if
17:19qw4qj_ey oh wow, you're blowing my mind, thanks. So I won't have the constant pain of an arm64 package not being available? As far as I can see, there is no x64 emulation or plans for x64 emulation to run non-arm64 packages
17:20Gaspare has joined #asahi
17:20psykosegames aside arm64 should have pretty much everything
17:21Gaspare has quit []
17:22qw4qpsykose ok great, thank you
17:22Retr0idI have an ubuntu "server" VM (with ubuntu-desktop installed) running in UTM nicely
17:22qw4qRetr0id is it nice and snappy?
17:23qw4qi've had problems in the past simply trying to scroll through web pages in VMs if there wasn't proper GPU acceleration
17:23Gaspare has joined #asahi
17:24Retr0idits fine even with software rendering
17:24Retr0id there's even experimental gl acceleration passthru stuff working, although I haven't tried that yet
17:25qw4qRetr0id ok thanks, that's great. I currently have Ubuntu running inside a Parallels VM, and performance really isn't very good, even on my i9 MBP
17:25qw4qand that is GPU accelerated as far as i know
17:31crabbedhaloablut has joined #asahi
17:31loki_val has quit [Ping timeout: 480 seconds]
17:40crabbedhaloablut has quit [Ping timeout: 480 seconds]
17:40crabbedhaloablut has joined #asahi
17:50mpsqw4q: I'm running arm64 distro inside qemu VM on M1, works fine
17:51mpsthough I had to build qemu from git repo to get HVF accelation
17:52mpsacceleration*
17:53j_eyat least it has been merged now :)
17:54mpsyes, it is, but not yet released stable
17:55mpsabout year ago had to hunt patches around
17:56qw4qmps thanks
17:56qw4qactually what a great coincidence, AWS just announced M1 instances to rent
17:57qw4qso i can test things
17:57qw4qalthough of course, that probably won't give me a good idea of e.g. scrolling responsiveness when i remote desktop into a VM inside an M1
17:58matthewayers[m]Ooh that could be really useful, but I also need to keep my AWS bill under $30/month (thanks, college)
17:59qw4qlooks like scaleway rent them by the hour too
18:02minithe aws pricing is pretty extortionate last I checked
18:02matthewayers[m]Something like $15 per day?
18:04mini$1.083 an hour for the intel one, with a 24hr minimum
18:05minithe M1 ones are $0.6498/hr while in preview with a 24 hour minimum
18:05sveniirc the 24h minimum comes from apple's eula
18:06matthewayers[m]Interesting...
18:06qw4qoh scaleway are much cheaper then
18:06miniyeah, it does. but that's up to $483/mo
18:06qw4qand looks like i have to sign up for the m1 aws preview and request access
18:06miniin two months you could just buy a mac mini
18:07mini(744hrs is the most in a calendar month, afaik?)
18:07miniscaleway's 0.1 EUR an hour is considerably cheaper, but I think they're struggling for stock
18:08qw4qyeah resale prices on M1 minis are so incredible that if you just buy and sell on ebay, "rental" is just postage and only a few percent in depreciation
18:08minior you can buy direct from apple and return it inside 14 days if you don't like it
18:08minior at the moment, you actually get until jan 8th in some countries
18:08Retr0idjust wrote a tiny swift program to open an URL, works nicely in 1TR
18:09qw4qalthough there aren't discounts on the m1 mini direct from the apple store
18:09minithere are not, no
18:09qw4qwhereas there are from most retailers
18:09cth451_desktop has quit [Remote host closed the connection]
18:09matthewayers[m]The biggest discounts are education and for veterans/military
18:09minimost retailers don't have the 16GB model though, afaik
18:09cth451_desktop has joined #asahi
18:09Retr0idactually I spoke too soon, it opened safari but not to the correct url...
18:10matthewayers[m]What did it open to then?
18:10svenlooks like you get also rent a m1 at hetzner for ~60eur/month
18:10sven*you can
18:11Retr0idit opened to the default homepage
18:11gig has quit [Remote host closed the connection]
18:11matthewayers[m]Is there some way to change the default homepage to localhost or that redirect .html file?
18:12Retr0idI'm trying to do things cleanly
18:13matthewayers[m]Yeah, unfortunately Apple isn't giving you much to work with. If it is possible to change the default homepage, however, that could make a clean Safari launch possible..
18:35Retr0idat least it works to foreground safari
18:36matthewayers[m]Yeah, that's at least a plus. It just isn't as elegant. I might go in and play around with it later to see if I can figure anything out.
18:58qw4q has quit [Quit: Page closed]
19:00Mary has quit [Quit: The Lounge - https://thelounge.chat]
19:01Mary has joined #asahi
19:01cth451_desktop has quit [Remote host closed the connection]
19:03cth451_desktop has joined #asahi
19:03Mary has quit []
19:06Mary has joined #asahi
19:13yuyichao has quit [Quit: Konversation terminated!]
19:14___nick___ has quit [Ping timeout: 480 seconds]
19:34Gaspare has quit [Quit: Gaspare]
19:48yuyichao has joined #asahi
20:11Gaspare has joined #asahi
20:12aleasto has quit [Remote host closed the connection]
20:46chamomile has joined #asahi
21:07Gaspare has quit [Quit: Gaspare]
21:24Gaspare has joined #asahi
21:25fgfhmnrtry4r4t[m] is now known as iPhowned[m]
21:43landscape15[m]Sorry my fault :)
21:43i509vcb[m]accidental silence
21:43landscape15[m]i509vcb: yeah exactly ;)
21:59chamomile has quit [Ping timeout: 480 seconds]
22:14d0p1__ has quit [Ping timeout: 480 seconds]
22:24Gaspare has quit [Quit: Gaspare]
22:43chamomile has joined #asahi
23:12jkm has quit [Ping timeout: 480 seconds]
23:49kode54 has quit [Quit: The Lounge - https://thelounge.chat]
23:49KDDLB has quit [Quit: The Lounge - https://thelounge.chat]
23:51KDDLB has joined #asahi
23:51kode54 has joined #asahi
…