On Tue, Oct 03, 2006 at 10:41:25PM +0100, Wayne Stallwood wrote:
On Mon, 2006-10-02 at 20:00 +0100, cl@isbd.net wrote:
If I boot in Suse's "safe mode" the normal login: prompt appears and, in addition, I can log in and run startx to get X windows up.
So, it's all working pretty well really except for the default console mode. Does anyone have any ideas how to remedy that?
I am unsure what the Suse safe mode boot does, but it's a pretty safe bet that the standard Suse boot enables the framebuffer console and the safe one doesn't (amongst other things).
I wouldn't mind betting that's where your problem is. Either your graphics chipset doesn't like vesa framebuffer modes, the kernel doesn't have the correct framebuffer modules or the default resolution of the framebuffer is putting your monitor out of signal range (although normally the monitor tells you this)
Yes, you're probably right.
So a quick fix would be to add a vga=normal to the /boot/grub/menu.lst file for the default boot line.
OK, thanks. If I stay with Suse I'll investigate. However as I'm currently playing 'distribution a minute' I'll leave it for the moment as it's not really an issue now I have a workaround.
Thanks for the ideas.
[snip further info]