LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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 01-03-2018, 08:39 AM   #16
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 36

Original Poster
Rep: Reputation: Disabled

I just need some simple instructions to make the initrd from the boot stick. I've done it before on occasion as an exercise.

I'm using -current to keep up-to-date so I can keep gimp-2.9.x current. If I remain with stock slackware, I don't have the libraries that I need to run gimp from git, and gimp-2.8 is so far behind 2.9.x that is' not worth talking about.

So, simple help, please?

John.
 
Old 01-03-2018, 08:43 AM   #17
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Maybe someone, with a better handling of English than me (@bassmadrigal hear me?), could put those things in a simpler way.

Last edited by Darth Vader; 01-03-2018 at 08:56 AM.
 
Old 01-03-2018, 08:44 AM   #18
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 335

Rep: Reputation: 180Reputation: 180
You could always go back to the previous kernel. It's here http://butler.cc.tut.fi/~kaukasoi/slackware64-current/. In chroot, install it and run lilo.
 
Old 01-03-2018, 09:04 AM   #19
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 36

Original Poster
Rep: Reputation: Disabled
OK, maybe you guys have given me enough info to work this out, so thanks!

I'll report back later (things to do right now) with happiness or more tears.

I see what do do with chroot.

John.
 
Old 01-03-2018, 09:30 AM   #20
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Quote:
Originally Posted by jkh2cpu View Post
OK, maybe you guys have given me enough info to work this out, so thanks!

I'll report back later (things to do right now) with happiness or more tears.

I see what do do with chroot.

John.
At the end of day, I believe that the -current is not for you.

IF you have even trouble to debug a failed boot, bad things could happen for you while using -current.

For example, for a considerable time, the -current kernels randomly crashed by fault of some mysterious misfeature.

Long story short, the slackware-current is not the rolling release version, but the very development tree of Slackware, and it may or may not work at random times.

Hence, its usage is supposed to be targeted to advanced users who willingly assume the role of beta-testers and knows really well how Slackware works, then able alone to bring back their installations, if something bad happens.

I strongly suggest you to go back to Slackware 14.2 and to find somehow how you can build your desired GIMP in a custom way.

Last edited by Darth Vader; 01-03-2018 at 09:54 AM.
 
Old 01-03-2018, 09:54 AM   #21
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 36

Original Poster
Rep: Reputation: Disabled
That screwed up.

Didier had an interesting paragraph:

Boot an installation media (or live as said Darth), login as root, don't run setup, mount your (installed) root partition as /mnt, bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys, chroot /mnt and make the intrd, install it and run lilo.

What do you mean: bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys An example would be helpful.

I'll wait for the fix from slackware, or maybe someone can actually help me out.

Thanks.

John.
 
Old 01-03-2018, 09:59 AM   #22
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
It is simple.

While you are logged as root into your live system, mount your Linux partitions; let's suppose that your Linux lives in /dev/sda2

Code:
mkdir /mnt/sda2

mount /dev/sda2 /mnt/sda2

mount --bind /dev /mnt/sda2/dev
mount --bind /proc /mnt/sda2/proc
mount --bind /sys /mnt/sda2/sys

chroot /mnt/sda2 su -l

# there you are root into your installed Linux, time to fix your boot.
IF your installed Linux is composed of multiple filesystems, you should mount all of them accordingly.

Last edited by Darth Vader; 01-03-2018 at 10:01 AM.
 
2 members found this post helpful.
Old 01-03-2018, 10:08 AM   #23
stormtracknole
Senior Member
 
Registered: Aug 2005
Distribution: Slackware, RHEL
Posts: 1,041

Rep: Reputation: 148Reputation: 148
I just tried doing an clean install from the latest -current64 iso and noticed a couple of issues. First, it never gave me an option to select the filesystem for the root (/) partition. Second, it can't detect the cdrom/dvd iso. Probably related the same kernel issue?
 
Old 01-03-2018, 10:14 AM   #24
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Quote:
Originally Posted by stormtracknole View Post
I just tried doing an clean install from the latest -current64 iso and noticed a couple of issues. First, it never gave me an option to select the filesystem for the root (/) partition. Second, it can't detect the cdrom/dvd iso. Probably related the same kernel issue?
I do not think so. Probably our BDFL messed something in the scripts from installer.
 
Old 01-03-2018, 10:15 AM   #25
montagdude
Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 989

Rep: Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709Reputation: 709
Quote:
Originally Posted by jkh2cpu View Post
What do you mean: bind mount /dev /proc and /sys as /mnt/dev, /mnt/proc and /mnt/sys An example would be helpful.
This is a good page to keep handy:

https://docs.slackware.com/howtos:sl...oot_from_media
 
1 members found this post helpful.
Old 01-03-2018, 10:22 AM   #26
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 355

Rep: Reputation: 106Reputation: 106
Also a victim.

Great info here, but keep in mind that in UEFI eras most people do not run lilo. I use GRUB.

Last edited by sombragris; 01-03-2018 at 11:46 AM.
 
Old 01-03-2018, 10:32 AM   #27
jkh2cpu
Member
 
Registered: Feb 2014
Location: Michigan, USA
Distribution: slackware
Posts: 36

Original Poster
Rep: Reputation: Disabled
Thanks for the steps.

And that didn't work. I got to the point of making an initrd, but the thing seems to be in an endless loop. My initrd.gz is 50 bytes ;-)

John.
 
Old 01-03-2018, 10:42 AM   #28
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Quote:
Originally Posted by jkh2cpu View Post
Thanks for the steps.

And that didn't work. I got to the point of making an initrd, but the thing seems to be in an endless loop. My initrd.gz is 50 bytes ;-)

John.
You executed the /usr/share/mkinitrd/mkinitrd_command_generator.sh in the chroot?

Mine one shows something like:
Code:
mkinitrd -c -k 4.14.11 -f ext4 -r /dev/sda2 -m xhci-pci:ohci-pci:ehci-pci:xhci-hcd:uhci-hcd:ehci-hcd:hid:usbhid:i2c-hid:hid_generic:hid-cherry:hid-logitech:hid-logitech-dj:hid-logitech-hidpp:hid-lenovo:hid-microsoft:hid_multitouch:jbd2:mbcache:ext4 -u -o /boot/initrd.gz
IF you use also ext4fs you can use something like this, adjusting the root partition.

Last edited by Darth Vader; 01-03-2018 at 10:44 AM.
 
Old 01-03-2018, 10:47 AM   #29
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,436

Rep: Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979Reputation: 979
Quote:
Originally Posted by sombragris View Post
Also a victim.

Great info here, but keep in mind that un UEFI eras most people do not run lilo. I use GRUB.
You are only a victim of your own laziness.

You are supposed to switch to the generic kernel and initrd after the first boot of your operating system. The huge one is/was only a workaround for the first boot, nothing more.

Quote:
Originally Posted by README.initrd
1. What is an initrd?

Initrd stands for "initial ramdisk". An initial ramdisk is a very small
Linux filesystem that is loaded into RAM and mounted as the kernel boots,
and before the main root filesystem is mounted.

2. Why do I need an initrd?

The usual reason to use an initrd is because you need to load kernel
modules before mounting the root partition. Usually these modules are
required to support the filesystem used by the root partition (ext3, ext4,
btrfs, xfs), or perhaps the controller that the hard drive is attached
to (SCSI, RAID, etc). Essentially, there are so many different options
available in modern Linux kernels that it isn't practical to try to ship
many different kernels to try to cover everyone's needs. It's a lot more
flexible to ship a generic kernel and a set of kernel modules for it.
 
Old 01-03-2018, 10:48 AM   #30
Petri Kaukasoina
Member
 
Registered: Mar 2007
Posts: 335

Rep: Reputation: 180Reputation: 180
Or just
Code:
mkinitrd -c -k 4.14.11 -m ext4
like in README.initrd.
 
  


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] slackpkg upgrade-all is not working in slackware64-current foobarz Slackware 1 08-13-2012 01:55 PM
[SOLVED] Can't get slackpkg to upgrade to slackware64 NightSky Slackware - Installation 4 06-09-2010 04:38 PM
Slackware64 -current (20-04-2010) problem with slackpkg mlpa Slackware 5 04-22-2010 01:55 AM
[SOLVED] slackpkg insists on NOT upgrading me to slackware64-current. What am I missing? GrapefruiTgirl Slackware 5 03-04-2010 01:01 PM
Slackware64-Current / slackpkg slackass Slackware 31 06-06-2009 10:51 PM

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

All times are GMT -5. The time now is 06:24 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration