HELP display problems in Linux !!

[n0cmonkey]

Anything in the logs? What are you doing when it locks up?

 

[The Linuxator]

Once the terminal starts acting wierd my hands are locked I am forced to restart

 

[The Linuxator]

And if the problem was just an update issue , I have used yum to update everything and still nothing changed so I'll have to give up too much htime wasted on this issue.

 

[n0cmonkey]

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

Ok. Well, I tried to help. I was willing to break it down to moronic easiness levels, but you continue to thwart my attempt. Good luck. :beer:

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

Ok. Well, I tried to help. I was willing to break it down to moronic easiness levels, but you continue to thwart my attempt. Good luck. :beer:

Sorry for wasting your elitist time that could have been invested in bashing Linux noobs around OS forums, but after the updates I lost hope in solving the issue, and I realized that I don't really need a 6600 but it would have been nice, plus my friend called me and he needs to pickup his PNY 6600 so I tried my best. better luck next time. :beer: And thanx for all the support guys especially Drag and TGS.

 

[n0cmonkey]

Originally posted by: The Linuxator
Sorry for wasting your elitist time that could have been invested in bashing Linux noobs around OS forums, but after the updates I lost hope in solving the issue, and I realized that I don't really need a 6600 but it would have been nice, plus my friend called me and he needs to pickup his PNY 6600 so I tried my best. better luck next time. :beer: And thanx for all the support guys especially Drag and TGS.

You could have posted something useful instead of the drivel I had just responded to. Then you wouldn't feel like I'm bashing newbies.

 

[n0cmonkey]

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

How in the hell does the above post respond to these questions: Anything in the logs? What are you doing when it locks up? ?

It doesn't. It's useless, uninformative, and reeks of idiocy.

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

How in the hell does the above post respond to these questions: Anything in the logs? What are you doing when it locks up? ?

It doesn't. It's useless, uninformative, and reeks of idiocy.

Did you read the thread before you started unleashing your tongue , I have informed Drag and the others very well about the situtation go back a page. But since you know everything you didn't want to read something that is in the first page, so ... keep those insults coming :thumbsup:

 

[n0cmonkey]

Originally posted by: The Linuxator

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

How in the hell does the above post respond to these questions: Anything in the logs? What are you doing when it locks up? ?

It doesn't. It's useless, uninformative, and reeks of idiocy.

Did you read the thread before you started unleashing your tongue , I have informed Drag and the others very well about the situtation go back a page. But since you know everything you didn't want to read something that is in the first page, so ... keep those insults coming :thumbsup:

Yes, I read the thread. Now, what is locking your hands? Your parents? The police? Nice fuzzy handcuffs put on you by the big burly man in the next cell?

How does the terminal act wierd? You never provided details, only mentioned that X is providing corrupt output.

When does the "terminal act wierd"? Is it right after you kill X? If so, does it happen when you start in text mode instead of going to [XKG]DM?

Anything in the logs?

Simple questions that are not answered anywhere else, but you can't be bothered to answer them like an adult. Instead you act like a 3 year old so you can appear to be the victim of elitist venom.

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
Once the terminal starts acting wierd my hands are locked I am forced to restart

How in the hell does the above post respond to these questions: Anything in the logs? What are you doing when it locks up? ?

It doesn't. It's useless, uninformative, and reeks of idiocy.

Did you read the thread before you started unleashing your tongue , I have informed Drag and the others very well about the situtation go back a page. But since you know everything you didn't want to read something that is in the first page, so ... keep those insults coming :thumbsup:

Yes, I read the thread. Now, what is locking your hands? Your parents? The police? Nice fuzzy handcuffs put on you by the big burly man in the next cell?

How does the terminal act wierd? You never provided details, only mentioned that X is providing corrupt output.

When does the "terminal act wierd"? Is it right after you kill X? If so, does it happen when you start in text mode instead of going to [XKG]DM?

Anything in the logs?

Simple questions that are not answered anywhere else, but you can't be bothered to answer them like an adult. Instead you act like a 3 year old so you can appear to be the victim of elitist venom.

OK the best way to describe the terminal is that you are able to insert up to like 2 commands before the whole thing stops responding, I can't describe "not responding" in any more advanced technical terms. And as to the log files, I had just formatted the drive just before you asked about log files, and yes wither I kill X or not I still end up with a crashed system , I have already menioned this befiore if you have read carefully you would have found me saying things about how exactly X behaves in my system, and you would have read a post by me about how unstable X is( with that card) and the error message from X talking about the display driver problem.

 

[n0cmonkey]

Originally posted by: The Linuxator
OK the best way to describe the terminal is that you are able to insert up to like 2 commands before the whole thing stops responding, I can't describe "not responding" in any more advanced technical terms. And as to the log files, I had just formatted the drive just before you asked about log files, and yes wither I kill X or not I still end up with a crashed system , I have already menioned this befiore if you have read carefully you would have found me saying things about how exactly X behaves in my system, and you would have read a post by me about how unstable X is( with that card) and the error message from X talking about the display driver problem.

I read that stuff, but didn't see any mention of how it reacts when you startup without X. Not to mention single user mode. That would have been interesting too.

 

[The Linuxator]

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
OK the best way to describe the terminal is that you are able to insert up to like 2 commands before the whole thing stops responding, I can't describe "not responding" in any more advanced technical terms. And as to the log files, I had just formatted the drive just before you asked about log files, and yes wither I kill X or not I still end up with a crashed system , I have already menioned this befiore if you have read carefully you would have found me saying things about how exactly X behaves in my system, and you would have read a post by me about how unstable X is( with that card) and the error message from X talking about the display driver problem.

I read that stuff, but didn't see any mention of how it reacts when you startup without X. Not to mention single user mode. That would have been interesting too.

OK I understand, it's just like an infinite loop basically, it keeps attempting to start a GUI. I keep killing it, and it keeps coming back, till I use the telinit 3 command then it stops.

 

[n0cmonkey]

Originally posted by: The Linuxator

Originally posted by: n0cmonkey

Originally posted by: The Linuxator
OK the best way to describe the terminal is that you are able to insert up to like 2 commands before the whole thing stops responding, I can't describe "not responding" in any more advanced technical terms. And as to the log files, I had just formatted the drive just before you asked about log files, and yes wither I kill X or not I still end up with a crashed system , I have already menioned this befiore if you have read carefully you would have found me saying things about how exactly X behaves in my system, and you would have read a post by me about how unstable X is( with that card) and the error message from X talking about the display driver problem.

I read that stuff, but didn't see any mention of how it reacts when you startup without X. Not to mention single user mode. That would have been interesting too.

OK I understand, it's just like an infinite loop basically, it keeps attempting to start a GUI. I keep killing it, and it keeps coming back, till I use the telinit 3 command then it stops.

I don't know about Linux/x86, but I know there have been problems with funky consoles after killing X on other OSes on other platforms. My Zaurus doesn't properly echo characters back to the screen on the console if I kill X, but works fine if I don't start X.

You could try booting to init level 3 (changing the /etc/inittab default to 3 instead of 5 or whatever), if you have a similar problem with your new card.

 

[The Linuxator]

 

[drag]

With a graphical login it will attempt to restart X as many times as it feels like.

I Fedora and other RPM distros generally you go to 'runlevel 3' by issuing a telinit 3 command or editing the /etc/inittab and rebooting.

with Debian style systems you can go /etc/init.d/gdm stop to turn it off. Other graphical login systems include xdm (generic) and kdm (for kde).

I don't know about Linux/x86, but I know there have been problems with funky consoles after killing X on other OSes on other platforms. My Zaurus doesn't properly echo characters back to the screen on the console if I kill X, but works fine if I don't start X.

On most platforms you have to use the 'linux framebuffer' drivers to get a virtual console going in Linux (not in X I mean) directly into the video card's memory. For x86, due to legacy applications, they tend to use the msdos dos-style VGA compatability mode for 'VGA console'.

The vga console is generally more stable and somewhat accelerated compared to what is aviable in non-x86 systems. One of the small advantages to x86.

Some drivers though require linux framebuffer to be present for some functionality. I beleive most DRI drivers are like that. Xegl runs as a mesa-solo application and requires access to the framebuffer. If you want to play video or get graphics outside X (and sometimes in X, I beleive) you use can that also.

The propriatory Nvidia drivers don't use it though. They have their own api they use for the card that nobody realy knows much about how it works. There is a framebuffer driver that some distros try to start up called rivafb though. It sucks and can cause problems with X and nvidia drivers.

With Linux then you then can have the X 2-d driver, thel DRM/DRI driver, the VGA console driver, and the framebuffer driver. All of these fight for control over the video card simultaniously and can cause bad issues.

(which is why saying it's a 'driver' issue is not that clear since there are going to be 2-4 drivers running at any one time)

when you switch to console or whatnot your basicly disabiling control from one software stack, clearing the video ram, then transfering control over to a completely different driver system.

For instance often on my old laptop with the onboard Intel video running plain X drivers would work fine. However when using DRI (which used the framebuffer driver) it would cause some corruption and cause artifacts when switching to console. (this was solved over time however by newer driver revisions).

Obviously video drivers in Linux is a mess. Although they are able to acheive a high degree of reliability and performance with all things considured.

This is why things like modular X and XGL is important to the future of X and video in general.. it's goal is to eliminate the need for all the legacy systems and concentrate on one software stack, (for Xegl it's a modified opengl api (egl extensions, which were originally developed for display/resolution control for embedded platforms) utilizing glitz on a linux framebuffer/dri/mesa-solo arrangement. With the opengl api though it can be abstracted to be portable on any platform, even if they lack opengl drivers.. minimal requirements would be the ability to compile and run/display mesa.)

more and better details... http://dri.freedesktop.org/~jonsmirl/graphics.html

 

[silverpig]

Funny thing is your x800xl is supported just fine in linux 😛

It won't run as fast as it does in windows, but it runs just fine 🙂

As for your problem, I had this with an old old version of redhat before (like many years ago, and i think it was with an nvidia card). I think I just re-seated the card in the slot, and got a new cd and it worked, but I can't recall for certain.