#
…

2023-08-29

00:49utsweetyfish has quit [Remote host closed the connection]
00:49utsweetyfish has joined #asahi-alt
00:52chadmed_ has joined #asahi-alt
00:53cy8aerjannau: ok now I tried the direct booting from u-boot. It looks fine until "booti": Wrong Ramdisk Image format. Ramdisk image is corrupt or invalid. Are there different Ramdisk formats around u-boot cannot handle? This is a "standard" initrd from a debian dist.
00:53cy8aerAnd now it is too late for me. I try it tomorrow again.
00:54chadmed has quit [Ping timeout: 480 seconds]
02:09jeisom has quit [Remote host closed the connection]
02:09jeisom has joined #asahi-alt
02:19chadmed_ has quit [Quit: Konversation terminated!]
02:30jeisom has quit [Remote host closed the connection]
02:31cylm_ has quit [Ping timeout: 480 seconds]
02:31jeisom has joined #asahi-alt
02:40utsweetyfish has quit [Remote host closed the connection]
02:40utsweetyfish has joined #asahi-alt
02:41jeisom has quit [Ping timeout: 480 seconds]
03:11chadmed has joined #asahi-alt
03:32utsweetyfish has quit [Remote host closed the connection]
03:32utsweetyfish has joined #asahi-alt
04:08BenTheTechGuyI think this U-Boot was only built with support for gz and xz compression, so make sure your initrd isn't ZSTD compressed.
04:48chadmed has quit [Remote host closed the connection]
05:33chadmed has joined #asahi-alt
07:07kdb424 has quit [Quit: Ping timeout (120 seconds)]
07:07loops has quit [Read error: Network is unreachable]
07:07loops has joined #asahi-alt
07:09kdb424 has joined #asahi-alt
07:21novafacing992 has quit [Read error: Connection reset by peer]
07:24novafacing992 has joined #asahi-alt
07:43kujeger has quit [Quit: ZNC 1.8.2 - https://znc.in]
07:52chadmed has quit [Ping timeout: 480 seconds]
07:59chadmed has joined #asahi-alt
08:20hightower3 has joined #asahi-alt
08:22chadmed has quit [Ping timeout: 480 seconds]
08:26hightower4 has quit [Ping timeout: 480 seconds]
08:44chadmed has joined #asahi-alt
08:57cy8aerBenTheTechGuy: hm, then it is no solution for me ☹️. Ok last chance is a live stick. But my stick does not start up and I guess this is the dtb problem. I use the https://tg.st/asahi-debian-live.tar and probably @Glanzmann does not build it every time a new kernel occurs. And then I have an older kernel not working with the actual m1n1/dtb combination.
09:01cy8aer... And I actual do not have the ressources to builld it on my own.
09:03cy8aerAnd when this does not work I am completely stranded, because I would need the live stick for re-installation too because I only use crypted systems on my laptop and this does not work with the debian image of the standard installation image provided by the installer.
09:03mpscy8aer: here is short guide and url to bootable usb https://arvanta.net/alpine/install-alpine-m1/
09:04mpsmaybe you can use it to fix your installation
09:04mpsor take ideas from it
09:06cy8aermps: Thank you. This is a solution if my live stick does not work. I for myself only need a running linux system to rescue. And an alpine system will do too. Do you know if this stick starts up with the actual m1n1/dtb combination?
09:07cy8aerBecause that is what I have: a efi partition with the latest m1n1
09:07mpsI think so though didn't tested it in last month
09:08mpsI could build new one later today
09:08cy8aerThat should be an environment >= kernel 6.4.0-5 or so.
09:10cy8aerBut please do not put too much work in it.
09:10_jannau__to make this work any "live" image should ship a boot.bin with matching dtbs which can be temporarily used for booting the live image
09:11_jannau__cy8aer: if you can edit the command line of the non-booting debian live image, try adding "nomodeset"
09:11mpscy8aer: it is script and don't require much work, just ./create-m1-img.sh
09:12kujeger has joined #asahi-alt
09:13cy8aer_jannau__: yes that is a problem I found just with my crash. Recovery is a mess for someone with not too many skills. Ok, "nomodeset" reads like that the dtbs are needed for the frame buffer stuff only? Interesting.
09:14mpscy8aer: just uploaded new image with latest asahi kernel, still didn't tested does it boots, hope will test it in hour or two
09:15_jannau__there was a dtb change for the display device nodes which could explain boot problems. It should be avoidable by not loading the dcp driver (which nomodeset does, if the kernel is not very old)
09:16cy8aermps: Yes for me this will work, no problem but I am talking about people who crash their system like that and do not know anything about the mechanisms for booting up and try to recover. Thank you for the image. I will try that too (but please stay tuned, need to do some "real work" first 😉 )
09:31hightower4 has joined #asahi-alt
09:37hightower3 has quit [Ping timeout: 480 seconds]
09:53cy8aer(other os, other circumstances, but same effect)
09:57mpsI can't remember but some of u-boot versions had a problem to boot from usb. not sure is this fixed in latest verified release
10:03chadmed has quit [Remote host closed the connection]
10:35chadmed has joined #asahi-alt
11:18cy8aerLooks like the version of installer 6.4.0 does have a problem. I am not able to boot any of the images.
11:19cy8aerfrom usb.
11:20cy8aerSo now I am stuck.
11:26cy8aerWhich components of grub should be on the efi partition? I know that the "classical" grub has components inside the file system. Is this the same for efi? Because those grub fragments I have try to scan nvm 0:4 and crash then but then there is only grub rescue and not the full grub system. Because with the full grub I could boot again...
11:26cy8aerAnother question: If I have another system which is installed the same way and I "steal" the EFI partition from there: is there a chance to rescue the system then?
11:38mpsah, yes. latest u-uboot have bug and can't boot from usb
11:38mpsjust fixed it and it boots fine
11:41cy8aerOk somehow reassuring. But then I need to wait until the next installer version with the patch or for access tomy "twin" system for building a new boot.bin
12:45jeisom has joined #asahi-alt
12:53tsujp_ has joined #asahi-alt
12:53handlerug_ has joined #asahi-alt
12:53okt_ has joined #asahi-alt
12:53d4ve_ has joined #asahi-alt
12:53pldtf_ has joined #asahi-alt
12:53probie_ has joined #asahi-alt
12:53signaryk_ has joined #asahi-alt
12:53alethkit_ has joined #asahi-alt
12:53asimpson_ has joined #asahi-alt
12:56BenTheTechGuy_ has joined #asahi-alt
12:57BenTheTechGuy has quit [resistance.oftc.net larich.oftc.net]
12:57handlerug has quit [resistance.oftc.net larich.oftc.net]
12:57tsujp has quit [resistance.oftc.net larich.oftc.net]
12:57alethkit has quit [resistance.oftc.net larich.oftc.net]
12:57pldtf has quit [resistance.oftc.net larich.oftc.net]
12:57signaryk has quit [resistance.oftc.net larich.oftc.net]
12:57asimpson has quit [resistance.oftc.net larich.oftc.net]
12:57probie has quit [resistance.oftc.net larich.oftc.net]
12:57d4ve has quit [resistance.oftc.net larich.oftc.net]
12:57okt has quit [resistance.oftc.net larich.oftc.net]
12:57JTL has quit [resistance.oftc.net larich.oftc.net]
12:57asimpson_ is now known as asimpson
12:57d4ve_ is now known as d4ve
12:57signaryk_ is now known as signaryk
12:57alethkit_ is now known as alethkit
12:57okt_ is now known as okt
12:57handlerug_ is now known as handlerug
12:58pldtf_ is now known as pldtf
12:58tsujp_ is now known as tsujp
12:58probie_ is now known as probie
13:02JTL has joined #asahi-alt
13:32SalimTer- has joined #asahi-alt
13:36SalimTerryLi has quit [Ping timeout: 480 seconds]
14:16jeisom has quit [Ping timeout: 480 seconds]
14:58zhdi has joined #asahi-alt
15:35cylm_ has joined #asahi-alt
15:36jeisom has joined #asahi-alt
16:43maria has quit [Ping timeout: 480 seconds]
16:58jeisom has quit [Ping timeout: 480 seconds]
17:21maria has joined #asahi-alt
17:59possiblemeatball has joined #asahi-alt
18:08zhdi has quit [Quit: Connection closed for inactivity]
18:51jeisom has joined #asahi-alt
19:14zhdi has joined #asahi-alt
19:15cy8aerHi there - back again. I needed to build the boot.bin offline on another (x86) machine with the patch of mps (thanks for that). The Glanzmann stick did not start the live image but - I had a full grub then. Booting twice, fighting with "grub-install" and everything is fine again.
19:16cy8aerThank you all for your help.
19:16mpscy8aer: did you read #asahi-dev about booting usb with current u-boot
19:17mpsit could be booted by break u-boot and from cmdline type ` env set boot_efi_bootmgr ; run bootcmd_usb0`
19:17mpsI tested with current asahi u-boot without patch
19:19cy8aermps: no, I just used your patch. Hm, yes, same effect, less efford. But does not matter, I found a way.
19:19mpsso, no need to rebuild u-boot and install/updtad current boot.bin on ESP
19:19cy8aeryes. simply disabling the new function in u-boot.
19:20cy8aerNow I need my time to document the stuff...
19:20mps(now I'm on the apple side view about EFI, don't like it)
19:22mpsu-boot people works on something better
19:25cy8aerThe main point why I kicked my efi and the whole volume: I played around with the boot.bin and it did not work. Then I wanted to copy an old version on the apple side in the efi partition and accidently erased (!) my volume. Don't ask, I work with an ISO keyboard and wanted to find out the partition name of the efi partition and somehow it kicked the volume via diskutil (and I was already root) from the history. That was too late and too unfocused.
19:25mpsVPL - Verified Program Loader
19:26cy8aerSome EFIs of the x86 machines are crazy too.
19:26cy8aer(non-apple machines)
19:27cy8aerThinking about the secure boot stuff and switching it on with linux...
19:27mpsnot advice but maybe it will be easier to simply reinstall
19:28delroth has quit [Remote host closed the connection]
19:29delroth has joined #asahi-alt
19:29cy8aerwould be, but it is my daily driver, I am not at home and restoring my stuff would take to long and I have a debian with a crypted file system - https://g3la.de/hedgedoc/buDIXGBuRzKMwUnYOpStuw - and for the reinstall a live image is needed too 😕
19:31cy8aerThis is a bit a chicken and egg problem.
19:31cy8aerAnd when you can see your two partitions which still work...
19:32mpsmaybe you can use qemu from macos to access your partitions
19:32cy8aerAnd yes, do not play around when you not have all tools for recovery at your side.
19:32cy8aerThat works?
19:33mpsyes, it worked last time I tried
19:34mpsI was even tempted to create alpine image for help users to access linux partitions from macos
19:34cy8aerI also thought about installing the standard asahi in space before my system - shrink macos a bit - and use this for rescuing. But I read about problems with two linuxes on one system.
19:35mpsbut it can be done using live linux iso
19:35cy8aer(before between macos and my partitions)
19:35cy8aerbut now everything is well and thanks again.
19:35mpslet me search backlog where I explained this
19:40hightower2 has joined #asahi-alt
19:41mpscy8aer: the 'trick' is to add something like ''-drive if=virtio,id=hd1,format=raw,file=/dev/disk0s6' to qemu cli
19:44mpscy8aer: https://tpaste.us/O89d script I used to start qemu to access partitions from macos
19:44cy8aerand macos loops that through? Wow
19:45mpsneed to find time to document this and become famous ;)
19:46hightower4 has quit [Ping timeout: 480 seconds]
19:46cy8aerright so.
19:47cy8aer(hm, sound german somehow)
19:47cy8aers/ound/ounds/g
19:57hightower3 has joined #asahi-alt
19:57cylm has joined #asahi-alt
19:59cylm_ has quit [Ping timeout: 480 seconds]
20:02hightower2 has quit [Ping timeout: 480 seconds]
20:28delroth has quit [Remote host closed the connection]
20:30delroth has joined #asahi-alt
20:35delroth has quit [Remote host closed the connection]
20:36delroth has joined #asahi-alt
21:08mcint has joined #asahi-alt
21:28zhdi has quit [Quit: Connection closed for inactivity]
22:08JTL has quit [Ping timeout: 480 seconds]
…