Re: Virtualbox vs VMware for Fedora?

[ToddAndMargo via users]

On 11/30/23 23:11, Thomas Dineen wrote:

"osx unlocker so I can run mac VM's"

Help me out here in that I have very little experience with MAC OS:

Are you running MAC OS in a VM?

if yes how do you purchase MAC OS License?

Thomas Dineen



Hi Thomas,

The OSx license states that you can only run it in a virtual
machine is you first run it on Mac hardware.  So you have to
purchase a Mac and install Fedora on it, then run OSx in a VM.

There are OSx hacks (Hackintosh), that you can
run in a VM, but they are illegal.

OSx does not play well with the other kiddies in the sand box.
It is an Apple thing.

Best to "rent-a-Mac" VM online to test things Mac.

-T

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Virtualbox vs VMware for Fedora?

[ToddAndMargo via users]

On 11/30/23 23:04, Jeffrey Walton wrote:

I don't know how well QEMU/KVM/libvirt handle other disk images, like
from VMware.


I have done it.


My Keeper:

References:
http://serverfault.com/questions/273982/virt-convert-ovf-to-kvm
http://edoceo.com/notabene/ova-to-vmdk-to-qcow2
http://wiki.hackzine.org/sysadmin/kvm-import-ova.html



Converting OVA for use with KVM / QCOW2

The OVA file is nothing more than a TAR archive, containing the .OVF and 
.VMDK files. Easy!


Using Evergreen ILS for example:

~ $ file Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ova:POSIX tar archive (GNU)

I'ts possible to use the tar command to list the contents

~ $ tar -tf Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ovf
Evergreen_trunk_Squeeze-disk1.vmdk

Simply extract those things...

~ $ tar -xvf Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ovf
Evergreen_trunk_Squeeze-disk1.vmdk

Now take a look at the created files The OVF XML file describes the 
image, it makes for some interesting reading about the expectations of 
the running environment.


~ $ file Evergreen_trunk_Squeeze*
Evergreen_trunk_Squeeze-disk1.vmdk: VMware4 disk image
Evergreen_trunk_Squeeze.ova:POSIX tar archive (GNU)
Evergreen_trunk_Squeeze.ovf:XML document text

Recent versions of qemu are able to run directly from the VMDK file, buy 
why do that? Use QCOW2, it's better. Execute: qemu-img -h and the last 
line of output shows the supported formats.


~ $ qemu-img -h |tail -n1
Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat qcow2 
parallels nbd blkdebug sheepdog host_cdrom host_floppy host_device file


Now actually convert it, this may take some time.

~ $ qemu-img convert -O qcow2 Evergreen_trunk_Squeeze-disk1.vmdk 
Evergreen_trunk_Squeeze.qcow2

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NVIDIA RPM DNF Update Issue?

[John Pilkington]

On 01/12/2023 05:57, Michael D. Setzer II via users wrote:



Forgot to add info. In working to get it originally working, had
following instruction from only page that actually worked and
ended up with these packages being installed.

rpm -qa | grep -i nvidia
xorg-x11-drv-nvidia-kmodsrc-535.129.03-2.fc38.x86_64
akmod-nvidia-535.129.03-1.fc38.x86_64
nvidia-driver-cuda-libs-545.23.08-1.fc37.x86_64
nvidia-driver-libs-545.23.08-1.fc37.x86_64
nvidia-driver-545.23.08-1.fc37.x86_64
nvidia-kmod-common-545.23.08-1.fc37.noarch
kmod-nvidia-latest-dkms-545.23.08-1.fc37.x86_64



This is a strange mix of updated fc37 and older fc38 packages.  Do you 
have the fc37 repo enabled?


https://rpmfusion.org/Howto/NVIDIA

sudo dnf install akmod-nvidia  xorg-x11-drv-nvidia-cuda

/!\ Please remember to wait after the RPM transaction ends, until the 
kmod get built. This can take up to 5 minutes on some systems.


John P
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NVIDIA RPM DNF Update Issue?

[Francis . Montagnac]

Hi

On Fri, 01 Dec 2023 09:43:09 + John Pilkington wrote:

> On 01/12/2023 05:57, Michael D. Setzer II via users wrote:
>> rpm -qa | grep -i nvidia
>> xorg-x11-drv-nvidia-kmodsrc-535.129.03-2.fc38.x86_64
>> akmod-nvidia-535.129.03-1.fc38.x86_64
>> nvidia-driver-cuda-libs-545.23.08-1.fc37.x86_64
>> nvidia-driver-libs-545.23.08-1.fc37.x86_64
>> nvidia-driver-545.23.08-1.fc37.x86_64
>> nvidia-kmod-common-545.23.08-1.fc37.noarch
>> kmod-nvidia-latest-dkms-545.23.08-1.fc37.x86_64

> This is a strange mix of updated fc37 and older fc38 packages.  Do you 
> have the fc37 repo enabled?

> https://rpmfusion.org/Howto/NVIDIA

I bet that both the rpmfusion repository and the nvidia one from
https://developer.download.nvidia.com/compute/cuda/repos/ are installed, since
nvidia-driver* is the naming of the RPMs on the later.

They cannot be used at the same time.

I just checked on developer.download.nvidia.com: the last fedora version
available if the fedora37 one.

> /!\ Please remember to wait after the RPM transaction ends, until the 
> kmod get built. This can take up to 5 minutes on some systems.

+1

-- 
francis
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NFS Mount Point Write Failure

[Stephen Morris]

On 30/11/23 22:42, Stephen Morris wrote:
I have a network drive being mounted from the following entry in 
/etc/fstab:


192.168.1.12:/mnt/HD/HD_a2    /mnt/nfs    nfs 
users,nconnect=2,owner,rw,_netdev 0 0


This results in the following definition in /etc/mtab:

192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs 
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,nconnect=2,timeo=600,retran
s=2,sec=sys,mountaddr=192.168.1.12,mountvers=3,mountport=57759,mountproto=udp,local_lock=none,addr=192.168.1.12 
0 0


I can read from the mount point but I can't write to it.
A    touch /mnt/nfs/filetest.txt fails with a read only volume error:

touch: cannot touch '/mnt/nfs/filetest.txt': Read-only file system

Can anyone guide me on what I am doing wrong, I am using F39, and I 
believe the fstab specification worked fine in F38 before I upgraded 
to F39.

This is an old nas device that only support nfsvers=3.
I have resetup the device via its web interface to specify that "All 
Accounts" have read/write on the cifs share the nfs share is on, but I 
still get the write failure.
I also have a cifs share define with myself and my wife having 
read/write access to the cifs share, and when I mount the share I user 
the username and password that has been defined on the server, which 
also happens to match my linux credentials, which mounts successfully, 
but it also it also gets "Access Denied" failures on write.


I'm at a loss to understand why the write access doesn't work under F39, 
as under F38 I uploaded 530 holiday photos from my digital camera to the 
nas device and also used Rawtherapee to write the 530 file format 
converted photos to that nas device as well.


regards,
Steve



regards,
Steve

--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue

[Patrick O'Callaghan]

On Thu, 2023-11-30 at 15:16 -0800, richard emberson wrote:
> Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue
> 
> KDE Screen Issue (or Plasma issue, or...)
> 
> 1) Login screen comes up and can login.
> 2)  KDE screen mix of colors and black... moving mouse and screen
> continues
>    to redraw random colors (but, mostly black).
> 3) Bottom panel (in hide mode) comes up and looks normal. Top ToolBar
>    is drawing like the screen (not normal) but I can tell its being
> drawn
>    ontop of the screen background (different colors/black).
> 5) Firefox comes up rendering like normal.
> 6) Thunderbird asks for password and it comes up drawing like normal.
> 7) Using Mouse Right Button, menu come up (look normal) and can
> 8 "Open Terminal". Kconsole comes up like normal.
> 9) From Kconsole can launch alacritty multiple times all normal.
> 10) Background and ToolBar still not rendering correctly.
> 11) Can move mouse over ToolBar and popups appear. Can also click and
>    launch/hide terminals, firefox, thunderbird when mouse if over
> their
>    position in ToolBar.
> 12) I can render a jpeg photo in eog and it comes up just fine.
> 
> With Fedora 38 KDE Spin I did not have this issue with the background
> or ToolBar.
> So, has anyone seen this behavior?
> Where do I start?
> 

I'd suggest asking on the Fedora KDE list.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NFS Mount Point Write Failure [Resolved]

[Stephen Morris]

On 1/12/23 22:54, Stephen Morris wrote:

On 30/11/23 22:42, Stephen Morris wrote:
I have a network drive being mounted from the following entry in 
/etc/fstab:


192.168.1.12:/mnt/HD/HD_a2    /mnt/nfs    nfs 
users,nconnect=2,owner,rw,_netdev 0 0


This results in the following definition in /etc/mtab:

192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs 
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,nconnect=2,timeo=600,retran
s=2,sec=sys,mountaddr=192.168.1.12,mountvers=3,mountport=57759,mountproto=udp,local_lock=none,addr=192.168.1.12 
0 0


I can read from the mount point but I can't write to it.
A    touch /mnt/nfs/filetest.txt fails with a read only volume error:

touch: cannot touch '/mnt/nfs/filetest.txt': Read-only file system

Can anyone guide me on what I am doing wrong, I am using F39, and I 
believe the fstab specification worked fine in F38 before I upgraded 
to F39.

This is an old nas device that only support nfsvers=3.
I have resetup the device via its web interface to specify that "All 
Accounts" have read/write on the cifs share the nfs share is on, but I 
still get the write failure.
I also have a cifs share define with myself and my wife having 
read/write access to the cifs share, and when I mount the share I user 
the username and password that has been defined on the server, which 
also happens to match my linux credentials, which mounts successfully, 
but it also it also gets "Access Denied" failures on write.


I'm at a loss to understand why the write access doesn't work under 
F39, as under F38 I uploaded 530 holiday photos from my digital camera 
to the nas device and also used Rawtherapee to write the 530 file 
format converted photos to that nas device as well.


regards,
Steve
I stopped the nfs service on the nas and restarted it, and also rebooted 
the nas, and that resolved the nfs write issue and also resolved the 
cifs write issue as well (I hadn't considered this as a requirement as 
this is the first time I've ever had to do this since I bought the nas 4 
or 5 years ago, although having said this occasional electricity 
blackouts may have alleviated the need for this).


regards,
Steve





regards,
Steve

--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue



--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NFS Mount Point Write Failure [Resolved]

[Stephen Morris]

On 1/12/23 23:09, Stephen Morris wrote:

On 1/12/23 22:54, Stephen Morris wrote:

On 30/11/23 22:42, Stephen Morris wrote:
I have a network drive being mounted from the following entry in 
/etc/fstab:


192.168.1.12:/mnt/HD/HD_a2    /mnt/nfs 
   nfs users,nconnect=2,owner,rw,_netdev 0 0


This results in the following definition in /etc/mtab:

192.168.1.12:/mnt/HD/HD_a2 /mnt/nfs nfs 
rw,nosuid,nodev,noexec,relatime,vers=3,rsize=32768,wsize=32768,namlen=255,hard,proto=tcp,nconnect=2,timeo=600,retran
s=2,sec=sys,mountaddr=192.168.1.12,mountvers=3,mountport=57759,mountproto=udp,local_lock=none,addr=192.168.1.12 
0 0


I can read from the mount point but I can't write to it.
A    touch /mnt/nfs/filetest.txt fails with a read only volume error:

touch: cannot touch '/mnt/nfs/filetest.txt': Read-only file system

Can anyone guide me on what I am doing wrong, I am using F39, and I 
believe the fstab specification worked fine in F38 before I upgraded 
to F39.

This is an old nas device that only support nfsvers=3.
I have resetup the device via its web interface to specify that "All 
Accounts" have read/write on the cifs share the nfs share is on, but 
I still get the write failure.
I also have a cifs share define with myself and my wife having 
read/write access to the cifs share, and when I mount the share I 
user the username and password that has been defined on the server, 
which also happens to match my linux credentials, which mounts 
successfully, but it also it also gets "Access Denied" failures on write.


I'm at a loss to understand why the write access doesn't work under 
F39, as under F38 I uploaded 530 holiday photos from my digital 
camera to the nas device and also used Rawtherapee to write the 530 
file format converted photos to that nas device as well.


regards,
Steve
I stopped the nfs service on the nas and restarted it, and also 
rebooted the nas, and that resolved the nfs write issue and also 
resolved the cifs write issue as well (I hadn't considered this as a 
requirement as this is the first time I've ever had to do this since I 
bought the nas 4 or 5 years ago, although having said this occasional 
electricity blackouts may have alleviated the need for this).
What I need to work out now is why on the cifs mount from /etc/fstab the 
mount process is ignoring the "nosetuids" option.


regards,
Steve



regards,
Steve





regards,
Steve

--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue



--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue



--
___
users mailing list --users@lists.fedoraproject.org
To unsubscribe send an email tousers-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report 
it:https://pagure.io/fedora-infrastructure/new_issue




OpenPGP_0x594338B1DE179AB2.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue

[richard emberson]

Where do I find "the Fedora KDE list"?

On 12/1/23 03:56, Patrick O'Callaghan wrote:

On Thu, 2023-11-30 at 15:16 -0800, richard emberson wrote:

Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue

KDE Screen Issue (or Plasma issue, or...)

1) Login screen comes up and can login.
2)  KDE screen mix of colors and black... moving mouse and screen
continues
    to redraw random colors (but, mostly black).
3) Bottom panel (in hide mode) comes up and looks normal. Top ToolBar
    is drawing like the screen (not normal) but I can tell its being
drawn
    ontop of the screen background (different colors/black).
5) Firefox comes up rendering like normal.
6) Thunderbird asks for password and it comes up drawing like normal.
7) Using Mouse Right Button, menu come up (look normal) and can
8 "Open Terminal". Kconsole comes up like normal.
9) From Kconsole can launch alacritty multiple times all normal.
10) Background and ToolBar still not rendering correctly.
11) Can move mouse over ToolBar and popups appear. Can also click and
    launch/hide terminals, firefox, thunderbird when mouse if over
their
    position in ToolBar.
12) I can render a jpeg photo in eog and it comes up just fine.

With Fedora 38 KDE Spin I did not have this issue with the background
or ToolBar.
So, has anyone seen this behavior?
Where do I start?



I'd suggest asking on the Fedora KDE list.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

turn off service that installs sytem updates(kernel) off when one shuts down

[olivares33561 via users]

Dear Fedora users,

The newest kernel was installed via a service that runs automatically.  I use 
command line to install updates.  There is a service that installs system 
updates and installed the kernel which did not boot on this machine. When 
starting the machine it froze and did not boot.  The service installed the 
latest kernel.  How can I prevent it from doing that?

Whenever another kernel comes out, I will give it a try again, but it installs 
the one which does not work on this machine.  I have to remove it manually.  
Removed:
  kernel-6.6.2-201.fc39.x86_64  
  kernel-core-6.6.2-201.fc39.x86_64 
  kernel-modules-6.6.2-201.fc39.x86_64  
  kernel-modules-core-6.6.2-201.fc39.x86_64 
  kernel-modules-extra-6.6.2-201.fc39.x86_64

Complete!


Best Regards,


Antonio 

Sent from ProtonMail, encrypted email based in Switzerland.

Sent with Proton Mail secure email.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: turn off service that installs sytem updates(kernel) off when one shuts down

[Felix Miata]

olivares33561 via users composed on 2023-12-01 13:49 (UTC):

> The newest kernel was installed via a service that runs automatically.  I use 
> command line to install updates.  There is a service that installs system 
> updates and installed the kernel which did not boot on this machine. When 
> starting the machine it froze and did not boot.  The service installed the 
> latest kernel.  How can I prevent it from doing that?
 How I do it:
# grep kernel /etc/dnf/dnf.conf
exclude= kernel* plymouth*
#
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Upgrade KDE Wayland Spin 38->39 KDE Background Screen Issue

[Patrick O'Callaghan]

On Fri, 2023-12-01 at 05:43 -0800, richard emberson wrote:
> Where do I find "the Fedora KDE list"?

k...@lists.fedoraproject.org

but I see you found it.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

how to remove unwanted old kernels.

[home user]

Good morning,

After yesterday's weekly patches via "dnf upgrade", I have more old kernels 
than I want.  I also have 2 memtest entries in the grub menu.

What is the current, simple, best practice f38 way of removing the oldest 
kernel, both from the hard drive and from the grub menu?

What is the current, simple, best practice, f38 way of removing the oldest 
memtest, both from the hard drive (if it's there) and from the grub menu?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NVIDIA RPM DNF Update Issue?

[Tim via users]

On Fri, 2023-12-01 at 09:43 +, John Pilkington wrote:
> /!\ Please remember to wait after the RPM transaction ends, until the 
> kmod get built. This can take up to 5 minutes on some systems.

Don't they bother to do anything to let you know when it's finished?
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Tim via users]

On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
> What is the current, simple, best practice, f38 way of removing the
> oldest memtest, both from the hard drive (if it's there) and from
> the grub menu?

It *ought* to be as simple as

dnf remove kernel.

Where you use a specific kernel package version name.  And it does
everything.

Which is pretty much happens when you install a new kernel update and
it removed the oldest one, automatically.

You can play with the DNF configuration files to specify how many
kernels (install-only packages) to keep on your system, and let it
automatically handle this for you.  But I always suggest keeping more
than 3, I go for 5.  It might be some time before you notice that a
kernel update has caused a problem, and it's handy to be able to go
back more than just one, to test things.

-- 
 
uname -rsvp
Linux 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 10:06 AM, Tim via users wrote:

On Fri, 2023-12-01 at 09:11 -0700, home user wrote:

What is the current, simple, best practice, f38 way of removing the
oldest memtest, both from the hard drive (if it's there) and from
the grub menu?


It *ought* to be as simple as

dnf remove kernel.

Where you use a specific kernel package version name.  And it does
everything.

Which is pretty much happens when you install a new kernel update and
it removed the oldest one, automatically.

You can play with the DNF configuration files to specify how many
kernels (install-only packages) to keep on your system, and let it
automatically handle this for you.  But I always suggest keeping more
than 3, I go for 5.  It might be some time before you notice that a
kernel update has caused a problem, and it's handy to be able to go
back more than just one, to test things.



Because of past problems with hard drive space when doing upgrades, I've got it 
set to keep 3.  (installonly_limit=3).
How do I get the full "name" of the kernel to be deleted without re-booting (so 
I can see the grub menu)?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NVIDIA RPM DNF Update Issue?

[Francis . Montagnac]

On Sat, 02 Dec 2023 03:32:04 +1030 Tim via users wrote:

> On Fri, 2023-12-01 at 09:43 +, John Pilkington wrote:
>> /!\ Please remember to wait after the RPM transaction ends, until the 
>> kmod get built. This can take up to 5 minutes on some systems.

> Don't they bother to do anything to let you know when it's finished?

This will hopefully come:

  https://bugzilla.redhat.com/show_bug.cgi?id=2011120

-- 
francis
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Patrick O'Callaghan]

On Fri, 2023-12-01 at 10:28 -0700, home user wrote:
> On 12/1/23 10:06 AM, Tim via users wrote:
> > On Fri, 2023-12-01 at 09:11 -0700, home user wrote:
> > > What is the current, simple, best practice, f38 way of removing
> > > the
> > > oldest memtest, both from the hard drive (if it's there) and from
> > > the grub menu?
> > 
> > It *ought* to be as simple as
> > 
> > dnf remove kernel.
> > 
> > Where you use a specific kernel package version name.  And it does
> > everything.
> > 
> > Which is pretty much happens when you install a new kernel update
> > and
> > it removed the oldest one, automatically.
> > 
> > You can play with the DNF configuration files to specify how many
> > kernels (install-only packages) to keep on your system, and let it
> > automatically handle this for you.  But I always suggest keeping
> > more
> > than 3, I go for 5.  It might be some time before you notice that a
> > kernel update has caused a problem, and it's handy to be able to go
> > back more than just one, to test things.
> > 
> 
> Because of past problems with hard drive space when doing upgrades,
> I've got it set to keep 3.  (installonly_limit=3).
> How do I get the full "name" of the kernel to be deleted without re-
> booting (so I can see the grub menu)?

'rpm -qa kernel' will list all the installed kernels. The one to be
deleted on the next dnf update will be the oldest.

poc
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Joe Zeff]

On 12/01/2023 11:53 AM, Patrick O'Callaghan wrote:

'rpm -qa kernel' will list all the installed kernels. The one to be
deleted on the next dnf update will be the oldest.


Fedora once supplied a program to remove all kernels except the running 
one and the newest.  It's rather old (2011) but should still work.  If 
you want it, ask off-list and I'll send you a copy.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Jeffrey Walton]

On Fri, Dec 1, 2023 at 11:12 AM home user  wrote:
>
> Good morning,
>
> After yesterday's weekly patches via "dnf upgrade", I have more old kernels 
> than I want.  I also have 2 memtest entries in the grub menu.
>
> What is the current, simple, best practice f38 way of removing the oldest 
> kernel, both from the hard drive and from the grub menu?
>
> What is the current, simple, best practice, f38 way of removing the oldest 
> memtest, both from the hard drive (if it's there) and from the grub menu?

See 
.
You should change '--latest-limit=-1' to suit your taste. -1 keeps the
current kernel only; -2 keeps the current and previous kernel, etc.

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: turn off service that installs sytem updates(kernel) off when one shuts down

[Samuel Sieb]

On 12/1/23 05:49, olivares33561 via users wrote:

The newest kernel was installed via a service that runs automatically.  I use 
command line to install updates.  There is a service that installs system 
updates and installed the kernel which did not boot on this machine. When 
starting the machine it froze and did not boot.  The service installed the 
latest kernel.  How can I prevent it from doing that?


Open the Software app and change the settings.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 11:53, Patrick O'Callaghan wrote:

On Fri, 2023-12-01 at 10:28 -0700, home user wrote:

On 12/1/23 10:06 AM, Tim via users wrote:

On Fri, 2023-12-01 at 09:11 -0700, home user wrote:

What is the current, simple, best practice, f38 way of removing
the
oldest memtest, both from the hard drive (if it's there) and from
the grub menu?


It *ought* to be as simple as

dnf remove kernel.

Where you use a specific kernel package version name.  And it does
everything.

Which is pretty much happens when you install a new kernel update
and
it removed the oldest one, automatically.

You can play with the DNF configuration files to specify how many
kernels (install-only packages) to keep on your system, and let it
automatically handle this for you.  But I always suggest keeping
more
than 3, I go for 5.  It might be some time before you notice that a
kernel update has caused a problem, and it's handy to be able to go
back more than just one, to test things.



Because of past problems with hard drive space when doing upgrades,
I've got it set to keep 3.  (installonly_limit=3).
How do I get the full "name" of the kernel to be deleted without re-
booting (so I can see the grub menu)?


'rpm -qa kernel' will list all the installed kernels. The one to be
deleted on the next dnf update will be the oldest.


The rpm command did not give me enough information, so I had to do the 
reboot.  The grub menu shows 4 kernels and 2 memtests (manually typed):

--
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
(the rescue kernel)
Memtest86+ (memtest86+x64.bin-6.20...
Fedora Memtest memtest86+-5.31...
(windows)
--
The rpm command
--
bash.27[~]: rpm -qa  kernel
kernel-6.5.5-200.fc38.x86_64
kernel-6.5.12-200.fc38.x86_64
kernel-6.6.2-101.fc38.x86_64
bash.28[~]: rpm -qa memtest86+
memtest86+-6.20-4.fc38.x86_64
bash.29[~]:
--
The "dnf upgrade" did fine, as Patrick described, for a few weeks, but 
not yesterday.  Trying the "dnf remove"...

--
bash.29[~]: dnf remove kernel-6.6.2-101.fc38.x86_64
Dependencies resolved.
==
 Package  Architecture Version 
 Repository  Size

==
Removing:
 kernel   x86_64 6.6.2-101.fc38 
   @updates   0


Transaction Summary
==
Remove  1 Package

Freed space: 0
Is this ok [y/N]: y
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing:
  1/1
  Erasing  : kernel-6.6.2-101.fc38.x86_64
  1/1
  Running scriptlet: kernel-6.6.2-101.fc38.x86_64
  1/1
  Verifying: kernel-6.6.2-101.fc38.x86_64
  1/1

Removed:
  kernel-6.6.2-101.fc38.x86_64


Complete!
bash.30[~]: dnf remove memtest86+-5.31
No match for argument: memtest86+-5.31
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!
bash.31[~]: ls /boot
config-6.5.10-200.fc38.x86_64 initramfs-6.5.8-200.fc38.x86_64.img 
System.map-6.5.10-200.fc38.x86_64
config-6.5.12-200.fc38.x86_64 initramfs-6.6.2-101.fc38.x86_64.img 
System.map-6.5.12-200.fc38.x86_64
config-6.5.8-200.fc38.x86_64 loader 
System.map-6.5.8-200.fc38.x86_64
config-6.6.2-101.fc38.x86_64 lost+found 
System.map-6.6.2-101.fc38.x86_64

efi memtest86+x64.bin vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
grub2 symvers-6.5.10-200.fc38.x86_64.xzvmlinuz-6.5.10-200.fc38.x86_64
initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img 
symvers-6.5.12-200.fc38.x86_64.xzvmlinuz-6.5.12-200.fc38.x86_64
initramfs-6.5.10-200.fc38.x86_64.img symvers-6.5.8-200.fc38.x86_64.xz 
 vmlinuz-6.5.8-200.fc38.x86_64
initramfs-6.5.12-200.fc38.x86_64.img symvers-6.6.2-101.fc38.x86_64.xz 
 vmlinuz-6.6.2-101.fc38.x86_64

bash.32[~]:
--
There's still too-old files in "/boot".
(rebooting so I can see the grub menu again)
The grub menu is unchanged.

(Jeffrey said)
> See  offline/#sect-clean-up-old-kernels>.
The script there uses the same dnf command that Patrick suggested.

I don't think Patrick's suggestion was wrong.  Rather, the situation is 
messier.  I recall seeing warnings and errors during yesterday's 
patching.  All were during the clean-up phase.  So I hunted through the 
logs.  I've attached a text file of what might be relevant lines, along 
with adjacent lines for context.  They are a

Re: how to remove unwanted old kernels.

[Joe Zeff]

On 12/01/2023 03:25 PM, home user wrote:
The rpm command did not give me enough information, so I had to do the 
reboot.


You could always look in /boot and see what's there.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 3:36 PM, Joe Zeff wrote:

On 12/01/2023 03:25 PM, home user wrote:

The rpm command did not give me enough information, so I had to do the reboot.


You could always look in /boot and see what's there.
--

That was a part of that same post.  Here it is again:
--
bash.1[~]: ls /boot
config-6.5.10-200.fc38.x86_64
config-6.5.12-200.fc38.x86_64
config-6.5.8-200.fc38.x86_64
config-6.6.2-101.fc38.x86_64
efi
grub2
initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img
initramfs-6.5.10-200.fc38.x86_64.img
initramfs-6.5.12-200.fc38.x86_64.img
initramfs-6.5.8-200.fc38.x86_64.img
initramfs-6.6.2-101.fc38.x86_64.img
loader
lost+found
memtest86+x64.bin
symvers-6.5.10-200.fc38.x86_64.xz
symvers-6.5.12-200.fc38.x86_64.xz
symvers-6.5.8-200.fc38.x86_64.xz
symvers-6.6.2-101.fc38.x86_64.xz
System.map-6.5.10-200.fc38.x86_64
System.map-6.5.12-200.fc38.x86_64
System.map-6.5.8-200.fc38.x86_64
System.map-6.6.2-101.fc38.x86_64
vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
vmlinuz-6.5.10-200.fc38.x86_64
vmlinuz-6.5.12-200.fc38.x86_64
vmlinuz-6.5.8-200.fc38.x86_64
vmlinuz-6.6.2-101.fc38.x86_64
bash.2[~]:
--
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Virtualbox vs VMware for Fedora?

[Sbob]

How is the virtual networking in QEMU/KVM/libvirt? can I just click into 
settings and 'add' a network interface?



On 12/1/23 01:17, ToddAndMargo via users wrote:

On 11/30/23 23:04, Jeffrey Walton wrote:

I don't know how well QEMU/KVM/libvirt handle other disk images, like
from VMware.


I have done it.


My Keeper:

References:
http://serverfault.com/questions/273982/virt-convert-ovf-to-kvm
    http://edoceo.com/notabene/ova-to-vmdk-to-qcow2
    http://wiki.hackzine.org/sysadmin/kvm-import-ova.html



Converting OVA for use with KVM / QCOW2

The OVA file is nothing more than a TAR archive, containing the .OVF 
and .VMDK files. Easy!


Using Evergreen ILS for example:

~ $ file Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ova:    POSIX tar archive (GNU)

I'ts possible to use the tar command to list the contents

~ $ tar -tf Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ovf
Evergreen_trunk_Squeeze-disk1.vmdk

Simply extract those things...

~ $ tar -xvf Evergreen_trunk_Squeeze.ova
Evergreen_trunk_Squeeze.ovf
Evergreen_trunk_Squeeze-disk1.vmdk

Now take a look at the created files The OVF XML file describes the 
image, it makes for some interesting reading about the expectations of 
the running environment.


~ $ file Evergreen_trunk_Squeeze*
Evergreen_trunk_Squeeze-disk1.vmdk: VMware4 disk image
Evergreen_trunk_Squeeze.ova:    POSIX tar archive (GNU)
Evergreen_trunk_Squeeze.ovf:    XML document text

Recent versions of qemu are able to run directly from the VMDK file, 
buy why do that? Use QCOW2, it's better. Execute: qemu-img -h and the 
last line of output shows the supported formats.


~ $ qemu-img -h |tail -n1
Supported formats: raw cow qcow vdi vmdk cloop dmg bochs vpc vvfat 
qcow2 parallels nbd blkdebug sheepdog host_cdrom host_floppy 
host_device file


Now actually convert it, this may take some time.

~ $ qemu-img convert -O qcow2 Evergreen_trunk_Squeeze-disk1.vmdk 
Evergreen_trunk_Squeeze.qcow2

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Samuel Sieb]

On 12/1/23 14:25, home user wrote:
The rpm command did not give me enough information, so I had to do the 
reboot.  The grub menu shows 4 kernels and 2 memtests (manually typed):


How did it not give you enough information?  What were you looking for?


Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...


4 of the same version?


bash.29[~]: dnf remove kernel-6.6.2-101.fc38.x86_64
Freed space: 0


"kernel" is a meta package as you can see it doesn't take any space.  It 
works for installing to bring in the right dependencies, but it doesn't 
work for removing.  You need to remove "kernel-core" instead.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: NVIDIA RPM DNF Update Issue?

[Michael D. Setzer II via users]

On 1 Dec 2023 at 18:43, francis.montag...@inria.fr wrote:

From:   francis.montag...@inria.fr
To: Community support for Fedora users 

Subject:Re: NVIDIA RPM DNF Update Issue?
Date sent:  Fri, 01 Dec 2023 18:43:31 +0100
Send reply to:  Community support for Fedora users 


> On Sat, 02 Dec 2023 03:32:04 +1030 Tim via users wrote:
> 
> > On Fri, 2023-12-01 at 09:43 +, John Pilkington wrote:
> >> /!\ Please remember to wait after the RPM transaction ends, until the 
> >> kmod get built. This can take up to 5 minutes on some systems.
> 
> > Don't they bother to do anything to let you know when it's finished?
> 
> This will hopefully come:
> 
>   https://bugzilla.redhat.com/show_bug.cgi?id=2011120
> 
> -- 
> francis

Followed instruction that removed all nvida packages.
rpm -qa | grep -i nvidia 
now shows nothing.

Tried to install but get message about filtering??

dnf install xorg-x11-drv-nvidia-cuda
Last metadata expiration check: 0:21:52 ago on Sat 02 Dec 2023 
09:15:52 AM ChST.
All matches were filtered out by modular filtering for argument: 
xorg-x11-drv-nvidia-cuda
Error: Unable to find a match: xorg-x11-drv-nvidia-cuda

Machine boots without nvidia packages, and BOINC is still running 
with the 6 CPU options, so not sure what driver it is actually 
using?? Machine doesn't actually have a monitor connected, so all 
access is via turbovnc.

BOINC message now showing [---] No usable GPUs found
Before it was seeing it, so not sure what it is actually seeing as the 
video card. Recall at one point having to disable the Noveau?

lsmod | grep -i nvidia
nvidia_drm 94208  0
nvidia_modeset   1556480  1 nvidia_drm
nvidia  62758912  1 nvidia_modeset
video  77824  2 asus_wmi,nvidia_modeset

So without xorg-x11-drv-nvidia-cuda
BOINC doesn't seem to show the GPU as usuable?



> --
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue


++
 Michael D. Setzer II - Computer Science Instructor (Retired) 
 mailto:mi...@guam.net
 mailto:msetze...@gmail.com
 mailto:msetze...@gmx.com
 Guam - Where America's Day Begins
 G4L Disk Imaging Project maintainer 
 http://sourceforge.net/projects/g4l/
++


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 16:41, Samuel Sieb wrote:

On 12/1/23 14:25, home user wrote:
The rpm command did not give me enough information, so I had to do the 
reboot.  The grub menu shows 4 kernels and 2 memtests (manually typed):


How did it not give you enough information?  What were you looking for?


I was looking for the part of the name that, in the "dnf remove" 
command, goes after "kernel", or as you say "kernel-core".  The rpm 
command listed 3 kernels, but the grub menu listed 4.  Not enough 
information to complete the dnf command argument.  I had to reboot to 
see the grub menu to get that.





Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.6.2-101.fc38.x86_64...


4 of the same version?


sigh
I selected the first line and pasted it 3 times, intending to then 
change a few characters in each line.  I forgot to do the edits.  It 
should be:

Fedora Linux (6.6.2-101.fc38.x86_64...
Fedora Linux (6.5.12-200.fc38.x86_64...
Fedora Linux (6.5.10-200.fc38.x86_64...
Fedora Linux (6.5.8-200.fc38.x86_64...

I need a drink.
Someone please e-mail a tall, cool one to me!




bash.29[~]: dnf remove kernel-6.6.2-101.fc38.x86_64
Freed space: 0


I didn't notice that.
Worse, the version was wrong.  6.6.2-101 is the current version.  I 
should have tried to remove 6.5.8-200 (based on the grub menu).


"kernel" is a meta package as you can see it doesn't take any space.  It 
works for installing to bring in the right dependencies, but it doesn't 
work for removing.  You need to remove "kernel-core" instead.


sigh
and now you know I really am no sys.admin.

Using the wrong version in the "dnf remove" may have caused more problems:
-
bash.1[~]: dnf remove kernel-core-6.5.8-200.fc38.x86_64
No match for argument: kernel-core-6.5.8-200.fc38.x86_64
No packages marked for removal.
Dependencies resolved.
Nothing to do.
Complete!
bash.2[~]: rpm -qa kernel
kernel-6.5.5-200.fc38.x86_64
kernel-6.5.12-200.fc38.x86_64
bash.3[~]:
-
6.6.2-101 (the current kernel) is gone.

I'm saving this draft and rebooting to see what's now in the grub menu.
(reboot)
I'm back.
The grub menu has not changed; it still has the same 4 kernels and 2 
memtests.


Curious: 6.6.2-101 seems to still be booting:
-
bash.2[~]: uname -a
Linux coyote 6.6.2-101.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Nov 22 
21:31:13 UTC 2023 x86_64 GNU/Linux

bash.3[~]:
-

I'm really lost now.
I'm no sys.admin.
This is a 10+ year old home workstation; dual boot (Fedora + windows).
I need step-by-step instructions.

...and I need a vacation after the tall, cool one!


--

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[old sixpack13]

...
> 
> What is the current, simple, best practice f38 way of removing the oldest 
> kernel, both
> from the hard drive and from the grub menu?
> 
> What is the current, simple, best practice, f38 way of removing the oldest 
> memtest, both
> from the hard drive (if it's there) and from the grub menu?

rpm -q kernel-core
will list all install kernels
sudo dnf remove kernel-core-

kernel-core is a metapackages and will remove all kernel packages belonging to 
a kernel version

rpm -q memtest 
or
rpm -qa | grep memtest
sudo dnf remove 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Virtualbox vs VMware for Fedora?

[old sixpack13]

...
>    -  can I run the osx unlocker with virtualbox?
> 
> 
>    - does virtualbox have the same issues where it needs a patch after 
> each kernel and sometimes
>     just breaks with a new kernel , even with the patch?
> 
I don't know if it also happens with OSX, but Vbox has issues with kernel 
Version > 6.6.x. 
guest and module compile is working though, but not without a crash on command 
line
see:
https://www.virtualbox.org/ticket/21898
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[old sixpack13]

> 
> I'm no sys.admin.

tomorrow you *are* the sys.admin !
;-)
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Samuel Sieb]

On 12/1/23 16:50, home user wrote:

Using the wrong version in the "dnf remove" may have caused more problems:
-
bash.1[~]: dnf remove kernel-core-6.5.8-200.fc38.x86_64
No match for argument: kernel-core-6.5.8-200.fc38.x86_64


You mentioned in a previous email that there was a rescue kernel.  That 
one isn't tracked by any package.  You can delete the files and the next 
kernel install will update it with the latest kernel.
The grub entries are in /boot/loader/entries/ and you'll see one with 
"rescue" in the name.



bash.2[~]: rpm -qa kernel
kernel-6.5.5-200.fc38.x86_64
kernel-6.5.12-200.fc38.x86_64


I don't know what you mean about this not providing the information you 
need.  That's the full version string there.  Just change "kernel" to 
"kernel-core".



bash.3[~]:
-
6.6.2-101 (the current kernel) is gone.

I'm saving this draft and rebooting to see what's now in the grub menu.
(reboot)
I'm back.
The grub menu has not changed; it still has the same 4 kernels and 2 
memtests.


Curious: 6.6.2-101 seems to still be booting:


You only removed the "kernel" package which has nothing in it. 
Everything else is still there.


rpm -qa kernel-core
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Samuel Sieb]

On 12/1/23 17:23, old sixpack13 wrote:

...


What is the current, simple, best practice f38 way of removing the oldest 
kernel, both
from the hard drive and from the grub menu?

What is the current, simple, best practice, f38 way of removing the oldest 
memtest, both
from the hard drive (if it's there) and from the grub menu?


rpm -q kernel-core
will list all install kernels
sudo dnf remove kernel-core-

kernel-core is a metapackages and will remove all kernel packages belonging to 
a kernel version


Not quite.  "kernel" is the metapackage and only works for installing. 
"kernel-core" is what everything depends on, so removing it will remove 
the others.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Virtualbox vs VMware for Fedora?

[ToddAndMargo via users]

On 12/1/23 15:32, Sbob wrote:
How is the virtual networking in QEMU/KVM/libvirt? can I just click into 
settings and 'add' a network interface?


Yes.  Lots of options

https://imgur.com/sOgQTvW.png
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 6:44 PM, Samuel Sieb wrote:

On 12/1/23 16:50, home user wrote:

Using the wrong version in the "dnf remove" may have caused more problems:
-
bash.1[~]: dnf remove kernel-core-6.5.8-200.fc38.x86_64
No match for argument: kernel-core-6.5.8-200.fc38.x86_64


You mentioned in a previous email that there was a rescue kernel.  That one 
isn't tracked by any package.  You can delete the files and the next kernel 
install will update it with the latest kernel.


The rescue kernel is not the issue here.  I included it in the grub menu list 
for completeness.


The grub entries are in /boot/loader/entries/ and you'll see one with "rescue" 
in the name.


Not the focus of this thread.




bash.2[~]: rpm -qa kernel
kernel-6.5.5-200.fc38.x86_64
kernel-6.5.12-200.fc38.x86_64


I don't know what you mean about this not providing the information you need.  That's the full 
version string there.  Just change "kernel" to "kernel-core".

The rpm command listed 3 kernels, but the grub menu listed 4.  So I had to 
reboot to see the grub menu to know what the oldest kernel is.  By now, I have 
a hand-written list of the 4 kernels in the grub menu.  The oldest is 
6.5.8-200.  Notice that that one is not in the rpm output.  It's the 6.5.8-200 
that I want deleted.

But...
I'm now noticing that the rpm output is listing kernels that are not in the grub menu.  As was 
suggested, listing "kernel-core" rather than "kernel"...
-
-bash.8[~]: rpm -qa kernel-core
kernel-core-6.5.5-200.fc38.x86_64
kernel-core-6.5.12-200.fc38.x86_64
kernel-core-6.6.2-101.fc38.x86_64
-bash.9[~]:
-
So...
6.5.10 is in the grub menu, but not the rpm -qa kernel-core output.
6.5.8 is in the grub menu, but not the rpm -qa kernel-core output.
6.5.5 is in the rpm -qa kernel-core output, but not the grub menu.

6.6.2 is in both, no problem.
6.5.12 is in both, no problem.

Looking at /boot, I see 4 kernel versions of
"config*.fc38.x86_64"
"initramfs-*.fc38.x86_64.img"
"symvers-*.fc38.x86_64.xz"
"System.map-*.fc38.x86_64" and
"vmlinuz-*.fc38.x86_64".
The versions are
6,6,2
6.5.12
6.5.10 and
6.5.8
Those match the grub menu, but not the rpm -qa kernel-core output.

The /boot/loader/entries/ kernel listing matches the grub menu, but not the rpm 
-qa kernel-core output.

What I want for the kernels:
the grub menu
the rpm -qa kernel-core output
the /boot listing
the /boot/loader/entries/ listing
to all match, and all out-of-date files gone.




bash.3[~]:
-
6.6.2-101 (the current kernel) is gone.

I'm saving this draft and rebooting to see what's now in the grub menu.
(reboot)
I'm back.
The grub menu has not changed; it still has the same 4 kernels and 2 memtests.

Curious: 6.6.2-101 seems to still be booting:


You only removed the "kernel" package which has nothing in it. Everything else 
is still there.

rpm -qa kernel-core
--


I get the impression from what you say that my having removed the "kernel" 
package, though wrong, will not cause problems for future weekly patches.  Is my 
impression correct?
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Samuel Sieb]

On 12/1/23 18:46, home user wrote:

On 12/1/23 6:44 PM, Samuel Sieb wrote:
You mentioned in a previous email that there was a rescue kernel.  
That one isn't tracked by any package.  You can delete the files and 
the next kernel install will update it with the latest kernel.


The rescue kernel is not the issue here.  I included it in the grub menu 
list for completeness.


It wasn't clear that it was a separate entry since it didn't have a version.

The /boot/loader/entries/ kernel listing matches the grub menu, but not 
the rpm -qa kernel-core output.


It would, since that's where the grub menu list comes from.


What I want for the kernels:
the grub menu
the rpm -qa kernel-core output
the /boot listing
the /boot/loader/entries/ listing
to all match, and all out-of-date files gone.


Remove the files for the entry that doesn't have a kernel package.

I don't know why you have a kernel package without a grub entry, but I 
wouldn't be surprised if it's related the entry that doesn't have a 
package.  After a couple more kernel updates it should all match.


I get the impression from what you say that my having removed the 
"kernel" package, though wrong, will not cause problems for future 
weekly patches.  Is my impression correct?


Yes, but I would recommend installing it again.
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

printer only prints in flip mode

[Michael Hennebry]

My Brother HL-L2360DW B&W laser printer
is only printing in flip mode,
i.e., when it prints 8.5x11 two-sided portrait,
to read the back page, one must flip it vertically
by a short side, rather that horizontally by a long edge.

The defaults for the printer is set to 
job-sheets=none, none media=na_letter_8.5x11in sides=two-sided-long-edge

I've restarted CUPS on F38.
The problem occurs with both gedit and vim.
In the case of gedit, page setup tells me I've set it up correctly,
but it still does the wrong thing.

Any ideas on what is wrong, how I can fix it or how I can find out?

--
Michael   henne...@mail.cs.ndsu.nodak.edu
"His longhand was fairly good in his youth, but as he got older it got
smaller, more scribbly, and harder to read; although, like being hanged,
one can get used to it." -- Gordon Dickson on H.P. Lovecraft's handwriting
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 8:38 PM, Samuel Sieb wrote:

On 12/1/23 18:46, home user wrote:

On 12/1/23 6:44 PM, Samuel Sieb wrote:

You mentioned in a previous email that there was a rescue kernel. That one 
isn't tracked by any package.  You can delete the files and the next kernel 
install will update it with the latest kernel.


The rescue kernel is not the issue here.  I included it in the grub menu list 
for completeness.


It wasn't clear that it was a separate entry since it didn't have a version.


The /boot/loader/entries/ kernel listing matches the grub menu, but not the rpm 
-qa kernel-core output.


It would, since that's where the grub menu list comes from.


What I want for the kernels:
the grub menu
the rpm -qa kernel-core output
the /boot listing
the /boot/loader/entries/ listing
to all match, and all out-of-date files gone.


Remove the files for the entry that doesn't have a kernel package.


Here's what I did:
-
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.3[entries]: rm 70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf'? y
-bash.4[entries]: rm 
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf'? y
-bash.5[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.6[entries]:
-
That's what you meant, right?


I don't know why you have a kernel package without a grub entry, but I wouldn't 
be surprised if it's related the entry that doesn't have a package.  After a 
couple more kernel updates it should all match.


I get the impression from what you say that my having removed the "kernel" 
package, though wrong, will not cause problems for future weekly patches.  Is my 
impression correct?


Yes, but I would recommend installing it again.


So how do I install the "meta package" "kernel" only for 6.6.2-101.fc38.x86_64?

Now I'll reboot and see what matches and what does not match, and report back 
in a separate post.


--


--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Samuel Sieb]

On 12/1/23 20:23, home user wrote:

On 12/1/23 8:38 PM, Samuel Sieb wrote:

Remove the files for the entry that doesn't have a kernel package.


Here's what I did:
-
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.3[entries]: rm 
70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf'? y
-bash.4[entries]: rm 
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf'? y

-bash.5[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.6[entries]:
-
That's what you meant, right?


Partly.  You also need to remove the corresponding files from /boot if 
they're there.



Yes, but I would recommend installing it again.


So how do I install the "meta package" "kernel" only for 
6.6.2-101.fc38.x86_64?


It's not in the repo anymore, so you would have to get it from koji. 
But see if your next upgrade brings in all the packages.  It should, 
since you still have other kernel packages installed.

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[home user]

On 12/1/23 9:30 PM, Samuel Sieb wrote:

On 12/1/23 20:23, home user wrote:

On 12/1/23 8:38 PM, Samuel Sieb wrote:

Remove the files for the entry that doesn't have a kernel package.


Here's what I did:
-
-bash.1[~]: cd /boot/loader/entries/
-bash.2[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.3[entries]: rm 70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.8-200.fc38.x86_64.conf'? y
-bash.4[entries]: rm 
70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf
rm: remove regular file 
'70857e3fb05849139515e66a3fdc6b38-6.5.10-200.fc38.x86_64.conf'? y
-bash.5[entries]: ls
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.6[entries]:
-
That's what you meant, right?


Partly.  You also need to remove the corresponding files from /boot if they're 
there.


In /boot/, the symvers-*.fc38.x86_64.xz were links to 
/lib/modules/*.fc38.x86_64/symvers.xz
I deleted the links, but not what they "point" to.
The other 8 files were deleted.
I notice that /lib/modules/ looks huge.  I'm wondering if that needs a serious 
cleaning.  But I'll come back to that in a new thread after some other f38 
issues are dealt with.

Here we go...
-
-bash.25[~]: rpm -qa kernel-core
kernel-core-6.5.5-200.fc38.x86_64
kernel-core-6.5.12-200.fc38.x86_64
kernel-core-6.6.2-101.fc38.x86_64
-bash.26[~]: ls /boot/loader/entries/
70857e3fb05849139515e66a3fdc6b38-0-memtest86+.conf
70857e3fb05849139515e66a3fdc6b38-0-rescue.conf
70857e3fb05849139515e66a3fdc6b38-6.5.12-200.fc38.x86_64.conf
70857e3fb05849139515e66a3fdc6b38-6.6.2-101.fc38.x86_64.conf
-bash.27[~]: ls /boot/
config-6.5.12-200.fc38.x86_64
config-6.6.2-101.fc38.x86_64
efi
grub2
initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img
initramfs-6.5.12-200.fc38.x86_64.img
initramfs-6.6.2-101.fc38.x86_64.img
loader
lost+found
memtest86+x64.bin
symvers-6.5.12-200.fc38.x86_64.xz
symvers-6.6.2-101.fc38.x86_64.xz
System.map-6.5.12-200.fc38.x86_64
System.map-6.6.2-101.fc38.x86_64
vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
vmlinuz-6.5.12-200.fc38.x86_64
vmlinuz-6.6.2-101.fc38.x86_64
-bash.28[~]:
-
The grub menu now includes kernel entries for 6.5.12 and 6.6.2 only (plus 
rescue, memory test, and windows).
Progress!




Yes, but I would recommend installing it again.


So how do I install the "meta package" "kernel" only for 6.6.2-101.fc38.x86_64?


It's not in the repo anymore, so you would have to get it from koji. But see if 
your next upgrade brings in all the packages.  It should, since you still have 
other kernel packages installed.


ok, I'll punt this.  I gather that the fix happens only when the kernel itself gets 
patched, and weekly patches that don't patch the kernel won't restore "kernel".

I'll turn my focus to the extra memory test in the grub menu tomorrow.


--

--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: how to remove unwanted old kernels.

[Jeffrey Walton]

On Fri, Dec 1, 2023 at 5:42 PM home user  wrote:
>
> On 12/1/23 3:36 PM, Joe Zeff wrote:
> > On 12/01/2023 03:25 PM, home user wrote:
> >> The rpm command did not give me enough information, so I had to do the 
> >> reboot.
> >
> > You could always look in /boot and see what's there.
> > --
> That was a part of that same post.  Here it is again:
> --
> bash.1[~]: ls /boot
> config-6.5.10-200.fc38.x86_64
> config-6.5.12-200.fc38.x86_64
> config-6.5.8-200.fc38.x86_64
> config-6.6.2-101.fc38.x86_64
> efi
> grub2
> initramfs-0-rescue-70857e3fb05849139515e66a3fdc6b38.img
> initramfs-6.5.10-200.fc38.x86_64.img
> initramfs-6.5.12-200.fc38.x86_64.img
> initramfs-6.5.8-200.fc38.x86_64.img
> initramfs-6.6.2-101.fc38.x86_64.img
> loader
> lost+found
> memtest86+x64.bin
> symvers-6.5.10-200.fc38.x86_64.xz
> symvers-6.5.12-200.fc38.x86_64.xz
> symvers-6.5.8-200.fc38.x86_64.xz
> symvers-6.6.2-101.fc38.x86_64.xz
> System.map-6.5.10-200.fc38.x86_64
> System.map-6.5.12-200.fc38.x86_64
> System.map-6.5.8-200.fc38.x86_64
> System.map-6.6.2-101.fc38.x86_64
> vmlinuz-0-rescue-70857e3fb05849139515e66a3fdc6b38
> vmlinuz-6.5.10-200.fc38.x86_64
> vmlinuz-6.5.12-200.fc38.x86_64
> vmlinuz-6.5.8-200.fc38.x86_64
> vmlinuz-6.6.2-101.fc38.x86_64

You can manually remove the packages. You might try that next since
the dnf-system-upgrade script did not work for you.

For each kernel version you want to remove, specify them explicitly.
Here is what the names look like from an old F39 kernel on one of my
machines:

* kernel-6.5.11-300.fc39.x86_64
* kernel-core-6.5.11-300.fc39.x86_64
* kernel-modules-6.5.11-300.fc39.x86_64
* kernel-modules-core-6.5.11-300.fc39.x86_64
* kernel-modules-extra-6.5.11-300.fc39.x86_64

Now, if you encounter errors upon removal, then your RPM database
probably needs to be repaired.

And a sharp edge... The removal script has a bug, and it leaves
artifacts in /lib/modules. See
. For example,
even though I removed 6.5.11-300.fc39, it still has artifacts in
/lib/modules:

$ ls /lib/modules
6.5.11-300.fc39.x86_646.5.12-300.fc39.x86_646.6.2-201.fc39.x86_64

You can delete the leftover artifacts with this script:

clean_lib_modules() {
   if [[ -d "/lib/modules" ]]; then
   echo "Cleaning /lib/modules"
   mapfile -t dirs < <(ls /lib/modules)
   for dir in "${dirs[@]}"
   do
   dir="/lib/modules/${dir}"
   if [ "$(du -s -B 4096 "${dir}" | awk '{print $1}')" -lt 4096 ]
   then
   echo "  removing ${dir}"
   rm -rf "${dir}" 2>/dev/null
   fi
   done
   fi
}

Jeff
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: conflict with ffmpeg

[Tim via users]

On Fri, 2023-12-01 at 22:11 -0600, Michael Hennebry wrote:
> ffmpeg seems to be necessary to play some videos,
> so I wanted ffmpeg.
> Not really sure how either firefox or chromium is using it.

Browsers can play video files within the page.  They may need extra
codecs to be able to play some files.
 
-- 
 
uname -rsvp
Linux 3.10.0-1160.102.1.el7.x86_64 #1 SMP Tue Oct 17 15:42:21 UTC 2023 x86_64
 
Boilerplate:  All unexpected mail to my mailbox is automatically deleted.
I will only get to see the messages that are posted to the mailing list.
 
--
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@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/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue