Well I'm back from my rather busy week-end (totally away from computers) and, after a few more clicks, the Suse 10.1 installation on my new hardware has completed.
However it does have on little oddity, when booted/rebooted it doesn't show anything on the display. It is working though as I assumed there was a login prompt and was able to login 'blind' as root and shut the system down. All the dmesg stuff appears it's just after that the display goes.
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?
On 10/2/06, cl@isbd.net cl@isbd.net wrote:
However it does have on little oddity, when booted/rebooted it doesn't show anything on the display. It is working though as I assumed there was a login prompt and was able to login 'blind' as root and shut the system down. All the dmesg stuff appears it's just after that the display goes.
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.
Do the virtual consoles work? Can you SSH in from another computer?
Tim.
On Tue, Oct 03, 2006 at 09:20:37AM +0100, Tim Green wrote:
On 10/2/06, cl@isbd.net cl@isbd.net wrote:
However it does have on little oddity, when booted/rebooted it doesn't show anything on the display. It is working though as I assumed there was a login prompt and was able to login 'blind' as root and shut the system down. All the dmesg stuff appears it's just after that the display goes.
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.
Do the virtual consoles work? Can you SSH in from another computer?
Well I assume the virtual consoles work, it would be a little difficult to check blind. The virtual consoles work if I boot Suse in safe mode.
I'm pretty sure that Suse disables the ssh daemon by default so you can't ssh into the system unless you re-enable sshd.
Apart from this little oddity it's all working very well, I copied my home directory across and my FVWM2 set up works perfectly. I'm actually rather impressed by how easy it has been to configure it.
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)
So a quick fix would be to add a vga=normal to the /boot/grub/menu.lst file for the default boot line.
It might also be worth taking out any options for quiet and splash if they are present (I suspect they are)
If that works then a better fix would be to find out why the framebuffer mode doesn't work on your hardware, that way you get the pretty boot screens back.
As always when modifying a bootloader configuration file, take special care. I have never seen a Suse installer created menu.lst file so I cannot tell you exactly where to put these options. If you get it very wrong then you may not be able to boot the system again without a recovery disk.
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]
-
cl＠isbd.net -
Tim Green -
Wayne Stallwood