chir4gm has quit [Read error: Connection reset by peer]
riker77_ has joined #asahi
riker77 has quit [Ping timeout: 480 seconds]
riker77_ is now known as riker77
nullroute has quit [Ping timeout: 480 seconds]
nullroute has joined #asahi
tolopea1E0040[m] has joined #asahi
PhilippvK has joined #asahi
phiologe has quit [Ping timeout: 480 seconds]
off^ has quit [Remote host closed the connection]
marvin24_ has joined #asahi
pyropeter1 has joined #asahi
PyroPeter_ has quit [Ping timeout: 480 seconds]
marvin24 has quit [Ping timeout: 480 seconds]
<amw>
Glanzmann: Just a brief question your latest build 5.19.0-rc7 WiFi not working :brcmfmac 0000:01:00.0: brcmf_pcie_init_ringbuffers: Allocating ring buffers failed
<amw>
5.18.0 was fine - brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4378/3 wl0: Oct 26 2021 16:10:41 version 18.20.310.15.7.8.120 FWID 01-5d6c3867
Glanzmann has joined #asahi
<Glanzmann>
Is it already safe to update to 12.5. The update was offered this morning to me. it seems to be GA.
ptudor has quit [Ping timeout: 480 seconds]
ptudor has joined #asahi
<Glanzmann>
update worked for me.
<Glanzmann>
amw: Update kernel. The current one worked for me, can you try running curl -sL https://tg.st/u/ksh | bash again, use a ethernet dongle or download it under macos copy it to the efi and install it from there. also make sure to update m1n1/u-boot. Moving discussion to #asahi-alt
thevar1a- has quit [Remote host closed the connection]
thevar1able1 has joined #asahi
mini0n has quit [Remote host closed the connection]
systwi has quit [Remote host closed the connection]
systwi has joined #asahi
systwi_ has joined #asahi
systwi has quit [Ping timeout: 480 seconds]
amarioguy2 has joined #asahi
amarioguy has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi
Ry_Darcy has joined #asahi
<wookey[m]>
The kernel I am using says it doesn't have apfs support built in so I can't mount apple partitions in Linux. Can we turn that option on?
<mps>
wookey[m]: kernel doesn't have apfs driver
<wookey[m]>
Perhaps it already is in an update I don't have? Would be very handy to share files between worlds until sleep works and I can forget about MacOS :-)
<bluetail>
dottedmag, I am aware. I cannot ascertain or explain it. I just know it does not happen on the macosx variant. But on macos I didnt run the unzip command in a folder... Could it be that >windows< set permissions the unzip command set 'false' permissions?
<bluetail>
Question would be, how can I make sure its >not< asahi?
<dottedmag>
Well, you could try to reproduce the same problem on another Linux machine.
<dottedmag>
Also please have a look at dmesg to see if there are any suspicious errors under Asahi - it might be that USB is really broken, of course.
gladiac is now known as Guest6474
gladiac has joined #asahi
<bluetail>
dottedmag, I think I know now what is going on. But it is very strange. Basically, when I extract the zip file as non-root user, it will end in operation not permitted and then when its plugged into a windows machine it wants to run chkdsk. What I just found out that if I unzip as a root it doesn't happen. Could it be that the user 'def' is not privileged to unzip and it messes up the folder and then messes up the privileges?
<dottedmag>
This sounds... dubious. What is the filesystem on the disk, and what driver do you use?
Guest6473 has quit [Ping timeout: 480 seconds]
<marcan>
if dmesg does not have any errors, there is ~no chance this is an asahi problem
<bluetail>
exfat. The second question I am not certain I can answer. But I try. "xhci_hcd". "USB6-2"d
<bluetail>
dmesg | grep error returns this:
<marcan>
"| grep error" is not how you look for errors
<bluetail>
Does it matter? Otherwise I'll just pick ntfs-3g
<marcan>
you're probably better off with ntfs
<marcan>
or just do what I said and try formatting it as exfat again
<marcan>
it could just be latent corruption
<bluetail>
thank you so much. I'll never use exfat again
Luciee has joined #asahi
Luciee was kicked from #asahi by ChanServ [You are not permitted on this channel]
<marcan>
persistent, eh
bisko has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Techcable has quit [Remote host closed the connection]
Techcable has joined #asahi
c10l has quit [Quit: Bye o/]
c10l has joined #asahi
c10l has quit []
c10l has joined #asahi
babble has joined #asahi
babble has quit []
<qyliss>
Hi, I'm trying to boot an Asahi kernel with QEMU TCG emulation, to debug a boot problem on my distro that's annoying to debug on hardware. I've tried both U-Boot and EDK2, and direct kernel boot, but none have worked.
<qyliss>
With U-Boot and EDK2, once I get past GRUB, I get "EFI stub: ERROR: This 16 KB granular kernel is not supported by your CPU", but QEMU TCG should support 4K, 16K, and 64K.
<qyliss>
Any ideas?
<j`ey>
what cpu are you passing to qemu?
<qyliss>
-cpu max
<bluetail>
sounds exciting. Is it possible to virtualize x86 on ARM? Like a small windows 10 vm. I know on mac I think it was limited to win 11 ARM. But whats the deal with QEMU?
<j`ey>
bluetail: you can emulate x86 with qemu
<qyliss>
QEMU can emulate other CPU architectures but it's very slow
<qyliss>
(it should be able to do it on macOS too!)
<bluetail>
I dont like the word 'emulate' cause I remember pcsx2 on my old athlon computer and it was sooo slow
janrinze has joined #asahi
<j`ey>
well thats what it is, as opposed to KVM where it runs natively
<janrinze>
qyliss: which distro are you trying to run?
<qyliss>
NixOS, but it shouldn't be relevant, because I'm not getting to the kernel.
<qyliss>
(and the kernel is Asahi's)
<janrinze>
did you first install Asahi and ARCH linux?
<qyliss>
no, I built a NixOS installer image with Asahi's kernel.
<j`ey>
qyliss: are you running qemu on linux on the mac or?
<qyliss>
I'm running it on x86_64 Linux.
<qyliss>
(But I'm using TCG, so the architecture shouldn't matter)
<j`ey>
what qemu version?
<qyliss>
6.2.0, I'm just about to try something more recent.
<j`ey>
thats still pretty recent
<janrinze>
Okay, I just ask because i tried to boot Debian with the ARCH kernel and that failed because the ARCH initrd and Debian do not work together.
<tpw_rules>
qyliss: hi
<qyliss>
I'm not getting as far as initrd :)
<qyliss>
tpw_rules: hi!
<j`ey>
qyliss: how big is the Image?
<qyliss>
ooh that's a good question
<tpw_rules>
there is the 4k patch if that might help?
<qyliss>
tpw_rules: I'm trying to avoid it
<tpw_rules>
are you sure tcg specifically supports 16k granules? there are cases in qemu that don't iirc
<jannau>
does '-cpu max' activates all supported features or does it resolves to a specific cpu? say cortex-a72? the latter doesn't support 16k page size iirc
<tpw_rules>
also what is your boot problem?
<jannau>
no need for the patch in qemu, dart is not emulated in qemu
<j`ey>
jannau: all features
<qyliss>
tpw_rules: on hardware, initramfs doesn't load.
<tpw_rules>
would the m1n1 hypervisor be helpful?
<qyliss>
possibly, but I'd rather use QEMU because I already know how to use it :P
<qyliss>
(and it doesn't require interacting with hardware, which is annoying, and this is unlikely to be a hardware-specific problem)
<qyliss>
It's a repository of hardware-specific NixOS profiles
<qyliss>
so it's the place for custom kernels, special drivers, etc.
<tpw_rules>
does hydra compile any of those kernels?
<qyliss>
No
<qyliss>
I'd like to change that
<qyliss>
I'd also like to expose them as packages, not just NixOS modules
<tpw_rules>
ok cause that is my biggest reason to not switch to a more nixos kernel config
<qyliss>
it's a bit underloved atm
<qyliss>
but I'm hoping to get it in much better shape so it's a satisfying solution to vendor kernel proliferation
<tpw_rules>
for arm too?
<qyliss>
yes
<qyliss>
okay, qemu 7.1.0-rc0 gives me 'qemu-system-aarch64: failed to find romfile "efi-virtio.rom"', so maybe that's a bit too recent :P
<qyliss>
(I tried 7.1.0-rc0 before 7.0.0 because I already had a 7.1.0-rc0 binary around)
<janrinze>
ARM32 kernels can self-decompress and have attached DTBs and more. Apparently in my head I assumed that these features would all be available in aarch64.
ciggi has joined #asahi
ciggi_ has quit [Read error: Connection reset by peer]
ciggi_ has joined #asahi
ciggi has quit [Read error: Connection reset by peer]
balrog has quit [Quit: Bye]
balrog has joined #asahi
Stroller has joined #asahi
<bluetail>
after installing ntfs on the USB drive, I can no longer login to the console since it was in /etc/fstab
<bluetail>
it expects the drive with exfat
<bluetail>
I tried using a usb stick with exfat temporarily instead but it wouldnt do
<bluetail>
I cannot seem to reach advanced settings before it boots it
<bluetail>
so I probably searching for a recovery stick to edit /etc/fstab
<mps>
bluetail: on asahi?
<bluetail>
yea on asahi
<bluetail>
next time I put fstab on auto mount and not explicitly on exfat
<jannau>
bluetail: appending "init=/bin/sh" should you let edit /etc/fstab without root password but you might have to load the necessary modules yourself
<Stroller>
ta very much, j`ey
<bluetail>
jannau, why would I do that though when I already have booted mps's boot image
<bluetail>
I can just mount the partition (have to find out which one) and edit the file
<jannau>
do what you like
<mps>
TIMTOWTDI
<mps>
bluetail: lsblk -f could help to find partitions
<bluetail>
hold on a sec
<bluetail>
so I flashed the image on windows with balena etcher
<bluetail>
but the recovery screen doesnt show the drive
<bluetail>
should I instead boot into mac and try mounting the installment?
<tpw_rules>
the macos recovery screen won't
<tpw_rules>
you'll have to start u-boot, interrupt the auto-run, then do `run bootcmd_usb0`
<bluetail>
thats the thing
<tpw_rules>
what's the thing
<mps>
yes, I documented this but bluetail is fast to read
<bluetail>
I cant interrupt it. I already put another usb keyboard to interrupt at boot but it wouldnt register
<bluetail>
I used the arrow keys and wanted to go to advanced settings
<bluetail>
or do I have to enter CTRL+C ?
<mps>
'enter' is enough
<bluetail>
so if you press enter during u-boot interrupts. ok
<mps>
but if keyboard is not detected it will not work
<mps>
bluetail: yes, when u-boot appears
<bluetail>
since my monitor is in a different room, can I just hammer enter a couple times?
<mps>
I think yes
<mps>
though never checked this
<bluetail>
oh it didnt work
<bluetail>
I hit it all the time and Im still at that account is locked screen
<Stroller>
Sorry to be so thick, but if I use the "Install macOS.app" to create install media, I can boot the macOS installer from a USB - am I correct in assuming that doesn't work for Linux because of signing?
<mps>
bluetail: some keyboards doesn't works with u-boot and grub