Bug 45942 - X server fails to start with xorg-x11-drv-ati driver
Summary: X server fails to start with xorg-x11-drv-ati driver
Status: RESOLVED DUPLICATE of bug 45900
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-11 13:12 UTC by Chris Rankin
Modified: 2012-02-12 10:05 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Xorg.0.log file showing failure. (21.90 KB, text/x-log)
2012-02-11 13:12 UTC, Chris Rankin 		no flags Details
View All

Description Chris Rankin 2012-02-11 13:12:11 UTC 
Created attachment 56903 [details]
Xorg.0.log file showing failure.

I upgraded my radeon_drv.so driver, but then the X server failed to start.

[   549.484] drmOpenDevice: node name is /dev/dri/card0
[   549.484] drmOpenDevice: open result is 10, (OK)
[   549.484] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
[   549.484] drmOpenDevice: node name is /dev/dri/card0
[   549.484] drmOpenDevice: open result is 10, (OK)
[   549.484] drmOpenByBusid: drmOpenMinor returns 10
[   549.484] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
[   549.484] (EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version mismatch.
[dri] This chipset requires a kernel module version of 1.17.0,
[dri] but the kernel reports a version of 2.12.0.[dri] Make sure your module is loaded prior to starting X, and
[dri] that this driver was built with support for KMS.
[dri] Aborting.

The full file is attached.
Comment 1 Chris Rankin 2012-02-11 13:15:43 UTC 
For reference, the git driver from 1st February works OK. My kernel is vanilla 3.2.5.
Comment 2 Alex Deucher 2012-02-12 10:05:04 UTC 

*** This bug has been marked as a duplicate of bug 45900 ***

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.