#
…

2023-04-07

00:45pthariensflame has quit [Quit: Textual IRC Client: www.textualapp.com]
00:49nsklaus has quit [Quit: ZZZzzz…]
01:41hightower2 has quit [Read error: Connection reset by peer]
01:42hightower2 has joined #asahi-alt
02:10cylm has quit [Ping timeout: 480 seconds]
02:26tobhe has joined #asahi-alt
02:31tobhe_ has quit [Ping timeout: 480 seconds]
02:57jamespmo_ has joined #asahi-alt
03:03jamespmorgan has quit [Ping timeout: 480 seconds]
03:33chadmed has quit [Remote host closed the connection]
03:34chadmed has joined #asahi-alt
03:59jamespmorgan has joined #asahi-alt
04:05jamespmo_ has quit [Ping timeout: 480 seconds]
06:13yuka has quit [Ping timeout: 480 seconds]
06:33yuka has joined #asahi-alt
07:02salimterryli has quit [Quit: ZNC - https://znc.in]
07:03salimterryli has joined #asahi-alt
09:34chadmed has quit [Quit: Konversation terminated!]
09:44chadmed has joined #asahi-alt
10:02nsklaus has joined #asahi-alt
10:51nela has quit [Quit: bye!]
10:51cylm has joined #asahi-alt
10:51nela has joined #asahi-alt
11:49zerdox has joined #asahi-alt
11:52zerdoxchadmed: I am not sure about kernel config files, I guess I did not set up anything of that. Commands you see in pastebin are almost complete.
11:53chadmedinteresting
11:54chadmedbecause i do remember running into similar issues when first developing all that stuff but ive done multiple installs since and havent hit it
11:54chadmedand the only fix i encountered was kernel config related
11:54chadmedvery odd indeed...
11:55zerdoxchadmed: I have no idea how I can run mismatched kernel version in asahi. I upgraded the whole system and rebooted before bootstrapping
11:59zerdoxAm I mounting partitions right? Do I need to do something with /boot? Is it ok to rm -rf whole asahi partition before installing Gentoo?
11:59zerdoxThis is the things I am not sure about cause they are not documented anywhere. When I run install script it says like "make sure your /boot is mounted anywhere you want and efi partition is mounted to /boot/efi. also add it do fstab". This is what I am unsure about
11:59zerdoxFeels like I am just missing something obvious in my installation
12:04chadmedno that should all be fine, theres nothing specific you need to do in that regard
12:04chadmedonly different thing i do is instead of rm -rf / on the asahi partition, i clobber it and make a new one
12:05chadmedits hard to really understand WHAT is causing the error because you have no kernel debug output
12:06chadmedif you have access to /boot somehow (virtualbox can be passed through a pointer to raw block devices on macos hint hint) you can add earlycon and debug to your kernel command line
12:06chadmedand that should at least give us an idea of whats causing the problem
12:06ChaosPrincessdoes your gentoo install do ESP as /boot or separate
12:07chadmedseparate by default because people are used to it, hence mounting the ESP at /boot/efi
12:07chadmedi run ESP as boot on my own machine though and will switch it over to do that once/if asahi does the same
12:09ChaosPrincessYea, if separate, then you need to do tricks
12:10ChaosPrincessi run esp on boot and its just a diskutil mount away
12:10chadmedyeah i had to do some surgery to /boot on my x86 mac in macos today, it was an ordeal :P
12:12chadmedfor context zerdox's issue is the kernel halting with no debug info on first boot
12:13chadmedid be curious to see if the WDT kills the machine after 2 minutes
12:13chadmedif it doesnt then the kernel isnt actually halted and the issue is simpledrm
12:15zerdoxi could wait for 15 minutes and it was hanging as is. if i understood right
12:17chadmedhmm. if the kernel was halted the WDT _should_ reboot the machine after a couple of minutes
12:17chadmedso i think the machine is alive, its just not happy with the firmware framebuffer driver
12:18zerdoxchadmed: my /boot dir is empty except content in /boot/efi. is it really ok?
12:21chadmedno, your kernel and initramfs should be in there
12:21chadmedwhat did you mount to /boot when you installed gentoo?
12:21zerdoxnothing. i created /boot/efi and mounted efi partition here
12:21zerdoxthat what i was saying earlier. I don't think this is the right way
12:22zerdoxyou can check pastebin again to ensure
12:23chadmedyour commands there are fine
12:23chadmedif your /boot is on your root partition then there should be content there. how do you know its empty if you cant access linux?
12:24zerdoxi mean its empty before i run install.sh. and before i run install I don't mount anything to /boot except /boot/efi
12:24chadmedoh right yeah thats fine
12:25zerdoxi could try to debug kernel if i got a bit more information how to do it properly
12:26chadmedwell youd need access to your /boot somehow so you can add kernel command line parameters
12:26zerdoxgrub won't help with it as i remember from that github issue
12:26chadmedif you have access to grub then yeah you can add command line parameters from there
12:27chadmedtake "quiet" out and add "earlycon debug" in its place
12:27zerdoxyes. before choosing gentoo linux i am getting grub loader
12:27zerdoxok. i'll do it rn
12:32zerdoxchadmed: linux params i got by default:
12:32zerdoxlinux /boot/vmlinuz-6.2.0-rc3-asahi-ARCH root=UUID=<my-uuid> ro
12:33zerdoxdo i need to add earlycon degub here? i can't see any quiet here
12:33chadmedadd "earlycon debug" to that
12:33chadmedyeah it should still print something
12:34zerdoxthe difference is that now I got "Booting a command list" on top. everything except this is the same, no useful output
12:34snyanz has joined #asahi-alt
12:35zerdoxI can also upload an image just in case
12:35chadmedif you could yeah
12:39zerdoxi guess booting a command list is just a message from grub. nothing changed in fact
12:39chadmedyeah so the kernel isnt able to write to the fw framebuffer
12:40chadmedis your machine connected with ethernet or wifi
12:40chadmedand did you add sshd to a runlevel before rebooting out of the livecd
12:43zerdoxmy machine is connected to wifi, i share it from my android phone. i did not add sshd to a runlevel before rebooting
12:43chadmedahhhh youre kind of up shit creek then
12:43chadmedlast hope would be sshing into the machine and looking at dmesg
12:43zerdoxi can reinstall again (⁠๑⁠•⁠﹏⁠•⁠)
12:44zerdoxbut i am not sure how this helps. once i exit livecd i dont have any access to os
12:45chadmedone thing that has changed is i have stabilised a newer version of the kernel since the other day
12:46zerdoxi did previous install 2 or 3 days ago i guess. so next time i add ssh and you will take a look?
12:47chadmedno im not sshing into your machine, youd do it yourself from your local network
12:47chadmedi might move the script to do ESP-as-boot by default
12:48chadmedjust so if this shit keeps happening its 1000x easier to play with m1n1/kernels
12:49chadmedits late here so im not ognna do anything tonight but ill make some changes to the script tomorrow and push them
12:49zerdoxi don't really understand the point. in what state of my machine i would ssh to and why. if I can ssh to a machine that it somehow works and i can see everything without ssh. If I get current state (even if i got added sshd) I dont have any access to the OS or even livecd anymore.
12:50chadmedok so remember before i said if the machine had actually crashed then it would have rebooted itself after two mins
12:50chadmedthe fact that its just frozen on that screen means that the kernel _might_ not have actually crashed, and your machine is running fine behind the scenes
12:50chadmedsshing in would confirm this
12:50chadmedand you would be able to get the dmesg log and paste it somewhere for me to look at
12:51zerdoxhm.. i could ssh even without logging in first? if yes, ok then
12:52chadmedyeah ssh spawns a new session on the machine, provided sshd is set to load on boot
12:53zerdoxi can try to do it tomorrow after you push the updates. but i need some help with it, i don't really know how to do it. i guess i also need to enable all services and set config for wpa_supplicant so it would get network connection before i can ssh
12:53zerdoxand i mean i need all this done before i exit livecd
12:55chadmedif you follow the handbook it shows you how to do all this
12:55chadmedbecause its considered a standard install to have all this stuff set
12:56chadmedalso use iwd for wifi its more reliable and supported
12:56chadmedits 2023 society has progressed beyond the need for wpa_supplicant
12:56zerdoxok, thank you. i will try to use it on livecd next time and on arch also
12:57zerdoxi usually drop handbook when it's time to configure kernel, as asahi tutorial on wiki says. so i just reboot after install script
12:58chadmedecho "This script will now exit. Continue setting up your machine as per the"
12:58chadmedecho "Gentoo Handbook, skipping the steps related to setting up the kernel or"
12:58chadmedecho "GRUB as these have been done for you."
12:58chadmedthis might have caused you some problems tbh...
12:59zerdoxthere are some necessary steps?
12:59zerdoxi posted my whole installation process, really. thats almost the full list of commands related to my gentoo installation
13:01chadmedyou need to configure a user, syslog, networking, fs tools, cron, portage options, some system services
13:01chadmedlike i said from the outset, its hard to diagnose and fault find when youre not following the instructions...
13:04snyanz has quit [Quit: Konversation terminated!]
13:06zerdoxwhy do i need to do it when i can do it after booting to gentoo? the only thing i do now is downloading networking tools so i can get online later. second time i tried to install gentoo i also started configuring the system, as you said. i added user, set up networking, fs tools, cron and all that (because second time i was much more confident in what i am doing and i was sure i will get my os). but i also got unbootable and was very disappointed because
13:06zerdoxspent about hour or more to configure the system which i don't have access to and which doesn't affect will I boot or not
13:08chadmedbecause thats how installing gentoo works? youre starting from literally nothing, and by default you get nothing out of the box except a toolchain, package manager and coreutils
13:08zerdoxthe most important staff later in handbook is configuring kernel which i skip, configuring bootloader which i also skip (i would like to use refind later tho). and configuring the system which i can do later when I login. the only necessary that seems to me things are installing networking tools and setting up fstab which is just genfstab
13:08chadmedthats the spirit of gentoo
13:09chadmedrefind doesnt work properly on arm64 macs anyway
13:09chadmedive tried it a couple of times
13:09chadmedi use systemd-boot
13:09chadmedanyway, you cant just skip steps youve been asked to do because you personally dont think its meant to work like that
13:10chadmedif you want a more user friendly out of the box experience just stick to arch
13:11zerdoxbut... not setting up crone and not creating the user won't stop from booting the system like this. this is not the issue
13:12chadmedprobably not yeah but the point is that youre not getting support unless youve followed the basic instructions laid out before you lmfao
13:12zerdoxi already used arch for about a year and then i got to void linux which was much better. now i decided to never go back to systemd. this is the reason why i decided to use gentoo and not just asahi
13:13chadmedand fair enough, but im not going to act as guarantor for your system when i have no idea what state its in
13:13chadmedthis is such a basic fundamental tenet of tech support
13:13chadmedif you want to go off script because you think its fine then go ahead be my gues
13:14chadmedthere wouldnt even be any gentoo infrastructure in the first place if i didnt have the same thought myself
13:14chadmedbut that usually comes with the understanding that youre on your own to fix any issues that crop up
13:14zerdoxok. i will post one more installation including all of the commands where i will set up user, install wifi tools, set crone, time sync which won't affect my boot process...
13:15chadmedyknow what
13:15chadmedim going to make the changes to the script right now
13:30yuka_ has joined #asahi-alt
13:31yuka has quit [Remote host closed the connection]
13:53rudi has joined #asahi-alt
13:53rudi has quit []
14:03_rudi has joined #asahi-alt
14:07MichaelLong*yay* it is a long time ago I had to setup gentoo from scratch, my current systems are so old by now...
14:08chadmedmy server root fs is at least 6 years old
14:09chadmedi dont mind the gentoo install experience tbh, i find it therapeutic
14:09MichaelLonghad to figure out basics like not to suspend on lid close (I'm still running without graphical environment)
14:11_rudi has quit [Ping timeout: 480 seconds]
14:12chadmedjust disable suspend in the kernel problem solved :P
14:13MichaelLongnah it is on the /etc/systemd/logind.conf HandleLidSwitch=ignore :)
14:25chadmedahhh systemd issue
14:51rudi has joined #asahi-alt
14:52rudi is now known as Guest10285
15:00Guest10285 is now known as _rudi
15:14_rudi has quit [Quit: Fell off the bus]
15:22zerdox has quit [Ping timeout: 480 seconds]
15:41compassion has joined #asahi-alt
15:43compassion has quit []
15:43compassion has joined #asahi-alt
15:47compassion has quit []
15:47compassion has joined #asahi-alt
15:55_rudi has joined #asahi-alt
16:25deteg1337 has joined #asahi-alt
16:38deteg1337 has quit [Remote host closed the connection]
16:58janrinze has joined #asahi-alt
17:00janrinzeanother round of bugfixes from Asahi Lina has been submitted. @glanzmann will we see them soon for Debian?
17:20_rudi has quit [Read error: Connection reset by peer]
17:22mpsjanrinze: does it builds on debian? I got '../src/gallium/drivers/asahi/agx_state.h:36:38: error: '__VA_ARGS' undeclared (first use in this function)' error on alpine linux
17:34zerdox has joined #asahi-alt
18:12jannaumps: yes, it will compile. the error is inside #else after '#ifdef __GLIBC__'
18:12jannaus/__VA_ARGS/__VA_ARGS__/
18:16mpsjannau: in src/asahi/compiler/agx_compile.c
18:17mpshm, src/gallium/drivers/asahi/agx_state.h
18:18jannausrc/gallium/drivers/asahi/agx_state.h line 36
18:18deteg1337 has joined #asahi-alt
18:19mpsyes, it passed now
18:22winter has quit [Quit: The Lounge - https://thelounge.chat]
18:26deteg1337 has quit [Ping timeout: 480 seconds]
18:32mpsyes, "Tested-by: mps" :)
19:14Cyrinux9 has quit []
19:14Cyrinux9 has joined #asahi-alt
19:24deteg1337 has joined #asahi-alt
19:32deteg1337 has quit [Ping timeout: 480 seconds]
19:32deteg1337 has joined #asahi-alt
19:46possiblemeatball has joined #asahi-alt
19:47janrinzeIf i wanted to roll my own deb for mesa, I should edit the mesa.sh to use the latest checkout and add jannau's patch. Right?
19:54jannauyou won't need the patch for debian but you probably want https://gitlab.freedesktop.org/asahi/mesa/-/merge_requests/27, note that you have to update the kernel as well
19:57mpslatest mesa commit with jannau patch doesn't work for me with kernel asahi-6.2-12. this is not bug report, just note
19:58mpsit is not important to me
20:01mpsuh, did I really upgraded kernel after build :) lets check again
20:03jannauthe UAPI change is not in asahi-6.2-12
20:03janrinzejannau: which kernel update do I need? i have linux debian 6.2.0-asahi
20:04janrinzeOk. building mesa first and then see how i can do a kernel build.
20:05mpsthings becoming stable so I stopping to be careful on building and installing
20:05janrinzehopefully grub will offer to boot the older kernel as a fail over if my newer kernel fails.
20:05janrinzemps: just my thought. being careful never hurt ;-)
20:07mpsjanrinze: right, but work on pkgs becoming routine and then attention is lowered
20:08janrinzemps: mesa build was fast!
20:09janrinzejannau: when using latest mesa build on older kernel, what would be the worst case scenario?
20:09mpsso, kernel tagged v6.3-rc4 will probably have UAPI 1007
20:10janrinzejannau: because if I would have to revert to 6.2 kernel i'd like to know the risks
20:17jannauno, v6.3-rc4 has no asahi driver at all
20:18jannauthe uapi change is only in lina's usual branch
20:18janrinzejannau: so i won't be able to test this yet?
20:18jannaubest case fallback to software rendering, in the worst case crashing X11 servers / wayland compositors
20:19QuickTimeX has joined #asahi-alt
20:19janrinzejannau: got it. As long as it boots to the console i'm fine.
20:20QuickTimeXHello channel! Is it possible to install Debian 11 Bullseye instead of Bookworm? The current guide uses bookworm but I need bullseye
20:21mpsyes, in my test it used swrast and xorg didn't crashed
20:22janrinzeQuickTimeX: It's quite an endeavour to roll your own. The Glanzmann installer does indeed bookworm (testing)
20:24QuickTimeXThanks! I am interested in running openmediavault which requires bullseye. but not if it is too difficult. maybe I will play with nextcloud in docker first
20:24janrinzeQuickTimeX: Before glanzmann worked on it I would roll my own. However that would require several disk partitions and a working install. Next mount an unused partition and debootstrap Bullseye. Not sure if the DEBs from Glanzmann will install on Bullseye though..
20:25janrinzeQuickTimeX: Also setting up after debootstrap is not for the faint of heart..
20:26janrinzeQuickTimeX: and booting into that image I would add a grub entry in the working Linux install.
20:27janrinzeQuickTimeX: My experience was that this will yield a setup that won't be maintainable and won't be compatible with future upgrades or installs
21:02QuickTimeX has quit [Remote host closed the connection]
21:08deteg1337 has quit [Remote host closed the connection]
21:17janrinze has quit [Remote host closed the connection]
21:19possiblemeatball has quit [Quit: Quit]
21:32zzywysm has quit [Quit: Textual IRC Client: www.textualapp.com]
21:33janrinze has joined #asahi-alt
21:34janrinzejannau: I've managed to get my homebrew kernel to run with latest mesa. (including your patch)
21:37pthariensflame has joined #asahi-alt
21:41pthariensflame has quit []
22:50nopeslide13 has quit []
22:52nopeslide13 has joined #asahi-alt
23:16zerdoxchadmed: Thank you for the help. I tried again and it worked just fine. I found out that I was also missing required licenses. Can I try to provide PR so we can handle this case in install script?
23:16zerdoxChaosPrincess: thank you too.
23:17jamespmorgan has quit [Remote host closed the connection]
23:37nsklaus has quit [Quit: disappears in a cloud of smoke]
23:39chadmedzerdox: interesting that you were missing licenses, the script adds the required licenses to package.license
23:39chadmedby all means file a PR though
23:40chadmedglad it's finally working for you
23:40zerdoxhm.. that was the only difference from my previous installation. maybe changes you made to the script made everything work
23:41chadmedcould be, although if you look at the commit it was mostly just rewording stuff and making the fwextract script run automatically
23:41chadmedso who knows
23:41chadmedyoud think a piece of sand that can only ever be in one of two states would behave a little more predictably
23:41zerdoxyeah i looked up commit. you changed /boot/efi to /boot and some other stuff
23:42nsklaus has joined #asahi-alt
23:44chadmedyeah oh well as long as it works!
23:44chadmedkeep in mind of course that your EFI System Partition is now your /boot
23:44chadmedthis makes it waaaaay easier to muck about with kernels and m1n1
23:44chadmedbecause you can just mount it directly in macos
23:44zerdoxnow i need to know how to automate updating my system with requirements from asahi tutorial. also i would dig a bit deeper about how do i customize kernel and all that stuff that i am unfamiliar with. i remember script asked me to install different kernel and play with it afterwards
23:45chadmedah right no you dont install a "different" kernel
23:45chadmedthe kernel sources and build artefacts are at /usr/src/linux
23:45zerdoxyeah i remember it from install script
23:45chadmedthe point of that message is to say that the kernel configuration is probably overly bloated for a gentoo install because its the default arch/asahi one
23:46chadmedso if youre comfortable customising kernel configs you can take stuff out like the useless HID drivers for devices you dont own etc
23:46chadmedfor example i run a minimal kernel built with clang using LTO and only the bare minimum modules i need to use the system
23:47chadmedwhich is basically just the asahi drivers plus the cmedia codec driver for my dac
23:47zerdoxi am not into all that kerneling stuff you know.. i used wrong wording for it. i will take a look at configurating current kernel
23:48zerdoxalso that boot penguins are a bit cringy imo. i guess they are related to kernel also, right?
23:48chadmedyeah thats just a kernel config option
23:49chadmed1 tux = 1 cpu
23:50zerdoxowkay. good luck to you and good luck for me learning all this. ima also create dotfiles repo this time so i can hop easier cause i will rice this shit now
23:51chadmedlmfao awesome have fun
23:51chadmedkeep /etc/portage synced up with that too
23:51chadmed you will end up with loads of stuff in there
23:51chadmedand its a pain in the arse to try and reconstruct
23:52zerdoxok. i will just right down things you say cause for now i don't understand them
23:52zerdoxalso i need to edit /etc/inittab after install due to https://wiki.gentoo.org/wiki/MNT_Reform#f0_respawning this
23:54chadmedhuh so thats how you fix that
…