On Thu, 2003-03-13 at 05:48, Tom Allison wrote:
> [EMAIL PROTECTED] wrote:
> > On Wed, 12 Mar 2003 17:29:05 -0500
> > Tom Allison <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I've been runnign this PC for about a year now.
> >>I recently upgraded from 2.4.18 to 2.4.20.
> >>And this is the thanks I get.
On Thu, 13 Mar 2003 05:48:01 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Wed, 12 Mar 2003 17:29:05 -0500
> > Tom Allison <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I've been runnign this PC for about a year now.
> >>I recently upgraded from 2.4.18 to 2.4.20.
> >>An
[EMAIL PROTECTED] wrote:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
---
I suggest you changing this drive before it's too late.
I had the same problem and 5 days after the drive crashes.
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any
Hi
I had a similiar problem with a WD 30gb drive. Used WD diag utils and it
seemed to solve the problem. I would agree on backup, but you may still
get some live out of the drive.
Regards
Tinus
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
> I've been runnign this PC for about a year now.
> I
On Wed, 2003-03-12 at 17:29, Tom Allison wrote:
> I've been runnign this PC for about a year now.
> I recently upgraded from 2.4.18 to 2.4.20.
> And this is the thanks I get
> Any suggestions? It seems to work.
>
> Mar 12 12:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> I've been runnign this PC for about a year now.
> I recently upgraded from 2.4.18 to 2.4.20.
> And this is the thanks I get
> Any suggestions? It seems to work.
> --
On Sat, 2003-01-18 at 23:42, Pigeon wrote:
> On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
> > I have been running the same woody box for more then 2 years, and I
> > just got the following message:
> >
> > hda: timeout waiting for DMA
> > hda: irq timeout: status=0x58 { Dri
On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
> I have been running the same woody box for more then 2 years, and I
> just got the following message:
>
> hda: timeout waiting for DMA
> hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: timeout waiti
hi ya mathew..
think you should swap your cable for an 18" cable..
and verify the chipset on your mb against the kernel
( might need to install the module for that chipset you're using )
have fun
alvin
- uptime will be sacrificed one way or other...
- the question is do you drag data do
On Fri, Jan 17, 2003 at 12:13:43PM -0800, Alvin Oga wrote:
> - what is the length of your ide cables ??
Standard, I would assume 24"
> - which drive is the "Master" ?? which ide connector is the Master ?
> - is the drive set to cable select or "fixed Master"
This is the only drive on t
hi ya matthew
- what is the length of your ide cables ??
- which drive is the "Master" ?? which ide connector is the Master ?
- is the drive set to cable select or "fixed Master"
- i assume you have the new 80-conductor cables
- power the machine off... wiggle the cables... pull it off an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 17 January 2003 16:06, Matthew Daubenspeck wrote:
> I have been running the same woody box for more then 2 years, and I
> just got the following message:
>
> hda: timeout waiting for DMA
> hda: irq timeout: status=0x58 { DriveReady SeekComple
13 matches
Mail list logo
