#asahi-alt · 2024-11-20 07:31
chaos_princesshttps://github.com/FEX-Emu/FEX/pull/4160#asahi-alt · 2024-11-20 07:31
chaos_princessYes. #asahi-alt · 2024-11-20 07:29
chaos_princessNo, there are several patches to fex itself#asahi-alt · 2024-11-20 07:26
chaos_princessGuess we need to pull lina's patches then#asahi-alt · 2024-11-20 07:15
chaos_princessCan you restart the vm, downgrade rootfs, and try again?#asahi-alt · 2024-11-20 07:14
chaos_princessWtf#asahi-alt · 2024-11-20 07:11
chaos_princessWhat wbout running zenity from vm manually?#asahi-alt · 2024-11-20 07:10
chaos_princessCan you try running glxgears from vm#asahi-alt · 2024-11-20 07:09
chaos_princessY'know what's weird? Zenity is no longer in the rootfs at all, it should be using the arm version now#asahi-alt · 2024-11-20 07:05
chaos_princesswhat error?#asahi-alt · 2024-11-20 07:05
chaos_princessRemoved all binaries that don't need to run under emulation, and also /var and /usr/share#asahi-alt · 2024-11-20 07:04
chaos_princessStrange, steam did launch on mine. #asahi-alt · 2024-11-10 08:28
chaos_princesschadmed: ty#asahi-alt · 2024-11-09 22:11
chaos_princessno, the issue is that i have system-llvm, and emerge -ac wants to delete it#asahi-alt · 2024-11-09 22:09
chaos_princessi also think that there is something broken with system-llvm, but that is also a problem for either future-me or someone-who-is-not-me#asahi-alt · 2024-11-09 22:04
chaos_princessdecided to do a world update today, and then decided that it can wait :P#asahi-alt · 2024-11-09 22:03
chaos_princessyes#asahi-alt · 2024-11-09 21:59
chaos_princesseither checksumming a wrong file, or re-running a build by accident#asahi-alt · 2024-11-09 21:58
chaos_princessit is _probably_ a screw-up on my part of some sort#asahi-alt · 2024-11-09 21:38
chaos_princesswell, ofc, i was doing other stuff(tm), and nobody else was working on it#asahi-alt · 2024-11-09 20:33
chaos_princessoverlay seems to be completely incompatible with slotted rust rn#asahi-alt · 2024-11-07 10:20
chaos_princessi will fix the msrv next release#asahi-alt · 2024-11-07 10:19
chaos_princessshould have probably did it that way in the first place tbh#asahi-alt · 2024-11-03 21:40
chaos_princessweird#asahi-alt · 2024-10-31 11:49
chaos_princessyou do not have to do any firmware updates, linux always uses firmware from macos 13.5#asahi-alt · 2024-10-21 12:42
chaos_princessnice#asahi-alt · 2024-10-20 10:57
chaos_princessevery single file open in vm is opened on the host from the same process, so naturally it hits that limit easily#asahi-alt · 2024-10-20 10:56
chaos_princessnot nearly enough due to how virtio-fs works#asahi-alt · 2024-10-20 10:55
chaos_princessyou need to do something on the host#asahi-alt · 2024-10-20 10:55
chaos_princessyes, fedora has something to deal with that#asahi-alt · 2024-10-20 10:52
chaos_princesssomething like that. i already use socket activation and it works, fedora does not use it for fedora reasons and instead has the steam script start it#asahi-alt · 2024-10-20 10:50
chaos_princessmuvm or hidpipe?#asahi-alt · 2024-10-20 07:57
chaos_princessdid you start the systemd unit for the server?#asahi-alt · 2024-10-18 10:17
chaos_princesshttps://pastebin.com/9b1kScd3 - the thing i use to get root inside the vm#asahi-alt · 2024-10-18 10:16
chaos_princessa bit busy with other stuff, but if you want to debug it - make a fake-sudo (simple c program that is setuid root, and just calls setuid() and then runs whatever you passed on command line), use it to run dhcpcd inside the vm with various flags, and see what goes wrong in your case#asahi-alt · 2024-10-17 18:54
chaos_princessyou need to add the copr https://copr.fedorainfracloud.org/coprs/g/asahi/steam/#asahi-alt · 2024-10-17 12:43
chaos_princessthis should fix it, but i haven't rebased that on latest version#asahi-alt · 2024-10-17 12:42
chaos_princesshttps://github.com/AsahiLinux/muvm/pull/53#asahi-alt · 2024-10-17 12:42
chaos_princessit is supposed to be set up as a private thingy inside the vm#asahi-alt · 2024-10-17 12:41
chaos_princessno#asahi-alt · 2024-10-17 12:40
chaos_princessthat would be the issue. #asahi-alt · 2024-10-17 12:39
chaos_princesswhat is the resolver inside the vm set to?#asahi-alt · 2024-10-17 12:37
chaos_princessoh, and yea, it makes sense that from iside the vm you get connection refused to 127/8, that is loopback to vm, not loopback to host#asahi-alt · 2024-10-17 12:36
chaos_princessno, not neccessary, just point it to 8.8.8.8 instead of your router#asahi-alt · 2024-10-17 12:35
chaos_princesson host#asahi-alt · 2024-10-17 12:35
chaos_princesscan you override your host dns to 8.8.8.8 or sth and check again#asahi-alt · 2024-10-17 12:35
chaos_princessno, but lina has a pr up to add that feature#asahi-alt · 2024-10-17 12:34
chaos_princessnetworking is just a mess, i may or may not look at it one day#asahi-alt · 2024-10-17 12:33
chaos_princessyou have your router as the dns server on host, right?#asahi-alt · 2024-10-17 12:30
chaos_princessecho 'nameserver 8.8.8.8' >/etc/resolv.conf from inside muvm before doing whatever you wanted to do