Bug 242120 - drm module don't work with 855GM chipset (xorg driver i915)
Summary: drm module don't work with 855GM chipset (xorg driver i915)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 7
Hardware: i386
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-06-01 20:19 UTC by Adrien Bustany
Modified: 2008-01-09 00:44 UTC (History)
1 user (show)

Fixed In Version: 2.6.23
Clone Of:
Environment:
Last Closed: 2008-01-09 00:44:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Adrien Bustany 2007-06-01 20:19:17 UTC
Description of problem:
Drm module i915 in /lib/modules/<kernel version>/kernel/drivers/char/drm does
not work with kernel 2.6.21-1.3194.fc7

Version-Release number of selected component (if applicable):
kernel 2.6.21-1.3194.fc7
xorg-x11-server-Xorg-1.3.0.0-5.fc7

How reproducible:
install fedora 7 on a box using an intel 855GM chipset (driver i915), try to
launch glxgears : you'll get a drmmap error
  
Actual results:
dri does not work

Expected results:
dri should work :)

Additional info:
SOLUTION : checkout mesa/drm from the freedesktop git, go in the linux-core dir,
make and copy the .ko files in the right dir (drivers/char/drm/), reboot.

Comment 1 Christopher Brown 2007-09-13 19:26:37 UTC
Hello,

I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug and will try and assist you in resolving it if I can.

There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?

If the problem has gone away then please close this bug or I'll do so in a few
days if there is no additional information lodged.

Cheers
Chris

Comment 2 Adrien Bustany 2007-09-13 20:05:42 UTC
Well, I don't have the problem anymore, so we could close it.


Note You need to log in before you can comment on or make changes to this bug.