I made some progress - I was able to boot into text mode after modifying the boot parameters - adding 'text' and removing the 'splash', and specifying the vesa mode.
At this point, I was able copy files to this system from another, using scp. I then copied the experimental driver and my old xorg.conf file to the sytem, saved the initial xorg.conf to a backup, copied my xorg.conf file to /etc/X11, and tried to install the driver. The install failed, indicating that "xserver-xorg-core conficts with xserver-xorg-video-4'. I'm not sure how to solve that problem! Even though I knew the old driver wouldn't work, I tried running startx. As expected, it failed, but I will provide the Xorg.0.log file that resulted. Peter On Wed, Jan 14, 2009 at 3:49 PM, Tormod Volden <bugpost.tor...@gmail.com> 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. > -- No signal with Samsung SyncMaster 750s and ProSavage8 https://bugs.launchpad.net/bugs/294899 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
