Bug 448109
Summary: | Wrong module name for intel_master and intel_batchbuffer | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gustavo Junior Alves <gjalves> | ||||||||||||||||||
Component: | xorg-x11-drv-i810 | Assignee: | Adam Jackson <ajax> | ||||||||||||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
Severity: | medium | Docs Contact: | |||||||||||||||||||
Priority: | low | ||||||||||||||||||||
Version: | 9 | CC: | mcepl, xgl-maint | ||||||||||||||||||
Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||
Hardware: | All | ||||||||||||||||||||
OS: | Linux | ||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||
Last Closed: | 2009-07-14 17:42:02 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
Gustavo Junior Alves
2008-05-23 14:39:26 UTC
Just to be sure, that we have all relevant information. Please attach your X server config file (/etc/X11/xorg.conf) and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Created attachment 306525 [details]
vncviewer on a machine with intel driver
This is the screenshot of a vncviewer session of Xorg from another Fedora
machine. The same screen can be seen on VNC for Windows. When changed the intel
driver to vesa, everything goes fine.
Created attachment 306526 [details]
Results from X :1 -configure
When tried to autogenerate the config file using X :1 -configure, the results
appears as in this attachment.
Created attachment 306527 [details]
Xorg with problem loading intel modules
This is the original file that I wrote for use with intel and vnc. From X, I
don't see any problems with those files. When I started to use with vnc, the
problem show up. Then, if I use any other driver, the problem goes away.
Created attachment 306528 [details]
A log with the error
Thie is one from many tests I have done. Its possible to see the wrong module
loading.
Created attachment 306529 [details]
Working log
I don't have any idea why, but the error goes away. From the various
tentatives, includes a installation from vanilla distribution of intel drivers
and some X recompilation.
The vnc still doens't work on intel. Maybe I assumed wrong the error from intel
driver is related with the vnc problem?
Is the issue reproduceable on the latest updates of your distribution? Unfortunally I doesn't have this machine anymore. :( Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. Created attachment 317193 [details]
Modules errors in "Xorg -configure"
Created attachment 317194 [details]
My xorg.conf
Comment on attachment 317193 [details]
Modules errors in "Xorg -configure"
My display blinks when I move anything on screen, like when double framebuffer are not used.
The command "Xorg -configure" prints these messages:
(EE) Failed to load module "intelbatchbuffer" (module does not exist, 0)
(EE) Failed to load module "intelmaster" (module does not exist, 0)
Fedora 9 system.
Graphics card i740 (intel 82740)
lspci:
01:05.0 VGA compatible controller: Intel Corporation 82740 (i740) AGP Graphics Accelerator (rev 21) (prog-if 00 [VGA controller])
# rpm -q xorg-x11-drv-i810
xorg-x11-drv-i810-2.3.2-2.fc9.i386
Created attachment 317195 [details]
My xorg log
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |