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.
Try without xorg.conf first. Slackware's X.Org does not need one.
What you should also try is to replace the mesa-7.9 package from slackware-current with the mesa-7.8.2 package which was uploaded here today by Pat Volkerding: http://slackware.osuosl.org/unsupported/mesa-7.8.2/
For some Ati and Nvidia cards (using the opensource drivers) the slightly older version mesa package may just work.
If that package works for you, please report it here!
Eric
Eric, it work, i have downgrade the mesa from 7.9 to 7.8.2 and my X.Org start work again. Thanks very much.
And about my last post, i know the Slackware's X.Org don't use anymore xorg.conf, i think since was integrated hal on it. Like i said previous in the other post(in page 2), i just try put it work again to check if i try force use vesa, it work again! But i think you know, it don't work.
Well like i said before, thank you very much, and thank you Patrick to upload the mesa-7.8.2 package, maybe it can be put on /pasture on the next update
Click here to see the post LQ members have rated as the most helpful post in this thread.
Well like i said before, thank you very much, and thank you Patrick to upload the mesa-7.8.2 package, maybe it can be put on /pasture on the next update
Well, I hate to think that we would have to keep that around for very long, but we seem to have a situation where some cards only work with Mesa-7.9, and some cards only work with Mesa-7.8.2. And, from what I gather, some Radeon cards only work if KMS is enabled, while others only work if KMS is disabled.
If anyone thinks Wayland will have fewer problems like this, I have a bridge to sell you.
After upgraded the X crashed too.
It complained that missing liblzma.so.0, so i made a link to liblzma.so.5 and it worked.
This is broken - that's not the solution. Upgrade aaa_elflibs.
Quote:
1. /dev/shm missing, revert to udev-153 fixed
This *is* a bug, and I have no idea how it happened - the build script says it didn't happen, but the package says it did.
In the meantime, do this:
Code:
mkdir /lib/udev/devices/shm
and all will be fine.
Quote:
2. the rc.M script section of gdk-pixbuf2 error
g_module_open() failed for /root/--update-cache: /root/--update-cache.so: cannot open shared object file: No such file or directory
You seem to have missed upgrading something - that's not reproducible on a properly upgraded system.
Quote:
3. bluetooth mouse not worked, revert former version of bluez fixed
Without more information, I can't say much about this one. I'm obviously skeptical though, given the diagnosis implied by #2.
Well, I hate to think that we would have to keep that around for very long, but we seem to have a situation where some cards only work with Mesa-7.9, and some cards only work with Mesa-7.8.2. And, from what I gather, some Radeon cards only work if KMS is enabled, while others only work if KMS is disabled.
If anyone thinks Wayland will have fewer problems like this, I have a bridge to sell you.
Well you could put in /pasture until i have some money to buy a new video card, lol.
I just have bought a new pc after 5 years using a P4 2.8Ghz 1Gb DDR1 )
FYI, if for whatever reason you don't like the new fonts or how they are being rendered, reverting freetype to the previous installed version (2.3.12) will restore them to their previous state.
Guess I'll make my first post today. Upgrade to -current, no problems so far except X failed to start. My solution was found in ChangeLog.txt.
Code:
x/mesa-7.9-i486-1.txz: Upgraded.
I was on the fence with this upgrade, and in fact it sat in /testing for
days with mesa-7.8.2 queued instead. But it seems the Intel driver really
does need this version of Mesa or there are major problems with compositing
(most of them leading to an X server crash).
If X crashes at start, try disabling compositing. Create a file named
/etc/X11/xorg.conf.d/disable-composite.conf with this in it:
Section "Extensions"
Option "Composite" "Disable"
EndSection
The machine that had issues here was using an onboard nVidia 6150SE.
Using the nv, nouveau, or even the vesa driver, X crashed at start unless
compositing was disabled. However, everything works perfectly when using
the binary nVidia drivers, and odds are that most users with decent nVidia
hardware are doing just that. So, that's the situation with nVidia and
Mesa as observed here for now. Hopefully the defaults will work better
soon, but meanwhile if you have nVidia hardware you may have to either
disable compositing or obtain and use nVidia's binary drivers.
This was with a Compaq Presario with nVidia Corporation NV17 [GeForce4 MX 440] (rev a3) on the motherboard.
In the past nVidia's driver gave me problems on this machine so they were not installed. Composting was enabled and working before the upgrade.
Last edited by chrisretusn; 11-23-2010 at 06:44 AM.
I upgraded aaa_elflibs, but can't start X yet, because of the errors:
SIGTERM to children
/home/user/.kde/socket-user/kdeinit4_0: No such file or directory
FAILED to connect to socket /tmp/dbus-62mVzAerCW
In this case, the correct solution is to upgrade aaa_elflibs. That package should always be upgraded if you're tracking the development tree of Slackware.
Sorry, to sound like a complete newb... but how is that done?
Both `upgradepkg` and `slackpkg` are returning a "package not found" error.
Do i manually download it from an ftp mirror and use pkgtool to install it?
FYI, if for whatever reason you don't like the new fonts or how they are being rendered, reverting freetype to the previous installed version (2.3.12) will restore them to their previous state.
great! I just signed up to LQ to see if there was a way to revert to previous fonts but how long will it last? ahh
FYI, if for whatever reason you don't like the new fonts or how they are being rendered, reverting freetype to the previous installed version (2.3.12) will restore them to their previous state.
Reverting isn't the ideal solution. Reconfiguring to get a good result is a better way forward. I've just symlinked "10-no-sub-pixel.conf" into /etc/fonts/conf.d and things already look a little bit more like they used to and closer to my tastes, but it still doesn't look quite as clear as it did before (unless I'm imagining it - hard to say without a side by side comparison).
Not knowing exactly what's changed doesn't help, but I daresay I'll get to something I can live with after some experimentation.
Sorry, to sound like a complete newb... but how is that done?
Both `upgradepkg` and `slackpkg` are returning a "package not found" error.
Do i manually download it from an ftp mirror and use pkgtool to install it?
You need to download this one manually and install. The reason it does not show up is because it is listed in the Slackpkg Blacklist file. It will never come up for upgrade.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Mesa was the problem
)
but how long will it last? ahh
