7.04 Beta: X Config Failure at Installation

Bug #105106 reported by ytene
2
Affects Status Importance Assigned to Milestone
xorg (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

A trial installation of 7.04 beta suggests that there may still be a problem with the configuration of X during installation. My hardware consists of a Tyan Thunder K8W board with 2 x Opteron 250s 4Gb RAM and an XFX7800GS [AGP] Graphics Card coupled with a Samsung 214T 21" [1600x1200] TFT LCD Monitor.

After the post-installation reboot, GNOME [ie X] comes back with resolution set to 1024x768.

Posts on the forums suggested that I try

dpkg-reconfigure ...

which I did, taking best educated guesses at the questions asked. When this failed I resorted to a technique that has worked in the past, which has been to manually hack xorg.conf, adding extra resolution parameters as shown below :-

This is the default xorg.conf setting :-

Section "Screen"
 Identifier "Default Screen"
 Device "NVIDIA Corporation NVIDIA Default Card"
 Monitor "Generic Monitor"
 DefaultDepth 24
 SubSection "Display"
  Depth 1
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 4
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 8
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 15
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 16
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 24
  Modes "1024x768" "800x600" "640x480"
 EndSubSection
EndSection

and this is my hacked version of the file...

Section "Screen"
 Identifier "Default Screen"
 Device "NVIDIA Corporation NVIDIA Default Card"
 Monitor "Generic Monitor"
 DefaultDepth 24
 SubSection "Display"
  Depth 1
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 4
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 8
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 15
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 16
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
 SubSection "Display"
  Depth 24
  Modes "1600x1200" "1280x1024" "1280x960" "1152x864" "1024x768" "800x600" "640x480"
 EndSubSection
EndSection

In the case of Feisty, I then restarted X and expected to see my monitor come back at 1600x1200 [ie native] resolution. It didn't. I went ahead and applied all the available updates and that solved the problem. I mention this only as this is the first distro [since Breezy] where I've found it necessary to patch before upscaling X to 1600x1200 native res for my monitor.

I posted this as a comment in the general discussion forum, here

http://ubuntuforums.org/showthread.php?t=400128

and had a response from "ssam" suggesting this was worth raising here, which I'm happy to do. In passing, one further and potentially useful point worth noting. Prior to upgrading to ubuntu, I had been a Mandrake user since about Mandrake 7.0 and have always been impressed with Mandrake's ability to detect and configure hardware properly. For example, from at least Mandrake 2005LE, the distro has correctly configured itself for my Monitor [in some releases I was able to select from a list] but was always able to correctly detect my nVidia graphics card.

When Mandriva spotted an nVidia card, it also then automatically applied the appropriate binary drivers and configured glx to work with X, with [in my experience] 100% success.

I'm not suggesting that we would want to go quite that far with ubuntu, but as this "bug" posting is effectively a wish-list item, one really nice option would be to see the installer detect an nVidia card and then give the user a prompt that says, "Installer has detected an nVidia card for which proprietary drivers exist. Would you like this installed?" and give the user the choice... That would be a nice and practical way to keep a fully FOSS machine for those who want one, but give others the option for specialist drivers in a way that clearly shows them what is being done to their build... Just a thought.

As my original posting to the forum observed, ubuntu is a terrific distro that goes from strength to strength.

It would be nice if someone could look at and resolve this annoying little problem, especially as I'm keen to see ubuntu get all the basics right before attempting the more adventurous things!

Thanks in advance

C

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

ytene:
Please attach these files:
/etc/X11/xorg.conf
/var/log/Xorg.0.log

It might also be interesting to see the output of:
xresprobe nv
too

Revision history for this message
ytene (ubuntu-ytene) wrote :

Hi Brian and Sitsofe,

Please accept my apologies for taking so long to respond to you. Today I made another attempt at a clean installation of 7.04 but I got the same result. [At least it is consistent]. I have a variety of files to offer you by way of attachments - I hope that I can append more than one at a time. Here is a quick explanation of the files I am sending you, file name by file name...

xorg.conf.orig - this is the xorg.conf file that is created by the installer
Xorg.0.log - this is the log file generated from the above config file
xorg.conf.test - this is my hacked version of the file, including the extra parameters which have worked before
Xorg.0.log.old - this is the log file generated when running my hacked config file, complete with extra errors
xresprobe.txt - this is the output from the "xresprobe nv" command that you asked me to try...

I hope that all the above help. That you again for being kind enough to look at this for me...

Regards,

C

Revision history for this message
ytene (ubuntu-ytene) wrote :

Next file

Revision history for this message
ytene (ubuntu-ytene) wrote :

and the next

Revision history for this message
ytene (ubuntu-ytene) wrote :

the next

Revision history for this message
ytene (ubuntu-ytene) wrote :

and the last...

Revision history for this message
ytene (ubuntu-ytene) wrote :

Footnote -

When I checked the contents of Xorg.0.log I saw the error messages relating to the resolution stanzas I had added and the "unknown mode" that is listed as either the reason for the failure or a symptom of my careless tweaking of the file. I'm guessing that this means that either xorg.conf is incomplete, or that there is another file that may need adjusting. Without making any more changes, I'll continue to trawl around and see what I can find.

Once again, I really appreciate your kind assistance here. Please don't hesitate to let me know if there is more information that you need.

Thanks and Regards,

C

Revision history for this message
ytene (ubuntu-ytene) wrote :

Duh!!

I'm sorry guys, I forgot to mention one more important thing. The original posting was made after using 7.04 Beta from the CD image. All the above files and data - ie the posts in response to your information request, come from installing from the production release of 7.04, AMD64 chipset, and from the DVD rather than the CD iso. In fairness I don't suppose the DVD/CD piece makes much difference, but perhaps the switch to the production codebase might be more important.

C

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi ytene,

Thanks for the detailed bug report! It looks fairly clear that this is another case of bug 3731, based on seeing the "Generic Monitor" in your xorg.conf. The xresprobe.txt is also empty of content. I've found this could happen for a few reasons: I suspect ddcprobe (which xresprobe depends on) sometimes fails to work - you could check by trying to run it and see if it segfaults. Another reason this can happen is if for whatever reason your monitor does not provide EDID information for whatever reason, or if your graphics card or its driver does not carry it through.

While there have been a number of simpler workarounds suggested, the only one that seems to work reliably is what you did - manually hack the xorg.conf file. One thing to be sure is to check the refresh rates listed for your monitor are correct according to your documentation (sometimes the detection mechanism detects them incorrectly.) On a positive note, 3731 is my #1 priority bug, and I'm very hopeful we can get a solution to it for gutsy.

Changed in xorg:
assignee: brian-murray → nobody
Revision history for this message
minty-morky-mindy (minty-morky-mindy) wrote : Re: [Bug 105106] Re: 7.04 Beta: X Config Failure at Installation

Hi Bryce,

My experience differs to "the only one that seems to work reliably is what
you did - manually hack the
xorg.conf file". The best I ever achieved is a locked in proper resolution
and refresh rate but one easily broken when I tried to install 3d drivers.
Having a barely working system is like driving a car on a flat tyre, it can
be done but isn't acceptable as an end result for average use.

You wrote "On a positive note, 3731 is my #1 priority bug, and I'm very
hopeful we can get a solution to it for gutsy." This is good to hear
as 7.04is the worst release of Ubuntu I have so far used - because of
this bug
which seems worse than previously.

Let me know when you have a solution you want tested. A proper download and
not some hack. I can hardly recommend Ubuntu and then give detailed
instructions on how to use the command line and modify xorg - my friends
would not waste their time on such a broken software and rightly so.

Without a proper fully functioning screen resolution and refresh rate, a
person can't even begin to use Ubuntu.

All the best Bryce,

Chris

On 5/7/07, Bryce Harrington <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> Hi ytene,
>
> Thanks for the detailed bug report! It looks fairly clear that this is
> another case of bug 3731, based on seeing the "Generic Monitor" in your
> xorg.conf. The xresprobe.txt is also empty of content. I've found this
> could happen for a few reasons: I suspect ddcprobe (which xresprobe
> depends on) sometimes fails to work - you could check by trying to run
> it and see if it segfaults. Another reason this can happen is if for
> whatever reason your monitor does not provide EDID information for
> whatever reason, or if your graphics card or its driver does not carry
> it through.
>
> While there have been a number of simpler workarounds suggested, the
> only one that seems to work reliably is what you did - manually hack the
> xorg.conf file. One thing to be sure is to check the refresh rates
> listed for your monitor are correct according to your documentation
> (sometimes the detection mechanism detects them incorrectly.) On a
> positive note, 3731 is my #1 priority bug, and I'm very hopeful we can
> get a solution to it for gutsy.
>
> ** This bug has been marked a duplicate of bug 3731
> Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
> incorrect
>
> --
> 7.04 Beta: X Config Failure at Installation
> https://bugs.launchpad.net/bugs/105106
> You received this bug notification because you are a direct subscriber
> of a duplicate bug (via bug 3731).
>

Revision history for this message
Hans van Esdonk (hans-excilas) wrote :
Download full text (3.4 KiB)

I agree. My friends are not very enthousiastic about this bug.
I was lucky I guess. The screen started at 800 x 600 which is just large
enough if you move the top and bottom bar to the left and right side of
the screen. So I could do the installation. After that I used the
xresprobe trick, simply by using the package manager. Problem solved. I
understand it doesn't work on every system and don't know an other
trick. I'm not really an expert.
Good luck
Hans van Esdonk

Op woensdag 09-05-2007 om 01:04 uur [tijdzone +0000], schreef Chris:
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> Hi Bryce,
>
> My experience differs to "the only one that seems to work reliably is what
> you did - manually hack the
> xorg.conf file". The best I ever achieved is a locked in proper resolution
> and refresh rate but one easily broken when I tried to install 3d drivers.
> Having a barely working system is like driving a car on a flat tyre, it can
> be done but isn't acceptable as an end result for average use.
>
> You wrote "On a positive note, 3731 is my #1 priority bug, and I'm very
> hopeful we can get a solution to it for gutsy." This is good to hear
> as 7.04is the worst release of Ubuntu I have so far used - because of
> this bug
> which seems worse than previously.
>
> Let me know when you have a solution you want tested. A proper download and
> not some hack. I can hardly recommend Ubuntu and then give detailed
> instructions on how to use the command line and modify xorg - my friends
> would not waste their time on such a broken software and rightly so.
>
> Without a proper fully functioning screen resolution and refresh rate, a
> person can't even begin to use Ubuntu.
>
> All the best Bryce,
>
> Chris
>
>
> On 5/7/07, Bryce Harrington <email address hidden> wrote:
> >
> > *** This bug is a duplicate of bug 3731 ***
> > https://bugs.launchpad.net/bugs/3731
> >
> > Hi ytene,
> >
> > Thanks for the detailed bug report! It looks fairly clear that this is
> > another case of bug 3731, based on seeing the "Generic Monitor" in your
> > xorg.conf. The xresprobe.txt is also empty of content. I've found this
> > could happen for a few reasons: I suspect ddcprobe (which xresprobe
> > depends on) sometimes fails to work - you could check by trying to run
> > it and see if it segfaults. Another reason this can happen is if for
> > whatever reason your monitor does not provide EDID information for
> > whatever reason, or if your graphics card or its driver does not carry
> > it through.
> >
> > While there have been a number of simpler workarounds suggested, the
> > only one that seems to work reliably is what you did - manually hack the
> > xorg.conf file. One thing to be sure is to check the refresh rates
> > listed for your monitor are correct according to your documentation
> > (sometimes the detection mechanism detects them incorrectly.) On a
> > positive note, 3731 is my #1 priority bug, and I'm very hopeful we can
> > get a solution to it for gutsy.
> >
> > ** This bug has been marked a duplicate of bug 3731
> > Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
> > ...

Read more...

Revision history for this message
Hans van Esdonk (hans-excilas) wrote :
Download full text (3.2 KiB)

Oh yes, forgot to tell.
Yesterday evening I installed Kubuntu 7.04 on a friends PC with hi-res
CRT 1600 x 1200, 500 MHz processor and 256 M memory. We used the text
mode for installing and it worked very nice. Earlier attempts with
Ubuntu 7.04 failed. Again, I don't understand why.

Hans van Esdonk

Op woensdag 09-05-2007 om 01:04 uur [tijdzone +0000], schreef Chris:
> *** This bug is a duplicate of bug 3731 ***
> https://bugs.launchpad.net/bugs/3731
>
> Hi Bryce,
>
> My experience differs to "the only one that seems to work reliably is what
> you did - manually hack the
> xorg.conf file". The best I ever achieved is a locked in proper resolution
> and refresh rate but one easily broken when I tried to install 3d drivers.
> Having a barely working system is like driving a car on a flat tyre, it can
> be done but isn't acceptable as an end result for average use.
>
> You wrote "On a positive note, 3731 is my #1 priority bug, and I'm very
> hopeful we can get a solution to it for gutsy." This is good to hear
> as 7.04is the worst release of Ubuntu I have so far used - because of
> this bug
> which seems worse than previously.
>
> Let me know when you have a solution you want tested. A proper download and
> not some hack. I can hardly recommend Ubuntu and then give detailed
> instructions on how to use the command line and modify xorg - my friends
> would not waste their time on such a broken software and rightly so.
>
> Without a proper fully functioning screen resolution and refresh rate, a
> person can't even begin to use Ubuntu.
>
> All the best Bryce,
>
> Chris
>
>
> On 5/7/07, Bryce Harrington <email address hidden> wrote:
> >
> > *** This bug is a duplicate of bug 3731 ***
> > https://bugs.launchpad.net/bugs/3731
> >
> > Hi ytene,
> >
> > Thanks for the detailed bug report! It looks fairly clear that this is
> > another case of bug 3731, based on seeing the "Generic Monitor" in your
> > xorg.conf. The xresprobe.txt is also empty of content. I've found this
> > could happen for a few reasons: I suspect ddcprobe (which xresprobe
> > depends on) sometimes fails to work - you could check by trying to run
> > it and see if it segfaults. Another reason this can happen is if for
> > whatever reason your monitor does not provide EDID information for
> > whatever reason, or if your graphics card or its driver does not carry
> > it through.
> >
> > While there have been a number of simpler workarounds suggested, the
> > only one that seems to work reliably is what you did - manually hack the
> > xorg.conf file. One thing to be sure is to check the refresh rates
> > listed for your monitor are correct according to your documentation
> > (sometimes the detection mechanism detects them incorrectly.) On a
> > positive note, 3731 is my #1 priority bug, and I'm very hopeful we can
> > get a solution to it for gutsy.
> >
> > ** This bug has been marked a duplicate of bug 3731
> > Xorg resolution falling back to 640x480 and/or 800x600 when h/v freqs
> > incorrect
> >
> > --
> > 7.04 Beta: X Config Failure at Installation
> > https://bugs.launchpad.net/bugs/105106
> > You received this bug notification because you are a dir...

Read more...

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.