2025-06-21
01:08___nick___ has quit []
01:12___nick___ has joined #asahi-dev
02:16tobhe_ has joined #asahi-dev
02:21hexdump0815 has joined #asahi-dev
02:22hexdump01 has quit [Ping timeout: 480 seconds]
02:23tobhe has quit [Ping timeout: 480 seconds]
02:28pb17 has quit [Ping timeout: 480 seconds]
02:33pb17 has joined #asahi-dev
03:26john-cabaj has quit [Ping timeout: 480 seconds]
04:00nora_ has joined #asahi-dev
04:01nora has quit [Ping timeout: 480 seconds]
04:14Z750 has quit [Quit: bye]
04:22john-cabaj has joined #asahi-dev
04:24Z750 has joined #asahi-dev
04:29eluks has quit [Remote host closed the connection]
04:30eluks has joined #asahi-dev
05:44neanderlot has joined #asahi-dev
05:45neanderlot has quit []
05:55john-cabaj has quit [Ping timeout: 480 seconds]
07:07mripard has quit [Quit: WeeChat 4.6.3]
10:37chadmed has quit [Quit: Konversation terminated!]
10:38riker77 has quit [Quit: Quitting IRC - gone for good...]
10:51chadmed has joined #asahi-dev
13:22malfunction54 has quit [Remote host closed the connection]
14:15jannaubreaks how? display does never power off? what happens when you press esc on the lock screen?
14:21fl0_iddoes anybody have an idea why this seemingly stops at bootup? https://www.pastery.net/exwxde/
14:24chaos_princessfl0_id: usb power gating is probably not working properly
14:40fl0_idmmh yeah that would make sense. if that is necessary for bootup :) anyway, if you have any idea on boot options to try, let me know. though I assume it needs support in m1n1
14:54fl0_idsven yeah. is there a way to turn more debugging/verbosity on? I just used the flags/command from the docs, only adapted for t6031 kernel
14:56fl0_idbased on the output, is this still just m1n1 output or already xnu? It doesn't look like xnu output that I am used to from just turning on -v mode
15:28fl0_idoh and as it has so much output about the cpu4 at the end, I assume that's the one it's starting on?
16:18chadmed has quit [Quit: Konversation terminated!]
16:18chadmed has joined #asahi-dev
16:20chadmed has quit []
16:20chadmed has joined #asahi-dev
16:28amarioguy2btw one note on the backtrace thing in m1n1 - more of an aside i wanted to note than anything else - i've had certain situations during my debugging where the hv debugger backtrace is just infinitely spamming the same two addresses when it tries to print the backtrace
16:30amarioguy2i don't think it's a foundational m1n1 debugger problem? but at the same time wanted to point the weird behavior out in case anyone else had that behavior (it usually tends to happen when the Windows first-stage bootloader hits an exception and enters the branch loop)
16:31amarioguy2also had a quirk a couple times where sometimes a few instructions before an exception is hit it will "speculate" to the exception directly - which was *so* annoying when trying to debug why exceptions happened
16:53amarioguy2fl0_id: yes that's sorta been the reason i sometimes ask questions here
17:53WindowPain4 has joined #asahi-dev
17:59WindowPain has quit [Ping timeout: 480 seconds]
17:59WindowPain4 is now known as WindowPain
18:35__nick__ has joined #asahi-dev
18:36___nick___ has quit [Ping timeout: 480 seconds]
18:51Calandracas_ has joined #asahi-dev
18:56chadmed has quit [Quit: Konversation terminated!]
18:57chadmed has joined #asahi-dev
18:57chadmed has quit []
18:57chadmed has joined #asahi-dev
18:57Calandracas has quit [Ping timeout: 480 seconds]
18:58chadmed has quit []
18:58chadmed has joined #asahi-dev
20:02__nick__ has quit [Remote host closed the connection]
20:20fossdd has joined #asahi-dev
21:03pb17 has quit [Ping timeout: 480 seconds]
21:07pb17 has joined #asahi-dev
21:30ece314378925355451680698427415 has joined #asahi-dev
22:16chadmed has quit [Quit: Konversation terminated!]
22:16chadmed has joined #asahi-dev
22:17chadmed has quit []
22:17chadmed has joined #asahi-dev
22:17chadmed has quit []
22:18chadmed has joined #asahi-dev
22:18chadmed has quit []
22:18chadmed has joined #asahi-dev