Slackware and the grub boot loader.

colorpurple21859 · 07-02-2020, 08:11 PM

did you try Petri Kaukasoina suggested mkinitrd line:

Code:

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

and/or add this to the mkinitrd command that was generated.

AlleyTrotter · 07-02-2020, 08:13 PM

I read this thread and it is very easy to see why Pat does not make grub the default boot manager.
Just a Thought

colorpurple21859 · 07-02-2020, 08:18 PM

This link has a section on creating an initrd for an emmc drive that may be of help, ignore the sections about efi. https://ansuz.sooke.bc.ca/entry/340

Petri Kaukasoina · 07-03-2020, 12:34 AM

Ok, I guess we tried to use modules for the wrong (non-smp) kernel. Try this:

Code:

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

stf92 · 07-03-2020, 06:49 AM

In order to paste the output of mkinitrd_command_generator.sh I run the commands of post #27 in a GUI terminal after doing 'su -' and then with the mouse I copy and paste. But I understand 'su -' is not exactly the same as using one of the consoles (dev/ttyN) as root. Is it OK if I use a GUI terminal?

colorpurple21859 · 07-03-2020, 07:37 AM

It will work good enough for this.

colorpurple21859 · 07-03-2020, 07:50 AM

chroot into slackware with a gui terminal post your

Code:

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

output

colorpurple21859 · 07-03-2020, 08:24 AM

try this one and see if it works, this is assuming slackware filesytem is ext4

Code:

mkinitrd -k 4.4.14 -f ext4 -r /dev/mmcblk0p2 -w 15 -m mmc_core:mmc_block:sdhci:sdhci_acpi:sdhci_pci:usb_storage:xhci_hcd:uas:xhci_pci:ext4 -u -o /boot/initrd.gz

based on your lsmod output

AlleyTrotter · 07-03-2020, 08:34 AM

Code:

# Figure out the device and partition number of the ESP:
DEVLEN=8
PARTLEN=9
if mount | grep vfat | grep -wq /boot/efi ; then
  mount | grep vfat | grep -w /boot/efi | grep -q -e nvme -e mmcblk && DEVLEN=12 && PARTLEN=14
  EFI_DEVICE=$(mount | grep vfat | grep -w /boot/efi | cut -b 1-${DEVLEN})
  EFI_PARTITION=$(mount | grep vfat | grep -w /boot/efi | cut -f 1 -d ' ' | cut -b ${PARTLEN}- | tr -d [a-z])
else
  mount | grep vfat | grep -w $T_PX/boot/efi | grep -q -e nvme -e mmcblk && DEVLEN=12 && PARTLEN=14
  EFI_DEVICE=$(mount | grep vfat | grep -w $T_PX/boot/efi | cut -b 1-${DEVLEN})
  EFI_PARTITION=$(mount | grep vfat | grep -w $T_PX/boot/efi | cut -f 1 -d ' ' | cut -b ${PARTLEN}- | tr -d [a-z])
fi

I don't have the knowledge to fix the problem, but the short code segement from current's eliloconfig seems to indicate that it supports 'mmcblk' devices.
Sorry I can't offer any further assistance
HTH
john

Petri Kaukasoina · 07-03-2020, 09:10 AM

Quote:

Originally Posted by stf92

I looked into the slackware /boot directory and the names of the images include '4.4.14-smp'.

Quote:

Originally Posted by Petri Kaukasoina

Ok, I guess we tried to use modules for the wrong (non-smp) kernel. Try this:

Code:

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

Please notice this. It should be "-k 4.4.14-smp", not "-k 4.4.14".

stf92 · 07-03-2020, 09:31 AM

Quote:

Originally Posted by Petri Kaukasoina

Please notice this. It should be "-k 4.4.14-smp", not "-k 4.4.14".

Yes, I'm using -k 4.4.14-smp, thanks Petri.

stf92 · 07-03-2020, 09:45 AM

Code:

bash-4.3# sh /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.14-smp
cat: /proc/mdstat: No such file or directory
#
# mkinitrd_command_generator.sh revision 1.45
#
# This script will now make a recommendation about the command to use
# in case you require an initrd image to boot a kernel that does not
# have support for your storage or root filesystem built in
# (such as the Slackware 'generic' kernels').
# A suitable 'mkinitrd' command will be:

mkinitrd -c -k 4.4.14-smp -f ext2 -r /dev/mmcblk0p2 -m mmc_core:sdhci:sdhci-pci:usb-storage:xhci-hcd:xhci-pci:ohci-pci:ehci-pci: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:mbcache:ext2 -u -o /boot/initrd.gz
bash-4.3#

Please notice the 'cat: /proc/mdstat: No such file or directory' line.

colorpurple21859 · 07-03-2020, 10:26 AM

I think the -smp is wrong that just for kernel naming, look in slackware /lib/modules for kernel versions

Petri Kaukasoina · 07-03-2020, 11:10 AM

kernel-modules-smp-4.4.14_smp-i686-1.txz extracts modules under /lib/modules/4.4.14-smp

stf92 · 07-03-2020, 11:28 AM

Quote:

Originally Posted by colorpurple21859

try this one and see if it works, this is assuming slackware filesytem is ext4

Code:

mkinitrd -k 4.4.14 -f ext4 -r /dev/mmcblk0p2 -w 15 -m mmc_core:mmc_block:sdhci:sdhci_acpi:sdhci_pci:usb_storage:xhci_hcd:uas:xhci_pci:ext4 -u -o /boot/initrd.gz

based on your lsmod output

It didn't work.

In /boot/grub/grub.cfg the slackware menu entry has vmlinuz-generic-4.4.14. So I assume in the mkinitrd we have to use is '-k 4.4.14', not '-k 4.4.14-smp'. Am I right?

Quote:

Originally Posted by colorpurple21859

This link has a section on creating an initrd for an emmc drive that may be of help, ignore the sections about efi. https://ansuz.sooke.bc.ca/entry/340

This guy used elilo succesfully (slackware with eMMC) (He does not state which slackware version). But I am using legacy mode (BIOS), no EFI. So could it be that lilo could do the job?