sil3112 SATA and libata.o boot problem on SuSE 9.0...

sil3112 SATA and libata.o boot problem on SuSE 9.0...

Post by Asko Telin » Fri, 12 Dec 2003 06:29:14

i all.

I installed SuSE 9.0 Pro recenlty and i got the following problem:
I have the Seagate ST3160023AS HD installed but it runs
in PIO mode (extremely slow) with original kernel.
So, i downloaded the latest stable kernel sources from
(2.4.23). After that i got UDMA on but now the PC hangs
occasionally, especially when copying large files. I tried
all UDMA modes from 2 to 6 like:
hdparm -d1 -X66 -c3 /dev/hde, but no help.
When the PC hangs, only Reset-button helps, but, on StartUp
automatic disk checking is forced and PC hangs during the check
again. I only be able to complete disk check with original kernel.
I found precompiled drivers for Sil3112A, but these are only
for 8.0, 8.1 and 8.2 SuSE versions. On redhat 9.0 they worked
just fine.

Then i read from that with libata.o, it could
be stable (and fast) enough.
So, I patched the latest stable kernel (2.4.23) with libata latest patch
(dated 01-dec-2003) and compiled new kernel. Then applied kernel
boot parameter "doataraid noraid" but this didn't work at all!!!!
ataraid.o silraid.o(or was it something else...) module was used by SuSE and
libata was not used at all (lsmod told that usage = 0).

Then i included modules "libata" and "sata_sil" to the kernel
boot parameters (MODULES_LOADED_ON_BOOT) and initrd parameters
(INITRD_MODULES), compiled the kernel again "without" those drivers,
that suse used, and made new initrd.

After that libata and sata_sil was loaded at boot and the SATA disk
found but boot failed to kernel panic. Then i tried to append
kernel parameter "root=/dev/sda8/" and it booted to somekind of rescue
mode (disk was read-only).

If anyone knows ho to proceed PLZ tell us !!!

Here is the dmesg from boot (when i appended boot parameter):

000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000003fff0000 (usable)
BIOS-e820: 000000003fff0000 - 000000003fff3000 (ACPI NVS)
BIOS-e820: 000000003fff3000 - 0000000040000000 (ACPI data)
BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
ACPI: have wakeup address 0xc0001000
On node 0 totalpages: 262128
zone(0): 4096 pages.
zone(1): 225280 pages.
zone(2): 32752 pages.
ACPI: RSDP (v000 Nvidia ) @ 0x000f6b60
ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3000
ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff3040
ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3fff79c0
ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000d) @ 0x00000000
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 Pentium(tm) Pro APIC version 16
ACPI: LAPIC_NMI (acpi_id[0x00] polarity[0x1] trigger[0x1] lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] global_irq_base[0x0])
IOAPIC[0]: Assigned apic_id 2
IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, IRQ 0-23
ACPI: INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0]
ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x9] polarity[0x1]
Using ACPI (MADT) for SMP configuration information
Kernel command line: root=/dev/sda8 vga=0x31a hdg=noprobe desktop
hda=ide-scsi hdalun=0 splash=silent doataraid noraid

1. After update from SuSE 9.0->9.1 the boot process stops with "GRUB"

2. Getting Fortran program compiled under SuSE 8.0 to run under SuSE 9.0

Fortran program compiled on SuSE 8.0 gives this error message when it's
run on the SuSE 9.0 platform:

forrtl: info: Fortran error message number is 174.
forrtl: warning: Could not open message catalog:
forrtl: info: Check environment variable NLSPATH and protection of

On the SuSE 8.0 platform:
cd /usr/lib is a link to

On the SuSE 9.0 platform:
cd /usr/lib
ll ifcore*
ls: No match.

Is it OK to define a link in /usr/lib on SuSE 9.0 that says -> /opt/intel/fc/9.0/lib/

The two files have slightly different sizes and are in
directories that follow a slightly different naming convention.

How else can I get the 8.0 program to run under 9.0? (I'd prefer not to
recompile on 9.0).


3. Suse 9.0 didn't work - trying again (Mandrake or Suse?)

4. [SATA] Disabling irq: #11 with silicon image 3112 sata controller with sata_sil and libata (NO RAID)

5. Su in SuSE 9.0 ( reposted to alt.os.linux.suse )

6. [sata] new libata-dev-2.6 queue created (AHCI, SATA bridges)

7. [SATA] non-PCI SATA devices and libata

8. Norton Ghost 9.0 Can't Find My SATA Drives When Booted From It's Recovery DVD.

9. Norton Ghost 9.0 Can't Find My SATA Drives When Booted From It's R

10. Norton Ghost 9.0 Can't Find My SATA Drives When Booted From It

11. What's the correllation between File I/O's and Disk I/O's

12. IRQ sharing, conflict, frozen after POST, SIL3112 SATA

13. postfix + cyrus (SuSE 9.0) - final problem

14. Sound problem KDE 3.1.2 -> 3.2 migration on Suse 9.0

15. SATA problems, problems, problem - Okay, so I have solved my SATA problems . . .