LinuxQuestions.org - [SOLVED] latest slackpkg upgrade-all bricks system on slackware64-current

Page 2 of 4

Show 50 post(s) from this thread on one page

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

- - latest slackpkg upgrade-all bricks system on slackware64-current (https://www.linuxquestions.org/questions/slackware-14/latest-slackpkg-upgrade-all-bricks-system-on-slackware64-current-4175620782/)

jkh2cpu

01-03-2018 08:39 AM

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.

Darth Vader

01-03-2018 08:43 AM

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

Petri Kaukasoina

01-03-2018 08:44 AM

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.

jkh2cpu

01-03-2018 09:04 AM

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.

Darth Vader

01-03-2018 09:30 AM

Quote:

Originally Posted by jkh2cpu (Post 5801061)

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.

jkh2cpu

01-03-2018 09:54 AM

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.

Darth Vader

01-03-2018 09:59 AM

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.

stormtracknole

01-03-2018 10:08 AM

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?

Darth Vader

01-03-2018 10:14 AM

Quote:

Originally Posted by stormtracknole (Post 5801097)

I do not think so. Probably our BDFL messed something in the scripts from installer. ;)

montagdude

01-03-2018 10:15 AM

Quote:

Originally Posted by jkh2cpu (Post 5801085)

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

sombragris

01-03-2018 10:22 AM

Also a victim.

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

jkh2cpu

01-03-2018 10:32 AM

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.

Darth Vader

01-03-2018 10:42 AM

Quote:

Originally Posted by jkh2cpu (Post 5801109)

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.

Darth Vader

01-03-2018 10:47 AM

Quote:

Originally Posted by sombragris (Post 5801105)

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.

Petri Kaukasoina

01-03-2018 10:48 AM

Or just

Code:

mkinitrd -c -k 4.14.11 -m ext4

like in README.initrd.

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

Page 2 of 4

Show 50 post(s) from this thread on one page