Date: Mon, 18 May 2009 11:33:52 -0700 From: "David Roberts" <dtrobert@pacbell.net> To: "'Kent Stewart'" <kstewart@owt.com>, <freebsd-questions@freebsd.org> Subject: RE: Disappointed with version 6.0 Message-ID: <002901c9d7e7$3214f020$963ed060$@net> In-Reply-To: <200905181043.42597.kstewart@owt.com> References: <000501c9d7d9$89fd8c60$9df8a520$@net> <200905181043.42597.kstewart@owt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm, I've unplugged the PC every time I played with the cables (changing positions, etc) but never had it work. It's an older Compaq Deskpro EN. Maybe time for to update my hardware/PC with something more recent. Thanks -----Original Message----- From: Kent Stewart [mailto:kstewart@owt.com] Sent: Monday, May 18, 2009 10:44 AM To: freebsd-questions@freebsd.org Cc: David Roberts Subject: Re: Disappointed with version 6.0 On Monday 18 May 2009 09:56:07 am David Roberts wrote: > Hi, I was reading this thread as the problem I'm having seems quite > similar, and with version 7.2, although I had the same behavior with 6.3 as > well. > < > > ad0: 9541MB <Seagate ST310212A 3.39> at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB <MAXTOR 6L080L4 A93.0500> at ata1-master UDMA33ad0: 9541MB > <Seagate ST310212A 3.39> at ata0-master UDMA66 > > ad2: DMA limited to UDMA33, controller found non-ATA66 cable > > ad2: 76345MB <MAXTOR 6L080L4 A93.0500> at ata1-master UDMA33 > > > > Any ideas? > I had a motherboard that would do this. If I killed power to the system for ~15 seconds, it would go back to accepting everything. What I though was wrong was the controller developed a problem and if I cut the power to the system such that the system voltages bled off, it would go back to accepting ata66 cables. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901c9d7e7$3214f020$963ed060$>