FC12 x86_64 Dell Optiplex 760 Install USB Keyboard Fail

maztaim · #1 18th November 2009, 06:56 PM

When attempting to install FC12 x86_64 on a Dell Optiplex 760, my USB devices stop working after initial boot. I see anaconda, but am unable to change anything since my keyboard, mouse and any other USB devices are not powering up after kernel boot.

drunkahol · #2 18th November 2009, 07:35 PM

Sounds familiar. I had USB issue during the Beta (see bug 524808). Something to do with VT-d on desktop machines. A grub line or a BIOS setting was enough to fix I thought?

Cheers

Duncan

maztaim · #3 18th November 2009, 07:57 PM

Thanks. Information in the bug report you included helped. I wound up adding "intel_iommu=off" to the boot options. I may need to disable "VT for Direct I/O" going forward in the BIOS.

drunkahol · #4 19th November 2009, 08:39 AM

Just so people know - it seems this USB bug hasn't gone away as anticipated. Work is still being done to isolate issues regarding certain USB on some configurations.

Worth putting together some info and having it as a sticky for a while?

Cheers

Duncan

jkissane · #5 24th November 2009, 12:42 PM

Quote:

Originally Posted by maztaim

Thanks. Information in the bug report you included helped. I wound up adding "intel_iommu=off" to the boot options. I may need to disable "VT for Direct I/O" going forward in the BIOS.

Thanks for the fix as I'm in the process of testing F12 on an Optiplex 760 as well. Will keep a watch on the Dell site to see if any new BIOS versions appear.

**AdamW** · #6 24th November 2009, 08:43 PM

drunkahol: what happened is we fixed the problem happening with systems with >4GB of addressable memory (approx. 2.5GB of physical RAM) but inadvertently broke it for 32-bit systems with *less* than 4GB of addressable memory. What fun.

It's all documented comprehensively in the common bugs: https://fedoraproject.org/wiki/Commo...iommu-problems

jkissane · #7 25th November 2009, 05:36 PM

Quote:

Originally Posted by AdamW

drunkahol: what happened is we fixed the problem happening with systems with >4GB of addressable memory (approx. 2.5GB of physical RAM) but inadvertently broke it for 32-bit systems with *less* than 4GB of addressable memory. What fun.

It's all documented comprehensively in the common bugs: https://fedoraproject.org/wiki/Commo...iommu-problems

I ran into the issue on a Dell Optiplex 760 with 8Gb of RAM and the 64 bit version using the kernel from the PXE image. Once the machine was fully built the same thing happened using the kernel that was installed (2.6.31.5-127.fc12.x86_64).

It was fixed by turning off "VT for Direct I/O" in the BIOS settings as pointed out by maztaim.

**AdamW** · #8 25th November 2009, 08:06 PM

you probably didn't run into the exact same issue, in that case. what was the *exact* error message you hit? and does kernel -149 (from koji) fix it?

jkissane · #9 26th November 2009, 12:42 PM

Quote:

Originally Posted by AdamW

you probably didn't run into the exact same issue, in that case. what was the *exact* error message you hit? and does kernel -149 (from koji) fix it?

Error message is:

Quote:

Your BIOS is broken; DMAR reported at address fedc1000 returns all ones!
BIOS vendor: Dell Inc.; Ver: A05; Product Version:

PC is a Dell Optixplex 760 with 8Gb of RAM running 2.6.31.5-127.fc12.x86_64 & I haven't tried any other kernels. With the "VT for Direct I/O" option turned off I don't see the error above & the keyboard/mouse work.

**AdamW** · #10 26th November 2009, 09:43 PM

yeah, that's the slightly different bug which isn't exactly like the case described in the common bugs (note the 'most cases' weasel words - your case is the exception). It should be fixed with a newer kernel from Koji. We're up to 151 now. http://koji.fedoraproject.org/koji/b...buildID=143154

jkissane · #11 27th November 2009, 09:52 AM

Quote:

Originally Posted by AdamW

yeah, that's the slightly different bug which isn't exactly like the case described in the common bugs (note the 'most cases' weasel words - your case is the exception). It should be fixed with a newer kernel from Koji. We're up to 151 now. http://koji.fedoraproject.org/koji/b...buildID=143154

Thanks for the update, we're testing F12 for a few weeks before it will be given to any users so guess the newer kernel will arrive at some stage before then. Now that my kickstart script has been debugged, I don't mind if the keyboard/mouse don't work while the PC is building

**AdamW** · #12 27th November 2009, 08:31 PM

you should always be able to use the 'intel_iommu=soft' parameter as a workaround until you can get the updated kernel installed, anyway.

jkissane · #13 2nd December 2009, 09:39 AM

The new kernel (2.6.31.6-145) recently pushed via the updates fixes the problem it looks like.

**AdamW** · #14 2nd December 2009, 07:47 PM

yes, it should fix most cases.