#asahi · 2024-01-05 10:10
j`eyand there's PRs with updated packages#asahi · 2024-01-05 10:10
capta1nt0adchadmed: ok, thank you.#asahi · 2024-01-05 10:09
chadmedcapta1nt0ad: not sure when new packages will be built but you can build your own packages if you really need to. the pkgbuilds should be there in the repo#asahi · 2024-01-05 09:41
ketteniskitlith: if the fw_dev_part u-boot env variable isn't set, you must be running a u-boot that doesn't have the required patches#asahi · 2024-01-05 09:29
capta1nt0adSorry if I am seeming a little impatient, that's not my intention at all.#asahi · 2024-01-05 09:24
capta1nt0adI have to find a time to switch to Fedora before I can use the speakers?#asahi · 2024-01-05 09:24
capta1nt0adHello, I messaged here a few weeks ago (December 20th) regarding speaker support on the legacy Arch Linux ARM Asahi distribution (which I am currently unable to reinstall due to time constraints and the amount of packages/configuration I have installed and made.) I noticed that the new version of lsp-plugins was released on the 24th and has been merged into ALARM. Can I expect the speakers to be enabled in ALARM soon, or will #asahi · 2024-01-05 08:19
chadmedspeakersafetyd expects/requires specific kernel level features which do not exist outside of our fork currently, and are kinda tightly bound to ASoC #asahi · 2024-01-05 08:18
chadmedand its not really clear how it's all supposed to mesh together post-2017-ish#asahi · 2024-01-05 08:18
chadmedgotlou: the amount of work required will be quite significant as the intel macs are a weird mix of SOF, HDA and codec drivers#asahi · 2024-01-05 08:10
kidplayer666gotlou: I am not sure, marcan and chamed probably know it a looot better than me#asahi · 2024-01-05 08:09
gotloukidplayer666: I see, what about the macbook air? afaik the m1 version is just an intel mba with no fan and an m1 instead of an intel chip, and a slightly different keyboard#asahi · 2024-01-05 08:00
kidplayer666gotlou: I get a feeling that MacBook with touchbar probably is the easiest to port as they probably reused most stuff. Everything else probably needs proper testing as they changed the chassis if I’m not mistaken#asahi · 2024-01-05 07:55
kidplayer666Hey, I’m trying to install PyQt6, but it is requiring an extremely high amount of RAM, and it is using up all my 8Gb of ram, plus the additional 24GB of swap, and it still crashes my laptop. Is this normal? How can I make it use less RAM?#asahi · 2024-01-05 07:38
gotlouspecifically the last intel macs from 2020, which are the closest machines to the m1 macs#asahi · 2024-01-05 07:37
gotlouhello, I was looking at the great work the asahi team did on speakersafetyd and was wondering how much additional work would be required to get it running on intel macs#asahi · 2024-01-05 05:55
kitlithI think I'm done for the night, but I am somewhat interested in digging deeper at some point. will check logs tomorrow#asahi · 2024-01-05 04:38
tpw_ruleskettenis: are you around?#asahi · 2024-01-05 04:37
tpw_rules(which you COULD set up...)#asahi · 2024-01-05 04:35
tpw_rulesthen i'm at a loss without a debugger#asahi · 2024-01-05 04:34
tpw_rulesah#asahi · 2024-01-05 04:34
tpw_rulesi don't remember the machine IDs but something like https://github.com/AsahiLinux/linux/blob/b5c05cbffb0488c7618106926d522cc3b43d93d5/arch/arm64/boot/dts/apple/t8103.dtsi#L1107#asahi · 2024-01-05 04:34
kitlithAccording to DM compat, apple_nvme is apple,nvme-ans2 compatible#asahi · 2024-01-05 04:32
tpw_rulesdig through the device tree some more i think#asahi · 2024-01-05 04:31
kitlithhm. what's the best way to check that?#asahi · 2024-01-05 04:30
tpw_rulesis the apple,nvme-ans2 check failing somehow?#asahi · 2024-01-05 04:30
tpw_rulesor an empty string rather#asahi · 2024-01-05 04:29
tpw_ruleswhich again can only really mean that this guy is returning null: https://github.com/AsahiLinux/u-boot/blob/75f0cb2074aaffcc13d18f6f6e5ab475550513e1/arch/arm/mach-apple/board.c#L777#asahi · 2024-01-05 04:29
tpw_ruleswhich i think we did#asahi · 2024-01-05 04:26
tpw_rulesas for env save i was just trying to run the partition selection function again#asahi · 2024-01-05 04:24
tpw_rulesok 0 is good i think#asahi · 2024-01-05 04:22
kitlithno device specified#asahi · 2024-01-05 04:22
kitlithit returns 0 on both partitions 5 and 9, and 1 on partition 7 and 1.#asahi · 2024-01-05 04:22
tpw_ruleswhat happens if you run "env save"?#asahi · 2024-01-05 04:17
tpw_rulesit shouldn't be#asahi · 2024-01-05 04:16
tpw_ruleshttps://github.com/AsahiLinux/u-boot/blob/75f0cb2074aaffcc13d18f6f6e5ab475550513e1/include/config_distro_bootcmd.h#L544 is this test failing?#asahi · 2024-01-05 04:16
tpw_rulescorrect#asahi · 2024-01-05 04:16
kitlithah. and fdt list complains that no addr is set?#asahi · 2024-01-05 04:16
tpw_rulesi checked on my machine and i'm not. fdt_addr_r doesn't point to a valid fdt if i interrupt the autoboot#asahi · 2024-01-05 04:15
kitlithGoing back to what you said about how the fdt should already be loaded -- I think you're right, and it's broken for some reason, which is messing up the overriding of efi boot order afterwards#asahi · 2024-01-05 04:15
tpw_rulesthat eventually does scan_dev_for_boot then scan_dev_for_efi then run boot_efi_bootmgr#asahi · 2024-01-05 04:12
kitlitham I parsing something wrong in the path of commands from bootcmd -> distro_bootcmd -> bootcmd_nvme0 -> nvme_boot -> scan_dev_for_boot_part?#asahi · 2024-01-05 04:09
tpw_rulesit should be running the boot manager#asahi · 2024-01-05 04:09
tpw_rulesit shouldn't be going through that path#asahi · 2024-01-05 04:06
kitlithsince that'd be the first one that scan_dev_for_boot_part will find#asahi · 2024-01-05 04:05
kitlithI don't see any reason why it *wouldn't* boot partition 5 anywhere#asahi · 2024-01-05 04:04
kitlithit lists partitions 5 and 9#asahi · 2024-01-05 04:02
tpw_ruleswhat if you do part list nvme 0 -bootable#asahi · 2024-01-05 04:02
kitlith(which was to be expected)#asahi · 2024-01-05 04:02
kitlithit just doesn't persist.