SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am using Suse 10.0, or rather: just installed it again. I have a Matrox G550 graphics card with two Acer monitors attached, and with some configuring dual head Xinerama mode works.
But there is another problem:
When I start Suse in normal mode, pressing Ctrl + Alt + F2 does not give me a console, but a monitor problem "Input not supported". The same happens when I shutdown the operating system. It does shut down, but the monitor does not show anything useful during the process.
Interestingly, it does not do that in FailSafe Mode, there everything works fine. So I thought that probably it is some service that usually starts but is skipped in FailSafe Mode. By the way, it is not a problem caused by dual head mode, since it is already there before I configure dual head. Even on the one monitor that the OS automatically recognizes.
I also thought that maybe it has to do with ACPI, so I installed the whole OS again without ACPI. Same problem.
Anyone out there who can think of an approach to this?