Slackware and the grub boot loader.

colorpurple21859 · 07-02-2020, 01:01 PM

Code:

sh /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.14

Forgot to add the -k for your slackware kernel version.

Quote:

Could it be because I installed 14.2 32-bit and this machine is 64-bit?

No that is debians kernel version that is currently running and the script defaults to the running kernel if the -k option isn't supplied

colorpurple21859 · 07-02-2020, 01:13 PM

If it still won't boot check-out the last 2 post in this thread https://www.linuxquestions.org/quest...ge-4175587811/

stf92 · 07-02-2020, 01:22 PM

Alright. Assume I already have my initrd.gz. Why can't I just make grub.cfg writable and manually edit it to modify the line? I've already done it adding to the line the kernel parameters edd=off and noapic.

colorpurple21859 · 07-02-2020, 01:31 PM

Quote:

Alright. Assume I already have my initrd.gz. Why can't I just make grub.cfg writable and manually edit it to modify the line?

yes you can do that, but the first debian update that runs update-grub will undo your edit. Slackware doesn't update the /boot/grub/grub.cfg when updating the system, but debian does. It should pick up the initrd.gz when update-grub is rerun

Quote:

I've already done it adding to the line the kernel parameters edd=off and noapic.

Those also will go away when debian updates the kernel. Edit /etc/default/grub and add it to the

Code:

GRUB_CMDLINE_LINUX=" edd=off noapic"

run update-grub

Petri Kaukasoina · 07-02-2020, 01:33 PM

I would not use mkinitrd_command_generator.sh running on the debian kernel but just try

Code:

mkinitrd -k 4.4.14 -m mmc_core:mmc_block:sdhci:sdhci_acpi:sdhci_pci

in that chroot.

stf92 · 07-02-2020, 02:10 PM

Code:

Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block (0,0)

I assume grub took notice of the 10_custom file, where the initrd line is. I'll see your link in post #32.

stf92 · 07-02-2020, 03:59 PM

I tried with the initrd.gz made as in post #27 and I tried with the one made as in post #35 both cases resulting in Kernel panic (same message).

@colorpurple21859: I read the posts you suggested in post #32. But they assume you recompile the kernel, a work I am not willing to do.

In the eMMC there are two partitions which are not shown by cfdisk. One of them is EFI, I think. When I ran the installer I was surprised it had found an NTFS partition with size 512MB. That is one of the "hidden" partitions. One thing: are we sure the kernel panic message is caused by the eMMC thing? What remains true is that both arch linux and debian had no problem with the eMMC.

EDIT: I have a second machine with 14.2 running on it, in case that is helpful.

Petri Kaukasoina · 07-02-2020, 04:42 PM

When you run lsmod in the installer, maybe it listed some other modules than you wrote in #28 ? If so, try add them in the mkinitrd command in #35.

Jeebizz · 07-02-2020, 04:45 PM

This probably will never happen, but maybe Slackware could provide a choice? LILO / GRUB , ELILO/GRUB (UEFI) - without having to manually go in and install GRUB instead of LILO/ELILO. Just a thought.

stf92 · 07-02-2020, 05:00 PM

Quote:

Originally Posted by Petri Kaukasoina

When you run lsmod in the installer, maybe it listed some other modules than you wrote in #28 ? If so, try add them in the mkinitrd command in #35.

I ran the installer and when it gave me the prompt I logged in as root and ran lsmod. Is it correct?

stf92 · 07-02-2020, 05:42 PM

Quote:

Originally Posted by Jeebizz

This probably will never happen, but maybe Slackware could provide a choice? LILO / GRUB , ELILO/GRUB (UEFI) - without having to manually go in and install GRUB instead of LILO/ELILO. Just a thought.

Volkerdi himself told me lilo can't manage eMMC. I think if elilo can he would have told me.

I'll run the installer and after having run lsmod I'll use gpm (general purpose mouse) to paste the output into a file. Only thing is I don't know where gmp will be in the file system (I installed it).

colorpurple21859 · 07-02-2020, 05:44 PM

Yes, run uname -r if the kernel version is the same as the one of the installed system rerun the commands of post 30 minus the update-grub

stf92 · 07-02-2020, 06:49 PM

This is the output of 'uname -r' run while running the installer:

Code:

4.4.14-smp

Does it match the kernel version?

This is the output of 'lsmod' run while running the installer:

Code:

Module                  Size  Used by
uas                    12314  0
usb_storage            44630  1 uas
mmc_block              26186  2
drm                   277806  0
xhci_pci                4217  0
xhci_hcd              108007  1 xhci_pci
i2c_i801               14717  0
i2c_designware_pci      3257  0
agpgart                26940  1 drm
sdhci_pci              15331  0
i2c_algo_bit            5190  0
8250_fintek             2820  0
wmi                     7983  0
video                  24660  0
i2c_hid                11423  0
hid                    87731  1 i2c_hid
i2c_designware_platform     3675  0
i2c_designware_core     6748  2 i2c_designware_pci,i2c_designware_platform
i2c_core               41745  7 drm,i2c_designware_pci,i2c_i801,i2c_hid,i2c_designware_core,i2c_designware_platform,i2c_algo_bit
dwc3                   33222  0
sdhci_acpi              5145  0
8250_dw                 5874  0
sdhci                  26312  2 sdhci_acpi,sdhci_pci
mmc_core               97537  4 mmc_block,sdhci,sdhci_acpi,sdhci_pci
fjes                   19156  0
pinctrl_cherryview     17811  1
button                  4494  0
processor              23453  0
loop                   17817  0

stf92 · 07-02-2020, 07:14 PM

Quote:

Originally Posted by stf92

This is the output of 'uname -r' run while running the installer:

Code:

4.4.14-smp

Does it match the kernel version?

Of course it does: I looked into the slackware /boot directory and the names of the images include '4.4.14-smp'. I did exactly what you said but still the same kernel panic message.

colorpurple21859 · 07-02-2020, 07:45 PM

add rootdelay=15 to the linux line of the grub menu