|
Bugzilla – Full Text Bug Listing |
| Summary: | Unable to run X or SaX2 on ATI hardware | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Bart Whiteley <bwhiteley> |
| Component: | X.Org | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stefan Dirsch <sndirsch> |
| Severity: | Blocker | ||
| Priority: | P5 - None | CC: | tonyj |
| Version: | Alpha 2plus | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/gdm/:0.log
hwinfo file for one box with this problem. hwinfo file for the other box with this problem (generated from 10.0 system, not 10.1) Another system with this problem: toshiba tecra 9000 laptop |
||
|
Description
Bart Whiteley
2005-11-08 00:53:17 UTC
Do the GDM logs (/var/log/gdm/*) show any meaningful message? This sounds like the broken fontconfig problem. *** This bug has been marked as a duplicate of 128080 *** Then should not "fc-cache --force" fix the problem? (it does not) I would have thought so, perhaps its a different issue the sax warning implies it can't find a virtual terminal Moving to the X guys for review of the Sax error. this is not a sax error. The message: can't find an unused tty... abort was thrown by the server and means there is no tty free to become opened by the X-Server. The X-Server requires a tty to operate. I don't know why your system is using so many tty's please check your environment first. How many mingetty processes are running ? in normal mode there are only 6 and the server choose the tty7 for its operations There are only six mingetty processes running. Note that if I select KDE instead of Gnome during install, all is well. Created attachment 56714 [details]
/var/log/gdm/:0.log
gdm log file.
I have only seen this error when I tried to used a cvs radeon driver that was backported to the xorg packages for SL 10.0. I was using the xorg packages from STABLE at the time. That was not the intended use and it was not a surprise that it didn't work. Have you made sure that all X servers are shutdown when you run sax2 in init level 3? If you switch to VT7 or VT8 is there anything displayed? I'm experiencing this on another box now. Maybe it's not related to gnome. On the new box, I selected a kde system, but in software selection selected gnome also. The box has a ATI FireGL X1. This new box behaves the same. X thinks it is running, but the display says it cannot display the video mode, even though the mode is precicely the display's recommended setting. When I try to run SaX2 from runlevel3, I get the same error: "SaX: can't find an unused tty... abort". I switched the default runlevel in inittab to 3, rebooted, and tried again. Same thing. So, there is certainly not another X server running, and there is nothing on VT7 or VT8. Maybe it's an ATI problem. I have seen this problem on two boxes, both ATI, Another box is Nvidia and it works. I'll adjust the bug to go to the X folks. *** Bug 133014 has been marked as a duplicate of this bug. *** Created attachment 56879 [details]
hwinfo file for one box with this problem.
Created attachment 56880 [details]
hwinfo file for the other box with this problem (generated from 10.0 system, not 10.1)
It could be related to bug 127757 could be related I guess. The behavior I see is different. That bug describes logging into X and it locks up later. I can't even get X to display. Could this be reproduced when using xdm as displaymanager? --> /etc/sysconfig/displaymanager DISPLAYMANAGER="xdm" I've tried gdm, xdm, kdm as DISPLAYMANAGER. None work. Created attachment 57166 [details]
Another system with this problem: toshiba tecra 9000 laptop
This laptop also has the problem. This time I tried a KDE install. May be related to 133572
Please try again with Alpha3 (released this week). Alpha2(plus) was broken WRT X11 in many aspects. :-( Tony, this also matches what you reported to me. Seems it wasn't ia64-specific at all, but a more general problem. For #7 sax throws this in /usr/share/sax/modules/CheckServer.pm. It uses fuser there, see bug 132180. Looks like a dupe. Indeed. Thanks. *** This bug has been marked as a duplicate of 132180 *** psmisc 21.8 did indeed solve the sax2 startup under init 3 part of the problem for me. In combination with that and the backported X driver from bug 127757, I have a working X under alpha2plus. Next stop, alpha3. |