14.2 kernel versions

[justwantin]

I installed salix 64 14.2 a couple weeks ago. It installed with a 4.4.19 kernel. Today I had a go at installing vbox but slapt-get -i kernel-source wants to download a 4.4.14 kernel source. I downloaded 4.4.19 source from kernel.org but had several problems and the vbox install script would not build modules. Is there any way to revert to 14.4.14? I did not have any problems with vbox in slackware 14.2

[DidierSpaier]

This looks strange as the current kernel version is 4.4.38. Did you run sudo slapt-get -u? Is your /etc/slapt-get/slapt-getrc correct?

In any case you should not revert to a previous kernel version.

[mimosa]

I just upgraded to 4.4.38, available here, and working fine:

Code: Select all

http://slackware.uk/salix/x86_64/slackware-14.2/patches/packages/linux-4.4.38

If you are unsure how to proceed, please check the wiki / forum.

Please post your slapt-getrc; as DidierSpaier says, it sounds like something may have gone wrong there.

[justwantin]

Sorry guys, I thought I was subscribed to this thread. I never received an email saying anyone replied.

I installed off an ISO downloaded sometime early Dec. and dd'ed to a usb stick. The kernel in the ISO was 14.4.19

Code: Select all

bash-4.3$ ls /run/media/rick/SALIX64/salix/kernels/
kernel-huge-4.4.19-x86_64-1_slack14.2.desc
kernel-huge-4.4.19-x86_64-1_slack14.2.md5
kernel-huge-4.4.19-x86_64-1_slack14.2.txz
kernel-modules-4.4.19-x86_64-1_slack14.2.desc
kernel-modules-4.4.19-x86_64-1_slack14.2.md5
kernel-modules-4.4.19-x86_64-1_slack14.2.txz

However, slapt-get wants to download 14.4.14

Code: Select all

root[rick]# slapt-get -i kernel-source
Reading Package Lists...Done
The following NEW packages will be installed:
  kernel-source 
0 upgraded, 0 reinstalled, 1 newly installed, 0 to remove, 0 not upgraded.
Need to get 79.2MB/86.8MB of archives.
After unpacking 624.8MB of additional disk space will be used.
1/1 Get http://salix.hostingxtreme.com/x86_64/slackware-14.2/ kernel-source 4.4.14-noarch-1 [79.2MB]...^C1%

Here's my slapt-getrc:

Code: Select all

bash-4.3$ cat /etc/slapt-get/slapt-getrc 
WORKINGDIR=/var/slapt-get
EXCLUDE=^aaa_elflibs,^aaa_base,^devs,^glibc.*,^kernel-.*,^rootuser-settings,^zzz-settings.*,-i?86-
SOURCE=http://salix.hostingxtreme.com/x86_64/slackware-14.2/:OFFICIAL
SOURCE=http://salix.hostingxtreme.com/x86_64/slackware-14.2/extra/:OFFICIAL
SOURCE=http://salix.hostingxtreme.com/x86_64/14.2/:PREFERRED
SOURCE=http://salix.hostingxtreme.com/x86_64/extra-14.2/:OFFICIAL

Current kernel version may be 4.4.38 but I would have expected SalixXfce-14.2 to be "stable" and not following current. I'm not too interested in anything but a "stable install on my desktop. I only follow current on a couple arm devices for fun.

[justwantin]

I just had a look and I see now that not only did the kernel change in current but in stable as well, my bad. So now I have to upgrade the whole kernel kit and kaboodle.. hmm...... and all because I want to run Odin on XP (which requires me to run vbox) so I can hose my galaxy S5 to install Cyanogen mod. I shouldv'e had a closer look before the holiday break, I start work again tomorrow....... sigh.

[gapan]

The original kernel in Slackware 14.2 was 4.4.14. That has been upgraded a few times due to security issues. Salix Xfce 14.2 was released at the time 4.4.19 was included, so we included the patched kernel. Slackware only keeps the original package (in this case 4.4.14) and the latest patch (currently 4.4.38) in their repositories, removing any intermediate patches. So yes, best thing to do is upgrade all kernel packages. It should be quite straight-forward from the command line using slapt-get. Check the wiki.

[colebaas]

@justwantin

I want to run Odin on XP (which requires me to run vbox) so I can hose my galaxy S5

... or you could just use Heimdall strait from Slackware.

[justwantin]

Thanks to all who replied. I'll get around to the kernel eventually.
@colebass, I rooted my galaxy s5 yesterday using heimdall CLI but only after recompiling with code change as per turboyz's post on this thread:https://github.com/Benjamin-Dobell/Heimdall/issues/348

[colebaas]

@justwantin

That is correct. There is/was the empty USB packet issue which is a Samsung bug and which we ourselves fixed some time ago. May be one should roll a Slack package with the correction, although I'm unclear whether there is enough interest out there?