#
…

2023-06-22

00:17odak_ has quit [Quit: odak_]
00:17odak_ has joined #asahi-dev
00:24mkurz has quit [Ping timeout: 480 seconds]
00:24void has joined #asahi-dev
00:45odak_ has quit [Quit: odak_]
00:45odak_ has joined #asahi-dev
02:00gabuscus has quit []
02:13ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
02:18chadmed_ has joined #asahi-dev
02:20gabuscus has joined #asahi-dev
02:21ourdumbfuture has joined #asahi-dev
02:59pbsds7 has quit []
02:59pbsds has joined #asahi-dev
03:01c10l35 has joined #asahi-dev
03:04novafacing has joined #asahi-dev
03:04novafacing_ has joined #asahi-dev
03:05void has quit [Remote host closed the connection]
03:08c10l3 has quit [Ping timeout: 480 seconds]
03:17novafacing_ has quit [Quit: Leaving]
03:17novafacing has quit [Quit: Leaving]
03:23compassion1 has quit [Read error: Connection reset by peer]
03:24compassion1 has joined #asahi-dev
03:34ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
03:35odak_ has quit [Quit: odak_]
03:36odak_ has joined #asahi-dev
03:55sid-linux has joined #asahi-dev
04:03sid-linuxQuestion relating to device tree. The IRQs for `mtp_mbox` for instance is `<AIC_IRQ 864 IRQ_TYPE_LEVEL_HIGH>` (etc)
04:05sid-linuxMany devices have AIC IRQ numbers that are in > 500
04:06sid-linuxBut if I do `cat /proc/interrupts` I am not able to find them there
04:09sid-linuxThe highest number before IPI0 is 106. Also all AIC2 interrupts do have a number have something like AIC2 66NNN . How do I find the interrupt number mentioned in the dtbi ?
04:11cylm_ has joined #asahi-dev
04:20cylm_ has quit [Quit: WeeChat 3.8]
04:28bisko has joined #asahi-dev
05:31odak_ has quit [Quit: odak_]
05:31odak_ has joined #asahi-dev
05:32Lightsword_ has joined #asahi-dev
05:34Lightsword has quit [Read error: Connection reset by peer]
05:34_isinyaaa has quit [Read error: Connection reset by peer]
05:38isinyaaa has joined #asahi-dev
06:21odak_ has quit [Quit: odak_]
06:21odak_ has joined #asahi-dev
06:27jannausid-linux: it's the low 16-bits of hwirq (the number after AIC2)
06:47cylm has quit [Ping timeout: 480 seconds]
06:58sid-linuxjannau: Thanks !
07:00sid-linux has quit [Remote host closed the connection]
07:28Dementor has quit [Ping timeout: 480 seconds]
07:32MajorBiscuit has joined #asahi-dev
07:36i509vcb has quit [Quit: Connection closed for inactivity]
07:44bps has joined #asahi-dev
07:45nsklaus has joined #asahi-dev
08:36MajorBiscuit has quit [Quit: WeeChat 3.6]
09:02c10l35 has quit []
09:03c10l has joined #asahi-dev
09:07Dementor has joined #asahi-dev
09:10bcrumb has joined #asahi-dev
09:11sid-linux has joined #asahi-dev
09:14sid-linuxA question related to asahi linux (arch) debugging. I set `loglevel=7` in /etc/grub.d/10_linux , run `update-grub` successfully
09:14sid-linuxHowever I still don't see a higher level of detail via dmesg
09:15sid-linux`cat /proc/sys/kernel/printk` gives me
09:16j`eysid-linux: what about /proc/cmdline?
09:17sid-linuxIt successfully shows `quiet loglevel=7` there
09:17sid-linuxsorry it is `[...] loglevel-7 quiet`
09:18mpssid-linux: loglevel controls whic messages will be printed on console, dmesg always shows what is 'in kernel'
09:18mpsusually is enough to remove quiet from kernel cmdline
09:19mpsto get messages on console
09:19sid-linux(sorry I had changed `default/grub` and not `/etc/grub.d/10_linux)
09:20sid-linuxI basically don't want any messages on console. I want more detail when I check out `dmesg`
09:20mpsthen loglevel will not change much, if anything
09:21j`eysid-linux: loglevel changes what's printed, not what goes into dmesg
09:21sid-linux dev_dbg(rtk->dev,
09:21sid-linux "RTKit: Starting system endpoint 0x%02x\n", ep);
09:21sid-linux apple_rtkit_start_ep(rtk, ep);
09:21Dementor7 has joined #asahi-dev
09:21mps"loglevel= All Kernel Messages with a loglevel smaller than the console loglevel will be printed to the console. It can also be changed with klogd or other programs."
09:22mpsquote from kernel-parameters.txt
09:22sid-linuxsee `drivers/soc/apple/rtkit.c` line 195 onwards
09:22sid-linuxI never see any "Starting system endpoint..." messages in dmesg
09:23sid-linuxHowever I do see:
09:23sid-linux dev_warn(rtk->dev,
09:23sid-linux "RTKit: Unknown system endpoint: 0x%02x\n",
09:23_jannau__dev_dbg is only printed if DEBUG is defined in the source file
09:23mpsmaybe this part is not reached by kernel
09:23sid-linuxbasically `dev_warn` is seen in `dmesg` while `dev_dbg` is never seen in dmesg
09:24_jannau__otherwise it's a no-op
09:24j`eysid-linux: add a #define DEBUG, to the top of that file and recompile
09:24sid-linuxj`ey: jannau: thanks :-)
09:25sid-linuxwould be cool to dynamically set DEBUG rather than recompile though
09:25mps"debug [KNL] Enable kernel debugging (events log level)." maybe this cmdline param could help
09:26mpsnever used it (at least last 10 years)
09:26sid-linuxWill try and report back.
09:27sid-linux has quit [Quit: User exited]
09:27j`eyoh, asahi builds with CONFIG_DYNAMIC_DEBUG
09:27j`ey(if you're using their kernels)
09:27Dementor has quit [Ping timeout: 480 seconds]
09:27Dementor7 is now known as Dementor
09:29j`eyso: dyndbg="file rtkit.c +p" on the boot commandline might work
09:30j`eymaybe you need rtkit.dyndbg, since rtkit is a module
09:39bcrumb has quit [Quit: WeeChat 3.8]
09:39sid-linux has joined #asahi-dev
09:41sid-linuxdyndebug looks very promising -- thanks. trying it out. Here is the link to the latest documentation https://www.kernel.org/doc/html/latest/admin-guide/dynamic-debug-howto.html
09:42ourdumbfuture has joined #asahi-dev
09:45sid-linux has quit [Quit: User exited]
09:52sid-linux has joined #asahi-dev
09:53sid-linuxmps: adding dyndbg to the boot cmdline worked ! I now see the debug messages
09:53sid-linuxvery useful
09:54sid-linuxfor rtkit.c
09:55Leftas7 has quit [Quit: Bye!]
09:55leftas has joined #asahi-dev
09:55WildCatFish has joined #asahi-dev
09:56j`eysid-linux: what was the dyndbg command you use?
09:56odak_ has quit [Quit: odak_]
09:57odak_ has joined #asahi-dev
09:57sid-linuxoops sorry I meant to thank you j`ey for the tip !
09:58sid-linuxIn my `/etc/default/grub`
09:58sid-linuxI now have
09:58sid-linuxGRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet dyndbg='file rtkit.c +p'"
09:58sid-linuxthen I did `sudo upgrade-grub`
09:59j`eyok nice, good to know that works!
09:59j`ey(but often when youre debugging you can just rebuild)
10:04sid-linux(thanks for patiently answering my questions). For a custom build you would build the tree with the asahi linux config and then simply copy over the vmlinuz to /boot/vmlinuz-linux-asahi-edge ?
10:04ydalton has joined #asahi-dev
10:05j`eyyou could also build the package with makepkg I think, if that allows you to modify the source dir
10:05sid-linuxyeah `makepkg -s` sounds better and is plugged into initramfs etc. generation
10:06sid-linuxbut I wonder if its compile is incremental
10:06sid-linuxI'm going to try it out. Trivially change a file and see how long it takes to regenerate package
10:09ydaltonhi, i have a question, is there any documentation on the m1n1 shell commands? i can't seem to find any info about them other than when i connect to m1n1 proxy mode.
10:11j`eyI don't think so
10:11j`eyjust the source
10:11WildCatFish has quit [Remote host closed the connection]
10:12WildCatFish has joined #asahi-dev
10:13ydaltonshould i open up an issue in the docs github repo?
10:14chadmedthe wiki is publicly editable
10:15ydaltonalright, thank you both, i'm gonna see what i can do
10:18bisko has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
10:24sid-linux has quit [Remote host closed the connection]
10:25WildCatFish has quit [Remote host closed the connection]
10:28sid-linux has joined #asahi-dev
10:29sid-linuxj`ey: btw if you want to add dyndbg for different files from the boot cmdline you can also do it
10:29sid-linuxGRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 quiet dyndbg='file rtkit.c +p' dyndbg='file apple-pmgr-pwrstate.c +p'"
10:29sid-linuxsimply repeat dyndbg
10:30sid-linuxProbably obvious in retrospect, but just mentioning to you
10:30ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
10:31ydalton has left #asahi-dev [ERC 5.4 (IRC client for GNU Emacs 28.2)]
10:32ourdumbfuture has joined #asahi-dev
10:35sid-linux_ has joined #asahi-dev
10:39sid-linux has quit [Ping timeout: 480 seconds]
10:42cylm has joined #asahi-dev
11:03nimprod3l has joined #asahi-dev
11:14ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
11:25cylm_ has joined #asahi-dev
11:30nimprod3l has quit [Ping timeout: 480 seconds]
11:36cylm_ has quit [Quit: WeeChat 3.8]
11:43cylm_ has joined #asahi-dev
11:45ourdumbfuture has joined #asahi-dev
11:54WildCatFish has joined #asahi-dev
12:07cylm_ has quit [Ping timeout: 480 seconds]
12:31nimprod3l has joined #asahi-dev
12:38WildCatFish has quit [Remote host closed the connection]
12:42WildCatFish has joined #asahi-dev
12:51WildCatF_ has joined #asahi-dev
12:51WildCatFish has quit [Read error: Connection reset by peer]
12:53WildCatFish has joined #asahi-dev
12:54WildCatF_ has quit [Read error: Connection reset by peer]
12:55WildCatF_ has joined #asahi-dev
13:01WildCatFish has quit [Ping timeout: 480 seconds]
13:03WildCatFish has joined #asahi-dev
13:03WildCatF_ has quit [Remote host closed the connection]
13:08WildCatFish has quit [Remote host closed the connection]
13:08WildCatFish has joined #asahi-dev
13:09WildCatFish has quit []
13:13sid-linux has joined #asahi-dev
13:17sid-linux_ has quit [Ping timeout: 480 seconds]
13:17rippanda12_ has joined #asahi-dev
13:19rippanda12_hello, im a dev for an ArchARM based OS and I want to support M1 how can I do it properly and not pull a Manjaro
13:19rippanda12_is there someone I need to get in contact with and if yes who
13:20nimprod3l has quit [Quit: Leaving]
13:28tpw_rulesrippanda12_: i can't speak for the asahi project staff but for my alt distro i ship package versions from the main branch of https://github.com/AsahiLinux/PKGBUILDs/ and everything has gone okay. that's what is the public release of asahi packages. manjaro got in trouble for shipping random tags
13:34bisko has joined #asahi-dev
13:43rippanda12_tpw_rules: how do users install your os? also which one? I wanna make it like the real Asahi installer but it installs my os
13:48rippanda12_ has quit [Remote host closed the connection]
14:22mkurz has joined #asahi-dev
14:28leitao has joined #asahi-dev
14:44onlined has joined #asahi-dev
14:57nela has quit [Ping timeout: 480 seconds]
15:02odak_ has quit [Quit: odak_]
15:02odak_ has joined #asahi-dev
15:06nela has joined #asahi-dev
15:20nela has quit [Ping timeout: 480 seconds]
15:25nela has joined #asahi-dev
15:25leitao has quit [Ping timeout: 480 seconds]
15:33onlined_ has joined #asahi-dev
15:33onlined has quit [Ping timeout: 480 seconds]
15:59cylm has quit [Quit: WeeChat 3.6]
16:13onlined has joined #asahi-dev
16:18onlined_ has quit [Ping timeout: 480 seconds]
16:22bps has quit [Ping timeout: 480 seconds]
16:26ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
16:28maria has quit [Remote host closed the connection]
16:45leitao has joined #asahi-dev
16:47onlined_ has joined #asahi-dev
16:47onlined has quit [Read error: Connection reset by peer]
17:05leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
17:07leitao has joined #asahi-dev
17:23ourdumbfuture has joined #asahi-dev
17:41maria has joined #asahi-dev
17:41onlined_ has quit [Read error: Connection reset by peer]
18:04leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:05Cyrinux9 has quit []
18:07leitao has joined #asahi-dev
18:08Cyrinux9 has joined #asahi-dev
18:09ydalton has joined #asahi-dev
18:11ydalton has quit [Remote host closed the connection]
18:16leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:23leitao has joined #asahi-dev
18:26ydalton has joined #asahi-dev
18:31ydaltonhi, i'm having troubles running macOS as a hypervisor guest. i seem to be running into kernel panics with the rainbow apple. i am using the stock macOS kernel.
18:33ChaosPrincessconnect to the shell, look at the debug logs see if anything is there
18:35ydalton has quit [Remote host closed the connection]
18:36svenmake sure that the kernel you feed to run_guest is the same version as the macOS installation where you installed m1n1
18:36svena mismatch usually results in obscure kernel panics
18:37ydalton has joined #asahi-dev
18:39ydaltonin my case m1n1 came installed with the asahi installer
18:39ydaltonwhen i was looking for the kernelcache, i noticed there were two directories with long hashes, only one of which contained a kernelcache
18:41ydalton has left #asahi-dev [ERC 5.4 (IRC client for GNU Emacs 28.2.50)]
18:42ydalton has joined #asahi-dev
18:43svenis the m1n1 on a partition that contains a full macOS installation?
18:43j`eysounds like it was a m1n1-only installation using the installer?
18:43svenyeah, that’s what I suspect
18:44ChaosPrincessthat means wrong firmware most likely, no?
18:44sventhat means it’s not gonna work even with the correct firmware
18:44ydaltoni used chose for a full desktop installation
18:44svenxnu expects a full macOS userspace
18:45svenyeah, that’s not gonna work for running xnu
18:45j`eyydalton: you want to partition and install macOS
18:46svenlooks reasonably up to date after a quick glance
18:47ydaltonso i'll need to have only macOS with m1n1?
18:48svenyou need a full macOS installation and then replace the boot object with m1n1 like shown on that page I linked
18:50ydaltonalright, does it matter what macOS version i have?
19:14joshwilding2011 has joined #asahi-dev
19:16mlp has quit [Read error: Connection reset by peer]
19:16mlp has joined #asahi-dev
19:17ydaltonif i install m1n1 in the macOS volume, does that mean i will no longer be able to boot macOS directly?
19:18ydalton has left #asahi-dev [ERC 5.4 (IRC client for GNU Emacs 28.2.50)]
19:19ydalton has joined #asahi-dev
19:21jannauydalton: not directly. changing the boot policy will revert to the macos kernel as boot object
19:23ydaltonokay, thank you guys for your help!
19:23ydalton has left #asahi-dev [#asahi-dev]
19:27leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:46___nick___ has joined #asahi-dev
19:47___nick___ has quit []
19:49___nick___ has joined #asahi-dev
19:57sid-linux has quit [Quit: User exited]
20:07___nick___ has quit [Ping timeout: 480 seconds]
20:09leitao has joined #asahi-dev
20:17joshwilding2011 has quit [Quit: Konversation terminated!]
20:26leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
20:34leitao has joined #asahi-dev
20:49kaazoo has joined #asahi-dev
20:53hightower2 has joined #asahi-dev
20:55kaazooHi, I was trying to understand why MTP didn't work after updating to u-boot-asahi-2023.04-2 on j414s. Seems like https://github.com/AsahiLinux/u-boot/tree/asahi-releng doesn't contain support for oslog yet (see earlier commit for adding this https://github.com/AsahiLinux/u-boot/commit/42bb4082b51725f1cb74a4864e009dc13b9301d3)
21:21kaazoo has left #asahi-dev [#asahi-dev]
21:46zalyx0 has quit [Quit: later alligator]
21:47zalyx0 has joined #asahi-dev
22:05cylm has joined #asahi-dev
22:18lynndotpy has quit [Quit: bye bye]
22:19lynndotpy has joined #asahi-dev
22:21lynndotpy has quit []
22:22lynndotpy has joined #asahi-dev
22:22odak_ has quit [Quit: odak_]
22:22odak_ has joined #asahi-dev
22:29bps has joined #asahi-dev
22:43leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:45leitao has joined #asahi-dev
23:14nsklaus has quit [Ping timeout: 480 seconds]
23:38ourdumbfuture has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
23:43ourdumbfuture has joined #asahi-dev
23:58chadmed_ has quit [Remote host closed the connection]
…