You are not logged in.
Pages: 1
Hello!
I've downloaded the latest Arch Linux ISO-image and put it on an USB-stick:
sudo dd if=archlinux-2017.11.01-x86_64.iso of=/dev/sdbIf I plug the stick into my computer the system boots from the USB-stick and I can select on the Arch Linux boot menu, what I want to do (booting Arch Linux, checking the memory, turning the machine off, ...). As I'm selecting Arch Linux without any custom boot parameters Arch Linux does not start properly. I get USB disconnects and the error code -32 along with the hint, that the cable could be broken. The computer is brand new and the USB-stick as well. I've tried all USB-ports, but the problem still remains. Sometimes it boots but most of the time, it does not boot.
To ensure that the hardware is working properly I've copied Kali Linux on the same USB-stick I've copied before Arch linux on. Again I've used dd to write the ISO-image directly to the USB-stick. Kali Linux booted on all tries and all ports every time properly without any trouble. Thus I'm assuming, that the hardware is working fine. Just to isolate the problem, later on I prepared again an Arch Linux USB-stick and at one of the really rare times Arch Linux has booted from the USB-stick I've installed it on the disk. The installed version of Arch Linux is booting fine. Using then an USB-stick as a mass storage device from time to time I see the same errors as during the boot process.
During the boot process I get as well ACPI errors due to a namespace lookup failure. I've made an BIOS Update to the latest version available on the website of the vendor, but that has not fixed the ACPI problems. Turning ACPI off is not an optioni for me. Not an a mobile device. Maybe the ACPI problem could be the reason for the USB problems, but that seems to me at the moment not feasible. In the BIOS setting of the machine I've deactivated Secure Boot and switched back to Legacy Only mode (no UEFI is in use).
What's going wrong and how can I fix it? On the internet I haven't found any helpful information on this topic. Could an boot parameter fix the issue?
Is it possible, that Kali Linux is more error-tolerant than Arch Linux and my test of the hardware is not convincing enough?
Last edited by Me@Work (2017-11-12 20:28:22)
Offline
Try passing "usbcore.autosuspend=-1", see https://bbs.archlinux.org/viewtopic.php?id=231733
Offline
As well as the comment from @seth, you forgot the "&& sync" at the end of the dd command - see..
https://wiki.archlinux.org/index.php/US … a#Using_dd
Do you have the same issue if you have/can use a usb2 port?
Offline
Pages: 1