2024-01-01 18:23:43 Happy New Year \o/ 2024-01-02 09:38:11 One of the two arm servers is now on the way with nu 2024-01-02 09:45:41 Right, the CI server 2024-01-02 09:47:02 yup 2024-01-02 09:48:34 oh no, it's che-bld-1 2024-01-02 09:53:40 why oh no :D 2024-01-02 09:58:56 I first said it was the CI host 2024-01-02 09:59:01 che-ci-1 2024-01-02 10:00:46 is that a problem? 2024-01-02 10:05:16 numono: No, it's fine 2024-01-02 10:23:45 ah, just got now what u said^^" still sleepy~ 2024-01-02 10:24:10 We did initially plan for the ci host to be sent, but it's fine 2024-01-02 12:13:41 Does this mean the ARM CI runners are now offline? i've started seeing MR pipelines fail on ARM 2024-01-02 12:14:21 celie: No, they are still available 2024-01-02 12:15:30 Ok, but they seems to be having problems reaching the DNS server? 2024-01-02 12:16:30 I'm chekcing 2024-01-02 12:18:03 Oh right, there still exists a dependency on the build server 2024-01-02 12:20:06 Ok 2024-01-02 13:03:51 celie: CI should work again 2024-01-02 13:25:07 Thanks 2024-01-02 15:16:25 its running 2024-01-02 16:00:33 it should have v6 and configurable v4 2024-01-02 16:01:21 can anyone access it, and check if something needs to be modified? 2024-01-02 16:02:37 im on the site for ~1h 2024-01-02 16:03:00 What's the IP address 2024-01-02 16:04:19 I'm visiting family, so my availability is limited 2024-01-02 16:06:47 we can continue another time^^ 2024-01-02 16:07:40 the network i can change remotely, and the only unknown is how to give you access to the mgmt port (since i didnt bring any apu-s) 2024-01-02 16:07:51 i can wire it into a vm 2024-01-02 16:08:40 Right, we can discuss that with clandmeter 2024-01-02 16:08:42 ip is 2a02:168:a077:2002:da5e:d3ff:fee6:1f48 2024-01-02 16:08:51 same as before except the prefix 2024-01-02 16:09:09 no more cofe :P 2024-01-02 21:46:20 numono: I cannot ping / ssh yet 2024-01-03 09:52:14 numono: do you have ipv4 i can connect to? 2024-01-03 09:52:19 ikke: does dmvpn work? 2024-01-03 10:02:51 it was firewalled 2024-01-03 10:03:00 it might work now 2024-01-03 10:03:48 @clandmeter: do you not have v6? v4 needs to be confed on the builder 2024-01-03 10:04:06 nope no ipv6 2024-01-03 10:05:19 i can give you a wireguard tunnel if u want (to get v6) 2024-01-03 10:07:41 what do you mean with builder? the actual box? 2024-01-03 10:08:21 yes 2024-01-03 10:08:35 ok understand 2024-01-03 10:08:47 i dont run dhcp atm 2024-01-03 10:10:41 ok it works now 2024-01-03 10:11:02 do you need me to add ipv4? 2024-01-03 10:11:38 unless you need to 2024-01-03 10:12:00 what does that mean? 2024-01-03 10:12:06 ipv6 nat/dns64 are available to reach v4 2024-01-03 10:12:46 so unless you have special usecases with legacy ip, then you dont need to configure it 2024-01-03 10:14:05 ipv6 only has caused issues before 2024-01-03 10:14:26 try ping6 github.com 2024-01-03 10:14:26 to the world it has only a A entry, but in the builder the command will work 2024-01-03 10:14:57 (if u take my dns ofc from the router advertisements :P) 2024-01-03 10:15:10 (rdnssd daemon can auto update resolv.conf) 2024-01-03 10:15:21 its trying to use the local ipv4 config 2024-01-03 10:15:38 want to give it a try if it works with v6 only? 2024-01-03 10:15:56 i dont mind ipv6 only, if it works. 2024-01-03 10:16:21 ikke bumped into issues before, thats what im echoing here now. 2024-01-03 10:16:28 lets wait for him to comment on it 2024-01-03 10:16:55 but in any case, thanks for setting this up :) 2024-01-03 10:17:06 we need to adjust the config anyways 2024-01-03 10:17:41 idk if u want to spend the time to invest into it again, if yes it would be nice, if not i can just give a v4 static gw/ip 2024-01-03 10:17:54 lmk^^ 2024-01-03 10:18:40 ikke did the network config, im not sure what he did. I think its related to the router in front of it before. 2024-01-03 10:18:44 just curious, did you use the ip i sent you earlier to access it, or was it through a dmvpn ip? 2024-01-03 10:18:54 your ipv6 2024-01-03 10:18:57 niiice 2024-01-03 10:19:16 but eth0 has an ipv4 config 2024-01-03 10:19:33 which is probably the subnet of the router at prev location 2024-01-03 10:19:45 probably static aswell :D 2024-01-03 10:20:20 ofc 2024-01-03 10:20:29 which is perfect if things dont change :p 2024-01-03 10:21:01 dw the vlan is dedicated to you 2024-01-03 10:21:13 dw? 2024-01-03 10:21:17 dont worry 2024-01-03 10:21:38 im almost 50, be gentle with slang ;-) 2024-01-03 10:23:06 i think we may need ipv4 for dmvpn iirc 2024-01-03 10:23:22 some parts of dmvpn is not ipv6 compar 2024-01-03 10:23:23 t 2024-01-03 10:23:25 would be nice to explore the v6 only path, id be motivated to resolve any issues that may arise from it 2024-01-03 10:23:25 its much simpler to maintain a single stack on the infra 2024-01-03 10:24:32 if needed the static v4 is ip: 10.159.1.2/24, gw: 10.159.1.1 2024-01-03 10:24:55 from what i understand fixing dmvpn it non trivial 2024-01-03 10:34:55 I think I have to chime in here... from what I can see is that IPv6 only is more and more the default and maintaining dual stack is indeed very cumbersome. I have heard in here about the dmvpn issues before and if it is not fixable, it might be a good route to take the IPv4 hack at nu 's location, IPv4 in place5 is also just a hack/add-on, as all other networks are IPv6 only. Mid term I would suggest to look for a replacement, either 2024-01-03 10:34:55 wireguard or openvpn based, both work fine IPv6 only 2024-01-03 11:09:19 thank you! 2024-01-03 11:10:20 i think we need ipv4. my isp is not making it easy with ipv6 for me 2024-01-03 11:11:22 ncopa: I think both nu and I can easily offer IPv6 tunnels that you can take with you to anywhere, a simple `wg-quick up wg0` will give you full IPv6 access 2024-01-03 11:11:33 Sadly many isps, docker and GitHub did not receive the message yet 2024-01-03 11:12:30 ikke: docker is ipv6 for about 3-6 months now, they dropped the ipv6. registry and enabled IPv6 on the main registry some time ago 2024-01-03 11:12:39 For github, I agree and I fight with their staff about 3 times a year 2024-01-03 11:14:04 my isp gives me a /48 prefix. But thats the only prefix I get. I have a ISP provided router (which looks nice) which grabs this prefix. I use this for the home wifi. For my work network I use ethernet and a linux router (with dmvpn). 2024-01-03 11:14:20 since the isp router takes the ipv6 prefix I cannot get any for my linux router 2024-01-03 11:14:58 and there is no way to turn that off on the ISP provided router 2024-01-03 11:15:12 that would be very strange, you should be either able to route it or to get it via dhcp 2024-01-03 11:15:33 But either way the proposed tunnel above would work, both for a single device or even for you whole home network 2024-01-03 11:15:34 the ISP provided router gets it via dhcp6 2024-01-03 11:15:53 ok. Maybe I should set that up then 2024-01-03 11:15:58 oh, then you might be able to get a sub prefix via dhcp from that router as well 2024-01-03 11:16:05 it's callled prefix-delegation 2024-01-03 11:16:20 I would assume they do that, because otherwise giving a whole /48 is pretty senseless 2024-01-03 11:16:21 i think that ISP router give a /64 prefix 2024-01-03 11:17:13 I am not fully understanding your setup, but if your ISP assigns a /48 to you, then usually the idea is that you can use /64's for your own management / own networks 2024-01-03 11:17:27 but that means that my work net would be behind the home net. I'd prefer to have it side by side, so they are completely independent 2024-01-03 11:17:58 Something needs to route the complete/64 2024-01-03 11:18:11 /48* 2024-01-03 11:18:36 i believe it will work if i put my work net behind the ISP router 2024-01-03 11:18:48 i mean, my work net would get a /64 2024-01-03 11:20:17 but I would ideally want to disable ipv6 on the ISP provided router, and use my alpine router for ipv6 and dmvpn etc. connected on the same switch. so they are separated. two different public ipv4 2024-01-03 11:20:18 ikke: Usually ("by the book") you design it like this: /48 goes to a location/customer, that should be terminated on the ISP's given equipment 2024-01-03 11:20:46 Then the ISP router should give out /64's either by routing (manual settings in the router) or by dhcp prefix delegation (if it is a more and end consumer device) 2024-01-03 11:21:15 ncopa: out of curiosity, where are you based at? 2024-01-03 11:21:23 norway. 2024-01-03 11:21:32 ISP is telenor 2024-01-03 11:21:44 ah, the country with 80% evs, pretty impressive 2024-01-03 11:21:58 yeah, maybe I should rewire the work net to go behind the ISP provided router 2024-01-03 11:22:39 Hmm, telenor looks good in what they do in general: https://stats.labs.apnic.net/ipv6/NO 2024-01-03 11:23:30 they do. except when it comes to documentation how the ipv6 works 2024-01-03 11:23:37 i kinda figured it out using tcpdump :) 2024-01-03 11:23:59 and then someone working at telenor confirmed it on a norwegian forume 2024-01-03 11:24:00 Do you know what kind of router they gave you? 2024-01-03 11:24:32 yup. this one: https://www.telenor.no/kundeservice/internett/modem-og-ruter/wifi-ruter/ 2024-01-03 11:24:45 it looks nice on the TV bench :) 2024-01-03 11:26:06 If I say that norwegian looks similar dutch, will I get kicked? 2024-01-03 11:26:22 It is actually almost readable for a German speaker (German and Dutch having similar roots) 2024-01-03 11:26:48 you wont get kicked for telling the truth :) 2024-01-03 11:26:52 "Koble opp WiFi Ruter" 2024-01-03 11:27:08 norwegian and duch is similar 2024-01-03 11:27:09 That could also pass as a Swiss dialect 2024-01-03 11:27:33 Ah, are they. I was a bit in Finnland, many years ago, which seems to be pretty much different to almost everything else 2024-01-03 11:27:53 So I was assuming Norwegian would also be far off 2024-01-03 11:28:04 there is a switch in the UI to disable ipv6. but it only prevents it from forwarding the ipv6 stuff on the LAN side 2024-01-03 11:28:18 tcpdump revealed that it still asks for the /48 prefix 2024-01-03 11:28:35 I'm actually wondering if that device is internally openwrt 2024-01-03 11:29:33 not sure. I sent a bug report/feature request to their development team. But I dont expect any answer 2024-01-03 11:47:28 My parents isp (local provider) does not support it yet, it seems 2024-01-03 11:52:29 my office isp same thing, need to purchase it separately by some special request. 2024-01-03 11:53:20 do we need ipv4 for other things then dmvpn? github can work with dns64? 2024-01-03 11:54:07 clandmeter: github works with dns64+nat64, yes. We use it everyday like that 2024-01-03 11:54:39 i think we ran into issues even with dns64 2024-01-03 11:54:58 not sure ikke can elaborate on this topic, he hit most of the issues. 2024-01-03 11:56:09 ikke: i guess the GRE issues with ipv6 are still existing? 2024-01-03 11:56:44 dns64 basically only kicking in, if you use dns 2024-01-03 11:57:04 If there are hardcoded IPv4 addresses, they will fail 2024-01-03 12:00:24 nod 2024-01-03 12:00:50 good and flawless solution for this mess doesn't exists yet and I could bet will not appear soon 2024-01-03 12:02:17 ACTION follow IPv6 from 1996 in a hope that it will be fixed soon 2024-01-03 12:05:41 Linux support for multipoint GRE which is used by dmvpn is still missing 2024-01-03 18:31:22 ikke: x86_64 CI out of space? 2024-01-03 20:23:49 ptrc: it's not completely out of space, but large builds would probably fail, will clean up 2024-01-03 20:47:18 numono: I have access to the server now 2024-01-03 20:53:13 numono: Is there some public ipv6 prefix that we can use? The containers right now receive a public ip from the previous /48 prefix 2024-01-04 10:00:24 sure, ive routed 2a02:168:a077:700::/56 to you 2024-01-04 10:19:25 numono: thanks 2024-01-04 10:19:41 np^^ 2024-01-04 17:45:18 ikke: are the ppc64le builds like the one reported here: https://sourceware.org/bugzilla/show_bug.cgi?id=30824 running on power10s? 2024-01-04 17:52:17 PureTryOut: ping 2024-01-04 17:52:25 pong 2024-01-04 17:52:31 hello 2024-01-04 17:52:49 could you help to add lv2 to pipewire 2024-01-04 17:53:24 I'm trying to debug it on #asahi-alt channel for asahi audio 2024-01-04 17:53:40 lv2? Not sure what that is 🤔 2024-01-04 17:53:53 some people from other distros to help there 2024-01-04 17:53:53 But probably very relevant for me since I'll be getting a M2 macbook from work soon 2024-01-04 17:54:40 lv2 plugins/filters 2024-01-04 17:54:41 any particular issue though? Is it something pipewire doesn't support yet? 2024-01-04 17:55:32 I build latest pipewire with -Dlv2=enabled, and it builds but missing some filters 2024-01-04 17:56:18 if you mind to join #asahi-alt there are people who understand these things (which I don't understand) 2024-01-04 17:56:43 not sure why you think I will understand but sure lol. What network? Just OFTC? 2024-01-04 17:56:54 (or is there a native Matrix room?) 2024-01-04 17:56:55 OFTC 2024-01-04 17:57:24 you are PW maintainter and I thought you know these things 2024-01-04 17:57:43 Annnndddd I'm banned from that channel 2024-01-04 17:57:51 I guess they don't allow bridging. SOL then 2024-01-04 17:57:59 iirc matrix doesn't work on asahi channels 2024-01-04 17:58:18 you are right, there is no bridge 2024-01-04 17:58:21 I'm not that deep into PipeWire knowledge tbh 2024-01-04 17:58:39 ah ok, and sorry then 2024-01-04 18:00:34 PureTryOut: but if you plan to run alpine or pmOS on M2 you will probably have to learn more about PW, as I'm trying now ;-) 2024-01-04 18:00:58 probably will haha 2024-01-04 18:02:06 FYI, I got working speakers on apple silicon but can't get to fix these filters 2024-01-04 18:08:46 ah, looks like I found solution 2024-01-04 18:25:55 PureTryOut: I would like to post patches for pipewire and wireplumber aports, i.e. create MR. is that ok for you? 2024-01-04 18:26:36 Yeah ofc, we can always discuss on the MR 2024-01-04 18:29:52 ok 2024-01-04 18:36:22 mick_ibm: our ppc64le server is power9 2024-01-04 18:41:12 telmich: vigir23 is unreachable again since last night 2024-01-04 20:10:07 PureTryOut: !58402 2024-01-04 20:11:45 Yeah I saw. That's easy enough 2024-01-04 20:12:27 thanks 2024-01-04 20:13:02 Btw in preparation for the incoming macbook, got any instructions on how to install Alpine on it? I can't find it on the wiki 2024-01-04 20:13:21 (easy after I learned by 'try-and-fail' method ;-) ) 2024-01-04 20:14:32 maybe we will need something for wireplumber also but will leave it to test tomorrow 2024-01-04 20:16:15 only not sure how to 'alarm' users that they must enable speakersafetyd on boot 2024-01-04 20:17:16 btw, do you know what controls 'Night colors' in KDE? 2024-01-04 20:17:29 PureTryOut: ^ 2024-01-04 20:20:24 Eh, just kwin I guess? 2024-01-04 20:21:13 thanks. but too much to find how to make separate program from it 2024-01-04 20:21:37 just checked, yeah kwin 2024-01-04 20:21:42 Why would you do that...? 2024-01-04 20:21:46 FYI, Night Color works fine on apple silicon with KDE plasma 2024-01-04 20:23:18 I don't like KDE and any other big DE so wanted to see if I can make simple utility for 'barebones' install 2024-01-04 20:23:55 ah ok, better write something from scratch probably 2024-01-04 20:24:04 anyway do you have instructions somewhere to install Alpine on Apple silicon? 2024-01-04 20:25:11 yes, https://arvanta.net/alpine/install-alpine-m1/ 2024-01-04 20:25:37 but it is outdated somewhat now, have to find time to update it 2024-01-04 20:26:15 you can always ask me on IRC if you decide to install 2024-01-04 20:26:44 and https://arvanta.net/alpine/upgrade-kernel-m1/ 2024-01-05 22:12:06 could someone reset pkgrel for telegram-desktop, it is 2 for few last upgrades 2024-01-05 22:12:48 uh, sorry, wrong channel 2024-01-05 22:20:50 Fyi, resetting pkgrel after the fact has no use and even can cause issues 2024-01-05 22:22:44 I know 2024-01-07 10:23:40 numono: thanks (re ipv6 prefix) 2024-01-07 10:35:25 welcome:> 2024-01-07 10:59:15 it works :) 2024-01-07 21:26:40 Hey, it seems that alpine gitlab isn't recieving my emails anymore. I can send emails to other fine though, can someone check please? My emails all come from matthiasahouansou.cz 2024-01-07 21:26:50 matthias@ahouansou.cz 2024-01-07 21:30:08 Kladky: when was the last mail you sent? 2024-01-07 21:30:40 6-7 mins ago: 21:24 UK time 2024-01-07 21:31:02 I see, postfix accepts it 2024-01-07 21:31:23 but? 2024-01-07 21:32:07 Trying to see if I can find more logs 2024-01-07 22:00:46 Kladky: I see the mail in a queue, but no idea yet why it's not being processed 2024-01-07 22:01:33 Odd, can other people send emails to gitlab or is it just me having this issue? 2024-01-07 22:03:14 I see more e-mails in the queue 2024-01-07 22:03:38 First one is from december 24 2024-01-07 22:05:35 I first started experiencing this issue on the 28th, so it probably is that. 2024-01-07 22:10:36 Do you mind opening an issue here? https://gitlab.alpinelinux.org/alpine/infra/ 2024-01-07 22:14:38 might be related to the last gitlab upgrade 2024-01-08 11:31:20 would someone review !58442 2024-01-08 11:31:31 nmeum: ncopa: ^ 2024-01-08 14:27:30 what do you think about creating a channel for #alpine-loongarch64? https://gitlab.alpinelinux.org/alpine/tsc/-/issues/72#note_367311 2024-01-08 14:28:27 ncopa: thanks for merging eudev 2024-01-08 14:28:47 now we have speakers working on apple silicon 2024-01-08 14:30:15 ncopa: I remember that you told earlier that you think to work on asahi installer for alpine. I started to learn it few days ago and now preparing base things 2024-01-08 14:31:03 still don't understand all details but hope to have first testing on next weekend 2024-01-08 17:01:47 ikkie: done #10813 2024-01-08 17:01:58 https://gitlab.alpinelinux.org/alpine/infra/infra/-/issues/10813 2024-01-09 10:09:57 I've got asahi installer to install alpine on apple silicon but don't know how to make EFI/BOOT/BOOTAA64.EFI to find root partition 2024-01-09 10:11:12 other distros use some complicated shims and similar things but I think we don't have such things in alpine 2024-01-09 10:12:10 searched net but couldn't find any hints to lead me to solution 2024-01-09 10:12:33 do anyone of you have any idea how this can be solved 2024-01-09 10:19:03 It is usually detected with grub-install? 2024-01-09 10:21:27 I think grub .efi finds the grub.cfg where kernel and kernel options are found. Root partition is boot option for kernel and used by initramfs 2024-01-09 10:21:56 ncopa: yes, in our normal install. but on apple silicon it couldn't be run with asahi installer 2024-01-09 10:22:55 boot partition number is 'embeded' in EFI/BOOT/BOOTAA64.EFI during grub install in normal cases 2024-01-09 10:23:27 for asahi installer we have to prepare EFI/BOOT/BOOTAA64.EFI in advance 2024-01-09 15:46:54 minimal: ping 2024-01-09 15:58:14 mps: Hi 2024-01-09 15:59:01 minimal: sorry to bother you but I remember that you have good knowledge about grub and I need help 2024-01-09 15:59:17 problem after 2.12 update? 2024-01-09 15:59:54 He was talking about Asahi earlier 2024-01-09 15:59:56 ah, it is updated, didn't noticed 2024-01-09 16:00:59 minimal: I'm trying to build asahi installer for alpine and last problem I have is embeding root partition in BOOTAA64.EFI 2024-01-09 16:01:44 no matter what I try grub-install embeds '(,gpt6)/boot/grub' 2024-01-09 16:01:47 embedding? not sure what you mean 2024-01-09 16:02:38 grub-install embeds root partition in BOOTAA64.EFI, where to search /boot/grub 2024-01-09 16:02:57 you mean how to tell grub-install where to copy the modules and config? 2024-01-09 16:03:26 you are specifying "--boot-directory=/boot" for grub-install? 2024-01-09 16:03:27 no, to set proper partition number in BOOTAA64.EFI 2024-01-09 16:04:33 normally you run "grub-install --efi-directory=/boot/efi --boot-directory=/boot" and that tells grub-install what it needs to know 2024-01-09 16:05:00 the "--efi-directory" option tells it where the ESP filesystems is (for it to place EFI files) 2024-01-09 16:05:20 yes, I have this 2024-01-09 16:05:40 the "--boot-directory" option tells it where the grub.cfg is to be found and where (in a subdirectory) it should copy the Grub modules etc 2024-01-09 16:05:41 `grub-install --target=arm64-efi --efi-directory=/boot/efi --boot-directory=/boot` 2024-01-09 16:06:19 all this works fine, except '(,gpt6)/boot/grub' 2024-01-09 16:06:49 grub-install amongst other things runs grub-mkimage as part of assembling the EFI file from components like the modules that need to be "built-in" 2024-01-09 16:08:04 run grub-install with "--verbose" so see exactly what it is doing 2024-01-09 16:08:55 aha, ok 2024-01-09 16:10:51 here is complete log from my install script https://tpaste.us/vNDk 2024-01-09 16:11:32 grub-mkimage takes a "--prefix=DIR" option which seems to related to "PATH" you're talking about (i.e. the manpage for grub-mkimage states that "-m implies -p (memdisk)/boot/grub" but any "-p" option should be passed to grub-mkimage by grub-install based on the "--boot-directory" you specify AFAIK 2024-01-09 16:12:34 there you go, search for the grub-image command in that output and see grub-install passes it "--prefix '(,gpt4)/boot/grub'" 2024-01-09 16:13:40 what's the 3rd line message regarding "old partition table" about?? 2024-01-09 16:14:00 you changed partitioning in some way but the kernel isn't "seeing" the changes? 2024-01-09 16:14:12 sgdisk message 2024-01-09 16:14:43 here is script which I use to create image https://tpaste.us/QRxw 2024-01-09 16:15:36 in your output it shows "grub-install --target=arm64-efi --efi-directory=/boot/efi --removable" - you didn't specify "--boot-directory" (not sure what it defaults to) 2024-01-09 16:16:22 also you're doing this with a loop device rather than a real disk... 2024-01-09 16:18:18 oh, maybe wrong output posted 2024-01-09 16:19:03 ah this is left cruft in 'echo' 2024-01-09 16:19:38 real command is `grub-install --target=arm64-efi --efi-directory=/boot/efi --boot-directory=/boot --verbose' 2024-01-09 16:20:44 but now I see file 'EFI/alpine/grubaa64.efi', for what it is used 2024-01-09 16:21:52 it's creating grubx64.efi as you removed the "--removable" flag otherwise it would create bootx64.efi 2024-01-09 16:23:10 could this file be used instead of BOOTAA64.EFI 2024-01-09 16:24:23 I see that fedora for asahi have booth plus some shims 2024-01-09 16:25:33 both* 2024-01-09 16:26:07 hm you gave me some ideas to test 2024-01-09 16:26:19 minimal: thank you for the help 2024-01-09 16:30:34 mps: let me look at one of the grub-install logs I have for a similar UEFI/GPT grub-install on loop device 2024-01-09 16:31:07 mps: if you are creating a (intended to be) removable EFI media then you need to use "--removable" 2024-01-09 16:31:22 as otherwise it won't be bootable 2024-01-09 16:32:00 EFP/BOOT/BOOTX64.EFI is the "fallback" EFI file for booting, when there are no suitable EFI boot variables to tell it how to boot 2024-01-09 16:32:23 EFI boot variables are stored on each *machine*, not on the boot media 2024-01-09 16:34:50 correction, you need to use both "--no-nvram" and "--removable" together, the 1st to not create EFI boot vars (as they're "useless" for removable media), the 2nd to create a BOOTX64.EFI file rather than a GRUBX64.~EFI/ALPINEX86.EFI/whatever.EFI file as there's no way to find a GRUBX64.EFI file *without* boot variables, only the fallback file can be founf 2024-01-09 16:37:04 also I believe you should run grub-mkconfig BEFORE grub-install 2024-01-09 16:38:02 as I believe grub-install looks at the /boot/grub/grub.cfg file to "inform it" of what Grub modules are required to be embedded into the generated EFI file 2024-01-09 16:39:46 minimal: it is for internal nvme on apple silicon, I have long time one which runs from removables 2024-01-09 16:39:52 e.g. if you /boot is encrypted then the EFI file needs to have "luks" or "luks2" module embedded into the EFI file otherwise it has no way to access the encrypted /boot filesystem and AFAIK grub-install looks at the grub.cfg to figure out that /boot is encrypted 2024-01-09 16:40:20 no, for now I try to get simple instaleer 2024-01-09 16:40:34 I was assuming removable based on the "m1-usb.img" filename used for the loop device 2024-01-09 16:40:54 no? no what? I don't understand 2024-01-09 16:41:13 filename is 'artefact' from time when I built removables 2024-01-09 16:41:51 no luks, lvm and other complicated setups 2024-01-09 16:44:33 encryption was just an example to make my point of why I believe grub-install reads grub.cfg (not 100% sure of that as grub-install does also run things like grub-probe) and therefore why I recommended you run grub-mkconfig before it 2024-01-09 16:44:52 I run grub-mkconfig before grub-install in my own script 2024-01-09 16:47:39 grub is 'strange' land for me and overcomplicated IMO 2024-01-09 16:48:58 "it is what it is" 2024-01-09 16:50:16 heh 2024-01-09 16:51:16 any the "--prefix '(,gpt4)/boot/grub'" looks correct as partition 4 is the rootfs containing the /boot/grub directory 2024-01-09 16:51:21 why would it be gpt6? 2024-01-09 16:52:03 it shouldn't but it is 2024-01-09 16:52:17 that is what I asked about 2024-01-09 16:54:59 in the output you provided it is gpt4 as I quoted above 2024-01-09 16:55:04 only what I can tell on fedora this is very diffent 2024-01-09 16:55:40 in grubaa64.efi it is 4 2024-01-09 17:01:23 I guess I could solve this by installing grub on ESP but think it is not good option 2024-01-09 17:01:24 well that's the only output you provided me with to look at... 2024-01-09 17:02:00 IDK what else is needed 2024-01-09 17:02:03 you ARE installing grub (EFI file) on ESP, the rest of Grub however is on the rootfs 2024-01-09 17:02:14 right 2024-01-09 17:03:14 so do you have output showing exactly what you want? do you want grubaa64.efi or bootaa64.efi? do you want to use EFI boot variables? I'd assume so if you want the Mac dual-boot 2024-01-09 17:03:41 if I know I will answer 2024-01-09 17:04:01 I want this to be bootable after install 2024-01-09 17:04:40 are you creating a disk image to later copy onto the Mac? or installing *directly* onto the Mac? 2024-01-09 17:05:34 no, install over http/s 2024-01-09 17:06:05 I already have disk image for installation 2024-01-09 17:06:21 https://arvanta.net/alpine/install-alpine-m1/ 2024-01-09 17:06:44 hah, now nearly 2 years old 2024-01-09 17:11:55 minimal: thanks again for help, I must go out for about one hour so will be AFK 2024-01-09 17:12:11 mps: so you ARE using a disk image? 2024-01-09 17:12:52 asahi installer is complicated thing because apple is complicated 2024-01-09 17:13:55 installer download from net some files and from macos creates partitions and copy files and 'dd' rootFS 2024-01-09 17:14:08 still doesn't change that I need a precise answer to my question before I can help further 2024-01-09 17:14:49 so you're creating the partitions directly on the Mac, not creating a partitioned disk image (like the script you showed me does)? 2024-01-09 17:15:38 question is simple, why grub doesn't set gpt number I want in BOOTAA64.EFI 2024-01-09 17:15:46 and therefore your runnnig grub-install *directly* on the Mac and not as part of any disk image prepation (which that script does) 2024-01-09 17:16:21 no, I have to prepare all these files on other machines and put them on the web 2024-01-09 17:16:40 I cannot attempt to answer the question if I don't understand precisely what you're doing and have grub-install verbose output to look at 2024-01-09 17:17:00 it grub-install runs on M1 machine it does correct things 2024-01-09 17:17:02 "prepare all these files on other machines" - including the Grub EFI file? 2024-01-09 17:17:15 yes 2024-01-09 17:17:33 so you ARE preparing a partitioned disk image to dd onto Mac? 2024-01-09 17:18:14 not disk image, file and root partition image 2024-01-09 17:18:14 or you arre preparing a partitioned disk image to create EFI file and then throwing aware the partitioned disk image once you extract the EFI file from it? 2024-01-09 17:18:22 s/aware/away/ 2024-01-09 17:19:57 in script I posted I created disk image, then copy root partition as image and files from ESP to upload in zip file 2024-01-09 17:21:34 and for now there is no even short guide how asahi installer works, I had to look and guess 2024-01-09 17:21:55 and ask on IRC 2024-01-09 17:23:53 so you are preparing a partitioned disk image to create EFI (and other) files and then throwing away the partitioned disk image once you extract the EFI file from it 2024-01-09 17:24:28 right 2024-01-09 17:24:35 why?? either (a) create a disk image like your script currently does and "dd" it onto the storage device, or (b) set up Grub directly on the Mac 2024-01-09 17:25:01 this is what done 2 years ago 2024-01-09 17:25:23 you're taking a EFI that Grub created BASED ON THE PARTITIONING LAYOUT OF THE DISK IMAGE and then putting it onto an already partitioned Mac and wondering why Grub is "confused" 2024-01-09 17:25:38 it is described here https://arvanta.net/alpine/install-alpine-m1/ 2024-01-09 17:26:40 well, not sure if proper word is confused, I doesn't set proper gpt number in BOOTAA64.EFI 2024-01-09 17:28:17 that article do not default copying any Grub EFI file onto the Mac, it shows grub-install being run on the Mac itself 2024-01-09 17:28:35 right 2024-01-09 17:28:37 s/default/detail/ 2024-01-09 17:29:13 so it is not "this is what done 2 years ago" - you didn't copy the EFI but that is what you are talking about now 2024-01-09 17:29:18 I wanted to tell that I solved problem with intall using removable image earlier 2024-01-09 17:29:21 so it is not the same 2024-01-09 17:29:34 sorry for confusion 2024-01-09 17:29:36 I'm totally confused as to what you're trying to achieve 2024-01-09 17:30:36 I'm trying to 'force' grub to embed desired gpt number in BOOTAA64.EFI 2024-01-09 17:31:10 I know this could be done by hex editor 2024-01-09 17:31:47 and I don't need all these things for me, I'm trying to make asahi installer for alpine users 2024-01-09 17:32:00 when (a) running grub-install directly on the Mac to create the BOOTAA64.EFI file? or (b) when running grub-install on a loopback device to generate BOOTAA64.EFI that you are then going to copy across onto the Mac? 2024-01-09 17:32:40 well, I want to make and publish these scripts for alpine users 2024-01-09 17:32:47 a or b? 2024-01-09 17:33:04 (b) for now 2024-01-09 17:33:26 I don't believe (a) is a valid thing to do 2024-01-09 17:33:45 oops, I meant I don't believe (b) is a valid thing to do 2024-01-09 17:34:07 as the partitioning of the loop device disk image is not 100% identical as the partitioning of the Mac 2024-01-09 17:34:32 for alpine (b) should be option in future 2024-01-09 17:34:43 for example is the Mac's NVME 512 or 4K sectors? 2024-01-09 17:35:06 asahi installer does ok partitioning 2024-01-09 17:36:34 minimal: sorry, I really must go now 2024-01-09 17:36:40 I don't know what "asahi installer" is and so I cannot comment on it 2024-01-09 17:37:08 basically it sounds like you're trying to do something that grub-install isn't really designed to handle 2024-01-09 17:37:35 and whilst they may be other alternative ways to achieve it I do not think to do so is a good idea 2024-01-09 18:35:35 minimal: sorry, I was in a hurry and forgot to tell that I very appreciate your willing to help 2024-01-09 18:37:01 I see that some other distros (debian, fedora ...) solved this problem somehow and had a hope that we also can 2024-01-09 18:37:27 I really don't understand why you do not want to run grub-install on the Mac itself as part of installation 2024-01-09 18:38:04 because it is not possible with asahi installer, at least for now 2024-01-09 18:38:13 https://github.com/AsahiLinux/asahi-installer 2024-01-09 18:39:05 also debian guide and some scripts here https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian/ 2024-01-09 18:40:30 your method is creating a EFI based on the particular "setup" (i.e. partitioning) of the disk image which is different to that of the Mac 2024-01-09 18:40:44 right 2024-01-09 18:40:57 so you could try setting up the disk image to look as close to the Mac's partitioning as possible and that then may work 2024-01-09 18:41:08 I did 2024-01-09 18:41:24 your disk image has 4 partitions, the Mac appears to have at least 6 2024-01-09 18:41:39 but problem is 'embeded' gpt root partition number 2024-01-09 18:42:01 sigh, that is passed on the partitioning grub seeing when you run grub-install 2024-01-09 18:42:11 yes 2024-01-09 18:42:31 if the disk image's partitioning looks like the Mac's partitioning then the generated EFI should have whatever the "correct" value is 2024-01-09 18:42:57 so it seems like the disk image partitioning is NOT like that of the Mac 2024-01-09 18:43:02 asahi installer creates some extra partitions in container, two at least, ESP and one for rootFS 2024-01-09 18:43:15 container? 2024-01-09 18:43:27