From owner-freebsd-mobile Tue Aug 4 07:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07231 for freebsd-mobile-outgoing; Tue, 4 Aug 1998 07:28:50 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles210.castles.com [208.214.165.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07115; Tue, 4 Aug 1998 07:28:26 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id HAA00456; Tue, 4 Aug 1998 07:24:16 -0700 (PDT) Message-Id: <199808041424.HAA00456@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brian Somers cc: Randy Philipp , Doug White , Greg Lehey , freebsd-mobile@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Neomagic chipset - is it a hardware problem ? In-reply-to: Your message of "Tue, 04 Aug 1998 08:04:28 BST." <199808040704.IAA25263@awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Aug 1998 07:24:15 -0700 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've found out more about this flickering problem.... it only occurs > when the laptop is physically warm - the warmer, the more flickering. > If the machine sleeps for ~15 minutes, it'll wake up with a perfect > picture and that picture will start to deteriorate with the building > heat. If I switch the display off for 15 minutes it makes no > difference. > > This is all under load. If the machine is idle it lasts a lot > longer (the fan is more effective I guess....) > > Has anyone else seen this problem ? I'm pretty much convinced that > it's a hardware problem now, so I'll probably return the machine > (second time) nearer the end of the week. I've seen similar symptoms on a Toshiba using the C&T 65555. The part would misbehave so badly that the X server would crash. Windows worked OK on it though; my hypothesis was just that the X driver wasn't doing whatever power management stuff the Windows driver was, and so the chip was overheating. I could be way off on that though; I know nothing about the C&T architecture. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message