MX Linux Forum

manyroads wrote: Tue Jan 29, 2019 10:44 am Please place the results of MX Tools- Quick System Info here to help people understand what your platform looks like.

I seriously doubt if there's a big of people here using VMware. Why pray tell does elementary need such a monstrous amount of video mem? (Never mind the requirement just seems weird.)

Adrian wrote: Fri Feb 15, 2019 9:57 am I think you get post notifications if you "subscribe" to the post, otherwise you don't get it by default. Or it might be a setting in your profile that you need to tick (not sure I don't need that).

As for the issue, I want to understand something, if you boot MX live, the original release do you have the same problem? So the question becomes, is this a "MX" problem or it's a setting that was screwed up somehow later on?

Adrian wrote: Fri Feb 15, 2019 9:57 am I think you get post notifications if you "subscribe" to the post, otherwise you don't get it by default. Or it might be a setting in your profile that you need to tick (not sure I don't need that).

As for the issue, I want to understand something, if you boot MX live, the original release do you have the same problem? So the question becomes, is this a "MX" problem or it's a setting that was screwed up somehow later on?

v3g4n wrote: Fri Feb 15, 2019 11:33 am I would see if you have the network issues while running live also because that may be root of the steam issue. If the network issues are not there while running live then I'm guessing it may have something to do with your firewall rules you created. By the way, what were they?

dolphin_oracle wrote: Fri Feb 15, 2019 1:19 pm do you have a previously existing ~/.local/share/Steam folder? I'm thinking that maybe its looking for a network connection that is not longer present.

dolphin_oracle wrote: Fri Feb 15, 2019 1:46 pm this is a dumb question, but did you say "yes" to the license agreement?

Stevo wrote: Fri Feb 15, 2019 3:49 pm Off-topic, but you don't need those two Waterfox repos, since we have it in our own repo and it's installable in the MX Package Installer.

timkb4cq wrote: Fri Feb 15, 2019 7:31 pm You have a Realtek 8111h ethernet chipset. Realtek suggests using the non-free r8168 driver for that chipset instead of the open source r8169 driver present in the kernel.

To build the r8168 driver, install the r8168-dkms package. This package builds the non-free driver and disables the one you are now using.
I would use

Code: Select all

sudo apt-get r8168-dkms

because you will see the messages as the driver auto-builds. It should work - but I haven't tried it with the newer kernels, and if the messages show that it failed you will want to

Code: Select all

dpkg -P 8168-dkms

before you reboot, lest you be left with no network driver at all.

Update 21:03
The r8168-dkms version 8.043.02 in debian stretch will not build with kernel 4.19. I have backported the buster version for the MX repo. I tested it with the same kernel version you have and it does build a working driver. Since I didn't have your particular problem I can't guarantee it will solve it but it does function normally on my similar realtek 8111 chipset.

Check to make sure your mirror has r8168-dkms version 8.046.00-1~mx17 before trying to install the package.

timkb4cq wrote: Fri Feb 15, 2019 7:31 pm You have a Realtek 8111h ethernet chipset. Realtek suggests using the non-free r8168 driver for that chipset instead of the open source r8169 driver present in the kernel.

To build the r8168 driver, install the r8168-dkms package. This package builds the non-free driver and disables the one you are now using.
I would use

Code: Select all

sudo apt-get r8168-dkms

because you will see the messages as the driver auto-builds. It should work - but I haven't tried it with the newer kernels, and if the messages show that it failed you will want to

Code: Select all

dpkg -P 8168-dkms

before you reboot, lest you be left with no network driver at all.

Update 21:03
The r8168-dkms version 8.043.02 in debian stretch will not build with kernel 4.19. I have backported the buster version for the MX repo. I tested it with the same kernel version you have and it does build a working driver. Since I didn't have your particular problem I can't guarantee it will solve it but it does function normally on my similar realtek 8111 chipset.

Check to make sure your mirror has r8168-dkms version 8.046.00-1~mx17 before trying to install the package.

timkb4cq wrote: Sat Feb 16, 2019 9:45 am Let's check a setting that has caused users some problems in the past.
Right Click on the network manager icon in the panel.
Select Edit Connections...
Select Wired connection 1 and press Edit
Select the General tab.
Two checkboxes should be checked
Automatically connect to this network when it is available
and
All users may connect to this network

The latter box being unchecked has been a problem before.

If it is checked, run an online speedtest like Ookla's to see if it's actually a problem with network speed or something specific to Steam.

timkb4cq wrote: Wed Feb 20, 2019 2:17 pm Have you run an online speedtest (like speedsmart.net or speedtest.net) to see if it's a general problem rather than something Steam related?

dolphin_oracle wrote: Wed Feb 20, 2019 2:59 pm might be time to check the /etc/hosts file and see if you've got any blocking entries.

or maybe do you have a vpn?

timkb4cq wrote: Wed Feb 20, 2019 3:34 pm You said you had gufw installed. ufw might still have rules enabled.
Let's see

Code: Select all

sudo ufw status verbose

and for good measure

Code: Select all

sudo iptables -L

Sl8er wrote: Wed Feb 20, 2019 4:45 pm

dolphin_oracle wrote: Wed Feb 20, 2019 2:59 pm might be time to check the /etc/hosts file and see if you've got any blocking entries.

or maybe do you have a vpn?

No, I'm not using a VPN
(Does using the VPN function on Opera count? Keeping in mind that I use Chromium for general browsing.)

I opened the hosts file and it had, a staggering, 1138 pages.
Is that normal?

┌─[dolphin@mx]─[05:32:00 pm]─────────────────────────────────────────────────────────────────────[~]
└─> cat /etc/hosts
127.0.0.1	localhost
127.0.0.1       mx

# The following lines are desirable for IPv6 capable hosts
::1		localhost ip6-localhost ip6-loopback
fe00::0		ip6-localnet
ff00::0		ip6-mcastprefix
ff02::1		ip6-allnodes
ff02::2		ip6-allrouters

dolphin_oracle wrote: Wed Feb 20, 2019 5:32 pm

Sl8er wrote: Wed Feb 20, 2019 4:45 pm

dolphin_oracle wrote: Wed Feb 20, 2019 2:59 pm might be time to check the /etc/hosts file and see if you've got any blocking entries.

or maybe do you have a vpn?

No, I'm not using a VPN
(Does using the VPN function on Opera count? Keeping in mind that I use Chromium for general browsing.)

I opened the hosts file and it had, a staggering, 1138 pages.
Is that normal?

if you are using an add blockier that might be normal. but mine is nearly empty.

Code: Select all

┌─[dolphin@mx]─[05:32:00 pm]─────────────────────────────────────────────────────────────────────[~]
└─> cat /etc/hosts
127.0.0.1	localhost
127.0.0.1       mx

# The following lines are desirable for IPv6 capable hosts
::1		localhost ip6-localhost ip6-loopback
fe00::0		ip6-localnet
ff00::0		ip6-mcastprefix
ff02::1		ip6-allnodes
ff02::2		ip6-allrouters

might be worth pursuing.

dolphin_oracle wrote: Thu Feb 21, 2019 6:12 am After you removed the ad blocker did you check to make sure the entries were removed from the hosts file?

dolphin_oracle wrote: Thu Feb 21, 2019 9:00 am everything except what's in my example.

Ok, let me just mention that I see 7 "host" files:

host.conf
hostname
hosts
hosts.allow
hosts.deny
hosts.ORIGINAL
hosts.saved

Is this what I'm supposed to see?
Are the "hosts.allow" and "hosts.deny" supposed to be there?