Possible general problem?

Hi everyone

I'm trying to find solutions from the forum, wikis, etc., to some problem I find in the system, and I just don't see it very clearly, because before shuffling trying luck (I'm not a computer scientist) with different things , I would like to know if everything comes from the same place or are they different problems. In summary I would say that they are cuts of different services (personal opinion of fan)

The fact is that at the time of entering the user there are small flashes in parts of the screen, a few seconds, then it no longer does.

There are also small cuts of wifi, it does not disconnect but the traffic is at 0B/s for a second or two. Sometimes it’s hard to load pages, although when I do speed tests, I’m more or less at 50Mbps download, 35Mbps upload, 18ms latency, and 84ms jitter.

Finally I also have cuts via bluetooth, it does not disconnect from the devices but stops transmitting sound. For example if I use a bluetooth speaker, every now and then it is not heard, even though the player and audio signal is working, I have to close the player and reopen it. Or if I’m playing from my cell phone from time to time the sound goes off, I have to disconnect and reconnect.

I leave the journalctl and inxi -Fxxxza output in case anyone has been there, sorry for the long post but I wanted to explain it in detail to make things easier for you. My English is from Google Translator. forgive me.

Thank you so much.

╭─[email protected] in ~ took 5ms
╰─λ journalctl -p 3 -xb
-- Journal begins at Wed 2021-04-07 17:08:59 CEST, ends at Tue 2021-05-11 18:42:19 CEST. --
de maig 11 17:23:22 tuxpep kernel: x86/cpu: SGX disabled by BIOS
de maig 11 17:23:23 tuxpep systemd-tmpfiles[532]: Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
de maig 11 17:23:23 tuxpep kernel:
de maig 11 17:23:23 tuxpep kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  460.67  Thu Mar 11 00:11:45 UTC 2021
de maig 11 17:23:24 tuxpep kernel: nvidia-gpu 0000:01:00.3: i2c timeout error e0000000
de maig 11 17:23:24 tuxpep kernel: ucsi_ccg 0-0008: i2c_transfer failed -110
de maig 11 17:23:24 tuxpep kernel: ucsi_ccg 0-0008: ucsi_ccg_init failed - -110
de maig 11 17:23:30 tuxpep nmbd[4043]: [2021/05/11 17:23:30.985152,  0] ../../lib/util/become_daemon.c:147(daemon_status)
de maig 11 17:23:30 tuxpep nmbd[4043]:   daemon_status: daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ...
de maig 11 17:23:30 tuxpep nmbd[4043]: [2021/05/11 17:23:30.985266,  0] ../../source3/nmbd/nmbd_subnetdb.c:253(create_subnets)
de maig 11 17:23:30 tuxpep nmbd[4043]:   NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6).
de maig 11 17:23:35 tuxpep sddm-helper[4055]: gkr-pam: unable to locate daemon control file
de maig 11 17:23:37 tuxpep pulseaudio[4608]: No s'ha pogut obrir el mòdul module-esound-protocol-tcp.so: module-esound-protocol-tcp.so: no s’ha pogut obrir el fitxer d’objecte compartit: El fitxer o directori no existeix
de maig 11 17:23:37 tuxpep pulseaudio[4608]: Failed to open module "module-esound-protocol-tcp".
de maig 11 17:23:37 tuxpep pulseaudio[4608]: pa_module_load() failed
de maig 11 17:23:37 tuxpep pulseaudio[4608]: connect() failed: La xarxa és inabastable
de maig 11 17:23:37 tuxpep pulseaudio[4608]: Failed to load module "module-rtp-send" (argument: "[email protected][email protected] loop=0"): initialization failed.
de maig 11 17:23:37 tuxpep pulseaudio[4608]: pa_module_load() failed
de maig 11 17:23:37 tuxpep pulseaudio[4608]: Master sink not found.
de maig 11 17:23:37 tuxpep pulseaudio[4608]: Failed to load module "module-ladspa-sink" (argument: "sink_name=ladspa_output.mbeq_1197.mbeq sink_master=bluez_sink.78_44_05_68_AD_77.a2dp_sink plugin=mbeq_1197 label=mbeq control=4.0,2.0,1.0>
de maig 11 17:23:37 tuxpep pulseaudio[4608]: Sink ladspa_output.mbeq_1197.mbeq does not exist.
de maig 11 17:23:37 tuxpep pulseaudio[4608]: No sink found by this name or index.
de maig 11 17:23:40 tuxpep nmbd[4043]: [2021/05/11 17:23:40.985835,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
de maig 11 17:23:40 tuxpep nmbd[4043]:   daemon_ready: daemon 'nmbd' finished starting up and ready to serve connections
de maig 11 17:23:41 tuxpep smbd[4878]: [2021/05/11 17:23:41.028207,  0] ../../lib/util/become_daemon.c:135(daemon_ready)
de maig 11 17:23:41 tuxpep smbd[4878]:   daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
de maig 11 17:23:43 tuxpep bluetoothd[564]: src/profile.c:record_cb() Unable to get Headset Voice gateway SDP record: Host is down
de maig 11 17:24:03 tuxpep nmbd[4043]: [2021/05/11 17:24:03.056231,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
de maig 11 17:24:03 tuxpep nmbd[4043]:   *****
de maig 11 17:24:03 tuxpep nmbd[4043]:
de maig 11 17:24:03 tuxpep nmbd[4043]:   Samba name server TUXPEP is now a local master browser for workgroup WORKGROUP on subnet 192.168.0.197
de maig 11 17:24:03 tuxpep nmbd[4043]:
de maig 11 17:24:03 tuxpep nmbd[4043]:   *****
lines 1-34/34 (END)

The first line of Pulseaudio is in Catalan, the language of the system, and reads as follows: The module module-esound-protocol-tcp.so could not be opened: module-esound-protocol-tcp.so: no could not open shared object file: File or directory does not exist.

╭─[email protected] in ~ 
╰─λ inxi -Fxxxza
System:    Kernel: 5.12.2-zen2-1-zen x86_64 bits: 64 compiler: gcc v: 10.2.0 
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=73fd15b3-147e-42cb-8f83-fead19893501 rw 
[email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0 
systemd.unified_cgroup_hierarchy=1 loglevel=3 nouveau.modeset=0 
Desktop: KDE Plasma 5.21.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM Distro: Garuda Linux 
base: Arch Linux 
Machine:   Type: Desktop System: HP product: HP Pavilion Gaming Desktop TG01-1xxx v: N/A serial: <filter> Chassis: type: 3 
serial: <filter> 
Mobo: HP model: 8767 v: A (SMVB) serial: <filter> UEFI: AMI v: F.22 date: 11/27/2020 
CPU:       Info: 6-Core model: Intel Core i5-10400F bits: 64 type: MT MCP arch: Comet Lake family: 6 model-id: A5 (165) 
stepping: 3 microcode: E0 cache: L2: 12 MiB 
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 69597 
Speed: 3347 MHz min/max: 800/4300 MHz Core speeds (MHz): 1: 3347 2: 4283 3: 4217 4: 4066 5: 4078 6: 4197 7: 4303 
8: 4200 9: 4200 10: 4199 11: 4196 12: 4200 
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled 
Type: l1tf status: Not affected 
Type: mds status: Not affected 
Type: meltdown status: Not affected 
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp 
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization 
Type: spectre_v2 mitigation: Enhanced IBRS, IBPB: conditional, RSB filling 
Type: srbds status: Not affected 
Type: tsx_async_abort status: Not affected 
Graphics:  Device-1: NVIDIA TU116 [GeForce GTX 1660 SUPER] vendor: Hewlett-Packard driver: nvidia v: 460.67 
alternate: nouveau,nvidia_drm bus-ID: 01:00.0 chip-ID: 10de:21c4 class-ID: 0300 
Display: x11 server: X.Org 1.20.11 compositor: kwin_x11 driver: loaded: nvidia unloaded: modesetting,nouveau 
alternate: fbdev,nv,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 93 s-size: 524x312mm (20.6x12.3") s-diag: 610mm (24")
Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 82 size: 597x336mm (23.5x13.2") diag: 685mm (27")
OpenGL: renderer: GeForce GTX 1660 SUPER/PCIe/SSE2 v: 4.6.0 NVIDIA 460.67 direct render: Yes
Audio:     Device-1: Intel Comet Lake PCH cAVS vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
alternate: snd_soc_skl,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:06c8 class-ID: 0403
Device-2: NVIDIA TU116 High Definition Audio vendor: Hewlett-Packard driver: snd_hda_intel v: kernel
bus-ID: 01:00.1 chip-ID: 10de:1aeb class-ID: 0403
Sound Server-1: ALSA v: k5.12.2-zen2-1-zen running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.27 running: yes
Network:   Device-1: Intel Comet Lake PCH CNVi WiFi driver: iwlwifi v: kernel bus-ID: 00:14.3 chip-ID: 8086:06f0
class-ID: 0280
IF: wlo1 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel
port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Bluetooth: Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-14:3 chip-ID: 8087:0026 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
RAID:      Hardware-1: Intel SATA Controller [RAID mode] driver: ahci v: 3.0 port: 5020 bus-ID: 00:17.0 chip-ID: 8086.2822
rev: class-ID: 0104
Drives:    Local Storage: total: 1.38 TiB used: 62.52 GiB (4.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKNW512G8H size: 476.94 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: HPS1 scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD10EZEX-60WN4A1 size: 931.51 GiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> rev: 1A03 scheme: GPT
Partition: ID-1: / raw-size: 234.38 GiB size: 234.38 GiB (100.00%) used: 62.49 GiB (26.7%) fs: btrfs dev: /dev/nvme0n1p5
maj-min: 259:5
ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%) used: 25.5 MiB (26.5%) fs: vfat dev: /dev/nvme0n1p1
maj-min: 259:1
ID-3: /home raw-size: 234.38 GiB size: 234.38 GiB (100.00%) used: 62.49 GiB (26.7%) fs: btrfs dev: /dev/nvme0n1p5
maj-min: 259:5
ID-4: /var/log raw-size: 234.38 GiB size: 234.38 GiB (100.00%) used: 62.49 GiB (26.7%) fs: btrfs
dev: /dev/nvme0n1p5 maj-min: 259:5
ID-5: /var/tmp raw-size: 234.38 GiB size: 234.38 GiB (100.00%) used: 62.49 GiB (26.7%) fs: btrfs
dev: /dev/nvme0n1p5 maj-min: 259:5
Swap:      Kernel: swappiness: 10 (default 60) cache-pressure: 75 (default 100)
ID-1: swap-1 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram0
ID-2: swap-2 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram1
ID-3: swap-3 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram2
ID-4: swap-4 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram3
ID-5: swap-5 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram4
ID-6: swap-6 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram5
ID-7: swap-7 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram6
ID-8: swap-8 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram7
ID-9: swap-9 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram8
ID-10: swap-10 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram9
ID-11: swap-11 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram10
ID-12: swap-12 type: zram size: 1.29 GiB used: 0 KiB (0.0%) priority: 32767 dev: /dev/zram11
Sensors:   System Temperatures: cpu: 36.0 C mobo: 27.8 C gpu: nvidia temp: 33 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 42%
Info:      Processes: 334 Uptime: 1h 29m wakeups: 0 Memory: 15.5 GiB used: 3.09 GiB (19.9%) Init: systemd v: 248
tool: systemctl Compilers: gcc: 10.2.0 clang: 11.1.0 Packages: pacman: 1889 lib: 550 Shell: fish v: 3.2.2
running-in: konsole inxi: 3.3.04

Thnks a lot! :slight_smile:

Is this not just the DE loading during login?

Is your wifi signal reliable? Is there other electromagnetic interference, e.g. radios, microwave ovens, other wifi access points, emergency service vehicles, aeroplane radar, ... ?

If the same thing happens on your phone then it's not a Garuda issue, and could instead be an issue with the speaker or (as above) general EM interference.

4 Likes

Hi @jonathon thanks for replying :slight_smile:

Is this not just the DE loading during login?

Yes, once I put the password

Is your wifi signal reliable? Is there other electromagnetic interference, e.g. radios, microwave ovens, other wifi access points, emergency service vehicles, aeroplane radar, ... ?

I have two laptops with Linux Mint and a netbook with EmmaDE4 and I have no problem with it

If the same thing happens on your phone then it's not a Garuda issue, and could instead be an issue with the speaker or (as above) general EM interference.

I must not have translated it correctly; sometimes I use my cell phone to play music on my computer, via bluetooth, and just like what happens with the bluetooth speaker.
Everything works fine, and suddenly nothing is heard, but the volume indicators show the movement of the sound level, as if everything was working fine

Thank you so much

I would suggest testing alternate kernels such as linux-lts, linux-mainline, or linux-next-git (and possibly others) for your Wifi issue.

I would also try downgrading the iwlwifi firmware, or alternately see if there is a newer version available on the Intel website (or a developmental Android version).

You could also try disabling TSO with Ethtool to improve performance of your wifi (known bug in the past).

5 Likes

Thank you so much @tbg, I will try one by one what you propose to me. I'll start with the kernel, as the sound output, bluetooth and wifi, seem to do the same (it seems to go well, but stop working without giving any error), I would say it must all come from there.

I messed it up several times trying to install the nvidia drivers, I also recovered several previous images, because I didn't know how to fix the boot again, I also tried to install the conky and it crashed everything. I must have unconfigured something.

Now on updating, it also tells me that protontricks-git: local (1.5.1.dev5 + g2d33981-1) is newer than chaotic-aur (1.5.1-1), but it is already installed.

I will try one by one what you propose to me

but that, I don't know how to look for it, I don't know what it is

Search on the internet:

Ethtool TSO off

3 Likes

Grateful :sweat_smile:

1 Like

Hi again

I've tried linux-lts, linux-mainline and linux-next-git, but I can only boot the system with linux-zen and linux-lts, to which, I haven't noticed any difference.

With linux-mainline and linux-next-git, when you try to start the system, a black screen appears with a phrase that says (FAILED) Failed to start Samba NMB Daemon. staying that way. I reinstalled Samba, but it stays the same.

Blinking into pieces of the screen when starting the user environment, does the same in linux-lts.

i tried different iwlwifi, i don't know how it worked but i found none of it installed, in the end i left iwlwifi-7265-ucode + iwlwifi-next.

I did what you told me, but unfortunately it doesn’t improve. In fact on this computer I have a partition with Windows that I do not use (I put it for video games, but I never have time :sweat_smile:), and it gives a upload speed of 30/40Mbps faster than here, with the same browser.

Before, I forget, I must say that I have not noticed any cut bluetooth as happened yesterday.
Today bluetooth has also been disconnected several times

I was thinking of following in the footsteps of @tgb in another thread, this, for the issue of slow wifi, what I do not know is if there are any parameters that may have changed since then, as it is 2020 five months ago.

What do you think? can I apply it as is?

Yes, it is always a good idea to test different iwlwifi driver options to see if it improves your connectivity.

There is no risk in testing different options via modprobing. The options only apply to your current session. A restart wipes any alterations, so there is zero risk in permanently messing things up.

1 Like

thanks @tgb, I guess the code is the same, nothing has changed, right? Because I don’t even understand it and I’ll copy and paste it

Copy and paste away, no risk involved.

If you find improvement with various options they can be made permanent later.

1 Like

Yes, I have already seen that you have explained it very well, thank you very much, if it works I will comment on who you can use it for

Well the first option is the one closest to what I have, it gives me similar results, I go between 18/21Mbps, sharing office I have my son, with the same hardware (I bought two computers exactly the same) with Linux Mint connected to the same wifi, and goes at 95/96Mbps. We both have dual boot with windows.

I probably shuffled something I shouldn’t have touched


Well, right now, I feel the same as I did in the first few seconds of the start of Slayer's Raining Blood :sweat_smile:

I tried the two kernels that work for me, the linux-lts and the linux-zen (which I am using now), without seeing differences, the linux-next-git and the linux-mainline, they do not work for me, they do not let me start the system . As commented in other different posts by @tbg .

I have installed and reinstalled different iwlwifi and different drivers for RealTek from Pamac.

I have renamed the file /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm as it says in this post.

I checked that the dhcpcd.service and the networkmanager.service as described in this post did not work at the same time, and some other thing that I have seen on the Garuda and Arch Linux forums and that I do not remember now (I have broken the head), and the constant connection cuts of a second or two continue, they kill me, since I work from home managing one the content of a CMS and it gets stuck continuously. :exploding_head:

I'm about to reinstall the system again (I've already done it 5 times with the nVidia drivers issue), unfortunately, even though I like Garuda Linux, it's like fresh air, but if I don't get it either, I'll be sad to have to go back to some .deb branch, since, as I mentioned earlier, my son works fine with exactly the same hardware that I have.

Of course, I do not think it is due to a Garuda Linux malfunction, but because I do not know how to configure it correctly with the hardware I have. I'm just a hobbyist and some more technical tips I don't understand.

Maybe some step I have not done correctly, anyway if someone has an idea that I have not tried yet, apart from throwing me out of the window of course! :rofl:

Thnx!

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.