SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Unfortunately I cannot find where I got this particular listing from and it probably needs updating for Mesa 7.9, but it does offer clues for some devices and drivers.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
Just installed today's (22 November) updates and nothing has changed.
Mesa is still the problem. With the latest version installed nothing works.
Re-installed the older version (7.8.2) and now Xfce works, but KDE still
self-destructs after a few minutes.
Last edited by cwizardone; 11-22-2010 at 09:20 AM.
Just did a fresh install of current. After the initial boot I added a user and installed the nouveau git driver from extra. (upgradepkg --install-new)
The system starts X with desktop effects enabled. My onboard chipset is a 6150LE
My second attempt to startx failed with a lockup. Required poweroff to reset
Since then X has successfully started with desktop effects enabled and everything seems to be the same as when running the proprietary driver.
143 FPS on full screen glxgears with kmail running on one desktop & firefox running on other DT#3 blank
I will be pleased to report any changes.
thanks you RW and Alien
sorry forgot to thank PV -- U DA MAN PAT!
john
Last edited by AlleyTrotter; 11-24-2010 at 08:05 AM.
Just did a fresh install of current. After the initial boot I added a user and installed the nouveau git driver from extra. (upgradepkg --install-new)
The system starts X with desktop effects enabled. My onboard chipset is a 6150LE
My second attempt to startx failed with a lockup. Required poweroff to reset
Since then X has successfully started with desktop effects enabled and everything seems to be the same as when running the proprietary driver.
I will be pleased to report any changes.
thanks you RW and Alien
john
Glad to hear it's working! For reference, any time the driver is changed to or from nouveau a reboot is going to be required to either load or unload the kernel module. Due to the way the module uses Kernel Mode Setting, I don't think it's possible to switch back and forth without that reboot.
Just installed today's (22 November) updates and nothing has changed.
Mesa is still the problem. With the latest version installed nothing works.
Re-installed the older version (7.8.2) and now Xfce works, but KDE still
self-destructs after a few minutes.
I have the same problem...
But with compositing and/or desktop effects disabled KDE seems to be running without self-desctructing...
Maybe a desktop effect causes KDE to crash?
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,097
Original Poster
Rep:
Quote:
Originally Posted by kukukk
I have the same problem...
But with compositing and/or desktop effects disabled KDE seems to be running without self-desctructing...
Maybe a desktop effect causes KDE to crash?
Any ideas what to try?
Thanks for the tip. By turning off all desktop effects KDE 4.5.3 is running.
Have to say the fonts looked much better in Xfce for whatever reason.
Quote:
So at first I had some nasty problems, but then after reading alienBob's blog I found out I should have upgraded the aaa_elflibs too. Ok, after that I have a new problem: Xorg won't work as it should with nvidia driver.
this happened on my current x86 system the fix I had to do two things. deleted my .kde file then
this got kde going. but the next problem is the setting for composite kwin desktop when you do that it goes blank then goes black. I had to go in even though I was using nvidia and set it to direct render then it failed nice then reset to openglx and it is fixed. this is a kwin problem after the last upgrade and it did it for 4.5.1 to 4.5.3 . it has to do with kwin composite setting.
It works because your reading this. did not have the problem in x86_64 yet going to upgrade that now.
as posted earlier
Quote:
after reading that that told me why the package had failed with my nvidia card.
Thank you, but that has no effect on my particular problem. I had already deleted the ,kde directory, switched to the vest driver, and I do not have an nVidia chipset. Mine is an ATI (X1250), and I have never used compiz or any other com.positing desktop. KDE still crashes (after trying to start. The KDE. Splash screen starts, then crashes back to a terminal screen). The error is still "cannot contact kdeinit4!"
I am not sure it can be fixed now. I f no one else has any thoughts then I will just have to wait and see if a future update fixes it.
With today's updates had to delete my user ~/.kde to get kde to come up. was getting a kdeinit4 error. nevermind had to reinstall nvidia driver to get everything working again.
Last edited by colorpurple21859; 11-22-2010 at 07:09 PM.
Sorry, Drakeo, but my problem is nothing like that. As I said, I tried three window managers (KDE, lxde and xfce), so the problem doesn't look like WM related. As far as I know xfce and lxde don't use those shinny pretty compositing stuff like KDE, so...
slackpkg --reinstall kde and sit back then run pkgtool and run your setup script and select your window manger all the correct symlinks should be back. re run your nvida installer because you have a bunch of new links with the new xorg. let me know.
Did a fresh install of slackware64-current upgradepkg nouveau git driver from extra as root before running the Xwindows then rebooted
then created a user then ran kdm all went well nVidia Corporation G96 [GeForce 9400 GT) and also ran ok on my integrated 9600 GT.
hard to tell the difference between the proprietary and open source.
tried now and desktop effects with latest nvidia prop are super-smooth (maybe because I tried those for the first time also with the autogroup kernel patches of these days ), but I've got Eric's kde 4.5.3 installed, can't give confirmation for the standard 4.5.1, sorry.
slackpkg --reinstall kde and sit back then run pkgtool and run your setup script and select your window manger all the correct symlinks should be back. re run your nvida installer because you have a bunch of new links with the new xorg. let me know.
Did a fresh install of slackware64-current upgradepkg nouveau git driver from extra as root before running the Xwindows then rebooted
then created a user then ran kdm all went well nVidia Corporation G96 [GeForce 9400 GT) and also ran ok on my integrated 9600 GT.
hard to tell the difference between the proprietary and open source.
Once again, the problem has nothing to do with KDE. If I try XFCE or LXDE I get the same results when using NVidia driver: a black screen. If I go to a console and use 'ps', I can see X is running and the process that have been fired up after it runs. This even easier to see when I set KDE to be my WM, because I run 'ps' and I can see all the applications I let it load everytime I am on KDE (like kopete, qmmp, chromium,...).
So, KDE is runs fine; XFCE runs fine; and LXDE runs fine. The problem is between Xorg and the NVidia driver, I just don't know where/what I should do to fix it.
Again, if I use the 'nv' driver, Xorg runs without problems, no matter the WM I use. And there are no errors on Xorg.0.log or on the stderr when I try to use the NVidia driver.
ponce, yes, I REMOVED the nvidia driver, then reinstalled it and then I even rebooted the computer.
Oh guys, the latest NVidia driver is 260.19.21 (released on 11/11/2010). And that's the driver I was running before the upgrade of my slackware64-current
So, for now I am having to stick with 'nv'.
Any more hints on what I should do to fix this Xorg x Nvidia problem?
it can be you got some double card setup/SLI configuration? I got something like this and I had to create an xorg.conf (I used the vesa one and substituted the driver option from "vesa" to "nvidia").
but the /var/log/Xorg.0.log should list the attached display it uses (or some other hints).
Once again, the problem has nothing to do with KDE. If I try XFCE or LXDE I get the same results when using NVidia driver: a black screen. If I go to a console and use 'ps', I can see X is running and the process that have been fired up after it runs. This even easier to see when I set KDE to be my WM, because I run 'ps' and I can see all the applications I let it load everytime I am on KDE (like kopete, qmmp, chromium,...).
well what do you think how about posting your hardware or making sure your /etc/modprobe.d/blacklist nouveau
slackware-current is just that a test bed.
when I have run into your problem I go back and start reinstalling. slackpkg reinstall x, xap ap, d , etc.. sorry you are having the problem. you described the problem I had to the T when I upgraded with out reading.
Quote:
Once again, the problem has nothing to do with KDE.
but if you are actually running the latest current and read this thread from the beginning you would see it is a kde and mesa problem remeber current changes daily . if you want to go back just edit your slackpkg mirror to slackware 13.1 and slackpkg update slackpkg upgrade-all --install-new
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.