First time installing Arch

kitnikitafedosoff · 2020-06-28 13:34:45

Hey fam!
I am first time installing Arch Linux on my laptop Toshiba Satellite C855 M12 Modena.
First I’ve downloaded and burnt iso file through a program called Rufus.
File was downloaded from the official archlinux.org website.
For first installation I’ve used a combination of both methods mentioned in itsfoss.com/install-arch-linux and itsfoss.com/install-kde-arch-linux.

It resulted into a following trouble with logging into my user account on the desktop(tty with graphic interface(plasma):

• I’m logging in with my password
• It turns me to a black screen with

Starting version 245.6-8-arch
/dev/sda1: clean, 246934/655360 files, 2193022/2621440 blocks

• Then it throws me back to normal desktop login screen as if I would have to start the whole logging process over again.
Tried going to tty2, there is no /home/myusername file/folder even tho it still allows me to login as myusername, but doesn’t give superuser’s right even though myusername has ALL (ALL) = ALL in /etc/hosts file.

I decided to reinstall the whole thing again, formatted partitions with fdisk, saved changes, restarted the laptop and noticed that when I launch boot from usb the bios shows me following lines before going further(It was showing those lines all the time, I just got to pay attention to these only now):

Probing EDD (edd=off to disable)... ok
[    0.984132] ACPI Error: Needed type [Reference], found [Integer] (____ptrval____)  (20200110/exresop-66)
[    0.984203] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store]  (20200110/dswexec-431)
[    0.984268] ACPI Error: Aborting method \_PR.CPU0.PDC due to previous error (AE_AML_OPERAND_TYPE) (20200110/psparse-529)

Then it’s followed by following lines of code:

 :: running early hook [udev]
Starting version 245.5-2-arch
:: running early hook [archiso-pxe-nbd]
:: running hook [udev]
:: Triggering events...
:: running hook [memdisk]
:: running hook [archiso]
:: running hook [archiso_loop_mnt]
:: running hook [archiso_pxe_common]
:: running hook [archiso_pxe_nbd]
:: running hook [archiso_pxe_http]
:: running hook [archiso_pxe_nfs]
:: Mounting ‘/dev/disk/by-label/ARCH_202006’ to ‘/run/archiso/bootmnt’
Waiting 30 seconds for device /dev/disk/by-label/ARCH_202006 ...
:: Device ‘/dev/disk/by-label/ARCH_202006’ mounted successfully.
:: Mounting /run/archiso/cowspace (tmpfs) filesystem, size=256M...
:: Mounting ‘/dev/loop0’ to ‘/run/archiso/sfs/airootfs’
:: Device ‘/dev/loop0’ mounted successfully.
:: running late hook [archiso_pxe_common]
:: running cleanup hook [archiso_shutdown]
:: running cleanup hook [udev]

Welcome to Arch Linux!

Since it gets me to the developer zone where I’m logged in as a root user, I’ve thought that everything is just fine.
Then, when I’ve tried to shutdown the system it has shown me the list of processes happening to shut the system down and there I’ve noticed that a few processes have failed.
Those are:

 [FAILED] Failed unmounting Temporary /etc/pacman.d/gnupg directory.
[FAILED] Failed unmounting /run/archiso/bootmnt.

And after the “[ OK ] Reached target Power-Off”:

 /dev/mapper/control: open failed: No such device
Failure to communicate with kernel device-mapper driver.
Check that device-mapper is available in the kernel.
Incompatible libdevmapper 1.02.170 (2020-03-24) and kernel driver (unknown version).
Command failed.
umount: can’t unmount /dev/loop0: Invalid argument
umount: can’t unmount /oldrun/archiso/cowspace: Invalid argument

After that before the very shutdown the very last line was:

 [   61.0S4Z09] reboot: Power down

I ran memtest, checked hardware info and everything has assured to be fine.
Of course, it means that I’ve done something wrong on some sort of phase.
What has happened?
Why system resulted in those type of errors?
Where were done my mistakes?
How can I resolve the issue?
Either, how can I fix it?
Please, do not end the topic until my response, because I’d be glad if I could get the max out of being in here.
Thanks in advance for understanding.
Best regards, Nikita.

Last edited by kitnikitafedosoff (2020-06-28 14:11:02)

Head_on_a_Stick · 2020-06-28 13:40:47

kitnikitafedosoff wrote:

For first installation I’ve used a combination of both methods mentioned in itsfoss.com/install-arch-linux and itsfoss.com/install-kde-arch-linux.

No. Just no.

Please go through the official installation guide and the relevant ArchWiki page for Plasma to see where those "guides" fucked things up for you.

EDIT: and please use code tags when posting terminal or console output.

Last edited by Head_on_a_Stick (2020-06-28 13:45:00)

kitnikitafedosoff · 2020-06-28 13:46:25

Oh okay. Thank you, Head_on_a_Stick

seth · 2020-06-28 13:49:41

OP wrote:

I decided to reinstall the whole thing again, formatted partitions with fdisk

@kitnikitafedosoff, please edit your post. Add some paragraphs and wrap shell I/O and file contents into code tags, https://bbs.archlinux.org/help.php#bbcode
I assume HoaS stopped at that line because nobody wants to read that wall of text.

kitnikitafedosoff · 2020-06-28 14:15:14

seth, thank you very much for the advice

seth · 2020-06-28 15:05:15

as if I would have to start the whole logging process over again.

The system did indeed reboot.

there is no /home/myusername file/folder

See

useradd --help | grep -- -m

.

doesn’t give superuser’s right even though myusername has ALL (ALL) = ALL in /etc/hosts file.

/etc/hosts is not the sudoers file, seems you followed a quite shitty tutorial there… ;-)

shows me following lines before going further

ACPI errors are common and usually harmless. They indicate that board vendors implement ACPI by trial-and-does-windows-now-boot …

Since it gets me to the developer zone

The linux console is not the "developer zone"

where I’m logged in as a root user, I’ve thought that everything is just fine.

Seems so far.

I’ve noticed that a few processes have failed.

Looks like you didn't exit the chroot.

Here's the crucial question: did you follow https://wiki.archlinux.org/index.php/Installation_guide (which tells you to exit the chroot…) or this shitty "follow along installing a true h4x0r linux!!!!" tutorial again?
What did you do between entering the "developer zone" and rebooting?

Last edited by seth (2020-06-28 15:07:46)

Arch Linux

#1 2020-06-28 13:34:45