I X going using nvidia driver by recompiling kernel, however got something else strange happening too. I got X going by recompiling 2.6.7.35 kernel with config file used for 2.6.33.4 kernel using my own custom version so as to not bork the standard /lib/modules/2.6.35.7 directory. Using my custom kernel everything seems to work great at the moment. However now when I boot with the generic-2.6.35.7 kernel and try to run I get a can't install error, Unable to load the kernel module 'nvidia.ko'. However if I do "lsmod" no nvidia display driver of any sort is displayed.
Earlier while trying to get X to work, had somehow got nvidiafb driver loading on bootup and it would not show up with "lsmod", and the only way I could get to remove it was to recompile the 2.6.35.7 kernel. However when I recompiled that kernel I didn't use a custom version or an older config file. couldn't get X to work with this kernel either. Don't know if it makes any difference, but I don't use initrd to boot when I compile my own kernel. LOL It's late, I feel like I'm writing a book here that nobody will make sense of, but maybe somebody can make sense of this

Just installed the latest update 15minutes ago, at first KDE would segfault just before the "K" logo appears on the splash screen.

However xfce and other desktops loaded as normal, to fix it (if your using the NVIDIA binarys). You simply reboot into run-level 3 or end all x sessions...

and then reinstall it; depending on where you saved it to
if needed regenerate an xorg.conf with
and KDE should be working again.
Smooth update.

I've got the same problem with thunderbird. Solved running ldconfig as root (without rebooting). Thunderbird and Firefox works good after that

Just a thought for people who have done upgrades and are having problems with X and KDE in particular. It may pay to look in /usr/lib/modules/extensions/ (/usr/lib64/modules/extensions/ in 64bit) to see if you have any old libraries hanging around.
I just amazed myself with the amount of clutter I had accumulated from previous driver installations.
I think anything older than Nov 17 05:25 can be safely deleted.

This works here, so I will keep Mesa 7.9.

I have a nVidia Corporation Quadro NVS 140M (rev a1) and don't use the blob.

Well, as I use some KDE apps but never the KDE desktop I'm not even sure I will disable compositing at time of upgrading to 13.2 - even if this issue is not solved by then

@allend: no clutter accumulated here but a fresh install of slackware-current.

Didier The fix in the changelog works here also on a nvidia 6150LE onboard chipset

I can live without 'special effects' for now

thanks
john

Not sure what driver X is trying to use for your card, but I have an IGP340M that requires the radeon driver, and none of the recommended fixes work. X does work with the VESA drivers, though.
You may want to try that.

Regarding the last line in your log, I think that just means that the server died while xinit was still running, so no server to connect to.

Thanks for your reply. I have been using an xorg.conf file for a long time and it has always worked perfectly. The driver is the open source "radeon" driver. I have tried everything I could from this thread and nothing has made any difference. I have put too much time into geting Slack the way wanted for over two years. I won't reinstall and will continue to try to find an answer. Disappointed, but hopefully some future updates will fix it. The rest of the system, including wireless, seems to work fine.

Anyone have any ideas of what else I can try I would really like to fix this if I can.

Thanks

Bob

Completed my second -current upgrade today. All is well. Many thanks to Robby and the entire Slackware team.

Just updated last night, so far everything works. Though in my minimal test setup some library needs to be added to start X.

In my main Slack, everything just works. Although I have noticed some minor differences on the fonts. I'll have to tweak it further.

to Bobnutfield, try recompiling kernel. Also couldn't get X to work and tried a lot of different things as mention in my earlier post. reconfiguring the kernel seems to fixed eveything. I first got X to work by just compiling the only the drivers I needed for my hardware, but still couldn't get the vmlinuz-generic-2.6.35.7 kernel to work. I just got done recompiling the generic kernel with the /boot/config-generic-2.6.35.7 file, didn't make any changes to it before compiling and X is working including kde. I know you don't have the same video card, as mine is a Nvidia gefore 6150se nforce430, but recompiling the kernel might work.

Everything is working for me (granted I did a clean install), but now my /dev/cdrom symlink to /dev/sr0 is not being created anymore.

I just finished round two of this massive update. This time, I finished without incident. The last thing I did was to upgrade the kernel and make a new initrd. I had been running 2.6.35.4. I usually build a custom kernel, but I've since given in to using the generic. Seems to work well!

Did a completely clean install from a dvd-burn of yesterdays 64 current tree. I have the same issue as rmjohnso with regard to /dev/cdrom, /dev/dvd symlinks not being there, but I've fallen in to the habit of just using /dev/sr0 ever since the libata change, so I didn't actually notice until (s)he posted and I checked.

1 members found this post helpful.

My symlinks are still there, but I did not do a clean install. They point to sr0 and sr1. One thing I noticed - KDE starts way quicker now than before. Booting period seems to be faster. I may be off on that though, since I don't reboot that often.