All,
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
Regards,
Peter
Peter Kitchener wrote:
All,
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
Seagate and Silicon Image are a not very well known disaster combination due to unclear specificitions which led to varying implementations.
The only idea possible is get another card or another brand of disk.
Feizhou wrote:
Peter Kitchener wrote:
All,
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
Seagate and Silicon Image are a not very well known disaster combination due to unclear specificitions which led to varying implementations.
The only idea possible is get another card or another brand of disk.
I ran into somewhat the same problem with an install, and got the same type of irq 11 message, which happened to be for that machine, a USB hub. If I recall right, in order to get the thing to install, I had to use the noacpi and a few other commands, but once I figured out what was killing things, the install process went ahead. Realize this is probably not much help, but I wouldn't toss the disk just yet. There has to be something that can be done to get it installed.
Sam Drinkard wrote:
Feizhou wrote:
Peter Kitchener wrote:
All,
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
Seagate and Silicon Image are a not very well known disaster combination due to unclear specificitions which led to varying implementations.
The only idea possible is get another card or another brand of disk.
I ran into somewhat the same problem with an install, and got the same type of irq 11 message, which happened to be for that machine, a USB hub. If I recall right, in order to get the thing to install, I had to use the noacpi and a few other commands, but once I figured out what was killing things, the install process went ahead. Realize this is probably not much help, but I wouldn't toss the disk just yet. There has to be something that can be done to get it installed.
Well, for some a bios update would make their Silicon Image play nice with Seagate disks but then there are also reports of Silicon Image + Seagate NCQ having an entirely different problem. This is with them being 'blacklisted' by the driver. (blacklisted as in work around the problem)
On Monday 12 December 2005 19:35, Peter Kitchener wrote:
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
I have seen the exact same error (on IRQ 10) with a Maxtor SATA drive on a Silicon Image controller. Let's see: 00:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 01) Subsystem: Silicon Image, Inc. SiI 3112 SATARaid Controller Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 10 I/O ports at 9000 [size=8] I/O ports at 9400 [size=4] I/O ports at 9800 [size=8] I/O ports at 9c00 [size=4] I/O ports at a000 [size=16] Memory at ee180000 (32-bit, non-prefetchable) [size=512] Capabilities: [60] Power Management version 2
Motherboard is a VIA KT400, Soyo DRAGON Platinum IIRC.
Everything is OK until I put a SATA drive on the controller, and then it won't boot. Machine is running right now just fine, using PATA drives.
Lamar Owen wrote:
On Monday 12 December 2005 19:35, Peter Kitchener wrote:
I have a problem with a new Seagate hard disk. The problem occurs when i go to install CentOS, i insert the cd and start the boot up process, when it gets to the section where it detects the hard disks, the driver is seems crashes, the message it produces complains about no one caring about a interrupt on IRQ11. The hard disk is a Seagate 200GB 8MB SATA150 NCQ drive, on a SilliconImage 3112 PCI adapter card. Does anyone have any ideas?
I have seen the exact same error (on IRQ 10) with a Maxtor SATA drive on a Silicon Image controller. Let's see: 00:0b.0 RAID bus controller: Silicon Image, Inc. SiI 3112 [SATALink/SATARaid] Serial ATA Controller (rev 01) Subsystem: Silicon Image, Inc. SiI 3112 SATARaid Controller Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 10 I/O ports at 9000 [size=8] I/O ports at 9400 [size=4] I/O ports at 9800 [size=8] I/O ports at 9c00 [size=4] I/O ports at a000 [size=16] Memory at ee180000 (32-bit, non-prefetchable) [size=512] Capabilities: [60] Power Management version 2
Motherboard is a VIA KT400, Soyo DRAGON Platinum IIRC.
Tsk, tsk. Same old VIA. I have the exact same motherboard and I cannot use my DC10 capture card due to VIA's horrible latency problems.
Everything is OK until I put a SATA drive on the controller, and then it won't boot. Machine is running right now just fine, using PATA drives.
Running fine until you try something that requires low latency.
So do we now add if motherboard = VIA, keep Silicon Image card and Seagate driver, change motherboard? Sigh.
-
Feizhou -
Lamar Owen -
Peter Kitchener -
Sam Drinkard