Bug 14474
| Summary: | "Test Configuration" locks up for Voodoo3 cards (button is gone, good) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Sam Varshavchik <mrsam> | ||||
| Component: | XFree86 | Assignee: | Mike A. Harris <mharris> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 7.1 | CC: | chris | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2001-05-15 04:30: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
Sam Varshavchik
2000-07-22 21:21:54 UTC
If you're using a wheelmouse and selected PS/2 as the protocol, this should be fixed in beta5. Installer in pinstripe still locks up on me at this point. Voodoo 3 video card with 16MB RAM, 30-66Khz/50-100Hz refresh rates. PS-2 Kensington mouse with a scrollwheel. "Test Configuration", instead of giving me a 1280x1024 display (maximum resolution in this frequency range), gives me what looks like a 640x480 display with a 1280x1024 virtual screen. I reliably reproduce this every time. Upon exit from the test screen, the anaconda installer display appears noticeably garbled, and is no longer responsive to mouse input. If the configuration is not tested, the installer appears to write out a passable X configuration. Same thing happens here, seems to be an X server bug. I'd *like* to consider this a show-stopper, but it's an XFree86 bug and we won't be changing the X-server without XFree changing it first (realistically). Someone needs to forward this information to the developers at XFree to ensure they know about it... I'm unaware of the details for doing so -- otherwise I'd forward it on. Sam, could you please find out how to send this defect report on to the XFree developers and make a note in this bugzilla entry when you've done this? I'd really apprecaite it! - Glen What exactly is the problem here? I'm not sure what to report to them -- after the system is installed, the mouse does work just fine. If you start an X server, then run yet another X server on a different screen (:2), your first X server gets broken and stops responding. Created attachment 1736 [details]
This following report was forwarded to the XFree86 project.
*** Bug 15084 has been marked as a duplicate of this bug. *** *** Bug 15084 has been marked as a duplicate of this bug. *** clearing 'Mouse' status; this is a voodoo3 problem, not a mouse problem. *** Bug 14076 has been marked as a duplicate of this bug. *** *** Bug 16995 has been marked as a duplicate of this bug. *** *** Bug 17365 has been marked as a duplicate of this bug. *** This defect is considered MUST-FIX for Florence Gold release X server problem. This bug appears very much to be a Voodoo 3 problem, which will have to wait until someone that knows about the problem at a deeper level can provide more intimate details, and perhaps a patch or suggest a workaround. Right now, the workaround seems to be "don't test X on Voodoo installs. This defect is now considered MUST-FIX for Florence Release-Candidate #1 In fisher, the test button is not there (at least with a Voodoo3 3000 AGP card). However, the top of the help at the left says to "Click _Test Setting_". If there is some logic that decides not to show the button, then maybe it should also not show that part of the help. I was looking for this to test, and was momentarily confused. :-) I still haven't tracked down any fixes for the Voodoo cards. Also I haven't received the test hardware to replicate any of the problems with either. Thus this is unlikely to be fixed for RC-1. As such, I'm elevating the priority. I also don't see the TEST X button in the BETA3 install. This is good - it always locked my machine, PCI Voodoo3 2000. I'm glad the bug is still open, though, as removing the button is fixing the symptom rather than the cause. I'm glad people are searching for the cause still (I would have logged a new bug if this bug were closed ;-) This might be related to a problem with the installer being memory hungry, and trying to start up 2 xservers on memory starved machines. I'm investigating... It is unknown why this problem occurs but it might have to do with the GUI installer running 2 X servers simultaneously. Does it work ok if you install Fisher (not Wolverine) using the text install? Please test this. If it does work using the 'test' button in text install on fisher, then it is a problem with running 2 Xservers, or with using XFree 4 and FBdev together perhaps. At this point, I'm inclined to close this bug as it is no longer an issue regardless of wether it is a symptom fix or not. As long as the driver *works* is what is important. Please let me know the results of text install of fisher. I'll look into it later this week, but I don't think I recall a "test configuration" button in text mode install... I do not have an update, unfortunately, due to other "problems" :-) I'll look into it later, and reopen this bug, if so needed. This is not reproduceable in Rawhide for all I can tell. |