Bug 152486

Summary: can't install beta4 on Adaptec aic7899 Ultra160 SCSI adapter
Product: [openSUSE] SUSE Linux 10.1 Reporter: Forgotten User WWATXcldtK <forgotten_WWATXcldtK>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED FIXED QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Beta 4   
Target Milestone: ---   
Hardware: x86   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User WWATXcldtK 2006-02-21 14:19:48 UTC
Boot beta4 with acpi=off - installation ends because can't see disks, but devices (adapter and disks) are recognized, aic7xxx module is loaded. When after installation ends manualy load module, than say that module already is there. But network installation don't work too :(
Comment 1 Michael Gross 2006-02-21 15:26:33 UTC
OK let's start from the beginning.
Is it necesarry for you to install with ACPI=off? What does happen if you perform a normal installation?
Comment 2 Forgotten User WWATXcldtK 2006-02-21 15:53:50 UTC
(In reply to comment #1)
> OK let's start from the beginning.
> Is it necesarry for you to install with ACPI=off? What does happen if you
> perform a normal installation?
> 

if acpi isn't off than scsi adapter can't be initialized or something -
ACPI Warning (pci_lin-0386): PCI Interrupt Link [LN04] disabled and referenced, BIOS bug [20060127]
ACPI Warning (pci_lin-0407): PCI Interrupt Link [LN04] BIOS reported IRQ 0, using IRQ 9 [20060127]

than

0:0:0: Attempting to queue an ABORT message ... bla-la-la

I myself installed on than box suse 9.3 and 10.0, and when installed always switched off ACPI, after installation than wasn't nessesary.
Comment 3 Michael Gross 2006-02-21 17:11:31 UTC
Try booting with a combination of pci=routeirq and pci=noacpi, does this help anything?
Comment 4 Forgotten User WWATXcldtK 2006-02-22 08:37:25 UTC
Thx, that helped.
Comment 5 Michael Gross 2006-02-22 09:23:59 UTC
OK then this is most likely caused by a buggy BIOS. I think we can consider this resolved then ;) Maby a BIOS-update also does the trick.