Date: 11 Dec 95 14:25:21 EST From: Dave Franco <100075.2767@compuserve.com> To: Anyone <bugs@freebsd.org> Subject: Assistance with FreeBSD and aha1542 Message-ID: <951211192521_100075.2767_EHK107-1@CompuServe.COM>
next in thread | raw e-mail | index | archive | help
Help Anyone, I have posted the following problem in less detail in questions@freeBSD and have had a few suggestions that mostly centre around checking IRQ's and DMA's these have been tried in many configurations but to no avail. I cannot get the system to initialise to installation at all. During the boot up sequence the system performs the various memory and device sniffs. It then locates the aha and produces the following lines (without line numbers) 1. aha0: reading board settings dma=5, int=11 (bus speed defaulted) 2. aha0: aha_cmd, cmd/data port full 3. aha0: at 0x330 - 0x333 irq 11 drq 4 on isa 4. aha0: waiting for SCSI devices to settle 5. probe 0(aha0:0:0), timed out 6. adapter not taking comands . . frozen ?! 7. 8. probe 0(aha0:0:0), timed out 9. adapter not taking comands . . frozen ?! 10. Debug(AHA-1542) 11. AGAIN 12. aha0: MBO not free it then repeats lines 5 to 12 as long as it is left on. My initial suspicion was a hardware interrupt conflict but I have been through these several times. The same boot disk works on a configuration without a SCSI device upto setting up the drive but unable to access the drive because it is on a sound CDROM when using an IDE disk. The configuration I am trying to now make it work in is Pentium 90, 16 Mb RAM ISA VGA adapter - 512Kb RAM AHA 1542 ISA SCSI host adapter Seagate 2Gb barracuda HDD on the AHA - device 0 Matshita CDRom on the AHA device 3 ( also tried 1) TEAC 1.44 running on the AHA 1542 NO PCI devices, all pci interrupts disabled NO VL bus devices For test purposes I have put a 60Mb partition at the front of the disk for dos and have installed dos drivers for the drive and CD and this is able to work. As soon as I boot the system with the disk 1 of 2 created from the CD using rawwrite it initialises and then eventually arrives at the situation described above. If anyone has more suggestions, or someone who knows where the error is generated and can explain what it is looking for at this point so that I can resolve it I would be most appreciative. Anyone who has already sent a suggestion thank you very much for your ideas, sorry they didn't work yet. Regards Dave Franco
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?951211192521_100075.2767_EHK107-1>