No graphical display during ubuntu install or live cd

[Denis]

Binary package hint: x11-xserver-utils

I need to install my old xorg.conf to get graphical display. Here is its content (I already have similar problem with previous Ubuntu versions).
Section "Monitor"
 Identifier "Configured Monitor"
 VendorName "Iiyama"
 ModelName "Iiyama AS4314UT 17inches"
 HorizSync 24.0-80.0
 VertRefresh 56.0-75.0
EndSection

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
 DefaultDepth 24
 SubSection "Display"
  Depth 24
  Modes "1280x1024"
 EndSubSection
EndSection
Section "Module"
 Load "glx"
EndSection

Section "Device"
 Identifier "Configured Video Device"
 Driver "nvidia"
 Option "NoLogo" "True"
EndSection

I needed to replace nvidia by vesa as nvidia proprietary driver is not installed by default.

ProblemType: Bug
Architecture: i386
CheckboxCommand: xrandr_cycle
CheckboxData: No the screen didn't appear for each mode. This is the problem I had during Ubuntu installation or live CD. No Input was written by my monitor
CheckboxDescription:
 Click Test to cycle through the detected video modes for your system.

 Did the screen appear to be working for each mode?
CheckboxTest: xrandr_cycle
Date: Sat Oct 31 06:51:06 2009
DistroRelease: Ubuntu 9.10
MachineType: System manufacturer P5K
NonfreeKernelModules: nvidia
Package: x11-xserver-utils 7.4+2ubuntu3
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=3fd8084c-0f71-489c-a85f-367843e1fa47 ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 LANG=C
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu7
 libgl1-mesa-glx 7.6.0-1ubuntu4
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1
SourcePackage: x11-xserver-utils
Tags: checkbox-bug
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 10/30/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0704
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0704:bd10/30/2007:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.31-14-generic

[Bryce Harrington (bryce)]

Thank you for seeking to improve Ubuntu. It seems you have filed a bug
against X using the new System Testing utility. Unfortunately, this tool
is filing bugs without collecting sufficient information to properly
diagnose the issues. I wish we could reply to every report to guide you
to gather the correct information, but it happens that so many people
are using this testing feature to file bug reports that we simply cannot
keep up with the influx. I'm replying in bulk so I can get everyone
pointed into a direction most likely to result in getting you a useful
workaround and us a complete bug report that can be solved.

Most of these problems describe issues that have documented
troubleshooting procedures, so perhaps the most helpful thing I can
do is point you to them:

  http://wiki.ubuntu.com/X/Troubleshooting

These guides explain why things break the way they do, and in some cases
provide workarounds.

I would ask that you first go through the appropriate guide for your
problem, particularly if you are having problems with resolution,
crashes, fonts, or blank screen issues, and then file a bug report using
the following command:

   ubuntu-bug xorg

This collects more detailed information than the System Testing tool
does. Please also write a detailed explanation, indicating when you
first discovered the problem, analysis steps you've done, workarounds
that work, and so on.

Or, if you suspect the problem has something to do with the way the test
script itself is working (such as if Ubuntu worked fine until you ran
the script), then file the bug against the test suite:

   ubuntu-bug checkbox

Thanks again, and good luck!