Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270458AbTHGUBn (ORCPT ); Thu, 7 Aug 2003 16:01:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270461AbTHGUBn (ORCPT ); Thu, 7 Aug 2003 16:01:43 -0400 Received: from public1-brig1-3-cust85.brig.broadband.ntl.com ([80.0.159.85]:44720 "EHLO ppg_penguin.kenmoffat.uklinux.net") by vger.kernel.org with ESMTP id S270458AbTHGUBm (ORCPT ); Thu, 7 Aug 2003 16:01:42 -0400 Date: Thu, 7 Aug 2003 21:01:40 +0100 (BST) From: Ken Moffat To: marcelo@conectiva.com.br Cc: linux-kernel@vger.kernel.org Subject: 2.4.22-rc1 breaks dri in X-4.3.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 935 Lines: 30 Apologies if this is a known bug, I'm slightly lost following the list, and the only bug I can see mentioned seems to be in Alan's tree. I've just built 2.4.22-rc1 for my PIII (via chipset, radeon 7500), and rebuilt radeon.o from the X 4.3 release. This combination worked with 2.4.22-pre7 (although with occasional X lock-ups). In X's log I can see that the radeon module fails to open /dev/dri/card0 (no such device) and therefore the module load fails. From dmesg I can see that agpgart detects the chipset and reports the aperture, but there are zero [drm] messages following. My .config shows CONFIG_DRM=y CONFIG_DRM_NEW=y CONFIG_DRM_RADEON=m Ken -- Peace, love, linux - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/