You are not logged in.
Hi everyone,
I have a Dell Venue 8 Pro and there is installed windows 8.1.
Since I want to install Arch, I disabled the secure boot but when I try to boot Archlinux usb for the installation, the tablet keeps booting windows.
I found this guide but it seems to be old.
Useful information:
CPU: Intel Atom Z3740D Processor (2MB Cache, up to 1.8GHz Quad-Core)
RAM: 2 GB DDR3L SDRAM
Last edited by Superjolly002 (2020-04-29 18:28:02)
See, I'm not a monster. I'm just ahead of the curve.
Offline
Everything you need know to install Arch is documented in the Arch wiki installation guide
Last edited by f33dm3bits (2020-04-24 16:34:06)
Offline
The problem keeps persisting, because the tablet doesn't boot the archlinux iso
See, I'm not a monster. I'm just ahead of the curve.
Offline
The guide Superjolly002 posted does mention an important detail :
You'll need a 32-bit UEFI bootloader, there's a couple of options to get that sorted.
It seems the dell venue 8 Pro is one of the (rare) systems that uses a 32-bit uefi firmware.
Archiso doesn't support that, but there are workarounds .
Read https://wiki.archlinux.org/index.php/Un … _Interface thoroughly to find them.
Sidenote :
While the installation guide doesn't state 32-bit uefi as a special case, it does link to the uefi page.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Thank you so much, I finally booted the usb.
But now there is a new problem, it doesn't load the kernel...
This is the error:
error: no such device: ARCH_202002.
error: file `/arch/boot/x86_64/vmlinuz` not found.
error: you need to load the kernel first.
This is my grub.cfg:
insmod part_gpt
insmod part_msdos
insmod fat
insmod efi_gop
insmod efi_uga
insmod video_bochs
insmod video_cirrus
insmod font
if loadfont "${prefix}/fonts/unicode.pf2" ; then
insmod gfxterm
set gfxmode="1024x768x32;auto"
terminal_input console
terminal_output gfxterm
fi
menuentry "Arch Linux archiso x86_64 UEFI USB" {
set gfxpayload=keep
search --no-floppy --set=root --label ARCH_202002
linux /arch/boot/x86_64/vmlinuz archisobasedir=arch archisolabel=ARCH_202002 add_efi_memmap
initrd /arch/boot/intel_ucode.img /arch/boot/x86_64/archiso.img
}
What did I do wrong?
P.s: my arch iso: archlinux-2020.02.01-x86_64.iso
See, I'm not a monster. I'm just ahead of the curve.
Offline
Maybe the label is not what we think it is .
The archiso label can be aquired from the .iso file with isoinfo from cdrtools or iso-info from libcdio.
run
$ isoinfo -d -i /path/to/archlinux/isofile
to verify the label .
Last edited by Lone_Wolf (2020-04-27 11:08:38)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The output is:
Setting input-charset to 'UTF-8' from locale.
CD-ROM is in ISO 9660 format
System id:
Volume id: ARCH_202002
Volume set id:
Publisher id: ARCH LINUX <HTTP://WWW.ARCHLINUX.ORG>
Data preparer id: PREPARED BY MKARCHISO
Application id: ARCH LINUX LIVE/RESCUE CD
Copyright File id:
Abstract File id:
Bibliographic File id:
Volume set size is: 1
Volume set sequence number is: 1
Logical block size is: 2048
Volume size is: 330752
El Torito VD version 1 found, boot catalog is in sector 40
NO Joliet present
SUSP signatures version 1 found
Rock Ridge signatures version 1 found
Rock Ridge id 'RRIP_1991A'
Eltorito validation header:
Hid 1
Arch 0 (x86)
ID ''
Cksum AA 55 OK
Key 55 AA
Eltorito defaultboot header:
Bootid 88 (bootable)
Boot media 0 (No Emulation Boot)
Load segment 0
Sys type 0
Nsect 4
Bootoff 8029 32809
The label is correct, what else could it be?
See, I'm not a monster. I'm just ahead of the curve.
Offline
While it certainly won't hurt to do this the long way on your own, if you want to get a working Arch Linux ISO for 32bit EFI systems, you can use archisomod from https://gitlab.com/HOMEINFO/archiso-tools
I wrote this script a while ago for my company since we also deployed some systems using 32bit EFIs.
Last edited by schard (2020-04-27 12:16:34)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
Thank you, I have created an iso that I can boot correctly.
Just one thing, when I boot the iso I have to change the boot options and replace i386 with x86_64.
I executed the following command:
sudo ./archisomod -v -e i386 ~/archlinux-2020.02.01-x86_64.iso ~/archlinux.iso
Did I do something wrong?
Anyway, I followed all the instructions of Archlinux installation except for the grub installation where I did :
grub-install --target=i386-efi --efi-directory=/boot --bootloader-id=ArchLinux --recheck
grub-mkconfig -o /boot/grub/grub.cfg
But when I boot the micro sd, it does boot windows.
EDIT: I finally installed archlinux, the solution to my problem is described in this post, thanks to everyone
Last edited by Superjolly002 (2020-04-29 18:27:42)
See, I'm not a monster. I'm just ahead of the curve.
Offline
Just one thing, when I boot the iso I have to change the boot options and replace i386 with x86_64.
I executed the following command:
sudo ./archisomod -v -e i386 ~/archlinux-2020.02.01-x86_64.iso ~/archlinux.iso
Did I do something wrong?
Nope, this was a bug in the script. Good catch! I fixed it in commit cf8355084c03ca03c929ff608ff376b5b6935151.
Last edited by schard (2020-05-04 14:49:48)
Inofficial first vice president of the Rust Evangelism Strike Force
Offline