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.
When I first booted debian it attempted to load the window manager automatically, but failed, reverting to the shell. When I try to run startx from the shell I get a list of pairs of what appears to be hexidecimal notations separated by colons, followed by:
space: 24 wanted 32
Fatal server error:
waiting for server to begin accepting connections
xinit: Connection reset by peer (errno 104): unable to connect to X server
xinit: No such process (errno 3): Server error.
There has been bugs associated with the "intel" module which can lead to an X server lockup. Read through the link I gave you (last post) and the bug report (this post) -- see if it looks like what is happening to you re the posted logs.
This is quite an old bug as they go, but I'm seeing problems with intel cards again... particularly the newer cheapies.
Find out a more useful description of your gfx chipset in live mode, open a terminal, enter "lspci" and look for the entry about your gfx card. Vendor designations are designed to look exciting.
I understand there have been good results removing the intel package and just using the i810 package alone. People also disable DRI.
You did not "upgrade" from an existing installation.
Not real familiar with md5sum check
So the answer is "no" md5sum and sha1sum is a hashing method which allows you to check to see if the iso has become corrupted as you downloaded it. You did not perform the check, which means we don't know. You should google for how to do this.
I think 24X
Rapid burning can lead to subtle corruption in the disk. Never burn a data DVD higher than 8x ... never mind it takes a long time. If you have the patience, you can elect to make a "master" - which burns all the pits twice.
Is the fact that I prepared the CD in Windows relevant?
Not really. Some windows software can assume you want to DRM or encrypt the data you burn by default, but that would just make the disk unbootable. We usually assume you do not already have linux when you make an install disk. A program like Nero is usually reliable.
Considering the fast burn, there is reasonable suspicion that you may have weird errors on the disc. Remove the suspicion by running the checksum and burning a new disk at a low speed.
I don't really think this is what is wrong, but its good practice.