A question about switching kernels

[Francisco Tissera]

Hello everyone,


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, instead of 20.

Is there a way to switch to the new installed kernel and remove the old 
one, is it safe to do so? if so, how?

Thank you for any answer.

Best regards.

Francisco.

[Samuel Sieb]

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, instead of 20.
>  
>  Is there a way to switch to the new installed kernel and remove the old 
>  one, is it safe to do so? if so, how? 
By default, dnf will keep the latest 3 kernels, so you can go back to a 
previous one if something goes wrong.  However, the new kernel should be 
the default one.  Reboot again and make sure you select the latest 
kernel from the grub menu.  Hopefully, it will stick after that.

[Francisco Tissera]

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?

Thanks again.

best regards,

Francisco.

On 3/9/21 9:26 AM, Samuel Sieb wrote:
> 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, instead of 20.
>>
>> Is there a way to switch to the new installed kernel and remove the 
>> old one, is it safe to do so? if so, how?
>
> By default, dnf will keep the latest 3 kernels, so you can go back to 
> a previous one if something goes wrong.  However, the new kernel 
> should be the default one.  Reboot again and make sure you select the 
> latest kernel from the grub menu.  Hopefully, it will stick after that.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Samuel Sieb]

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 latest kernel, or is it unsafe? 
You can remove any kernel that's not the running one.  But it shouldn't 
be necessary.

[George N. White III]

On Tue, 9 Mar 2021 at 07:32, dileepa.tissera dileepa.tissera <
audiogamer2004(a)gmail.com&gt; 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 miss one "error" message.

Can you send the output of "ls -l /boot/vm*", "dnf info
kernel-5.10.19" and
"dnf info kernel-5.10.20"?  Does the system have more than one OS installed?

-- 
George N. White III

[Francisco Tissera]

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 root 10546160 Mar  4 14:32 
/boot/vmlinuz-5.10.20-200.fc33.x86
_64
-rwxr-xr-x. 1 root root 11698160 Oct 15 19:23 
/boot/vmlinuz-5.8.15-301.fc33.x86_
64
[francisco@blueblink ~]$

dnf info kernel-5.10.19
Last metadata expiration check: 0:03:08 ago on Wed 10 Mar 2021 07:46:19 
AM CET.
Error: No matching Packages to list
[francisco@blueblink ~]$
dnf info kernel-5.10.20
Last metadata expiration check: 0:04:51 ago on Wed 10 Mar 2021 07:46:19 
AM CET.
Installed Packages
Name         : kernel
Version      : 5.10.20
Release      : 200.fc33
Architecture : x86_64
Size         : 0.0
Source       : kernel-5.10.20-200.fc33.src.rpm
Repository   : @System
 From repo    : updates
Summary      : The Linux kernel
URL          : https://www.kernel.org/
License      : GPLv2 and Redistributable, no modification permitted
Description  : The kernel meta package
[francisco@blueblink ~]$

I did, just to make sure it would choose the latest kernel version, 
remove 5.10.19, but apparently it didn't work for some odd reason.
Regarding any other OS being installed, no nothing other than Fedora is 
installed on this mac.
On 3/9/21 4:03 PM, George N. White III wrote:
>  On Tue, 9 Mar 2021 at 07:32, dileepa.tissera dileepa.tissera 
>  <audiogamer2004(a)gmail.com <mailto:[e-mail]>> 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 miss one "error" message.
>
>  Can you send the output of "ls -l /boot/vm*", "dnf info 
>  kernel-5.10.19" and "dnf info kernel-5.10.20"?  Does the system have 
>  more than one OS installed?
>
>  -- 
>  George N. White III
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Samuel Sieb]

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?

[Francisco Tissera]

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 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(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Ed Greshko]

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 don't know if you're running secure boot, or if that would make any difference. 
But what is
the output of

sudo grub2-editenv list

As well as....

sudo ls /boot/loader/entries/


-- 
People who believe they don't make mistakes have already made one.

[Francisco Tissera]

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@blueblink ~]$

[francisco@blueblink ~]$ sudo ls /boot/loader/entries/
133a2487cda040dbbe9609f0ab827def-0-rescue.conf
133a2487cda040dbbe9609f0ab827def-5.10.19-200.fc33.x86_64.conf
133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86_64.conf
133a2487cda040dbbe9609f0ab827def-5.8.15-301.fc33.x86_64.conf
[francisco@blueblink ~]$

And, i don't believe secure boot is present on macs, I've never seen it 
at least.
Best regards.
Francisco
On 3/10/21 8:12 AM, Ed Greshko wrote:
> 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 don't know if you're running secure boot, or if that would make any 
> difference.  But what is
> the output of
>
> sudo grub2-editenv list
>
> As well as....
>
> sudo ls /boot/loader/entries/
>
>

[Ed Greshko]

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=133a2487cda040dbbe9609f0ab827def-5.10.19-200.fc33.x86_64
>  menu_auto_hide=1
>  boot_success=1
>  boot_indeterminate=0
>  [francisco@blueblink ~]$
>
>  [francisco@blueblink ~]$ sudo ls /boot/loader/entries/
>  133a2487cda040dbbe9609f0ab827def-0-rescue.conf
>  133a2487cda040dbbe9609f0ab827def-5.10.19-200.fc33.x86_64.conf
>  133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86_64.conf
>  133a2487cda040dbbe9609f0ab827def-5.8.15-301.fc33.x86_64.conf
>  [francisco@blueblink ~]$
>
>  And, i don't believe secure boot is present on macs, I've never seen it at
> least.
> > 
OK....

You can fix it, and boot into 5.10.20-200 by using the following command

sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86"

and rebooting.



-- 
People who believe they don't make mistakes have already made one.

[Francisco Tissera]

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 Greshko wrote:
> sudo grub2-editenv - set 
> "saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86

[Ed Greshko]

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 regards.
>
>  Francisco.
>
>  On 3/10/21 8:28 AM, Ed Greshko wrote:
> > sudo grub2-editenv - set
> "saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86 
Ooops....  It looks like a copy/paste error on my part.

sudo grub2-editenv - set
"saved_entry=133a2487cda040dbbe9609f0ab827def-5.10.20-200.fc33.x86_64"

Good catch.

-- 
People who believe they don't make mistakes have already made one.

[Francisco Tissera]

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

[Ed Greshko]

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.

[Francisco Tissera]

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.

Francisco.

On 3/10/21 8:54 AM, Ed Greshko wrote:
>  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.

[Ed Greshko]

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 happen with a bogus entry.

My system was booted to the 5.10.20-200 kernel and I gave a bogus entry....

[root@f33k ~]# grub2-editenv list
saved_entry=8b511c4b483b4414b7bf742b35809e2c-5.10.19-200.fc33.x86
boot_success=0
boot_indeterminate=0

I then rebooted the system.  The entry above remained unchanged but the system again
booted to the 5.10.20-200 kernel.

So, the good news is that I'd probably wouldn't be responsible for breaking your
system.  The bad
news is that the results would have probably confused the issue even more.

-- 
People who believe they don't make mistakes have already made one.

[Francisco Tissera]

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=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 happen with a 
>  bogus entry.
>
>  My system was booted to the 5.10.20-200 kernel and I gave a bogus 
>  entry....
>
>  [root@f33k ~]# grub2-editenv list
>  saved_entry=8b511c4b483b4414b7bf742b35809e2c-5.10.19-200.fc33.x86
>  boot_success=0
>  boot_indeterminate=0
>
>  I then rebooted the system.  The entry above remained unchanged but 
>  the system again
>  booted to the 5.10.20-200 kernel.
>
>  So, the good news is that I'd probably wouldn't be responsible for 
>  breaking your system.  The bad
>  news is that the results would have probably confused the issue even more.
>
>  -- 
>  People who believe they don't make mistakes have already made one.

[George N. White III]

On Wed, 10 Mar 2021 at 03:23, Francisco Tissera <audiogamer2004(a)gmail.com&gt;
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-linux quotes
Apple:

NOTE: There is currently no trust provided for the Microsoft Corporation
UEFI CA 2011, which would allow verification of code signed by Microsoft
partners. This UEFI CA is commonly used to verify the authenticity of
bootloaders for other operating systems such as Linux variants.

https://www.wikihow.com/Turn-Off-Secure-Boot-on-Mac.

-- 
George N. White III

[Francisco Tissera]

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 
>  <audiogamer2004(a)gmail.com <mailto:[e-mail]>> 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-linux 
>  <https://www.omgubuntu.co.uk/2018/11/apple-t2-chip-cant-boot-linux> 
>  quotes Apple:
>
>  NOTE: There is currently no trust provided for the Microsoft Corporation
>  UEFI CA 2011, which would allow verification of code signed by Microsoft
>  partners. This UEFI CA is commonly used to verify the authenticity of
>  bootloaders for other operating systems such as Linux variants.
>
>  https://www.wikihow.com/Turn-Off-Secure-Boot-on-Mac 
>  <https://www.wikihow.com/Turn-Off-Secure-Boot-on-Mac>;.
>
>  -- 
>  George N. White III
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Samuel Sieb]

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 change 
anything at all.  If you really want to remove it, you need to remove 
"kernel-core" instead.  But you won't be able to remove it until you 
boot the newer kernel because you can't remove the kernel that's 
currently being used.

[Francisco Tissera]

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-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 change 
> anything at all.  If you really want to remove it, you need to remove 
> "kernel-core" instead.  But you won't be able to remove it until you 
> boot the newer kernel because you can't remove the kernel that's 
> currently being used.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Francisco Tissera]

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 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 change 
> anything at all.  If you really want to remove it, you need to remove 
> "kernel-core" instead.  But you won't be able to remove it until you 
> boot the newer kernel because you can't remove the kernel that's 
> currently being used.
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: 
> https://pagure.io/fedora-infrastructure

[Ed Greshko]

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 already made one.

[Francisco Tissera]

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 Greshko wrote:

> 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.
>

[Samuel Sieb]

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"

[Ed Greshko]

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.


-- 
People who believe they don't make mistakes have already made one.

[Francisco Tissera]

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.

Francisco.

On 3/10/21 10:21 AM, Ed Greshko wrote:
> 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.
>
>
> -- 
> People who believe they don't make mistakes have already made one.