New updates in -current, including 4.14 kernel

orbea · 11-18-2017, 03:08 AM

Quote:

Originally Posted by ReaperX7

The nvidia-driver is extremely picky over which kernel it supports. Unfortunately, this is nothing new, so you're going to be stuck using nouveau or modesetting with egl enabled for the time being.

Fyi the xf86-video-nouveau and modesetting ddx that is included in xorg-server are only the xorg drivers. Nouveau has components as part of libdrm, mesa and the kernel too. So even even with the modesetting ddx you could still be using nouveau. Its simply a generic solution that can be shared among the various gpu drivers. Opinions on which one is preferred do not really seem to be consistent among nouveau developers. Personally I find modesetting avoids several bugs, but the opposite could be true for other people.

ReaperX7 · 11-18-2017, 03:17 AM

I technically use nvidia-driver only on my 14.2 stable machine, but I do use modesetting's egl driver for nouveau acceleration in my -Current machine.

I prefer modesetting as it does seem to have a few less issues with my GTX 460 when starting X.

tazza · 11-18-2017, 03:51 AM

We can talk about nvidia binary blobs until the cows come home (ie why tf do they install vulcan drivers for cards that are not compatible) but back to the upgrades in -current.

Anyone had issues with CPU speed being locked? ie

Code:

cat /proc/cpuinfo | grep '^cpu MHz' | sed -e 's/.*: //' | sed -e 's/\..../ MHz/' | head -n 1

always shows 3800.. no matter what load the system is under. In the past it would vary from 800-4200 depending upon the load. I tried changing the bios to a forced multiplier of 48x100 ie 4800 and it still shows 3800.

GazL · 11-18-2017, 04:18 AM

Quote:

Originally Posted by tazza

We can talk about nvidia binary blobs until the cows come home (ie why tf do they install vulcan drivers for cards that are not compatible) but back to the upgrades in -current.

Anyone had issues with CPU speed being locked? ie

Code:

cat /proc/cpuinfo | grep '^cpu MHz' | sed -e 's/.*: //' | sed -e 's/\..../ MHz/' | head -n 1

always shows 3800.. no matter what load the system is under. In the past it would vary from 800-4200 depending upon the load. I tried changing the bios to a forced multiplier of 48x100 ie 4800 and it still shows 3800.

https://lwn.net/Articles/738812/

Quote:

The most noticeable last-minute change is probably that we had to
revert the code that showed a good MHz value in /proc/cpuinfo even for
the modern "CPU picks frequency dynamically" case. It worked fine, but
it was much too expensive on machines with tens or hundreds of CPU
cores. There's a cunning plan, but it didn't make 4.14, so we'll get
it working and then back-port.

You need to look at the values in /sys/devices/system/cpu/cpu0/cpufreq/ instead, or better yet, just use cpufreq-info -f.

cgorac · 11-18-2017, 04:36 AM

Quote:

Originally Posted by tazza

We can talk about nvidia binary blobs until the cows come home (ie why tf do they install vulcan drivers for cards that are not compatible)...

The point is not in talking about Nvidia drivers in particular, but in making bold statement about configuration that it seems given person is not actually using.

allend · 11-18-2017, 05:12 AM

Just testing what my post looks like now that Firefox 57.0 no longer has the general.useragent.override setting.

PS - Thought so. I have lost the Slackware logo.

tazza · 11-18-2017, 05:50 AM

Quote:

Originally Posted by GazL

https://lwn.net/Articles/738812/

You need to look at the values in /sys/devices/system/cpu/cpu0/cpufreq/ instead, or better yet, just use cpufreq-info -f.

Thanks mate, really appreciate it

Quote:

Originally Posted by cgorac

The point is not in talking about Nvidia drivers in particular, but in making bold statement about configuration that it seems given person is not actually using.

Ok my bad (I hate using that term, and rarely do, but it seems apt here) +1.

Quote:

Originally Posted by allend

Just testing what my post looks like now that Firefox 57.0 no longer has the general.useragent.override setting.

PS - Thought so. I have lost the Slackware logo.

Yeah - a lot of stuff is cut out and a lot of stuff (data) is gathered whether you allow it or not. I knew they always farmed links but now.. well...

anon074 · 11-18-2017, 09:13 AM

The NIS domain is no longer set by /etc/rc.d/rc.yp. The new command doesn't output "(none)" if the domain has not been set.

Code:

if [ "$(nisdomainname)" = "(none)" ]; then
  nisdomainname $(cat /etc/defaultdomain)
fi

Aeterna · 11-18-2017, 01:03 PM

Quote:

Originally Posted by tazza

Thanks mate, really appreciate it

Ok my bad (I hate using that term, and rarely do, but it seems apt here) +1.

Yeah - a lot of stuff is cut out and a lot of stuff (data) is gathered whether you allow it or not. I knew they always farmed links but now.. well...

if you set resist fingerprinting it will mess with useragent anyway.
Clearly linuxquestions.org is not using OS fingerprinting but browser fingerprinting which is not reliable. Just install add-on that changes browser fingerprintig and disable resist fingerprinting in FF57

rworkman · 11-18-2017, 07:38 PM

Quote:

Originally Posted by voegelas

The NIS domain is no longer set by /etc/rc.d/rc.yp. The new command doesn't output "(none)" if the domain has not been set.

Code:

if [ "$(nisdomainname)" = "(none)" ]; then
  nisdomainname $(cat /etc/defaultdomain)
fi

If you change that to look like this, does it work again?

Code:

  if ! /bin/nisdomainname 1>/dev/null 2>/dev/null ; then
    /bin/nisdomainname $(cat /etc/defaultdomain)
  fi

anon074 · 11-19-2017, 06:41 AM

Quote:

Originally Posted by rworkman

If you change that to look like this, does it work again?

Code:

  if ! /bin/nisdomainname 1>/dev/null 2>/dev/null ; then
    /bin/nisdomainname $(cat /etc/defaultdomain)
  fi

Yes, that works. But I don't know why there's an if-condition at all.

Chuck56 · 11-19-2017, 09:21 AM

Code:

bash-4.4$ uname -a
Linux slacker.localdomain 4.14.0 #1 SMP Sat Nov 18 16:41:11 CST 2017 x86_64 AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G AuthenticAMD GNU/Linux

I upgraded the 2 mozilla files on my current-64 desktop on Friday. I wanted to deal with the FF 57 changes mostly due to the legacy addons separate from the the other system changes.

Saturday morning I upgraded the still pending Friday changes (UEFI install) and all went well. My open issue is learning to use Postfix instead of Sendmail. I can slow roll that learning process as it isn't as important on my current-64 desktop as on my 14.2-64 servers when the time comes.

Today, Sunday morning, I upgraded with the latest changes after Friday's massive update. All is well. The system booted up after making the UEFI changes, the /var/log files appear clean of errors. So far so good!

Thanks again to the core team for a great series of updates to slackware-current!

glorsplitz · 11-19-2017, 10:50 AM

Quote:

Originally Posted by Chuck56

Thanks again to the core team for a great series of updates to slackware-current!

same here, thank you!

hitest · 11-19-2017, 12:51 PM

Quote:

Originally Posted by Chuck56

Today, Sunday morning, I upgraded with the latest changes after Friday's massive update. All is well.

Yes. All is well here. Many thanks to Pat and the entire Slackware Team.

Code:

bash-4.4$ uname -a
Linux thor.thor 4.14.0 #2 SMP Sat Nov 18 16:51:58 CST 2017 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz GenuineIntel GNU/Linux

slackb0t · 11-19-2017, 09:11 PM

All updates completed... everything working fine so far.

Code:

$ uname -a
Linux slackware.slackware.org 4.14.0 #1 SMP Sat Nov 18 16:41:11 CST 2017 x86_64 Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GenuineIntel GNU/Linux