PCI IDE controller card IRQ issue - Tech Support Forums

#43 fan · May 28th, 2008, 11:36 AM

In order to try and fix my server, I've gotten a PCI controller card. There is an issue with it, however.
When I plug in my IDE cable, it somehow loses the IRQ it was assigned. Therefore, I can't boot from it.
Without the IDE cable, it apparently has an IRQ, and should work fine.
Any ideas?

Steve R Jones · May 28th, 2008, 12:11 PM

Is there a setting in the BIOS - Boot Sequence - to boot from other devices?

#43 fan · May 28th, 2008, 07:52 PM

I could boot from the IDE, but the drive doesn't seem to be recognized.
When I used WD tools, there are no drives, apparently, in the IDE, when in fact there are 2: a DVD and a Hard drive. This is on the IDE channel that is on the motherboard, which seems to be the only one that works somewhat decently.
I can not access the PCI IDE card, either. In the BIOS, it seems to be unable to set an IRQ, it is not disabled, it simply can't be set.
Additionally, on the boot up, it says that the PCI device is a Type 2 Header, and therefore can't be set up by the BIOS, it has to be set up by the OS or driver.
So, anybody have an idea of how I can fix this server? Any ideas on how to get the IDE channel to start working?

BipolarBill · May 29th, 2008, 06:51 PM

Set BIOS boot order to put "SCSI" (your PCI adapter is in that category) or "Removable drive" ahead of IDE.

When you boot with this card it, you should see the BIOS for the adapter card right after the motherboard BIOS. If you don't, it isn't working properly. Try another PCI slot. If you have no more, try another brand of adapter.

Keep in mind that there is only so much memory for booting devices in the BIOS spec. If you have onboard video and a video card, they may be bumping the adapter card off. Remove any added video cards and limit bootable adapters.

#43 fan · May 29th, 2008, 07:01 PM

I was able to get the computer working, which I put in the other thread (CD drive not working).
I do have a different issue now; the hard drive's firmware isn't ready to be reinitialized, and the PC won't boot.
What's up with that?
Edit- It simply needs to be shutdown for a while.

BipolarBill · May 29th, 2008, 07:11 PM

So we're good?

#43 fan · May 29th, 2008, 07:20 PM

I think (and hope) so.
PC BSD did lock up, or at least KDE did, on the boot that was successful.
It seemed like the menu bar was the culprit.