Date: Fri, 8 Dec 1995 23:18:41 -0800 (PST) From: Rob Mallory <rmallory@wiley.csusb.edu> To: scsi@FreeBSD.org Cc: se@freefall.FreeBSD.org Subject: ncr[01] conflicts..? Message-ID: <199512090718.XAA08642@wiley.csusb.edu>
next in thread | raw e-mail | index | archive | help
OK, I took the "easy" way out,,throw more hardware at it apporach:) I finaly found (through a tech at symbios) how to successfully get both a ncr825 and 810 in my asus p55tp4xe with 3.07 ncr bios. the tyan 825 had a 3.04 rom, complete with geometry bugs which prevented me from installing slowaris-2.5 and freebsd on the same disk. the tech suggested that the 810 be installed in a lower slot than the 825 so it booted first. the 825, now romless, would 'use' the 3.07 bios which was incarnated by the 810 from the asus bios. it follows that the 810 would have to contain the boot drive. well, this is where it gets fun. the 810 has a 2 way jumper on it that says '2nd'. it does what it implies, and moves its mem-base(?) somewhere else(i guess). see the following boot messages: (chopped up for readability) [conflicting with the 825] Dec 8 21:58:16 kickme /kernel: Probing for devices on the PCI bus: Dec 8 21:58:16 kickme /kernel: chip0 <Intel 82437 (Triton)> rev 1 on pci0:0 Dec 8 21:58:16 kickme /kernel: ncr0 <ncr 53c810 scsi> rev 1 int a irq ?? on pci 0:6 Dec 8 21:58:16 kickme /kernel: pci_map_mem failed: device's memrange 0xff00-0xf fff is incompatible with its bridge's memrange 0x4000000-0xffffffff Dec 8 21:58:16 kickme /kernel: CACHE TEST FAILED: reg dstat-sstat2 readback fff fffff. Dec 8 21:58:16 kickme /kernel: CACHE INCORRECTLY CONFIGURED. Dec 8 21:58:16 kickme /kernel: chip1 <Intel 82371 (Triton)> rev 2 on pci0:7 Dec 8 21:58:16 kickme /kernel: vga0 <VGA-compatible display device> rev 0 int a Dec 8 08:45:56 kickme /kernel: ncr1 <ncr 53c825 wide scsi> rev 2 int a irq 11 o n pci0:11 Dec 8 08:45:56 kickme /kernel: (ncr1:0:0): "TOSHIBA MK537FB 6261" type 0 fixed Dec 8 08:45:57 kickme /kernel: sd0(ncr1:0:0): Direct-Access Dec 8 08:45:57 kickme /kernel: sd0(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) off ...boots off ncr(1), the 825, sd0. [not conflicting boots off ncr1, but of course, the kernel says root on sd0] Dec 8 08:50:37 kickme /kernel: Probing for devices on the PCI bus: Dec 8 08:50:37 kickme /kernel: chip0 <Intel 82437 (Triton)> rev 1 on pci0:0 Dec 8 08:50:37 kickme /kernel: chip1 <Intel 82371 (Triton)> rev 2 on pci0:7 Dec 8 08:50:38 kickme /kernel: ncr0 <ncr 53c825 wide scsi> rev 2 int a irq 11 o Dec 8 08:50:38 kickme /kernel: (ncr0:0:0): "TOSHIBA MK537FB 6261" type 0 fixed Dec 8 08:50:38 kickme /kernel: sd0(ncr0:0:0): Direct-Access ... Dec 8 08:50:40 kickme /kernel: ncr1 <ncr 53c810 scsi> rev 1 int a irq 14 on pci 0:12 Dec 8 08:50:40 kickme /kernel: ncr1 waiting for scsi devices to settle Dec 8 08:50:40 kickme /kernel: (ncr1:0:0): "CONNER CFA540S 13B0" type 0 fixed S Dec 8 08:50:40 kickme /kernel: sd4(ncr1:0:0): Direct-Access Dec 8 08:50:40 kickme /kernel: sd4(ncr1:0:0): FAST SCSI-2 100ns (10 Mb/sec) off sd4 is a 2.1R disk which was probed by sdms at boot, and the bootblocks were read, a kernel read, and then tried to switch root to sd0. ... i noticed how they switch posisions when i jumper the '2nd' jumper.. my question is,, Why does the ncr probe look backwards to me? if the 810 is hooked first and booted, and the sd4 kernel is read that device, why does the kernel call the 810 ncr1? ...has anyone else run into this? is there a valid reason for this being default? ...give me a 'FLIP_NCR_PROBE' option flag! :-) Thanks, Rob Mallory [rmallory@csusb.edu]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512090718.XAA08642>