[SOLVED] Very cool!!!

hitest · 11-30-2019, 04:39 PM

Today's current changelog.

http://slackware.osuosl.org/slackwar.../ChangeLog.txt

SqdnGuns · 11-30-2019, 04:59 PM

Quote:

Originally Posted by hitest

Today's current changelog.

http://slackware.osuosl.org/slackwar.../ChangeLog.txt

See anything odd/new with dmesg?

hitest · 11-30-2019, 05:06 PM

Quote:

Originally Posted by SqdnGuns

See anything odd/new with dmesg?

Just ran dmesg. Included the last bit of dmesg.

Code:

bash-5.0$ sudo dmesg
[    0.000000] Linux version 5.4.1 (root@hive64.slackware.lan) (gcc version 9.2.0 (GCC)) #1 SMP Sat Nov 30 14:09:29 CST 2019

[  276.191051] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36208 WINDOW=0 RES=0x00 RST URGP=0 
[  276.191076] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36208 WINDOW=0 RES=0x00 RST URGP=0 
[  276.191088] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36208 WINDOW=0 RES=0x00 RST URGP=0 
[  357.377078] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=66.163.35.36 DST=192.168.1.12 LEN=52 TOS=0x00 PREC=0x00 TTL=242 ID=7351 DF PROTO=TCP SPT=443 DPT=42188 WINDOW=2560 RES=0x00 ACK URGP=0 
[  853.064435] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=172.217.14.205 DST=192.168.1.12 LEN=40 TOS=0x00 PREC=0x00 TTL=122 ID=0 DF PROTO=TCP SPT=443 DPT=52224 WINDOW=0 RES=0x00 RST URGP=0 
[ 1098.766503] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=54.201.252.209 DST=192.168.1.12 LEN=40 TOS=0x00 PREC=0x00 TTL=45 ID=0 DF PROTO=TCP SPT=443 DPT=58668 WINDOW=0 RES=0x00 RST URGP=0 
[ 1189.072036] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=54.201.252.209 DST=192.168.1.12 LEN=40 TOS=0x00 PREC=0x00 TTL=44 ID=0 DF PROTO=TCP SPT=443 DPT=58672 WINDOW=0 RES=0x00 RST URGP=0 
[ 1474.481021] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36558 WINDOW=0 RES=0x00 RST URGP=0 
[ 1474.481047] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36558 WINDOW=0 RES=0x00 RST URGP=0 
[ 1474.481064] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36558 WINDOW=0 RES=0x00 RST URGP=0 
[ 1474.481068] Invalid packet: IN=eth0 OUT= MAC=18:03:73:2a:3e:e7:74:d0:2b:42:b1:c8:08:00 SRC=23.59.158.215 DST=192.168.1.12 LEN=40 TOS=0x08 PREC=0x40 TTL=54 ID=0 DF PROTO=TCP SPT=443 DPT=36558 WINDOW=0 RES=0x00 RST URGP=0 
bash-5.0$

SqdnGuns · 11-30-2019, 06:10 PM

So, I decided to take the plunge.

Only issue was when I rebooted. I have two NVME SSD's, one is for /storage and the other is for /home. For some odd reason, they switched. I had to edit my fstab so they would mount properly. Rebooted and all is well. Also, no problem running the Nvidia driver.

glorsplitz · 11-30-2019, 09:17 PM

I'm not fabulously weathly like hitest to have so much bare metal lying around.

Couple currents in vbox, one with kde5, booted and are up and running.

Quote:

[Sat Nov 30 22:01:44 2019] Linux version 5.4.1 (root@hive64.slackware.lan) (gcc version 9.2.0 (GCC)) #1 SMP Sat Nov 30 14:09:29 CST 2019

Quote:

Originally Posted by SqdnGuns

I had to edit my fstab so they would mount properly.

did you have to use UUIDs?

PROBLEMCHYLD · 11-30-2019, 11:16 PM

Wrong post. Sorry.

FlinchX · 12-01-2019, 03:04 AM

I would like to know if nvidia-legacy390 from SBo works with the 5.x kernel.

ZhaoLin1457 · 12-01-2019, 03:23 AM

Quote:

Originally Posted by FlinchX

I would like to know if nvidia-legacy390 from SBo works with the 5.x kernel.

Not with 5.4.x

marrowsuck · 12-01-2019, 03:38 AM

Two boxes migrated. Everything works so far expect for the VirtualBox-6.0.14 kernel module.

Code:

[…]
.h -fno-omit-frame-pointer -fno-pie -Wno-declaration-after-statement -I./include -I/tmp/vbox.0/ -I/tmp/vbox.0/include -I/tmp/vbox.0/r0drv/linux -D__KERNEL__ -DMODULE -DRT
_WITHOUT_PRAGMA_ONCE -DRT_OS_LINUX -DIN_RING0 -DIN_RT_R0 -DIN_SUP_R0 -DVBOX -DRT_WITH_VBOX -DVBOX_WITH_HARDENING -DSUPDRV_WITH_RELEASE_LOGGER -DVBOX_WITH_64_BITS_GUESTS -
DCONFIG_VBOXDRV_AS_MISC -DRT_ARCH_AMD64  -DMODULE  -DKBUILD_BASENAME='"SUPDrvSem"' -DKBUILD_MODNAME='"vboxdrv"' -c -o /tmp/vbox.0/SUPDrvSem.o /tmp/vbox.0/SUPDrvSem.c
In file included from ././include/linux/compiler_types.h:59,
                 from <command-line>:
/tmp/vbox.0/SUPDrvGip.c: In function ‘supdrvTscDeltaThread’:
./include/linux/compiler_attributes.h:200:41: error: expected ‘)’ before ‘__attribute__’
  200 | # define fallthrough                    __attribute__((__fallthrough__))
      |                                         ^~~~~~~~~~~~~
/tmp/vbox.0/include/iprt/cdefs.h:1169:48: note: in expansion of macro ‘fallthrough’
 1169 | # define RT_FALL_THROUGH()      __attribute__((fallthrough))
      |                                                ^~~~~~~~~~~
[…]

marrowsuck · 12-01-2019, 03:46 AM

Fix for VirtualBox will probably arrive in 6.1.
https://www.linuxquestions.org/quest...ml#post6063586

Olek · 12-01-2019, 09:00 AM

Like after every kernel upgrade I run r8168.SlackBuild.
This time, they start build all kernel modules!
So, I interrupted SBo build process and I am running now on vanilla kernel Realtek r8169 module.
I will see, maybe module from 5.4.x kernel is fixed?
If yes, there is no need to use SBo r8168 module.

hitest · 12-01-2019, 04:41 PM

Quote:

Originally Posted by glorsplitz

I'm not fabulously weathly like hitest to have so much bare metal lying around.

Heh-heh. It would be nice if I was wealthy. I'm a retired teacher living comfortably. All of my 6 desktops/laptops that are running Slackware64-current are second hand units mostly picked up on ebay.
Slackware 15.0 is shaping up to be an amazing release.

FlinchX · 12-01-2019, 06:19 PM

Quote:

Originally Posted by ZhaoLin1457

Not with 5.4.x

So I'll not be able to use 15.0 when it's out unless I upgrade my GPU hardware?

Edit: just found this https://devtalk.nvidia.com/default/t.../post/5399849/

FlinchX · 12-01-2019, 06:21 PM

Quote:

Originally Posted by Olek

Like after every kernel upgrade I run r8168.SlackBuild.
This time, they start build all kernel modules!
So, I interrupted SBo build process and I am running now on vanilla kernel Realtek r8169 module.
I will see, maybe module from 5.4.x kernel is fixed?
If yes, there is no need to use SBo r8168 module.

Keep this info coming, I run 14.2 and my network cards only work with r8168.

phalange · 12-01-2019, 07:08 PM

Very pleasant surprise, this. I have to admit it feels like a milestone, although I realize it's largely symbolic.