From owner-freebsd-questions@FreeBSD.ORG Mon Sep 6 04:26:37 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A004316A4CE for ; Mon, 6 Sep 2004 04:26:37 +0000 (GMT) Received: from ms-smtp-03-eri0.southeast.rr.com (ms-smtp-03-lbl.southeast.rr.com [24.25.9.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1004B43D45 for ; Mon, 6 Sep 2004 04:26:37 +0000 (GMT) (envelope-from jason@ec.rr.com) Received: from [192.168.1.101] (cpe-065-184-172-100.ec.rr.com [65.184.172.100])i864QYiA025674 for ; Mon, 6 Sep 2004 00:26:35 -0400 (EDT) Message-ID: <413BE6FF.7000602@ec.rr.com> Date: Mon, 06 Sep 2004 00:26:39 -0400 From: jason User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040808) X-Accept-Language: en-us, en MIME-Version: 1.0 To: FreeBSD - questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: R200 Microcode detection not correct? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Sep 2004 04:26:37 -0000 I have had problems with getting dri working in the past, and still do, so I started going through code for my video card and related stuff. I found that tracking current caused the line about loading the r200 microcode for my radeon driver to go and come in my dmesg. Right now I have 5.3beta3, I plan to stay with 5.3 release for a while, and the line is missing. I don't beleive I have ever been able to run with dri loaded on my nforce 2 board and a radeon 8500. But now I can use agp instead of pci mode and run xorg. If I load dri with agp my system now gets to the wm stage and my monitor's osd tells me it has switched to 1280x1024@85hz. I get a black screen with some colors at the top and the mouse stays functionail but my keyboard seems to die. I check very thoroughly and there was no Xorg.0.log made for the run when dri was loaded. I only checked for the long once and crashed it by loading dri twice. I'll try to get a log if it is needed. The power button is set to shutdown with acpi on, it works half the time. Maybe this was responcable for me not finding a long of the crash? My question is could this be related to the wrong microcode being loaded? I know I have a r200, its even in the Xorg.0.log and pciconf that I have a r200. Is there anyone that has experince on this that could give me a hint? Should I make a pr for this? Lines 672-706 from /usr/src/sys/dev/drm/radeon_cp.c /* ================================================================ * CP control, initialization */ /* Load the microcode for the CP */ static void radeon_cp_load_microcode( drm_radeon_private_t *dev_priv ) { int i; DRM_DEBUG( "\n" ); radeon_do_wait_for_idle( dev_priv ); RADEON_WRITE( RADEON_CP_ME_RAM_ADDR, 0 ); if (dev_priv->is_r200) { DRM_INFO("Loading R200 Microcode\n"); for ( i = 0 ; i < 256 ; i++ ) { RADEON_WRITE( RADEON_CP_ME_RAM_DATAH, R200_cp_microcode[i][1] ); RADEON_WRITE( RADEON_CP_ME_RAM_DATAL, R200_cp_microcode[i][0] ); } } else { for ( i = 0 ; i < 256 ; i++ ) { RADEON_WRITE( RADEON_CP_ME_RAM_DATAH, radeon_cp_microcode[i][1] ); RADEON_WRITE( RADEON_CP_ME_RAM_DATAL, radeon_cp_microcode[i][0] ); } } }