New to Arch-based - issue with latest iso

General system EndeavourOS installation
1

Hello there!

I am a Slackware user normally, but wanted to give Arch-based a go using my Surface Go (1st gen) as a guinea pig.

I was not able to install any of the 2020 versions due to it stalling at

image
image4032×3024 2.57 MB
this screen after a clean online installer made using Rufus. Note: Picture is not of latest OS but same screen on working/booting 2019.04 iso

Decided to drop to the latest 2019 version and while it boots I am not able to update it due to key and signature errors.

image
image1512×2016 1.32 MB

I have WiFi working, some of the issues are ignorable, some are not. I’d really like to get the latest working but not sure If I am doing something wrong or not doing something before exiting liveuser after installation completes. Any help would be appreciated

2

Looks to me like a corrupt download; check the checksum on the ISO?

1 Like
3

is archlinux-keyring and endeavouros-keyring installed?

Btw welcome to EndeavourOS :grinning:

2 Likes
4

Rufus might also be the culprit. Definitely double check the checksum as Beardedgeek72 suggested, then maybe try using another option for creating the live disk.

1 Like
5

sha512 checks out; not the iso at fault.

Trying unetbootin now.

@T-Flips cannot get the install to boot at all, doesn’t post kernel, just gets stuck at the /dev/mckblk screen

6

Welcome! :smile:

Try dd instead:

sudo dd bs=4M if=/path/to/endeavouros-x86_64.iso of=/dev/sdX status=progress && sync

See more:

Unetbootin does not work AFAIK.

6 Likes
7

Looks like corrupted downloads due to keyring and mirror issues.

2 Likes
8

@ricklinux

The keyring and mirror issues are on the 2019 build that is semi-working. In fact, working on it right now.

I am making a new usb using dd with the verified ‘latest 2020’ ISO as opposed to unetbootin as suggested and will test it.

5 Likes
9

I only use dd and comfortable with using it but one mistake can cause a lot of problems if you have no idea what you are doing.
Backups!

10

Try ventoy:


Initialize the drive and just copy the ISO to the root of the USB, so much easier than “burning” images.
1 Like
11

Welp. Looks like Rufus was the issue. Same iso, same computer, same drive, just dd instead of Rufus and it looks to be working.

Strange though that Rufus worked with the 2019 iso.

Appreciate the assistance. Redoing it with online installer for the tablet mode “friendlier” Gnome DE.

EDIT: online installer fails with the same issue stalling before kernel. Going the long route to install Gnome.

2 Likes
12

Glad to hear you got it sorted! dd or openSUSE’s Imagewriter from the aur typically work for me with dd being the most consistent.

13

Welcome to the community :beers:

1 Like
14

It’s not installing or not booting once it’s installed?

15

It installs fine. Boots, and even gets to update via the welcome menu. However, after updating it from either term or the welcome menu, it fails to load the kernel when rebooting. I am thinking it has something to do with the kernel or grub updates but I am holding off on updates for now until I find a better solution. I’ve got nearly everything how I want it so far.

16

Maybe you could install inxi and post the hardware output. I think you’ll have to start looking at some boot logs and stuff.

yay -S inxi

Then inxi -Fxxxa --no-host

1 Like
17

Sorry for the late response, work got a bit hectic. Here is the output from inxi

[pyr0cide@NixVault-Go ~]$ inxi -Fxxxa --no-host
System: Kernel: 5.9.1-arch1-1 x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=42d95b0b-5342-4bb4-bfca-ddc8981364b8 rw quiet loglevel=3
nowatchdog
Desktop: GNOME 3.38.1 tk: GTK 3.24.23 wm: gnome-shell dm: GDM 3.38.1, LightDM 1.30.0 Distro: EndeavourOS
Machine: Type: Laptop System: Microsoft product: Surface Go v: 1 serial: <superuser/root required> Chassis: type: 9
serial: <superuser/root required>
Mobo: Microsoft model: Surface Go serial: <superuser/root required> UEFI: Microsoft v: 1.0.28 date: 06/17/2020
Battery: ID-1: BAT1 charge: 12.3 Wh condition: 25.2/26.3 Wh (96%) volts: 7.5/7.7 model: SMP AHA22135001 type: Li-ion
serial: 5697 status: Discharging cycles: 43
Device-1: hid-0018:04F3:261A.0001-battery model: ELAN9038:00 04F3:261A serial: N/A charge: N/A status: N/A
CPU: Info: Dual Core model: Intel Pentium 4415Y bits: 64 type: MT MCP arch: Amber Lake family: 6 model-id: 8E (142)
stepping: 9 microcode: D6 L2 cache: 2048 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 12805
Speed: 900 MHz min/max: 400/1600 MHz Core speeds (MHz): 1: 993 2: 959 3: 991 4: 940
Vulnerabilities: Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics: Device-1: Intel HD Graphics 615 vendor: QUANTA driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:591e
Display: wayland server: X.Org 1.20.9 compositor: gnome-shell driver: intel unloaded: fbdev,modesetting,vesa
display ID: :0 screens: 1
Screen-1: 0 s-res: 1800x1200 s-dpi: 96 s-size: 476x318mm (18.7x12.5") s-diag: 572mm (22.5")
Monitor-1: XWAYLAND0 res: 1800x1200 hz: 60 dpi: 218 size: 210x140mm (8.3x5.5") diag: 252mm (9.9")
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Imaging Unit vendor: QUANTA driver: ipu3-imgu
alternate: ipu3_imgu bus ID: 00:05.0 chip ID: 8086:1919
Device-2: Intel CSI-2 Host driver: ipu3-cio2 alternate: ipu3_cio2 bus ID: 00:14.3 chip ID: 8086:9d32
Device-3: Intel Sunrise Point-LP HD Audio vendor: QUANTA driver: snd_hda_intel v: kernel alternate: snd_soc_skl
bus ID: 00:1f.3 chip ID: 8086:9d71
Sound Server: ALSA v: k5.9.1-arch1-1
Network: Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter driver: ath10k_pci v: kernel port: 3000
bus ID: 01:00.0 chip ID: 168c:003e
IF: wlan0 state: up mac:
Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 1-5:2 chip ID: 0cf3:e302
Drives: Local Storage: total: 117.72 GiB used: 11.34 GiB (9.6%)
ID-1: /dev/mmcblk0 model: hC8aP size: 58.24 GiB block size: physical: 512 B logical: 512 B serial: 0x69487626
rev: 0x8 scheme: GPT
SMART Message: Unknown smartctl error. Unable to get data.
ID-2: /dev/mmcblk1 model: SN64G size: 59.48 GiB block size: physical: 512 B logical: 512 B serial: 0x9c001711
SMART Message: Unknown smartctl error. Unable to get data.
Partition: ID-1: / raw size: 57.95 GiB size: 56.79 GiB (98.00%) used: 11.34 GiB (20.0%) fs: ext4 dev: /dev/mmcblk0p2
Swap: Alert: No Swap data was found.
Sensors: System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 227 Uptime: 31m Memory: 3.72 GiB used: 1.84 GiB (49.4%) Init: systemd v: 246 Compilers: gcc: 10.2.0
Packages: pacman: 1080 lib: 249 flatpak: 0 Shell: Bash v: 5.0.18 running in: xfce4-terminal inxi: 3.1.08

So I finally got it to update. Was a problem with mirrors i believe. Pacman -Syy fixed that portion.

The newest problem is that the uSD I have will not format, and will not write/read when it is properly formatted in Slack using parted. the uSD works perfectly fine in other distros and windows. I did notice, I had this show up in the update process - not sure if it is related.

==> WARNING: Possibly missing firmware for module: xhci_pci
18

Everyone got those at mkinitcpio generation

1 Like
19

It’s difficult to help when you post output that is truncated. Plug the usb in and return:

lsblk and sudo parted -l

20

once again dd proofs it’s superior :smiley: