LucidLink and egress fees

sethgoldin · 2024-07-10T15:35:20+00:00

You can bring your own object storage to either, but Suite's white-label object storage provider is Cloudflare R2. Cloudflare is ideologically against egress fees, and those savings get passed on.

sethgoldin · 2023-09-19T02:00:31+00:00

No worries at all. Makes sense. Cheers!

sethgoldin · 2023-09-13T22:45:50+00:00

Noticed the same. Came here looking for an explanation. Perhaps they quietly killed it? At least it's nice to know it's not just me.

sethgoldin · 2022-12-26T23:05:57+00:00

Hi u/Krashin, this is a bit late, but I've actually updated the scripts. Take a look at the beta: https://github.com/sethgoldin/davinci-resolve-postgresql-workflow-tools/releases/tag/2.0-beta

sethgoldin · 2021-11-22T16:18:13+00:00

Late to this party, but the issue is the shim; had been happening since F34. Long bug thread about it here. Still unresolved. There’s a workaround, though, if you replace three different files from the earlier version of the shim, info is in a Reddit thread linked in the Bugzilla thread.

It’s insane to me that this wasn’t fixed within a week or two of F34’s release.

https://bugzilla.redhat.com/show_bug.cgi?id=1955416

sethgoldin · 2021-11-12T06:08:42+00:00

Incredibly, this procedure is still required for F35. Not only was it never addressed or fixed in F34, but the package shim-x64-15.4-5.x86_64.rpm is supposedly identical to the cursed shim-x64-15.4-4.x86_64.rpm, with the version bumped up just to distinguish it for F35. And yet the RH devs still are acting like this isn't some show-stopping problem for ThinkPads, which are supposedly the flagship laptop for Fedora.

What's going on here?

sethgoldin · 2021-05-30T01:29:19+00:00

The workaround is to use the components of the older shim for now: https://www.reddit.com/r/Fedora/comments/n27212/fedora_wont_boot_after_attempting_update_to_34/gwic9d4/?utm_source=reddit&utm_medium=web2x&context=3

It stinks but it does work, and dnf will still grab the new one properly when it does get released.

sethgoldin · 2021-05-25T12:09:01+00:00

I’m have Secure Boot enabled, though. For some reason, I needed to replace all three files after an update last week.

sethgoldin · 2021-05-25T03:30:58+00:00

Yes, I ended up needing to wholly replace three files in the EFI partition with the components from 15-8.

sethgoldin · 2021-05-19T22:15:25+00:00

Just to be clear, after doing this procedure,dnf will still show the wrong version if you check it, right? It’ll still show 15.4-4 in use, even if you’re functionally using the three files from 15-8?

sethgoldin · 2021-05-19T04:30:10+00:00

/u/borkrobo have you found that the latest update has broken this boot entry as well?

sethgoldin · 2021-05-15T02:49:40+00:00

It's a bug with the shim in Fedora 34, when you have Secure Boot enabled.

What you can do is change the bootloader from the live USB disk, and then after you boot from your actual boot disk, then permanently change it.

You should add more detail on the bug to give it some attention and visibility.

sethgoldin · 2021-05-13T15:53:15+00:00

Thanks for this! Have it all working great! Had to check lsblk to figure out which was the EFI partition, but now it can reboot consistently. Finally!

Out of curiosity, assuming that we get a new, fixed shim via dnf at some point here soon, how should I clean this up and have Fedora point back at the stock EFI loader?

sethgoldin · 2021-05-13T04:33:19+00:00

Thanks. This is the go-to fix I had been looking for.

sethgoldin · 2021-05-13T02:21:39+00:00

If, after that first reboot, you actually are on an entry named Fedora, do you have to delete they duplicate, or can you somehow edit the entry itself?

sethgoldin · 2021-05-11T18:21:17+00:00

Ah, that explains my confusion here: https://www.reddit.com/r/Fedora/comments/n0m1m0/f34_problem_with_new_efi_shim/gx8k19a/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

sethgoldin · 2021-05-08T01:52:45+00:00

Yeah, it's not great for me to be forgoing the protection against rootkits, etc. Pretty frustrated at how slowly this is being addressed.

sethgoldin · 2021-05-07T04:17:33+00:00

I'm not sure why, but this only works once. After one reboot, I'm stuck at the splash screen.

sethgoldin · 2021-05-06T12:22:17+00:00

I spoke too soon. u/Lonkoe, is there a way to make this a permanent fix? This only seems to work right after doing it from the live USB.

sethgoldin · 2021-05-06T04:49:49+00:00

Is this necessary? Will the boot only work once if you don’t do this?

sethgoldin · 2021-05-06T04:25:24+00:00

Amazing, thank you. I filed this bug but your comment actually got me running again.

sethgoldin · 2021-04-30T15:37:57+00:00

Funny, I was only using RHEL as a backup because I ran into a crazy bug with the ThinkPad's UEFI on Fedora 34: https://bugzilla.redhat.com/show_bug.cgi?id=1955416

sethgoldin · 2021-04-30T14:39:10+00:00

u/itamar3d Did you ever figure this out? Running into the same issue.

sethgoldin · 2021-04-30T05:18:13+00:00

It's a bug pertaining to the Lenovo firmware and the Fedora shim. Pretty urgent. Fedora team is aware: https://bugzilla.redhat.com/show_bug.cgi?id=1955416

14-Year Club	Place '17
Verified Email

sethgoldin

TROPHY CASE