it is more than likley something in the bios...
if not change it around slots...
as my scsi card conflicted with my network... scsi worked fine...
network appeared to... remove scsi... network works fine... only
happened in 2.4 series... which is wierd...
is it something to do with acpi?
Ben Donohue wrote:
> hi,
> maybe not much help but have you tried simplifying the problem?
> boot up with just the scsi card in only. then if no errors, just add one device,
>then another etc.
> any other cards in the pc that don't need to be there, network card etc that might
>be conflicting?
> also try another slot for the scsi card.
> set the bios in pci settings to auto for all and let pci find and assign settings.
>if not then manually
> assign settings.
> i've noticed with a 2.2 kernal and a aha1520 card that what adaptec said was the
>irq, dma, was not really.
> strange. then i changed it and the kernal found the card after a modprobe and away
>she went. anyway HTH.
> ben
>
> David Fisher wrote:
>
>
>> Evenin' all,
>>
>> I have been bothered for some time with an error message I get upon
>> bootup with 2.4.x kernels. I quote:
>>
>> Mar 14 20:59:19 colossus kernel: SCSI subsystem driver Revision: 1.00
>> Mar 14 20:59:19 colossus kernel: PCI: Found IRQ 5 for device 00:0a.0
>> Mar 14 20:59:19 colossus kernel: IRQ routing conflict in pirq table for device
>00:0a.0
>> Mar 14 20:59:19 colossus kernel: (scsi0) <Adaptec AHA-294X Ultra2 SCSI host
>adapter> found at PCI 0/10/0
>>
>> Now I have been getting heaps of problems on the SCSI bus - can anyone
>> tell me what I've got here and what I can do about it? It it's RTFM
>> then just tell me where the FM is and I'll go and R it.
>>
>> --
>> David
Daniel Finn
--> Email = [EMAIL PROTECTED]
--> ICQ = 4886934
--> Phone = +61 (403) 364 302
Nepean Micro Computers - www.nmc.com.au
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
