Re: Binary packages (Was: Re: [Dri-devel] R200 testing)
On Sunday 14 July 2002 16:15, José Fonseca wrote: On Sun, Jul 14, 2002 at 07:42:36AM -0600, Keith Whitwell wrote: Next, tuxracer ran, but the menus were basically unusable. Sounds like he hit a whack of software fallbacks - frame rate on menus must have been less than 1fps. He didn't have the patience to get into the game. this happens to me as well, but only if i restart the system after installing the beta r200 driver. Re-running the install.sh script solves the problem and the tuxracer menusystem is as fast as expected. I suspect this is a problem of default dri kernel modules not being overwritten (?), but the install reloads them properly. It's not a big issue though. Interesting. Jose, Alan, have you seen similar problems with the install scripts for other hardware? It sounds like the old radeon.o isn't getting overwritten/overridden. I guess the install script insmod's it explicitly? No. The install script loads the module with `modprobe radeon`, i.e., without the .o, so it should pick the installed one. What the install scripts additionally does is `modprobe agpgart`. Could it be that agpgart was forgotten to be added to /etc/modules.conf? It should read this way correctly: # agpgart is i386 only right now--- not true anylonger? pre-install mga /sbin/modprobe -k agpgart pre-install r128 /sbin/modprobe -k agpgart pre-install radeon /sbin/modprobe -k agpgart options agpgart agp_try_unsupported=1 -- Dieter Nützel Graduate Student, Computer Science University of Hamburg Department of Computer Science @home: [EMAIL PROTECTED] --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Binary packages (Was: Re: [Dri-devel] R200 testing)
On Mon, Jul 15, 2002 at 10:35:46PM +0200, Dieter Nützel wrote: On Sunday 14 July 2002 16:15, José Fonseca wrote: [...] What the install scripts additionally does is `modprobe agpgart`. Could it be that agpgart was forgotten to be added to /etc/modules.conf? It should read this way correctly: # agpgart is i386 only right now --- not true anylonger? pre-install mga /sbin/modprobe -k agpgart pre-install r128 /sbin/modprobe -k agpgart pre-install radeon /sbin/modprobe -k agpgart options agpgart agp_try_unsupported=1 I really don't know much about modules.conf. Usually I just add lines like the ones below: below mach64 agpgart below radeon agpgart José Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Binary packages (Was: Re: [Dri-devel] R200 testing)
Next, tuxracer ran, but the menus were basically unusable. Sounds like he hit a whack of software fallbacks - frame rate on menus must have been less than 1fps. He didn't have the patience to get into the game. this happens to me as well, but only if i restart the system after installing the beta r200 driver. Re-running the install.sh script solves the problem and the tuxracer menusystem is as fast as expected. I suspect this is a problem of default dri kernel modules not being overwritten (?), but the install reloads them properly. It's not a big issue though. Interesting. Jose, Alan, have you seen similar problems with the install scripts for other hardware? It sounds like the old radeon.o isn't getting overwritten/overridden. I guess the install script insmod's it explicitly? Keith --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Binary packages (Was: Re: [Dri-devel] R200 testing)
On Sun, Jul 14, 2002 at 07:42:36AM -0600, Keith Whitwell wrote: Next, tuxracer ran, but the menus were basically unusable. Sounds like he hit a whack of software fallbacks - frame rate on menus must have been less than 1fps. He didn't have the patience to get into the game. this happens to me as well, but only if i restart the system after installing the beta r200 driver. Re-running the install.sh script solves the problem and the tuxracer menusystem is as fast as expected. I suspect this is a problem of default dri kernel modules not being overwritten (?), but the install reloads them properly. It's not a big issue though. Interesting. Jose, Alan, have you seen similar problems with the install scripts for other hardware? It sounds like the old radeon.o isn't getting overwritten/overridden. I guess the install script insmod's it explicitly? No. The install script loads the module with `modprobe radeon`, i.e., without the .o, so it should pick the installed one. What the install scripts additionally does is `modprobe agpgart`. Could it be that agpgart was forgotten to be added to /etc/modules.conf? José Fonseca --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: Binary packages (Was: Re: [Dri-devel] R200 testing)
There are a number of conditions that I know of that requirer a reboot, thought I don't know the cause. 1. When changing from dri to binary nvidia drivers, apps fail to use the new libGLs. Ldconfig is not enuf and a reboot may be needed. This was reproducible, and I could not get libGL to bind with ought rebooting. 2. If AMD760 agpgart is unloaded then after reloading agpgart.o and radeon.o. When you run X it will lock up and you will have to hit the reset button. Could ether of these be related? --- Keith Whitwell [EMAIL PROTECTED] wrote: Next, tuxracer ran, but the menus were basically unusable. Sounds like he hit a whack of software fallbacks - frame rate on menus must have been less than 1fps. He didn't have the patience to get into the game. this happens to me as well, but only if i restart the system after installing the beta r200 driver. Re-running the install.sh script solves the problem and the tuxracer menusystem is as fast as expected. I suspect this is a problem of default dri kernel modules not being overwritten (?), but the install reloads them properly. It's not a big issue though. Interesting. Jose, Alan, have you seen similar problems with the install scripts for other hardware? It sounds like the old radeon.o isn't getting overwritten/overridden. I guess the install script insmod's it explicitly? Keith --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.yahoo.com --- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
