On 7/4/05, Tino Keitel <[EMAIL PROTECTED]> wrote: > On Mon, Jul 04, 2005 at 14:01:12 +0200, Jerome Glisse wrote: > > Is this a hard lockup or not ? ie could you ssh in the box ? > > Yes, it's a hard lockup. > > > If you can ssh to the box, could you provide Xorg log (in /var/log/) > > & revealent part of syslog or whatever is the ouput of radeon module > > when you try to start Xserver with it. > > > > Maybe you could try to first load radeon module & then Xserver, > > if you don't already try this. > > When I load the radeon module on the command line everything works. The > lockup occurs when the server starts. > > > > > Btw a "depmod -a " shouldn't hurt, and do a find /lib/modules -name > > radeon.ko > > to see if there isn't two copy of it in different places. > > $ /sbin/modprobe -l | grep radeon > /lib/modules/2.6.12/kernel/drivers/char/drm/radeon.ko >
Hhhmmm there must be a difference somewhere in your system. Somethings which have changed between first start & your last reboot. Is there any things in your kernel message after loading radeon.ko (without starting x) ? Recompiling everythings from CVS should fix that (use Mesa CVS too). Jerome Glisse ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
