On Wed, 25 Sep 2002, Yanek Korff wrote:

>
>  I'm working on a system with an Intel motherboard (SE7500CW2SCSI) - the one
>  that's being discussed in freebsd-smp right now due to SMP problems, panic
>  on boot when SMP is enabled.  That's somewhat beside the point for now...
>
>  What I'd really like to do is get the integrated SCSI controller working
>  with the sym drivers.  LSI chipset listed as LSI Logic* 53C1000 on the Intel
>  website.  Here's a piece of the dmesg:
>
>  sym0: <1010-66> port 0x7000-0x70ff mem
>  0xfc200000-0xfc201fff,0xfc202000-0xfc2023ff irq 11 at devic
>  e 1.0 on pci3
>  sym0: Symbios NVRAM, ID 7, Fast-80, SE, parity checking
>  sym0: open drain IRQ line driver, using on-chip SRAM
>  sym0: using LOAD/STORE-based firmware.
>  sym0: handling phase mismatch from SCRIPTS.
>  CACHE TEST FAILED: script execution failed.
>  start=7c99f4fc, pc=7c99f4fc, end=7c99f51c
>  sym0: CACHE INCORRECTLY CONFIGURED.
>  device_probe_and_attach: sym0 attach returned 6
>
>  There are two onboard NICs on this box and a graphics card using irq11.
>  dmesg | grep "irq 11":
>  sym0: <1010-66> port 0x7000-0x70ff mem
>  0xfc200000-0xfc201fff,0xfc202000-0xfc2023ff irq 11 at device 1.0 on pci3
>  pci4: <ATI Mach64-GR graphics accelerator> at 3.0 irq 11
>  fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0x8400-0x843f mem
>  0xfc300000-0xfc31ffff,0xfc341000-0xfc341fff irq 11 at device 4.0 on pci4
>  fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0x8440-0x847f mem
>  0xfc320000-0xfc33ffff,0xfc342000-0xfc342fff irq 11 at device 5.0 on pci4
>  pci0: <unknown card> (vendor=0x8086, dev=0x2483) at 31.3 irq 11
>
>
>  Also the PCI NIC isn't showing up -at all-  It's likely also trying to use
>  irq11 (it's an XL -- ah... 3com905).
>
>  Any idea what's going on here?  Advice?  Can I manually change the IRQs of
>  any of this stuff to get things going?

Can you manually assigning IRQs in the BIOS setup?

-- 
Juha Saarinen


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message

Reply via email to