marcan changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
mps has quit [Ping timeout: 480 seconds]
mps has joined #asahi-alt
Catyre_ has joined #asahi-alt
Catyre has quit [Ping timeout: 480 seconds]
<m1n1m4[m]>
hello all, i am using alpine and after a failed updar
<m1n1m4[m]>
s/updar/update, i could no longer boot for a few weeks./
<m1n1m4[m]>
i booted withu
<m1n1m4[m]>
usb a d
<mps>
ah, answered on #asahi
<m1n1m4[m]>
sorry, retyping... booted via usb and tried to rein
<mps>
I didn't tried with btrfs but I think you need 'insmod btrfs' in grub.cfg
<m1n1m4[m]>
mps: hello
<mps>
m1n1m4[m]: did you see my previous msg
<mps>
I didn't tried with btrfs but I think you need 'insmod btrfs' in grub.cfg
<m1n1m4[m]>
divficult to type on the salls reen, ahah, big confusion
<m1n1m4[m]>
.
<m1n1m4[m]>
this is matrix
<m1n1m4[m]>
ok, good. I edi
<m1n1m4[m]>
will edit
<mps>
must go now, will be later here again
<m1n1m4[m]>
ok, thanks
Catyre_ has quit [Ping timeout: 480 seconds]
Catyre has joined #asahi-alt
Catyre_ has joined #asahi-alt
Catyre has quit [Ping timeout: 480 seconds]
<mps>
m1n1m4[m]: did you got it booting with btrfs
<m1n1m4[m]>
yes, quite an adventure.. but it is done!
<m1n1m4[m]>
thank you so much
<m1n1m4[m]>
had to change the also of the drives and the boot partition also
<m1n1m4[m]>
and the flag of the partition accordingly to the disk
<mps>
m1n1m4[m]: fine, though I don't understand what you did
<m1n1m4[m]>
OK so, i ended up copying the boot/grub from the usb to the linux partition, then i got to boot from it
<m1n1m4[m]>
after, it was asking for the uuids of wrong disks, i edited the grub.cfg of the linux partition to correct the uuids and the grub partition to boot.
<m1n1m4[m]>
next step will be to update the cfg files to generate the grub.cfg
<m1n1m4[m]>
another thing was to replace the insmod of ext4 to btrfs, and that was it
<mps>
m1n1m4[m]: aha, good, now I understand
<m1n1m4[m]>
ehehe, took me some time but all got back to normal. However when i do apk upgrade, at the end he fails to create the new grub cfg. If you like i can give you more details, to try see what happened. I know i had an apk error due to incorrectly replacing the **dev to be able to use the USB Hotspot, it broke something
<m1n1m4[m]>
anyway i was away from the keyboard for some time and it was nice so "solve the puzzle" :D
<m1n1m4[m]>
s/so/to/
<mps>
m1n1m4[m]: no, you don't need to explain to me how this have to be done. I did this many times
<m1n1m4[m]>
<mps> "m1n1m4!: no, you don't need to..." <- what i mean is that it did not work for me, i could not make it happen...
<m1n1m4[m]>
i mean to be able to have internet from the phone with usb
<m1n1m4[m]>
it would be great, since it might save both devices battery
<mps>
m1n1m4[m]: ah that was not on M1?
<m1n1m4[m]>
it was on M1
<m1n1m4[m]>
asahi/alpine
<mps>
hm, I'm lost. how it is related to phone
<m1n1m4[m]>
OK i spoke 3 subjects at the same time, will explain.
<m1n1m4[m]>
1 - broke apk somehow, sometime ago, i was always getting an error.
<mps>
'apk fix'
<m1n1m4[m]>
output of apk fix:
<m1n1m4[m]>
reinstalling grub 2.06-r5
<mps>
aha, ok
<m1n1m4[m]>
it works well until the trigger
<mps>
(grub is one of the worst software on my list of bad ones)
<m1n1m4[m]>
so it runs well the post-upgrade, the busibox trigger but i when doing the grub triger i get