[Dri-devel] [Bug 108] matrox drm code cannot find framebuffer, crashes X
[This e-mail has been automatically generated.] 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//cgi-bin/bugzilla/show_bug.cgi?id=108 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||NOTOURBUG --- Additional Comments From [EMAIL PROTECTED] 2003-05-29 16:47 --- I agree, if one is using Matrox's drivers, they're not using what ships with XFree86, but rather a binary blob loaded into a driver that isn't what ships with XFree86. --- 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: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 108] matrox drm code cannot find framebuffer, crashes X
[This e-mail has been automatically generated.] 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//cgi-bin/bugzilla/show_bug.cgi?id=108 --- Additional Comments From [EMAIL PROTECTED] 2003-05-29 02:06 --- Since quite a bit of stuff changed from 4.2.x to 4.3.0, it doesn't seem surprising that driver binaries from a previous release would break. IIRC, the same thing happened with the Radeon driver. Isn't the moral of the story to use the driver for the version of XFree86 you're using? I suspect this bug should be closed. --- 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: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
[Dri-devel] [Bug 108] matrox drm code cannot find framebuffer, crashes X
[This e-mail has been automatically generated.] 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//cgi-bin/bugzilla/show_bug.cgi?id=108 [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |dri- ||[EMAIL PROTECTED] --- Additional Comments From [EMAIL PROTECTED] 2003-04-05 05:26 --- The oops happens because when mga_do_init_dma() fails to find the framebuffer it calls mga_do_cleanup_dma() which tries to free a bunch of stuff which never was allocated. I know this because I've come across this once. Nevertheless the real problem is that the framebuffer can't be found on the first place. Please post your XFree86.0.log and give details about which versions you're using, specifically the linux kernel version, XFree86 version, and where did the DRM module you're using came from (kernel or XFree86). --- 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: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ ___ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
