Re: Display Problems


"imotgm" <imotgm_REM@xxxxxxxxxxxxxxxxx> wrote in message
news:pan.2005.12.09.15.04.56.578887@xxxxxxxxxxxxxxxxxxxx
> On Fri, 09 Dec 2005 09:37:07 +0000, Ash wrote:
>
>
>>> This also makes no sense to me. The directory is /etc/X11, and it
>>> exists,
>>> or does not. If it shows up in the GUI, it is there, and must be present
>>> from the console also.
>>
>> i typed:
>> cd /etc
>> then i typed:
>> cd /X11
>
> This should not work. This command asks to change to a directory "X11" in
> the root directory, ie / and, as there is no such directory, you should
> get the error message that you, in fact, did get.
>
> If you are already in the /etc directory, first type "ls" (small L, s)
> <Enter> to get a list of all files and directories in /etc. Toward the end
> or the list should be "X11/" , the trailing / denoting that it is a
> directory.
>
> Or issue the command;
>
> ls -l | grep X11 <Enter> # That's a small L after the -, and a pipe |
>
> and it will return:
>
> drwxr-xr-x 16 root root 4096 Sep 21 17:36 X11/
>
> showing that the directory exists, and is owned by root, with group root.
>
> That, being there, the command to enter X11, would be;
>
> cd X11 <Enter> # Note, no leading /
>
> or
>
> cd ./X11 <Enter> # Note, the "." in front of the / ./ = from this
> # directory
>
>> and got the error message file or folder not found (or something like
>> that).
>> although i could find the /X11 directory in GUI mode.
>> i have also tried :
>> cd /etc/X11
>
> This should work. Are you sure you typed that with an X rather than x?
>
>> and i got the error message (file or folder not found).

well it was stupid of me to assume that linux would be anything like DOS i
suppose :P

>>
>> I'm not stupid.
>
> If that's meant for me, it's wasted. I neither stated, nor implied, that
> you were. I'd bet on frustrated, though. If it's a little self assurance,
> in the midst of the frustration, by all means, vent away.

well i was doing just that, as i was beginning to feel stupid....

>
>> according to the command prompt the folder is not there!
>
> And we need to find out why that is. Let's take a moment to assess the
> situation.
>
> You are at home, somewhere in OZ. I am at home in Illinois, smack in the
> middle of the U. S. of A. You have a problem, I do not. I have the same
> model GeForce 6600 graphics card you have, and had, in the past, the same
> problems that you are encountering now. After doing some research, I found
> the solution to my problem, and logic dictates it should also be the
> solution to your problem. Assuming, for the moment, that you do not have a
> defective card, if I tell you what I did to solve the problem, and you
> apply, exactly, the procedure that I relay to you, the results should be
> the same. If the results are not the same, something in the procedure is
> different. Either I am missing something, in my instructions, you are not
> following them exactly, or there is something, as yet unknown, that is
> preventing them from working, after having been properly applied. As yet,
> we can not rule out the possibility of a defective card, a defect in some
> other hardware, or a corrupt piece of software interfering with an
> otherwise proper fix.
>
> If we follow a very methodical, step by step, procedure, we should be
> able to ascertain which of the above possibilities is at fault, and remedy
> the situation. If you get all frustrated, give up, and quit, you are not
> going to be a happy individual. I, on the other side of the world, will be
> largely unaffected. I'm not the one with the problem. As long as you're
> willing to post the information I, or anyone else that reads these posts,
> ask for, I'm happy, as a clam sucking ditch water, to keep on helping you
> to solve your problem.
>
> Maybe someone else will see something in those posts that both of us miss,
> and offer a perfect solution. That's how these groups work. Stay with it,
> and you win, twice. You get your problem fixed, and you learn some nifty
> *** in the process.

what im going to try is, installing the lastest drivers. hopefully that will
fix the problem.
ill get back to you soon.

>
>>>> what now?
>>>
>>> Copy paste the contents of your xorg.conf to your next post, so that we
>>> (the group) can read it directly to see what errors might be present.
>>
>> ok if you think it will help. I'll do that next time I'm not frustrated
>> with SUSE.
>
> I certainly think it will help, or I wouldn't have asked you to post it.
> It positively can't hurt.
>
> --
> imotgm
> "Lost? Lost? I've never been lost... Been a tad confused for a
> month or two, but never lost."
>
>


.