LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
Reload this Page [SOLVED] New kernel in Slackware 14.2
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 10-22-2020, 09:24 AM   #1
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Debian, Slackware
Posts: 7,342

Rep: Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746
New kernel in Slackware 14.2

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

Code:
Wed Oct 21 21:51:26 UTC 2020
patches/packages/kernel-firmware-20201005_58d41d0-noarch-1.txz:  Upgraded.
patches/packages/linux-4.4.240/*:  Upgraded.
  These updates fix various bugs and security issues, including the recently
  discovered "Bleeding Tooth" vulnerability in the Bluetooth subsystem
  (CVE-2020-12351, CVE-2020-12352, and CVE-2020-24490).
  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.
  For more information, see:
    Fixed in 4.4.228:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810
    Fixed in 4.4.229:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12771
    Fixed in 4.4.230:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15393
    Fixed in 4.4.232:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10323
    Fixed in 4.4.233:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26088
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19054
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25212
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9445
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13094
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8043
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16166
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14331
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19448
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19074
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19073
    Fixed in 4.4.234:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14314
    Fixed in 4.4.236:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25285
    Fixed in 4.4.237:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25284
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14390
    Fixed in 4.4.238:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25643
    Fixed in 4.4.239:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25211
    Fixed in 4.4.240:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12351
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12352
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24490
  (* Security fix *)
+--------------------------+
 
Old 10-22-2020, 10:24 PM   #2
agropec
Member
 
Registered: Nov 2014
Posts: 35

Rep: Reputation: Disabled
I did the upgrade, but something that i have no idea had happend!

What could be the problem? What should i do, please?
Last edited by agropec; 10-27-2020 at 01:26 AM.
 
Old 10-23-2020, 12:44 AM   #3
Paulo2
Member
 
Registered: Aug 2012
Distribution: Slackware64 15.0 (started with 13.37). Testing -current in a spare partition.
Posts: 928

Rep: Reputation: 515Reputation: 515Reputation: 515Reputation: 515Reputation: 515Reputation: 515
Quote:
Originally Posted by agropec View Post
I did the upgrade, but something that i have no idea had happend!

How to upgrade initrd? i have forgotten it! Please help.
Can you boot the huge kernel? It doesn't require an initrd (in most cases I think).
 
Old 10-23-2020, 12:55 AM   #4
agropec
Member
 
Registered: Nov 2014
Posts: 35

Rep: Reputation: Disabled
I tried first building the initrd:
# mkinitrd -c -m ext4 -k linux-4.4.240.x64

second:
booting from install usb.

then i am trying to do chroot from other linux.
 
Old 10-23-2020, 01:06 AM   #5
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.240
 
1 members found this post helpful.
Old 10-23-2020, 03:13 AM   #6
IlyaK
Member
 
Registered: Jun 2017
Location: The Netherlands
Distribution: Debian
Posts: 118

Rep: Reputation: 72
If you forgot to update your initrd, you can boot from the flash drive, mount you drive, chroot it, cd to the "boot" folder and recreate initrd. See /boot/README.initrd . I also recommend to read ``main mkinitrd`` and ``ramfs-rootfs-initramfs.txt`` in the Kernel documentation folder.
 
Old 10-23-2020, 04:47 AM   #7
agropec
Member
 
Registered: Nov 2014
Posts: 35

Rep: Reputation: Disabled
Quote:
Originally Posted by IlyaK View Post
If you forgot to update your initrd, you can boot from the flash drive, mount you drive, chroot it, cd to the "boot" folder and recreate initrd. See /boot/README.initrd . I also recommend to read ``main mkinitrd`` and ``ramfs-rootfs-initramfs.txt`` in the Kernel documentation folder.
Yes, i forgot to upgrade initrd, when i tried i was not able to read anything usin MC, or nano, links where broken!

Booting from usb installetion disk, is exactly the same situation, nothing works correctly.

I think that because i used slackpkg to upgrade the kernel, the old kernel has been deleted!

I am downloding a usb live to do chroot, or if it exist current usb image, because it has a newer kernel.

Thanks to all for the help.
 
Old 10-23-2020, 08:21 AM   #8
hitest
Guru
 
Registered: Mar 2004
Location: Canada
Distribution: Void, Debian, Slackware
Posts: 7,342

Original Poster
Rep: Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746Reputation: 3746
Code:
Wed Oct 21 21:51:26 UTC 2020
patches/packages/kernel-firmware-20201005_58d41d0-noarch-1.txz:  Upgraded.
patches/packages/linux-4.4.240/*:  Upgraded.
  These updates fix various bugs and security issues, including the recently
  discovered "Bleeding Tooth" vulnerability in the Bluetooth subsystem
  (CVE-2020-12351, CVE-2020-12352, and CVE-2020-24490).
  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.
  For more information, see:
    Fixed in 4.4.228:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810
    Fixed in 4.4.229:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12771
    Fixed in 4.4.230:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15393
    Fixed in 4.4.232:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10323
    Fixed in 4.4.233:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26088
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19054
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25212
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9445
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13094
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8043
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16166
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14331
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19448
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19074
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19073
    Fixed in 4.4.234:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14314
    Fixed in 4.4.236:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25285
    Fixed in 4.4.237:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25284
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14390
    Fixed in 4.4.238:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25643
    Fixed in 4.4.239:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25211
    Fixed in 4.4.240:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12351
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12352
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24490
  (* Security fix *)
+--------------------------+
 
1 members found this post helpful.
Old 10-23-2020, 09:58 AM   #9
_peter
Member
 
Registered: Sep 2014
Location: paris
Distribution: slackware
Posts: 314

Rep: Reputation: Disabled
Quote:
Originally Posted by agropec View Post
Yes, i forgot to upgrade initrd, when i tried i was not able to read anything usin MC, or nano, links where broken!

Booting from usb installetion disk, is exactly the same situation, nothing works correctly.
best of luck repairing your initrd. following by the letter the slackware documentation does work.

https://docs.slackware.com/howtos:sl...ge_for_generic
https://docs.slackware.com/howtos:sl...oot_from_media

maybe backup your data on that drive before anything, it doesn't hurt.
 
Old 10-23-2020, 10:30 AM   #10
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 4,784

Rep: Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434Reputation: 4434
If one is not using an encrypted file system on the bootable drive, there are extremely few situations that actually require an initrd. In most cases, just checking the box for your boot drive's file system as "built-in" (no loadable module needed) eliminates that "gotcha". I actually don't understand why the generic kernel doesn't come with the most common file system support built in. I know of no downside. The kernel size difference is insignificant in the extreme. Some folks just use the huge kernel but kernel building is so easy I don't see why. A stock generic kernel can be rebuilt to require no initrd in way less than an hour. My current i5 box takes 15 minutes.
 
Old 10-23-2020, 12:25 PM   #11
agropec
Member
 
Registered: Nov 2014
Posts: 35

Rep: Reputation: Disabled
Quote:
Originally Posted by willysr View Post
Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.240
I did it, but there are not modules installed. The boot prompt does reference to kernel 2.2.227 not to kernel 2.2.240, which is the upgraded.
 
Old 10-23-2020, 12:29 PM   #12
agropec
Member
 
Registered: Nov 2014
Posts: 35

Rep: Reputation: Disabled
Quote:
Originally Posted by hitest View Post
Code:
Wed Oct 21 21:51:26 UTC 2020
patches/packages/kernel-firmware-20201005_58d41d0-noarch-1.txz:  Upgraded.
patches/packages/linux-4.4.240/*:  Upgraded.
  These updates fix various bugs and security issues, including the recently
  discovered "Bleeding Tooth" vulnerability in the Bluetooth subsystem
  (CVE-2020-12351, CVE-2020-12352, and CVE-2020-24490).
  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.
  For more information, see:
    Fixed in 4.4.228:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-20810
    Fixed in 4.4.229:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12771
    Fixed in 4.4.230:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15393
    Fixed in 4.4.232:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10323
    Fixed in 4.4.233:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26088
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19054
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25212
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9445
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-13094
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8043
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-16166
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14331
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19448
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19074
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19073
    Fixed in 4.4.234:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14314
    Fixed in 4.4.236:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25285
    Fixed in 4.4.237:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25284
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14390
    Fixed in 4.4.238:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25643
    Fixed in 4.4.239:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-25211
    Fixed in 4.4.240:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12351
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12352
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24490
  (* Security fix *)
+--------------------------+
If i understend correctly, vmlinz point to huge kernel, and it does not need initrd!

The other thing is, that at boot prompt says "Welcome to kernel 2.2.227.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
New kernel today in Slackware 14.2 and in Slackware-current hitest Slackware 24 07-06-2017 01:05 AM
New to slackware, how to install new kernel bvbellomo Slackware 11 01-11-2013 01:08 PM
passwd.new, shadow.new, group.new and gshadow.new after upgrade to slackware 12.1 rhermsen Slackware 6 11-08-2008 04:59 PM
A new kernel is out! A new kernel is out! A new kernel is out! Aussie Linux - General 9 11-29-2002 08:31 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:43 AM.

Contact Us - Advertising Info - Rules - Privacy - LQ Merchandise - Donations - Contributing Member - LQ Sitemap -
Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration