Hi, Sorry for my bad english: i have a GigaByte GA-970A-DS3 motherboard with FX-4100 CPU. I try to boot with gentoo amd64 minimal from pendrive but instantly after begin the boot process all my usb stop working(optical mouse led is off and when need to set the keyboard layout, my keyboard is dead) and after this the boot process fail because the pendrive is not present too. On this system run a windows 7 without problem, and i have installed Gentoo x86 working perfect, but i wish to change to amd64 version of gentoo and this process was tried with more earlier amd64 version without success. Reproducible: Always
Which exact iso (full filename) did you use?
(In reply to Ben Kohler from comment #1) > Which exact iso (full filename) did you use? install-amd64-minimal-20131010.iso
(In reply to Frici from comment #2) > (In reply to Ben Kohler from comment #1) > > Which exact iso (full filename) did you use? > > install-amd64-minimal-20131010.iso I guess is something motherboard incompatibility problem with 64 bit gentoo... I have the latest BIOS update installed
Are you using the USB-2.0 or 3.0 ports? Try switching from one to the other, if you can. It's possible there is a problem specific to the EHCI (2.0) or XHCI (3.0) driver.
(In reply to Ben Kohler from comment #4) > Are you using the USB-2.0 or 3.0 ports? Try switching from one to the > other, if you can. It's possible there is a problem specific to the EHCI > (2.0) or XHCI (3.0) driver. now i am in the office, cannot check, but probably the pendrive is now in USB 3.0 but the keyboard and the mouse sure is in USB 2.0 I tried to boot after was disable in BIOS the audio, lan and USB 3.0(in this case is sure the pendrive was in USB 2.0 port) but the same result
I have news: all USB 3.0 port is ok, i have two(boot pendrive+keyboard), and all USB 2.0 is dead(there is the mouse) with dmesg i get this error: usb 7-3: device descriptor read/64, error -32 usb 7-3: device descriptor read/64, error -32 usb 7-3: device descriptor read/64, error -32 usb 7-3: device descriptor read/64, error -32 usb 7-3: device not accepting address 4, error -32 usb 7-3: device not accepting address 5, error -32
Interesting output, can you attach the full output from dmesg after a (semi) successful boot? I'm curious what it shows while the EHCI driver is being initialized.
Created attachment 361266 [details] full dmesg
(In reply to Ben Kohler from comment #7) > Interesting output, can you attach the full output from dmesg after a (semi) > successful boot? I'm curious what it shows while the EHCI driver is being > initialized. hi, dmesg is attached, i hope you can detect something interesting Thanks for your help Frici
I just had a thought on this-- the OHCI/UHCI drivers may be interfering with the EHCI drivers. If you boot with kernel parameters "ohci_hcd.blacklist=yes uhci_hcd.blacklist=yes", does it make any difference?
Thanks for help i will today
We need more information to work on this bug.
I have nearly the same motherboard and pretty much the same problem. I tried ohci_hcd.blacklist=yes etc and it made no difference - no keyboard input accepted. I'm using the latest iso as of yesterday (March 14, 2021). I somehow installed Gentoo probably 5 years ago, although this problem appears to go back to 2013. I noticed the same problem with another minimal install CD (Gentoo) that I made several years ago. Can we work to get this problem fixed? I'm willing to help. Best Wishes, Bob Gleitsmann
Can you boot with netconsole or serial console, so that you can check kernel messages after boot? Alternatively, you could build a new installcd based on our specs but with ssh functionality in the initramfs
I don't have another linux machine or serial terminal available. I tried the AdminCD to see if was any different, and it was not. I was trying to find the source code for these iso files but haven't so far. Would using a virtual machine be of value? I am pursuing this because I am trying to transfer my working system to an SSD. I got it through grub and it starts booting, but hangs at the point where it starts running init. I am using OpenRC. But I can pursue this. I don't think my keyboard is anything special. It works perfectly well with the complete system that I have set up and only works on the partition it was installed on. It doesn't seem like there a lot of debugging resources for this kind of problem. Forgive the digressions. Let's get this working first (if possible). If there's no there's no other way I may have to find another machine somewhere to act as a remote terminal. Bob
Maybe you can use the installcd kernel config [1] passed to genkernel on your own gentoo, build a kernel with it, and see if you can reproduce the problem there. Be sure to pass 'dokeymap' so that you get the same keymap-selection prompt. If you can reproduce the problem on your real gentoo with that kernel, then that opens up a lot more possibilities for troubleshooting and logging. [1] https://gitweb.gentoo.org/proj/releng.git/plain/releases/kconfig/amd64/installcd-4.14.52.config