Splash screen video mode incompatible with some DVI monitors

Had no problems showing the splash screen while loading system on an ATI Rage 9200 DVI (MacMini). But the problems appeared on the gdm login screen: the screen is compressed to half the width, i.e. 840x1050x60Hz instead of 1680x1050x60Hz.

Plugging the DVI to analog converter solves the issue, but I'd like to use DVI... :(

I'm using latest Dapper updates.

I'm having a similar problem with the LiveCD. I've a dual CRT setup connected to a GeForece 6800GT.

-Mitsubishi DP930SB w/ 110KHz horizontal refresh - connected to the DVI port
-NEC FE991SB w/ 96khz horizontal refresh - connected to the VGA port

When booting, the kubuntu edgy eft knot 3 cd will give the FE991SB a 108KHz horizontal refresh rate, while it will give the DP930SB a ~255KHz refresh rate. Trying to boot in safe mode does the same thing.

I'll assign that to usplash right now, since it has to do with it.

When booting Feisty with the version 0.4, the screen turns off because the screen haven't signal and it doesn't turn on again and I must reboot.
My system is AMD64 and ATI x700

I have the same problem with usplash on Ubuntu 7.04 and now 7.10 with last update.
My CPU is an AMD64 X2 and my graphic card an ATI X600.
When I boot the splash screen don't appear and my monitor say that the signal is "out of range".

I have the same problem with gutsy. LG Flatron monitor goes to power save during boot. System: AMD64 X2 and NVidia 8600GT.

I have the same problem with Feisty Fawn AMD64.
My monitor : Samsung SyncMaster 206bw
My system : AMD 64 X2 Dual-Core, Nvidia GeForce 8500GT.
Thanks a lot!

Try putting after grub's line ( /boot/grub/menu ) vga=791

2007/9/6, nicoletti <email address hidden>:
>
> I have the same problem with Feisty Fawn AMD64.
> My monitor : Samsung SyncMaster 206bw
> My system : AMD 64 X2 Dual-Core, Nvidia GeForce 8500GT.
> Thanks a lot!
>
> --
> Splash screen video mode incompatible with some DVI monitors
> https://bugs.launchpad.net/bugs/25011
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Hi,

It works fine with vga=791 after grub's line!
Thanks a lot!

On 9/6/07, David Elfau <email address hidden> wrote:
>
> Try putting after grub's line ( /boot/grub/menu ) vga=791
>
> 2007/9/6, nicoletti <email address hidden>:
> >
> > I have the same problem with Feisty Fawn AMD64.
> > My monitor : Samsung SyncMaster 206bw
> > My system : AMD 64 X2 Dual-Core, Nvidia GeForce 8500GT.
> > Thanks a lot!
> >
> > --
> > Splash screen video mode incompatible with some DVI monitors
> > https://bugs.launchpad.net/bugs/25011
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Splash screen video mode incompatible with some DVI monitors
> https://bugs.launchpad.net/bugs/25011
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Same problem (video frequency too high between grub and gdm) after fresh Gutsy install with:

GC: ATI Radeon RV100 QY [Radeon 7000/VE]
Samsung SyncMaster 570S (Flat 15'), DVI output, DVI to VGA adapter

The vga=791 trick doesn't help.
In tty, the screen quality is very poor, trembling, partially blinking.
No problem in graphical mode (from GDM on).

Have the same issue on Ubuntu 8.04 (Hardy Heron). Tried alpha 3 and the daily build from 19th January. I have a Nvidia 8800GTS 512 MB graphics card and a Samsung SyncMaster 226BW. Pressing 'F6' at boot and changing --splash to --nosplash solves the issue.

All people that has a nvidia geforce 8xxx card on ubuntu 64bit won't see the usplash screen, this is bug 147623

Can someone reproduce the DVI-only-not-working bug with the latest Hardy alpha release? Thanks to everyone who work on this bug report.

Setting bug for expiration. Can someone confirm it for Hardy?

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!