GNU Linux/Workarounds - Revision history

Root: /* GPU's */

2025-04-10T00:25:33Z

GPU's

← Older revision		Revision as of 00:25, 10 April 2025
Line 21:		Line 21:
	== GPU's ==		== GPU's ==

	=== Wayland User Experience ===		=== Prioritize the Usage of NVIDIA's OpenGL Library ===
			Set these environment variables, either by prefixing export, or by prepending the following, before the path to a program:
			__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia

			=== Wayland User Experience Fixes ===
	==== Lag with NVIDIA GPU's ====		==== Lag with NVIDIA GPU's ====
	If you have an AMD graphics card, either integrated or dedicated, you will likely be accustomed to having a better user experience than those with NVIDIA graphics cards.		If you have an AMD graphics card, either integrated or dedicated, you will likely be accustomed to having a better user experience than those with NVIDIA graphics cards.

Root at 07:35, 9 April 2025

2025-04-09T07:35:21Z

← Older revision		Revision as of 07:35, 9 April 2025
Line 1:		Line 1:
	[[Category:~~Knowledge Base~~\|GNU Linux]]		[[Category:Information Technology\|GNU Linux]]
	A lot of distributions come fairly close to being perfect, but sometimes default configurations or behaviors need to be adjusted to work for certain scenarios. Please consult the help material that accompanies the tools referenced below, if you need a better understanding of their functionalities or behaviors, and whether or not these fixes are appropriate for your use cases.		A lot of distributions come fairly close to being perfect, but sometimes default configurations or behaviors need to be adjusted to work for certain scenarios. Please consult the help material that accompanies the tools referenced below, if you need a better understanding of their functionalities or behaviors, and whether or not these fixes are appropriate for your use cases.

Root at 04:02, 31 March 2025

2025-03-31T04:02:55Z

← Older revision		Revision as of 04:02, 31 March 2025
Line 7:		Line 7:

	==== Clients Unable to Get Internet Access ====		==== Clients Unable to Get Internet Access ====
	In my case, after installing Docker on endeavourOS, I found that my hotspot could be connected to, but, the client was unable to obtain an IP address. I was using GNOME's settings applet, which is a wrapper for NetworkManager.		<blockquote>I recommend just having iptables as a firewall alone, and not in combination with, other firewalls. After writing this, I found that no rules in iptables chains were necessary for my client to connect to my WiFi hotspot. Add the rules below, as a last resort.</blockquote>In my case, after installing Docker on endeavourOS, I found that my hotspot could be connected to, but, the client was unable to obtain an IP address. I was using GNOME's settings applet, which is a wrapper for NetworkManager.

	Luckily, iptables, the firewall built into Linux, can be used. Based on hints provided by (https://wiki.archlinux.org/title/Internet_sharing#With_iptables)[https://wiki.archlinux.org/title/Internet_sharing#With_iptables], I could add a link level packet filter with NAT, using something similar to the these commands (with superuser privileges):		Luckily, iptables, the firewall built into Linux, can be used. Based on hints provided by (https://wiki.archlinux.org/title/Internet_sharing#With_iptables)[https://wiki.archlinux.org/title/Internet_sharing#With_iptables], I could add a link level packet filter with NAT, using something similar to the these commands (with superuser privileges):
Line 15:		Line 15:
	iptables -A FORWARD -i <wifi adapter name> -o <ethernet interface name> -j ACCEPT		iptables -A FORWARD -i <wifi adapter name> -o <ethernet interface name> -j ACCEPT

	~~You~~ can ~~find~~ the ~~network interface names with~~ ifconfig.		Note: Network interfaces can be listed with the "ifconfig" program.

	If clients are still unable to gain internet access after connecting to the hotspot, try disabling firewalld (this is because, as a RedHat blog article points out, it can conflict with iptables: https://www.redhat.com/en/blog/iptables)~~. After disabling firewalld, I can enable the iptables-based firewall using gufw~~.		If clients are still unable to gain internet access after connecting to the hotspot, try disabling firewalld (this is because, as a RedHat blog article points out, it can conflict with iptables: https://www.redhat.com/en/blog/iptables).

	== GPU's ==		== GPU's ==

Root at 03:52, 31 March 2025

2025-03-31T03:52:33Z

← Older revision		Revision as of 03:52, 31 March 2025
Line 1:		Line 1:
	[[Category:Knowledge Base]]		[[Category:Knowledge Base\|GNU Linux]]
	A lot of distributions come fairly close to being perfect, but sometimes default configurations or behaviors need to be adjusted to work for certain scenarios. Please consult the help material that accompanies the tools referenced below, if you need a better understanding of their functionalities or behaviors, and whether or not these fixes are appropriate for your use cases.		A lot of distributions come fairly close to being perfect, but sometimes default configurations or behaviors need to be adjusted to work for certain scenarios. Please consult the help material that accompanies the tools referenced below, if you need a better understanding of their functionalities or behaviors, and whether or not these fixes are appropriate for your use cases.

Root: /* Broken IP Configuration */

2025-03-15T04:20:41Z

Broken IP Configuration

← Older revision		Revision as of 04:20, 15 March 2025
Line 6:		Line 6:
	=== WiFi Hotspot Issues ===		=== WiFi Hotspot Issues ===

	==== ~~Broken IP Configuration~~ ====		==== Clients Unable to Get Internet Access ====
	In my case, after installing Docker on endeavourOS, I found that my hotspot could be connected to, but, the client was unable to obtain an IP address. I was using GNOME's settings applet, which is a wrapper for NetworkManager.		In my case, after installing Docker on endeavourOS, I found that my hotspot could be connected to, but, the client was unable to obtain an IP address. I was using GNOME's settings applet, which is a wrapper for NetworkManager.

	Luckily, ~~using~~ iptables, ~~based~~ on hints provided by (https://wiki.archlinux.org/title/Internet_sharing#With_iptables)[https://wiki.archlinux.org/title/Internet_sharing#With_iptables], I could add a link level packet filter with NAT, using something similar to the these commands (with superuser privileges):		Luckily, iptables, the firewall built into Linux, can be used. Based on hints provided by (https://wiki.archlinux.org/title/Internet_sharing#With_iptables)[https://wiki.archlinux.org/title/Internet_sharing#With_iptables], I could add a link level packet filter with NAT, using something similar to the these commands (with superuser privileges):

	iptables -t nat -A POSTROUTING -o <ethernet interface name> -j MASQUERADE		iptables -t nat -A POSTROUTING -o <ethernet interface name> -j MASQUERADE
Line 16:		Line 16:

	You can find the network interface names with ifconfig.		You can find the network interface names with ifconfig.

			If clients are still unable to gain internet access after connecting to the hotspot, try disabling firewalld (this is because, as a RedHat blog article points out, it can conflict with iptables: https://www.redhat.com/en/blog/iptables). After disabling firewalld, I can enable the iptables-based firewall using gufw.

	== GPU's ==		== GPU's ==

Root at 23:37, 13 March 2025

2025-03-13T23:37:44Z

← Older revision		Revision as of 23:37, 13 March 2025
Line 1:		Line 1:
	[[Category:Knowledge Base]]		[[Category:Knowledge Base]]
	A lot of distributions come fairly close to being perfect, but sometimes ~~workarounds are required~~ to ~~improve the user experience~~. Please ~~note~~ that ~~these are filed under distribution~~ and ~~driver specific sections, so may~~ or ~~may~~ not ~~be suitable~~ for ~~other combinations~~.		A lot of distributions come fairly close to being perfect, but sometimes default configurations or behaviors need to be adjusted to work for certain scenarios. Please consult the help material that accompanies the tools referenced below, if you need a better understanding of their functionalities or behaviors, and whether or not these fixes are appropriate for your use cases.

	== Networking ==		== Networking ==

Root at 23:32, 13 March 2025

2025-03-13T23:32:45Z

← Older revision		Revision as of 23:32, 13 March 2025
Line 16:		Line 16:

	You can find the network interface names with ifconfig.		You can find the network interface names with ifconfig.

			== GPU's ==

	=== Wayland User Experience ===		=== Wayland User Experience ===

Root at 23:31, 13 March 2025

2025-03-13T23:31:47Z

← Older revision		Revision as of 23:31, 13 March 2025
Line 2:		Line 2:
	A lot of distributions come fairly close to being perfect, but sometimes workarounds are required to improve the user experience. Please note that these are filed under distribution and driver specific sections, so may or may not be suitable for other combinations.		A lot of distributions come fairly close to being perfect, but sometimes workarounds are required to improve the user experience. Please note that these are filed under distribution and driver specific sections, so may or may not be suitable for other combinations.

	== ~~EndeavourOS~~ ==		== Networking ==

			=== WiFi Hotspot Issues ===

			==== Broken IP Configuration ====
			In my case, after installing Docker on endeavourOS, I found that my hotspot could be connected to, but, the client was unable to obtain an IP address. I was using GNOME's settings applet, which is a wrapper for NetworkManager.

			Luckily, using iptables, based on hints provided by (https://wiki.archlinux.org/title/Internet_sharing#With_iptables)[https://wiki.archlinux.org/title/Internet_sharing#With_iptables], I could add a link level packet filter with NAT, using something similar to the these commands (with superuser privileges):

			iptables -t nat -A POSTROUTING -o <ethernet interface name> -j MASQUERADE
			iptables -A FORWARD -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT
			iptables -A FORWARD -i <wifi adapter name> -o <ethernet interface name> -j ACCEPT

			You can find the network interface names with ifconfig.

	=== Wayland User Experience ===		=== Wayland User Experience ===

	==== Lag with NVIDIA GPU's ====		==== Lag with NVIDIA GPU's ====
	If you have an AMD graphics card, either integrated or dedicated, you will likely be accustomed to having a better user experience than those with NVIDIA graphics cards.		If you have an AMD graphics card, either integrated or dedicated, you will likely be accustomed to having a better user experience than those with NVIDIA graphics cards.

Root: /* Lag with NVIDIA GPU's */

2025-02-25T08:09:51Z

Lag with NVIDIA GPU's

@@ Line 13: / Line 13: @@
   sudo nvidia-smi -lmc 1000,6000
   sudo nvidia-smi -lgc 1000,2000
-The first command enables the persistence mode daemon, which keeps the kernel mode driver running (even when no other application is actively using it), the second locks the memory clock between 1000 and 6000 MHz, and the last, locks the graphics clock to be between 1000 and 2000 MHz.
+The first command enables the persistence mode daemon, which keeps the kernel mode driver running (even when no other application is actively using it), the second locks the memory clock between 1000 and 6000 MHz, and the last, locks the graphics clock to be between 1000 and 2000 MHz. The command line arguments cannot be combined into one invocation, as nvidia-smi will not allow it.
 ==== OpenGL/X11 Application Not Running With a Dedicated NVIDIA GPU ====

Root at 09:40, 29 January 2025

2025-01-29T09:40:33Z

← Older revision		Revision as of 09:40, 29 January 2025
Line 15:		Line 15:
	The first command enables the persistence mode daemon, which keeps the kernel mode driver running (even when no other application is actively using it), the second locks the memory clock between 1000 and 6000 MHz, and the last, locks the graphics clock to be between 1000 and 2000 MHz.		The first command enables the persistence mode daemon, which keeps the kernel mode driver running (even when no other application is actively using it), the second locks the memory clock between 1000 and 6000 MHz, and the last, locks the graphics clock to be between 1000 and 2000 MHz.

	==== ~~GLX~~ Application ~~not~~ Running on NVIDIA GPU ====		==== OpenGL/X11 Application Not Running With a Dedicated NVIDIA GPU ====
	I encountered this issue when running ''Freecad,'' which, in my case, could not use my dedicated GPU due to initialization issues with ~~a GLX component (~~OpenGL ~~Extensions~~ for X11). I use this code below, within a script, to ensure Freecad's rendering path goes a different way:		I encountered this issue when running ''Freecad,'' which, in my case, could not use my dedicated GPU due to initialization issues with the OpenGL Extension for X11 (GLX). I use this code below, within a script, to ensure Freecad's rendering path goes a different way:
	Xwayland -decorate -geometry 1920x1080 :2 &		Xwayland -decorate -geometry 1920x1080 :2 &
	QT_QPA_PLATFORM=xcb prime-run freecad -display :2		QT_QPA_PLATFORM=xcb prime-run freecad -display :2