Red Hat Bugzilla – Bug 208463
"intel" X11 server dies with error : "No modes found on either pipe" on i830 chipset
Last modified: 2008-05-01 11:38:06 EDT
Description of problem:
"intel" X11 server dies with error : "No modes found on either pipe"
Version-Release number of selected component (if applicable):
I used the "intel" driver (not the "i810" driver) on a Dell Latitude C400 (which
has an i830 chipset). This same xorg.conf file works fine on a i915 chipset.
It also works fine on the i830 if I use the "i810" driver. I've attached the
Steps to Reproduce:
1. Find a Dell Latitude C400
2. Try to start X11 with the "intel" driver
3. Shock and awe
X server dies with error: "No modes found on either pipe"
I expected the X server to run OK.
I generated the xorg.conf file by running "X -configure" (and then changed
'Driver "i810"' to 'Driver "intel"'). It works OK on a i915 machine.
Created attachment 137332 [details]
This X server log file
Created attachment 137333 [details]
This is the xorg.conf file
Fedora Core 5 and Fedora Core 6 are, as we're sure you've noticed, no longer
test releases. We're cleaning up the bug database and making sure important bug
reports filed against these test releases don't get lost. It would be helpful if
you could test this issue with a released version of Fedora or with the latest
development / test release. Thanks for your help and for your patience.
[This is a bulk message for all open FC5/FC6 test release bugs. I'm adding
myself to the CC list for each bug, so I'll see any comments you make after this
and do my best to make sure every issue gets proper attention.]
Even after almost three months there has been no activity on these bugs, so we
consider them obsolete and they are being closed as INSUFFICIENT_DATA.
Please, if you are able to reproduce this bug on currently supported (FC6 and
F7) non-test distribution, or if there is any other reason why this bug should
be kept alive, please, reopen, change the product to something more recent and
add an additional information to the comment of such bug.
Thank you very much.