I'm glad that this issue has a solution, user Darthvader from Romania liked to spread fud. Darth Vader is a Cyborg may be he is lucky?
|
Quote:
And no, he did not spread FUD. He advocated for LinuxPAM and elogind, and was against adopting Plasma5 "before it's ready" while he had certain expectations from it. And he was against Pure-Alsa. And yes, his English was worst than yours. On contrary, LuckyCyborg advocated Plasma5 as was seen and if Darth Vader remained in this forum, probably they will have ended arguing in long threads. Darth Vader used to make really long threads. But Darth was at his time a distribution maintainer, similar with Didier Spaier, and a C/C++ programmer who written complicated programs in Qt. You have long way until to compare yourself with people of this caliber. Anyway, why did you come here? To stalk LuckyCyborg? You have nothing else to say? |
Quote:
Quote:
|
@adcdam what's your problem with me? What's with all those insinuations and insults? What's with this stalking?
I did not even remember to have an argument with you. You did just hate me? If you don't stop with this behavior, I will raise this issue to Mr. Jeremy, the forum owner. Because what you do is harassment. And for your information I'm not Romanian or Chinese, I'm Russian and I live in Karelia, near Finland. |
Quote:
Code:
a/elilo-3.16-x86_64-13.txz: Rebuilt. |
Quote:
|
Quote:
|
Just rebooted after manually updating elilo. No problems. I haven't tried the 5.19 kernel yet because I didn't keep it.
|
Quote:
https://slackware.uk/cumulative/ |
5.19 works with elilo. :^)
|
Quote:
|
elilo if its not broke dont fix it or do anything with it. I love elilo not as well as lilo prior but its nice bootloader except back when it had a file size issue but that was quickly remedied.
|
what means exactly "manually copy (and rename) the proper elilo binary to your EFI System Partition" ?
Is it copy /boot/elilo-x86_64.efi to /boot/efi/EFI/Slackware/elilo.efi ? |
Quote:
Those failures seems to suggest that the elilo patch is just a workaround and that their remains an underlying problem with the kernel's EFI_STUB when this new "confidential computing" functionality is enabled (CONFIG_AMD_MEM_ENCRYPT). |
|
All times are GMT -5. The time now is 05:50 AM. |