LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-15-2010, 03:17 PM   #46
gbschenkel
LQ Newbie
 
Registered: Nov 2010
Location: Faxinal do Soturno, RS - Brazil
Distribution: Slackware of course
Posts: 6

Rep: Reputation: 0
Thumbs up Mesa was the problem


Quote:
Originally Posted by Alien Bob View Post
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.
Old 11-15-2010, 03:22 PM   #47
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 861

Rep: Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680Reputation: 1680
Quote:
Originally Posted by gbschenkel View Post
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.
 
5 members found this post helpful.
Old 11-15-2010, 03:24 PM   #48
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 1,913

Rep: Reputation: Disabled
Quote:
Originally Posted by zhoun View Post
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.
 
Old 11-15-2010, 03:34 PM   #49
conraid
Member
 
Registered: Feb 2008
Location: Leghorn, Tuscany, Italy
Distribution: Slackware
Posts: 78

Rep: Reputation: 28
Quote:
Originally Posted by rworkman View Post
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.
This bug seems to be only in 64bit udev package. 32bit package is ok
 
Old 11-15-2010, 03:39 PM   #50
gbschenkel
LQ Newbie
 
Registered: Nov 2010
Location: Faxinal do Soturno, RS - Brazil
Distribution: Slackware of course
Posts: 6

Rep: Reputation: 0
Quote:
Originally Posted by volkerdi View Post
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 )
 
Old 11-15-2010, 03:45 PM   #51
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 745

Rep: Reputation: 64
After update, on 64bit KDE throws me back to the KDM login screen when restoring a minimized app (and sometimes by other causes, seemingly at random).

With the following in /var/log/messages:
Code:
Nov 15 22:36:20 chacha kernel: [drm] Resetting GPU
Nov 15 22:36:21 chacha acpid: client 2554[0:0] has disconnected
Not sure if this is related, but I never noticed these lines before in Xorg.0.log:
Code:
[   207.091] (WW) RADEON(0): DRI init changed memory map, adjusting ...
[   207.091] (WW) RADEON(0):   MC_FB_LOCATION  was: 0x00ef00d0 is: 0x00ef00d0
[   207.091] (WW) RADEON(0):   MC_AGP_LOCATION was: 0x003f0000 is: 0x00030000

[   207.410] (EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
[   207.426] (EE) PreInit returned NULL for "Device USB Device"
Graphics:
Code:
lspci|grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV730XT [Radeon HD 4670]
Downgraded mesa but the same happens.

Anyone?

[edit] Enabling KMS solved it!

Last edited by BroX; 11-16-2010 at 06:16 PM. Reason: added lspci; spelling; solved
 
Old 11-15-2010, 03:53 PM   #52
Lucifer4o
Member
 
Registered: Mar 2010
Distribution: Slackware Current
Posts: 50

Rep: Reputation: 15
I have a problem ... after fixing problems with all else, a lost the wi fi card ...
 
Old 11-15-2010, 04:21 PM   #53
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
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.
 
2 members found this post helpful.
Old 11-15-2010, 05:18 PM   #54
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 475

Rep: Reputation: Disabled
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.
 
1 members found this post helpful.
Old 11-15-2010, 05:33 PM   #55
Intel_
Member
 
Registered: Mar 2009
Location: Bulgaria
Distribution: Slackware
Posts: 103
Blog Entries: 5

Rep: Reputation: 20
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

any ideas, please?
 
Old 11-15-2010, 05:36 PM   #56
coralfang
Member
 
Registered: Nov 2010
Location: Bristol, UK
Distribution: Slackware, FreeBSD
Posts: 259

Rep: Reputation: 74
Quote:
Originally Posted by rworkman View Post
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?
 
Old 11-15-2010, 05:49 PM   #57
lonestar_italy
Member
 
Registered: Nov 2010
Location: Italy
Distribution: Slackware
Posts: 62

Rep: Reputation: 0
Quote:
Originally Posted by stormtracknole View Post
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
 
Old 11-15-2010, 06:24 PM   #58
GazL
Senior Member
 
Registered: May 2008
Posts: 3,367

Rep: Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904Reputation: 904
Quote:
Originally Posted by stormtracknole View Post
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.
 
1 members found this post helpful.
Old 11-15-2010, 06:31 PM   #59
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,374

Rep: Reputation: 164Reputation: 164
Quote:
Originally Posted by coralfang View Post
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.
 
1 members found this post helpful.
Old 11-15-2010, 06:38 PM   #60
stormtracknole
Member
 
Registered: Aug 2005
Location: The Big Easy
Distribution: Slackware, RHEL
Posts: 817

Rep: Reputation: 104Reputation: 104
Quote:
Originally Posted by coralfang View Post
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?
If you are running current, then it is safe to un-comment aaa_elflibs from /etc/slackpkg/blacklist. It is commented by default on the stable branch.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Latest current problems brodo Slackware 17 03-03-2010 10:14 AM
Latest current ? brodo Slackware 34 03-13-2009 03:15 PM
Latest nmap (4.50) in current and its gui jazzor Slackware 30 05-16-2008 12:22 PM
Race condition in /etc/rc.d/ with latest -current ? Yalla-One Slackware 1 08-06-2006 02:23 PM
warning about latest current aaa_elflibs-10.1.0 xushi Slackware 2 01-25-2005 07:57 AM


All times are GMT -5. The time now is 03:16 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration