Folks, I have 2 issues with F40 and F40. One of them is frustrating the other a genuine problem.
First the genuine problem. I have VMware installed on my system and every time I install kernel updates the compilation of the vmmon and vmnet VMware modules fail.
here is an excerpt of the issue:
./include/linux/rwlock.h:56:48: note: in definition of macro
'read_lock'
56 | #define read_lock(lock) _raw_read_lock(lock) | ^~~~ /tmp/git/vmware-host-modules/vmnet-only/bridge.c:587:4: note: in
expansion o
587 | dev_lock_list(); | ^~~~~~~~~~~~~
On another system I download the VMware modules from
https://github.com/mkubecek/vmware-host-modules.git
and the apply the following patch
--- a/vmnet-only/vmnetInt.h +++ b/vmnet-only/vmnetInt.h @@ -41,8 +41,13 @@ compat_skb_set_network_header(skb, sizeof (struct ethhdr)), \ dev_queue_xmit(skb) \ ) -#define dev_lock_list() read_lock(&dev_base_lock) -#define dev_unlock_list() read_unlock(&dev_base_lock) +#if LINUX_VERSION_CODE >= KERNEL_VERSION(6, 9, 0) +# define dev_lock_list() rcu_read_lock() +# define dev_unlock_list() rcu_read_unlock() +#else +# define dev_lock_list() read_lock(&dev_base_lock) +# define dev_unlock_list() read_unlock(&dev_base_lock) +#endif
extern struct proto vmnet_proto;
and the kernel builds without issues.
The reason I mention this error is that this failure occurs during the kernel update and not when I try to build the VMware modules.
Now for the frustrating issue.
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. I have MATE configured to remember running application on logout so they are restarted when I login. At the time I logout my mate-terminals are 24x80. When I log back in they are 7x42. New ones are 24x80. So every time I login I have to resize my terminals. This is frustrating. This problem only occurs with the MATE desktop and mate-terminal combination. If I run gnome-terminal or xfce-terminal under MATE they remain at 24x80. If I run Xfce desktop and run mate-terminal it remains 24x80 through logout and login. This does not happen with F39. I don't know what changed to cause this. I first noticed this after upgrading a system from F39 -> F40. This issue also happens with F40 and F41 virtual machines and with F40 Server and doing a groupinstall of the MATE desktop.
I don't know where MATE saves the session information to see if the problem is when MATE saves the current desktop state.
Any assistance is appreciated.
Paolo
On Tue, 19 Nov 2024 07:56:07 -0800 Paolo Galtieri wrote:
Folks,
[ ... ]
Now for the frustrating issue.
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. I have MATE configured to remember running application on logout so they are restarted when I login. At the time I logout my mate-terminals are 24x80. When I log back in they are 7x42. New ones are 24x80. So every time I login I have to resize my terminals. This is frustrating. This problem only occurs with the MATE desktop and mate-terminal combination. If I run gnome-terminal or xfce-terminal under MATE they remain at 24x80. If I run Xfce desktop and run mate-terminal it remains 24x80 through logout and login. This does not happen with F39. I don't know what changed to cause this. I first noticed this after upgrading a system from F39 -> F40. This issue also happens with F40 and F41 virtual machines and with F40 Server and doing a groupinstall of the MATE desktop.
You are not alone. I've the same issue and it is realy annoying. A beer for the person who solves it.
--Frank
Glad to know I'm not the only one. Given the frustration 1 beer may not be enough :)
Paolo
On 11/19/24 09:49, Frank Elsner wrote:
On Tue, 19 Nov 2024 07:56:07 -0800 Paolo Galtieri wrote:
Folks,
[ ... ]
Now for the frustrating issue.
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. I have MATE configured to remember running application on logout so they are restarted when I login. At the time I logout my mate-terminals are 24x80. When I log back in they are 7x42. New ones are 24x80. So every time I login I have to resize my terminals. This is frustrating. This problem only occurs with the MATE desktop and mate-terminal combination. If I run gnome-terminal or xfce-terminal under MATE they remain at 24x80. If I run Xfce desktop and run mate-terminal it remains 24x80 through logout and login. This does not happen with F39. I don't know what changed to cause this. I first noticed this after upgrading a system from F39 -> F40. This issue also happens with F40 and F41 virtual machines and with F40 Server and doing a groupinstall of the MATE desktop.
You are not alone. I've the same issue and it is realy annoying. A beer for the person who solves it.
--Frank
Hi Mike, I think that will him/her forget :)
Paolo
On 11/19/24 14:28, Mike Wright wrote:
On 11/19/24 11:24, Paolo Galtieri wrote:
Glad to know I'm not the only one. Given the frustration 1 beer may not be enough :)
Hi Paolo,
On a scale of 1 to 6 this definitely sounds like a 6.
;D
On Tue, 19 Nov 2024 18:49:20 +0100 Frank Elsner via users wrote:
On Tue, 19 Nov 2024 07:56:07 -0800 Paolo Galtieri wrote:
Folks,
[ ... ]
Now for the frustrating issue.
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. I have MATE configured to remember running application on logout so they are restarted when I login. At the time I logout my mate-terminals are 24x80. When I log back in they are 7x42. New ones are 24x80. So every time I login I have to resize my terminals. This is frustrating. This problem only occurs with the MATE desktop and mate-terminal combination. If I run gnome-terminal or xfce-terminal under MATE they remain at 24x80. If I run Xfce desktop and run mate-terminal it remains 24x80 through logout and login. This does not happen with F39. I don't know what changed to cause this. I first noticed this after upgrading a system from F39 -> F40. This issue also happens with F40 and F41 virtual machines and with F40 Server and doing a groupinstall of the MATE desktop.
You are not alone. I've the same issue and it is realy annoying. A beer for the person who solves it.
New observation:
The problem occurs on one of my 5 desktops only, on the other 4 all the terminals come up in correct size.
--Frank
On 2024-11-19 07:56, Paolo Galtieri wrote:
Folks, I have 2 issues with F40 and F40. One of them is frustrating the other a genuine problem.
First the genuine problem. I have VMware installed on my system and every time I install kernel updates the compilation of the vmmon and vmnet VMware modules fail.
This is not a Fedora problem. External kernel modules are your problem. Why don't you use kvm/qemu instead?
here is an excerpt of the issue:
./include/linux/rwlock.h:56:48: note: in definition of macro
'read_lock'
56 | #define read_lock(lock) _raw_read_lock(lock) | ^~~~ /tmp/git/vmware-host-modules/vmnet-only/bridge.c:587:4: note: in
expansion o
587 | dev_lock_list(); | ^~~~~~~~~~~~~
On another system I download the VMware modules from
https://github.com/mkubecek/vmware-host-modules.git
and the apply the following patch
and the kernel builds without issues.
The reason I mention this error is that this failure occurs during the kernel update and not when I try to build the VMware modules.
Then it's a problem with whatever setup you have that's automatically building the vmware kernel module when the kernel is updated. Or else whatever source you're using to build them from needs that patch. It's unclear which build you're referring to.
On 20 Nov 2024, at 11:21, Samuel Sieb samuel@sieb.net wrote:
I have 2 issues with F40 and F40. One of them is frustrating the other a genuine problem. First the genuine problem. I have VMware installed on my system and every time I install kernel updates the compilation of the vmmon and vmnet VMware modules fail.
This is not a Fedora problem. External kernel modules are your problem. Why don't you use kvm/qemu instead?
I converted my VMware VMs to run under virtual machine manager (aka kvm) and it was not that hard. All the tools you need exist and with documentation of the process.
In my case I convert a Windows 10 VM and later upgraded it to Windows 11 under virt manager.
Barry
As far as I'm concerned this is a Fedora problem. I do not automatically build VMware modules. I have always built them manually. Anyway here is the output I see:
Running post-transaction scriptlet:
kernel-core-0:6.11.8-300.fc41.x86_641.x8
Non-critical error in post-transaction scriptlet:
kernel-core-0:6.11.8-300.f
Scriptlet output: modinfo: ERROR: Module vmmon not found. Usage: scripts/sign-file [-dp] <hash algo> <key> <x509> <module>
[<dest>]
scripts/sign-file -s <raw sig> <hash algo> <x509> <module>
[<dest>]
modinfo: ERROR: Module vmnet not found. Usage: scripts/sign-file [-dp] <hash algo> <key> <x509> <module>
[<dest>]
scripts/sign-file -s <raw sig> <hash algo> <x509> <module>
[<dest>]
Cloning into 'vmware-host-modules'... make -C vmmon-only make[1]: Entering directory '/tmp/git/vmware-host-modules/vmmon-only' Using kernel build system. make -C /lib/modules/6.11.8-300.fc41.x86_64/build/include/.. M=$PWD
SRCROOT=
MODULEBUILDDIR= modules make[2]: Entering directory '/usr/src/kernels/6.11.8-300.fc41.x86_64' CC [M] /tmp/git/vmware-host-modules/vmmon-only/linux/driver.o CC [M] /tmp/git/vmware-host-modules/vmmon-only/linux/driverLog.o CC [M] /tmp/git/vmware-host-modules/vmmon-only/linux/hostif.o
Paolo
On 11/20/24 03:21, Samuel Sieb wrote:
On 2024-11-19 07:56, Paolo Galtieri wrote:
Folks, I have 2 issues with F40 and F40. One of them is frustrating the other a genuine problem.
First the genuine problem. I have VMware installed on my system and every time I install kernel updates the compilation of the vmmon and vmnet VMware modules fail.
This is not a Fedora problem. External kernel modules are your problem. Why don't you use kvm/qemu instead?
here is an excerpt of the issue:
>>> ./include/linux/rwlock.h:56:48: note: in definition of macro 'read_lock' >>> 56 | #define read_lock(lock) _raw_read_lock(lock) >>> | ^~~~ >>> /tmp/git/vmware-host-modules/vmnet-only/bridge.c:587:4: note: in expansion o >>> 587 | dev_lock_list(); >>> | ^~~~~~~~~~~~~
On another system I download the VMware modules from
https://github.com/mkubecek/vmware-host-modules.git
and the apply the following patch
and the kernel builds without issues.
The reason I mention this error is that this failure occurs during the kernel update and not when I try to build the VMware modules.
Then it's a problem with whatever setup you have that's automatically building the vmware kernel module when the kernel is updated. Or else whatever source you're using to build them from needs that patch. It's unclear which build you're referring to.
On 2024-11-20 08:30, Paolo Galtieri wrote:
As far as I'm concerned this is a Fedora problem. I do not automatically build VMware modules. I have always built them manually.
Somehow you have set them to do that. vmware modules are not provided by Fedora. They don't even seem to be provided by rpmfusion. So this is something you have set up and Fedora has no obligation to support that in any way, although people on this list might try to help you.
You're right. Over 18 months ago I did set it up to do that. I also set it up to do it on an F39 system, and I don't see any errors there. The difference is that dnf on F41 spews out a lot more error messages than did dnf oon F39.
Paolo
On 11/20/24 11:31, Samuel Sieb wrote:
On 2024-11-20 08:30, Paolo Galtieri wrote:
As far as I'm concerned this is a Fedora problem. I do not automatically build VMware modules. I have always built them manually.
Somehow you have set them to do that. vmware modules are not provided by Fedora. They don't even seem to be provided by rpmfusion. So this is something you have set up and Fedora has no obligation to support that in any way, although people on this list might try to help you.
On Wed, 2024-11-20 at 12:19 -0800, Paolo Galtieri wrote:
You're right. Over 18 months ago I did set it up to do that. I also set it up to do it on an F39 system, and I don't see any errors there. The difference is that dnf on F41 spews out a lot more error messages than did dnf oon F39.
F39 (and F40) used DNF4. F41 uses DNF5. As several people have remarked here, they have some differences, so I'd start by looking there.
poc
On 2024-11-20 12:19, Paolo Galtieri wrote:
You're right. Over 18 months ago I did set it up to do that. I also set it up to do it on an F39 system, and I don't see any errors there. The difference is that dnf on F41 spews out a lot more error messages than did dnf oon F39.
It's a compile error from whatever is doing the compiling. What are you expecting dnf to do?
I know it's a compile error. It's just that dnf4 did not provide any feedback while dnf5 does. The same error would occur with dnf4 but no dnf4 does not provide feedback. That is what was confusing me.
Paolo
On 11/20/24 15:19, Samuel Sieb wrote:
On 2024-11-20 12:19, Paolo Galtieri wrote:
You're right. Over 18 months ago I did set it up to do that. I also set it up to do it on an F39 system, and I don't see any errors there. The difference is that dnf on F41 spews out a lot more error messages than did dnf oon F39.
It's a compile error from whatever is doing the compiling. What are you expecting dnf to do?
On Tue, 19 Nov 2024 07:56:07 -0800 Paolo Galtieri pgaltieri@gmail.com wrote:
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. I have MATE configured to remember running application on logout so they are restarted when I login. At the time I logout my mate-terminals are 24x80. When I log back in they are 7x42. New ones are 24x80. So every time I login I have to resize my terminals. This is frustrating. This problem only occurs with the MATE desktop and mate-terminal combination. If I run gnome-terminal or xfce-terminal under MATE they remain at 24x80. If I run Xfce desktop and run mate-terminal it remains 24x80 through logout and login. This does not happen with F39. I don't know what changed to cause this. I first noticed this after upgrading a system from F39 -> F40. This issue also happens with F40 and F41 virtual machines and with F40 Server and doing a groupinstall of the MATE desktop.
I think mate-terminal is confusing pixel and character dimensions when restoring its session. I've found xfce4-terminal to be a good replacement.
Jim
On Wed, 20 Nov 2024 07:38:47 -0700, James Szinger wrote:
On Tue, 19 Nov 2024 07:56:07 -0800 Paolo Galtieri pgaltieri@gmail.com wrote:
I run the MATE desktop and since F40 I see a strange problem with mate-terminal. [...]
I think mate-terminal is confusing pixel and character dimensions when restoring its session. I've found xfce4-terminal to be a good replacement.
Question about that: Is there a way to color-code what MATE calls different profiles? I use that heavily, but I haven't found a way to do it with the xfce-terminal.
-
Barry Scott -
Beartooth -
Frank Elsner -
James Szinger -
Mike Wright -
Paolo Galtieri -
Patrick O'Callaghan -
Samuel Sieb