Comment 21 for bug 294899

Oh, good. I was wondering whether there was a way to boot in text
mode. That will make it MUCH easier to proceed!

Also removing the splash progress bar might help, I'll see.

I'll be home in a couple of hours to try this! Then I can try either
the new driver, or my old xorg.conf file, or both. I expect to be able
to proceed Ok.

What the monitor appears to do during its attempts to work is to turn
on, display the warning box about mode incompatibility somewhere on
the screen, turn its 'on' LED off, and repeat the same thing at random
parts of the screen ... apparently forever in this case.

Thanks!

On Wed, Jan 14, 2009 at 3:49 PM, Tormod Volden <email address hidden> wrote:
> If you add "text" to the boot parameters (the kernel line, F6 in the CD
> boot menu), it will not start X. You can then log in on the console and
> install the driver like mentioned above. To start X an X session, type
> "startx".
>
> I don't think the driver is trying out different modes, it's just the
> monitor trying to match the signal from the driver. In principle the X
> server will ask the monitor about which modes it accepts, and tell the
> driver to use the "best" mode (usually the highest resolution or the one
> the monitor designates as "preferred"). If we can get the modedebug
> Xorg.0.log, we can see the details of this communication.
>
> But not being able to switch the console might indicate more issues than
> just a wrong mode. You see the usplash progress bar until X should
> start, right? Try also to remove the "splash" word in the boot
> parameters - sometimes usplash interferes with the console modes and
> corrupts the screen.
>
> --
> No signal with Samsung SyncMaster 750s and ProSavage8
> https://bugs.launchpad.net/bugs/294899
> You received this bug notification because you are a direct subscriber
> of the bug.
>