Xorg-server 1.7.6 was released. There are two release candidates to mesa: 7.7.1 and 7.8. Sorry, I hadn't time to see the changelogs, but maybe some mix with kernel 2.6.33.1 and xf86-video-nv-2.1.17 can work.

Perhaps the culprit was 2.6.33, as even Linus was really pissed with it: http://lkml.org/lkml/2010/3/4/299

Yeah :0 I read that mailing list thread about a week ago (checking again for updates right now) and Linux was really unglued over the whole thing. It's a painful read, that thread.

P.S. I have pondered in the past, if I were some of the people in such threads, if I would eventually just say **** this, I don't need this crap. It gets pretty heated.

I haven't been able to get to a DE since the "Big One" in -Current64 but this is Current and glitches are expected.
However:
When they do fix it, I'm sure I'll love it.

sys:
2 monitors -twinview
1 Nvidia card
AMD Phenom II X4 945
Asus mobo
8 gb ram

And this makes me wonder how much respect the COMMUNITY has for the MAN who created this wonderful COMMUNITY? This situation is truly a shame!

But what I really need to know, setting all of my previously bad comments aside, How do I now fix my installation to get X running again? I've installed a second system in this computer using the same hardware. But X simply won't start on my main system. Someone please help me if you have answers. What packages do I need to return my system to it's previous state?

Xavian-Anderson Macpherson
Shingoshi

@ Shingoshi,

if you merely wish to see if you can get X to start (all other problems aside) you might try what I am currently doing: revert your packages:

xorg-server
xf86-input-mouse (if you use that)
xf86-input-keyboard (if you use that)

Revert those to their prior versions (such as the stable Slack-13.0 versions) and see if X will start.

HOWEVER: I/we really do not know exactly WHY your X will not start -- my suggestion here assumes the problem is VERY MUCH like my own problem; but if it is not, then this may not work. It could be your kernel; it could be another hardware driver; it could be myriad other things, or a combination of things, that are giving you problems -- we don't know. Best place to start, is your log files of course, to see if you can identify exactly what is the problem.

Cheers
Sasha

I will try what you've instructed here. If it does or doesn't work, I will let you know. If it doesn't, I will definitely post my logs. The one thing that kept coming up was the drivers weren't being recognized. Kept getting messages about them missing. But I will try this and something else which I may have forgotten to do and see what comes of it.

Xavian-Anderson Macpherson
Shingoshi

Shingoshi,

May be you'll find this article interesting. I didn't understand everything to say the least but anyhow I'm going to try try 2.6.34-rc1 against libdrm-2.4.18 as well as the last snapshot of libdrm just for fun...

Oh and Sasha, sorry for hijacking your thread again

Sasha, have you tried the latest nvidia drivers (195.36.15) and had any luck?

Nope, as yet I have not used the newest nvidia release at all; have been busy with working on some other things here.

When I do get around to downloading it, I'll be sure to try it with the new Xorg as well as my existing one. But, I did read the ChangeLog for that new driver release (a few days ago) and I don't recall reading that there was anything particularly interesting about it, other than the fan-control bug-fix.

Do I recall wrongly? I.e. is there anything about it that maybe I missed, that hints that it might work?

Thanks,
Sasha

I didn't see anything specific, but the patching that was needed to install the drivers against 2.6.33 seems to have been fixed. Who knows how good the changelog is anyways.

compiled the libdrm-2.4.19 mesa 7.9 going to play with the open 3d driver see what it does.
Slackware64-current uses mesa-7.7 but mesa-7.7 requiers libdrm-2.4.19 but Slackware64-current.
libdrm-2.4.18 wonder how they got all of mesa to compile.

They didn't they just --disabled-gallium .
they work fine it has been certified lol

I couldn't start X with the latest packages of Slackware 13.2 (on March 2) so I rolled back to those in 13.0. Determined to get the latest working I downloaded the source for all of X from X.org, which worked.

Where does your Xorg.0.log end? Mine ended at the 'setting physical screen size'.

I tried to post this last night. But LinuxQuestions is one of those forums which doesn't work inside of Thunderbird using the Thunderbrowse extension. So I'm finally posting it now.

I just tried to build the drivers for this machine, but I get an error about the gcc version being incorrect. So I don't know what to do about that. But frankly, I've never been able to build the drivers on this machine. I don't know if it's due to my board or not. But it really doesn't matter now. All I ever wanted was my desktop back. And now I have it.

When did Slackware-13.2 become officially released? The main page doesn't show it.

Xavian-Anderson Macpherson
Shingoshi

I couldn't build the X driver, that is to say nouveau_drv.so yesterday or the day before after upgrading to 2.6.34-rc1 (BTW 2.6.34-rc2 is out, but I didn't see anything about nouveau in the changelog). But as I could do it a few days ago (against 2.6.33 though), I suspect this be because of a change in a source file (as I pull a snapshot from the git repository). Will try again later.

Sorry to reply a old topic

I solved my problem switching the second monitor from left to right.

On left my mouse goes crazy, but with second monitor on right, my mouse works fine on second monitor.