Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter your comments there.
http://bugs.xfree86.org/show_bug.cgi?id=717
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|X server should unload DRM |X server doesn't load
|module when X quits |correct DRM if another one
|(prevents DRI on multiple |is already loaded
|cards) |
------- Additional Comments From [EMAIL PROTECTED] 2003-21-09 07:42 -------
> > [...] I don't agree with your analysis of the cause or conclusion what
> > should be done about it.
>
> My thoughts were based on comment #1 which suggested that the "r128 DRM in
> kernel 2.4.22 doesn't deinitialize correctly".
Well, you engraved your conclusion in the bug summary from the very beginning...
> Thanks for the suggestion. I let the "r128" stay loaded (after quitting X).
> Then I manually loaded the tdfx module and then started X on the voodoo3 card
> and DRI worked !!
Good. So the real problem seems to be that the X server doesn't load the correct
DRM if another one is already loaded. Changing the bug summary accordingly.
> Also, it appears from lsmod that the r128 module is still being used (even
> though X is not using the rage128 card).
I guess the X server doesn't close /dev/dri/card0 even though it doesn't use it.
Again, this shouldn't prevent it from being used by another server though, or
does it?
--
Configure bugmail: http://bugs.xfree86.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
-------------------------------------------------------
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
