#
…

2023-09-02

00:17utsweetyfish has quit [Remote host closed the connection]
00:17utsweetyfish has joined #asahi-alt
01:53jeisom has joined #asahi-alt
02:02hightower3 has joined #asahi-alt
02:09hightower4 has quit [Ping timeout: 480 seconds]
02:12jeisom has quit [Ping timeout: 480 seconds]
03:05utsweetyfish has quit [Remote host closed the connection]
03:06utsweetyfish has joined #asahi-alt
03:31utsweetyfish has quit [Remote host closed the connection]
03:31utsweetyfish has joined #asahi-alt
04:01sefidel has quit [Remote host closed the connection]
04:02sefidel has joined #asahi-alt
05:27chadmedhm so the gentoo livecd does _not_ like the fedora kernel very much
05:28chadmedmain issues are fedora's dracut firmware module not working (easily worked around) and something funky with the wifi chipset and how the kernel deals with its firmware
05:28chadmedthat one is not so easy to work around
05:29chadmedgood news is that with a usb-c rtl8169 thing the actual install went totally fine after that
05:29chadmedwe will need to ship a default .config now though as we can't rely on the fedora kernel's it seems
05:34utsweetyfish has quit [Remote host closed the connection]
05:34utsweetyfish has joined #asahi-alt
05:49jannaumaybe we should look now into how hard it is to repack or rebuild the livecd?
05:49chadmedill have more time once uni finishes, im on 12+ hour days between work and study at the moment
05:50chadmedbut yeah, i think its time to look at a proper live booting thing
05:53jannauit might be enough to use an asahi kernel and an "overlay" initrd for kernel modules and firmware
06:28utsweetyfish has quit [Remote host closed the connection]
06:28utsweetyfish has joined #asahi-alt
07:21stipa has joined #asahi-alt
07:22jacksonchen666 has joined #asahi-alt
07:43utsweetyfish has quit [Remote host closed the connection]
07:43utsweetyfish has joined #asahi-alt
08:46cy8aermps: This looks good for me except: the standard macos tar needs "-" - " tar -xf ..." or is there a way to install a standard tar with brew?
08:47mpscy8aer: macos have bsdtar by default. but it worked fine for me
08:47mpsI think it is possible to install gnu tar with brew though didn't tried
08:47cy8aernice peace of work and tricky 😉
08:48mpsI forgot to add that qemu should be run as root
08:48cy8aerhm, yes, of course...
08:49mpslater I will create alpine VM disk image with more tools added than those minimal on iso virt image
08:51mpswhat is default shell on macos nowadays?
09:16utsweetyfish has quit [Remote host closed the connection]
09:16utsweetyfish has joined #asahi-alt
10:07mpslooks like it is
10:10jacksonchen666 has quit [Remote host closed the connection]
10:15jacksonchen666 has joined #asahi-alt
10:47kdb424 has quit [Quit: The Lounge - https://thelounge.chat]
10:47kdb424 has joined #asahi-alt
10:50jacksonchen666 has quit [Remote host closed the connection]
10:55jacksonchen666 has joined #asahi-alt
12:10cy8aerThat is a problem if people write scripts cross system: "/bin/sh" is zsh in macos, but e. g. in debian it is dash - a very small shell with a limited set of functions.
12:10sam_the default user shell is not the same as /bin/sh
12:10sam_i doubt apple would make a non-posix shell /bin/sh
12:10sam_on macos it is still bash
12:11jeisom has joined #asahi-alt
12:13chadmedapple take pride in (or at least used to) being POSIX and SUS certified
12:14chadmedsh will always be a posix shell
12:14sam_indeed
12:15possiblemeatball has joined #asahi-alt
12:25lynndotpy has quit [Quit: bye bye]
12:25lynndotpy has joined #asahi-alt
12:40possiblemeatball has quit [Quit: Quit]
12:42mpsbash is not posix compliant afaik (didn't used bash for decades)
12:43sam_you know what i mean
12:43sam_it's capable of executing posix scripts, it still supports a superset
12:44mpslast time I posted commit to u-boot it was related to shell and I saw that bash can run posix shell but I didn't tested other cases
12:45mpsso yes, I understand and expect bash can run posix scripts but didn't tested, and I trust you it is ok
13:27utsweetyfish has quit [Remote host closed the connection]
13:27utsweetyfish has joined #asahi-alt
14:25cylm has joined #asahi-alt
15:07chadmed has quit [Read error: Connection reset by peer]
15:08possiblemeatball has joined #asahi-alt
15:08chadmed has joined #asahi-alt
15:25possiblemeatball has quit [Quit: Quit]
15:46cylm_ has joined #asahi-alt
15:55utsweetyfish has quit [Remote host closed the connection]
15:55cylm_ has quit [Quit: WeeChat 4.0.0]
15:56utsweetyfish has joined #asahi-alt
15:56chadmed has quit [Read error: Connection reset by peer]
15:57chadmed has joined #asahi-alt
17:26jacksonchen666 has quit [Remote host closed the connection]
17:40jeisom has quit [Ping timeout: 480 seconds]
17:50utsweetyfish has quit [Remote host closed the connection]
17:50utsweetyfish has joined #asahi-alt
18:13chadmed has quit [Ping timeout: 480 seconds]
18:15jacksonchen666 has joined #asahi-alt
18:38chadmed has joined #asahi-alt
19:52jeisom has joined #asahi-alt
19:55zerdox_ has joined #asahi-alt
19:58zerdox_anyone tried upgrading to latest mesa? today i tried pre20230821 and it hyprland won't start, asks to enable software rendering. rolling back to pre20230812 fixes the issue
20:01zerdox_running latest kernel from overlay
20:03zerdox has joined #asahi-alt
20:13jannauzerdox: if your kernel is compatible with mesa-pre20230812, it won't be compatible with current mesa
20:14zerdox_jannau: hmm.. let me double check please
20:14jannauasahi-sources-6.4.0_p9 and mesa-23.2.0_pre20230821 had an uapi bump and you'll need both if you install any newer version
20:16zerdox_usr/src/linux pointing to 6.4.0_p9 which is latest
20:17zerdox_somehow I am running previous drivers...
20:19zerdox_jannau: i am not really sure, do i need to recompile wayland or wm or any other stuff when getting new drivers especially on big updates like this?
20:20jacksonchen666 has quit [Ping timeout: 480 seconds]
20:22jannauno need to recompile anything but you have to reboots after updating kernel and mesa. `uname -a` should tell you which kernel you're running
20:23zerdox_oh.. i can't imagine i made this mistake again. i upgraded kernel sources package but forgot to compile it and update grub and m1n1
20:24zerdox_that's probably because i still can't get used to gentoo in all aspects. do you have any advices how this process can be automated?
20:28jannauno, I do that manually. someone is working on asahi-kernel though which should automate at least parts of it. there's a merge request in the overlay repo
20:29zerdoxthank you :)
20:34jacksonchen666 has joined #asahi-alt
20:34chadmed has quit [Quit: Konversation terminated!]
20:34chadmed has joined #asahi-alt
20:54zerdox_ has quit [Remote host closed the connection]
21:17utsweetyfish has quit [Remote host closed the connection]
21:17utsweetyfish has joined #asahi-alt
21:19zerdoxjannau: for some reason i still could not make it start.. uname -a now gives 9 version instead of 6, and i installed latest mesa
21:20zerdoxmaybe there are some use flags i need to set? except asahi video of course. i hope i am missing that kind of thing
21:31zerdoxsorry for my noob questions. hope everything is resolved now because i found that rust was disabled in kernel. i cannot understand how this happed again, because i was copying old config which was already on my system
21:32zerdoxthis is my second upgrade and second time i am here with the same issues. sorry :) now i definitely learned a lesson
21:38mpsah, new kernel and mesa today
21:46cylm_ has joined #asahi-alt
21:52cylm has quit [Ping timeout: 480 seconds]
22:17zerdox_ has joined #asahi-alt
23:03zerdox_ has quit [Remote host closed the connection]
23:30chadmed has quit [Ping timeout: 480 seconds]
23:37ellyq has joined #asahi-alt
23:45utsweetyfish has quit [Remote host closed the connection]
23:45utsweetyfish has joined #asahi-alt
23:57utsweetyfish has quit [Remote host closed the connection]
23:57utsweetyfish has joined #asahi-alt
…