ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

RED2 · 2016-01-17 23:12:09

ArchLinux i686 Install Issue on Nextbook Tablet via USB boot up ArchISO (with eth0 enabled)
Model: NXW10QC32G
CPU: Intel Atom Processor Z3735G
Memory: 1GB DDR3L
The USB device is the SDA, SDA1 – TABLET start up boot to this usb device.
The TABLET device is the MMCBLK0
Partition 1: MMCBLK0P1 - INSTALL ARCH BOOT HERE
Partition 2: MMCBLK0P2 - INSTALL ARCH LINUX HERE

ARCHLINUX COMMAND: lsblk -f

NAME         FSTYPE   LABEL       UUID                                 MOUNTPOINT
sda                                                                    
└─sda1       vfat     ARCH_201512 D191-97A4                      /run/archiso/bootmnt
loop0        squashfs                                                  		/run/archiso/sfs/airootfs
mmcblk0rpmb                                                            
mmcblk0boot0                                                           
mmcblk0boot1                                                           
mmcblk0                                                                
├─mmcblk0p1  vfat     EFI SYSTEM  4854-3E0A                            /mnt/efimmc
└─mmcblk0p2  vfat     ARCH_SYSTEM AB36-4BEC                      /mnt/mmc

ARCHLINUX COMMAND: df -l

Filesystem     1K-blocks    Used Available Use% Mounted on
dev               472648       0    472648   0% /dev
run               484136   35644    448492   8% /run
/dev/sda1       30363648 1646016  28717632   6% /run/archiso/bootmnt
cowspace          262144   11864    250280   5% /run/archiso/cowspace
/dev/loop0        290304  290304         0 100% /run/archiso/sfs/airootfs
airootfs          262144   11864    250280   5% /
tmpfs             484136       0    484136   0% /dev/shm
tmpfs             484136       0    484136   0% /sys/fs/cgroup
tmpfs             484136       0    484136   0% /tmp
tmpfs             484136    1048    483088   1% /etc/pacman.d/gnupg
tmpfs              96828       0     96828   0% /run/user/0
/dev/mmcblk0p1    129039    1217    127822   1% /mnt/efimmc
/dev/mmcblk0p2  30388720  185856  30202864   1% /mnt/mmc

ARCHLINUX COMMAND: mount

proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=472648k,nr_inodes=118162,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)

NOTE: HERE IS THE USB ARCHISO BOOT UP
/dev/sda1 on /run/archiso/bootmnt type vfat (ro,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
cowspace on /run/archiso/cowspace type tmpfs (rw,relatime,size=262144k,mode=755)
/dev/loop0 on /run/archiso/sfs/airootfs type squashfs (ro,relatime)
airootfs on / type overlay (rw,relatime,lowerdir=/run/archiso/sfs/airootfs,upperdir=/run/archiso/cowspace/persistent_ARCH_201512/i686/upperdir,workdir=/run/archiso
ENDNOTE:

/cowspace/persistent_ARCH_201512/i686/workdir)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /etc/pacman.d/gnupg type tmpfs (rw,relatime,mode=755)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=96828k,mode=700)

NOTE: HERE IS MMCBLK0P1
/dev/mmcblk0p1 on /mnt/efimmc type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ENDNOTE:

binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

NOTE: HERE IS MMCBLK0P2
/dev/mmcblk0p2 on /mnt/mmc type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
ENDNOTE:

ARCHLINUX COMMAND: pacstrap /mnt/mmc base

==> Creating install root at /mnt/mmc
==> Installing packages to /mnt/mmc

:: Synchronizing package databases...
 core is up to date
 extra is up to date
 community is up to date
:: There are 50 members in group base:
:: Repository core
   1) bash  2) bzip2  3) coreutils  4) cryptsetup  5) device-mapper  6) dhcpcd  7) diffutils  8) e2fsprogs  9) file  10) filesystem  11) findutils  
   12) gawk  13) gcc-libs  14) gettext  15) glibc  16) grep  17) gzip  18) inetutils  19) iproute2  20) iputils  21) jfsutils  22) less  23) licenses  
   24) linux  25) logrotate  26) lvm2  27) man-db  28) man-pages  29) mdadm  30) nano  31) netctl  32) pacman  33) pciutils  34) pcmciautils  35) perl  
   36) procps-ng  37) psmisc  38) reiserfsprogs  39) s-nail  40) sed  41) shadow  42) sysfsutils  43) systemd-sysvcompat  44) tar  45) texinfo  
   46) usbutils  47) util-linux  48) vi  49) which  50) xfsprogs

Enter a selection (default=all): 
resolving dependencies...
looking for conflicting packages...

Packages (124) acl-2.2.52-2  archlinux-keyring-20151220-1  attr-2.4.47-1  ca-certificates-20150402-1  ca-certificates-cacert-20140824-2  ca-certificates-mozilla-3.21-1  ca-certificates-utils-20150402-1  cracklib-2.9.4-1  curl-7.46.0-1  db-5.3.28-3  dbus-1.10.6-1  expat-2.1.0-4  gdbm-1.11-1  glib2-2.46.2-2  gmp-6.1.0-2  gnupg-2.1.10-3  gnutls-3.4.7-2  gpgme-1.6.0-2  groff-1.22.3-5  hwids-20150717-1  iana-etc-20151016-1  iptables-1.4.21-3  kbd-2.0.3-1  keyutils-1.5.9-1  kmod-22-1  krb5-1.13.2-1  libaio-0.3.110-1  libarchive-3.1.2-8  libassuan-2.4.2-1  libcap-2.24-2  libdbus-1.10.6-1  libelf-0.164-2  libffi-3.2.1-1  libgcrypt-1.6.4-1  libgpg-error-1.21-1  libidn-1.32-1  libksba-1.3.3-1  libldap-2.4.43-1  libpipeline-1.4.1-1  libsasl-2.1.26-7  libseccomp-2.2.3-1  libssh2-1.6.0-1  libsystemd-228-3  libtasn1-4.7-1  libtirpc-1.0.1-2  libunistring-0.9.6-1  libusb-1.0.20-1  libutil-linux-2.27.1-1  linux-api-headers-4.1.4-1  linux-firmware-20150904.6ebf5d5-1  lz4-131-1  lzo-2.09-1  mkinitcpio-18-2  mkinitcpio-busybox-1.21.1-2  mpfr-3.1.3.p4-1  ncurses-6.0-4  nettle-3.1.1-1  npth-1.2-1  openresolv-3.7.2-1  openssl-1.0.2.e-1  p11-kit-0.23.2-1  pacman-mirrorlist-20151215-1  pam-1.2.1-3  pambase-20130928-1  pcre-8.38-2  pinentry-0.9.7-1  popt-1.16-7  readline-6.3.008-3  sqlite-3.9.2-1  systemd-228-3  thin-provisioning-tools-0.5.6-2  tzdata-2015g-1  xz-5.2.2-1  zlib-1.2.8-4  bash-4.3.042-4  bzip2-1.0.6-5  coreutils-8.24-1  cryptsetup-1.7.0-1  device-mapper-2.02.137-1  dhcpcd-6.9.4-1  diffutils-3.3-2  e2fsprogs-1.42.13-1  file-5.25-1  filesystem-2015.09-1  findutils-4.4.2-6  gawk-4.1.3-1  gcc-libs-5.3.0-3  gettext-0.19.6-2  glibc-2.22-3  grep-2.22-1  gzip-1.6-1  inetutils-1.9.4-2  iproute2-4.1.1-1  iputils-20140519.fad11dc-1  jfsutils-1.1.15-4  less-481-2  licenses-20140629-1  linux-4.3.3-2  logrotate-3.9.1-1  lvm2-2.02.137-1  man-db-2.7.5-1  man-pages-4.03-1  mdadm-3.3.4-1  nano-2.5.0-1  netctl-1.11-1  pacman-4.2.1-4  pciutils-3.4.0-1  pcmciautils-018-7  perl-5.22.1-1  procps-ng-3.3.11-2  psmisc-22.21-3  reiserfsprogs-3.6.24-1  s-nail-14.8.5-1  sed-4.2.2-3  shadow-4.2.1-3  sysfsutils-2.1.0-9  systemd-sysvcompat-228-3  tar-1.28-1  texinfo-6.0-1  usbutils-008-1  util-linux-2.27.1-1  vi-1:070224-2  which-2.21-1  xfsprogs-4.3.0-1

Total Download Size:     0.14 MiB
Total Installed Size:  531.54 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages ...

error: could not open file /mnt/mmc/var/cache/pacman/pkg/vi-1:070224-2-i686.pkg.tar.xz.part: Invalid argument

warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
==> ERROR: Failed to install packages to new root
Errors occurred, no packages were upgraded.

At this stage, it began to install packages, until it encounter and fails at pkg/vi-1:070224-2-i686.pkg.tar.xz.part

Does anyone know or suggest a resolution to this?

Thank you.
RED2

Last edited by RED2 (2016-01-17 23:20:15)

Scimmia · 2016-01-17 23:20:34

You can't use vfat for your root filesystem.

RED2 · 2016-01-17 23:24:43

Cannot use vfat filesystem? Really? Why? The usb device is vfat with ArchISO.
I've tried MMCBLK0P2 as ext4, however, I was unable to mount it, thus unable to do pacstrap.

Last edited by RED2 (2016-01-17 23:26:28)

Scimmia · 2016-01-17 23:27:27

You need a POSIX compliant filesytem. The specific error you're seeing is because vfat doesn't allow colons in filenames, but you'd have other problems as well.

The ISO only uses it for the EFI system partition, which is normal.

RED2 · 2016-01-17 23:34:39

Ah ... I see.
To understand better, so the Nextbook Tablet having MMCBLK0 is EFI file system only and only vfat partitions?
I've read the Beginner's guide, Grub Wiki, and several how-tos install ArchLinux to Tablets, of which, at some point, a step or two does not work right.
Unknown how to grub menu command to preset the mount points and then install to mmcblk0p2 from the usb boot grub i686 ArchISO.img
Or after USB boot up i686 ArchISO and mount /dev/mmcblk0p2 /mnt/mmc, how to install ArchISO.img directly from path of USB bootmnt located at /dev/sda1?
Or install i686 ArchISO.img from eth0 to mount /dev/mmcblk0p2 /mnt/mmc?
Or other option for i686 ArchLinux installation to mount /dev/mmcblk0p2 /mnt/mmc?
Please note, currently, I can USB boot, grub menu, to the i686 ArchISO.img, I have some of the workable instruction set is already done here, I will share it, help fine tune this, and publish here or other method.
Unknown whether or not this is feasible here on forum, I am open to help others and pay a nominal fee $25, 50, 75 for a nice workable complete instruction set via the usb booti32, grub menu options, proper set up of mmcblk0 partitions, and successful installation of either ArchLinux ISO, or i686, or x86_64 onto Nextbook tablet mmcblk0 drive. Also, I have another tablet, ASUS T100TAF that I'd like to get ArchLinux installed, the USB boot grub ArchISO is also doable on this, same issue with this tablet's mmcblk0 solid state drive as discovered on this post of Nextbook tablet.

Thank you,
RED2

Last edited by RED2 (2016-01-18 02:53:16)

Scimmia · 2016-01-18 02:48:28

Forget about the ISO. You've got that booting, that's all that matters. From here, you do a normal installation including, at a minimium, an EFI system partition and a root partition.

RED2 · 2016-01-18 04:00:33

Scimmia wrote:

Forget about the ISO. You've got that booting, that's all that matters. From here, you do a normal installation including, at a minimium, an EFI system partition and a root partition.

Ah ... that is what i had thought beforehand - thank you for the clarification.

I've been stuck on this ArchLinux install to tablet over two months, little embarrassed, I come from the dinosaur days, so decipher the ArchLinux wiki's on Grub, Beginner Guide, etc is a challenge with newer tech terminologies, and devices such as this Nextbook and ASUS T100 having mmcblk0 solid state drives.

So, I gather these two tablets requires vfat partitions - ok, done.

Thus far, the mmcblk0p2 has broken/partial installs and possibly a good install at folder location root.i686 (appears to have full folders here, I think I did the tar method from the i686.tar file). Unknown of how to wipe out these broken/partial folders to start fresh again. Unknown if how to make the root.i686 the primary ArchLinux at boot up from mmcblk0p1.

Not entirely clear of how to make mmcblk0p1 really boot up correctly.

Not entirely clear of how to make mmcblk0p2 really has good ArchLinux installation.

I am sold on the ArchLinux platform, I really do need help with the EFI system partition, root partition, and proper normal installation - please.

Thanks,
RED2

Last edited by RED2 (2016-01-18 04:07:39)

Scimmia · 2016-01-18 05:23:16

RED2 wrote:

Thus far, the mmcblk0p2 has broken/partial installs and possibly a good install at folder location root.i686 (appears to have full folders here, I think I did the tar method from the i686.tar file). Unknown of how to wipe out these broken/partial folders to start fresh again. Unknown if how to make the root.i686 the primary ArchLinux at boot up from mmcblk0p1.

OK, stop there. This makes no sense at all. Forget all of this root.i686 stuff, what happens when you do a normal install following the Beginner's Guide?

Edit: BTW, that processor seems to support x86_64, why aren't you using that? That could be part of your issue, as 64 bit UEFI needs a 64 bit executable to run. Unless it's one of those strange systems with 32 bit UEFI, but I don't believe the install media supports that.

Last edited by Scimmia (2016-01-18 06:26:19)

RED2 · 2016-01-18 19:57:53

Scimmia wrote:

RED2 wrote:
Thus far, the mmcblk0p2 has broken/partial installs and possibly a good install at folder location root.i686 (appears to have full folders here, I think I did the tar method from the i686.tar file). Unknown of how to wipe out these broken/partial folders to start fresh again. Unknown if how to make the root.i686 the primary ArchLinux at boot up from mmcblk0p1.
OK, stop there. This makes no sense at all. Forget all of this root.i686 stuff, what happens when you do a normal install following the Beginner's Guide?
Edit: BTW, that processor seems to support x86_64, why aren't you using that? That could be part of your issue, as 64 bit UEFI needs a 64 bit executable to run. Unless it's one of those strange systems with 32 bit UEFI, but I don't believe the install media supports that.

The Nextbook and ASUS tablet is a 32 bit UEFI, with x86_64 processor. The USB stick I built, requires the bootia32.efi, then two grub menu selection for i686 ArchISO and x86_64 ArchISO, both works fine to boot up and it will load the selected choice of the ArchISO.

I am able to create 2 partitions and mkfs, first partition /dev/mmcblk0p1 as vfat and second partition /dev/mmcblk0p2 as vfat or ext4. Then mkdir /mnt/efimmc for partition 1 and mkdir /mnt/mmc for partition 2.

I can mount the partition 1 at /dev/mmcblk0p1 to /mnt/efimmc. If partition 2 at /dev/mmcblk0p2 is ext4 format, I cannot mount it to /mnt/mmc, it says unknown filesystem type ext4.

Scimmia · 2016-01-18 20:14:58

Sounds like the ext4 kernel module isn't available.

RED2 · 2016-01-18 20:33:29

Scimmia wrote:

Sounds like the ext4 kernel module isn't available.

Ah ... searching wiki how to add ext4 kernel module. Performed 'modprobe ext4' returned no message.

Here is the 'lsmod' info

Module                  Size  Used by
overlay                40960  1
squashfs               49152  1
loop                   28672  2
nls_iso8859_1          16384  1
nls_cp437              20480  1
vfat                   20480  1
fat                    65536  1 vfat
sd_mod                 36864  2
cdc_ether              16384  0
usbnet                 32768  1 cdc_ether
r8152                  45056  0
mii                    16384  2 r8152,usbnet
uas                    24576  0
usb_storage            61440  2 uas
scsi_mod              147456  3 uas,usb_storage,sd_mod
hid_generic            16384  0
usbhid                 45056  0
hid                   114688  2 hid_generic,usbhid
i915                 1056768  0
xhci_pci               16384  0
i2c_algo_bit           16384  1 i915
xhci_hcd              155648  1 xhci_pci
drm_kms_helper        102400  1 i915
drm                   286720  2 i915,drm_kms_helper
usbcore               196608  8 uas,r8152,usb_storage,usbhid,usbnet,xhci_hcd,xhci_pci,cdc_ether
mmc_block              36864  0
crc32c_intel           24576  0
usb_common             16384  1 usbcore
intel_gtt              20480  1 i915
button                 16384  1 i915
serio                  20480  0
video                  32768  1 i915
sdhci_acpi             16384  0
sdhci                  40960  1 sdhci_acpi
led_class              16384  1 sdhci
mmc_core              110592  3 mmc_block,sdhci,sdhci_acpi

Last edited by RED2 (2016-01-18 22:01:08)

Scimmia · 2016-01-18 20:38:00

try `modinfo ext4`. Also check the filesystem, it should be located in /usr/lib/modules/<kernelversion>/kernel/fs/ext4/

RED2 · 2016-01-18 20:56:26

Scimmia wrote:

try `modinfo ext4`. Also check the filesystem, it should be located in /usr/lib/modules/<kernelversion>/kernel/fs/ext4/

modinfo ext4
modinfo: ERROR: Module alias ext4 not found

The filesystem shows file 'ext4.ko.gz' exists at folder path /usr/lib/modules/4.2.2-1-ARCH/kernel/fs/ext4/

Scimmia · 2016-01-18 21:02:18

And what is `uname -r`?

RED2 · 2016-01-18 21:09:57

uname -r
4.2.5-1-ARCH

Last edited by RED2 (2016-01-18 21:10:25)

Scimmia · 2016-01-18 21:16:57

So there's your problem. You're booting kernel 4.2.5, but you have modules for 4.2.2

RED2 · 2016-01-18 21:40:05

Ah, ok, makes sense. Isn't this configuration directly from the boot up of the USB x86_64 ArchISO image? Not sure of my next steps then?

Last edited by RED2 (2016-01-18 22:00:00)

Scimmia · 2016-01-18 21:52:21

Since I don't use either GRUB or the ISO, I don't know where to tell you to go. For one reason or another, you're loading a different kernel than is installed in the image.

RED2 · 2016-01-18 23:01:13

I had the wrong airootfs.sys version. It is fixed now.
Now I see /usr/lib/modules/4.2.5-1-ARCH/ folder and the uname -r is 4.2.5-1-ARCH, both match.
And partition 2 having ext4 format, I am able to mount /dev/mmcblk0p2 to /mnt/mmc.
Good, ok, attempting to do ArchLinux install via pacstrap /mnt/mmc base

RED2 · 2016-01-18 23:43:16

Awesome. Looks like successful install ArchLinux x86_64 at partition 2 mounted at /mnt/mmc.
Now onward to the partition 1 at /mnt/efimmc to install efi boot loader files.
Since partition 1 is 32 bit UEFI based, then assumption is bootia32.efi, grub, for symbolic pointer to the root partition 2.
Would this be based on UUID rather than LABEL name?
The partition 2 does not have a LABEL name, unable to issue 'mlabel -i /dev/mmcblk0p2 ::ARCH_SYSTEM'. << ah, dos fat32 fs cmd, thks for clarification

Last edited by RED2 (2016-01-19 02:48:51)

Scimmia · 2016-01-19 00:12:33

You can set it up with labels or with UUIDs, it's up to you (or up to GRUB, again, I don't know it).

Of course mlabel doesn't work, it isn't an MSDOS filesystem. You really seem hung up on FAT32.

progandy · 2016-01-19 00:34:40

Since partition 1 is 32 bit UEFI based, then assumption is bootia32.efi, grub

Exactly. If you prefer refind, then you can try the binary 32bit version provided here or build your own copy from the sourcecode and a modified refind-efi PKGBUILD.
http://www.rodsbooks.com/refind/getting.html

For labeling ext2/3/4 partitions (and other actions) , you need to use the tools provided by e2fsprogs, e.g. tune2fs or e2label.

Last edited by progandy (2016-01-19 00:40:27)

RED2 · 2016-01-19 03:23:39

Thank you Scimmia for your invaluable help.
Thank you progandy for the e2fsprogs and refind info.

Looking at ArchLinux Grub wiki.
Looking at rEFInd info, will review in-depth.

As per ArchLinux Grub wiki, UEFI systems, Create an ESP.

arch-chroot /mnt/mmc /bin/bash

Successful with new prompt having [] bracket as in [root@archiso /]#

pacman -S grub
pacman -S efibootmgr

Successful installations.

Grub-install fails, having issues and understanding with --efi-directory (and --boot-directory).
Msg: '/boot', '/mnt/boot', doesn't look like an EFI partition.
Also Msg: failed to get canoical path of '/boot', '/mnt/boot', etc.

Yet, the parted /dev/mmcblk0 print shows ...

GNU Parted 3.2
Using /dev/mmcblk0
Model: MMC 032GE4 (sd/mmc)
Disk /dev/mmcblk0: 31.3GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number   Start        End        Size       File system    Name                     Flags
1              1049kB   513MB   512MB   fat16              EFI System            boot, esp
2              512MB    31.3GB  30.8GB   ext4               ARCH_SYSTEM

The cfdisk /dev/mmcblk0 shows ...

Label: gpt
Filesystem: vfat
Partition 1 as EFI System having mount point at /mnt/boot
Partition 2 as Linux root (x86_64) having mount point at /mnt/mmc

Scimmia · 2016-01-19 03:31:26

I think you meant to mount to to /mnt/mmc/boot/. Right now, it wouldn't be available inside the chroot.

RED2 · 2016-01-19 04:10:20

Ah ... fixed the mount point of /dev/mmcblk0p1 /mnt/mmc/boot

arch-chroot /mnt/mmc /bin/bash

Successful transfer arch-chroot 'root' to the mmc partition 2, verified with ls -l command

Next step:

grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=grub --recheck
Installing for x86_64-efi platform.
efibootmgr: EFI variables are not supported on this system.
efibootmgr: EFI variables are not supported on this system.
Installation finished. No error reported.

Review of EFI and Grub folders shows several different efi and grub cfg files, etc.

Boot to this fails, attempt manual file manager locator to any of these efi files and all these fails.

\EFI\grub\grubx64.efi fails.
\grub\x86_64-efi\core.efi fails.
\grub\x86_64-efi\grub.efi fails.

Selection of bootia32.efi shows the grub prompt.

Hmm ...

Last edited by RED2 (2016-01-19 04:13:09)

Arch Linux

#1 2016-01-17 23:12:09

ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#2 2016-01-17 23:20:34

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#3 2016-01-17 23:24:43

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#4 2016-01-17 23:27:27

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#5 2016-01-17 23:34:39

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#6 2016-01-18 02:48:28

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#7 2016-01-18 04:00:33

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#8 2016-01-18 05:23:16

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#9 2016-01-18 19:57:53

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#10 2016-01-18 20:14:58

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#11 2016-01-18 20:33:29

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#12 2016-01-18 20:38:00

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#13 2016-01-18 20:56:26

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#14 2016-01-18 21:02:18

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#15 2016-01-18 21:09:57

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#16 2016-01-18 21:16:57

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#17 2016-01-18 21:40:05

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#18 2016-01-18 21:52:21

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#19 2016-01-18 23:01:13

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#20 2016-01-18 23:43:16

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#21 2016-01-19 00:12:33

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#22 2016-01-19 00:34:40

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#23 2016-01-19 03:23:39

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#24 2016-01-19 03:31:26

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

#25 2016-01-19 04:10:20

Re: ArchLinux i686 Install Issue on Nextbook Tablet via USB bootup ArchISO

Board footer