You are not logged in.
I am running into some errors while trying to install Arch on my new build. I can successfully get to the installation shell prompt, but only when I have the bootable usb and a wired usb keyboard plugged into my 2 usb 3.0 slots. When I don't have the install usb or my keyboard plugged into these slots, I get a slew of errors like the following:
device descriptor read/64, error -32
I'm sorry I can't post all of the errors, because I can't copy and paste it. When I do plug both items into the usb 3.0 slots and I get to the shell prompt, I can not establish a network connection. I know the hardware works, because everything runs fine on Ubuntu live CD (old kernel 2.6) as well as my Windows 7 boot.
I also tried booting off my old Arch hard drive and it throws the same usb errors above.
I have no idea what is going on or how to begin to get around it, so any tips or guidance will be greatly appreciated!
Edit:
I've seen some posts saying this could be a kernel issue with my hardware. Affected kernels appear to be 3.7.? and up. I'm trying to install with arch-2012.02.01. Is there a way I can attempt to install with an older kernel, say 3.6? The oldest kernel version I have on my old drive is version 3.7 something too, so I can't get into an old kernel on it. How can I install an older kernel on my old drive to see if I can get it to boot?
Edit 2:
I can successfully boot into the i686 installer with no errors. I can also establish a network connection, so this issue appears to be a i86_64 problem. The install usb I'm is using is ARCH_201302, so kernel 3.7.
***** SOLUTION *****
The solution to my problem was to enable IOMMU in my BIOS. I recently upgraded my hardware and the motherboard I got is a Gigabyte 970A-D3. IOMMU is disabled by default. See my last post below for more details.
Last edited by tlawren (2013-03-12 13:29:19)
Offline
Look here older install isos .
the 2012.09.07 iso has kernel 3.5 in it, 2012.12.01 has a 3.6 kernel .
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 just tried 2012.12.01 and 2012.09.07 and both resulted in the same issue. Here is an image of what I'm seeing each time.
Offline
I just tried 2012.12.01 and 2012.09.07 and both resulted in the same issue. Here is an image of what I'm seeing each time.
This was from 2013.02.01. The same errors occur for 12.01 and 09.07.
Last edited by tlawren (2013-03-11 11:08:03)
Offline
The latest iso 2013.03.01 has kernel 3.7.9 in it, you could try that one
If you still have an existing archinstall that boots, you can try 2 things :
install the lts 3.0.x -kernel and check if that has those errors aswell
switch to testing which has a 3.8 kernel
Last edited by Lone_Wolf (2013-03-12 11:32:21)
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
After a lot of searching I finally found the solution to my problem. I had to enable IOMMU in the BIOS on my motherboard (Gigabyte 970A-D3).
In case it helps someone else, I found the solution in the following forum post:
http://ubuntuforums.org/showthread.php?t=2114055
Another related post is:
http://ubuntuforums.org/showthread.php?t=2111223
As an aside, I'm not really sure why when IOMMU is disabled, 32-bit kernels work, but 64-bit kernels don't. I'm guessing IOMMU support is disabled in 32-bit kernels while it is enabled in 64-bit kernels. Or, it is at least handled differently.
Last edited by tlawren (2013-03-12 13:20:35)
Offline
Sorry for posting to a solved thread with no more useful information.
But I just wanted to say Thank You! I have the same motherboard and I have been trying for 2 nights now to get it to work with no luck and I had all of the same issues you posted in the first thread. This thread saved me!
Thanks!
Offline