Attempting to install on an HP Stream netbook (problems dealing with EFI)

bassmadrigal · 12-28-2017, 07:58 PM

If you used the generic kernel, you'd need to load an initrd. What is the output of the following commands (of your regular filesystem... if you need to mount the drive first in the installer, change the location of the files as needed)?

Code:

ls -la /boot/
file /boot/efi/EFI/Slackware/vmlinuz

ahc_fan · 12-29-2017, 05:46 AM

Quote:

Originally Posted by bassmadrigal

If you used the generic kernel, you'd need to load an initrd. What is the output of the following commands (of your regular filesystem... if you need to mount the drive first in the installer, change the location of the files as needed)?

Code:

ls -la /boot/
file /boot/efi/EFI/Slackware/vmlinuz

Code:

# ls -la /boot/
total 20757
drwxr-xr-x  4 root root    4096 Dec 27 13:27 .
drwxr-xr-x 22 root root    4096 Dec 27 13:27 ..
lrwxrwxrwx  1 root root      38 Dec 27 13:15 README.initrd -> /usr/doc/mkinitrd-1.4.11/README.initrd
lrwxrwxrwx  1 root root      22 Dec 27 13:27 System.map -> System.map-huge-4.9.67
-rw-r--r--  1 root root 2934472 Dec  5 14:19 System.map-generic-4.9.67
-rw-r--r--  1 root root 4265788 Dec  5 14:29 System.map-huge-4.9.67
-rw-r--r--  1 root root     426 Jul  9 10:40 coffee.dat
lrwxrwxrwx  1 root root      18 Dec 27 13:27 config -> config-huge-4.9.67
-rw-r--r--  1 root root  169602 Dec  5 14:19 config-generic-4.9.67
-rw-r--r--  1 root root  169602 Dec  5 14:29 config-huge-4.9.67
drwxr-xr-x  3 root root    1024 Dec 31  1969 efi
-rwxr-xr-x  1 root root  215987 Nov 20 11:01 elilo-ia32.efi
-rwxr-xr-x  1 root root  237749 Nov 20 10:36 elilo-x86_64.efi
drwxr-xr-x  2 root root    4096 Apr 26  2017 grub
-rw-r--r--  1 root root   22578 Jul  9 10:40 inside.bmp
-rw-r--r--  1 root root     432 Jul  9 10:40 inside.dat
-rw-r--r--  1 root root    6878 Jul  9 10:40 onlyblue.bmp
-rw-r--r--  1 root root     424 Jul  9 10:40 onlyblue.dat
-rw-r--r--  1 root root   15634 Mar 26  2011 slack.bmp
-rw-r--r--  1 root root   33192 Jul  9 10:40 tuxlogo.bmp
-rw-r--r--  1 root root     423 Jul  9 10:40 tuxlogo.dat
lrwxrwxrwx  1 root root      19 Dec 27 13:27 vmlinuz -> vmlinuz-huge-4.9.67
lrwxrwxrwx  1 root root      22 Dec 27 13:15 vmlinuz-generic -> vmlinuz-generic-4.9.67
-rw-r--r--  1 root root 4892960 Dec  5 14:19 vmlinuz-generic-4.9.67
lrwxrwxrwx  1 root root      19 Dec 27 13:15 vmlinuz-huge -> vmlinuz-huge-4.9.67
-rw-r--r--  1 root root 8235296 Dec  5 14:29 vmlinuz-huge-4.9.67

vmlinuz.txt

Code:

/boot/efi/EFI/Slackware/vmlinuz: Linux kernel x86 boot executable bzImage, version 4.9.67 (root@hive64.slackware.lan) #2 SMP Tue Dec 5 16:29:07 CST 2017, RO-rootFS, swap_dev 0x7, Normal VGA

Didier Spaier · 12-29-2017, 06:25 AM

Not sure that matters, but something is wrong in your /etc/fstab. This line:

Code:

/dev/mmcblk01    /boot/efi        vfat        defaults         1   0

should be:

Code:

/dev/mmcblk01p1    /boot/efi        vfat        defaults         1   0

ahc_fan · 12-29-2017, 06:30 AM

I noticed that and changed it but it made no difference.

Didier Spaier · 12-29-2017, 06:46 AM

I would then try to reinstall, agreeing to format the root partition when asked.

Instead of typing "setup" type "setup 2>/tmp/errors" so after installation" you can check for errors that could have occurred. Do that before rebooting as /tmp is in RAM during installation, so after rebooting its content will be lost.

ahc_fan · 12-29-2017, 07:06 AM

The errors are:

Code:

rmdir: '/tmp/tmp.NgcC56': Directory not empty
mv: can't rename 'etc/fonts/conf.d/99pdftoopvp.conf.net': No such file or directory

Just guessing but they don't seem relevant to the main issue.

I guess if all else fails I'll just stick with Antergos.

Didier Spaier · 12-29-2017, 07:12 AM

Maybe try the Slint64-14.2.1 ISO, but I doubt that makes a difference. I you have the patience, see here.

ahc_fan · 12-29-2017, 07:17 AM

I might just do that. Anyway I appreciate all the help from everyone in this topic, as usual the Slackware community doesn't let me down.

Not sure if I should mark this as solved or not. I guess I'll just leave it in case anyone else has an idea.

laprjns · 12-29-2017, 12:42 PM

Regarding the missing "p" in the fstab entry for the esp partition;

Quote:

Not sure that matters, but something is wrong in your /etc/fstab. This line:

Code:

/dev/mmcblk01    /boot/efi        vfat        defaults         1   0

should be:

Code:

/dev/mmcblk01p1    /boot/efi        vfat        defaults         1   0

Today 06:46 AM

Looking at the SeTefi script in the installer, this below section of code appears to have logic to deal with the "p" in nvme device names, but not for mmcblk device names.

Code:

# Scan for EFI partitions:
# We accept at most 10 NVMe controllers, each controlling at most 4 SSDs
for drive in sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp \
  mmcblk0 mmcblk1 mmcblk2 mmcblk3 mmcblk4 mmcblk5 mmcblk6 mmcblk7 mmcblk8 mmcblk9 \
  nvme0n1 nvme1n1 nvme2n1 nvme3n1 nvme4n1 nvme5n1 nvme6n1 nvme7n1 nvme8n1 nvme9n1 \
  nvme0n2 nvme1n2 nvme2n2 nvme3n2 nvme4n2 nvme5n2 nvme6n2 nvme7n2 nvme8n2 nvme9n2 \
  nvme0n3 nvme1n3 nvme2n3 nvme3n3 nvme4n3 nvme5n3 nvme6n3 nvme7n3 nvme8n3 nvme9n3 \
  nvme0n4 nvme1n4 nvme2n4 nvme3n4 nvme4n4 nvme5n4 nvme6n4 nvme7n4 nvme8n4 nvme9n4  ; do
  gdisk -l /dev/$drive 2> /dev/null | grep -w EF00 | while read efisp ; do
    p=""
    echo $drive| grep -q nvme && p="p"
    echo /dev/$drive$p$(expr $(echo "$efisp" | cut -b 1-4)) >> $TMP/SeTefipartitions
  done
done

Didier Spaier · 12-29-2017, 01:16 PM

Hello Rich,

Which installer?

In Slint64-14.2.1:

Code:

# Scan for EFI partitions:
# We accept at most 10 NVMe controllers, each controlling at most 4 SSDs
# and 0 MMC cards.
for drive in sda sdb sdc sdd sde sdf sdg sdh sdi sdj sdk sdl sdm sdn sdo sdp \
  mmcblk0 mmcblk1 mmcblk2 mmcblk3 mmcblk4 mmcblk5 mmcblk6 mmcblk7 mmcblk8 mmcblk9 \
  nvme0n1 nvme1n1 nvme2n1 nvme3n1 nvme4n1 nvme5n1 nvme6n1 nvme7n1 nvme8n1 nvme9n1 \
  nvme0n2 nvme1n2 nvme2n2 nvme3n2 nvme4n2 nvme5n2 nvme6n2 nvme7n2 nvme8n2 nvme9n2 \
  nvme0n3 nvme1n3 nvme2n3 nvme3n3 nvme4n3 nvme5n3 nvme6n3 nvme7n3 nvme8n3 nvme9n3 \
  nvme0n4 nvme1n4 nvme2n4 nvme3n4 nvme4n4 nvme5n4 nvme6n4 nvme7n4 nvme8n4 nvme9n4  ; do
  gdisk -l /dev/$drive 2> /dev/null | grep -w EF00 | while read efisp ; do
    p=""
    echo $drive| grep -q -e nvme -e mmcblk && p="p"
    echo /dev/$drive$p$(expr $(echo "$efisp" | cut -b 1-4)) >> $TMP/SeTefipartitions
  done
done

I should have written 10, no 0 MMMC cards but still.

However thanks that maybe made me find a mistake in one of my previous posts. In /etc/fstab this line

Code:

/dev/mmcblk01p1    /boot/efi        vfat        defaults         1   0

was badly corrected. It should be:

Code:

/dev/mmcblk0p1    /boot/efi        vfat        defaults         1   0

But maybe the OP did the correction properly.

laprjns · 12-29-2017, 01:38 PM

Hi Didier,

Quote:

Originally Posted by Didier Spaier

Which installer?

I got the SeTefi script for the slackware64-current DVD iso. I used Alien Bob's mirror-slackware-current script to make the iso yesterday or the day before. I believe that OP was using a Slackware current iso, so he should try installing Slint64 14.2.1.