Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Newbie Problems With Absolute Linux


  • Please log in to reply
3 replies to this topic

#1 seedsofchaos

seedsofchaos

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southern Illinois
  • Local time:09:11 AM

Posted 28 November 2007 - 10:28 AM

Alright, so I'm a Linux virgin so forgive my ignorance. :flowers:

I just installed Absolute Linux on an old 64M system with a 667 processor. Checked out what the OS required and this seemed to fit well within the accepted specs.

So I installed and followed along with everything. I pretty much accepted all the defaults during installation. The only thing I didn't do was to configure a network.

I got to the end of it all and rebooted my system. I logged in as root and was presented with a message that said "You can now type startx to begin"

So I typed startx, thinking that would log me into the OS like the old "win" command did in DOS years ago.

I was returned a message that stated:

Fatal server error:
no screens found

waiting for xserver to begin accepting connections
giving up

xinit: connection reset by peer (errno104): unable to connect to x server
xinit: no such process (errno3): server error


Again, I'm new at this. I checked the Absolute website and found little help except a suggestion that this could be due to screen resolution..?

Any suggestions are much appreciated! :thumbsup:

BC AdBot (Login to Remove)

 


#2 seedsofchaos

seedsofchaos
  • Topic Starter

  • Members
  • 41 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Southern Illinois
  • Local time:09:11 AM

Posted 29 November 2007 - 10:05 AM

Figured this was an easy problem... hmmm... maybe not... Any suggestions at all?

I might just end up reinstalling and trying a different resolution as that's what the Absolute site lead me to believe was the problem.

#3 raw

raw

    Bleeping Hacker


  • Members
  • 2,577 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Texas
  • Local time:09:11 AM

Posted 29 November 2007 - 11:59 PM

Not familiar with Absolute at all, but some tips for you.
In my distro I can type: 'video' on the command line (logged in as root)
and it will open up the video configuration tool. On some systems it may be
xconfig, xfconfig, xfdrake (mandriva), log in as root and have a look in the
/usr/bin for programs along those lines. If not you might have to edit
your xorg.conf file by hand.

rawsig.png

 rawcreations.net          @raw_creations


Current systems: WHAT OS, BackTrack-raw, PCLinuxOS, Peppermint OS 6, Kali Linux

and a custom Linux From Scratch server hosting a bunch of top secret stuff.


#4 Joedude

Joedude

  • Members
  • 337 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sutton Coldfield, West Midlands, England
  • Local time:03:11 PM

Posted 30 November 2007 - 04:34 AM

Those errors come from the kernel, 104 is exactly what the description says. A peer process (usually associated with repositories for updating, whether apt, synaptic or yast) has shut it down. This means there is either a problem in the repositorie, or the package name submitted isn't written properly. This more than likely is from a corrupt install or an outdated repo (check the date on your distro).

The errorno3 is telling you that xserver isn't playing nice. You need to update your drivers.

Of course, there are other possibilities, these are just the ones I would check first.
If someone tells you to su rm -rf /
DON'T DO IT!!!!
Be in the know, Bash smart!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users