LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-18-2021, 01:40 PM   #166
FTIO
Member
 
Registered: Mar 2015
Location: Las Vegas, NV
Distribution: Slackware 14.2_x64, sometimes Current
Posts: 428

Rep: Reputation: 225Reputation: 225Reputation: 225

Well, I just didn't know about it or what it did, and figured Pat's 'readme' for it would cover what needed to be done...which, by the way, I seem to have screwed up anyway as my system with the kernels from /testing (5.12.x) that I used in an 'upgradepkg' in konsole, then changed to /boot and did this:

Code:
mkinitrd -c -k 5.12.4* -m reiserfs
(all as root, of course, and because I use reiserfs on all my drives/systems), then rebooted - didn't. It got to vmlinuz and then initrd then just hung there forever, so I figure I screwed something up, lol.

So how am I supposed to do this? Do I do the 'upgradepkg' with those kernels, then cd to /boot and then use that command you showed or is there some step somewhere I'm missing? Can this all be done in konsole, or should I not be in X at all? Told ya I get confused easily, heh.
 
Old 05-18-2021, 02:44 PM   #167
MDKDIO
Member
 
Registered: Mar 2004
Location: Sweden
Distribution: Slackware 14.2 & Current
Posts: 236

Rep: Reputation: 63
All commands run as root (su)

The steps I take when upgrading a kernel (or installing a dif kernel from what is the main kernel in Slackware at the moment):

First, I do run 5.12.x (5.11.x before this, as I had too many problems with 5.10.x)

I download the (4) packages needed from a mirror.
Run installpkg kernel-* (from within the directory containing the kernel files).
Once completed, I run
/usr/shar/mkinitrd/mkinitrd_command_generator.sh

Yes, it is just a suggestion for what command to run, but I've done this for years and it has never failed so far.

Code:
mkinitrd -c -k 5.12.4 -f ext4 -r /dev/nvme0n1p2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz
This is what I get when using the mkinitrd_command_generator.sh script

Example:
If I have just installed kernel 5.12.5, I'd have to change that command line, by two things:
1. mkinitrd -c -k 5.12.4 changed to 5.12.5
2. /boot/initrd.gz to /boot/initrd-5.12.5.gz

So the suggested command (see code section above), is changed to this:
Code:
mkinitrd -c -k 5.12.5 -f ext4 -r /dev/nvme0n1p2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-asus:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd-5.12.5.gz
Next, I'll have to copy two files from /boot to /boot/efi/EFI/Slackware/
cp /boot/vmlinuz-generic-5.12.4 /boot/efi/EFI/Slackware/
cp /boot/initrd-5.12.5.gz /boot/efi/EFI/Slackware/


Finally:
edit the file /boot/efi/EFI/Slackware/elilo.conf (nano /boot/efi/EFI/Slackware/elilo.conf as an example)

Either add a new section, or edit the previous (in my above example, 5.12.4) section
elilo.conf looks something like this:
Code:
chooser=simple
delay=5
timeout=5
default=generic1
#
image=vmlinuz-generic-5.12.4
        label=generic1
        initrd=initrd-5.12.4.gz
        read-only
        append="root=/dev/nvme0n1p2 vga=normal ro"
So what I have to edit here, is
image=vmlinuz-generic-5.12.4 to image=vmlinuz-generic-5.12.5
and
initrd=initrd-5.12.4.gz to initrd=initrd-5.12.5.gz

IF I am not updating a kernel as above, but adding a new kernel instead. I would have to add a new section to elilo.conf
Copy the default section, make sure you change the label=It's_Name AND make sure the default= points to that newly added sections label=

And yes, all of this can be done in konsole while in X (KDE in my case), it makes it easier as you can just copy/paste the mkinitrd command
(ctrl+shift+c to copy, ctrl+shift+v to paste into konsole, of course by first selecting the command line by using the mouse (or highlight it for another word)

Hope that helps a bit on your way

Last edited by MDKDIO; 05-18-2021 at 02:46 PM.
 
2 members found this post helpful.
Old 05-19-2021, 09:45 AM   #168
FTIO
Member
 
Registered: Mar 2015
Location: Las Vegas, NV
Distribution: Slackware 14.2_x64, sometimes Current
Posts: 428

Rep: Reputation: 225Reputation: 225Reputation: 225
I'll give it another shot, can't hurt, right? Thank you, also, for taking the time to try and help this idiot out with this, I can imagine it's probably frustrating, heh.
 
Old 05-19-2021, 01:44 PM   #169
MDKDIO
Member
 
Registered: Mar 2004
Location: Sweden
Distribution: Slackware 14.2 & Current
Posts: 236

Rep: Reputation: 63
Quote:
Originally Posted by FTIO View Post
I'll give it another shot, can't hurt, right? Thank you, also, for taking the time to try and help this idiot out with this, I can imagine it's probably frustrating, heh.
You'll get it sorted, you'll see
And no, it's not frustrating
 
Old 06-09-2021, 09:39 AM   #170
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,592

Original Poster
Blog Entries: 1

Rep: Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982Reputation: 3982
A new test build, 6.1.23-145004 and extension pack version 6.1.23-145002, have been posted at, https://www.virtualbox.org/wiki/Testbuilds
 
2 members found this post helpful.
Old Yesterday, 11:31 AM   #171
FTIO
Member
 
Registered: Mar 2015
Location: Las Vegas, NV
Distribution: Slackware 14.2_x64, sometimes Current
Posts: 428

Rep: Reputation: 225Reputation: 225Reputation: 225
That test build is working on the latest Slackware current! So it seems the problems I was having with Virtualbox not working on my system was kernel 5.10.x. WOOHOO!
 
Old Yesterday, 02:44 PM   #172
MDKDIO
Member
 
Registered: Mar 2004
Location: Sweden
Distribution: Slackware 14.2 & Current
Posts: 236

Rep: Reputation: 63
Quote:
Originally Posted by FTIO View Post
That test build is working on the latest Slackware current! So it seems the problems I was having with Virtualbox not working on my system was kernel 5.10.x. WOOHOO!
Great news!!
Good reading it finally got sorted, just hope it'll keep working for you in the future as well
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
[SOLVED] virtualbox is installed along with virtualbox-dkms and virtualbox-ext-pack and linux-headers-generic, but error for no /dev/vboxdrv Astral Axiom Linux - Software 2 03-04-2019 08:09 PM
Issues activating virtualbox within my linux fedora 25 virtualbox on my windows device. QuantumChaos Linux - Virtualization and Cloud 5 02-21-2017 08:31 AM
Move Slackware guest from a Slackware hosted Virtualbox to Windows hosted Virtualbox? damgar Slackware 1 08-07-2012 11:28 PM
virtualbox or virtualbox ose manuleka Linux - Software 2 06-11-2009 02:56 PM

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

All times are GMT -5. The time now is 04:56 PM.

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