You are not logged in.
Hello everybody!
I've downloaded installation media, but failed to load it because of the error. ENTIRE log that I can see is:
:: running early hook [udev]
starting version 235
:: running early hook [archiso_pxe_ndb]
:: running hook [udev]
:: Triggering uevents...
[ 4.586809] hub 1-0:1.0: config failed, hub doesn't have any ports! (err -19)
[ 4.748790] nouveau 0000:07:00.0: DRM: Pointer to flat panel table invalid
[ 6.027135] nouveau 0000:42:00.0: DRM: Pointer to flat panel table invalid
[ 7.283873] nouveau 0000:43:00.0: DRM: Pointer to flat panel table invalid
:: running hook [memkisk]
:: 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_201712' to '/run/archiso/bootmnt'
Waiting 30 seconds for device /dev/disk/by-label/ARCH_201712 ...
ERROR: '/dev/disk/by-label/ARCH_201712' device did not show up after 30 seconds...
Falling back to interactive promt
You can try to fix the problem manually, log out when you are finished
sh: can't access tty; job control turned off
[rootfs ]# _
What did I wrong?
Thanks for your attention!
Last edited by alex_hmn (2017-12-15 07:10:07)
Offline
Have you verified the checksum of the downloaded iso ?
Which os/program did you use to put it on which medium (cd, usb stick etc)
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
Yes, checksum is verified.
I'm using rufus 2.7.855 from win10.
Tried in both DD and ISO modes. Result is the same.
Offline
Try booting with nomodeset, however this reads like an issue with the image. To which medium and with which tools did you write the image you are attempting to start here? Did you verify the checksums of the image?
Edit: Whoops too slow...
Last edited by V1del (2017-12-13 13:36:46)
Offline
Use win10 Disk Management to check the label of the drive .
If it's not ARCH_201712 , change it to that.
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
I've finally found a problem!
It was a problem with USB ports connection to motherboard, so I've reconnected them and installation media started to work.
Sorry for disturbing you guys
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
Well that can happen, please mark as [SOLVED] by editing the title of your first post
Offline
to slow
Last edited by Lone_Wolf (2017-12-14 08:27:40)
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