Bug 24879
Summary: | X Does not work | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Aaron Brown <abrown> |
Component: | XFree86 | Assignee: | Mike A. Harris <mharris> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | matt_domsch, notting |
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: | 2001-02-16 05:44:07 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: |
Description
Aaron Brown
2001-01-24 20:22:49 UTC
I just found out that if boot the system in mode 3, and run Xconfigurator, startx works fine. So, should this be filed under something besides XFree86? Once the system has been rebooted, things get screwy again. Screen redraws don't happen, and if I try to switch back from another VC, the system hangs. Try out beta 3 and see if it still occurs. I don't have an ia64 kicking around, so I can't test this at all. ;o) I've Cc'd Bill as I believe he is the ia64 guru unless I'm horribly mistaken. ;o) However, if anyone wants to send me an 8 way 1Ghz ia64 box strictly for debugging purposes, I wouldn't mind. ;o) ALso, you should indicate what video card you are using and as many other details as might help track the problem down including making a file attachment to the bug report with your X server logs, and configuration files. This problem is 95% fixed in beta-3. I'm only seeing problems on about 1 out of 4 Big Surs, and I'm pretty sure that's because of "questionable" hardware. Also, I'm aware of bug reporting protocol. There were *no* differences between the logs of a working IA-64 GUI config, and a non-working one. All of the IA- 64s we have have the same exact video card in them (ATI Rage 128), so I made (the possibly) incorrect assumption that I didn't have to include information about what video card I was using. If you believe you should not be assigned IA-64 bugs, please let Preston know on Monday, so we can make sure they get assigned to the right folks. Thanks. Date: Tue, 13 Feb 2001 15:27:31 -0500 From: Bill Nottingham <notting> To: testers-list Subject: Re: Anyone testing IA64 bits?? Short answer is that the int10 stuff is somewhat fubar on ia64. On server machines it can't read the video BIOS, on workstation machines it has a nasty habit of locking the machine if it's using a PCI card. There are some fixes in trunk that are supposed to fix it from Marc Aurele La France (who I'm pretty sure I just butchered the name of), they didn't fix the workstation issue when I tried, and I haven't built a package to try them on the server machines yet. Bill abrown - you're right, bad assumption about me knowing what hardware is in ia64 machines. Doing bugzilla queries based on video card type, etc.. also doesn't work if that information isn't in them. When a bug report doesn't contain enough info for me to do anything about it, I have to request more info. Doesn't matter where the report came in from. I wasn't trying to challenge you on protocol. Sorry if you took it that way. It's better for me to ask than to just hit PRIORITY=LOW, or somesuch.. ;o) I also don't always look to see who reported the bug and wether it was internal or not. I will talk to Preston about having ia64 bugs assigned to someone else. Thanks for the idea. Should be fixed with the 4.0.2-10 X packages. Confirmed fixed in XFree86-4.0.2-11. |