On Sat, 4 Aug 2001, Gordon Tetlow wrote:
> Sure enough, that fixed the kernel panic, but here's the next odd piece,
> my hard drive wasn't showing up! I have a rather standard Adaptec AHA-2940
> dmesg reports that ahc0 is there. The lines from the dmesg are (hand
> typed):
>
> ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0x5000-0x50ff mem 0x50000000-0x50000fff
>irq 15 at device 15.0 on pci0
> device_probe_and_attach: ahc0 attach returned 12
>
> errno.h says ENOMEM is 12, so it seems that something in the ahc driver is
> unable to allocate memory. Dunno where or why, but something is fouling
> it up. By contrast 4.3-RELEASE doesn't have any issues (I'll try a recent
> snapshot if that would help). Sorry I can't help out any more, but the
> debugging tools in the installation disks seem to lacking
> (understandably).
Okay, I tried with a 4.4-PRERELEASE bootdisk that was available on
current.jp.freebsd.org and dmesg came up with the following:
ahc0: <Adaptec 2940 Ultra SCSI adapter> port 0x5000-0x50ff mem 0x50000000-0x50000fff
irq 15 at device 15.0 on pci0
aic7880: Wide Channel A, SCSI Id=7, 16/255 SCBs
Since -stable and -current are using the exact same driver, there is
something more subtle (and sinister?) going on that I can't figure out. At
this point, I'm throwing my hands up in the air unless someone can give me
a better idea as to what the possible problem could be. I'd really like to
try -current on this box as it's a dual proc PPro 200.
Thanks,
-gordon
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
