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.
Wow! This morning was a ride. I went o bed while this massive update was being done. Got up this morning and rebooted. Good thing I have another Slackware install to fall back on whilst I research problems.
Thanks to all of you that posted - both the problems and solutions. I was up and running in seconds.
Smooth as silk for me. Just needed to reinstall the nVidia proprietary driver to get KDE up.
Is it my imagination, or just the red wine I drank while waiting for the update to complete, that LQ looks a little different in Firefox with the new font packages? HIC.
Ugh!
X crashes and reports a segmentation fault, address nil.
I've been using the generic Radeon driver without any problems, until now. Looks like it will be winblows until I figure out the problem.
Any resolution for this issue? I got the same.
Code:
[ 369.902] (II) AIGLX: Screen 0 is not DRI2 capable
[ 369.902] drmOpenDevice: node name is /dev/dri/card0
[ 369.902] drmOpenDevice: open result is 14, (OK)
[ 369.902] drmOpenByBusid: Searching for BusID pci:0000:02:00.0
[ 369.902] drmOpenDevice: node name is /dev/dri/card0
[ 369.902] drmOpenDevice: open result is 14, (OK)
[ 369.902] drmOpenByBusid: drmOpenMinor returns 14
[ 369.902] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[ 369.902] drmOpenByBusid: drmGetBusid reports pci:0000:02:00.0
[ 369.911]
Backtrace:
[ 369.911] 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80e6cfb]
[ 369.911] 1: /usr/bin/X (0x8048000+0x5daf5) [0x80a5af5]
[ 369.911] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xffffe40c]
[ 369.911] 3: /usr/lib/xorg/modules/extensions/libglx.so (0xb7308000+0x4079c) [0xb734879c]
[ 369.911] 4: /usr/lib/xorg/modules/extensions/libglx.so (0xb7308000+0x37838) [0xb733f838]
[ 369.911] 5: /usr/bin/X (InitExtensions+0x9d) [0x80cb82d]
[ 369.911] 6: /usr/bin/X (0x8048000+0x1ad22) [0x8062d22]
[ 369.911] 7: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb738fc66]
[ 369.911] 8: /usr/bin/X (0x8048000+0x1aaa1) [0x8062aa1]
[ 369.911] Segmentation fault at address (nil)
[ 369.911]
Fatal server error:
[ 369.911] Caught signal 11 (Segmentation fault). Server aborting
[ 369.911]
[ 369.911]
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 369.911] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 369.912]
[ 369.917] disable FP1
[ 369.917] (II) RADEON(0): RADEONRestoreMemMapRegisters() :
[ 369.917] (II) RADEON(0): MC_FB_LOCATION : 0x1fff0000 0xf7fff000
[ 369.917] (II) RADEON(0): MC_AGP_LOCATION : 0x27ff2000
Smooth as silk for me. Just needed to reinstall the nVidia proprietary driver to get KDE up.
Is it my imagination, or just the red wine I drank while waiting for the update to complete, that LQ looks a little different in Firefox with the new font packages? HIC.
My thanks to Pat and the team.
Nah, I didn't drink any red wine and I can tell a big difference. Just trying to determine if I like the difference or not.
not sure if it applies, but remember also to remove the obsoleted xf86-video-radeonhd, as Robby suggests in the link above.
Unfo, disabling the compositing helped me just to start X with vesa driver.
Didn't know xf86-video-radeonhd is obsolete, the ChangeLog doesn't say anything.
Anyway, thanks for the ideas but neither of the above helped me.
x blew up on me. I rebooted into init3, ran startx, and it tells me taht the server has a video driver abi version that this driver does not officially support. Then I get a fatal error, no screens found. I tried reinstalling the Nvidia drivers from Slackbuilds.org... no good. Help!
Are you running at least a 2.6.35 kernel? I know I don't upgrade kernels real often, and when I first used Robby's new xorg packages I had to first update the kernel. The nvidia driver I am using is 256.52. I just run the script, not the slackbuild version.
Yes, I'm running the .35 kernel. But I can't get a graphical login screen with the nv drivers, either. I ran rmmod to ditch the nvidia module, changed xorg to the nv drivers, and I got a little white box at the top of my screen with the following:
Code:
kstartupconfig4 does not exist or fails. The error code is 127. Check your installation.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Original Poster
Rep:
Kiroff,
Looks like we have the same card and the same problem.
I disabled compositing, but it didn't make a bit of difference.
Up until last night, I have always downloaded the 'current' files to my hard drive and installed them from there. Last night I used slackpkg to do the upgrade so my 'current' files, prior to last night, were untouched.
So, I used upgradepkg to re-install the 'x' files from my 'current' 'x' directory and at least now I can use Xfce. I haven't tried KDE, yet.
I'll wait a few more days before trying to install last nights upgrades, again.
Cheers!
Last edited by cwizardone; 11-15-2010 at 10:20 AM.
Reason: Typo.
Did a bit more google searching, was I supposed to allow it to upgrade aaa_elflibs? I'd just do it, but my google searching also suggested that it might be a bad idea to upgrade that package after upgrading the other ones. Someone please advise...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.