Hi.
I seem to be getting closer to the solution, but I'm not sure what it is. I
tried Adrian's logging trick and got the full log this time (thanks,
Adrian!). However, I couldn't see anything obviously wrong.
So, I then tried switching between monitors (to try out Adrian's idea of the
wrong monitor being used), but with no success.
Then, I accidentally made a discovery. Whilst trying the monitor swap
(special hot key on this laptop), I hit the wrong key, and hit the suspend
to disk key. For a moment, just before the suspend status screen appeared,
the display came back! When I resumed from the suspended system, the
display worked fine!
This is repeatable - boot Linux into text console mode, run startx, lose
display, suspend to disk, resume, et voila! I have my display back.
Does the above give anyone any pointers?
Thanks for your help so far.
Regards,
Austin Denyer.
----- Original Message -----
From: "Adrian D Jensen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 07, 2000 5:23 PM
Subject: Re: Problem with X (Blank screen).
> [EMAIL PROTECTED] on 04/07/2000 10:27:57 AM
> [snip]
> >The system itself installs fine, but I can't get X to work. > During the
> >setup (and later using Xconfigurator) the "can you see me" >test screen
works
> >fine, but when I try to run X for real I get a blank screen >a few
seconds
> >after the blue background appears. If I Ctrl-Alt-BS out, >linux is still
> >running (I can type 'reboot' and the system obliges) but I >still have a
> >blank
> >screen (Alt-F(n) does not help).
> [snip]
> >So far, I have tried 'startx 2 > x.out' on the advice of >another list
> [snip]
>
> Try doing a "startx 2>&1 |tee start.log" (you should be able to us a ">"
instead
> of the "|tee" but it never seems to work on mine) to write all output
(standard
> and error) to a log file.
> My best guess (and that's all it is) is that XFree86 is finding and
enabling the
> external display first and then disabling/ignoring the internal display
(LCD).
> The driver for this just came out in 3.3.6 so there very well might be a
general
> detection bug. Several of the drivers will take an option in the "display"
> section like "intern_disp" to force the use. Have you tried this?
>
> Adrian
>
>
