DragonFlyBSD

:New submission from Rumko <rumcic@gmail.com>:
:
:After updating from 1.9.0-PREVIEW (from May ~10th), my RAID controller is n=
:ot
:recognized anymore (I only use it as a normal SCSI controller, since the on=
:board
:controllers are problematic and dfly doesn't support RAID functionality of =
:that
:card).
:
:With the old kernel, it is recognized as:
:ahc0: <Adaptec 398X Ultra SCSI RAID adapter> port 0xa000-0xa0ff mem

A fix will probably not make it into the release but please post
    pciconf -l output with the old kernel AND with the new kernel.

-Matt

ahc0@pci2:4:0: class=0x010000 card=0x78839004 chip=0x83789004 rev=0x01 hdr=0x00

I can't get the pciconf output with the new kernel, because the machine can't
boot (all the drives are on that controller) and the cd-rom is broken (whenever
i close the tray, a few seconds later it opens it again ... the only "spare"
drive is in my workstation which i don't want to disassemble unless its really
really necessary).

http://www.rumko.net/dragonfly/boot
I put the pictures of the verbose boot process in that directory.

:Rumko <rumcic@gmail.com> added the comment:
:
:ahc0@pci2:4:0: class=3D0x010000 card=3D0x78839004 chip=3D0x83789004 rev=3D=
:0x01 hdr=3D0x00
:
:I can't get the pciconf output with the new kernel, because the machine can=
:'t
:boot (all the drives are on that controller) and the cd-rom is broken (when=
:ever
:i close the tray, a few seconds later it opens it again ... the only "spare"
:drive is in my workstation which i don't want to disassemble unless its rea=
:lly
:really necessary).

I think I found the issue.  For some reason AHC_PCI_CONFIG needs to be
    defined and it isn't.  I am going to commit a fix right (i.e. remove
    the need to define AHC_PCI_CONFIG).

-Matt

That was it, this bug has been fixed, thank you :)