Over the last couple of weeks I've been preparing new X.Org CVS rpm packages for rawhide. After several rounds of internal testing by a few people, I've stomped out the obvious upgrade breakages that turned up. Now it is time to get more widespread testing for two purposes:
1) To help upstream X.Org get wider testing coverage before the final release of X11R6.8.0, which is currently slated for August 25th barring any slippage, and get any software bugs that are found reported to X.Org bugzilla on freedesktop.org.
2) To get distribution testing for Fedora Core 3 of the new X release, as we will be shipping 6.8.0 in FC3.
*** IMPORTANT ***
If you upgrade or install the new CVS rpms and experience any bugs in the X.Org X server, video drivers, client libraries, or other parts of the X11 release, they need to be filed in *X.Org* bugzilla, so that they stand a chance of getting fixed before 6.8.0 is finalized.
This is very important, because bugs filed in Red Hat bugzilla will NOT likely be seen by the many people who are working upstream that do not look at Red Hat bugzilla. The proper place to file X.Org bugs, is at:
http://bugs.freedesktop.org in the "xorg" component.
By doing this, bug tracking is centralized, and developers can look in one spot to find what bugs there are in X. It also helps all distributions out, by being able to query bugs, and minimizes duplication of effort amongst distributions and X developers.
Before reporting a bug in bugzilla, query bugzilla first to see if someone else has already reported the issue or not. If someone has, add yourself to CC, and add your own information to the report, as this helps confirm issues happen with multiple people, and that often raises the priority of the issue.
When filing a bug upstream, describe your problem very thorougly with as much detail as possible, and be sure to give the exact steps to reproduce the problem in detail. If a problem is not 100% reproduceable, please indicate that in your report and tell any details which might help X.Org developers reproduce the problem.
You should automatically attach your X server config file and log file to *ALL* bug reports filed in bugzilla, even if you think the information is not useful for the bug report, as developers usually do get some useful information from both of these, and it is easier if the bug report starts out with this information than it is to ask for it later and wait for someone to attach it. Also, if you experience crashes, wether using DRI or not, please attach your complete /var/log/messages file as well, and the output of "lsmod".
When attaching files to bug reports, as always, attach one file per attachment as single individual uncompressed file attachments so developers can click on the file in a web browser and see it right away without having to download it, unzip, and try to keep track of it.
We're trying to help X.Org test this release out, so it is very important that bug reports go to their bugzilla.
If you find a flaw in the rpm packaging, or an upgrade related bug, script bug, or have found a bug that is Red Hat specific, and not likely to be a X.Org generic bug, then of course please report the issue in Red Hat bugzilla, including all of the information and files mentioned above for upstream X.Org bug reports.
Things to test:
- Different video modes and color depths - Xvideo (run various video player applications) - DRI - Xinerama - DMX (Distributed Multihead X - like Xinerama, but works over a network with multiple machines) - Switching VTs to console and back - Suspend and resume on laptops et al. - Anything else you can think of.
The more test coverage things get ahead of time, the more bugs that will likely be fixed for 6.8.0, and the less problems people will experience when FC3 comes out. ;o)
Additional Notes: ~~~~~~~~~~~~~~~~ With every new X release, people often wonder about various things, such as:
Q) What is new in this release? A) Lots. Read the CVS Changelog for the full details, as the release notes haven't been written yet. If you're brave enough, volunteer to write the release notes on xorg@freedesktop.org.
Q) Will this work with my Nvidia or ATI binary drivers? A) Generally speaking, you will always have to test that yourself to find out. One of the goals of X.Org is to retain module ABI compatibility with XFree86 4.4.0. To the best of our knowledge, the 6.7.0 release did good with that. To the best of my own knowledge, there are no ABI changes in 6.8.0, however part of the testing process is to find that out. If there are any ABI changes, X.Org would like to fix them if at all possible, to ensure the maximum level of compatibility, without losing any new functionality.
Q) What if it doesn't work with my binary drivers? A) Report this in X.Org bugzilla. It could be an ABI problem, or it could be a problem in the binary driver. Developers can try to determine this only after a problem has been reported, then if possible hopefully the problem can be resolved. If an ABI compatibility issue happens which turns out is required for some new functionality, then 3rd party driver vendors will have to recompile and/or enhance their driver to work with the new ABI before people can use them. 3rd parties such as ATI and Nvidia will most likely release new drivers to support the new X release, some time after it has been released in a major OS release. (this is what usually happens).
Q) Does the new release have translucent window support? A) Yes, and no, and maybe. The new release currently has several new X extensions, including "XFIXES", "DAMAGE", and "COMPOSITE". The COMPOSITE extension is *EXPERIMENTAL ONLY* at this point in time, is disabled by default until you enable it in the config file, and is currently broken although Keith and others are hacking diligently to try and get it working for 6.8.0. It will be off by default no matter what, but hopefully it will work properly when enabled in 6.8.0. If you decide to test it, do so realizing it is experimental only, and not ready for primetime yet. You WILL experience bugs/flaws/problems, and may find it partially works or not at all. It may slow down your system to a crawl, or it may eat your family. ;o) If you need assistance trying it out, subscribe to xorg mailing lists and ask for help.
That's about all I can think of off the top of my head for now, so have fun testing the new release, I hope it is reasonably stable at this point, and that any major probs get worked out before 6.8.0 by all of the bug reports that will be going to the freedesktop.org bugzilla. ;o)
One more note... Please do not email me directly for help, as I probably won't respond. I usually get 10 million emails when I send out a notice like this, and I can't help 10 million people one at a time. ;o) That is what mailing lists are for, so please use xorg mailing lists or Red Hat mailing lists to ask for help with anything if you have trouble configuring things, or whatnot.
Other than that, thanks in advance for taking the time to pound on the new X11 release and report bugs to X.Org bugzilla. Your test coverage will help to ensure this release is of good quality!
Enjoy 6.7.99-2, and look forward to frequent updates between now and the release of 6.8.0!
Take care, TTYL
On Sunday 15 August 2004 06:43, Mike A. Harris wrote:
Other than that, thanks in advance for taking the time to pound on the new X11 release and report bugs to X.Org bugzilla. Your test coverage will help to ensure this release is of good quality!
Enjoy 6.7.99-2, and look forward to frequent updates between now and the release of 6.8.0!
Here's one data point. It won't start on my system at all after applying this morning's development updates. Logs can be seen here:
http://www.futzin.com/xorgFail.txt
This is a vanilla "Workstation" install on a Sony VAIO which has been working well up till this round of updates. If anyone sees anything else that will help with diagnosing the problem don't hesitate to speak up. I'll head over to the bugzilla on xorg site now .....
Regards, Mike Klinke
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sunday 15 August 2004 18:16, Mike Klinke wrote:
On Sunday 15 August 2004 06:43, Mike A. Harris wrote:
Other than that, thanks in advance for taking the time to pound on the new X11 release and report bugs to X.Org bugzilla. Your test coverage will help to ensure this release is of good quality!
Enjoy 6.7.99-2, and look forward to frequent updates between now and the release of 6.8.0!
Here's one data point. It won't start on my system at all after
xorg-x11-6.7.99.2-5 working fine here on nVidia graphics and nVidia binary driver. Can't really notice any difference yet.
3D apps segfault, but that can be some problem with the binary driver, I don't use 3D apps normally.
- -Andy
- -- Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players http://warmcat.com/usbautocam
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 16 August 2004 13:21, Andy Green wrote:
On Sunday 15 August 2004 18:16, Mike Klinke wrote:
Here's one data point. It won't start on my system at all after
xorg-x11-6.7.99.2-5 working fine here on nVidia graphics and nVidia binary driver. Can't really notice any difference yet.
Another piece of info... installed the new Xorg on a second machine, this one an IBM R31 latop with i810/830 video. Basically worked, but locked the machine solid on X logout. I updated the kernel to the latest Development one and the crash was gone! Didn't expect that but I was very pleased. So if you are having troubles, consider to make sure you have the latest kernel.
- -Andy
- -- Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players http://warmcat.com/usbautocam
On Wednesday 18 August 2004 13:01, Andy Green wrote:
Another piece of info... installed the new Xorg on a second machine, this one an IBM R31 latop with i810/830 video. Basically worked, but locked the machine solid on X logout. I updated the kernel to the latest Development one and the crash was gone! Didn't expect that but I was very pleased. So if you are having troubles, consider to make sure you have the latest kernel.
- -Andy
My problems are when running 2.6.7-1.51 which was still the latest on my development mirror as of this morning. Which kernel are you running?
Regards, Mike KLinke
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wednesday 18 August 2004 19:12, Mike Klinke wrote:
On Wednesday 18 August 2004 13:09, Mike Klinke wrote:
My problems are when running 2.6.7-1.517 which was still the latest on my development mirror as of this morning. Which kernel are you running?
That's what I am running on that machine. The guy with the crashes on X logout was 2.6.7-1.437.
- -Andy
- -- Automatic actions for USB cameras, cardreaders, memory sticks, MP3 players http://warmcat.com/usbautocam
On Wednesday 18 August 2004 14:29, Andy Green wrote:
On Wednesday 18 August 2004 13:09, Mike Klinke wrote:
My problems are when running 2.6.7-1.517 which was still the latest on my development mirror as of this morning. Which kernel are you running?
That's what I am running on that machine. The guy with the crashes on X logout was 2.6.7-1.437.
- -Andy
Well, darn! I was getting my hopes up too ....
Thanks, Mike Klinke
Andy Green wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday 16 August 2004 13:21, Andy Green wrote:
On Sunday 15 August 2004 18:16, Mike Klinke wrote:
Here's one data point. It won't start on my system at all after
xorg-x11-6.7.99.2-5 working fine here on nVidia graphics and nVidia binary driver. Can't really notice any difference yet.
Another piece of info... installed the new Xorg on a second machine, this one an IBM R31 latop with i810/830 video. Basically worked, but locked the machine solid on X logout. I updated the kernel to the latest Development one and the crash was gone! Didn't expect that but I was very pleased. So if you are having troubles, consider to make sure you have the latest kernel.
- -Andy
After updating X, the 845 card works great also. For the 815 video card, X will work until you log out, then it will not start. I was wondering if the FC2 test kernel (521) would allow the X server to work for the 815. I booted up with the 517 kernel when X refused to start. The reason that I wonder if the 521 version would work, when the 517 kernel does not work is because of the different versioned compiler.
Regarding the 830 video card, I saw a few postings on the regular mailing list where X locked up on exit. Maybe the 830 video card works that way. The kernel version might be the ticket to get past the X lockup on exit.
If the code is that dependent on kernel versions or the compiler used for building the kernel, we would never know for sure if upgrading the kernel is wise. Having a backup kernel makes this not a major problem. However, upgrading all of the modular X packages and finding out that X does not work is a bit tougher to handle.
About all of the intel video cards that use the i810 driver. I think that these should be seperated for the different chipsets. Working on systems with both an 815 and another with the 845 make me realize that these two video cards work nothing alike. One was cursed w/ the previous X version and blessed using the CVS version. The before very stable and dependable 815 worked fine up until the installation of the CVS version.
Hopefully something simple can be found out on how to optimize each of the intel cards that use the i810 driver w/o sacrificing the quality of the other chip. I know that spreading out the drivers into independent versions would be hard to maintain. However, the changes to accomidate the 815, 830 or 845 won't bust the other video card from the tradeoff.
Jim
On Wednesday 18 August 2004 19:34, Jim Cornette wrote:
Andy Green wrote:
After updating X, the 845 card works great also. For the 815 video card, X will work until you log out, then it will not start. I was wondering if the FC2 test kernel (521) would allow the X server to work for the 815. I booted up with the 517 kernel when X refused to start. The reason that I wonder if the 521 version would work, when the 517 kernel does not work is because of the different versioned compiler.
I gave this a try this evening; Kernel 2.6.8-1.521 and Xorg-x11 6.7.99.2.-5, but there was no joy. Xorg-x11 still just chokes on start-up. The previous version of Xorg-x11 and the new kernel seem to like one another just fine though.
Regards, Mike Klinke
Mike Klinke wrote:
On Wednesday 18 August 2004 19:34, Jim Cornette wrote:
Andy Green wrote:
After updating X, the 845 card works great also. For the 815 video card, X will work until you log out, then it will not start. I was wondering if the FC2 test kernel (521) would allow the X server to work for the 815. I booted up with the 517 kernel when X refused to start. The reason that I wonder if the 521 version would work, when the 517 kernel does not work is because of the different versioned compiler.
I gave this a try this evening; Kernel 2.6.8-1.521 and Xorg-x11 6.7.99.2.-5, but there was no joy. Xorg-x11 still just chokes on start-up. The previous version of Xorg-x11 and the new kernel seem to like one another just fine though.
Regards, Mike Klinke
Thanks for the feedback. I noticed that the CVS version and the original version on FC3T1 were built on the same build host and used the same kernel.
It looks like time to download the source code related to the i810 video driver, for past and present versions. Either that or try to isolate the binary for the i810 from the version that worked and rename it i815 and use it for the life of the computer. Xorg doesn't seem to be actively responding to the bug report.
Oh well, hopefully it will be fixed before the next beta.
Jim
For the CVS version: Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Build Date: 13 August 2004 Build Host: tweety.build.redhat.com
For the FC3T1 CD version. Build Operating System: Linux 2.4.21-14.ELsmp i686 [ELF] Build Date: 02 July 2004 Build Host: tweety.build.redhat.com
On Thursday 19 August 2004 06:41, Jim Cornette wrote:
It looks like time to download the source code related to the i810 video driver, for past and present versions. Either that or try to isolate the binary for the i810 from the version that worked and rename it i815 and use it for the life of the computer. Xorg doesn't seem to be actively responding to the bug report.
Oh well, hopefully it will be fixed before the next beta.
Jim
You may be right. I'm curious to know, though, if anyone is able to get the i815 to start-up as the two of us seem to be the only two who have reported problems with it and I was kind of expecting a few "me too!" posts.
Regards, Mike Klinke
On Thu, 2004-19-08 at 08:05 -0500, Mike Klinke wrote:
On Thursday 19 August 2004 06:41, Jim Cornette wrote:
It looks like time to download the source code related to the i810 video driver, for past and present versions. Either that or try to isolate the binary for the i810 from the version that worked and rename it i815 and use it for the life of the computer. Xorg doesn't seem to be actively responding to the bug report.
Oh well, hopefully it will be fixed before the next beta.
Jim
You may be right. I'm curious to know, though, if anyone is able to get the i815 to start-up as the two of us seem to be the only two who have reported problems with it and I was kind of expecting a few "me too!" posts.
You can consider this a belated "me too" post.
If most people are like me, they decided to play it safe and not install the xorg update as it seemed to cause trouble. (I did try and install it last night, and X stopped working as described in Jim and your messages). Fortunately, both Jim and your messages were quite helpful in getting me back up and running quickly (well within the hour).
On Thu, 2004-08-19 at 09:05, Mike Klinke wrote:
[snip]
You may be right. I'm curious to know, though, if anyone is able to get the i815 to start-up as the two of us seem to be the only two who have reported problems with it and I was kind of expecting a few "me too!" posts.
Me too! ;-)
Actually, mine's i810 (lspci says 82810E). Running kernel 2.6.8-1.524 and xorg-x11 6.7.99.902-1 and getting no joy. Shall I attach my configs and logs to bug 1086 on freedesktop.org? I'm not getting any kernel crashes, just X crashes (sig11) on startup.
-Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets
On Thursday 19 August 2004 12:57, Paul Iadonisi wrote:
On Thu, 2004-08-19 at 09:05, Mike Klinke wrote:
[snip]
You may be right. I'm curious to know, though, if anyone is able to get the i815 to start-up as the two of us seem to be the only two who have reported problems with it and I was kind of expecting a few "me too!" posts.
Me too! ;-)
Actually, mine's i810 (lspci says 82810E). Running kernel 2.6.8-1.524 and xorg-x11 6.7.99.902-1 and getting no joy. Shall I attach my configs and logs to bug 1086 on freedesktop.org? I'm not getting any kernel crashes, just X crashes (sig11) on startup.
Well, since as Jim noted, we haven't heard anything at all since we posted bugs to freedesktop.org so just in case the problem hasn't really been noticed yet, it may help to shine a little more light on it.
Jim's Bug Posting
http://freedesktop.org/bugzilla/show_bug.cgi?id=1086
My Bug Posting
Paul Iadonisi wrote:
On Thu, 2004-08-19 at 09:05, Mike Klinke wrote:
[snip]
You may be right. I'm curious to know, though, if anyone is able to get the i815 to start-up as the two of us seem to be the only two who have reported problems with it and I was kind of expecting a few "me too!" posts.
Me too! ;-)
Actually, mine's i810 (lspci says 82810E). Running kernel 2.6.8-1.524 and xorg-x11 6.7.99.902-1 and getting no joy. Shall I attach my configs and logs to bug 1086 on freedesktop.org? I'm not getting any kernel crashes, just X crashes (sig11) on startup.
-Paul Iadonisi Senior System Administrator Red Hat Certified Engineer / Local Linux Lobbyist Ever see a penguin fly? -- Try Linux. GPL all the way: Sell services, don't lease secrets
There is a newer version of X that I noted today. The version is the same as you described. I guess adding your xorg-x11 log to the report will give insight into their progression or regression regarding the 815 video card.
I might try to isolate the i810 driver from the working version, rename it to i815, then change my xorg.conf to i815 and see what happens after installing the latest beta. This is probably not a rational solution, but a learning experience anyway.
Jim
I might try to isolate the i810 driver from the working version, rename it to i815, then change my xorg.conf to i815 and see what happens after installing the latest beta. This is probably not a rational solution, but a learning experience anyway.
Jim
Never mind. I toyed around blindly with the concept before upgrading X. I do know more about the kernel and server modules directory structure. Checking the makefile and source code files overwhelmed me.
copying the driver from /usr/X11R6/lib/modules/drivers/i810_drv.o into /usr/X11R6/lib/modules/drivers/i815_drv.o and then modifying the xorg.conf file for i815 instead of i810 left this like the problem we saw with the new X.
I'll hold off on upgrading X until some real progress is made for the i810 driver related to the 815 video server.
Jim
Mike A. Harris wrote:
Over the last couple of weeks I've been preparing new X.Org CVS rpm packages for rawhide. After several rounds of internal testing by a few people, I've stomped out the obvious upgrade breakages that turned up. Now it is time to get more widespread testing for two purposes:
- To help upstream X.Org get wider testing coverage before the
final release of X11R6.8.0, which is currently slated for August 25th barring any slippage, and get any software bugs that are found reported to X.Org bugzilla on freedesktop.org.
- To get distribution testing for Fedora Core 3 of the new X
release, as we will be shipping 6.8.0 in FC3.
*** IMPORTANT ***
If you upgrade or install the new CVS rpms and experience any bugs in the X.Org X server, video drivers, client libraries, or other parts of the X11 release, they need to be filed in *X.Org* bugzilla, so that they stand a chance of getting fixed before 6.8.0 is finalized.
I submitted a bug for the i815 video driver. I'm playing w/ SELinux also. I had to reinstall the original version off of disk to get back up and running.
The bug filed is below. Uploading message txt now.
http://freedesktop.org/bugzilla/show_bug.cgi?id=1086
Jim (Back to basics)
On Sunday 15 August 2004 14:31, Jim Cornette wrote:
I submitted a bug for the i815 video driver. I'm playing w/ SELinux also. I had to reinstall the original version off of disk to get back up and running.
The bug filed is below. Uploading message txt now.
You and I may be suffering from a similar problem.
Mike Klinke wrote:
On Sunday 15 August 2004 14:31, Jim Cornette wrote:
I submitted a bug for the i815 video driver. I'm playing w/ SELinux also. I had to reinstall the original version off of disk to get back up and running.
The bug filed is below. Uploading message txt now.
You and I may be suffering from a similar problem.
The problem with the i810 look pretty similar. I installed all the xorg-x11 rpms from the FC3T1 disc. The output of lsmod and lspci are w/ X running again. I assume your output is with X still broken.
I don't dare trying these rpms on the Dell I have at work. :-)
Jim
On Sunday 15 August 2004 15:08, Jim Cornette wrote:
The problem with the i810 look pretty similar. I installed all the xorg-x11 rpms from the FC3T1 disc. The output of lsmod and lspci are w/ X running again. I assume your output is with X still broken.
I don't dare trying these rpms on the Dell I have at work. :-)
Jim
You're correct, the logs I showed are with X broken. I haven't downgraded the xorg stuff yet to get it working again though. I was holding back to see if anyone more knowledgeable than I might see an easy fix and besides, the lawn mower beckoned....
Regards Mike Klinke
Mike Klinke wrote:
On Sunday 15 August 2004 15:08, Jim Cornette wrote:
The problem with the i810 look pretty similar. I installed all the xorg-x11 rpms from the FC3T1 disc. The output of lsmod and lspci are w/ X running again. I assume your output is with X still broken.
I don't dare trying these rpms on the Dell I have at work. :-)
Jim
You're correct, the logs I showed are with X broken. I haven't downgraded the xorg stuff yet to get it working again though. I was holding back to see if anyone more knowledgeable than I might see an easy fix and besides, the lawn mower beckoned....
Regards Mike Klinke
To get back to the old X version. I copied all of the xorg-x11 files from the installation CD's into a directory on my harddrive. (Using mc to highlight the xorg-x11 rpms. There were parts on all 4 discs.
I then tried to change to the directory where all of the rpms were copied, then run rpm -Fvh *.rpm --oldpackage on the rpms. This did not work. I then tried to run 'rpm -Uvh *.rpm --oldpackage' within the directory where I transferred the rpms to. This installed all of the earlier versions of the xorg-x11 rpms and made X work again.
I then noticed that you had references to selinux in permissive mode. So I decided to disable selinux and reinstall the newer rpms with up2date. They are currently installed. I did not close down X yet to see if it will come back alive.
My theory is that something did not get installed properly because of selinux. I am just trying to determine if this is a real X or selinux not installing the needed files properly. This happened to me before when installing packages w/ selinux in permissive mode.
My guess is that X won't come up again and selinux is not the problem.
I'll know shortly. :-)
Jim
Jim Cornette wrote:
Mike Klinke wrote:
On Sunday 15 August 2004 15:08, Jim Cornette wrote:
The problem with the i810 look pretty similar. I installed all the xorg-x11 rpms from the FC3T1 disc. The output of lsmod and lspci are w/ X running again. I assume your output is with X still broken.
I don't dare trying these rpms on the Dell I have at work. :-)
Jim
You're correct, the logs I showed are with X broken. I haven't downgraded the xorg stuff yet to get it working again though. I was holding back to see if anyone more knowledgeable than I might see an easy fix and besides, the lawn mower beckoned....
Regards Mike Klinke
To get back to the old X version. I copied all of the xorg-x11 files from the installation CD's into a directory on my harddrive. (Using mc to highlight the xorg-x11 rpms. There were parts on all 4 discs.
I then tried to change to the directory where all of the rpms were copied, then run rpm -Fvh *.rpm --oldpackage on the rpms. This did not work. I then tried to run 'rpm -Uvh *.rpm --oldpackage' within the directory where I transferred the rpms to. This installed all of the earlier versions of the xorg-x11 rpms and made X work again.
I then noticed that you had references to selinux in permissive mode. So I decided to disable selinux and reinstall the newer rpms with up2date. They are currently installed. I did not close down X yet to see if it will come back alive.
My theory is that something did not get installed properly because of selinux. I am just trying to determine if this is a real X or selinux not installing the needed files properly. This happened to me before when installing packages w/ selinux in permissive mode.
My guess is that X won't come up again and selinux is not the problem.
I'll know shortly. :-)
Jim
It was the actual xorg-x11 packages. I had to reinstall X to the earlier and eneded up getting some logs when I shut down. (xorg exiting after the newer rpms were installed, ... NOT pretty) and one where X was initialized after trying to restart X.
It looks like I can go back to selinux and hold off on the CVS xorg until it is fixed for the 815 chipset.
Jim
On Sunday 15 August 2004 19:07, Jim Cornette wrote:
It was the actual xorg-x11 packages. I had to reinstall X to the earlier and eneded up getting some logs when I shut down. (xorg exiting after the newer rpms were installed, ... NOT pretty) and one where X was initialized after trying to restart X.
It looks like I can go back to selinux and hold off on the CVS xorg until it is fixed for the 815 chipset.
Jim
Thanks for the update and the "rpm -Uvh *.rpm --oldpackage" tip. I used it to downgrade the xorg stuff and, bingo, I'm back in business.
Regards, Mike Klinke
On Sun, 2004-08-15 at 07:43 -0400, Mike A. Harris wrote:
*** IMPORTANT ***
If you upgrade or install the new CVS rpms and experience any bugs in the X.Org X server, video drivers, client libraries, or other parts of the X11 release, they need to be filed in *X.Org* bugzilla, so that they stand a chance of getting fixed before 6.8.0 is finalized.
This is very important, because bugs filed in Red Hat bugzilla will NOT likely be seen by the many people who are working upstream that do not look at Red Hat bugzilla. The proper place to file X.Org bugs, is at:
http://bugs.freedesktop.org in the "xorg" component.
Things to test:
- Different video modes and color depths
Is it just me? I can't change screen resolution at all! When I attempt, I get a smaller screen in the upper left corner of my monitor. Not even re-starting X solves this.
- Xvideo (run various video player applications)
Screensavers are now very slow (GL ones I think) Atunnel crawls by at under 1 screen per second. OTOH Bouncing Globe is perhaps 5 screens per second, but the shadow effect is jagged - looks terrible! Graphics card is ATI radeon 7200
There are now so many bugs in my test system that I am unsure as to what may be causing them. Since Friday, my panel often crashes when changing preferences such as background, but this is not regular - as it will do it 2 or three times and then it will work fine! Don't know if I should re-install or just give up and wait 2 weeks for test 2. Not doing Bugzilla in case I'm alone in these problems.
Scott
Take care, TTYL
On Mon, 2004-08-16 at 07:51 -0700, Scott Talbot wrote:
Things to test:
- Different video modes and color depths
Is it just me? I can't change screen resolution at all! When I attempt, I get a smaller screen in the upper left corner of my monitor. Not even re-starting X solves this.
I'm stuck in 1600x1200/60Hz also. Changing resolution just shrinks the view, but the monitor stays at the higher res (maximum for my setup). Running system-config-display --reconfig fails. I'll try to get a bug report filed.
-
Andy Green -
Christian Thibodeau -
Jim Cornette -
Michael Knepher -
Mike A. Harris -
Mike Klinke -
Oldman -
Paul Iadonisi