Re: Nvidia SATA - Seagate SATA Drives

2007-10-10 Thread Jim Gifford
Robert Hancock wrote: Jim Gifford wrote: Robert Hancock wrote: Jim Gifford wrote: Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate Barracuda 250 GB SATA drive. I have replaced this drive three times in the last two weeks due to it failing. Now the only thing in common i

Re: Nvidia SATA - Seagate SATA Drives

2007-10-10 Thread Robert Hancock
Jim Gifford wrote: Robert Hancock wrote: Jim Gifford wrote: Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate Barracuda 250 GB SATA drive. I have replaced this drive three times in the last two weeks due to it failing. Now the only thing in common is the use of a 2.6.22.9

Re: Nvidia SATA - Seagate SATA Drives

2007-10-10 Thread Jim Gifford
Robert Hancock wrote: Jim Gifford wrote: Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate Barracuda 250 GB SATA drive. I have replaced this drive three times in the last two weeks due to it failing. Now the only thing in common is the use of a 2.6.22.9 kernel I built from

Re: Nvidia SATA - Seagate SATA Drives

2007-10-10 Thread Steen Eugen Poulsen
Robert Hancock skrev: > Using "irqpoll" is not a very good workaround, it really is just a > band-aid to get things working. Often this indicates motherboard IRQ > routing issues. You may want to make sure you have the latest BIOS > installed for the board. MSI seems to have problems with the qual

Re: Nvidia SATA - Seagate SATA Drives

2007-10-09 Thread Robert Hancock
Jim Gifford wrote: Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate Barracuda 250 GB SATA drive. I have replaced this drive three times in the last two weeks due to it failing. Now the only thing in common is the use of a 2.6.22.9 kernel I built from scratch, before that I

Nvidia SATA - Seagate SATA Drives

2007-10-09 Thread Jim Gifford
Here's the situation. I have a MSI KN8Neo-f motherboard with a Seagate Barracuda 250 GB SATA drive. I have replaced this drive three times in the last two weeks due to it failing. Now the only thing in common is the use of a 2.6.22.9 kernel I built from scratch, before that I was using 2.6.19 k