Hello George,
Thanks for that bit of info.
Fortunately enough, then, in this case, mi Mac is a 2017 Air, so I don't
have to worry about it.
Best regards.
Francisco.
On 3/10/21 1:29 PM, George N. White III wrote:
On Wed, 10 Mar 2021 at 03:23, Francisco Tissera
mailto:audiogamer2...@gmail.c
Hello Ed,
LOL, thanks for that one. Yeah, the issue would have been even more
confused indeed.
Best regards.
Francisco.
On 3/10/21 12:07 PM, Ed Greshko wrote:
On 10/03/2021 15:32, Francisco Tissera wrote:
in the command you gave me,
sudo grub2-editenv - set
"saved_entry=133a2487cda040db
On Wed, 10 Mar 2021 at 03:23, Francisco Tissera
wrote:
> [...]
> And, i don't believe secure boot is present on macs, I've never seen it
> at least.
>
Just to keep the record current: Recent macs with T2 chips do use secure
boot, see
https://www.omgubuntu.co.uk/2018/11/apple-t2-chip-cant-boot-li
On 10/03/2021 15:32, Francisco Tissera wrote:
in the command you gave me,
sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86
the entry x64 is absent. Is it normal, is it supposed to be like that?
FWIW, I decided to test on a system here what would ha
Hello,
About the kernel modules, thanks, it's good to know that i don't
necessarily have to rebuild drivers, cause I've done my share of things
to get this mac book air up and running as it should.
And Ed, LOL! I hope your wife is nowhere near your computer right now!
Best regards.
Francis
On 10/03/2021 17:10, Francisco Tissera wrote:
Yeah, it worked, thanks.
Just so you know, you forgot dnf in there.
I hope you don't mind me telling you.
LOL!!!
Not at all. I even forgot to put chestnuts in the rice today. Bad day.
I blame it on my wife cutting my hair and freezing my brain
On 3/10/21 1:10 AM, J.Witvliet--- via users wrote:
Removing any kernel, sure.
But don’t do it on anyone referenced by your bootloader, or you’ll have
to do some repair activities.
What do you mean? Every kernel you install is referenced by the
bootloader. When you remove the kernel, the boo
On 3/10/21 1:10 AM, Francisco Tissera wrote:
Do i have to rebuild drivers and such I've installed after erasing
5.10.19, or do they automatically apply to 20 as well?
Every kernel has its own set of kernel modules. They are never shared.
"rpm -q kernel-modules"
From: "dileepa.tissera dileepa.tissera"
mailto:audiogamer2...@gmail.com>>
Date: Tuesday, 9 March 2021 at 12:32:38
To: "Community support for Fedora users"
mailto:users@lists.fedoraproject.org>>
Subject: RE: A question about switching kernels
Hello Samuel,
Hello Ed,
Yeah, it worked, thanks.
Just so you know, you forgot dnf in there.
I hope you don't mind me telling you.
Do i have to rebuild drivers and such I've installed after erasing
5.10.19, or do they automatically apply to 20 as well?
Best regards.
Francisco.
On 3/10/21 10:05 AM, Ed G
On 10/03/2021 15:54, Francisco Tissera wrote:
Hello Samuel,
The problem is solved.
To uninstall the core, i just do,
sudo dnf remove kernel-core --skip-broken, right?
sudo remove kernel-core-5.10.19-200.fc33
should be sufficient.
--
People who believe they don't make mistakes have alread
Well, you don't, not on purpose.
I know I'm going a little OT, but it's not just on you to assist people,
but it's on them, if they can, and this time I could, to help the helper
out too, if needed.
That's one of the reasons why i really chose Fedora, because of the
community.
Best regards
Hello Samuel,
The problem is solved.
To uninstall the core, i just do,
sudo dnf remove kernel-core --skip-broken, right?
Thanks again for all your help, everyone.
Best regards.
Francisco.
On 3/10/21 8:17 AM, Samuel Sieb wrote:
On 3/9/21 10:59 PM, Francisco Tissera wrote:
rpm -q kernel's
On 10/03/2021 15:43, Francisco Tissera wrote:
But still, I'm glad i caught it.
Not as glad as I am. I normally don't break other people's systems.
--
People who believe they don't make mistakes have already made one.
___
users mailing list -- users
Hello Ed,
Oh... well, i didn't think it was an error really, it was a curiosity.
But still, I'm glad i caught it.
Thanks again.
Best regards.
Francisco.
On 3/10/21 8:41 AM, Ed Greshko wrote:
sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86_64
On 10/03/2021 15:32, Francisco Tissera wrote:
Hello Ed,
Just a curiosity, if you don't mind:
in the command you gave me,
sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86
the entry x64 is absent. Is it normal, is it supposed to be like that?
Best r
Hello Ed,
Just a curiosity, if you don't mind:
in the command you gave me,
sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86
the entry x64 is absent. Is it normal, is it supposed to be like that?
Best regards.
Francisco.
On 3/10/21 8:28 AM, Ed Gr
On 10/03/2021 15:23, Francisco Tissera wrote:
Hello Ed,
This is odd indeed.
Samuel has already explained why this is so...
Anyways, the output of the two commands, of which i understand nothing is,
[francisco@blueblink ~]$ sudo grub2-editenv list
saved_entry=133a2487cda040dbbe9609f0ab82
Hello Samuel,
Yes, i did indeed do dnf remove kernel 5.10.19.
Well, as soon as this issue gets fixed, I'll do as you suggested.
Thanks.
Best regards.
Francisco
On 3/10/21 8:17 AM, Samuel Sieb wrote:
On 3/9/21 10:59 PM, Francisco Tissera wrote:
rpm -q kernel's output is,
kernel-5.10.20-20
Hello Ed,
This is odd indeed.
Anyways, the output of the two commands, of which i understand nothing is,
[francisco@blueblink ~]$ sudo grub2-editenv list
saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.19-200.fc33.x86_64
menu_auto_hide=1
boot_success=1
boot_indeterminate=0
[francisco@bluebl
On 3/9/21 10:59 PM, Francisco Tissera wrote:
rpm -q kernel's output is,
kernel-5.10.20-200.fc33.x86_64
the output of uname -r though, is,
5.10.19-200.fc33.x86_64
From your other email, I suspect you did "dnf remove kernel-5.10.19".
The "kernel" package is just a meta-package, so you didn't
On 10/03/2021 14:59, Francisco Tissera wrote:
rpm -q kernel's output is,
kernel-5.10.20-200.fc33.x86_64
the output of uname -r though, is,
5.10.19-200.fc33.x86_64
That would be very odd.
It would be saying you have only one kernel installed but the kernel you're
running isn't listed.
I d
Hello,
rpm -q kernel's output is,
kernel-5.10.20-200.fc33.x86_64
the output of uname -r though, is,
5.10.19-200.fc33.x86_64
Best regards.
Francisco.
On 3/9/21 11:07 PM, Samuel Sieb wrote:
On 3/9/21 3:32 AM, dileepa.tissera dileepa.tissera wrote:
Interesting thing is, although I installed
Hello George,
Below the output of the 3 commands you requested.
ls -l /boot/vm*
-rwxr-xr-x. 1 root root 11698160 Mar 3 11:14
/boot/vmlinuz-0-rescue-133a2487cda
040dbbe9609f0ab827def
-rwxr-xr-x. 1 root root 10538096 Feb 26 17:36
/boot/vmlinuz-5.10.19-200.fc33.x86
_64
-rwxr-xr-x. 1 root roo
On 3/9/21 3:32 AM, dileepa.tissera dileepa.tissera wrote:
Interesting thing is, although I installed 5.10.20, the only available
version in the grub menu is 5.10.19, strange.
What does "rpm -q kernel" show?
___
users mailing list -- users@lists.fedora
On Tue, 9 Mar 2021 at 07:32, dileepa.tissera dileepa.tissera <
audiogamer2...@gmail.com> wrote:
> Hello Samuel,
>
>
>
> Thank you.
>
> Interesting thing is, although I installed 5.10.20, the only available
> version in the grub menu is 5.10.19, strange.
>
It is easy in the stream of messages to m
Hello Samuel, Thank you.Interesting thing is, although I installed 5.10.20, the only available version in the grub menu is 5.10.19, strange.Best regards.Francisco.From: Samuel SiebSent: Tuesday, March 9, 2021 11:31 AMTo: Community support for Fedora usersSubject: Re: A question about switching
On 3/9/21 1:43 AM, Francisco Tissera wrote:
Oh dear, all right, will see if i can get access to the grub menu, being
blind, i guess I'll have to set the grub timeout to maybe 15 seconds,
just to get it right.
Is there a way to remove the old kernel, if i miraculusly manage to
select the lates
hello Samuel,
Oh dear, all right, will see if i can get access to the grub menu, being
blind, i guess I'll have to set the grub timeout to maybe 15 seconds,
just to get it right.
Is there a way to remove the old kernel, if i miraculusly manage to
select the latest kernel, or is it unsafe?
On 3/8/21 10:55 PM, Francisco Tissera wrote:
Just a few minutes ago, i updated my system, and found out that from
kernel version 5.10.19, there was an upgrade to 5.10.20, which I gladly
did.
Well, when i, after rebooting, typed uname -r, I found out that i was
still using kernel 5.10.19, inst
30 matches
Mail list logo
