Re: missing pcib?

workdamyou@xxxxxxxx wrote:
Greetings,

I've been attempting to get FBSD 6.1(R)elease (G)eneric to work for
awhile now.

Essentially, I have a Symbios 53C896 on the motherboard of an
Intergraph TDZ2000 GT1. The problem being that the bridge that
connects the '896 controller is skipped somehow.

pcib0, pcib1, then pcib3 are all that comes up. Of course, the '896 is
on the pcib2. :/

FBSD 4.11 (RG) can see the controller, and 5.0(RG) doesn't. I've
*attempted* to see what changed between the two, however, not only has
the source code changed, the source trees changed as well between the
two versions. (Thus, I am lost!)

** What's the general rule about contacting the source coder within
the FreeBSD community? **
(Stefan Esser, in this case..)

Your SCSI controller is driven by the sym driver under FreeBSD-4.
sym0: <896> port 0xf000-0xf0ff mem
0xdffec000-0xdffedfff,0xdffef800-0xdffefbff irq 10 at device 1.0 on
pci2
sym0: Symbios NVRAM, ID 7, Fast-40, LVD, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
sym0: handling phase mismatch from SCRIPTS.
sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/a0/01/00/24
sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 07/4e/80/01/08/24
sym0: SCAN FOR LUNS disabled for targets 0 1.
sym0: Delay (GEN=11): 234 msec, 37984 KHz
sym0: Delay (GEN=11): 264 msec, 33667 KHz
sym0: Delay (GEN=11): 265 msec, 33540 KHz
sym0: enabling clock multiplier
sym0: Downloading SCSI SCRIPTS.

and similarly for sym1 and sym2. This is compatible with the model Symbios
53C896 for sym0 and sym1 while sym2 is a 560. The 3 are on irq10.
sym0 and sym1 are on pcib1, sym2 is on pcib2.

I have a 875 which has always worked well under FreeBSD-3,4,5, and 6. Here is
the relevant part of dmesg.
sym0: <875> port 0xb800-0xb8ff mem 0xec800000-0xec8000ff,0xec000000-0xec000fffi
rq 23 at device 11.0 on pci2
sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking
sym0: [GIANT-LOCKED]

The original author of the driver is Gerard Roudier <groudier@xxxxxxx>
you can try to contact him. I don't think that Stefan Esser is to be
contacted. The 896 is certainly mentioned in the FreeBSD-6 sources i have:
the README starts by:
* Device driver optimized for the Symbios/LSI 53C896/53C895A/53C1010
* PCI-SCSI controllers.

As you are noting it is probably not the Symbios chip which is not recognized,
but the PCI bus pcib2 which is not explored. The dmesg on FreeBSD-4 shows that
pcib0, pcib1, pcib3 are on ServerWorks bridges and are recognized as such.
While pcib2 is on an unnamed bridge
pcib2: <Host to PCI bridge> on motherboard ...
However on FreeBSD-4 sees two 896 chips, one on pcib1, and a 860 on pcib2.
The bus enumeration is not the same on FreeBSD-5 and 6, it is based on acpi,
so you cannot directly compare the numbering. Anyways the FreeBSD-6 message
mentions pcib0, pcib1, and pcib3, but not pcib2. The 860 is seen on pcib3.
Hence something is seen since the enumeration skips pcib2, but is not
recognized as such.

I don't see acpi messages in your FreeBSD-6 dmesg. Is it disabled? For me
dmesg starts by:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 1
ioapic0 <Version 2.0> irqs 0-23 on motherboard
acpi0: <ASUS P4PE> on motherboard
acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 22
acpi0: Power Button (fixed)

If acpi is disabled you can expect bus enumeration problems with FreeBSD-6
since it is mainly designed to enumerate hardware using acpi. It would
probably better to upgrade the BIOS of the machine and try to use an acpi
enabled boot. Note that some old BIOSES are blacklisted by the acpi code, and
acpi is not used even without your intervention. If your problem is not solved
you should post on freebsd-stable@xxxxxxxxxxx, here are people who know the
acpi stuff, and the bus enumeration problem like John Baldwin.




as under FreeBSD-4.



--
Michel Talon
.

Quantcast