From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1DqOpX-0002xG-BE for garchives@archives.gentoo.org; Thu, 07 Jul 2005 05:21:47 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j675JwW1001477; Thu, 7 Jul 2005 05:19:58 GMT Received: from smtp100.mail.sc5.yahoo.com (smtp100.mail.sc5.yahoo.com [216.136.174.138]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j675GNWg003611 for ; Thu, 7 Jul 2005 05:16:24 GMT Received: (qmail 79859 invoked from network); 7 Jul 2005 05:17:22 -0000 Received: from unknown (HELO ?192.168.50.105?) (richard?j?fish@212.180.33.26 with plain) by smtp100.mail.sc5.yahoo.com with SMTP; 7 Jul 2005 05:17:21 -0000 Message-ID: <42CCBB86.8060306@asmallpond.org> Date: Thu, 07 Jul 2005 07:20:06 +0200 From: Richard Fish User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050623) X-Accept-Language: en-us, en Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] 2.4 -> 2.6 wierdness References: <49bf44f10507051238e316b9c@mail.gmail.com> <200507051919.25357.mcbrides9@comcast.net> <42CBAA8E.9080901@planet.nl> <200507061330.26204.mar@ml.lv> <42CBC312.7010608@planet.nl> <1058.66.42.166.197.1120691202.squirrel@66.42.166.197> In-Reply-To: <1058.66.42.166.197.1120691202.squirrel@66.42.166.197> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: daf90e43-15b1-4b46-8610-5752aa68b4a2 X-Archives-Hash: 995ab32ff1fa12fe8dec5ca788472190 creighto@spunge.org wrote: >Okay, let's start over. I have only posted the first post of this thread, >but I would say that all off the noise may imply that I am not alone here. > >-I have a working setup in 2.4, less so now than before, but xorg does >still work. > >-in 2.6, xorg will break and complain that /dev/agpgart does not exist. > > > Check /etc/udev/50-udev.rules. You should have a line that says: KERNEL="agpgart", NAME="misc/%k", SYMLINK="%k" A quick explanation of how udev works may help you find the real problem here: For drivers compiled into the kernel, their device nodes get created either: 1. permanently by creating the device nodes manually and using the tarball feature in /etc/conf.d/rc 2. When udevstart is executed by /sbin/rc during startup For modules, the device nodes are created when the kernel runs /sbin/udevsend when the module is loaded. You *must* have hotplug support in the kernel for this though. You can cause udev to generate debug messages by setting "udev_log = 7" in /etc/udev/udev.conf. The debug output goes to /var/log/messages. >-genkernel --udev --menuconfig all will not show me an option that refers >to AGP anything, is this a bus? > > Well, in the normal kernel configuration, It is under "Device drivers->Character devices->/dev/apgart". You need both AGPGART and the chipset specific driver. For example, my config has: carcharias linux # grep AGP /usr/src/linux/.config CONFIG_AGP=y # CONFIG_AGP_ALI is not set # CONFIG_AGP_ATI is not set # CONFIG_AGP_AMD is not set # CONFIG_AGP_AMD64 is not set CONFIG_AGP_INTEL=y # CONFIG_AGP_NVIDIA is not set # CONFIG_AGP_SIS is not set # CONFIG_AGP_SWORKS is not set # CONFIG_AGP_VIA is not set # CONFIG_AGP_EFFICEON is not set >-I tried compiling the kernel directly once and got a kernel panic, I >don't remember if AGP was mentioned in that case. > > > Most common cause of this is not compiling the required drivers for your root filesystem (disk and filesystem drivers) into your kernel. Such drivers cannot be modules without a great deal of effort. -Richard -- gentoo-user@gentoo.org mailing list