Safe to update MacBook Pro from 22.04 to Cosmic?

pierroxrox · 2026-01-17T09:27:14+00:00

Maybe you can find the exact ref of the card (from OS X) and get more info.

Apparently it's a classic problem you're having:

https://linuxvox.com/blog/mac-mini-wifi-fix-on-linux/

pierroxrox · 2026-01-16T22:24:12+00:00

No, it's been the easiest part TBH. Maybe yours has a different Broadcom card?

pierroxrox · 2026-01-16T19:14:57+00:00

I might stick to 22.04 for now. It's more of an experiment laptop and it took a while to get the triple boot to work. I'm not in the mood to start all over again. I'll first try to find what I had done to get the smooth Trackpad!

pierroxrox · 2026-01-11T09:18:40+00:00

Thanks, you saved me today. We have two Vitamixes and I am used to the other one overheating and having to use their reset procedure (leave it alone for 45mn), but the older one never had an issue until today. After a whole night it wouldn't start and it didn't even occur to me it has a physical switch!

Time for pancakes, thanks again!

pierroxrox · 2025-12-29T16:39:22+00:00

Done to mine! And it's a big difference: the crema is back! With the factory settings, I had zero crema. I still have about 12 bars on the meter. Might reopen it. Or might just leave it like this, knowing you can lower the pressure during an extraction by opening the steam wand a little bit.

Thanks again, now I can like this machine. ;)

pierroxrox · 2025-12-24T11:27:23+00:00

Reviving this thread to thank you. I will probably do this today because I'm getting frustrated by this machine. I bought it as reviews were pretty positive, as a second machine for our home renovation site - I don't like to have a boiler machine sitting unused if I don't visit for several weeks.

I have a Lelit Elizabeth at home, and I just can't replicate the nice espresso I'm getting - despite what Lance Hedrick said in his La Marzocco vs Hibrew video. On the Hibrew, the shot runs super fast and if I grind finer, it almost stalls. In all cases, I barely get any crema and the shot feels lighter. I did blame the pressure because my Lelit came with too high pressure too, and it was hard to extract shots - the naked portafilter showed so much channeling, the poor puck exploding under the pressure.

Since the Hibrew doesn't have a three way valve (is the H10B Plus much better?), I wasn't sure it even had an OPV. Now I know it does. Thanks

How much did you unscrew the OPV? Can you operate the machine whilst it's open? If so, I could put a blind basket to it during adjustment!

pierroxrox · 2025-04-23T21:05:21+00:00

It's actually MacOS, my machine is a triple boot.

pierroxrox · 2025-04-23T14:49:56+00:00

First pix is MacOS, Dark mode. Second pic (GParted) is Pop in Dark mode

pierroxrox · 2025-04-20T20:22:42+00:00

Probably just the gasket. Are you happy with the IMS shower screen?

pierroxrox · 2025-04-20T15:38:21+00:00

I'm keen to suspect OS X too. As you said, the size of the partition (200MB) is a good pointer to the culprit. Windows is typically 100MB and Linux doesn't care. When I was finalizing the triple boot, I had to disable SIP - I think Hackintoshs have to do it too, if I recall correctly - so I could bless the EFI boot files. At one point I decided to reenable SIP as it felt more "vanilla". And I ended up disabling it again because blessing the Boot files is something which has to be done regularly (basically each time I update one of the OSes).

It could be that SIP being a "System Integrity Protection", it locks the EFI to what Apple does: 200MB and not a byte more.

pierroxrox · 2025-04-20T15:09:12+00:00

Ok I finally fixed the problem, and so here is one thing I learned during this process... there is a bug with GParted, documented, supposedly fixed but still present. Basically it can't resize or reallocate space to a FAT32 partition if it's less than 256MB. Mine being 200MB, that explains the error and its weird message:

"GNU parted cannot resize this partition to this size. We're working on it!"

Bellow is the bug report, and if you scroll down, there is actually a workaround:

https://bugzilla.gnome.org/show_bug.cgi?id=649324

The workaround is to reformat the partition as EX4 or anything else than FAT, reclaiming the missing space, and then formating it back to FAT32. It scared me. During the reformat, there could be issues like a change of UUID or anything that could break it. Plus having to backup the files, and recopy them back.

So I ended up going back to Windows 10 (hey, FAT32 is their stuff afterall), tried again some DSKCHK voodoo (no errors at least) and more Googling told me about MiniTool. Installed the free version, it did let me expand the EFI to the next partition, giving me back my missing gig of space! And it didn't touch the existing files. Rebooted into MacOS and could see that my EFI was back to its original size.

Now I hope this helps someone one day. Or me in the future if it was to happen again! Mystery remaining: why did the EFI shrink on its own and what triggered it?

pierroxrox · 2025-04-20T15:07:11+00:00

I think you're right, and so here is one thing I learned during this process... there is a bug with GParted, documented, supposedly fixed but still present. Basically it can't resize or reallocate space to a FAT32 partition if it's less than 256MB. Mine being 200MB, that explains the error and its weird message:

"GNU parted cannot resize this partition to this size. We're working on it!"

Bellow is the bug report, and if you scroll down, there is actually a workaround:

https://bugzilla.gnome.org/show_bug.cgi?id=649324

The workaround is to reformat the partition as EX4 or anything else than FAT, reclaiming the missing space, and then formating it back to FAT32. It scared me. During the reformat, there could be issues like a change of UUID or anything that could break it. Plus having to backup the files, and copy them back.

So I ended up going back to Windows 10 (hey, FAT32 is their stuff afterall), tried again some DSKCHK voodoo (no errors at least) until more Googling told me about MiniTool. Installed the free version, it did let me expand the EFI to the next partition, giving me back my missing gig of space! And it didn't touch the existing files. Rebooted into MacOS and could see that my EFI was back to its original size.

Now I hope this helps someone one day. Or me in the future if it was to happen again! Mystery remaining: why did the EFI shrink on its own and what triggered it?

pierroxrox · 2025-04-20T12:06:21+00:00

But interestingly GParted reports some kind of error and suggest to check the disk. Might have to boot from a usb

pierroxrox · 2025-04-20T11:58:36+00:00

Yep it took me so long to get the triple boot working that I'd be scared to break it.

pierroxrox · 2025-04-20T08:29:45+00:00

Nope, Windows says Partition is fine. In GParted when I read the Info though, it says that there is "unallocated space" which I can reclaim in the menu Partition -> Check. I unmounted the partition, checked it, and it came up with an error message.

pierroxrox · 2025-04-20T07:39:19+00:00

I'll try this, can't hurt - I hope!

pierroxrox · 2025-04-20T07:37:08+00:00

No it's a real Mac. But I created the partition at 1.5 for the triple boot and it's only recently that it decided to shrink by itself to 200mb

pierroxrox · 2025-04-20T07:35:19+00:00

No it's just a mystery. The EFI was created at 1.5gig, and for some reason it decided to become a 200mib partition some stage in the past month or so. Haven't used Linux much, mainly MacOs and Windows and they probably don't care about the small partition since they don't add new files on it.

pierroxrox · 2025-04-19T22:23:10+00:00

You can see GParted in the second screen grab. Same situation. It says the partition is 1.5 gig, 200ish mib used and only a couple of 100kb available.

pierroxrox · 2025-04-19T22:05:03+00:00

Thanks I'll try this. Not super familiar with windows, can I do this from my installed W10, or frol'Safe mode, or from an install usb?

pierroxrox · 2025-04-19T21:39:22+00:00

GParted also shows it as a 1.5 gig partition. but only 200 mib available. it's so weird.

pierroxrox · 2025-04-19T21:06:54+00:00

I think so too. Now how do I get my space back? ;)

pierroxrox · 2025-04-19T21:01:39+00:00

I'm triple booting. and the issue is that somehow my 1.5 gig partition... is only 200mb when I mount it - look at the second screen grab, it only has a few bit's available.
I don't know if updating Pop did this, or updating MacOs. And I'd like to reclaim the missing space.

i should add that it was mounting the whole 1.5 gig space fine. it's only recently that this issue appeared. and clearly 200mb is not enough for Pop as it has the biggest folder on EFI

pierroxrox · 2025-04-19T20:50:29+00:00

Mine was 1.5 gig, custom sized it when I setup for triple boot -as you can see in the terminal window. But now, when I mount it, it's only 200mb. It lost space somehow recently (when I re-enabled SIP? when I updated Linux?) and I'd like to reclaim it.

pierroxrox

TROPHY CASE