#
…

2021-12-15

00:03tpw_rulesdoes this kernel have the pcie stuff: https://github.com/AsahiLinux/linux/tree/asahi/ ? i've got it booted, but neither usb nor ethernet work. nvme works fine though
00:04tpw_rulesis there a config option i need?
00:04j`eyyes pcie stuff is in mainline now
00:05j`eytpw_rules: CONFIG_PCIE_APPLE
00:06tpw_rulesthen i am confused about what is missing. are the usb and ethernet controllers not in the default config?
00:07Dcow_ has joined #asahi
00:07leah has quit [Quit: WeeChat 3.3]
00:09tpw_rulesoh perfect, thank you
00:42tertu2 has joined #asahi
00:47tertu has quit [Ping timeout: 480 seconds]
00:51yuyichao has quit [Ping timeout: 480 seconds]
01:12tpw_rulesj`ey: that config worked, thank you!
01:13tpw_rulesi assume getting a stable display is dependent on DCP work. is there some kernel branch somewhere i can use to give that a whirl?
01:39tpw_rulesso i've got kettenis uboot booting, but something goes wrong handing off to the kernel. the screen just prints Starting kernel... and the hypervisor console only goes this far: pastebin.com/z0Dc09EM it seems to freeze because the network never comes up
01:39tpw_rulesbooting it without the hypervisor does not help
01:50skipwich has joined #asahi
02:39Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
02:50leah has joined #asahi
03:07PhilippvK has joined #asahi
03:10phiologe has quit [Ping timeout: 480 seconds]
04:52marvin24_ has joined #asahi
04:55marvin24 has quit [Ping timeout: 480 seconds]
05:20marvin24 has joined #asahi
05:22yuyichao has joined #asahi
05:24marvin24_ has quit [Ping timeout: 480 seconds]
05:27marvin24_ has joined #asahi
05:30marvin24 has quit [Ping timeout: 480 seconds]
06:12sailorek1234 has joined #asahi
06:15Glanzmann has joined #asahi
06:16Glanzmanntpw_rules: For the mini, rerun the asahi installer with the oldest version (10.1 I think). That one gives you a display on the mini (on macbook air the newest version also gives you display).
06:16marcantpw_rules: you want keep_bootcon when stuff fails right after the serial init
06:17GlanzmannAbout the resolution, since dcp is currently not working, you can try the following steps (untested - I'll test them if I have the time): https://pbot.rmdir.de/aabP_zkJFhxOIbysRcsJZQ
06:17marcanGlanzmann: anything <12.0.1 works, please don't tell people to go to the oldest firmware for no reason
06:17Glanzmannmarcan: What is the newest that works?
06:18GlanzmannBtw, yesterday a macos update was released, I immediatly tried it, but still does not give video on mini.
06:18marcananything <12.0.1
06:18marcanyes we know
06:18marcanit's looking like I'll have to add iBoot-protocol DCP support to m1n1 to bring up the display
06:18marcan(sigh, thanks apple)
06:19Glanzmannmarcan: Yes, looks like it, but the code is probably already there.
06:19marcanm1n1 has no native DCP support
06:19marcanand nobody has even reverse engineered the iBoot protocol yet
06:20Glanzmanntpw_rules: Than about the xorg. If you want to run wayland, firefox and other applications will just work. If you go with xorg, I recommend on using the 'fbdev' driver instead of the default 'modesetting' Because with the fbdev, firefox works. About video playback. The best results I got was with mpv using the 'drm' driver.
06:20Glanzmannmarcan: Alyssa wrote some experiments for m1n1 which at least sets the resolution.
06:20Glanzmannmarcan: Alyssa has a kernel dcp driver which currently does not work, but worked in the past which was able to do 'hdmi hotplug'.
06:20marcanthose are python
06:21marcanI wrote the DCP python stuff
06:21marcanthat is not using the iBoot protocol nor is it C
06:21marcanI am fully aware of the kernel driver she wrote based on my python :)
06:21marcannone of this helps what I want to do in m1n1 which implies writing a minimal RTKit stack in C for m1n1 and then reverse engineering and writing a minimal client for the iBoot DISP0 service endpoint
06:22marcanbecause we are *not* putting dcpep support in m1n1
06:23Glanzmanntpw_rules: That is what I use: curl https://ab34.de/u/device.conf > /etc/X11/xorg.conf.d/device.conf
06:24Glanzmannmarcan / sven: About the random writes with sync issue, has someone already looked up the nvme device in the apples and looked up, if it has 'powerloss protect - a supercapacitor on the ssd which dumps the write cache on a flash chip on powerloss', if that is the case we can skip the 'flush cache' on the sync.
06:25marcanthe controller is in the SoC, there is no supercapacitor for that
06:25Glanzmannmarcan: I see. So this is no off the shelf device.
06:26marcanwell of course it isn't, otherwise we wouldn't have to write a driver for it
06:28GlanzmannOkay, got it.
06:28chadmedi dont even think its even based on anything, it breaks the nvme spec in a couple of places aiui
06:29marcanit's custom, embedded in the SoC
06:29marcanlike many other things about this SoC
06:31svenI have some outdated rtkit c code for m1n1 somewhere fwiw. Should be in a closed PR I think
06:45GlanzmannOkay, got it.
06:54Glanzmannmarcan: New notebooks have a battery (for the nvme write cache). If you boot up macos on mini, pull the physical plug, the screen stays on for ca. 1 second. Maybe macos uses that second to destage the nvme write cache.
06:54svenspeculation isn’t going to help anyone
06:56marcanGlanzmann: all laptops have a battery, ???
06:56Glanzmannmarcan: My bad. What I wanted to say is the nvme on the notebooks can use the battery of the notebook to destage the write cache.
06:57marcanyes, it can
06:57GlanzmannOn the mini, I just pulled the plug and noticed that my screen stays on for one more second. So maybe they have enough power in a capcitor or a battery hidden in the power supply (has someone disassembled that) to destage the write cache on power loss.
06:57marcanit's obviously safe to not flush caches on a laptop if you have last-gasp handling of some sort
06:58marcanand the capacitor of the system PSU might also be enough to do the same on desktops, if it has last-gasp notification too, though I'm not sure how that works out with the iMacs having it external
06:58marcanthere is no magic battery
06:58chadmedthe M1 mini's power supply has enough capacitance to keep the system going for a second or two if its idling yeah but thats not a substitute for safe disk handling
06:58marcanit's normal for a low power machine to run for a second or so off of the main SMPS reservoir cap
06:58marcanchadmed: it is *if* designed that way
06:58GlanzmannGood point.
06:59marcanwhich we don't know
06:59svenif you want to help go and use my nvme tracer and see what’s up. Throwing out random ideas doesn’t get us anywhere
06:59marcanbut either way cache flushes shouldn't kill performance like they do
06:59Glanzmannsven: Good point.
07:23Rakshit[m]Hey guys, can anyone guide me on how I can start contributing 😅 or if there's anyone who I could join and help?
07:23Rakshit[m]There's so much going on I don't know where to start haha
07:23Rakshit[m]But as for my experience, I know Kernel character Device Development :P
07:32Rakshit[m]s/character/Character/, s/Device/Driver/
07:39pg12 has joined #asahi
07:41pg12_ has quit [Ping timeout: 480 seconds]
07:56darkapex has joined #asahi
08:00somkls^ has joined #asahi
08:01darkapex4 has quit [Ping timeout: 480 seconds]
08:18darkapex1 has joined #asahi
08:23darkapex has quit [Ping timeout: 480 seconds]
09:40aleasto has joined #asahi
10:16Dcow_ has joined #asahi
10:21kenzie has quit [Remote host closed the connection]
10:22kenzie has joined #asahi
10:38Dcow_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:12etamarcan: progress report typo: "following Apple’s exiting naming convention"
11:12etaexiting -> existing
11:12marcanfixed, thanks :)
11:13jnoh, a new blogpost, exciting!
11:15minithanks to everyone who's been involved in the project so far :) my m1 mac mini now boots up into debian so I can use it as a local & fast arm64 build machine!
11:36jkm has joined #asahi
11:37jkm has quit []
11:53conradev has quit [Quit: -]
11:55conradev has joined #asahi
11:59sorearI just want to say that I love what you did with the color-coded support matrix
12:05mpsjust built latest asahi kernel and booted it. keyboard works (I'm typing on it right now) and touchpad work
12:07mpssound driver is loaded but doesn't work. got this in dmesg: PS mca1: Failed to reach power state 0xf (now: 0x24f)
12:07StupidYui has joined #asahi
12:08mpsvery good progress, thanks all who works on this
12:17mpstouchpad is too sensitive, can move cursor even without contacting surface
12:23al3xtjames0 has joined #asahi
12:24al3xtjames has quit [Read error: Connection reset by peer]
12:24al3xtjames0 is now known as al3xtjames
12:54aafsmarak[m] has joined #asahi
12:55mpsf2fs doesn't work, dmesg says '07:21 .....................@marcan| I wrote the DCP python stuff
12:55mpsuh sorry
12:55aafsmarak[m] has left #asahi [#asahi]
12:56mpsf2fs doesn't work, dmesg says '07:21 .....................@marcan| I wrote the DCP python stuff
12:57mpssorry again
12:57mpsF2FS not supported on PAGE_SIZE(16384) != 4096
12:57mpskeyboard and touchpad are to sensitive
12:58j`eyI assumed it was a PAGE_SIZE issue, but nice it's that explicit about it
12:58svenah yes... that reminds me that i also need to pick up those dart patches for 4k page size again
12:59mpsI'll rebuild with 4K and check
12:59svenwith 4k anything attached to pcie will not work fwiw
12:59sven(no usb a ports, no wifi, no ethernet at least)
12:59j`eymps has a mbp, so just no wifi
13:00svenand no sd card reader
13:00mpsI'm not sure but I think usb worked when I build it with 4K about week ago
13:00svenyes, usb *C* works
13:00j`eybecause that's USB C, not USB A
13:00svenusb *A* on the mini doesn't
13:01mpssven: aha, that is
13:13Dcow_ has joined #asahi
13:13Dcow has quit [Read error: Connection reset by peer]
13:25chadmed has quit [Quit: Konversation terminated!]
13:25chadmed has joined #asahi
13:25mpsyes, on mbp with 4K pages f2fs works and also usb-c
13:25mpsbut firefox still doesn't
13:33Dcow has joined #asahi
13:36GlanzmannWhat is f2fs?
13:36mpsflash friendly filesystem
13:39Namidairocompression does not exist on it to give you more space, it's there for flash endurance :P
13:44mpsNamidairo: compression is added in last few kernels
13:49j`eymarcan: planning on having a stream this week?
13:50marcanj`ey: yes, haven't decided when yet though
13:50marcanI wanted to do it today but ended up with too many things to pick at
13:51j`eyGlanzmann: yup
13:53j`eymarcan: look forward to it, if/when it happens ^_^
14:19nilsi[m]Looks like the September progress report is pinned still on the asahi twitter account.
14:21marcannilsi[m]: thanks, just updated it :)
14:28kyoto has joined #asahi
14:34kyoto has quit [Remote host closed the connection]
14:36darkapex2 has joined #asahi
14:41darkapex1 has quit [Ping timeout: 480 seconds]
14:48sailorek1234 has quit [Quit: sailorek1234]
14:50c10l8 has joined #asahi
14:56guan_ has joined #asahi
14:56aeroraptor_ has joined #asahi
14:56sjg1_ has joined #asahi
14:56philpax_ has joined #asahi
14:56tertu has joined #asahi
14:57c10l has quit [Ping timeout: 480 seconds]
14:57jabashque_ has joined #asahi
14:57Lightsword_ has joined #asahi
14:57nkaretnikov_ has joined #asahi
14:57tardyp_ has joined #asahi
14:57sorear_ has joined #asahi
14:57Vaughn_ has joined #asahi
14:58guan has quit [Ping timeout: 480 seconds]
14:58guan_ is now known as guan
14:58nkaretnikov has quit [Ping timeout: 480 seconds]
14:58nkaretnikov_ is now known as nkaretnikov
14:58gruetze_ has joined #asahi
14:58sorear has quit [Ping timeout: 480 seconds]
14:58sorear_ is now known as sorear
14:58tbodt_ has joined #asahi
14:59tbodt has quit [Ping timeout: 480 seconds]
14:59rcombs has quit [Ping timeout: 480 seconds]
15:00Lightsword has quit [Ping timeout: 480 seconds]
15:00jabashque has quit [Ping timeout: 480 seconds]
15:00tpw_rulesmarcan: i tried keep_bootcon, but i'm not sure that's the problem and nothing really cahnged. i think something goes wrong when linux tries to take over the DART/iommu. i'm using extlinux boot, but maybe that's not really working now? booting the kernel through grub loaded by efi seems to work though
15:00tardyp has quit [Ping timeout: 480 seconds]
15:00tardyp_ is now known as tardyp
15:01Vaughn has quit [Ping timeout: 480 seconds]
15:01Vaughn_ is now known as Vaughn
15:01aeroraptor has quit [Ping timeout: 480 seconds]
15:01aeroraptor_ is now known as aeroraptor
15:01sjg1 has quit [Ping timeout: 480 seconds]
15:01sjg1_ is now known as sjg1
15:01philpax has quit [Ping timeout: 480 seconds]
15:01tertu2 has quit [Ping timeout: 480 seconds]
15:01_jannau_ has quit [Ping timeout: 480 seconds]
15:01yuyichao has quit [Ping timeout: 480 seconds]
15:02gruetzkopf has quit [Ping timeout: 480 seconds]
15:02_jannau_ has joined #asahi
15:07svendoes m1n1 remove the first dwc3/darts these days if you boot it in the HV?
15:07svenotherwise things will go very wrong when linux starts using those
15:07j`eyyes 94a73a404c2185649a1940db44c87052ab8a3e54
15:07sventpw_rules: ^-- if you try to run linux in the HV
15:07j`eyunless I mis understood
15:08svenah. then maybe check if your m1n1 already has that commit ;)
15:10tpw_rulesi've tried booting it without the hypervisor too. i'm using u-boot to try to load the kernel via an extlinux.conf. it loads, then prints "Starting kernel..." on the u-boot console on my HDMI screen, then nothing else happens. if i run it in the HV, then the same stuff happens on the screen but this is all i get over /dev/ttyACM1: https://pastebin.com/z0Dc09EM . it never seems to progress further as the network never
15:12sven382f00000 is the DART that should be used by the HV, isn't it?
15:12_jannau_does the u-boot mem layout script_addr/ramdisk_adr? script_addr is required for extlinux boot
15:13tpw_rulesi set those values to something which seemed to work
15:13rcombs has joined #asahi
15:15_jannau_tpw_rules: which usb-c port do you use on the mac mini?
15:15tpw_rulesthe one apple labels as the DFU port
15:17_jannau_the one closest to the power button? then the dart at @382f00000 should not be there
15:18tpw_rulesif i download the kernel over m1n1, then it boots fine, and that DART is still there
15:19_jannau_how old is the m1n1 on disk? do you chainload a current one before run_guest.py
15:19tpw_rulesit's yesterday's master
15:20tpw_rulesgoing through u-boot also works if i have u-boot load grub with efi, then have grub start the kernel
15:20marcanare you passing in a device tree at some point post-m1n1?
15:20_jannau_it's expected to be there for the bare metal boot. It's a problem for the HV as it is the same USB port the HV uses
15:20marcanif you're somehow overriding the device tree that m1n1/the HV cooks up with a fresh one, that won't work
15:22tpw_rulesok yeah, u-boot is loading one
15:23tpw_rulesbut this doesn't work even without the HV. does that also need a custom device tree? does the linux.py script appropriately massage the device tree i pass it?
15:23_jannau_it must not then running under the hypervisor
15:25jkm has joined #asahi
15:26marcantpw_rules: linux.py does
15:26tpw_ruleswell perhaps i have two problems. if i simply chain u-boot instead of running it under the hypervisor, it still doesn't boot and i don't get any console output on the video screen. but i don't have any compatible usb-serial hardware to get a serial console, so maybe it is failing at a different point.
15:26marcanit would under the hypervisor too, if you do that (e.g. run it over vUART, though most people wouldn't do that)
15:26marcanthe hypervisor has a virtual UART
15:26marcanopen the second ttyACM device
15:27matthewayers[m]Would somebody be able to spend some time with me making sure that I have everything set up to contribute to the project? I would very much like to help out over the next month or so as I am out of classes but I am not quite sure where to start even after reading through the documentation. Any help would be appreciated. Feel free to DM me if you are interested and we can hopefully set something up.
15:27tpw_rulesyes. if i do that then i lose connection when the kernel sets up the DART for that because it conflicts with m1n1 and it never appears to boot further
15:27marcanyou need to stop overriding the device tree
15:27marcanthat's completely unsupported; m1n1 is the source of truth there, it's not just about hypervisor stuff
15:28marcanwith the HV you should be loading a m1n1 + devicetree + u-boot payload, where m1n1 takes care of the DT munging
15:28marcanand no DTs anywhere else after that
15:29tpw_rulesokay. so loading a device tree is expected to break things even without the HV being in the picture
15:29marcanbasically, device trees must go through the m1n1 kboot.c code (which is called by both the embedded payload runner and linux.py)
15:29marcanit might not break things very badly (yet) but it's still a terrible idea :-)
15:29tpw_rulesalright, i'll fix that
15:29marcanI actually wonder what u-boot does about the framebuffer? I guess it transplants /chosen at least... but yeah, there's more than that
15:30tpw_rulesi think whatever it does is wrong because i never get one from the kernel... but being able to boot it under the HV is a step towards rectifying that
15:30marcanthen it might not even do that
15:30marcanI sure hope it transplants the memory range at least... if it doesn't then you're lucky it works at all
15:31tpw_rulesby the way, is there any opinion about publishing some sort of "how to install linux on your m1" guide and precompiled materials? i don't want to unnecessarily increase your support burden
15:31marcanI won't stop you, but I do want to work on making that less painful myself in the very near future...
15:32marcanthough at least if you're telling people how to set up u-boot + grub, that's a lot more useful than people burning kernels into m1n1 with kmutil :p
15:32yuyichao has joined #asahi
15:32tpw_rulesok. i don't intend to really try to publicize it but i don't want to keep it to myself. it seems nobody has really put all the pieces in one coherent place yet
15:33marcanyeah, some docs to point people to are helpful
15:33marcan(even for myself, once I get around to starting to bundle u-boot with the installer)
15:33marcanI just hope it doesn't end up on Hacker News prematurely :-)
15:33tpw_rulesthank you for all your hard work too, and all the other contributors.
15:33tpw_rulesyeah exactly
15:34tpw_rulesthat reminds me, would pointing people to https://mrcn.st/alxsh be a problem
15:35marcanI just did on HN a few minutes ago; I'm reluctant to put it in any high-visibility doc of ours just *yet* but I certainly want people who are going to try to run this to use it
15:35marcan(in HN it was under a disclaimer that this is for kernel devs :p)
15:35tpw_rulesperfect, thank you.
15:35marcanFWIW the real URL will be alx.sh once this is properly published :)
15:36tpw_rulesalso by the way, i somehow confused it the first time i used it and it told me to start step 2 from /Volumes/''/step2.sh
15:36marcanyeah, I wonder what happened there...
15:37_jannau_matthewayers[m]: I would start with compiling m1n1 and the linux kernel and then start with installing m1n1
15:37miniI had that once, but the other time it Did /Volumes/Linux/step2.sh like I expected
15:37_jannau_matthewayers[m]: I
15:38_jannau_matthewayers[m]: feel free to ask questions here if you run in to problems. I think that's more efficient than a 1 on 1
15:38marcanprint(f"/Volumes/{shlex.quote(self.part.label)}/step2.sh")
15:38marcanprint(f"Installing stub macOS into {self.part.name} ({self.part.label})")
15:38minibut my install approach was: build m1n1, cross-compile a kernel, get yourself a rootfs, stick the rootfs on usb, use the install script to get a version of m1n1 running, boot linux under the hypervisor (useful for debugging, as you get easy usb serial outputs), copy the rootfs over, and then boom, working nicely :)
15:38marcantpw_rules: do you remember if that message had the right thing in the parentheses?
15:38c10l8Is it safe to YOLO that script on my M1 Air? :D
15:39minithe hypervisor is incredibly helpful for getting up and running :)
15:39tpw_rulesmarcan: i don't, sorry. the script ultimately ended up in /Volumes/Linux\ 1/step2.sh and executed without problems once i found it
15:40marcanyeah, if you have multiple with the same name it gets confusing
15:40marcanbut I didn't expect it to outright say ''
15:40marcanwonder if it's a diskutil issue...
15:40tpw_rulesi'm not 100% sure why it was Linux 1 and not Linux. i created a container called Linux in disk utility before starting
15:41marcanthe mountpoint gets a number appended if there is another one with the same name already
15:41yuyichao_ has joined #asahi
15:41marcanthat's not the volume name, just the mountpoint
15:41marcanalso, I think I haven't tested existing-container mode in a long time, maybe that's broken!
15:41marcanI should test it again
15:42tpw_rulesit didn't let me do anything until i created the container. i guess it's easier to create just a blank space with the command line diskutil, but disk utility itself seemed to automatically format it
15:42marcanyes, blank space is easiest, but you need the commandline diskutil for that
15:42marcanthe GUI diskutil is... limited and broken in interesting ways
15:42tpw_rulesoh yes. i found my own bug in it
15:43miniI did it last night using an existing container - I resized down to a 40G macOS, and created a 5GB APFS called "Linux", and the rest as a FAT32 for later formatting as ext4
15:43miniand I did get the right name once, but the wrong name once too, and I'm not quite sure what was different
15:43mini(once it was '', once it was 'Linux')
15:43tpw_rulesif you create a FAT partition with lower case characters in the name, it fails to format it and gives it the wrong name
15:44marcanI get the feeling I need to add a logging framework (not log4j :p) to the installer and have it copy out its log to the target Preboot partition or so, for post-facto debugging
15:45tpw_rulesso just to be sure, changing the resolution on the mini's hdmi port from linux is not supported yet?
15:45marcanhaving extremely verbose debug logs behind the scenes would be very helpful (and also make it easier for me to trim down the output)
15:45tpw_rulesthat reminds me, you were saying it was scary to have access to the SPI NOR flash from linux, but have now added it to the device trees. did you find some reason to touch it?
15:45yuyichao has quit [Ping timeout: 480 seconds]
15:45marcantpw_rules: you need the DCP driver, but that's limited to 11.4 right now; it's on my list of things to look at and forward-port to 12.0...
15:45marcanbut then again if you have 12.0 HDMI won't work at all right now without DCP :D
15:46tpw_ruleshow do i get it? i think i installed with 11.4 my second time.
15:46marcantpw_rules: well, I'm also not advertising this to end users yet, and also I hear you can't actually brick it by wiping NOR
15:46marcansupposedly the restore process actually phones home to apple to download the calibration/etc info
15:46marcanI should actually test that though :-)
15:46tpw_rules"supposedly"? :)
15:46marcanI have a brand new Mini here... maybe it should be sacrificed to science...
15:47tpw_rulesis the dcp driver in the linux-asahi branch? or some other one
15:47svenyou already wanted to sacrifice it once and it didn't happen!
15:47marcanbut yeah, tbh I just added it to test the SPI driver, but I might disable it by default
15:47marcansven: every time I try to sacrifice it I come up with some way to achieve the same thing through software!
15:47marcantpw_rules: it is not
15:47marcanI think alyssa just tried to rebase it recently?
15:48svenit'll also need proper locked DART support
15:48tpw_rulesok, i will have to try to track that down then because my display barely works and it's a pain
15:48svenand be ported over from the DMA api to the raw iommu api
15:48marcanhow was I supposed to know that was going to work that well :D
15:49svenyou can overwrite the NOR from software, can't you? :-P
15:50miniis HDMI display compatibility a bit wonky, even with 11.4?
15:50tpw_rulesthat's my experience
15:50miniI found the apple stuff even only brings up my display successfully about 50% of the time
15:50marcan12.0 messed with DCP a lot, maybe it improved?
15:50tpw_rulesi will say it's significantly worse than in macos itself
15:51marcanoh you mean the iBoot bring-up?
15:51marcanthat's not too surprising
15:51miniyeah, to the point that I often don't even have any video for the boot options picker
15:52mini(but if I do it blindly, it *does* then boot into 1TR okay)
15:56yuyichao_ has quit [Quit: Konversation terminated!]
15:56yuyichao_ has joined #asahi
15:57jkmHello all, is Linux already usable on Mac Mini M1?
15:58jkmOr Linux image that is ready to install on Mac Mini M1?
15:58jkmOr is it still WIP?
15:59j`eyjkm: usuable to what level?
15:59matthewayers[m]jannau: Thanks!
16:00j`eythere's no simple install-everything script yet
16:00jkmj`ey: By usable I mean working DE (eg. GNOME/KDE) and HDMI output to external monitor.
16:00j`eyjkm: that works, no GPU accel thouggh
16:01Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:11tpw_rulesmarcan: so the only way for the user to update their device tree will be to use kmutil? can u-boot be taught to do the same munging m1n1 does, or does it not have enough information?
16:11marcantpw_rules: correct; no, u-boot does not have access to the ADT and cannot be taught to do what m1n1 does
16:12marcaneventually there will be an "update my m1n1" option in the installer, so you can just do the same curl and it'll run kmutil for you
16:13yuyichao has joined #asahi
16:13tpw_rulesso i should use kmutil to install m1n1 + my kernel's device tree + u-boot, have u-boot pass the kernel the device tree it's been given by m1n1, and start the kernel?
16:14marcandevice trees are not (in principle) tied to kernels, they are just maintained alongside the kernel
16:14tpw_rulesok, i had been using u-boot's device tree instead of my kernel's.
16:14marcanah, well, that's a different thing, talk to kettenis
16:14marcanthere are some differences that should eventually disappear
16:14marcanISTR we need m1n1 to add some u-boot specific properties for the UART and its PMGR nodes
16:15marcanbut yes, I think right now you need a couple changes for u-boot on top of the kernel device tree
16:15tpw_rulesso the u-boot one is a superset rather than a subset? i guess it's easy enough to diff, but i'll have to double check later
16:16marcanwell, it's probably both right now due to missing stuff
16:16marcanbut it *should* be a superset ultimately
16:20yuyichao_ has quit [Ping timeout: 480 seconds]
16:26minihm, interestingly if I use a different HDMI monitor it works far more reliably
16:26miniI guess the iboot display bringup stuff is a little rough
16:27marcansounds like another reason to put my own attempt at that in m1n1...
16:27marcangiven apple took it out entirely in 12.0.1 :/
16:28minion my lg 4k (which I was using with this mac mini when it was my daily driver...) it's pretty much flawless. on a spare dell 24" it's very broken
16:28marcanI've never really had it go wrong myself, but yeah...
16:28tpw_rulesmy choices are doesn't work at all and works until the machine reboots
16:29minitpw_rules: that's what I was seeing with the dell u2413 I was using. if you have a different monitor it's worth a shot
16:33miniI wonder if it works well with those cheap hdmi -> usb2 capture devices
16:33minithe UVC ones that are <20 USD/EUR/GBP
16:35somkls^ has quit [Remote host closed the connection]
16:41Dcow has joined #asahi
16:47kgarrington has joined #asahi
16:47kgarringtonIs the on-die ram in Apple Silicon ECC? Does that term even mean anything when there are no slots?
16:49kgarrington has quit [Remote host closed the connection]
16:50marcanI briefly thought it was but I think it isn't; in fact I think ECC is impossible with 16-bit LPDDR channels :(
16:51marcan(or, well, not cost effective anyway)
16:51marcanit's not on-die, it's on package, fwiw
16:52marcanmini: I use it with a cheap usb3 one and it works
16:52marcan(the ~$30-40 ones)
16:53miniexcellent, there's one on my desk... somewhere...
16:53miniI'll try that
16:54miniis it actually USB3 or does it just have a blue bit of plastic? I know some of them were doing that
16:54jn(i've seen rather wasteful ECC with 8 bit data + 5 bit polinomial + 3 bits wasted, but that's besides the point for this discussion)
16:54mini(in fact, the one I've just found on my desk is USB2, but has a blue bit of plastic in the connector. no USB3 pins!)
16:59riker77 has quit [Quit: Quitting IRC - gone for good...]
17:12riker77 has joined #asahi
17:14riker77 has quit []
17:15jkm has quit []
17:17kgarrington has joined #asahi
17:18kgarrington has quit [Remote host closed the connection]
17:20tpw_rules has quit [Quit: Textual IRC Client: www.textualapp.com]
17:24kgarrington has joined #asahi
17:24kgarrington has quit [Remote host closed the connection]
17:25kgarrington has joined #asahi
17:25tdmm has joined #asahi
17:26kgarrington has quit [Remote host closed the connection]
17:27riker77 has joined #asahi
17:46Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:49Dcow has joined #asahi
17:51tdmm has quit [Remote host closed the connection]
17:51tdmm has joined #asahi
17:57Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:18yamii has joined #asahi
18:20Dcow has joined #asahi
18:33Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:39Dcow has joined #asahi
18:40Dcow has quit []
18:41somkls^ has joined #asahi
18:49lendi[m] has joined #asahi
18:54c10l8 has quit [Remote host closed the connection]
18:54c10l8 has joined #asahi
18:54c10l8 has quit [Remote host closed the connection]
18:54c10l8 has joined #asahi
18:54c10l8 has quit [Remote host closed the connection]
18:54c10l8 has joined #asahi
18:54c10l8 has quit [Remote host closed the connection]
18:54c10l8 has joined #asahi
18:54c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55lendi[m]Soo... How useable is Linux on m1? I need a laptop for school, but I don't wanna get a x86 based laptop since the battery is so much better on arm.
18:55c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55c10l8 has quit [Remote host closed the connection]
18:55c10l8 has joined #asahi
18:55c10l8 has quit [Remote host closed the connection]
18:56c10l8 has joined #asahi
18:56c10l8 has quit [Remote host closed the connection]
18:56c10l8 has joined #asahi
18:56c10l8 has quit [Remote host closed the connection]
18:56c10l8 has joined #asahi
18:56c10l8 has quit [Remote host closed the connection]
18:56c10l8 has joined #asahi
18:56c10l8 has quit [Remote host closed the connection]
18:56mpslendi[m]: it is not yet ready for casual users, more for developers and reverse enginers, and for those who want to play with it
18:57mpsthough some people uses it
18:58matthewayers[m]lendi: I am a student right now and I've resorted to using a Docker container for anything Linux-related until this project is mature enough to do a bare metal install
18:58matthewayers[m]That being said, I am going to set my computer up to contribute to the development of it over winter break
18:59mpsthere are cheap (used_ arm64 chromebooks which can be used quite fine with linux (I use them for more than 5 years)
18:59mpss/(used_/used/
19:00lendi[m]Okey, thanks! I'll look into it! Do you have any recommendations?
19:03mpscurrently I use old acer R13 chromebook with renewed battery which keeps it on battery around 12 hours, but it doesn't have GPU driver for linux
19:03Dcow has joined #asahi
19:04matthewayers[m]lendi: If you are looking at using Linux on a Mac with Intel but don't want to deal with the T2 chip, there are probably some used 2015 MacBook Pro models floating around on Ebay. If you prefer something newer but still want Linux, there are companies that will ship laptops with Linux pre-installed, or you could do what mps did and use an old Chromebook.
19:04mpsalso my daughter use samsung chromebook (rk3399, gru-kevin) which have GPU driver
19:06Dcow has quit []
19:06mpsalso I have old i3 intel macbook (2010 year) which still works fine with linux, but battery is not so good
19:07lendi[m]matthewayers[m]: It's mainly the arm chip im after because of the battery. And also, where I live we don't really have a good way of buying used, sadly
19:09lendi[m]But hey, maybe the stock os is enough for now? I never really used a Mac before, but I know that it's based of UNIX
19:10mpslendi[m]: I run linux in qemu on macos about for about month, works fine but plugging perifherals (usb) is cumbersome
19:11mpsso not much usable for daily use
19:12lendi[m]Yeah, but it would be enough for application testing ig...
19:12mpsyes, I think
19:13lendi[m]Otherwise I'll have to just bring my old shitty Linux laptop, but that works too ig :p
19:15Dcow has joined #asahi
19:17Dcow has quit []
19:51___nick___ has joined #asahi
19:51c10l8 has joined #asahi
19:51c10l8 has quit [Remote host closed the connection]
19:51___nick___ has quit []
19:51c10l8 has joined #asahi
19:51c10l8 has quit [Remote host closed the connection]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Remote host closed the connection]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Read error: Connection reset by peer]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Remote host closed the connection]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Remote host closed the connection]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Remote host closed the connection]
19:52c10l8 has joined #asahi
19:52c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53___nick___ has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:53c10l8 has joined #asahi
19:53c10l8 has quit [Remote host closed the connection]
19:54c10l8 has joined #asahi
19:54c10l8 has quit [Remote host closed the connection]
19:54matthewayers[m]lendi: I use macOS as my daily driver right now and have little to no issues. It works very well for a lot of college-related tasks and there are plenty of ways to get around software incompatibilities. If you want more of a linux-like experience, definitely download Homebrew (https://brew.sh)
20:00c10l8 has joined #asahi
20:04lendi[m]Oh, cool! I'll look into the stuff more.
20:04lendi[m]Homebrew looks really interesting
20:23___nick___ has quit [Ping timeout: 480 seconds]
20:27clover[m]macOS is a killer laptop OS, using it on desktop multimonitor setups is still very awkward to me
20:27clover[m]i got a magic trackpad which helps a good deal
20:58Dcow has joined #asahi
21:20andreafeletto has joined #asahi
21:33Dcow has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:37Dcow has joined #asahi
21:40ey3ball[m] has joined #asahi
21:40Dcow has quit []
21:52ey3ball[m]Hi everyone ! I'm trying to get up and running with Asahi's dev setup but I'm currently hitting a wall while attempting to install m1n1 into my stub partition
21:52ey3ball[m]I'm getting the following error from kmutil : Error Domain=KMErrorDomain Code=71 "Fileset Error: Invalid Mach-O boot properties" UserInfo={NSLocalizedDescription=Fileset Error: Invalid Mach-O boot properties}
21:53ey3ball[m]does this ring any bell ?
22:35Dcow has joined #asahi
22:38Dcow has quit []
23:15yuyichao has quit [Quit: Konversation terminated!]
23:15yuyichao has joined #asahi
…