So it’s systems that don’t support EFI that grub breaks?

That was a fun attempt to watch

Sometimes I wonder why do I bother maintaining the pin if people won’t read it anyway and then complain about it.

The pin message has a severe issue

It needs to be read
People able to read wouldn’t have asked a thing written everywhere

needs to be read understood

if i’m not mistaken KDEConnect uses TLS, so it shouldn’t

so it’s systems that don’t support EFI that grub breaks?

https://archlinux.org/news/grub-bootloader-upgrade-and-configuration-incompatibilities/

@C0rn3j there’s work for you (that noone will ever read)

Finally 🙂

I always read

Most don’t read the news too

I always read the pin messages in the Telegram group and use an RSS service (Feeder – in browser and mobile) to receive news from the official Arch Linux website. Helps a lot. thanks to the group moderators for pin important messages to users. @C0rn3j

all you had to do was arch-chroot and run grub-install, which you would’ve known if you clicked the link I sent you after you were too lazy to read the pins

grub-install didn’t work…
Then I had to downgrade.

I’ve just updated my Lenovo laptop, no issues with grub

kernel: Bluetooth: hci0: command 0xfd70 tx timeout
bluetooth not working, any idea how to fix it?

edit:
➜ ~ rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
and btusb is loaded

I tried everything written here https://wiki.archlinux.org/title/bluetooth#bluetoothctl:_No_default_controller_available
But still shows same error

I did grub-install…. didn’t work
grub-mkconfig… didn’t work
Downgraded grub…. still didn’t work

That’s why now I am using systemd-boot

Systemd-boot really is nice, haven’t looked back since i switched a few years ago

I’ve been using systemd-boot for a while now

is good

I update Lenovo Legion. grub failed -> I had to chroot and reinstall, and now I’m typing to you again from it. No big deal other than I’m half drunk and tried to install grub to /boot/efi like 2-3x before I realized I’m a moron and it needed to go on /boot

Otherwise, no big deal. > Although I’m really annoyed that the archiso I have to unblock my damn wifi chip. I had completely forgotten it was a pain to connect to wifi upon initial install and found it was easier to use usb tethering from my mobile to reinstall grub

Nice, few more beers might make it less of a hassle

Whoa, beer. . . what is this a Monday – It’s a tequila night

It wasn’t so bad though.

Regarding the splash, it shows up for just ~0.5s, then it shows the text outputs of the boot process

I’m sorry. I just can’t take anything seriously.

😂 thought it was funny, made me laugh its almost 5am here

Almost 9pm. I gotta get to sleep. I just have fun with all of this. It also helps I’m a raving lunatic alcoholic in the process, but I love all of it and always have good time learning along the way. Even if I break something. Which with arch-chroot as so many are learning with grub – pretty much makes arch impossible to screw up beyond repair

As long as there’s a file system – it’s fixable

Right

Well i used dd to write the arch iso to my usb stick a few days ago.. turns out 4am is a bad time for that and i wrote it to my external 1tb nvme

Huge f

What tool did you use that let you do that? Dd?

Can’t understand whether I should laugh or be sad at this, but that’s nice