#asahi-dev · 2024-11-22 21:19
jannaucould be my fault#asahi-dev · 2024-11-22 21:17
mpson headphones it is ok, as earlier#asahi-dev · 2024-11-22 21:14
mpsyes, something like you say#asahi-dev · 2024-11-22 21:12
cy8aer6db == twice as loud. For me it is 4 times as quiet (not measured but heard).#asahi-dev · 2024-11-22 21:10
mpscy8aer: I don't know much about sound so can't tell in units but it looks like volume is halved down#asahi-dev · 2024-11-22 21:09
mpsthough on my loongarch64 it is normal with 6.12#asahi-dev · 2024-11-22 21:08
mpsmaybe is something with mainline 6.12#asahi-dev · 2024-11-22 21:07
cy8aer12db lower? #asahi-dev · 2024-11-22 21:06
cy8aeryes it is very low.#asahi-dev · 2024-11-22 21:02
mpshm, sound on speakers are lower than on previous kernels#asahi-dev · 2024-11-22 21:00
mpslooks like everything is fine#asahi-dev · 2024-11-22 20:47
mpsI will build now and see#asahi-dev · 2024-11-22 20:37
jannauthis hasn't seen a lot of testing yet (compared to 6.11.x)#asahi-dev · 2024-11-22 20:35
mpsjannau: thank you#asahi-dev · 2024-11-22 20:33
jannauI've pushed asahi-6.12.1-1 to github / asahi-wip#asahi-dev · 2024-11-21 23:48
emilia-mikihey. running `cat /proc/sys/vm/max_map_count` on the host gives me 1048576, but `muvm -- bash -c 'cat /proc/sys/vm/max_map_count'` prints 65530. Is it possible to set this value inside muvm?#asahi-dev · 2024-11-20 15:35
jannauor iboot left it in a state m1n1 doesn't expect. that shouldn't be a problem for running macos though. macos doesn't expect the display up at boot#asahi-dev · 2024-11-20 15:34
jannaudavid: m1n1 is interacting with firmware running on dcp. the firmware is included in macos and changes with each version. apparently it changed too much in macos 15.1 to be compatible with the code in m1n1#asahi-dev · 2024-11-20 14:20
david2I am trying to run m1n1 on past couple of week on m1 mini 2020 with 15.1 mac os ... here are the logs https://github.com/AsahiLinux/m1n1/issues/423 ... if there any workaround it will be helpful....#asahi-dev · 2024-11-19 19:34
solomonNo way to get a kernel console neither , not getting to a tty seems strange to me. If DRM fails shouldnt fbdev be a fallback ?#asahi-dev · 2024-11-19 19:32
solomonI have compiled and installed a new kernel image (asahi-6.9.8-1) with GPU support, however when I reboot I get a black screen with a blinking cursor#asahi-dev · 2024-11-19 19:31
solomonI have a question regarding kernel and mesa out-of-sync issues #asahi-dev · 2024-11-19 19:30
solomonHey yall :D#asahi-dev · 2024-11-18 15:55
david2Does anybody run m1n1 on latest macOS? M1 or M2 chip and it works fine?#asahi-dev · 2024-11-17 18:15
jannauI've pushed asahi-6.12-rc7-1 to github. This replaces parts of the imported rust-for-linux commits with upstream rust changes (both already accepted and recently proposed)#asahi-dev · 2024-11-16 17:17
sand4rt:q#asahi-dev · 2024-11-16 16:56
LarstiQooh!#asahi-dev · 2024-11-16 16:49
jannauI've pushed asahi-6.11.8-1 (and asahi-6.11.7-1) to github. main visible change should be edid support#asahi-dev · 2024-11-13 02:48
halloy-userhello#asahi-dev · 2024-11-12 14:20
david3well I am getting ESR_EC.IABORT_LOWER this exception whenever I try to run m1n1 and it is not handled#asahi-dev · 2024-11-12 12:27
david3hey anybody run the m1n1 with 15.x version on M1 pro or m1n1 late 2020? #asahi-dev · 2024-11-10 16:32
yeriFinally, bcm4388 works with recent broadcom firmware in OpenBSD bwfm(4)! I'll send diffs to OpenBSD after the refactoring.#asahi-dev · 2024-11-10 05:14
yeriI resolved the issue by adding skip_reset_vector flag to the softc and prevent PCI error. #asahi-dev · 2024-11-09 20:33
yeriI'm wondering if bwfm(4) lacks of some implementations.#asahi-dev · 2024-11-09 20:32
yeriHi, I'm working on adding supports for bcm4388 to OpenBSD bwfm(4). I have applied some patches imported from wifi/bcm4388 branch in the asahi linux to bwfm(4) (including firmware signature, SYSMEM core revision). The firmware was loaded properly, however, after a while the firmware was crashed. Here is the dmesg: https://pastebin.com/mJDcD67w (BWFM_DEBUG and console are enabled)#asahi-dev · 2024-11-09 10:49
slim083ty!!#asahi-dev · 2024-11-09 10:48
chaos_princesshttps://github.com/AsahiLinux/docs/wiki/SW%3AHypervisor#asahi-dev · 2024-11-09 10:37
slim083hi all! curious on if there's a way to get a developer configuration setup for an m3 mac? understandably, the script for installing asahi linux does not work on m3, but is there a way around for targeted development for the platform known currently? apologies if there is an existing forum already available for this information :)#asahi-dev · 2024-11-08 19:50
nicolas17looks like MBP M4 changed DFU port too#asahi-dev · 2024-11-08 19:49
nicolas17jannau: https://support.apple.com/en-us/120694 (DFU ports) has been updated#asahi-dev · 2024-11-08 14:55
mazah, first machine to advertise ETS2!#asahi-dev · 2024-11-08 14:50
jannauyes#asahi-dev · 2024-11-08 14:50
mazjannau: is that M4 mini?#asahi-dev · 2024-11-08 14:48
jannauuart is still working, no idea what the issue was#asahi-dev · 2024-11-08 14:47
jannaumaz: https://gist.github.com/jannau/21887332184c47b9c49c1561df9c23ed in the case you find an interesting bit#asahi-dev · 2024-11-08 14:00
mazhard to tell. they could have fused it. is there any way to use the UART from macos?#asahi-dev · 2024-11-08 13:58
jannauonly one line? I get the m1n1 uart debug output just no responses on proxy commands#asahi-dev · 2024-11-08 13:48
mazit could be that they have repurposed the SBU lines for something else.#asahi-dev · 2024-11-08 13:48
mazjannau: have you tried switching the UART lines to the primary USB, in case that helps (^_1, from memory)?#asahi-dev · 2024-11-08 13:43
jannaudavid: did you follow https://github.com/AsahiLinux/docs/wiki/SW:Hypervisor#preparing-the-macos-volume-by-disabling-security-features ? Can you try an earlier macos version? is there a lot of info printed from run_guest.py ? does macos print anything on the virtual uart?