#
…

2022-07-07

00:05millenialhacker has joined #asahi
00:13millenialhacker has quit [Ping timeout: 480 seconds]
00:29roote has joined #asahi
00:31roote has quit []
00:36quarkyalice has joined #asahi
00:41nicolas17 has joined #asahi
01:23Zaprit has quit [Ping timeout: 480 seconds]
01:27millenialhacker has joined #asahi
01:35millenialhacker has quit [Ping timeout: 480 seconds]
02:07PhilippvK has joined #asahi
02:10phiologe has quit [Ping timeout: 480 seconds]
02:49millenialhacker has joined #asahi
02:57millenialhacker has quit [Ping timeout: 480 seconds]
03:34marvin24_ has joined #asahi
03:38marvin24 has quit [Ping timeout: 480 seconds]
03:44kprasadvnsi[m]anybody using VSCode on asahi plasma desktop. it crashes for me.
03:45millenialhacker has joined #asahi
03:50tpw_rulesit has to update to chromium 102 or so
03:50tpw_rulesdue to the hardware's 16k page size
03:53Lucy[m]Shouldn't it be possible to force it to use electron 19? Well, not for the proprietary binaries obviously
03:53millenialhacker has quit [Ping timeout: 480 seconds]
04:00kov has quit [Quit: Coyote finally caught me]
04:02Lucy[m]Yeah, assuming you build it from source, that looks relatively easy to change
04:16SilverHammerMax has joined #asahi
04:16SilverHammerMax has left #asahi [#asahi]
04:26marcanthe change was backported to electron 18 already
04:27marcan"The issue has been addressed in vscode insiders and the fix will also be available in 1.69.0 stable release next week"
04:27marcanwould be nice if someone can confirm that insiders works :)
04:29Ry_Darcy has joined #asahi
05:02Lucy[m]Cool, good to know.
05:10millenialhacker has joined #asahi
05:18millenialhacker has quit [Ping timeout: 480 seconds]
05:22psykosecant confirm if it works on m1 or not but forcing electron 19 is like a 5 line patch and that works :)
05:23nicolas17 has quit [Ping timeout: 480 seconds]
05:28quarkyalice has quit [Ping timeout: 480 seconds]
05:36hell__ has joined #asahi
05:53guillaume_g has joined #asahi
06:17millenialhacker has joined #asahi
06:23the_lanetly_052___ has joined #asahi
06:27millenialhacker has quit [Ping timeout: 480 seconds]
06:28MajorBiscuit has joined #asahi
06:39mrCyborg has joined #asahi
06:39keegans has joined #asahi
06:39jleightcap_ has quit [Read error: Connection reset by peer]
06:39WhyNotHugo_ has quit [Write error: connection closed]
06:39WhyNotHugo has joined #asahi
06:39jleightcap has joined #asahi
06:48zanfix has joined #asahi
07:03millenialhacker has joined #asahi
07:04MajorBiscuit has quit [Ping timeout: 480 seconds]
07:11millenialhacker has quit [Ping timeout: 480 seconds]
07:28the_lanetly_052___ has quit [Ping timeout: 480 seconds]
07:30Zaprit has joined #asahi
07:40bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
07:41guan has quit [Read error: Connection reset by peer]
07:41enomem has quit [Read error: Connection reset by peer]
07:41snek has quit [Read error: Connection reset by peer]
07:41guan has joined #asahi
07:41enomem has joined #asahi
07:41stblassitude has quit [Write error: connection closed]
07:41stblassitude has joined #asahi
07:42esden has quit [Read error: No route to host]
07:42jabashque has quit [Read error: Connection reset by peer]
07:42esden has joined #asahi
07:42jabashque has joined #asahi
07:42jkkm has quit [Read error: Connection reset by peer]
07:42Manouchehri has quit [Write error: connection closed]
07:42Vaughn has quit [Read error: Connection reset by peer]
07:42Vaughn has joined #asahi
07:42taowa_ has quit [Read error: No route to host]
07:42eichin_ has quit [Read error: Connection reset by peer]
07:42Manouchehri has joined #asahi
07:42austriancoder has quit [Remote host closed the connection]
07:42snek has joined #asahi
07:42eichin_ has joined #asahi
07:42Illya has joined #asahi
07:42austriancoder has joined #asahi
07:43cptcobalt has joined #asahi
07:43taowa_ has joined #asahi
07:43kendfinger has joined #asahi
07:43arnd_ has joined #asahi
07:43jkkm has joined #asahi
07:43mmarchini__ has joined #asahi
07:43Gaelan has joined #asahi
07:44Ry_Darcy has quit [Remote host closed the connection]
08:12MajorBiscuit has joined #asahi
08:14Zaprit has quit [Ping timeout: 480 seconds]
08:48millenialhacker has joined #asahi
08:59millenialhacker has quit [Ping timeout: 480 seconds]
09:16nsklaus has quit [Quit: Textual IRC Client: www.textualapp.com]
09:23nsklaus has joined #asahi
09:47IcaroDextris[m]Anyone knows if there are any plans about matlab on Linux arm?
09:48j`eyrun it under an emulator, unless they release an arm version
10:14Zaprit has joined #asahi
10:37kov has joined #asahi
11:19Zaprit has quit [Quit: Zaprit]
11:40eroux_ has joined #asahi
11:45eroux has quit [Ping timeout: 480 seconds]
11:48MajorBiscuit has quit [Quit: WeeChat 3.5]
11:51MajorBiscuit has joined #asahi
12:23zanfix has quit [Quit: Konversation terminated!]
12:24millenialhacker has joined #asahi
12:27zanfix has joined #asahi
12:28IcaroDextris[m]<j`ey> "run it under an emulator, unless..." <- Do you think is doable under box64 or similar?
12:32millenialhacker has quit [Ping timeout: 480 seconds]
12:33j`eyIcaroDextris[m]: dunno, worth a try!
12:37IcaroDextris[m]Sure, now I can’t, that’s why the question, thanks 😊
12:38mpsmixi: you told that you boot same rootFS in qemu and native. any hint how you solved it? with u-boot or grub?
12:41mpsor you pass ESP and root partition to qemu
12:53c10l has quit [Quit: Ping timeout (120 seconds)]
12:54c10l has joined #asahi
13:04Raqbit9 has joined #asahi
13:05sven has joined #asahi
13:05milek7 has quit [Remote host closed the connection]
13:06milek7 has joined #asahi
13:07deflax has joined #asahi
13:07deflax has quit []
13:07deflax has joined #asahi
13:09Raqbit has quit [Ping timeout: 480 seconds]
13:09Raqbit9 is now known as Raqbit
13:11Raqbit has quit [Quit: The Lounge - https://thelounge.chat]
13:29miximps: I created my own esp + kernel partition with and efi bootloader and qemu efi support as a qcow2-file on macos, and passed that and the root partition as separate hard drives to qemu; but I think it would have been a lot easier to just pass the root partition and have qemu load the kernel and maybe initramfs you want to boot directly
13:31mixithe qemu efi support was of course not part of the qcow2-file, I just rewrote that sentence wrongly when trying to add extra information to it
13:32andreas has joined #asahi
13:32mixithe qemu efi support was referring to also passing -bios QEMU_EFI.fd with an appropriate QEMU_EFI.fd stolen from some distribution package
13:32mpsmixi: aha, ok. I thought about same. just wanted to know which option you used. thank you
13:33andreas has quit []
13:33mpsyes, I sued QEMU_EFI.fd earlier when run daily linux in qemu on m1
13:35mpsand I can confirm that passing partition to qemu works on macos
13:42bisko has joined #asahi
13:45bisko has quit []
13:46bisko has joined #asahi
13:52andreas has joined #asahi
13:52andreas has quit []
13:53bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:53bisko has joined #asahi
13:54andreas has joined #asahi
13:55andreas has quit []
14:02Ry_Darcy has joined #asahi
14:19Ry_Darcy has quit [Remote host closed the connection]
14:49bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:08Gaspare has joined #asahi
15:40zzywysm has joined #asahi
15:44zanfix has quit [Quit: Konversation terminated!]
16:00MajorBiscuit has quit [Ping timeout: 480 seconds]
16:03Gaspare has quit [Quit: Gaspare]
16:21zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:28trouter- has quit [Quit: ZNC 1.8.2 - https://znc.in]
16:30zzywysm has joined #asahi
16:30trouter has joined #asahi
16:52Zaprit has joined #asahi
17:05janrinze has joined #asahi
17:07janrinzehi all.. anyone here who has been compiling their own kernels for the mac mini? (probably yes..) I have some issues getting newer kernels to boot properly. it seems they can't find the root disk. UUID is set but the kernel does not see that partition..
17:10Gaspare has joined #asahi
17:13mpsjanrinze: kernel doesn't recognize UUID
17:13AdryzzOLEDEdition[m]1you mean latest linux-asahi?
17:13mpsyou have to use PARTUUID
17:16janrinzemps: PARTUUID, sorry but what i mean is that the kernel I built a while back works with the same cmdline..
17:17janrinzeBOOT_IMAGE=/boot/vmlinuz-5.18.0-asahi-jrp4k-00184-g6296bb4b5ae5 root=UUID=581a80f0-19e1-43ba-a82c-fcedd5ea1ca8 ro quiet
17:17mpsjanrinze: do you correct initramfs
17:17janrinzethat's the one that my 'old' current kernel gets from grub.
17:18janrinzemps: if i bake in the modules required the initramfs shouldn't matter much, right?
17:18mpsto use UUID for root initramfs must contain proper tools
17:18janrinzeunless the DTBs are not found.. that might cause problems.
17:19mpsjanrinze: DTB is loaded by m1n1
17:19janrinzemps: I boot kernels on many different machines here without initramfs.. so probably not a requirement.
17:19mpsjanrinze: then use PARTUUID instead of UUID
17:20mpsI do that
17:20janrinzeDTB in m1n1 is for u-boot, i thought.. will the kernel not use its own DTBs?
17:20janrinzemps: the kernel boots.. but the newer kernel that i compiled just now doesn't..
17:20mpsjanrinze: DTB is general, whoever loads it it is ok
17:21janrinzemps: DTB in m1n1 does not get updated after a kernel build.. right?
17:21ElvishJerricco[m]janrinze: You're not using any initramfs at all?
17:22mpsjanrinze: 5.18 kernels have DTB in default m1n1
17:22janrinzeElvishJerricco[m]: generally not.. If the kernel can start and has sufficient modules to mout root fs then all should just work..
17:22janrinzeoops .. mount
17:23ElvishJerricco[m]The kernel will use whatever DTB is provided by the previous stage. It doesn't load its own, I'm pretty sure. But u-boot can be configured to load a DTB from disk and provide that to the kernel. Dunno if the asahi installer sets it up that way or if it just passes the one it gets from m1n1 onward
17:24janrinzeOkay, I can add the DTBs in the kernel. I'm used to different ARM platforms.
17:24mpsElvishJerricco[m]: DTB must be chained to m1n1, even u-boot doesn't load it
17:24ElvishJerricco[m]Ah so m1n1 does some essential fixups?
17:24ElvishJerricco[m]on the FDT that is?
17:24mpsElvishJerricco[m]: yes
17:25janrinzelet me reboot for a second and see if the nwely built kernel can find the root partition now.
17:25ElvishJerricco[m]good to know; means I can't have per-kernel DTBs with NixOS :(
17:25mpsElvishJerricco[m]: for now yes, but maybe in future
17:26mpsjanrinze: 'BOOT_IMAGE=/boot/vmlinuz-5.18.0-rc5-2-asahi root=PARTUUID=b0a3.........' is my line in grub.cfg
17:26mpsI do not use initramfs
17:26ElvishJerricco[m]shouldn't be a big deal as long as the asahi kernel remains backward compatible with older DTBs; though I understand that's only assured for patches that make it to mainline
17:27janrinzeElvishJerricco[m]: during kernel config you should be able to set the flag to add the DTBs to the kernel image..
17:27ElvishJerricco[m]oh really? TIL. That could be useful on some other platforms.
17:27janrinze has quit [Quit: Leaving.]
17:29mpsElvishJerricco[m]: you can add newer DTBs to second stage m1n1+u-boot easily
17:29janrinze has joined #asahi
17:29janrinzeback.. now on Linux M1DebianSid 5.18.0-asahi-jrp-git-new-dirty #3 SMP Thu Jul 7 18:44:44 CEST 2022 aarch64 GNU/Linux
17:30janrinzeat least rebooting is faaaast
17:32janrinzeWhy i wanted to get a newer kerenl working is because i did some benchmark test (Geekbench 5) and it showed that it only runs at a little over 56% of the speed of OSX.
17:32janrinzes/kerenl/kernel/g
17:38nicolas17 has joined #asahi
17:41janrinzethe mac mini on OSX does almost 1.65x this score for single score and around 1.42x on multi core score.. So i was thinking that since i have an older kernel it might not run at the full 3.2 GHz. Unfortunately no nodes in /sys that give me a clue on cpu scaling and such.
17:42nicolas17I assume "running at the full 3.2GHz" and "exposing scaling info in /sys" needs the same kind of work :P
17:43janrinzeno info at /sys/devices/system/cpu/cpu4/cpufreq
17:44janrinzenicolas17: at some point the cpu frequency gets set.. either at m1n1, u-boot or kernel..
17:49janrinzehttps://browser.geekbench.com/v5/cpu/compare/14185972?baseline=15880140 for example shows that my system is running much slower than that other asahi linux system...
17:50mpscat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_cur_freq
17:54janrinze2188000 if i'm lucky but mostly 1190000.. and that's while i am running the benchmark..
17:56mpsecho performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
17:56janrinze/sys/devices/system/cpu/cpufreq/policy0/cpuinfo_max_freq is 2265600
17:57nicolas17mps: how do I make scaling_governor changes persist on reboot?
17:57janrinzethere is a file for that in /etc ..
17:57mpsjanrinze: I've 3.2GHz earlier but now I have 2988000 because I tweaked DTS
17:58janrinzemps: exactly my point about the DTBs..
17:58mpsnicolas17: I use boot script to add different tweaks
17:58nicolas17afaik sysctl.conf can set /proc/sys parameters on boot but I don't think there's something for /sys
17:59janrinzemps: which DTS holds the frequency?
17:59mpsI use chadmeds linux-asahi-eas DT now
18:00mpsnot sure is that related or schedutil governor
18:00leo60228 has joined #asahi
18:01janrinzemps: where to get that?
18:01nicolas17a boot script with echo blah > /sys/blah is of course an option but I feel there *has* to be a better way :P
18:01mpsI forgot, somewhere on chadmed's github repo
18:02mpsnicolas17: sysctl.conf tweaks /proc options
18:02zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:02nicolas17right, I'm asking if there's an equivalent for /sys
18:03mpsdon't know
18:05tabthetextoutforwimps[m] has joined #asahi
18:07janrinzemps: https://github.com/chadmed/linux but can't find linux-asahi-eas
18:13zzywysm has joined #asahi
18:16janrinzemps: cleary my kernel is not using its own DTBs but the ones provided somewhere else indeed. So I probably need to bake them in the kernel..
18:19mpsjanrinze: what kernel config option enables putting DTBs in kernel
18:21zzywysm has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:24thevar1able has joined #asahi
18:24thevar1able has quit [Remote host closed the connection]
18:24thevar1able has joined #asahi
18:25thevar1able1 has joined #asahi
18:25thevar1a- has joined #asahi
18:25janrinzemps: looks like it's not supported anymore in the kernel.. apparently maintainers were afraid that people would actually use it..
18:26zzywysm has joined #asahi
18:26thevar1a- has quit []
18:26thevar1able has quit []
18:26thevar1able1 has quit []
18:27thevar1able has joined #asahi
18:27steevyou could always use a fit image
18:29janrinzemps: this means when the DTBs are updated we need to update UEFI/m1n1 too.
18:29mpssteev: yes, I use fit on some chromebooks
18:30mpsjanrinze: right
18:30steevif you're doing u-boot->grub, grub also has a "devicetree" option that isn't really exposed, but you can add it in
18:30janrinzewould be nice to have a way of integrating the m1n1 build with the linux kernel build. but it probably will make it harder if the kernel fails to boot and we need to fall back on an older kernel..
18:31mpssteev: yes, I saw 'devicetree' in grub docs but this doesn't work on current grub
18:31steevit should, i've been using it for a few years now, unless current grub is.... not > 2
18:31mpsjanrinze: asahi build scripts already have this I think
18:32steevmps: if you don't mind patching your grub, you can always pull in the ubuntu patches that add it automagically
18:32mpssteev: I'm not sure but this must be in some patches. At least it doesn't work with grub in alpine linux and I didn't investigated further
18:34steevdebian doesn't patch it in, so i'd say its an issue with alpine
18:36mpssteev: I guess so. I tried on riscv board to use grub with devicetree but didn't worked and I used plain u-boot with extelinux.conf which could load DTB fine
18:36steevi've been using it on my lenovo yoga c630 (non-chromebook) which has uefi, and it makes flipping between kernels very easy when there had been significant dt changes while working on getting its support in the kernel
18:36steevyeah, extlinux works fine too
18:37mpsI even used extlinux.conf for long on M1 but switched to grub a month or two ago
18:38janrinzeOn the Nvidia AGX the DTBs are at /boot and it uses extlinux.conf as well
18:41janrinzesteev: so where do i add the device tree in grub?
18:42mrnoda has joined #asahi
18:42janrinzeor how do i add them to UEFI?
18:43steevjanrinze: edit grub config entry and simply add "devicetree /path/to/devicetree.dtb"
18:44steevyou can also add (above it) "echo 'loading dtb file ...'" like the other entries do to show it's loading it
18:44tpw_rulesFTR you can't use that on m1n1
18:44steevthe kernel can't override the dtb passed in from m1n1?
18:44tpw_rulesno, m1n1 has to do various massaging. if you try the kernel won't boot
18:45steevwell that would explain why it isn't working :D
18:45quarkyalice has joined #asahi
18:48tpw_rulesi did write a patch a while ago for u-boot to do this massaging based on m1n1's data but the asahi folks were pretty against it. i agree with them in an ideal world but it would really be a nice capability while things are still in flux
18:49janrinze echo 'Loading Linux 5.18.0-asahi-jrp-git-new-dirty ...'
18:49janrinze linux /boot/vmlinuz-5.18.0-asahi-jrp-git-new-dirty root=UUID=581a80f0-19e1-43ba-a82c-fcedd5ea1ca8 ro quiet
18:49janrinze echo 'Loading initial ramdisk ...'
18:49janrinzebefore or after the ramdisk?
18:49janrinze initrd /boot/initrd.img-5.18.0-asahi-jrp-git-new-dirty
18:50steevjanrinze: i'd normally put it after - but if tpw_rules is correct, it won't boot anyway
18:50tpw_rulesjanrinze: your machine won't boot if you do that
18:50steevi normally just edit the grub config at boot time to do it, just to make sure things work, rather than make them permanent
18:51janrinzesteev: yup.. good idea. btw. most ARM platforms don't use grub. so i have not been fiddling with that for a long time..
18:51steevjanrinze: i know :(
18:52steevmost of them don't really *need* it though, since u-boot is there already
18:52janrinzenow.. where did i leave those dtbs..
18:53tpw_ruleseven if you do not care about nixos, that post is very relevant and it sounds like you would like it
18:55steevtpw_rules: i'm the kali arm guy, so it's very interesting to me what other distros are doing as well
18:55tpw_rulesget on the tow-boot train
18:56steevonce it supports more boards....
18:57steevit supports... 19 boards? i have to support 50+
18:57tpw_rulesdo you have a large pile of them? it's 99% (mainline) u-boot. the nix stuff is quite gnarly if you are unfamiliar but support is almost entirely about just testing it
18:58steevi have over 200 here :D i've been working with arm devices since the early 2000s and have amassed a bit of a collection
18:58tpw_rulesdo you guys commonly use vendor u-boots?
18:58steevon some devices i do, on some i don't
18:58janrinzebrb, will reboot now. (wish me luck ;-) )
18:59___nick___ has joined #asahi
18:59steevi try to move off the vendor stuff as soon as is feasible
18:59janrinze has quit [Remote host closed the connection]
18:59___nick___ has quit []
19:00janrinze has joined #asahi
19:01___nick___ has joined #asahi
19:01janrinzeokay.. that was interesting.. grub says the path is not a regular file.. yes.. duh..
19:02steevah, if grub is on a separate partition, you'd need to either hardcode the (hdX,gptX) to the beginning of the path, or cp the dtb to the partition that has grub on it
19:04tpw_rulesi know bandwidth to contribute is an eternally limited resource but if you have lots of boards which are supported in mainline u-boot and like tow-boot's mission statement it would be great to help out
19:04janrinzesteev: i'll copy the dtbs to the /boot partition.. brb after reboot.
19:04tpw_ruleswould kali be interested in board-agnostic images anyway? that's a pretty application specific distribution right
19:05steevtpw_rules: it would definitely be nice to have board agnostic images to increase maintainer sanity ;) the bigger problem is that every board is a special snowflake and you can't write the bootloader to the same spot and have it work across all of them
19:07janrinze has quit [Quit: Leaving.]
19:07tpw_rulesthat's what tow-boot aims to solve. make each distro's installation be: 1. follow tow-boot's instructions for your board 2. download our iso and run the installer
19:07tpw_rulesi just wasn't sure if kali included lots of board-specific packages and setup or so
19:08pb17[m] has joined #asahi
19:08janrinze has joined #asahi
19:09janrinzeok.. copied the dtbs but grub still says not a regular file.. which i do agree with because it's a directory..
19:10j`eyjanrinze: as they said, dont try to use grub for that
19:12j`eyjanrinze: its not supported to use anything but the DTS that is passed through 1m1n to uboot to the kernel
19:12j`eylol 1m1n, I mean m1n1
19:13janrinzej`ey: but u-boot starts grub, not the kernel..
19:14___nick___ has quit [Ping timeout: 480 seconds]
19:14j`eywell to grub, to the kernel, its passed through grub too
19:15steevjanrinze: you need to put the full dtb not the directory
19:15steevgrub doesn't have the info that u-boot does, so it doesn't know which dtb to use
19:15janrinzesteev: that's what i am thinking as well.. so which dtb for the mac mini?
19:15j`eyjanrinze: it wont work
19:16j`eythe issue is elsewhere
19:20steevtpw_rules: is there a tow boot irc channel because the convo is a bit OT for here :)
19:21tpw_ruleshttps://matrix.to/#/#Tow-Boot:matrix.org is the official thing. don't think it has irc
19:23j`eyjanrinze: which kernel versions are you testing? dont think there was anyway dtb changes recently that would stop it working
19:25guillaume_g has quit []
19:26janrinze/boot/dtbs/linux-image-5.18.0-asahi-jrp-git-new-dirty/apple/t8103-j274.dtb that's the one for mac mini :-)
19:26janrinzej`ey: it works.. but it does not go beyond 2 GHz..
19:28j`eyjanrinze: and it previously did?
19:29jole has quit [Remote host closed the connection]
19:29janrinzej`ey: no .. when i installed linux i ran an older kernel..
19:29j`eywell I dont think cpufreq has changed..
19:30j`ey(well i suppose the changes for m2 could have broken it somehow.. but if it didnt work on an older kernel anyway it wasnt that)
19:31tpw_rulesi think it did once, i forget when
19:31jole has joined #asahi
19:31j`eyjanrinze: max is like 2.9Ghz right now
19:33j`eyjanrinze: thats from may
19:34janrinzeyes.. like i say.. older kernel... Duh..
19:34j`eyjanrinze: how old?
19:34janrinzebrb.. rebooting.
19:34janrinze has quit [Remote host closed the connection]
19:35opticronhave there been any murmurs about the PSCI stuff getting merged in/accepted?
19:37svenI don’t think that stuff is even remotely ready yet
19:40opticronunfortunate :/ it's kind of important for me to be able to sleep the computer for hours at a time and last time I tried with s2idle it ended up very warm in a bag
19:41opticronthough I guess I may have done something wrong
19:43j`eyopticron: s2idle.. didnt that crash the wifi driver?
19:44janrinze has joined #asahi
19:44opticronI don't think s2idle powers down the PCIe bus, so no?
19:45j`eyopticron: it doesnt work yet
19:45janrinzeso the good news is: yes grub dtb loading works.. but the bad news is that X doesn't work. can boot into a console though.
19:48janrinzeso we got running on an efficiency core only.. probably onlu cpu0
19:48opticronyou're only running one core?
19:49janrinzeLOL.. yup
19:49tpw_rulesthat's one of the symptoms of not having the correct dtb. i'm surprised it got that far
19:50janrinzethe thing is if i break m1n1 the sytem definitely won't boot anymore.
19:50tpw_rulesm1n1 passes information on how to start the other CPUs through the device treee
19:50janrinzetpw_rules: that's another option..
19:50j`eytpw_rules: yeah, they seem hell bent on loading it with grub, even though thats explicitly not how youre meant to do it
19:50tpw_rulesi don't think that you could even dump. it changes every boot
19:51janrinzej`ey: i'm actually trying to avoid to replace m1n1
19:52tpw_rulesyou do know you can chainload m1n1 right? that's how you are intended to update the device tree
19:52janrinzetpw_rules: the device tree is what i added with grub
19:52j`eyjanrinze: are you using the asahi distro or?
19:53janrinzenope running debian sid
19:54janrinzebuilding deb files for newer kernels works, installing the deb files properly add them to grub..
19:54j`eyok so you dont have the chainloading setup
19:55janrinzelet's see how to rebuild m1n1
19:55gladiac has quit [Quit: k thx bye]
19:57janrinzecat build/m1n1.bin /path/to/dtbs/*.dtb /path/to/uboot/u-boot-nodtb.bin > /boot/efi/m1n1/boot.bin
19:57janrinzeso not just building m1n1 but u-boot too..
20:08nathanthegr8[m] has joined #asahi
20:11janrinzeok. built m1n1 and u-boot.. now i probably will need to replace /boot/efi/m1n1/boot.bin
20:12janrinzemade backups.. will now check if i can reach the /boot partition from OSX.
20:14janrinzetoo bad grub can't boot OSX..
20:15janrinze has quit [Remote host closed the connection]
20:16svenwhy are you trying to load the dtb from grub?
20:18zzywysmis anyone running the current up-to-date Asahi Linux distro? can you send me the output of the command cat /proc/cmdline
20:20mrnoda has quit [Quit: Page closed]
20:25ElvishJerricco[m]I get the feeling we could potentially load the dtb in later stages if we supported the efi fixup protocol https://github.com/U-Boot-EFI/EFI_DT_FIXUP_PROTOCOL
20:25ElvishJerricco[m]I don't think that proposal is like... official at all, but it does solve the problem I think, and seems like a good idea in general even outside asahi/m1n1
20:27ElvishJerricco[m]Though I guess u-boot would have to do something else to figure out what fixups were made by m1n1 so that it could offer this protocol to the boot loader, so maybe it's just kicking the can
20:32Zaprit has quit [Ping timeout: 480 seconds]
20:39ptudor_ is now known as ptudor
20:42janrinze has joined #asahi
20:43janrinzeok.. good thing is : i can mount the fat32 partition from OSX and yes i broke m1n1.. copied the backup and now back in linux.
20:45janrinzetpw_rules: how do i 'chainload' m1n1.. the one i built crashed and got me in a boot loop
20:49janrinze has quit [Remote host closed the connection]
20:53janrinze has joined #asahi
20:53jluthra has quit [Remote host closed the connection]
20:54jluthra has joined #asahi
20:54janrinzesven: I want to update the dtbs. so either need to add it in a working m1n1 or use grub for that.. however both methods seem to fail. lots of reboots
20:56j`eywell grub is not the right way
20:57Zaprit has joined #asahi
20:58janrinzej`ey: and m1n1 will crash and get me in a boot loop.. so now what?
20:58j`eyhow is m1n1 crashing?
20:59janrinzequick register list and rebooting again
21:00janrinzeso the recipe for creating /boot/efi/m1n1/boot.bin is not quite ok yet
21:02c10l has quit [Ping timeout: 480 seconds]
21:03ElvishJerricco[m]janrinze: And you're configuring/building for stage 2 m1n1, not stage 1, right?
21:06janrinzecat build/m1n1.bin /path/to/dtbs/*.dtb /path/to/uboot/u-boot-nodtb.bin > /boot/efi/m1n1/boot.bin
21:06Gaspare has quit [Quit: Gaspare]
21:06janrinzeand the dtbs from the fresh built kernel from asahi-linux
21:09janrinzehmm.. later-on it says uboot needs to be gzipped
21:11ElvishJerricco[m]janrinze: Hm yea it also says to use DTBs shipped with u-boot, not the kernel. Dunno if those are identical or not
21:11Gaspare has joined #asahi
21:12j`eyjanrinze: https://github.com/AsahiLinux/asahi-scripts/blob/main/update-m1n1 try gzipping, thats what the reference distro does
21:18janrinze has quit [Remote host closed the connection]
21:21janrinze has joined #asahi
21:28j`eyand prettu sure it adds a bunch of the same file names
21:30j`ey(ah no, spi-hid-core.c vs spi-hid-apple-core.c)
21:32Zaprit has quit [Quit: Zaprit]
21:45deepphilosopher846[m] has joined #asahi
21:56janrinze has quit [Remote host closed the connection]
21:59janrinze has joined #asahi
22:03c10l has joined #asahi
22:19Gaspare has quit [Quit: Gaspare]
23:04nsklaus_ has joined #asahi
23:09nsklaus has quit [Ping timeout: 480 seconds]
23:09derzahl has joined #asahi
23:10derzahl has quit [Remote host closed the connection]
23:11derzahl has joined #asahi
23:14derzahlstrange. sound stopped working on my macbook(air). I figured it was just the latest kernel I installed but I went back to a known good kernel and stil no sound
23:15derzahli reinstalled the known-good kernel so that m1n1 would update its dtb (even though my PKGBUILD automatically adds the modified dts file to enable sound). still no go
23:16derzahlanyone else have issues?
23:18j`eycheck dmesg, any errors?
23:21zzywysmhave you tried shutting the system down completely? or have you just been rebooting since you discovered the issue?
23:43nicolas17derzahl: I heard some sound errors go away if you switch the sound device to something else and switch back
23:48ptudor_ has joined #asahi
23:54ptudor has quit [Ping timeout: 480 seconds]
…