ianrickey: excuse me, I should have specified that post #14 was directed at lucky_luuk ... my bad.

I tired the acpi=off and and added the option to use the IRQ from the BIOS, but this did not help getting it to work, but gives a different error (see below). And I do agree that it is not a good thing to shut off the ACPI, but it would help if I could find how to get the USB working at least for a short wile.

Simon: I looked at the DSDT but there is non for my PC (Averatec C3500). Any suggestions?

The result of dmesg is (with different the modifications):
shpchp: acpi_shpchprm:get_device PCI ROOT HID fail=0x1001
PCI: Enabling device 0000:00:03.2 (0000 -> 0002)
PCI: No IRQ known for interrupt pin D of device 0000:00:03.2.
ehci_hcd 0000:00:03.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:03.2 setup!ehci_hcd 0000:00:03.2: init 0000:00:03.2 fail, -19
ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
PCI: Enabling device 0000:00:03.0 (0000 -> 0002)
PCI: No IRQ known for interrupt pin A of device 0000:00:03.0.
ohci_hcd 0000:00:03.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:03.0 setup!ohci_hcd 0000:00:03.0: init 0000:00:03.0 fail, -19
PCI: Enabling device 0000:00:03.1 (0000 -> 0002)
PCI: No IRQ known for interrupt pin B of device 0000:00:03.1.
ohci_hcd 0000:00:03.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:03.1 setup!ohci_hcd 0000:00:03.1: init 0000:00:03.1 fail, -19

Well, this is kinda intreguing.

How did you check that ACPI was really off as a result of the noacpi option - check /proc/acpi ... does the fan stay on continuously or stay off all the time? Does the battery applet behave differently? (When acpi is switched on, do you have any issues apart from usb?)

Anyway: remove the option to use IRQ from BIOS. Lets just test one "solution" at a time, and make sure ACPI is responsible for this and not something weird. Fixing DSDT is not something you want to have to do.

Normally, the usb drivers are compiled as loadable modules instead of being stuck right in the kernel. (Double check through make xconfig - load your configuration, and make sure you have installed every usb driver you are likely to need...)

There is a very good chance your firmware is buggy anyway.
To check, you need the intel ASL compiler from intel's download site. To compile it, you need gcc, bison, and flex. Flex must be an old version.

With acpi enabled
Look in /proc/acpi, there will be a file called dsdt - copy this to a working directory, say:
cp /proc/acpi/dsdt ~/work/dsdt.dat
... then decompile it:
iasl -d dsdt.dat
... this creates a file called dsdt.dsl, (I think) which you can look at with a text editor. Now compile dsdt.dsl
iasl -at dsdt.aml
... this creates a file called DSDT.aml - but only if all goes well. If you get any errors, then the dsdt is buggy. Warnings are OK though.

What may be better - get an official fedora kernel, and boot from that. If USB still dosn't go, then you can look to your firmware. Otherwise, you missed something on the compile. Of course - it's always possible that the hardware is broken - - -