Xconfigurator strangeness

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'd be grateful for any suggestions on the following strange (to me)
behaviour. I am running RH7.3, XFree 4.2.0, with an ATI Mach64 card with a
visible 1Mb of onboard RAM and a Sun0587 monitor.

I boot into text mode (init 3) and run Xconfigurator, selecting all the
defaults/probed values, and a resolution that is known to work (800x600,
16-bit). I can see the 'can you see this message?', and allow it to write
the XF86Config-4 files.  Then I 'startx', and all appears fine as Gnome
appears.  I save the /var/adm/XFree86.9.log file (calling it
/var/adm/XFree86.9.log.successful) and delete the original.

Then I run Xconfigurator again (from a terminal window in Gnome), again
selecting exactly the same values.  This time, however, instead of the
'can you see this message?' I get the grey screen of doom, and have to
Ctrl-Alt-Backspace to get back to Gnome.  /However/ it *has* successfully
written the XF86Config-4 file.  I save the /var/adm/XFree86.{0,9}.log
files as .unsuccessful.

The differences between XFree86.9.log.successful and .unsuccessful are:
("<" indicating the earlier, successful attempt from text mode, ">" the
later, unsuccessful attempt from Gnome.

< (==) Log file: "/var/log/XFree86.9.log", Time: Tue Jul 16 10:04:44 2002
---
> (==) Log file: "/var/log/XFree86.9.log", Time: Tue Jul 16 10:06:09 2002
29c29
< (--) using VT number 7
---
> (--) using VT number 8
53c53
< (II) PCI: stages = 0x03, oldVal1 = 0x8000003c, mode1Res1 = 0x80000000
---
> (II) PCI: stages = 0x03, oldVal1 = 0x00000000, mode1Res1 = 0x80000000
515a516
> AUDIT: Tue Jul 16 10:06:12 2002: 1522 X: client 1 rejected from local
host

At the end of the XFree86.0.log.unsuccessful file are the lines:

AUDIT: Tue Jul 16 10:05:30 2002: 1295 X: client 6 rejected from local host
(WW) Open APM failed (/dev/apm_bios) (No such device)

(But I believe this is just a power manager thing and nothing to do with
graphics?)

So I start again, booting into text mode, and this time repeat the
experiment but this time instead of starting X with 'startx', I go for the
brute force 'xinit' (with no arguments).  This time, Xconfigurator
completes the second time just fine, and I see the 'Can you see this
message?' screen.

I'd be grateful for any suggestions on what I've missed - something
obvious I imagine!   And where else I might look for logged clues, since
the XF logs don't seem particularly vocal.

thanks in advance,
Richard.











[Red Hat General]     [Red Hat Watch]     [Red Hat Development]     [Kernel Development]     [Yosemite Camping]

  Powered by Linux