Bug 103936
| Summary: | xfree86 4.3 dri not working on radeon 7000 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 3 | Reporter: | jahshaka <jah> | ||||||||||
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | David Lawrence <dkl> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 3.0 | CC: | jdennis, lwoodman | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | ia64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2006-02-21 18:58:29 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
jahshaka
2003-09-08 00:40:03 UTC
Apparently the main problem is here (XFree86 log file) drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed drmOpenDevice: minor is 0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is -1, (No such device) drmOpenDevice: open result is -1, (No such device) drmOpenDevice: Open failed [drm] failed to load kernel module "radeon" (II) RADEON(0): [drm] drmOpen failed (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI. as a note, i have rebuilt my kernel from the source rpm and built xfree86 4.3 and tried their driver and i cant seem to get around the dri issue here... Please reproduce this with the Red Hat kernel binaries, and attach your X server log, config file and /var/log/messages booted into the Red Hat built kernel using Red Hat built XFree86. We do not support user recompiled binaries. If the problem can be reproduced using our binaries, I can investigate this problem deeper with you. Thanks in advance. i have the exact same problem with the stock install - exactly the same. i still had it after installing all the latest up2date patches (including going through 3 different kernel rpm's). thats why i tried doing a custom build and tried to install x... i will attach the log files for you to examine but need to reinstall the kernel first (however, the results will be the same as originally mentioned) Created attachment 94365 [details]
XFree86.0.log
note that this kernel was rebuilt from srpm and was not a custom build... i am attaching the previous log file as well Created attachment 94367 [details]
XFree86.1.log - redhat kernel
>note that this kernel was rebuilt from srpm and was not a custom build... i am >attaching the previous log file as well Those two statements are contradictory. A kernel not compiled by Red Hat on a Red Hat build machine, and supplied to a customer via ftp or RHN is by definition a "custom" kernel by our definition. We only support kernels that we build. We do not support user compiled kernels wether they are compiled from kernel.org sources, or our sources modified or unmodified. [From - Additional Comment #3 From Mike A. Harris on 2003-09-09 03:42] >Please reproduce this with the Red Hat kernel binaries, and attach your >X server log, config file and /var/log/messages booted into the Red Hat >built kernel using Red Hat built XFree86. We do not support user recompiled >binaries. Awaiting X server config file, /var/log/messages, and an X log. The kernel log and the X log need to be from the same X server invocation. These are crucial pieces of information for debugging these types of problems. Created attachment 94632 [details]
latest messages logfile
Created attachment 94633 [details]
latest xfree logfile
I just upgraded to the latest kernel, the 2.4.21-3.EL and am still having this problem. I am attaching the X log and the messages log - these are using the standard installs. Note that i also upgraded to the latest XFree86 update as well XFree86-4.3.0-32.EL Are there also issues with this being -32 and not -64 (the xfree build) ? To the best of my knowlege nothing has changed with respect to DRI support on ia64 so I would not expect this to have started to work. The agpgart kernel driver is known to have problems. We are still in the process of investigating possible solutions. The initial release of RHEL 3.0 will likely ship without support, however we may be able to provide a driver update without having to wait for RHEL 3.0 Update. I will update this bugzilla as soon as I have further information. *** This bug has been marked as a duplicate of 104338 *** Sounds great, i ran out and bought a geforce card to see if i could get nvidias driver to install but now realize its not the drivers... Although while you are working on this the latest nvidia ia64 drivers wont even compile, they give a highmem error and crap out. I noticed that the latest release of these driver by nvidia was devember 2002 close to a year ago. I know that redhat doesnt support binary only drivers but maybe you can push them to get a newer release out the door in time for the agpgart fix? How can i test the patch that bjorn put up for agpgart, its for the last kernel before the EL-3 release which i am now running... and i dont want to break anything in my current kernel which seems to be running perfectly! Anyone trying to get nvidia drivers running on taroon ia64 may want to follow this post http://www.nvnews.net/vbulletin/showthread.php?s=&postid=201323#post201323 Red Hat doesn't support Nvidia's binary drivers at all on any platform. We do not approach vendors and ask them to speed up their proprietary driver release process for drivers we don't support either. People who use their drivers however are of course free to ask them for updated drivers, support, etc. if they wish, however Red Hat is not involved in that process. Nvidia uses their own proprietary agpgart, and does not use the agpgart which we ship, so any fixes to agpgart that we provide won't affect users using Nvidia proprietary drivers at all. The problem described in the email you point out above, is because the Red Hat kernel contains various enhancements over a stock 2.4.x kernel, which have either been developed at Red Hat directly, or back ported from 2.5.x, which change many kernel internals. The kernel does not have a stable advertised ABI, and so proprietary kernel modules will break and require their vendors to fix them to work with new kernels. Nvidia will have to update their drivers to work with the Red Hat Enterprise Linux 3 kernel. Please contact Nvidia directly for any support issues/requests pertaining to their drivers. Thanks. Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |