Bug 467986 - [830M] startx fails - no screens found
Summary: [830M] startx fails - no screens found
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 11
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-10-22 05:22 UTC by Chad Calkins
Modified: 2018-04-11 08:17 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-15 19:16:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The results of startx (1.26 KB, text/plain)
2008-10-22 05:22 UTC, Chad Calkins
no flags Details
Xorg.0.log when starting without an xorg.conf file (13.07 KB, text/plain)
2008-10-22 05:23 UTC, Chad Calkins
no flags Details
Log from the setup (1.02 KB, text/plain)
2008-10-22 05:24 UTC, Chad Calkins
no flags Details
Xorg.0.log (33.17 KB, text/plain)
2009-05-25 12:01 UTC, John Penfold
no flags Details

Description Chad Calkins 2008-10-22 05:22:29 UTC
Created attachment 321110 [details]
The results of startx

Description of problem:
X does not start, configure or anything.  No matter what I do it comes back with:
Fatal Server error:
no screens found

Version-Release number of selected component (if applicable):
xorg-x11-drv-i810
2.4.2  12.fc10

How reproducible:
100%

Steps to Reproduce:
1. login in
2. startx
  
Actual results:
...
Fatal Server error:
no screens found

Expected results:
X starts up and displays the window manager

Additional info:
This machine is a tablet, when ran against an external display instead of the built-in display something similar to bug 461829 happens.

X11 last worked with Fedora 7, although at this version it would boot graphically, and then when X is restarted it would appear to hunt around for an appropriate mode before X would actually display anything.  Also, the bug exists in the most current Ubuntu version with the exact same result.

Comment 1 Chad Calkins 2008-10-22 05:23:21 UTC
Created attachment 321111 [details]
Xorg.0.log when starting without an xorg.conf file

Comment 2 Chad Calkins 2008-10-22 05:24:05 UTC
Created attachment 321112 [details]
Log from the setup

Comment 3 Bug Zapper 2008-11-26 04:06:44 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Chad Calkins 2008-12-27 02:50:28 UTC
The exact same issue exists at the currently most advanced version 10.90?  2.6.20-2.fc11.

Comment 5 Chad Calkins 2008-12-27 02:52:20 UTC
The "intel" driver doesn't work, the "i810" driver doesn't work.  Same results regardless of which is picked.

Comment 6 John Penfold 2008-12-31 14:38:36 UTC
This also occurs on a Fujitsu-Siemens Lifebook S6010 which also uses the Intel 82830 (i830) chipset. With Fedora 8 the i810 driver works but not the intel driver. With Fedora 9 and Fedora 10 neither driver works.

Comment 7 Chad Calkins 2009-04-13 07:27:26 UTC
Doesn't work with Fedora 11 beta live.  The display appears to be starting X, but nothing happens.  The screen just sort of slowly accumulates pixels, but never displays anything.

Comment 8 Matěj Cepl 2009-04-15 20:44:04 UTC
COuld you attach updated /var/log/Xorg.0.log, and /var/log/dmesg, (and maybe even /etc/X11/xorg.conf, if there is any) from F11, please?

Comment 9 Matěj Cepl 2009-05-18 11:55:18 UTC
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

Comment 10 Chad Calkins 2009-05-24 23:55:20 UTC
Tried again with Fedora 11 preview (F11-Preview-i686-Live-KDE.iso).  Same behaviour.  How exactly do I get these files?  I cannot switch to the console with ctrl-alt-F3 (nothing happens, which is odd).  It definitely booted all the way because it played the KDE splash sound.

I'll pull down the F11 preview install, do a text install, and try from there.

Comment 11 John Penfold 2009-05-25 12:01:45 UTC
Created attachment 345303 [details]
Xorg.0.log

Xorg.0.log when run with external monitor connected.

Comment 12 John Penfold 2009-05-25 12:05:15 UTC
When Fedora 11 preview is run on Fujitsu-Siemens Lifebook S6010 on internal display, the screen fades out as soon a X starts. With an external monitor connected it works (on the monitor), but will not switch to the internal display. It seems as if the internal display is not detected.

Comment 13 Matěj Cepl 2009-05-25 16:53:18 UTC
(In reply to comment #12)
> When Fedora 11 preview is run on Fujitsu-Siemens Lifebook S6010 on internal
> display, the screen fades out as soon a X starts. With an external monitor
> connected it works (on the monitor), but will not switch to the internal
> display. It seems as if the internal display is not detected.  

Please, keep this bug on-topic ... a) this is Fedora 10 bug, not Rawhide, b) error is different. File a separate bug for your issue.

Thank you

Comment 14 Chad Calkins 2009-06-06 06:23:18 UTC
The Fedora 11 preview does the same thing.  How do I get the various requested logs when the problem happens?  ctrl alt F3 doesn't give me a console like I expected.  

If I boot with an external monitor attached it does work, just not on the internal flat panel.

I can say that the bug in Fedora 11 is exactly the same bug as in Fedora 10, and the previously attached log files show the same problem.  The new mode-setting intel display driver fails to recognize any valid modes and instead puts the display into something completely invalid.  If I could get it to start in text-mode (the live version doesn't do this even if I change the boot info to be single or runlevel 3.  It always starts the x server.

The same exact problem happens with the current Ubuntu (9.04).  It however eventually fails and dumps me to a console where I can see that the x.org log file says no valid screens.  This leads me to think that the problem is with the Intel driver.

The issue that John Penfold reports sounds like the same issue - it started with the same version of Fedora (I think it did work for me with 8 for awhile (was a long time ago)).  

Any ideas on how to get the log files off it?  An external monitor changes the results, so the log files are almost certainly different.

Comment 15 Vedran Miletić 2009-09-06 08:07:20 UTC
Please provide output of lspci -vv.

Also, Rawhide might be a bit better, but I wouldn't bet on that...

Comment 16 Vedran Miletić 2009-10-15 19:16:41 UTC
Reporter doesn't reply, and intel driver had lots of changes since. I will close this one now, but if anyone can reproduce it, feel free to reopen it.


Note You need to log in before you can comment on or make changes to this bug.