Monitor shuts off randomly - possibly sync problem?
by Alex
Hi,
I have fedora34 installed on my desktop with three monitors; two of
them are older 27" Samsungs, and the third is a new 34" Samsung
S34J55x. Occasionally, the 34" seems to shut off for a second, then
comes back on and continues to work normally.
Has anyone seen this type of behavior before? The other two monitors
have never done this. However, when it happens, the other two seem to
follow with shutting off for a second. It always seems to be driven by
the new 34" monitor.
The problem is that, when this happens, all of the windows on the 34"
monitor move to the 27" monitor on the right once the monitors turn on
again.
This is not a power problem, as the entire computer is connected to
the same power strip, backed by a 2200W UPS.
My video card is also new - it's a Radeon RX570. All three monitors
are connected via displayport.
I do see lines in my Xorg.0.log file periodically along the lines off
the following:
[992023.990] (EE) event3 - Logitech Gaming Mouse G900: client bug:
event processing lagging behind by 16ms, your system is too slow
[994674.766] (EE) event6 - Logitech Gaming Keyboard G910: client bug:
event processing lagging behind by 29ms, your system is too slow
But are they related? Is this also an issue? The system itself is a
12-core with 64GB of RAM, so certainly not slow.
Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz
Please let me know what more I can do to troubleshoot this before
contacting Samsung directly.
2 years, 7 months
NFS mount
by Dave Close
I'm trying to setup an NFS mount to an older NAS device. The client
is Fedora 34, the NAS is a Buffalo Linkstation. I have access to the
NAS via SSH and I can successfully mount it using CIFS and SSHFS. Of
course, CIFS loses some file attributes and SSHFS seems slow and
doesn't see the filesystem usage properly. So I'd prefer NFS but it
keeps failing. I've even tried with my firewall disabled but no luck.
The NAS only works with NFS v2. It's NFS is a client-side application
as there is no NFS built into its kernel. But it is nothing new; the
app has been running successfully for many folks for years.
All the necessary ports seem to be open.
# nmap -sU -p2049,111 nas1
PORT STATE SERVICE
111/udp open rpcbind
2049/udp open nfs
# nmap -sT -p2049,111 nas1
PORT STATE SERVICE
111/tcp open rpcbind
2049/tcp open nfs
I can access the NAS with rpcinfo and showmount.
# showmount -e nas1
Export list for nas1:
/mnt/array1/share client.compata.com
# rpcinfo -p nas1
program vers proto port service
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100003 2 udp 2049 nfs
100003 2 tcp 2049 nfs
100005 1 udp 726 mountd
100005 2 udp 726 mountd
100005 1 tcp 729 mountd
100005 2 tcp 729 mountd
But mount fails.
# mount -v -o vers=2 -t nfs nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 17:52:01 2021
mount.nfs: trying text-based options 'vers=2,addr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
# mount -v -o udp -o vers=2 -t nfs nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 17:53:43 2021
mount.nfs: trying text-based options 'udp,vers=2,addr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=17
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot UDP port 2049
mount.nfs: prog 100005, trying vers=1, prot=17
mount.nfs: trying 192.168.44.20 prog 100005 vers 1 prot UDP port 726
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
I have tcpdump captures from both ends and I don't see anything obviously
wrong. (But then I'm not sure just what I ought to see there.) I do see
the portmap calls and the results seem ok. Each is followed by a null
call and a null reply, again nothing obviously wrong. I don't understand
why the mount proceeds to use V1 for prog 100005 (mount) without any
indication of a problem with the V2 attempt for NFS. But forcing V2 for
both doesn't help.
# mount -v -o nfsvers=2 -o mountvers=2 -o mountproto=tcp -t nfs
nas1:/mnt/array1/share /nas1
mount.nfs: timeout set for Sat Aug 28 18:28:37 2021
mount.nfs: trying text-based options 'nfsvers=2,mountvers=2,
mountproto=tcp,addr=192.168.44.20,mountaddr=192.168.44.20'
mount.nfs: prog 100003, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100003 vers 2 prot TCP port 2049
mount.nfs: prog 100005, trying vers=2, prot=6
mount.nfs: trying 192.168.44.20 prog 100005 vers 2 prot TCP port 729
mount.nfs: mount(2): Protocol not supported
mount.nfs: Protocol not supported
I can't find anything relevant in any system log. The final message,
"Protocol not supported", doesn't clearly indicate which protocol --
I presume mount(2) -- nor give any clue to a remedy. But if I force
v3 for mount, I get a version mismatch.
--
Dave Close, Compata, Irvine CA +1 714 434 7359
dave(a)compata.com dhclose(a)alumni.caltech.edu
"Computers are useless. They can only give you answers."
-- Pablo Picasso
2 years, 7 months
rkhunter warning
by François Patte
Bonjour,
Since I upgraded to f34, rkhunter is warning me with this file:
Warning: Hidden file found: /usr/share/man/fr/man1/..1.gz: symbolic link
to builtins.1.gz
Asking rpm -qf /usr/share/man/fr/man1/..1.gz, it returns that this file
belongs to the man-pages-fr package.
rkhunter --propupd does not change anything, every day rkhunter sends me
a warning mail...
Which of these two must be believed: rkhunter or rpm -qf?
Thank you.
--
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
2 years, 7 months
Weird keyboard problem
by Frederic Muller
Hi!
I'm using a Logitech G512 (wired) keyboard. Usually works perfectly in
the morning and little by little I get stuck with 'some' keys. I say
some because it's not regular. I press them and they don't seem to
work.. then work "if I press harder" ... or later?
When using the native laptop keyboard, or another BT Logitech K480
keyboard the problem is not there.
I am really hesitating to bring it back as I've noticed when in the
browser or some applications highlighting the blinking character cursor,
that it actually stops blinking at times, and then suddenly either gets
3 keys typed in a row, or just a 'huge' time delay between the moment I
typed that key and the moment it appears.
Are there any reliable ways to troubleshoot and pinpoint where the issue
could be coming from?
Thank you.
Fred
2 years, 7 months
touchpad for Fedora 34?
by Jack Craig
just joining the F34 party and craving a touchpad.
recommendations for touchpad on F34/gnome 40??
tia, jackc...
2 years, 7 months
Where(in which file) does the installer(Anaconda) write the grub menu
entries (for the user to edit)?
by Gueven Bay
Hello,
I have installed a Centos (8.4) on my harddisks thrid partition and
after that a Fedora 33 on the fourth partition. The Fedora installer
made the correct entries for grub. I can choose and boot both
operating systems.
BUT
My Problem is: I can not find the menu entries in the scripts under
/etc/grub.d !?
(I looked in 40_custom, 41_custom, 10_linux)
I also looked in /etc/default/grub. The grub menu entries for both
OSes are also not in this file.
Where do I find and edit my grub menu (of course, if I do not want to
edit the menu manually at every boot time on the grub command line,
which is what I do _not_ want)?
(The side problem is: In the Quick Docs it is not documented!
https://docs.fedoraproject.org/en-US/quick-docs/bootloading-with-grub2/)
Thanks!
2 years, 7 months
firefox?
by Patrick Dupre
Hello,
I guess that it is a firefox specificity.
Now (after I dialed something!), when I open a file search window, the
file are sorted in reversed alphabetic order.
How can I return to the standard alphabetic file order?
Thanks
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire interdisciplinaire Carnot de Bourgogne
9 Avenue Alain Savary, BP 47870, 21078 DIJON Cedex FRANCE
Tel: +33 (0)380395988 | | Room# D114A
===========================================================================
2 years, 7 months
new issues with Signal on Fedora 34
by Ranjan Maitra
Dear friends,
Since yesterday's updates, I have been unable to get into Signal messenger desktop client from Fedora. Specifically, I get that the "loading" screen with the 3 animated dots and the screen never finishes. THere are no issues with the phone version. I do not know about other desktop versions but I wonder if others here have the same issue and a possible fix.
I did put in a request on github: https://github.com/luminoso/fedora-copr-signal-desktop/issues/10
but am not sure what to do.
Many thanks and best wishes,
Ranjan
2 years, 7 months
GPU switching without custom kernels on ASUS AMD hybrid GPU laptops ? asusctl...
by linux guy
I recently purchased an ASUS A17 laptop with an AMD 4800H processor. Of
course I immediately installed Fedora 34 on it. Everything works well out
of the box... except GPU switching.
The ASUS A17 comes with 2 GPUs. GPU0 is the integrated GPU (iGPU) on the
4800H processor. GPU1 is a discrete NVIDIA GTX1660Ti GPU. (dGPU)
My laptop is currently running with iGPU using AMD drivers under X11. I'm
not a gamer. It works well for driving the 1920x1080 laptop screen but
will not drive an external 4K monitor without blanking out.
I installed the proprietary NVIDIA drivers using akmod from the RPMFusion
repository. lsmod shows both AMD and NVIDIA drivers installed on my
machine.
There is a utility for controlling a number of ASUS hardware features
called asusctl.
https://asus-linux.org/asusctl/
I'd rather not use this utility because it relies on custom kernels. I'd
like my kernels to come straight from the Fedora repositories.
I'm OK with rebooting to swap GPUs. In laptop mode I'm fine using the
iGPU. When I'm at my desktop, I need to use the dGPU to drive my external
monitor.
Is there an (easy) way to set up grub to blacklist one driver or the other
at boot time in order that the other driver can run and thus use the
desired GPU ? Right now I'm blacklisting nouveau. Could I also create
grub entries to blacklist the AMD or NVIDIA driver ?
Any other thoughts on doing this ?
Thanks
# lsmod | grep amd
edac_mce_amd 32768 0
kvm_amd 139264 0
kvm 1007616 1 kvm_amd
amdgpu 7049216 109
drm_ttm_helper 16384 1 amdgpu
ttm 77824 2 amdgpu,drm_ttm_helper
iommu_v2 24576 1 amdgpu
gpu_sched 45056 1 amdgpu
i2c_algo_bit 16384 1 amdgpu
drm_kms_helper 290816 2 amdgpu,nvidia_drm
drm 630784 22
gpu_sched,drm_kms_helper,nvidia,amdgpu,drm_ttm_helper,nvidia_drm,ttm
ccp 110592 1 kvm_amd
# lsmod | grep nvidia
nvidia_drm 69632 2
nvidia_modeset 1200128 3 nvidia_drm
nvidia_uvm 1175552 0
nvidia 35319808 91 nvidia_uvm,nvidia_modeset
i2c_nvidia_gpu 16384 0
drm_kms_helper 290816 2 amdgpu,nvidia_drm
drm 630784 22 gpu_sched,drm_kms_helper,nvidia
,amdgpu,drm_ttm_helper,nvidia_drm,ttm
2 years, 7 months
premature umount
by Geoffrey Leach
I have a script that mounts an MP3 device, copies files and umounts. As
I have counted on the umount to hang until the data transfer is
complete. That has worked fine until recently. Now the umount finishes,
leaving much of the data uncopied.
Fedora 32, up-to-date at end-of-life.
Has some parameter been changed inadvertently? Or was I just lucky, and
my luck has run out? If so, is there a way to test for the real end of
transfer?
2 years, 7 months