SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
New kernel running fine here [...]. Virtual Box 6.0.14 barfs at building kernel modules however...
It has probably been noted elsewhere that one fix for Virtual Box and its kernel modules with 5.4.x is to install Virtual Box 6.1 RC1 which certainly rectifies the situation here.
However I have noted one issue with the new kernel: Booting stalls for a good 10 seconds following the line '[ 10.857183] usbcore: registered new interface driver snd-usb-audio'. The output via dmesg shows the following around this line:
Code:
[ 10.654072] input: Logitech Webcam C930e as /devices/pci0000:00/0000:00:01.1/0000:01:00.0/usb1/1-2/1-2:1.0/input/input18
[ 10.655479] usbcore: registered new interface driver uvcvideo
[ 10.656863] USB Video Class driver (1.1.1)
[ 10.857183] usbcore: registered new interface driver snd-usb-audio
[ 101.760298] Adding 4210772k swap on /dev/sda2. Priority:-2 extents:1 across:4210772k SSFS
[ 102.787133] EXT4-fs (sda1): re-mounted. Opts: (null)
[ 102.969109] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[ 103.554688] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
Something odd and slow with setting a swap file, not seen with previous kernels? fdisk on my system shows:
Code:
root@ilium/home/andrew# fdisk -l
Disk /dev/sda: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: CT2000MX500SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb8f67cb2
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 3898607615 3898605568 1.8T 83 Linux
/dev/sda2 3898607616 3907029167 8421552 4G 82 Linux swap
Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: CT2000MX500SSD1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x02c1b74e
Device Boot Start End Sectors Size Id Type
/dev/sdb1 2048 3907029167 3907027120 1.8T 83 Linux
root@ilium/home/andrew#
Sat Nov 30 17:13:31 EST 2019 [25307]: Getting ChangeLog.txt...
0a1,20
> Sat Nov 30 21:17:21 UTC 2019
> a/kernel-generic-5.4.1-x86_64-1.txz: Upgraded.
> a/kernel-huge-5.4.1-x86_64-1.txz: Upgraded.
> a/kernel-modules-5.4.1-x86_64-1.txz: Upgraded.
I'm sure this brings 15.0 closer
John
PS as an aside I've been using 5.4.0/1 on 14.2 since their release no problemo
One less hurdle now, indeed, now just hope the QT gets more fresh, the KDE5 gets even more fresh and an even more fresh 5.4.x kernel to break the latest NVidia *.run for a good measure
RESULTS UPDATE - My 14.2 MultiLib Main install has now been up a few minutes shy of 24 hours with half of that time undergoing Unigine Superposition Stressing. Heating was not a problem at all... GPU never exceeded 58C. I just ran the Benchmark utility and given the only changes from the last benchmarks are kernel and nVidia driver, my scores are substantially up.
The average for 3 runs running 5.0.20 with a slightly earlier nVidia driver (430.50) was 8350 and now, with 5.4.1 and 440.36 the average of 3 runs on High was 8950. Perhaps more valuable was a single run at Extreme with a rather low score of 3680 but minimal FPS increased to 27 FPS from 19 which I really don't understand. There is one point in the test where there is extreme shading and a very large number of various sized items in a lab are flying about that previously behaved in a stuttering fashion but which now are quite smooth. Makes little sense to me but I'll take it!
Well, it must be freezing in hell. The new kernel (5.4.1) has made my old Penryn/GM965 laptops usable again with -current. I was having very slow boot times at ~10 minutes to XFCE. Now working normal again.
I'm having a bad time with Slackware 32 bit current with the 5.4.1 kernel. The last kernel upgrade to 4.19.84 was perfect in my Sony Vaio laptop (dual core). The latest 32 bit huge smp kernel always gives a kernel panic when attempting to unpack the initramd. I even created a current 32 bit dvd to try installing the latest Slackware from scratch, but I can't get past the unpacking initramd kernel panic. I can install the latest generic non-smp kernel, but that only gives me a single core. Any good ideas?
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,000
Rep:
Quote:
Originally Posted by staus
I'm having a bad time with Slackware 32 bit current with the 5.4.1 kernel. The last kernel upgrade to 4.19.84 was perfect in my Sony Vaio laptop (dual core). The latest 32 bit huge smp kernel always gives a kernel panic when attempting to unpack the initramd. I even created a current 32 bit dvd to try installing the latest Slackware from scratch, but I can't get past the unpacking initramd kernel panic. I can install the latest generic non-smp kernel, but that only gives me a single core. Any good ideas?
I read that several hours ago a performance regression involving some bug in PAT code in the 5.4 tree was fixed. Someone noticed a nearly 24% loss in the Phoronix test suite. If this means I can expect further increase in performance, I'm stoked!... but then I know almost nothing about PAT. So I guess my work today is cut out for me.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.