LinuxQuestions.org - [SOLVED] New Kernel in Slackware-current

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - New Kernel in Slackware-current (https://www.linuxquestions.org/questions/slackware-14/new-kernel-in-slackware-current-4175605279/)

New Kernel in Slackware-current

Many thanks to Pat and the entire Slackware Team. There's a new kernel in -current. :cool:

Code:

Thu May  4 22:14:08 UTC 2017

a/btrfs-progs-v4.10.2-x86_64-2.txz:  Rebuilt.

  Ship libbtrfs shared library. Thanks to Vincent Batts.

a/elilo-3.16-x86_64-3.txz:  Rebuilt.

  Patched eliloconfig to properly handle NVMe devices.

  Thanks to Didier Spaier.

a/gettext-0.19.8.1-x86_64-3.txz:  Rebuilt.

a/glibc-solibs-2.25-x86_64-1.txz:  Upgraded.

a/kernel-firmware-20170504git-noarch-1.txz:  Upgraded.

a/kernel-generic-4.9.26-x86_64-1.txz:  Upgraded.

a/kernel-huge-4.9.26-x86_64-1.txz:  Upgraded.

a/kernel-modules-4.9.26-x86_64-1.txz:  Upgraded.

ap/nano-2.8.2-x86_64-1.txz:  Upgraded.

d/flex-2.6.2-x86_64-1.txz:  Upgraded.

  Switched to flex-2.6.2 until there's a new release that fixes unexpected

  symbol remapping macro definitions in flex-2.6.3.

  See:  https://github.com/westes/flex/issues/162

d/gcc-7.1.0-x86_64-1.txz:  Upgraded.

d/gcc-brig-7.1.0-x86_64-1.txz:  Added.

d/gcc-g++-7.1.0-x86_64-1.txz:  Upgraded.

d/gcc-gfortran-7.1.0-x86_64-1.txz:  Upgraded.

  Shared library .so-version bump.

d/gcc-gnat-7.1.0-x86_64-1.txz:  Upgraded.

  Shared library .so-version bump.

d/gcc-go-7.1.0-x86_64-1.txz:  Upgraded.

  Shared library .so-version bump.

d/gcc-java-5.4.0-x86_64-1.txz:  Removed.

d/gcc-objc-7.1.0-x86_64-1.txz:  Upgraded.

d/gettext-tools-0.19.8.1-x86_64-3.txz:  Rebuilt.

d/kernel-headers-4.9.26-x86-1.txz:  Upgraded.

k/kernel-source-4.9.26-noarch-1.txz:  Upgraded.

l/glibc-2.25-x86_64-1.txz:  Upgraded.

l/glibc-i18n-2.25-x86_64-1.txz:  Upgraded.

l/glibc-profile-2.25-x86_64-1.txz:  Upgraded.

isolinux/initrd.img:  Rebuilt.

  Patched SeTEFI and probe to fix NVMe device handling.

  Thanks to Didier Spaier.

kernels/*:  Upgraded.

usb-and-pxe-installers/usbboot.img:  Rebuilt.

  Patched SeTEFI and probe to fix NVMe device handling.

  Thanks to Didier Spaier.

+--------------------------+

Started testing right after you posted.

[problemchyld@darkstar:~] $ uname -r
4.9.26-smp
[problemchyld@darkstar:~] $

Code:

bash-4.4$ uname -a

Linux odin 4.9.26 #2 SMP Thu May 4 03:46:26 CDT 2017 x86_64 Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz GenuineIntel GNU/Linux

Everything seems to work well here.

Finally!

Now I can use Pat's latest LTS vetted .config and piggyback it on -stable :)

Code:

% uname -a                                                                    

Linux ouroboros 4.9.26 #1 SMP Fri May 5 11:31:02 CEST 2017 x86_64 Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz GenuineIntel GNU/Linux

So far, so good....

Quote:

Linux 4.9.26 #1 SMP Thu May 4 03:36:04 CDT 2017 x86_64....

Question, does the #1 indicate it is the generic kernel and the #2 (see post number 3, above) the huge kernel?

patch for nvidia legacy kernel

You might need to patch NVIDIA legacy 340 run file; test with 340.102 file and works
source

Code:

--- kernel/nv-drm.c        2016-12-15 12:41:26.000000000 +0100

+++ kernel/nv-drm.c        2016-12-15 12:58:48.000000000 +0100 

@@ -115,7 +115,11 @@ 

 };

 static struct drm_driver nv_drm_driver = { 

+#if LINUX_VERSION_CODE >= KERNEL_VERSION(4, 9, 0) 

+    .driver_features = DRIVER_GEM | DRIVER_PRIME | DRIVER_LEGACY, 

+#else      .driver_features = DRIVER_GEM | DRIVER_PRIME, 

+#endif      .load = nv_drm_load,

      .unload = nv_drm_unload,

      .fops = &nv_drm_fops,

Its running good here ;)

Quote:

Originally Posted by cwizardone (Post 5706746)

So far, so good....
Question, does the #1 indicate it is the generic kernel and the #2 (see post number 3, above) the huge kernel?

uname -v
#1 SMP Thu May 4 03:36:04 CDT 2017
is the version number according to man uname
John
[EDIT]
misread the question!
1 = generic
2 = huge
[/EDIT]

And GCC 7 too. That's a big jump. I wonder why 6 was skipped over (only in testing)?

On my laptop with new kernel (32 bit) I can't compile virtualbox module and I have in /var/log/syslog this errors:

Quote:

May 6 20:00:40 laptop kernel: [ 185.925136] WARNING: CPU: 0 PID: 3712 at drivers/gpu/drm/drm_irq.c:1254 drm_wait_one_vblank+0x17c/0x190 [drm]
May 6 20:00:40 laptop kernel: [ 185.925139] vblank wait timed out on crtc 0
May 6 20:00:40 laptop kernel: [ 185.925141] Modules linked in: rfcomm nfsd ipv6 bnep tun fuse i2c_dev btusb btrtl btbcm btintel bluetooth ssb_hcd b43 bcma mac80211 cfg80211 tpm_i
nfineon joydev hp_wmi sparse_keymap rfkill ppdev coretemp acpi_cpufreq kvm_intel kvm irqbypass evdev psmouse serio_raw snd_hda_codec_hdmi snd_hda_codec_analog snd_hda_codec_generic
firewire_ohci ssb tg3 firewire_core yenta_socket ptp pcmcia_rsrc mmc_core lpc_ich pps_core pcmcia libphy pcmcia_core hwmon snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep uhci_
hcd snd_pcm snd_timer snd soundcore shpchp i915 drm_kms_helper drm ehci_pci ehci_hcd i2c_algo_bit fb_sys_fops syscopyarea sysfillrect sysimgblt i2c_core intel_agp intel_gtt agpgart
fan thermal wmi parport_pc parport hp_accel lis3lv02d input_polldev video tpm_tis tpm_tis_core fjes tpm battery button ac
May 6 20:00:40 laptop kernel: [ 185.925285] loop ext4 jbd2 mbcache
May 6 20:00:40 laptop kernel: [ 185.925299] CPU: 0 PID: 3712 Comm: Xorg Tainted: G W O 4.9.26-smp #1
May 6 20:00:40 laptop kernel: [ 185.925302] Hardware name: Hewlett-Packard HP Compaq 6710b (RJ459AV)/30C0, BIOS 68DDU Ver. F.20 12/01/2011
May 6 20:00:40 laptop kernel: [ 185.925305] f1f21abc c12e3563 f1f21b00 f8665908 f1f21aec c1059bfa f8669dc8 f1f21b1c
May 6 20:00:40 laptop kernel: [ 185.925319] 00000e80 f8665908 000004e6 f863f3ec 000004e6 f76a0000 00000000 00000000
May 6 20:00:40 laptop kernel: [ 185.925331] f1f21b08 c1059c5b 00000009 00000000 f1f21b00 f8669dc8 f1f21b1c f1f21b4c
May 6 20:00:40 laptop kernel: [ 185.925344] Call Trace:
May 6 20:00:40 laptop kernel: [ 185.925357] [<c12e3563>] dump_stack+0x47/0x64
May 6 20:00:40 laptop kernel: [ 185.925365] [<c1059bfa>] __warn+0xea/0x110
May 6 20:00:40 laptop kernel: [ 185.925397] [<f863f3ec>] ? drm_wait_one_vblank+0x17c/0x190 [drm]
May 6 20:00:40 laptop kernel: [ 185.925403] [<c1059c5b>] warn_slowpath_fmt+0x3b/0x40
May 6 20:00:40 laptop kernel: [ 185.925434] [<f863f3ec>] drm_wait_one_vblank+0x17c/0x190 [drm]
May 6 20:00:40 laptop kernel: [ 185.925443] [<c109a8f0>] ? wake_bit_function+0x70/0x70
May 6 20:00:40 laptop kernel: [ 185.925525] [<f88ce857>] intel_get_load_detect_pipe+0x627/0x680 [i915]
May 6 20:00:40 laptop kernel: [ 185.925600] [<f890ae15>] intel_tv_detect+0x135/0x5f0 [i915]
May 6 20:00:40 laptop kernel: [ 185.925636] [<f8650d60>] ? crtc_commit_free+0x10/0x20 [drm]
May 6 20:00:40 laptop kernel: [ 185.925658] [<f86b8cee>] drm_helper_probe_single_connector_modes+0x9e/0x500 [drm_kms_helper]
May 6 20:00:40 laptop kernel: [ 185.925666] [<c1655c20>] ? mutex_lock+0x10/0x30
May 6 20:00:40 laptop kernel: [ 185.925701] [<f8655a37>] drm_mode_getconnector+0xb7/0x2d0 [drm]
May 6 20:00:40 laptop kernel: [ 185.925736] [<f8655980>] ? drm_mode_connector_property_set_ioctl+0x40/0x40 [drm]
May 6 20:00:40 laptop kernel: [ 185.925766] [<f863d93e>] drm_ioctl+0x20e/0x470 [drm]
May 6 20:00:40 laptop kernel: [ 185.925801] [<f8655980>] ? drm_mode_connector_property_set_ioctl+0x40/0x40 [drm]
May 6 20:00:40 laptop kernel: [ 185.925808] [<c1094b9a>] ? trigger_load_balance+0x11a/0x1b0
May 6 20:00:40 laptop kernel: [ 185.925838] [<f863d730>] ? drm_version+0x80/0x80 [drm]
May 6 20:00:40 laptop kernel: [ 185.925845] [<c11b2f31>] do_vfs_ioctl+0x81/0x6c0
May 6 20:00:40 laptop kernel: [ 185.925852] [<c103e538>] ? lapic_next_event+0x18/0x20
May 6 20:00:40 laptop kernel: [ 185.925859] [<c10d244d>] ? clockevents_program_event+0xfd/0x160
May 6 20:00:40 laptop kernel: [ 185.925865] [<c10c436a>] ? __hrtimer_run_queues+0x12a/0x240
May 6 20:00:40 laptop kernel: [ 185.925871] [<c10d40d0>] ? tick_program_event+0x40/0x90
May 6 20:00:40 laptop kernel: [ 185.925877] [<c11b35d3>] SyS_ioctl+0x63/0x80
May 6 20:00:40 laptop kernel: [ 185.925883] [<c10019a7>] do_int80_syscall_32+0x57/0xc0
May 6 20:00:40 laptop kernel: [ 185.925889] [<c16588dd>] entry_INT80_32+0x31/0x31
May 6 20:00:40 laptop kernel: [ 185.925894] ---[ end trace 5684cb2aee4c8a3a ]---

Even with the binary from Oracle VirtualBox won't work either.

VirtualBox-5.1.14-112924-Linux_amd64.run and kernel 4.9.26 work fine together.

I was planning to upgrade to the latest VB 5.1.22 but after reading your posts I am not sure if it will work.

Running it in VirtualBox 5.1.2.2 doesn't work for me. I get "unknown symbol" errors when I try to modprobe vboxguest.

Quote:

Originally Posted by willysr (Post 5707088)

Even with the binary from Oracle VirtualBox won't work either.

I downloaded the .run vbox from Oracle this morning. It is working okay for me.

I just installed all new updates.. including the new kernel. No issues so far. All went smooth.