Network and Xorg issues sounds to me like you did too much in one go.https://wiki.archlinux.org/index.php/Be … leshootingCheck the connection, check the driver status and load the module: https://wiki.archlinux.org/index.php/Ne … figurationIf the network interface doesn't show up (eth0), read this part: https://wiki.archlinux.org/index.php/Ne … Interfaces
The ArchLinux Wiki has the best documentation available and with the problems you describe here, if it does not suffice, ArchLinux is likely not for you.Everyone can install ArchLinux and most can use it, but it does require more from the user than Ubuntu and such.https://wiki.archlinux.org/index.php/The_Arch_Wayhttps://wiki.archlinux.org/index.php/Beginners%27_Guide
Things should be working as outlined in the wiki: https://wiki.archlinux.org/index.php/Sy … managementIf you think it's important, you can add a line about halt, although it's already mentioned in systemd FAQ https://wiki.archlinux.org/index.php/Sy … r_stays_onThere's also https://wiki.archlinux.org/index.php/Al … o_ShutdownObviously you can use an alias e.g.alias halt='sudo sy
Of course you can edit the grub.cfg manually. But you're probably looking for this: https://wiki.archlinux.org/index.php/GR … ious_entryPS: If you miss GRUB Legacy, Syslinux is very similar: https://wiki.archlinux.org/index.php/Be … bootloaderAnd don't forget to mark it as solved.
DSpider wrote:https://wiki.archlinux.org/index.php/US … _USB_driveMake sure to use /dev/sdx and NOT /dev/sdx1. This is a very common error!Also: https://wiki.archlinux.org/index.php/Arch64_FAQ (specifically "Why 64-bit?")Yes!!! for usb I had used /dev/sdb1.
Do you really want these things to start at boot, or do you want them to start when you log in? If you want them to be run at boot, read this: https://wiki.archlinux.org/index.php/Sy … process.3FIf you want to start something when you log in, refer to your DE's documentation, or use .xinitrc.