Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 m using RH 9 and facing hell lots of problems regarding GUI... At first during installation i was unable to install in GUI mode... The screen turned blank... Then i used the following command...
boot: linux lowres
it worked out fine, but after completing the installation, i was unable to start X server again... Then i opened the file /etc/X11/XF86config and kept the resolution as 640 * 480... The GUI came back but at very poor resolution....
And ultimately my problem is that if i increase it from 640 * 480, and run startx, the same problem arises again, ie the screen turns blank and a message "Sync. Out of Range" flashes on the screen... Even i tried to change the horrizontal and veritical sync on XF86config, but still i got same bitter taste...
My monitor is SAMTRON from Samsung... And my video card is S3 ProSavage KM 133...
Following are the copy of my XF86config file for additional information:-
# RgbPath is the location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use:
# Option "XkbOptions" "ctrl:nocaps"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
# If the normal CorePointer mouse is not a USB mouse then
# this input device can be used in AlwaysCore mode to let you
# also use USB mice at the same time.
Option "Protocol" "IMPS/2"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
It was really a big and 1.5yr old problem for me... I tried to find out many solutions for that, but unfortunately, nothing worked for me... I changed it to "vesa", coz i got this instruction on search result... Hope it may work for u if ur video card is S3ProSavageKM133...
However i didnt try with something other than vesa... I dont want bitter taste again... Now i m enjoying the sweetness... Hope u can enjoy the same....
vesa is an Xorg driver for generic VESA video cards. It can drive most
VESA-compatible video cards, but only makes use of the basic standard VESA
core that is common to these cards. The driver supports depths 8, 15 16
The vesa driver supports most VESA-compatible video cards. There are some
known exceptions, and those should be listed here.
Please refer to xorg.conf(5x) for general configuration details. This
section only covers configuration details specific to this driver.
The driver auto-detects the presence of VESA-compatible hardware. The
ChipSet name may optionally be specified in the config file "Device" sec_
tion, and will override the auto-detection:
Type man vesa in a terminal to view the entire manual. Vesa is a generic Video driver that works with most vesa compatible video cards. Sometimes it may just be able to run your videocard. To get improved/better/max performance it's advisable to use a driver provided by the vendor of the particular videocard. I guess you have a machine with an Intel Onboard Video Device (I guess you have an Intel 845/865/........ motherboard) The driver for all these motherboards is now supported by Intel and is known as the i810 driver. That's why you have i810 there.
Post what exact problem you are facing.
Hope this helps!
I asked just as to be knowledgible in order to face future problems.yes i have Intel D865GBF moterboard.
I am sorry if it made you pay more attention and pain than required.
My problem is resolved now.