2022-12-19
00:44swaggie has joined #asahi-alt
00:52swaggie has quit [Ping timeout: 480 seconds]
00:57cylm_ has quit [Ping timeout: 480 seconds]
02:14swaggie has joined #asahi-alt
02:22swaggie has quit [Ping timeout: 480 seconds]
02:54jamespmo_ has joined #asahi-alt
03:00jamespmorgan has quit [Ping timeout: 480 seconds]
03:25swaggie has joined #asahi-alt
04:31dgb has joined #asahi-alt
04:55pthariensflame has joined #asahi-alt
04:55pthariensflame has quit []
04:56dgb has quit [Quit: dgb]
05:03kallisti has joined #asahi-alt
05:21dgb has joined #asahi-alt
06:41dgbGlanzmann: hey i just want to say thanks for all your hard work on debian! do you have any plans on a debian archive? i got tired of building new kernels and briefly thought about using a ci, but it's not really worth it if no one else uses it. but if you have any plans or if there's an audience i'd be happy to help.
08:13dgboh thanks. i don't recall seeing this when i first started and i haven't checked his git in a while.
08:14Glanzmanndgb: It is pretty new. I started it on the day the gpu code was available. Because we now need to many packages which are not upstream and won't be for quiet a while.
08:15GlanzmannThere is no CI, but I have a cronjob which notifies me of any changes at 18:00 each day. I'll test them and if I don't see any regressions I push them out. But I also keep all old versions in the repository. So if we have any regressions, we can easily go back. Also m1n1 makes backup copies.
08:20dgbis there a debian installer in the works? i have some time after the new year and i don't mind giving it a crack
08:24GlanzmannBut at some point I decided that the debian installer is so broken and constantly being broken and noone really cared, so I decided to drop it.
08:25GlanzmannSo now we have two options to install Debian a) you use the image b) you use the live system and do everything manual
08:26Glanzmanndgb: But if you want to make a functional debian installer, you can checkout 'bootstrap.sh' from 2 weeks ago and modify the commented out d-i section.
08:50dgbi used your flash drive image because i wanted to use btrfs and it was quite some typing. i figure it'll make it easier to have an actual installer.
08:53dgbthat reminds me, i was having trouble with wifi until i recalled i've been using dfs channels for so long i forgot about it. wireless-regdb was missing in your image at the time.
08:56Glanzmanndgb: In the livesystem you can also install xorg and cut paste the commands for setup Linux. Most commands are in /root/quickstart.txt
08:56GlanzmannPersonally I stopped using the d-i after it let me down a few times with simple raid 1 + ext4 setups and now only use livesystems (now my own, before grml) to setup Debian.
08:56cy8aerThe main problem of the di was that it did text resolution changes (even in text mode). But I guess/hope that these problems would be solved with a dcp kernel (and - of course: grub, self install the kernel, firmware)
08:57Glanzmanncy8aer: For me the man problem with d-i that they broke different things every other day and I just got sick of it.
08:59cy8aerGlanzmann: yeah one of the d-i developers should fall in love with asahi . Then the problems would be vanish...
09:03GlanzmannYes. But to be honest the changed to the d-i was minimal. It was just: another kernel, extracting the firmware and loading the wifi module. And install grub with the removable flag.
09:03dgbGlanzmann: thanks. for some reason it never occur to me to install a desktop... i'll remember next time for sure.
09:05Dcow has joined #asahi-alt
09:13dgbi don't have a second box but i guess i could've edited quickstart.txt into .sh, not saying it's a good idea ofc...
09:14Dcow has quit [Ping timeout: 480 seconds]
09:23GlanzmannWhen I have a second computer, I boot into live, install ssh, set a password for a user or install my ssh key and do the rest remotely.
09:33dgbGlanzmann: that reminds me, is there a reason why you are installing system packages with apt individually instead of tasksel?
10:04Glanzmanndgb: I did not know about tasksel. Also the options seems very limited, at least on my system https://pbot.rmdir.de/tvlateM7zhYQjuOv4NM0Mw
10:05Glanzmanndgb: I did a meta package for keeping the kernel up2date. And m1n1 is optional. Maybe people want to build there own m1n1.
10:11swaggie has quit [Remote host closed the connection]
10:12swaggie has joined #asahi-alt
10:17Dcow has joined #asahi-alt
10:25Dcow has quit [Ping timeout: 480 seconds]
10:26swaggie has quit [Ping timeout: 480 seconds]
10:46swaggie has joined #asahi-alt
10:48dgbGlanzmann: afaik `standard` installs `~prequired ~pimportant ~pstandard` for the complete "standard system utilities," so future upstream changes wouldn't break your list
10:52Glanzmanndgb: I see. I try to keep the list as small as possible to make the installation quicker and the live system boot faster.
10:54Glanzmanndgb: I also have a version of the live system for amd64 which I internally use. There I have issues with the initrd to become to big to be booted by any bootloader I found on amd64 (grub, syslinux, ipxe). So I made the initrd as small as possible and have a rc.local which pulls in the rest.
11:10Dcow has joined #asahi-alt
11:15swaggie has quit [Ping timeout: 480 seconds]
11:16pjakobsson_ has joined #asahi-alt
11:18pjakobsson has quit [Ping timeout: 480 seconds]
11:20Glanzmanndgb: No on m1 the initrd size is so big that not yet found a limit. And I already tried several gb.
11:28arnd_rebooted into a different kernel, no change. Rebooted into a 4KB page kernel without DCP, this one works, but has the wrong sctreen resolution
11:29GlanzmannOr use mine: https://thomas.glanzmann.de/asahi/pool/main/libunwind-dev_1.6.2-2.1_arm64.deb
11:30GlanzmannIssue is that libunwind was recently updaed. The version had a 4k issue. See asahi mailinglist.
11:31Glanzmannmps: However if the anti tearing modesetting patch makes it upstream. I'm the first guy compiling a new xorg for debian. :-)
11:37Glanzmannmps: I use Debian, because it has the most packages for any distribution. It is stable, so it does not break all the time. And I can upgrade to another major release. I have systems which I have not reinstalled for 20+ years. I also have machines which used to be physical, than VMs, which used to be 32 bit and now 64. All without reinstallation ...
11:41GlanzmannI started with Debian 2001. At that time I was a sysadmin and student at FAU. And we reinstalled the CIP Pool (200+) machines with Debian. We used Caldera before.
11:41arnd_I did something wrong, now I get the same problem with both 4kb and 16kb kernels. time to get out a laptop
11:42Glanzmannmps: My first Linux distribution was Slackware 93 or 94. Don't remeber. Than SLES. Than RHEL. Than I also tried OpenBSD, NetBSD, FreeBSD, Solaris. And I build twice a linux distribution by myself. Once with linuxfrom scratch was 2000 or 2001 and once really from scratch. :-)
11:43Glanzmannarnd_: You can do the following to get your system to a working state: https://thomas.glanzmann.de/asahi/README.txt
11:43Glanzmannarnd_: I also upgraded the live system for you. So you can also use that to fix things, if you like to.
11:45mpsGlanzmann: looks like we switched to linux at nearly same time, I started in '92 or '93, forgot exact time
11:48arnd_mps: no, I did not touch touch the boot loader at all. I did install the packages from https://thomas.glanzmann.de/asahi/README.txt, but am still running my own kernel with dcp but no appledrm
11:49mpsarnd_: idk for debian but a lot of people have this issue forgetting to upgrade second stage m1n1+dtbs+u-boot. I think Glanzmann could give proper answer
11:51Glanzmannmps: Once I want to the GPU kernel I did not look back. Currently I have no issues other than xfreerdp. But it was broken with simpledrm as well but differently.
11:53GlanzmannI also had a lot of trouble with the kernel config on Debian. At first only mps config worked. System did not even boot. But than once to many users complained about missing kernel. I gave adopting the debian config another shot and it worked. And I automated the process. So hopefully in the future it will be easier.
11:53arnd_Glanzmann: it's the same crash as before. I installed libunwind8 and libunwind-dev manually and also did an 'apt upgrade' for the other packages on your server
11:55arnd_Glanzmann: no, let me try that next. What version of m1n1 do I need for that? I'm currently on linux-next from just before the merge window, with a m1n1 that matches the asahi-rc8 kernel
11:55Glanzmannarnd: So I updated all packages (both from Debian and myself) and I can still boot into Xorg.
11:59GlanzmannSo make sure it is mount or copy it manually over once the package is installed: cp /usr/lib/m1n1/boot.bin /boot/efi/m1n1/
11:59dgb has quit [Quit: dgb]
12:00GlanzmannAnd also do not forget about 30-modeset.conf: https://pbot.rmdir.de/hKnwtuSX6CHqS3o22PdV4A
12:06arnd_maybe I'm stil booting an old m1n1 from a different partition. I had installed two separate instances in order to have a fallback
12:07cylm_ has joined #asahi-alt
12:07arnd_right, I can log in remotely, everything else seems fine. Before updating libunwind, I could still use Xorg with the 4K kernel, now it's broken with all kernels
12:07Glanzmannarnd_: Okay and if you start Xorg manually as root from the first console, it crashes?
12:12arnd_I know which grub and kernel I'm booting, those are the ones I want, the question is which second stage m1n1 is picked up by the first stage
12:26Glanzmannarnd_: Can you run https://tg.st/u/debug.sh and paste us the output or compare it to mine? https://pbot.rmdir.de/u/r7c-EUBaZu13bkkj0O3xCw
12:34arnd_I'll do that later then, will work with remote login from my laptop for now, need to get a few things done that I can hopefully do with an inferior keyboard and screen ;-)
12:39arnd_"[ 22.533] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x188) [0xaaab0e6b96c8]\n [ 22.533] (EE) unw_get_proc_info failed: no unwind info found [-10]" sounds like the unwinding still has problems. Maybe I need to install some -dbg package to get a proper backtrace?
12:43Glanzmannarnd_: I had this issue when I had the wrong graphic card hardcoded in the 30-modsetting.conf
12:45Glanzmannarnd_: I tried the live system. It works. I followed the instructions here: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ logged in as root without password. configured wifi, apt update; apt install lightdm xterm blackbox; /etc/init.d/lightdm start and logged in as root without password.
12:46Glanzmannarnd_: But I would start with the live cd and see if that works. Because than you know it is a general problem or one with your userland.
12:47GlanzmannAnd than take it from there. I would also get rid of the second installation and use backup copies of m1n1 to revert back quickly using macos in case of an failure and the debian live usb for anything else.
13:07swaggie has joined #asahi-alt
13:11arnd_Glanzmann: after I went into the recovery boot menu and picked the other stage1 loader, it booted into the right stage2 partition and it all seems to work now. No idea what changed since both stage2 are the same, and I was booting the same kernel
13:11arnd_getting rid of the second installation is probably a good idea, this seems to be causing most of my problems, even though I still don't understand what exactly is going on
13:12arnd_I'll need to make sure it all still works with my own kernel though, but now I really need to get to my actual work
13:16swaggie has quit [Ping timeout: 480 seconds]
13:17Glanzmannarnd_: My assumption is that your other stub is the wrong macos version. As a result the gpu driver refuses to probe. As a result, xorg can't start because it doesn't get the color mapping right. But who knows.
13:40Glanzmann has quit [Quit: EOF]
15:08swaggie has joined #asahi-alt
15:16swaggie has quit [Ping timeout: 480 seconds]
15:39swaggie has joined #asahi-alt
15:47swaggie has quit [Ping timeout: 480 seconds]
16:11swaggie has joined #asahi-alt
16:19swaggie has quit [Ping timeout: 480 seconds]
16:42swaggie has joined #asahi-alt
16:51swaggie has quit [Ping timeout: 480 seconds]
17:15swaggie has joined #asahi-alt
17:23swaggie has quit [Ping timeout: 480 seconds]
19:17cy8aer@Glanzmann: saw your retrospection some hours ago... yes 93, I had an 486dx2 80 amd. And it did not run longer than two days (slackware). And nobody cared about this because these machines were not stable with DOS neither... But it was the bus wih 40MHz...
19:39swaggie has joined #asahi-alt
19:48swaggie has quit [Ping timeout: 480 seconds]
19:54jamespmorgan has joined #asahi-alt
20:00jamespmo_ has quit [Ping timeout: 480 seconds]
20:53swaggie has joined #asahi-alt
21:33Doliometer has quit [Remote host closed the connection]
21:56swaggie has quit [Ping timeout: 480 seconds]
23:06swaggie has joined #asahi-alt
23:57jamespmo_ has joined #asahi-alt