#Emergency Mode Loop Upon boot (Intel Based Mac)

1 messages · Page 1 of 1 (latest)

frozen mist
#

can you elaborate on the steps you followed in detail starting with the iso you used?

#

Guild?

#

Did you also try installing via a fedora silverblue iso and then rebasing?

#

Also, do you run into the same issue on upstream ublue?

#

Also, did you follow any postinstall steps like kargs?

#

Ok can you check if you get a repro on ublue's silverblue-main?

#

Thanks

#

@celest estuary you didn't set any kargs or do any postinstall stuff right?

#

I see okay

#

Let's see if you can repro on ublue main

#

Either way this might be a novel issue of some kind

#

Odd

#

Should be unnecessary

#

I'm hoping this is a secureblue issue and not an rpm-ostree issue, since that will be much easier to troubleshoot

#

Also in the meantime, can you provide more hardware info

#

Ok cool

#

I don't have time to dig into this right now but usually the process is to check one by one which piece is incompatible with your hardware

#

(It's probably hardened malloc)

#

You can test it by forking secureblue and incrementally disable stuff until you get a build you can rebase to

#

Great, yeah I haven't seen anyone else run into this so you may have discovered it. I recommend starting your fork off by removing hardened malloc since it's almost always the issue 😄

#

Once you've narrowed it down we can figure out a way to get it working without a fork

wise slate
#

I have no idea, I just did whatever bluebuild website took me through and edited the recipe stuff

wise slate
#

Then edit the recipe stuff to use secureblue as it's base but remove hardened malloc and maybe the ld preload too, idk if that just doesn't do anything cuz hardened malloc isn't there

wise slate
frozen mist
#

cosign.pub in the repo, and then the contents of cosign.key go into repo secrets

#

Wait what

#

I'm lost, what does this have to do with getting signing working on bluebuild 🤔

#

I think the secret has a different name but i might be remembering wrong

#

Let me check

#

The secret should be called SIGNING_SECRET not SIGNED_SECRETS

#

Unless they changed it

#

Im not sure what that flag is

#

You don't even need to fork @wise slate 's project you can just rebase to it i think

#

Might be easier

#

ok

#

It doesn't make sense though because you had no issue with silverblue-main

wise slate
wise slate
#

I mean the images too

#

If not they will be deleted eventually

#

Last upload is a month ago

frozen mist
#

But I doubt meddle's issue is caused by a recent package upgrade

#

Next I recommend trying without modprobe changes

#

Could be that some required module for mac is disabled

frozen mist
#

Remove the hardening.conf from modprobe.d in your fork

frozen mist
#

yes, I misremembered the name 🙂

frozen mist
#

yeah you can do a binary search 😄

#

add half, then the other half

#

it's probably something apple related though, try adding firewire back

#

or thunderbolt tbh

#

np

#

in a new drop-in of course

#

and on secureblue itself

#

that way you don't have to modify any files and so you'll continue receiving updates to those files, while still overriding to enable modules you need

#

not sure what you mean

#

you rebase with the usual command

#

did you figure out which module it is?

#

rpm-ostree?

#

you can do this locally lol

#

by editing the file

#

and rebooting

#

phone?

#

i'm lost 😄

#

let me know once you identify the problem module

#

it's probably thunderbolt

frozen mist
#

you don't need your own image. I recommend against it

#

just add a drop-in to /etc/modprobe.d and then rebase

#

to secureblue

#

no need for a custom image

frozen mist
#

awesome, so now you're on secureblue with a one-line modprobe.d drop-in?

celest estuary
#

Emergency Mode Loop Upon boot (Intel Based Mac)

frozen mist
#

is this something you see on secureblue only or ublue too?

frozen mist
#

cool

frozen mist
#

wait. it's not in the image but the kargs?

#

as in, it works fine on secureblue with the kargs removed?

#

ok and then:

ublue, with kargs=?
ublue, without kargs=?

#

there are two issues here i think

#

one could be an issue with opportunistic DoT, which you could try overwriting /etc/systemd/resolved.conf.d/securedns.conf

for the other issue with kargs, you should binary search it to find the problem karg

#

@celest estuary ☝️

frozen mist
#

yes

#

try overwriting the secureblue file

#

rand_mac.conf

frozen mist
#

wait so both issues are fixed? rand_mac override fixed one of them but what fixed the other one?

frozen mist
#

which flag

frozen mist
#

oh, so no kargs issues?

#

nice. so just hfsplus and an rand_mac.conf changes

#

cool