Summary: | [regression] X bails out: symbol lookup error: /usr/lib/xorg/modules/drivers/radeon_drv.so: undefined symbol: pciTag | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | David Ronis <David.Ronis> | ||||
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> | ||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | critical | ||||||
Priority: | medium | ||||||
Version: | git | ||||||
Hardware: | x86 (IA32) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
David Ronis
2011-11-07 20:07:14 UTC
Should be fixed with xf86-video-ati Git commit 89452c08048c98fb5cc3dc551b3824be40d52cf2 . Note that this should only have happened with UMS. Is there any reason why you aren't using KMS? Created attachment 53294 [details]
Logfile after xf86-video-ati rebuilt/reinstalled.
I applied the patch and rebuilt xf86-video-ati. The missing symbol error is gone, but the server still exits. I've attached a logfile. As to why no KMS here: This is an old HP Pavillion 5000 laptop and the last time I tried I ran into problems. I'll try again. I'm changing the status, but will submit a separate report if asked. I added KMS to the kernel and restarted. Now X starts; however, my keyboard and mouse aren't recognized. Both are handled by evdev. When I unplug and plug in the mouse it is recognized. Unfortunately I can't do that with the keyboard (it's on a laptop :)) (In reply to comment #4) > I'm changing the status, but will submit a separate report if asked. Please do file a separate report for the vgaHW failure. It would be great if you could bisect which xserver change triggered that one. (In reply to comment #5) > [...] my keyboard and mouse aren't recognized. That could be a configuration issue, but it's most definitely not related to the video driver. I don't think this should be closed just yet. Aren't things supposed to work without KMS? RE: the mouse/keyboard issues, I've opened a new bug as requested at https://bugs.freedesktop.org/show_bug.cgi?id=42743 (In reply to comment #7) > I don't think this should be closed just yet. The undefined symbol error reported here has been fixed. The vgaHW failure is a different problem that needs to be tracked separately. |
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.