#
…

2023-10-06

00:00Moprius has quit [Quit: bye]
00:14dcow has joined #asahi
00:22dcow has quit [Ping timeout: 480 seconds]
00:41nightstrikechadmed: 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
00:55dcow has joined #asahi
01:06dcow has quit [Ping timeout: 480 seconds]
01:10eiln has quit [Ping timeout: 480 seconds]
01:34dcow has joined #asahi
01:42dcow has quit [Ping timeout: 480 seconds]
01:55amarioguy has quit [Remote host closed the connection]
02:00gabuscus has quit []
02:08dcow has joined #asahi
02:16dcow has quit [Ping timeout: 480 seconds]
02:38gabuscus has joined #asahi
02:40dcow has joined #asahi
02:41crabbedhaloablut has joined #asahi
02:48dcow has quit [Ping timeout: 480 seconds]
02:58dcow has joined #asahi
03:01skipwich has quit [Quit: DISCONNECT]
03:02skipwich has joined #asahi
03:08dcow has quit [Ping timeout: 480 seconds]
03:19jeisom has quit [Quit: Leaving]
03:24marvin24 has joined #asahi
03:27marvin24_ has quit [Ping timeout: 480 seconds]
04:22ten157237743247 has joined #asahi
04:22ten15723774324 has quit [Remote host closed the connection]
05:15mspe has quit [Quit: WeeChat 3.8]
05:15mspe has joined #asahi
05:16mspe has quit []
05:18mspe has joined #asahi
05:47systwi has quit [Ping timeout: 480 seconds]
06:30dcow has joined #asahi
06:38dcow has quit [Ping timeout: 480 seconds]
06:43slp_ has joined #asahi
06:54toasterking has left #asahi [#asahi]
06:54kaazoo has joined #asahi
07:01dcow has joined #asahi
07:08Yannik_Sc has joined #asahi
07:09dcow has quit [Ping timeout: 480 seconds]
07:10rvalue has quit [Read error: Connection reset by peer]
07:10rvalue has joined #asahi
07:30dcow has joined #asahi
07:40dcow has quit [Ping timeout: 480 seconds]
07:44Yannik_Sc has quit [Ping timeout: 480 seconds]
07:50dcow has joined #asahi
07:54PaulFertser_nightstrike: this is the list of USB wifi adapters working reasonably (with upstream drivers in Linux): https://github.com/morrownr/USB-WiFi
07:57Yannik_Sc has joined #asahi
08:02tenkuu has quit [Ping timeout: 480 seconds]
08:05dcow has quit [Ping timeout: 480 seconds]
08:07leitao has joined #asahi
08:08leitao has quit []
08:23j`eychadmed: I would use firefox but chrome has web bluetooth which I ""need""!
08:23jannegbmc4388 (used on all apple devices with wifi 6e) is working now, support might arrive quicker than an order
08:24basso2 has quit [Ping timeout: 480 seconds]
08:27leitao has joined #asahi
08:30Yannik_Sc has quit [Ping timeout: 480 seconds]
08:36leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
08:36dcow has joined #asahi
08:37tano70_Air has joined #asahi
08:44dcow has quit [Ping timeout: 480 seconds]
08:44psykosewhat'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..
08:45j`eymy use case is that I have a timer that connects to a web application
08:45psykosehm, fancy :)
08:45j`eyit used to do it via mic input, and send rs232 signals in via sound
08:45j`eybut that was flakey, and needed a wire!
08:46chadmedpsykose: 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
08:47psykosethe more features you use the better as they say
08:53chadmedyour use case is nifty!
08:56leitao has joined #asahi
08:58stintelcool. have to try that next time I use my pinecil
08:59tano70_Air has quit [Quit: Xchat Azure 1.8.11]
09:05bgb has quit [Quit: WeeChat 4.0.5]
09:11systwi has joined #asahi
09:11dcow has joined #asahi
09:14leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
09:19leitao has joined #asahi
09:21dcow has quit [Ping timeout: 480 seconds]
09:27chadmed has quit [Remote host closed the connection]
09:33chadmed has joined #asahi
09:45Yannik_Sc has joined #asahi
09:47dcow has joined #asahi
09:49ward_ has joined #asahi
09:49ward_hey guys, how do you do?
09:49ward_is it still recommended to wait for the final release of the fedora remix before installing asahi?
09:50ward_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! :)
09:51Yannik_Sc has quit [Remote host closed the connection]
09:53Sellerie5 has joined #asahi
09:55Yannik_Sc has joined #asahi
09:56dcow has quit [Ping timeout: 480 seconds]
10:07j`eyward_: it;s fine to install now!
10:10Yannik_Sc has quit [Ping timeout: 480 seconds]
10:15ward_thx i know, but i do not want to reinstall after the official release ... :(
10:16ward_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
10:16ward_feeling not that adventurous :D
10:19ellyqi 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
10:19dcow has joined #asahi
10:21ChaosPrincessid 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
10:28dcow has quit [Ping timeout: 480 seconds]
10:28ward_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?
10:29ward_i never used fedora, do you have to much stuff manually when updating, like with archlinux?
10:30ellyqbeen using it for about a decade, there's a reason why i've got `alias update="sudo dnf update --refresh -y` :P
10:37kujegerbeen using it for ages as well, I can't really remember any update problem ever
10:38ellyqyep, on one of my systems I went trough multiple upgrades too (from 23 up to 34, when I decommisioned it)
10:38eiln has joined #asahi
10:41eilnward_: 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
10:43ward_ok thx for your support!
10:44j`eyI think the official release is going to come after F39
10:44ward_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
10:45ward_j`ey: ah ok, that makes sense! is the asahi stuff based on f38 now or 39 already?
10:46j`eythere's 38 39 rawhide branches
10:46j`ey"we're not planning to GA F38, fwiw
10:46j`eythat's a quote from one of the fedora SIG members
10:48ward_what does GA mean?
10:49j`eyGeneral Availability
10:49j`eyaka release
10:50ward_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?
10:50ward_j`ey: ok thx, so they started working on f38 but wont release that, only with f39 right?
10:50ward_stintel: thx! :)
10:50j`eyward_: yes
10:51ward_so is current asahi fedora still f38?
10:51ellyqjudging from my experience (not with Asahi in particular), it's mostly about firmware and upstreaming
10:51j`eyward_: you can install f39 now too
10:51ward_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?
10:52j`eyward_: the current fedora packages dont package the wifi fw for some machines and the webcam fw
10:52ellyqdoesn't really matter in all honesty
10:52ward_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?
10:53ward_j`ey: oh ok, so current images are already based on f39?
10:53j`eyyou can choose f38 or f39
10:53j`eytheres multiple images
10:54dcow has joined #asahi
10:56ward_within the asahi installer?
10:56ward_you dont install from a CD image right?
10:57j`eywithin the fedora-asahi-reminx installer, yup
10:57j`eynope, no CD
11:00bgb has joined #asahi
11:02dcow has quit [Ping timeout: 480 seconds]
11:06Yannik_Sc has joined #asahi
11:27leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
11:28pjakobsson has joined #asahi
11:32kidplayer666ward_: Any bugs you might find are probably due to missing or somewhat buggy drivers, probably not fault of bad integration with a particular distro
11:32kidplayer666Only 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
11:33dcow has joined #asahi
11:33kidplayer666And so we need a custom kernel that only ships in this specific distro
11:33kidplayer666But there’s plenty of more adventurous asahi users
11:33kidplayer666That compile their own kernels
11:33kidplayer666To use their favourite distro
11:37tirr has quit [Quit: ZNC 1.8.2 - https://znc.in]
11:37tirr has joined #asahi
11:41dcow has quit [Ping timeout: 480 seconds]
12:08dcow has joined #asahi
12:11jjanzic has quit [Ping timeout: 480 seconds]
12:12leitao has joined #asahi
12:14Moprius has joined #asahi
12:14Yannik_Sc has quit [Remote host closed the connection]
12:20jjanzic has joined #asahi
12:23dcow has quit [Ping timeout: 480 seconds]
12:27sefidel has quit [Remote host closed the connection]
12:28sefidel has joined #asahi
12:49DannyB has joined #asahi
12:52hightower3 has quit [Ping timeout: 480 seconds]
12:53dcow has joined #asahi
12:59cuiltb^ has quit [Ping timeout: 480 seconds]
13:05dcow has quit [Ping timeout: 480 seconds]
13:06leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:13leitao has joined #asahi
13:23AnuthaDev has joined #asahi
13:24jeisom has joined #asahi
13:29leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
13:31dcow has joined #asahi
13:32leitao has joined #asahi
13:37leitao has quit []
13:39leitao has joined #asahi
13:46dcow has quit [Ping timeout: 480 seconds]
13:55hex-spell has joined #asahi
13:56hex-spell has quit []
13:57hex-spell has joined #asahi
13:58hex-spell has quit []
13:58hex-spell has joined #asahi
14:01slp_ is now known as slp
14:10dcow has joined #asahi
14:13cy8aerI 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?
14:14cy8aerI guess this is the point why some applications and web applications fail?
14:23dcow has quit [Ping timeout: 480 seconds]
14:27Enzime has left #asahi [#asahi]
14:46dcow has joined #asahi
14:54dcow has quit [Ping timeout: 480 seconds]
14:57ten15723774324 has quit [Remote host closed the connection]
14:57ten15723774324 has joined #asahi
14:58cylm has joined #asahi
15:07DannyB@cy8aer: Are you asking what resolutions are supported by the camera under linux vs macos? If so, what model mac are you using?
15:07Moprius has quit [Quit: bye]
15:09cy8aerI 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?
15:09DannyB@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)
15:09DannyBah, not tried an m1pro
15:09DannyBbut i would be surprised if it didn't support what the underlying camera supports
15:11cy8aerBecause 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.
15:11cy8aerFor m2 this would work (you listed 720p).
15:13cy8aerAnd I guess that there is some bug in the actual module.
15:13cuiltb^ has joined #asahi
15:13DannyBAFAICT - the allowed resolutions are controlled by the sensor-preset dictionary in the DTB
15:14DannyBSo if you don't see a resolution you should
15:14DannyBit should suffice to simply add it to the dtb
15:14DannyByes, was just about the link that
15:15DannyBthe imx248 presets (which i assume is what m1 is) only list 720 in the dtb by default
15:15DannyBif 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
15:15j`eysome m2 seem to have imx248 too
15:15DannyBthe module does not in fact care what presets are listed, all are in the same format
15:16DannyBie it doesn't do anything special for any preset vs any other
15:16DannyBlike change video format, or whatever
15:16DannyBso it'll either wokr, or crash horribly
15:16j`ey"Apple MacBook Pro (13-inch, M2, 2022)"
15:16DannyBdepending on whether the lower resolutions happen to be in a different image format
15:16DannyBon that sensor
15:16DannyB(I doubt it, but who knows)
15:17j`eyI 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
15:18DannyBall it does is report whatever is in the preset dictionary to v4l2, assuming all image formats are NV12
15:19DannyBSo there is nothing wrong with the actual module that is preventing support for the other resolutions
15:19DannyBand it should require nothing but some dtb changes and a reboot
15:20dcow has joined #asahi
15:22leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:24leitao has joined #asahi
15:28dcow has quit [Ping timeout: 480 seconds]
15:30cuiltb^ has quit [Ping timeout: 480 seconds]
15:30cuiltb^ has joined #asahi
15:34ten15723774324 has quit [Remote host closed the connection]
15:34ten15723774324 has joined #asahi
15:36hex-spellhey! newb here, I was wondering if there was a roadmap to understand how asahi works or how it's been made
15:37hex-spellI'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
15:42lena6 has joined #asahi
15:44dylanchapellhex-spell: The wiki is the place to learn. Check out the platform documentation and the Project:References https://github.com/AsahiLinux/docs/wiki#developers
15:45DannyB has quit [Ping timeout: 480 seconds]
15:49j`eyalso watching some of the first markan streams on yt
15:52jacksonchen666 has joined #asahi
15:52dcow has joined #asahi
15:58jacksonchen666 is now known as Guest2389
15:58jacksonchen666 has joined #asahi
15:59leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:59tenkuu has joined #asahi
16:03Guest2389 has quit [Ping timeout: 480 seconds]
16:03leitao has joined #asahi
16:04dcow has quit [Ping timeout: 480 seconds]
16:08cuiltb^ has quit [Read error: Connection reset by peer]
16:08cuiltb^ has joined #asahi
16:18leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:22dcow has joined #asahi
16:25leitao has joined #asahi
16:27ten15723774324 has quit [Remote host closed the connection]
16:28ten15723774324 has joined #asahi
16:30dcow has quit [Ping timeout: 480 seconds]
16:36nela has quit [Ping timeout: 480 seconds]
16:52dcow has joined #asahi
16:55basso2 has joined #asahi
16:58leitao has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
16:59compassion1785 has quit [Quit: lounge quit]
17:00dcow has quit [Ping timeout: 480 seconds]
17:07rootbeerdan has joined #asahi
17:08dcow has joined #asahi
17:15compassion1785 has joined #asahi
17:20dcow has quit [Ping timeout: 480 seconds]
17:26ydalton has joined #asahi
17:27ydaltontried 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
17:29ydaltonwould be lovely to run x86 linux applications and windows programs again
17:29j`eyydalton: did yo read the blog/instructions?
17:29ydaltonyes, i did everything (except for perhaps installing his fork of mesa)
17:30ydaltonso i assume i have to do that right?
17:33j`eyhm yeah, does seem like the steps miss that out
17:34ydaltoni 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
17:35j`ey"Error opening virtio-gpu device for Asahi native context" that?
17:35j`eyif so, you have his mesa
17:35ydaltonand then some out of memory stuff
17:36ydaltonj`ey: wait, what?
17:37ydaltoninteresting, but why is it crashing?
17:37ydalton has quit [Remote host closed the connection]
17:41ydalton has joined #asahi
17:42ydaltonit doesn't make sense, i didn't explicitly install his fork of mesa?
17:48dcow has joined #asahi
17:49ydaltonnormally my mesa version is the standard one from fedora asahi?
17:51nela has joined #asahi
17:52ydaltonmaybe that's the mesa in the VM, not my host's mesa
17:53j`eyhm, I thought that it needed host support, but I haven't looked into any details!
17:55slpydalton: 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.
17:56slpydalton: have you tried running glmark2 in the microvm? does it work?
17:56ydaltonnope, Xwayland crashes and takes the VM with it
17:56ydaltondoes it matter what device i'm running it on? afaik you've only had an m1 macbook air to test it on
17:56j`eyslp: so the native thing in mesa knows how to forward stuff?
17:59nightstrikePaulFertser_: thanks!
17:59slpj`ey: yes, from the host's perspective it's a regular EGL/DRM client
17:59j`eyslp: neat!
17:59slpydalton: I don't think there's anything specific about the device model but could be wrong. Could you please paste your terminal output somewhere?
18:00ydaltonmaybe unrelated, but i cannot ping within the vm
18:00ydaltonit says "socket: Address family not supported by protocol"
18:00ydaltonis this normal?
18:03slpydalton: 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.
18:03slpydalton: because that network error comes from the TSI network model, while the packages in the COPR repo use virtio-net
18:04ydaltondoesn't look like it
18:04ydaltonam i missing an extra package or something?
18:06ydaltonwait, but i can curl within the VM?
18:09slpydalton: yes, that's the magic of TSI, you can curl without a network interface :-)
18:09slpydalton: what I don't understand is why are you getting TSI with those packages
18:09slpydalton: I don't suppose there's any change you have installed libkrun or krunvm from sources anytime?
18:10slps/change/chance/g
18:10ydaltonbefore this all came out i did
18:11slpcould you have some leftovers? what does "which krunvm" and "ldd /usr/bin/krunvm" tell you?
18:12dcow has quit [Ping timeout: 480 seconds]
18:13dcow has joined #asahi
18:14ydaltonand krunvm is indeed /usr/bin/krunvm
18:16ydaltonwait, i will remove the krunvm packages and see if there are remainders
18:17ydaltonaha! i found something
18:18ydaltonnow i will reinstall the packages
18:20ydaltonnope, same error
18:21slpydalton: let me do a fresh install here in case I messed up the COPR repo somehow
18:22dcow has quit [Ping timeout: 480 seconds]
18:23ydaltondo you know how many people have tested it?
18:24penguwin has joined #asahi
18:28ydaltonhold on, the packages i have here are from a while ago?
18:31ten15723774324 has quit [Remote host closed the connection]
18:31ten15723774324 has joined #asahi
18:31dcow has joined #asahi
18:33Moprius has joined #asahi
18:34slpydalton: you're the first I'm aware of
18:35slpwith "krunvm -V" you get "krunvm 0.2.4"?
18:37ydaltonyes, that's correct
18:38ydaltonwere you able to reproduce my issue?
18:39dcow has quit [Ping timeout: 480 seconds]
18:44slpydalton: nope, works fine, and now I remember someone from the Fedora Asahi channel on Matrix got it working
18:44slpwait, we were following the wrong path...
18:45slplooking again at your first screenshot, it looks like you don't have DRM native context support in virglrenderer
18:45slpcould you check which virglrenderer package do you have installed in your host?
18:46ydaltoni installed the virgl package from the copr
18:47ydaltonhow can i verify the shared library is the correct one?
18:47ydalton-rwxr-xr-x. 1 root root 739328 Jan 21 2023 /lib64/libvirglrenderer.so.1.8.8
18:47ydaltonthat does not make any sense?
18:48dcow has joined #asahi
18:51ydaltoni ran strings on that shared library, and it does contain references to asahi so i think that's the right one
18:52flokli has quit [Quit: WeeChat 4.0.2]
18:52flokli has joined #asahi
18:54slpydalton: nah, the binaries look fine, must be something else...
18:55slphow much memory and cpus have you given to the VM?
18:55ydaltoni gave 2 cpus and 5GB
18:55ydaltonwait, i will change the core count
18:56ydaltonnope, nothing
18:57ydaltonand it still does not explain the no pinging situation
18:58cyrinux has quit [Quit: bye]
18:59cyrinux has joined #asahi
18:59tenkuu has quit [Read error: No route to host]
18:59tenkuu has joined #asahi
19:00ydaltoni'd like to run strace on trying to run glmark2
19:00slpydalton: that's be nice, I'd like to see why that mmap is failing
19:01ydaltoni'll need to install strace in the vm somehow
19:01tenkuu_ has joined #asahi
19:01slpydalton: start the VM as "krunvm start VMNAME /bin/bash"
19:01slpthat'll get you root, then run dhclient to configure network
19:02slpyou should be able to install packages right away
19:02ydaltonand now i can ping?
19:03ydaltonis it normal it complains about init not running? it's always been complaining about that
19:05tenkuu has quit [Read error: Connection reset by peer]
19:07slpydalton: no, that's not normal... looks like a problem with the image in Quay, let me check
19:09ydaltoni dumped an strace of glmark2... the first error with "failed to map handle: Invalid argument" does not appear for some reason
19:09ydaltonoh, i did find it
19:09dcow has quit [Ping timeout: 480 seconds]
19:10ydalton19:06:08.932836 mmap(NULL, 16384, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0x10027f000) = -1 EINVAL (Invalid argument)
19:10ydaltoni assume this is the mmap that failed
19:12dcow has joined #asahi
19:17PaulFertser_ is now known as PaulFertser
19:20dcow has quit [Ping timeout: 480 seconds]
19:25ydalton has quit [Remote host closed the connection]
19:25ydalton has joined #asahi
19:25ydalton has quit []
19:26dcow has joined #asahi
19:38dcow has quit [Ping timeout: 480 seconds]
19:42slpturns 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
19:46ydalton has joined #asahi
19:46ydalton has left #asahi [#asahi]
19:46ydalton has joined #asahi
19:46ydaltonoh my god... how could this be DE aware
19:47ydalton has quit [Remote host closed the connection]
19:48ydalton has joined #asahi
19:49ydaltoni launched weston and ran krunvm there, and it worked perfectly
19:49ydaltonwhat could be missing in gnome that weston has?
19:50ydalton has quit []
19:58ward_very cool, i hope this improves the gaming stuff lina did :)
19:59ward_also that new vm direct gpu gaming stuff hopefully? :)
20:04luix has joined #asahi
20:05maximbaz has quit [Quit: bye]
20:06kidplayer_666Hey there yal
20:07kidplayer_666just tried slp's guide
20:07kidplayer_666this happened
20:07maximbaz has joined #asahi
20:07ydalton has joined #asahi
20:08j`eykidplayer_666: if thats GNOME, looks like it doesnt work there currently
20:08ydaltonslp: when i do glmark2 i get ~8000fps but the cpu ramps up to max
20:08j`eysee above ^
20:09ydaltonj`ey: that's a completely different error than i got
20:09ydaltoncan you install weston and try it there? that worked for me
20:12ydaltoni got it working in weston so
20:16luix has quit [Remote host closed the connection]
20:17ydaltonnice, on the terrain benchmark i get 327fps
20:21dcow has joined #asahi
20:23ydalton has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.0.92)]
20:24ydalton has joined #asahi
20:25ydaltonwell, i think that's enough for today, i think i'm gonna go to sleep :P
20:25ydalton has quit [Remote host closed the connection]
20:28Moprius has quit [Quit: bye]
20:29dcow has quit [Ping timeout: 480 seconds]
20:30mps has left #asahi [#asahi]
20:35jeisom has quit [Quit: Leaving]
20:40dcow has joined #asahi
20:42kidplayer666slp: it’s with great pride that after doing ydalton’s trickery
20:42kidplayer666I announce that I got glmark2 running
20:42kidplayer666With a score of 298 fps (13” MacBook Pro normal m1)
20:45milky62772 has joined #asahi
20:46milky62772My machine turned off while updating the kernel and now /boot/vmzlinuz-linux-asahi-edge is not being found
20:46hightower2 has joined #asahi
20:47milky62772How could I possible solve this? Any help would be really appreciated
20:48dcow has quit [Ping timeout: 480 seconds]
20:54milky62772I know I can't chroot into the system and reinstall the kernel
21:01jannegmilky62772: is /boot/vmzlinuz-linux-asahi still there? any idea why it turned off? which machine?
21:02milky62772M1 pro, yes, the battery ran out just as it was updating the kernel
21:02milky62772Really bad timing
21:07ChaosPrincessis 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
21:08ChaosPrincessmachine is j314s
21:11jannegdid I break something? asahi-6.5-8 boots fine on j493, my fixes dts worked on j473 (m2 mini)
21:12ChaosPrincessj493 doesnt have isp
21:13ChaosPrincesswell, 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
21:14jannegj493 has, j473 hasn't. I'm actually testing asahi-wip + bits/000-devicetree merged on j493
21:15ChaosPrincessi am testing both -wip and -wip+bits, on j314s, u-boot doesnt feel like booting on that
21:15dcow has joined #asahi
21:17jannegah, forgot u-boot again. just testing m1n1 with linux payload on j493
21:17ChaosPrincessyea, i am booting with u-boot
21:17ChaosPrincess has quit [Quit: ChaosPrincess]
21:19leahcl has quit [Remote host closed the connection]
21:19leahcl has joined #asahi
21:20ChaosPrincess has joined #asahi
21:22jannegasahi linux (alarm) with I think 6.5-8 seems busted on j314c
21:23jannegno, that still 6.5-3
21:25dcow has quit [Ping timeout: 480 seconds]
21:25ChaosPrincessis 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
21:25jannegu-boot can display it
21:25jannegs/display/print/
21:26ChaosPri1 has joined #asahi
21:27ChaosPrincess has left #asahi [#asahi]
21:27ChaosPri1 has quit []
21:27ChaosPrincess has joined #asahi
21:33mspe has quit [Quit: WeeChat 3.8]
21:33mspe has joined #asahi
21:39ChaosPrincessjanneg: which errors are you getting? in my case its this: https://paste.bingner.com/paste/rbtdx
21:49dcow has joined #asahi
21:51jannegChaosPrincess: unrelated, I forgot to update fstab aafter moving stuff around and I've only booted alarm via chainload/run_guest
21:51ChaosPrincessso, w/o u-boot?
21:53jannegno, fater fixing fstab to point at the correct PARTUUID everything seems to work
21:57dcow has quit [Ping timeout: 480 seconds]
22:05dcow has joined #asahi
22:07jannegstill using uboot-asahi-2023.04.asahi2-1 though. "2023.07.02-01799-g46d6873a24" sounds a little suspicios
22:09Misthios has quit [Quit: Misthios]
22:09jannegah, that's "asahi". can you try with asahi-releng
22:13dcow has quit [Ping timeout: 480 seconds]
22:18ChaosPrincesstried to boot with linux.py in the meantime - works, the problem seems to be defenitely in u-boot, will try releng shortly
22:18jannegChaosPrincess: do you have any output from m1n1?
22:18ChaosPrincessall the normal spam, yes
22:21jannegI don't see anything relevant in the diff between asahi/asahi-releng and asahi/asahi
22:21ChaosPrincessyep, same story, "failed to allocate"
22:21jannegI also don't understand why u-boot would want to allocate 2 times 1GB
22:22ChaosPrincessfor the kernel
22:22ChaosPrincessidk why two times though
22:25jannegdo you get to the u-boot prompt? iff yes have you looked at the device tree?
22:26ChaosPrincessaye to both, dtb looks okay-ish
22:29slpkidplayer666: 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
22:31jannegthe error message is in lib/lmb.c looks like there's an issue with memory accounting in u-boot
22:32jannegChaosPrincess: `fdt print /reserved-memory` would print the whole /reserved-memory subtree
22:32ChaosPrincessthats useful
22:33jannegwaht does `fdt rsvmem print` output?
22:36kidplayer_666 has quit [Quit: Connection closed for inactivity]
22:53crabbedhaloablut has quit []
22:55jannegnothing unexpected
22:57jannegthat 'below 0x0' seems not worrysome. that is just LMB_ALLOC_ANYWHERE
23:00jannegI remember one u-boot issue. allocations would fail if some things were not page aligned
23:25DannyB has joined #asahi
23:28dcow has joined #asahi
23:36dcow has quit [Ping timeout: 480 seconds]
23:45AnuthaDev has quit []
23:50tenkuu_ has quit [Ping timeout: 480 seconds]
23:52tenkuu has joined #asahi
23:52DannyB has quit [Ping timeout: 480 seconds]
…