http://bugs.freedesktop.org/show_bug.cgi?id=14094
vaLentin [EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|DUPLICATE |
--- Comment #3 from vaLentin [EMAIL PROTECTED] 2008-01-17 05:28:05 PST ---
(In reply to comment #2)
*** This bug has been marked as a duplicate of bug 13922 ***
I do not think that this report is related to (In reply to comment #2)
*** This bug has been marked as a duplicate of bug 13922 ***
Are you sure that this is related to 13922? All gl applications are dying and
the crash reports for each of them are pointing to intel_fbo.c:369.
The X server itself remains stable even gl applications such as glxgears dying
with Signal 11.
Moreover I can not find anything common between 13922 and this one but the
following message only:
Failed to initialize TTM buffer manager. Falling back to classic.
What do you mean in 13922? Here I will quote:
were you using the mesa tip? -- This reply is unclear. There are no references
or URLs to the tip you are referring to or to any other documentation page. If
you say something and you do not want to describe it in details I would like to
kindly ask you to give us (the users) URLs. There we will be able to learn more
about the tip. Some of us really prefer to dig the entire Google earth
before bugging you with bugreports. I really re-searched the world before
contacting you guys.
Moreover the mesa FAQ/Documentation page does not have a tips section
It is kind of confusing for the normal and even average users like me. I should
rather guess.
So proof me if I am wrong but here, my best guess is that you are saying that:
IF A USER WOULD LIKE TO USE MESA FROM GIT (so he/she can eventually test bug
fixes etc or simply want to get the GL applications working correctly) he/she
first download and install X from git. Am I right?
... Or I should first download and install X itself, the intel driver and DRM
all of them from the git so I can get a working git MESA implementation?
If that's the case it is NOT mentioned in any faq/install/readme or any other
documentation.
If that is not the case this means that the current mesa GIT version is failing
as there is no patch provided in bug 13922 or this bug is not a duplicate of
it.
I am really sorry for my language but indeed I have a lot of troubles with my
video card and the mesa implementation for it. There is not much documentation
available for troubleshooting.
What I am trying to say guys is that even there is no information on your web
site how I should fill mesa/dri related bug reports (please think of placing
instructions similar to the ones which the kernel source tree have in
/path/to/kernel/source/REPORTING-BUGS) and what You would like the user to do I
did my best. I provided you with all of the information that might be useful to
you in order to easily pinpoint the problem and will gladly provide you with
more if you tell me what I should do and what I am receiving here is an
automated reply to a bug report. The bug report to where you re-directed me is
UNCLEAR. Moreover the replies posted by the developers in there are even more
unclear than the bug report itself.
As a network technical support team member I really know how important is to
provide the end user with accurate, clear and straight forward answers. That's
all what I am asking for in here.
Your detailed reply regarding this matter will be highly appreciated.
With my best regards,
vaLentin
A desperate Intel Video X3100/965GM Linux user
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
