VectorLinuxThis forum is for the discussion of VectorLinux.
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 think I did something wrong during the X configuration that I went through before starting a newly installed copy of VectorLinux, because I'm having a screen resolution problem. All I can get is 1024x768 and below, but my optimal resolution is 1680x1050. That's an X issue, isn't it? Where do I change it? I couldn't find what I needed in vasm.
Distribution: gentoo,RH, mandrake, debian, slackware, lfs, and more.
screen resolution bad
A recent linux distro install resulted in the same 1024x768, even with a detailed xorg.conf.
I panicked when booting into existing multiboot linux installations also gave me 1024.
Seems recent xorg insists upon reading the EDID from the monitor, even with a spelled out xorg.conf.
In my case, I was using a KVM switch to multiplex between computers, and it had somehow latched up.
Powering off EVERYTHING, especially the KVM switch, and powering up again cleared the latch up.
Inspect the file /var/log/Xorg.0.log, read it in detail, to discover your problem.
Try booting a live CD, if you don't multi-boot, to determine if it is hardware or your new install.