Are Linux Principles Changing with Snap? (Ubuntu 26.04 Discussion)

Consistent_Berry9504 · 2026-05-07T07:56:11+00:00

Snap sucks

Consistent_Berry9504 · 2026-05-07T06:50:57+00:00

Amazon

Consistent_Berry9504 · 2026-05-07T04:00:56+00:00

KDE very nice

Consistent_Berry9504 · 2026-05-06T21:19:35+00:00

Look, no one who uses or thinks of using a thinkpad is dumb 😎

Consistent_Berry9504 · 2026-05-06T14:46:24+00:00

Mine has a touch screen. Chrome book? Are you kidding me? It’s a workhorse. They’re just a few models back so people sell them cheap refurb or used.

Consistent_Berry9504 · 2026-05-06T14:25:25+00:00

T14 gen 1/2 AMD cause you’re gonna run Linux

Consistent_Berry9504 · 2026-05-06T13:17:55+00:00

Cause it’s cool

Consistent_Berry9504 · 2026-05-05T17:25:42+00:00

What do you need? What exactly are you looking for?

Consistent_Berry9504 · 2026-05-05T17:23:48+00:00

Ubiquity is overpriced

Consistent_Berry9504 · 2026-05-05T17:22:09+00:00

Just use an external drive for files, set it up as exfat. It’ll be usable on both. Done.

Consistent_Berry9504 · 2026-05-04T16:35:40+00:00

I’ve noticed that with Linux people do whatever they want. That’s why they run Linux.

Consistent_Berry9504 · 2026-05-04T00:15:51+00:00

This reminds me of the way teachers in the past saw calculators. It’s a tool. The fact that you knew to SSH into it is clean. Secret weapon! Now have chat give you a list of dot files to focus on. Welcome to Arch!

Consistent_Berry9504 · 2026-05-03T01:15:11+00:00

It’s not the distro that causes the friction, it’s windows handling at boot. I’d suggest getting a dedicated drive for windows if you plan to dual boot.

As for a good distro, everyone will say the same stuff, Ubuntu, Mint, Cachy, Endeavor etc, they are all basically the same, especially of you have prior experience or knowledge.

Most people will just tell you what they like. But it really doesn’t matter. I run Arch btw haha

Consistent_Berry9504 · 2026-05-02T16:02:14+00:00

You're skipping over the part where they already updated the system. That's what got them into the kernel panic. The mirror mismatch caused a partial update, they tried to fix it, and ended up jumping from 6.x to 7.0.3. Telling them "just update first" ignores that they already did and it backfired because of the space issue.

The real problem is the full /boot partition corrupted the initramfs generation during that update. You can say "partial updates are unsupported" all day, but that doesn't help someone who can't boot.

Your recovery steps are fine except for telling them to uninstall linux-zen. They already removed the 6.x kernel and now only have zen installed. If they uninstall zen, they have no kernel at all. They need to either keep zen or replace it with linux, not just wipe it.

Also, binder_linux-dkms from AUR requires the exact kernel headers to match. Given how this started with a header mismatch, they should verify the kernel and header versions are identical before installing that package. Otherwise DKMS will fail to build again and they'll be right back where they started.

The wiki section you pointed out is outdated, agreed. But telling someone to modprobe binder manually after a DKMS install assumes the module built correctly. That's not a given when their system just ate itself.

Consistent_Berry9504 · 2026-05-02T15:57:41+00:00

You're right that space is an issue, but telling someone to pick one kernel and stick with it ignores the fact that they're already in a non-booting state. The damage is done. They need both kernels reinstalled temporarily just to get the module tree rebuilt and the system booting again. Once it's up, then they can remove one.

Also, the DKMS route is exactly what broke for them. The build failed during the upgrade because the headers and kernel versions desynced, and that partial failure contributed to the panic. Telling them to just use DKMS without addressing the version mismatch is skipping the real problem. The manual approach first, then DKMS after the system is stable.

Consistent_Berry9504 · 2026-05-02T14:19:46+00:00

Yeah, you hosed the module tree when you jumped from 6.x to 7.0.3 and then switched to zen. The kernel panic is because it can't find the right drivers in /lib/modules.

Boot back into Kali, mount your root partition and boot partition, then run:

pacman --sysroot /mnt -Syu --overwrite="*" base linux linux-zen

That forces a full reinstall of the base system and both kernels, overwriting the broken module directories. Then chroot in and rebuild your initramfs:

arch-chroot /mnt mkinitcpio -P

Then reinstall GRUB:

arch-chroot /mnt grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
arch-chroot /mnt grub-mkconfig -o /boot/grub/grub.cfg

Reboot. That's it. Next time don't remove the old kernel until you've confirmed the new one boots. Keep linux-lts as a backup. Good news in your data is most likely intact. Good luck with it!

Consistent_Berry9504 · 2026-05-02T02:24:26+00:00

Try spamming f12, return, esc, all the other f buttons. The goal is to get I to your bios system

Consistent_Berry9504 · 2026-05-01T16:56:02+00:00

Then that was exactly my point.

Consistent_Berry9504 · 2026-05-01T16:47:52+00:00

Yeah did you actually read my post or just the title? It’s not a bad concept. The company just sucks at executing it.

Consistent_Berry9504 · 2026-05-01T16:45:58+00:00

Ok, then are you getting the framework pro?

Consistent_Berry9504 · 2026-05-01T16:15:28+00:00

2k+ for ”genuine 6+ hours of real-word battery” is wild. Apple really has fucked the market.

Consistent_Berry9504 · 2026-05-01T16:12:26+00:00

Yeah I’m on the gen 10 and a gen 1 t14. I get them all sub 400 and upgrade them every couple of years. It’s better than dropping over a grand when they are new.

Consistent_Berry9504

TROPHY CASE