marcan changed the topic of #asahi to: Asahi Linux: porting Linux to Apple Silicon macs | "Does XXX work yet?": https://alx.sh/fs | GitHub: https://alx.sh/g | Wiki: https://alx.sh/w | Topics: #asahi-dev #asahi-re #asahi-gpu #asahi-alt #asahi-stream #asahi-offtopic | Keep things on topic | Logs: https://alx.sh/l/asahi
Moprius has quit [Quit: bye]
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
<nightstrike> chadmed: I wasn't using wifi as a euphemism for internet access, I was instead implying that via a vm, a wired interface would be emulated. Dongles on macs I suppose are another option, but they tend not to work well even natively IMO
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
eiln has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
amarioguy has quit [Remote host closed the connection]
gabuscus has quit []
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
gabuscus has joined #asahi
dcow has joined #asahi
crabbedhaloablut has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
skipwich has quit [Quit: DISCONNECT]
skipwich has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
jeisom has quit [Quit: Leaving]
marvin24 has joined #asahi
marvin24_ has quit [Ping timeout: 480 seconds]
ten157237743247 has joined #asahi
ten15723774324 has quit [Remote host closed the connection]
mspe has quit [Quit: WeeChat 3.8]
mspe has joined #asahi
mspe has quit []
mspe has joined #asahi
systwi has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
slp_ has joined #asahi
toasterking has left #asahi [#asahi]
kaazoo has joined #asahi
dcow has joined #asahi
Yannik_Sc has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #asahi
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
Yannik_Sc has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
<PaulFertser_> nightstrike: this is the list of USB wifi adapters working reasonably (with upstream drivers in Linux): https://github.com/morrownr/USB-WiFi
Yannik_Sc has joined #asahi
tenkuu has quit [Ping timeout: 480 seconds]
dcow has quit [Ping timeout: 480 seconds]
leitao has joined #asahi
leitao has quit []
<j`ey> chadmed: I would use firefox but chrome has web bluetooth which I ""need""!
<janneg> bmc4388 (used on all apple devices with wifi 6e) is working now, support might arrive quicker than an order
basso2 has quit [Ping timeout: 480 seconds]
leitao has joined #asahi
Yannik_Sc has quit [Ping timeout: 480 seconds]
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dcow has joined #asahi
tano70_Air has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
<psykose> what's an interesting use of web bluetooth? i can see webusb because it can do memes like "flash your usb stick" from the browser but..
<j`ey> my use case is that I have a timer that connects to a web application
<psykose> hm, fancy :)
<j`ey> it used to do it via mic input, and send rs232 signals in via sound
<j`ey> but that was flakey, and needed a wire!
<chadmed> psykose: there are a couple of nifty parlour tricks you can do wit hthat stuff, but its mostly enterprise ghouls who froth over web apps and "single pane of glass" bs demanding these boxes be ticked
<psykose> the more features you use the better as they say
<j`ey> :'(
<chadmed> your use case is nifty!
<j`ey> :3
leitao has joined #asahi
<stintel> cool. have to try that next time I use my pinecil
tano70_Air has quit [Quit: Xchat Azure 1.8.11]
bgb has quit [Quit: WeeChat 4.0.5]
systwi has joined #asahi
dcow has joined #asahi
<kidplayer666> Hey there, is this bug known? (I’m on fedora) https://usercontent.irccloud-cdn.com/file/j0Mj9fbd/IMG_2842.mp4
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
chadmed has quit [Remote host closed the connection]
chadmed has joined #asahi
Yannik_Sc has joined #asahi
dcow has joined #asahi
ward_ has joined #asahi
<ward_> hey guys, how do you do?
<ward_> is it still recommended to wait for the final release of the fedora remix before installing asahi?
<ward_> since the original release plan was for august, and it is october now, do you know if there is a updated roadmap? thanks and have a nice day! :)
Yannik_Sc has quit [Remote host closed the connection]
Sellerie5 has joined #asahi
Yannik_Sc has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
<j`ey> ward_: it;s fine to install now!
Yannik_Sc has quit [Ping timeout: 480 seconds]
<ward_> thx i know, but i do not want to reinstall after the official release ... :(
<ward_> it also says "Adventurous users can try out the Fedora Asahi Remix today, but please expect rough spots (or even complete breakage). We’re still very much in the process of integrating everything and a bunch of new features are coming, and things are expected to break while we get everything in shape. Please keep that in mind if you choose to try it ahead of time." on the website
<ward_> feeling not that adventurous :D
<ellyq> i mean, worst-case scenario you back your /home up, maybe /etc, dnf list --installed > packages_pre.log, reinstall, slap your home, configs back in place, diff packages with fresh install, install them... and off you go
dcow has joined #asahi
<ChaosPrincess> id even say that reinstalls are unlikely, more likely is that you will need to be careful with updating, and you may end up having to do some annoying firmware wrangling for some new features to work
dcow has quit [Ping timeout: 480 seconds]
<ward_> thx, but i think i can circumvent all that by waiting for final release? :) or will this stuff be true even after the "real" release?
<ward_> i never used fedora, do you have to much stuff manually when updating, like with archlinux?
<ellyq> been using it for about a decade, there's a reason why i've got `alias update="sudo dnf update --refresh -y` :P
<kujeger> been using it for ages as well, I can't really remember any update problem ever
<ellyq> yep, on one of my systems I went trough multiple upgrades too (from 23 up to 34, when I decommisioned it)
eiln has joined #asahi
<eiln> ward_: I think that was in reference to firmware (e.g. touchbar, camera calibration) not in the installer earlier. those you can't get with a simple linux update
<ward_> ok thx for your support!
<j`ey> I think the official release is going to come after F39
<ward_> since i dont need asahi *NOW*, i think i can wait for the final relase :) but because i am really interested, so i just wanted to ask if there is a update to the roadmap :D
<ward_> j`ey: ah ok, that makes sense! is the asahi stuff based on f38 now or 39 already?
<j`ey> there's 38 39 rawhide branches
<j`ey> "we're not planning to GA F38, fwiw
<j`ey> "
<j`ey> that's a quote from one of the fedora SIG members
<ward_> what does GA mean?
<j`ey> General Availability
<j`ey> aka release
<ward_> is asahi not finished with integrating into fedora yet? could this be the cause of problems if i install now? or is it already finished and the problem is of new hardware support, e.g. new drivers with need other firmware or something, and this could create problems in the future? because the installer does not provide it yet from macos or something?
<ward_> j`ey: ok thx, so they started working on f38 but wont release that, only with f39 right?
<ward_> stintel: thx! :)
<j`ey> ward_: yes
<ward_> so is current asahi fedora still f38?
<ellyq> judging from my experience (not with Asahi in particular), it's mostly about firmware and upstreaming
<j`ey> ward_: you can install f39 now too
<ward_> then i will just wait until f39 releases and install asahi now, i guess that will cause fewer problems then? because i dont need to upgrade?
<j`ey> ward_: the current fedora packages dont package the wifi fw for some machines and the webcam fw
<ellyq> doesn't really matter in all honesty
<ward_> or does fedora asahi to rebase first to f39, and it is not automatically? if i install f38 remix now, can i just uprade to f39, or does asahi first need to update stuff for it to work for drivers and stuff?
<ward_> j`ey: oh ok, so current images are already based on f39?
<j`ey> no
<j`ey> you can choose f38 or f39
<j`ey> theres multiple images
dcow has joined #asahi
<ward_> within the asahi installer?
<ward_> you dont install from a CD image right?
<j`ey> within the fedora-asahi-reminx installer, yup
<j`ey> nope, no CD
bgb has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
Yannik_Sc has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
pjakobsson has joined #asahi
<kidplayer666> ward_: Any bugs you might find are probably due to missing or somewhat buggy drivers, probably not fault of bad integration with a particular distro
<kidplayer666> Only reason why any distro won’t work just like that is because there’s some drivers that can’t be upstreamed to the usual kernel
dcow has joined #asahi
<kidplayer666> And so we need a custom kernel that only ships in this specific distro
<kidplayer666> But there’s plenty of more adventurous asahi users
<kidplayer666> That compile their own kernels
<kidplayer666> To use their favourite distro
tirr has quit [Quit: ZNC 1.8.2 - https://znc.in]
tirr has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
jjanzic has quit [Ping timeout: 480 seconds]
leitao has joined #asahi
Moprius has joined #asahi
Yannik_Sc has quit [Remote host closed the connection]
jjanzic has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
sefidel has quit [Remote host closed the connection]
sefidel has joined #asahi
DannyB has joined #asahi
hightower3 has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
cuiltb^ has quit [Ping timeout: 480 seconds]
dcow has quit [Ping timeout: 480 seconds]
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi
AnuthaDev has joined #asahi
jeisom has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dcow has joined #asahi
leitao has joined #asahi
leitao has quit []
leitao has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
hex-spell has joined #asahi
hex-spell has quit []
hex-spell has joined #asahi
hex-spell has quit []
hex-spell has joined #asahi
slp_ is now known as slp
dcow has joined #asahi
<cy8aer> I swap to #asahi for the camera thing: I now looked at the difference of Firefox/macOS and Firefox/asahi: https://webcamtests.com/resolution shows VGA, HD, and FHD on macOS but only FHD on Asahi. Is that right?
<cy8aer> I guess this is the point why some applications and web applications fail?
dcow has quit [Ping timeout: 480 seconds]
Enzime has left #asahi [#asahi]
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
ten15723774324 has quit [Remote host closed the connection]
ten15723774324 has joined #asahi
cylm has joined #asahi
<DannyB> @cy8aer: Are you asking what resolutions are supported by the camera under linux vs macos? If so, what model mac are you using?
Moprius has quit [Quit: bye]
<cy8aer> I have a mbp14 with m1pro (t6000). And yes what can be done to have the resolutions from macos in linux. Probably there is something missing in the actual kernel module or so?
<DannyB> @cy8aer: (at least in the epxerimental camera support on m2, it supports 480, 720p, 1280x960, 1080p, 1920x1440 in asahi, i have not tried an m1 or a non-experimental branch)
<DannyB> ah, not tried an m1pro
<DannyB> but i would be surprised if it didn't support what the underlying camera supports
<cy8aer> Because especially in jitsi 720p is standard and max limit and the mbpro only has 1080p. You can manipulate the server itself, but then it would not work with any standard server setting. VGA and HD are missing on the linux side.
<cy8aer> For m2 this would work (you listed 720p).
<cy8aer> And I guess that there is some bug in the actual module.
cuiltb^ has joined #asahi
<DannyB> AFAICT - the allowed resolutions are controlled by the sensor-preset dictionary in the DTB
<DannyB> So if you don't see a resolution you should
<DannyB> it should suffice to simply add it to the dtb
<DannyB> yes, was just about the link that
<DannyB> the imx248 presets (which i assume is what m1 is) only list 720 in the dtb by default
<DannyB> if you add the other presets to the dtb and recompile (and update m1n1, etc) i presume it will now list those other resolutions for you
<j`ey> some m2 seem to have imx248 too
<DannyB> the module does not in fact care what presets are listed, all are in the same format
<DannyB> ie it doesn't do anything special for any preset vs any other
<DannyB> like change video format, or whatever
<DannyB> so it'll either wokr, or crash horribly
<j`ey> "Apple MacBook Pro (13-inch, M2, 2022)"
<DannyB> depending on whether the lower resolutions happen to be in a different image format
<DannyB> on that sensor
<DannyB> (I doubt it, but who knows)
<j`ey> I think that's the one that's M2 in the same chasis as the M1 Pro, so thats maybe why the same sensor as M1
<DannyB> all it does is report whatever is in the preset dictionary to v4l2, assuming all image formats are NV12
<DannyB> ;)
<DannyB> So there is nothing wrong with the actual module that is preventing support for the other resolutions
<DannyB> and it should require nothing but some dtb changes and a reboot
dcow has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
leitao has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
cuiltb^ has quit [Ping timeout: 480 seconds]
cuiltb^ has joined #asahi
ten15723774324 has quit [Remote host closed the connection]
ten15723774324 has joined #asahi
<hex-spell> hey! newb here, I was wondering if there was a roadmap to understand how asahi works or how it's been made
<hex-spell> I'm still learning about hardware and OS's, but I'd like to focus my learning so I can start contributing to these kind of projects
lena6 has joined #asahi
<dylanchapell> hex-spell: The wiki is the place to learn. Check out the platform documentation and the Project:References https://github.com/AsahiLinux/docs/wiki#developers
DannyB has quit [Ping timeout: 480 seconds]
<j`ey> also watching some of the first markan streams on yt
<hex-spell> ty!!
jacksonchen666 has joined #asahi
dcow has joined #asahi
jacksonchen666 is now known as Guest2389
jacksonchen666 has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tenkuu has joined #asahi
Guest2389 has quit [Ping timeout: 480 seconds]
leitao has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
cuiltb^ has quit [Read error: Connection reset by peer]
cuiltb^ has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
dcow has joined #asahi
leitao has joined #asahi
ten15723774324 has quit [Remote host closed the connection]
ten15723774324 has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
nela has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
basso2 has joined #asahi
leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
compassion1785 has quit [Quit: lounge quit]
dcow has quit [Ping timeout: 480 seconds]
rootbeerdan has joined #asahi
dcow has joined #asahi
compassion1785 has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
ydalton has joined #asahi
<ydalton> tried the fruit of slp's krunvm work, i'm assuming i need his version of mesa for the whole thing to work? or at least wait til his MR is created and merged
<ydalton> would be lovely to run x86 linux applications and windows programs again
<j`ey> ydalton: did yo read the blog/instructions?
<ydalton> yes, i did everything (except for perhaps installing his fork of mesa)
<ydalton> so i assume i have to do that right?
<j`ey> hm yeah, does seem like the steps miss that out
<ydalton> i can start the vm, but as soon as i launch a graphical application, it complains it can't "open the virtio-gpu device for asahi native context", and then Xwayland throws a hissy fit and crashes the vm
<j`ey> "Error opening virtio-gpu device for Asahi native context" that?
<ydalton> yes
<j`ey> if so, you have his mesa
<ydalton> and then some out of memory stuff
<ydalton> j`ey: wait, what?
<ydalton> interesting, but why is it crashing?
ydalton has quit [Remote host closed the connection]
ydalton has joined #asahi
<ydalton> it doesn't make sense, i didn't explicitly install his fork of mesa?
dcow has joined #asahi
<ydalton> normally my mesa version is the standard one from fedora asahi?
<ydalton> wait
nela has joined #asahi
<ydalton> maybe that's the mesa in the VM, not my host's mesa
<j`ey> hm, I thought that it needed host support, but I haven't looked into any details!
<slp> ydalton: you don't need to upgrade Mesa on the host, and the "asahi-krun" OCI image already ships with the version including native context support.
<slp> ydalton: have you tried running glmark2 in the microvm? does it work?
<ydalton> nope, Xwayland crashes and takes the VM with it
<ydalton> does it matter what device i'm running it on? afaik you've only had an m1 macbook air to test it on
<j`ey> slp: so the native thing in mesa knows how to forward stuff?
<nightstrike> PaulFertser_: thanks!
<slp> j`ey: yes, from the host's perspective it's a regular EGL/DRM client
<j`ey> slp: neat!
<slp> ydalton: I don't think there's anything specific about the device model but could be wrong. Could you please paste your terminal output somewhere?
<ydalton> maybe unrelated, but i cannot ping within the vm
<ydalton> it says "socket: Address family not supported by protocol"
<ydalton> is this normal?
<slp> ydalton: that network error is a good hint. I'm pretty sure your system doesn't have the krunvm/libkrun/libkrunvm packages from the COPR repo.
<slp> ydalton: because that network error comes from the TSI network model, while the packages in the COPR repo use virtio-net
<ydalton> doesn't look like it
<ydalton> am i missing an extra package or something?
<ydalton> wait, but i can curl within the VM?
<slp> ydalton: yes, that's the magic of TSI, you can curl without a network interface :-)
<ydalton> whaaa
<slp> ydalton: what I don't understand is why are you getting TSI with those packages
<slp> ydalton: I don't suppose there's any change you have installed libkrun or krunvm from sources anytime?
<slp> s/change/chance/g
<ydalton> before this all came out i did
<slp> could you have some leftovers? what does "which krunvm" and "ldd /usr/bin/krunvm" tell you?
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
<ydalton> and krunvm is indeed /usr/bin/krunvm
<ydalton> wait, i will remove the krunvm packages and see if there are remainders
<ydalton> aha! i found something
<ydalton> now i will reinstall the packages
<ydalton> nope, same error
<slp> ydalton: let me do a fresh install here in case I messed up the COPR repo somehow
dcow has quit [Ping timeout: 480 seconds]
<ydalton> do you know how many people have tested it?
penguwin has joined #asahi
<ydalton> hold on, the packages i have here are from a while ago?
ten15723774324 has quit [Remote host closed the connection]
ten15723774324 has joined #asahi
dcow has joined #asahi
Moprius has joined #asahi
<slp> ydalton: you're the first I'm aware of
<slp> with "krunvm -V" you get "krunvm 0.2.4"?
<ydalton> yes, that's correct
<ydalton> were you able to reproduce my issue?
dcow has quit [Ping timeout: 480 seconds]
<slp> ydalton: nope, works fine, and now I remember someone from the Fedora Asahi channel on Matrix got it working
<slp> wait, we were following the wrong path...
<slp> looking again at your first screenshot, it looks like you don't have DRM native context support in virglrenderer
<slp> could you check which virglrenderer package do you have installed in your host?
<ydalton> i installed the virgl package from the copr
<ydalton> how can i verify the shared library is the correct one?
<ydalton> -rwxr-xr-x. 1 root root 739328 Jan 21 2023 /lib64/libvirglrenderer.so.1.8.8
<ydalton> that does not make any sense?
dcow has joined #asahi
<ydalton> i ran strings on that shared library, and it does contain references to asahi so i think that's the right one
flokli has quit [Quit: WeeChat 4.0.2]
flokli has joined #asahi
<slp> ydalton: nah, the binaries look fine, must be something else...
<slp> how much memory and cpus have you given to the VM?
<ydalton> i gave 2 cpus and 5GB
<ydalton> wait, i will change the core count
<ydalton> nope, nothing
<ydalton> and it still does not explain the no pinging situation
cyrinux has quit [Quit: bye]
cyrinux has joined #asahi
tenkuu has quit [Read error: No route to host]
tenkuu has joined #asahi
<ydalton> i'd like to run strace on trying to run glmark2
<slp> ydalton: that's be nice, I'd like to see why that mmap is failing
<ydalton> i'll need to install strace in the vm somehow
tenkuu_ has joined #asahi
<slp> ydalton: start the VM as "krunvm start VMNAME /bin/bash"
<slp> that'll get you root, then run dhclient to configure network
<slp> you should be able to install packages right away
<ydalton> huh
<ydalton> and now i can ping?
<ydalton> is it normal it complains about init not running? it's always been complaining about that
tenkuu has quit [Read error: Connection reset by peer]
<slp> ydalton: no, that's not normal... looks like a problem with the image in Quay, let me check
<ydalton> i dumped an strace of glmark2... the first error with "failed to map handle: Invalid argument" does not appear for some reason
<ydalton> oh, i did find it
dcow has quit [Ping timeout: 480 seconds]
<ydalton> 19:06:08.932836 mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0x10027f000) = -1 EINVAL (Invalid argument)
<ydalton> i assume this is the mmap that failed
dcow has joined #asahi
PaulFertser_ is now known as PaulFertser
dcow has quit [Ping timeout: 480 seconds]
ydalton has quit [Remote host closed the connection]
ydalton has joined #asahi
ydalton has quit []
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
<slp> turns out that, at the moment, this is only working on Plasma. With GNOME you get that "failed to map handle" error. This is kind of funny... ;-P
ydalton has joined #asahi
ydalton has left #asahi [#asahi]
ydalton has joined #asahi
<ydalton> oh my god... how could this be DE aware
ydalton has quit [Remote host closed the connection]
ydalton has joined #asahi
<ydalton> i launched weston and ran krunvm there, and it worked perfectly
<ydalton> what could be missing in gnome that weston has?
ydalton has quit []
<ward_> very cool, i hope this improves the gaming stuff lina did :)
<ward_> also that new vm direct gpu gaming stuff hopefully? :)
luix has joined #asahi
maximbaz has quit [Quit: bye]
<kidplayer_666> Hey there yal
<kidplayer_666> yall
<kidplayer_666> just tried slp's guide
<kidplayer_666> this happened
maximbaz has joined #asahi
ydalton has joined #asahi
<j`ey> kidplayer_666: if thats GNOME, looks like it doesnt work there currently
<ydalton> slp: when i do glmark2 i get ~8000fps but the cpu ramps up to max
<j`ey> see above ^
<ydalton> j`ey: that's a completely different error than i got
<ydalton> can you install weston and try it there? that worked for me
<kidplayer_666> only kde?
<ydalton> i got it working in weston so
luix has quit [Remote host closed the connection]
<ydalton> nice, on the terrain benchmark i get 327fps
dcow has joined #asahi
ydalton has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.0.92)]
ydalton has joined #asahi
<ydalton> well, i think that's enough for today, i think i'm gonna go to sleep :P
ydalton has quit [Remote host closed the connection]
Moprius has quit [Quit: bye]
dcow has quit [Ping timeout: 480 seconds]
mps has left #asahi [#asahi]
jeisom has quit [Quit: Leaving]
dcow has joined #asahi
<kidplayer666> slp: it’s with great pride that after doing ydalton’s trickery
<kidplayer666> I announce that I got glmark2 running
<kidplayer666> With a score of 298 fps (13” MacBook Pro normal m1)
milky62772 has joined #asahi
<milky62772> My machine turned off while updating the kernel and now /boot/vmzlinuz-linux-asahi-edge is not being found
hightower2 has joined #asahi
<milky62772> How could I possible solve this? Any help would be really appreciated
dcow has quit [Ping timeout: 480 seconds]
<milky62772> I know I can't chroot into the system and reinstall the kernel
<janneg> milky62772: is /boot/vmzlinuz-linux-asahi still there? any idea why it turned off? which machine?
<milky62772> M1 pro, yes, the battery ran out just as it was updating the kernel
<milky62772> Really bad timing
<ChaosPrincess> is asahi-wip branch supposed to work rn? i have latest m1n1, latest u-boot, dtbs from asahi-wip, with jannau's dts fixes merged, u-boot fails to boot anything, first complaining that it can't reserve memory, then crashing when trying to boot efi
<ChaosPrincess> machine is j314s
<janneg> did I break something? asahi-6.5-8 boots fine on j493, my fixes dts worked on j473 (m2 mini)
<ChaosPrincess> j493 doesnt have isp
<ChaosPrincess> well, it doesnt work without your fixes either :P, the current wip tree does not include them and so i tried both wip as-is and manually merging those
<janneg> j493 has, j473 hasn't. I'm actually testing asahi-wip + bits/000-devicetree merged on j493
<ChaosPrincess> i am testing both -wip and -wip+bits, on j314s, u-boot doesnt feel like booting on that
dcow has joined #asahi
<janneg> ah, forgot u-boot again. just testing m1n1 with linux payload on j493
<ChaosPrincess> yea, i am booting with u-boot
ChaosPrincess has quit [Quit: ChaosPrincess]
leahcl has quit [Remote host closed the connection]
leahcl has joined #asahi
ChaosPrincess has joined #asahi
<janneg> asahi linux (alarm) with I think 6.5-8 seems busted on j314c
<janneg> no, that still 6.5-3
dcow has quit [Ping timeout: 480 seconds]
<ChaosPrincess> is it possible to somehow dump the adt after the code in kboot.c finishes doing it's stuff to it? maybe some no-maps are missing
<ChaosPrincess> s/adt/dts/
<janneg> u-boot can display it
<janneg> s/display/print/
ChaosPri1 has joined #asahi
ChaosPrincess has left #asahi [#asahi]
ChaosPri1 has quit []
ChaosPrincess has joined #asahi
mspe has quit [Quit: WeeChat 3.8]
mspe has joined #asahi
<ChaosPrincess> janneg: which errors are you getting? in my case its this: https://paste.bingner.com/paste/rbtdx
dcow has joined #asahi
<janneg> ChaosPrincess: unrelated, I forgot to update fstab aafter moving stuff around and I've only booted alarm via chainload/run_guest
<ChaosPrincess> so, w/o u-boot?
<janneg> no, fater fixing fstab to point at the correct PARTUUID everything seems to work
dcow has quit [Ping timeout: 480 seconds]
dcow has joined #asahi
<janneg> still using uboot-asahi-2023.04.asahi2-1 though. "2023.07.02-01799-g46d6873a24" sounds a little suspicios
Misthios has quit [Quit: Misthios]
<janneg> ah, that's "asahi". can you try with asahi-releng
dcow has quit [Ping timeout: 480 seconds]
<ChaosPrincess> tried to boot with linux.py in the meantime - works, the problem seems to be defenitely in u-boot, will try releng shortly
<janneg> ChaosPrincess: do you have any output from m1n1?
<ChaosPrincess> all the normal spam, yes
<janneg> I don't see anything relevant in the diff between asahi/asahi-releng and asahi/asahi
<ChaosPrincess> yep, same story, "failed to allocate"
<janneg> I also don't understand why u-boot would want to allocate 2 times 1GB
<ChaosPrincess> for the kernel
<ChaosPrincess> idk why two times though
<janneg> do you get to the u-boot prompt? iff yes have you looked at the device tree?
<ChaosPrincess> aye to both, dtb looks okay-ish
<slp> kidplayer666: upgrading to the latest sommelier package *in the VM* should fix the problem for GNOME. 1) krunvm start VMNAME /bin/bash 2) dhclient 3) dnf upgrade -y --refresh sommelier
<ChaosPrincess> https://paste.bingner.com/paste/r8kgw - logs from looking at dtb
<janneg> the error message is in lib/lmb.c looks like there's an issue with memory accounting in u-boot
<janneg> ChaosPrincess: `fdt print /reserved-memory` would print the whole /reserved-memory subtree
<ChaosPrincess> thats useful
<janneg> waht does `fdt rsvmem print` output?
kidplayer_666 has quit [Quit: Connection closed for inactivity]
crabbedhaloablut has quit []
<janneg> nothing unexpected
<janneg> that 'below 0x0' seems not worrysome. that is just LMB_ALLOC_ANYWHERE
<janneg> I remember one u-boot issue. allocations would fail if some things were not page aligned
DannyB has joined #asahi
dcow has joined #asahi
dcow has quit [Ping timeout: 480 seconds]
AnuthaDev has quit []
tenkuu_ has quit [Ping timeout: 480 seconds]
tenkuu has joined #asahi
DannyB has quit [Ping timeout: 480 seconds]