No image during bootup with DVI panel

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

The problem still exist in Ubuntu 7.10 (2007-12-22)
I have written a small howto to increase the console buffer which fix the problem with no output over DVI. The howto is located on https://help.ubuntu.com/community/ConsoleFramebuffer under the section "Increase the number of visible rows and columns in console".

Back to the matter, the original concerns in the bug description from Gavin Hamill is still valid. No output on the screen is visible from the point Grub is loading the kernel and until gdm/X is loaded. In case of X failure there is no output to the screen which might lead users to think their whole system is broken.
/Johan Herdegård

This problem also exists in hardy beta (19-Mar-2008 CD).
I have a GeForce 8500 GT (10de:0421) with DVI and VGA output
and use the VGA output.
No output from kernel start to X start (which means for the install
CD that "Check CD" simply goes blank and you never see anything
again).
The "vga=0x314" on the kernel line helps with kernel boot output,
but unfortunately the text consoles (CTRL-ALT-Fx) write black on
black, i.e. I see only the cursor moving :-(

A short update: not using any "vga=" option (just removing "silent" and "splash") solves the "black on black" problem on the text consoles.

I have a ViewSonic 2035wm monitor, an nVidia 8800GTS video card. On a fresh ubuntu 8.04 install, x doesn't detect my monitor. The only thing I was able to do is select a flat panel 1280x1024 and use 1024x768 resoluion.
However, i switched the DVI cable for a analog VGA cable, restarted and Ubuntu booted up in native 1680x1050 resolution.

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Re-tested using Intrepid Alpha 5 Live CD with linux 2.6.27-2-generic

The boot progress is now shown correctly, although some ugly kernel messages flashed on the screen momentarily between 'Starting up....' and the progress indicator:

[ 2.797758] uvesafb: failed to execute /sbin/v86d
[ 2.797805] uvesafb: make sure that the v86d helper is installed and executable
[ 2.797854] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-2)
[ 2.797895] uvesafb: vbe_init() failed with -22
[ 2.797939] uvesafb: probe of uvesafb.0 failed with error -22

Just to add further confirmation, I rebooted with the VGA input to the monitor also connected, and it still works fine. Am able to see the boot progress via both VGA and DVI inputs.

Alt-Fx virtual consoles also work fine on both inputs.

Thanks Gavin. For the uvesafb issue, please refer to bug 246269 . It sounds like however, this particular bug you reported has been resolved. I'll go ahead and close it. Thanks.