2026-05-11
01:59tellowkrinkle has quit [Remote host closed the connection]
02:07tobhe has joined #asahi-alt
02:14tobhe_ has quit [Ping timeout: 480 seconds]
02:22tellowkrinkle has joined #asahi-alt
03:33dataviruset has joined #asahi-alt
04:16apc has quit [Read error: Connection reset by peer]
04:17apc has joined #asahi-alt
04:32apc is now known as Guest9161
04:32apc has joined #asahi-alt
04:32Guest9161 has quit [Ping timeout: 480 seconds]
05:00chadmed has quit [Read error: Connection reset by peer]
05:00chadmed has joined #asahi-alt
05:50dataviruset has quit [Ping timeout: 480 seconds]
06:05berdanka_Hi everyone! Very recently I started on porting Kali Linux to Apple Silicon. This project is heavily based on the work that Team Bananas did to port Debian, where I will try to add Kali stuff instead. I am a beginner, so most of my time is taken by troubleshooting simple problems :( Let me know if you want to get involved too! The repo is at https://codeberg.org/berdanka/m2-kali
06:11dataviruset has joined #asahi-alt
06:19dataviruset has quit [Ping timeout: 480 seconds]
06:35berdanka_ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
07:32berdanka has joined #asahi-alt
08:05u154ss_ has joined #asahi-alt
08:05u154ss_Cross-posted to asahi-dev - Hello all. A MESA question. Running Debian on an M2 Pro. The "current" MESA version seems to be pinned at 20250425. Is there a newer version? TIA.
08:06chaos_princessthis is not what a mesa version looks like
08:07JamesCalligeros[m]That sounds long enough ago to be one of our tags though
08:08chaos_princessswitch to upstream mesa, our fork is no longer needed and not updated
08:09chaos_princessmy link
08:09JamesCalligeros[m]If youre on debian just use the debian package
08:12JamesCalligeros[m]Can you not just remove the installed version to unpin it then grab from the main debian repo?
08:12JamesCalligeros[m]There is absolutely zero chance upstream arm64 debian has pinned their mesa to one of our tags
08:13u154ss_"There is absolutely zero chance upstream arm64 debian has pinned their mesa to one of our tags" - True.
08:15hightower3 has joined #asahi-alt
08:22hightower4 has quit [Ping timeout: 480 seconds]
08:34chadmed_ has joined #asahi-alt
08:34chadmed has quit [Remote host closed the connection]
08:57berdanka[m] has joined #asahi-alt
08:58berdanka[m]Hi everyone! Very recently I started working on porting Kali Linux to Apple Silicon. This project is heavily based on the work that Team Bananas did to port Debian, where I will try to add Kali stuff instead. I am a beginner, so most of my time is taken by troubleshooting simple problems :( Let me know if you want to get involved too! The repo is at https://codeberg.org/berdanka/m2-kali
09:06chaos_princessout of curiosity - why run kali on bare metal and not in a vm?
09:09berdankaso I am studying cybersecurity, and using a VM daily is a bit inconvenient. First of all - resource limitations. You have to divide RAM and CPU between the main host and the VM, this is especially problematic when cracking hashes. Secondly, the VM's integration isn't perfect. Even now it is a journey to properly install it, and the screen does not fit properly :(
09:19u154ss_ has quit [Quit: Page closed]
10:05jannau has quit [Quit: WeeChat 4.9.0]
10:08jannau has joined #asahi-alt
10:11hightower4 has joined #asahi-alt
10:18hightower3 has quit [Ping timeout: 480 seconds]
10:29kloenk has quit [Remote host closed the connection]
10:30kloenk has joined #asahi-alt
11:11hightower4 has quit [Read error: Connection reset by peer]
11:13hightower2 has joined #asahi-alt
11:30fossdd has quit [Remote host closed the connection]
11:31fossdd has joined #asahi-alt
12:04chadmed_ is now known as chadmed
12:36fen_ has joined #asahi-alt
12:41fen has quit [Ping timeout: 480 seconds]
12:44fen_ is now known as fen
14:07nela has quit [Ping timeout: 480 seconds]
14:08nela has joined #asahi-alt
14:26dataviruset has joined #asahi-alt
15:16hightower3 has joined #asahi-alt
15:18hightower4 has joined #asahi-alt
15:23hightower2 has quit [Ping timeout: 480 seconds]
15:26hightower3 has quit [Ping timeout: 480 seconds]
16:14hightower4 has quit [Remote host closed the connection]
16:38dataviruset has quit [Quit: dataviruset]
16:59hami has joined #asahi-alt
17:01hami has quit []
17:01Ardu0us_berdanka I run Kali via Parallels VM on a MBP M1 Max with 64gb unified memory and have zero issues with it. It wouldn't run properly via UTM, but runs great via Parallels. That said, if you're successful in porting Kali to run on bare metal via Asahi, I'm sure many would be grateful.
17:17berdanka has quit [Remote host closed the connection]
17:20berdanka has joined #asahi-alt
17:44berdanka has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
17:44berdanka has joined #asahi-alt
18:20habiby has joined #asahi-alt
18:22habibyberdanka i completely understand where you're coming from and would love to help you, little tiny thing though, you cited hash cracking as one of your needs for bare metal, but you can crack hashes in macOS anyway, unless you're using some obscure linux only hashes?
18:24habibyI would love to give you pointers on that if you would like because I've been cracking hashes competitively on my m1 for years with great success.
19:32noisycoil[mds]Folks, please send Debian people to the Debian channel
19:33noisycoil[mds]Trixie does not support asahi, DO NOT switch to the Debian packages
19:33noisycoil[mds]The pinning is correct, it is the last tag released by asahi
19:33noisycoil[mds]Testing/forky switched to upstream mesa
19:34noisycoil[mds]berdanka: Already done but unmaintained, see http://gitlab.com/NoisyCoil/kali-arm
19:34noisycoil[mds]I don't know if it still builds
19:35noisycoil[mds]I've also spoken with the Kali on arm maintainer, they seemed interested
19:37noisycoil[mds]The channel for Debian on Apple Silicon is #_oftc_#debian-bananas:matrix.org
19:38noisycoil[mds]berdanka: Note that the kali kernel is not the debian kernel, it has patches. So you must patch the debian+asahi kernel with the kali patches
19:39noisycoil[mds]Which in turn is based on the Debian kernel
19:41noisycoil[mds]If any of you is interested, I also ported Tails
19:42noisycoil[mds]In fact my work on Debian was initially motivated by porting Tails
20:30Guest8909is there any workaround for some usb devices (e.g. yubikey) disappearing after resuming from suspend until they are manually replugged? I've tried reloading some modules after resuming, but that didn't seem to help.
20:36Guest8909 is now known as craftyguy
20:37craftyguy is now known as Guest9233
20:41Guest9233 is now known as craftyguy
20:56noisycoil[mds]np :-)
21:18habiby has quit [Ping timeout: 480 seconds]
22:18berdankaArdu0us_: Parallells isn't free unfortunately, and I want to make it accessible to everyone
22:18kode54 has quit [Quit: The Lounge - https://thelounge.chat]
22:19berdanka<habiby> You can definitely do so on Mac, just not that convenient to switch between the Kali in VM and MacOS
22:22berdanka<noisycoil[mds]> I am a beginner, but I want to make the final project as a single installer script like Asahi Fedora and Asahi Debian :) Hopefully isn't too big of a goal
22:22chaos_princessi was actually suggesting kali in vm on a linux host
22:23chaos_princessno macos involved - fedora asahi host, kali guest
22:23kode54 has joined #asahi-alt
22:24chaos_princessor just run it on the same kernel but in docker/podman/distrobox
22:24noisycoil[mds]berdanka: No it's definitely possible and not at all hard once you understand what you need to do. Feel free to ping me
22:25noisycoil[mds]One word of advice: Kali still uses xfce, you should probably switch to kde
22:26berdankanoisycoil[mds] Do you mean that the Kali arm maintainer is interested in porting in on Mac?
22:26noisycoil[mds]Very much, yes!
22:26noisycoil[mds]I had a few discussions with them
22:27noisycoil[mds]Last time was around one year ago though
22:27noisycoil[mds]Np :-)
22:28berdankaSo I think I understood the process of how the Fedora Asahi script works. Now my main issue is compiling root.img and boot.img. I started figuring it out through the https://git.g3la.de/repos/m1-debian repo, however faced some dependency issues, which I am slowly solving
22:29berdankaBy the way, is that still the way Debian packages are being compiled for Asahi, or is it outdated?
22:30noisycoil[mds]So in Debian at this point we have everything in the archive but the kernel and u-boot
22:30noisycoil[mds]These you will find here: salsa.debian.org/bananas-team/wip/
22:30noisycoil[mds](linux-asahi and u-boot-asahi)
22:31noisycoil[mds]Kali tracks Debian testing, so you should too
22:32noisycoil[mds]cy8aer, the maintainer of the repo you linked to, compiles them from that repo. That's not the Bananas repo but it will still work
22:32noisycoil[mds]It's also simpler to use, so if you're still learning it's probably good to start from there
22:33noisycoil[mds]But also, you should consider using an external repository for Kali, like the bananas repository
22:34noisycoil[mds]That is, unless you really want to add the Kali patches, you probably don't need to build your own kernel, just use ours or cy8aer's
22:34noisycoil[mds](Same for u-boot)
22:36berdankanoisycoil[mds] Got it. I am trying to figure out how it works - could you summarize the process? Because I see the debian-asahi-image repo which compiles (?) the images I need, but what about U-boot and mesa? Does it compile them too?
22:37noisycoil[mds]No, everything is already in our archives, so we just apt-install them from within the image
22:37noisycoil[mds]We don't build debs when building images, we do it before
22:37noisycoil[mds]Mesa is not needed anymore
22:38noisycoil[mds]Debian testing's mesa already supports asahi
22:39noisycoil[mds]And yes, debian-asahi-image does build the images, but that's not suitable at all for Kali
22:39noisycoil[mds]Because it preinstalls Debian stuff
22:39noisycoil[mds]Instead, you should have a look at how kali builds its images, and adapt that to pull in the asahi packages
22:42berdankaGot it. So I will have to Use your kernel and U-boot with the $(How ARM Kali compiles images) and then put it through the debian-asahi-image and I'll get ready root.img and boot.img?
22:44noisycoil[mds]Most of the heavy lifting debian-asahi-image does is to build the Debian image. Since you don't want to do that, I wouldn't put it through the entire debian-asahi-image, only through the last stages, in which boot.img and root.img are created and then zipped into the final asahi package
22:45noisycoil[mds](You also need the metadata file for the installer, which is taken care of in repo too)
22:46berdankaGot it, thank you! Will start working on it. Last question - where would you recommend me have the project? I learned using the git ecosystem only a couple days ago, should I use GitLab, Codeberg or smth else?
22:48noisycoil[mds]This is purely a matter of personal preference, but if I had to choose, I'd mostly keep my projects wherever upstream leaves so things like PRs are simpler. In this case, Kali is on Gitlab, so I would choose Gitlab if you're working with the kali-arm repo
22:49noisycoil[mds]s/leaves/lives/
22:50noisycoil[mds]Hehe "substitute leaves with lives"
22:50noisycoil[mds]Not quite IRC but regex-like substitutions
22:50noisycoil[mds]And I hope you have a lot of fun, I absolutely did
23:20vimproved has quit [Remote host closed the connection]
23:21vimproved has joined #asahi-alt