You are not logged in.
- Topics: Active | Unanswered
#1 2013-12-29 17:28:29
- Petrovich1999
- Member
- Registered: 2013-12-29
- Posts: 2
Unable to enumerate usb device - GIGABYTE GA-970A-DS3 and x64 kernel
Hi, im new to linux. But i really like the idea of this distribution, so i decided to check arch out. I tried ubuntu, slackware and didnt like them for some reasons. I also tried linux mint, it's really nice but i wan't more control over my system and linux knowledge (that's why try linux instead of working on my windows 7).
So i installed arch on my virtual box, did some customizes and it works atm.
Now i want to install arch on my PC as second system.
I made my usb flash with archlinux-2013.12.01-dual.iso on it by this guide https://wiki.archlinux.org/index.php/US … tion_Media (Using manual formatting (Alternative method)).
It works, but when i try to load x86_64 kernel load fails (or smth like that, i dont really know).
It writes smth like this:
--- waiting /dev/disk/by-label/ARCH_201312
--- ...
--- usb 2-1: device descriptor read/64, error -32
--- some errors here (linked to first)
--- ...
--- this 4-5 errors repeat some times
--- ...
--- unable to enumerate usb device
and then falling back to ramfs promt (or smth like that)
I tried to switch usb ports, and it didnt help.
With unplagged mouse i still get some errors, but arch loads, though i can't use keyboard
i googled around and found this:
https://bbs.archlinux.org/viewtopic.php?id=158206
https://bbs.archlinux.org/viewtopic.php?id=158492
as i could understand, it was fixed since kernel version 3.8
but this arch is with 3.12 kernel.
i'm loading not in UEFI mode
arch 32bit installation menu entry works fine
i have motherboard http://www.gigabyte.com/products/produc … id=4122#ov
keyboard - Logitech K seriers (120 probably)
mouse - A4Tech Bloody V7
usb flash - Silicon-power 8Gb
Sorry for my bad english
Last edited by Petrovich1999 (2013-12-31 12:48:38)
Offline
#2 2013-12-31 01:40:06
- Petrovich1999
- Member
- Registered: 2013-12-29
- Posts: 2
Re: Unable to enumerate usb device - GIGABYTE GA-970A-DS3 and x64 kernel
i have 3.0 version of this motherboard, though it doesn't change anything.
So i found out that its either my motherboard or kernel drivers work wrong.
this post describes what's going on better
this guy has same issue. He says that latest bios for his asus on 970 chipset works well.
For my GIGABYTE mb BIOS update didn't help.
So i enabled IOMMU in BIOS peripherals, and linux kernel loads. But i have read that it hits overall PC perfomance.
BIOS update for my mb GA-970A-DS3 (rev. 3.0)
and BIOS update for GA-970A-D3 (rev. 1.4)
(revisions display only difference in preinstalled bios)
Here is question. 2nd is later. Can i use it or not? This is more related to gigabyte forums than arch, but i just dont want to create another thread for crap question.
Maybe it will solve the issue without enabling IOMMU
Last edited by Petrovich1999 (2013-12-31 11:11:33)
Offline
#3 2014-01-04 01:41:57
- Peterle
- Member
- Registered: 2013-03-10
- Posts: 13
Re: Unable to enumerate usb device - GIGABYTE GA-970A-DS3 and x64 kernel
Offline
#4 2015-07-09 11:25:08
- Ambrevar
- Member
- Registered: 2011-08-14
- Posts: 212
- Website
Re: Unable to enumerate usb device - GIGABYTE GA-970A-DS3 and x64 kernel
I have the same issue with a GA-970A-DS3P. USB3 ports are working perfectly, but the USB2 refuse to accept devices randomly (most of the time), even the front panel ports. It is the opposite on Windows 7. Changing kernel did not help.
Installing Arch with this issue would have been tricky if it were not for the USB3 ports. Since this motherboard has 2 USB3 ports, a keyboard and the USB media would be enough to perform the install.
The aforementioned link did not help. Flashing the BIOS neither. However this link was insightful:
http://unix.stackexchange.com/questions … -uefi-bios
* Enable IOMMU. This made USB2 work, but I experienced a lot of issues: no USB3 anymore (!), IOMMU errors on startup, slow startup, crashes.
* Appending `iommu=soft` to the kernel parameters solved _all_ the above problems.
Now the question is, is it the manufacturers fault or should the Linux kernel behave differently on this? If the latter case is true, I'll file a bug report on kernel.org.
Last edited by Ambrevar (2015-07-09 13:37:42)
Offline