Xorg update in current, yay!

Martinus2u · 05-05-2012, 09:34 AM

have been waiting for it in the hope that it will sort out some issues on some of my machines...

will give it a wirl after the next rsync (scheduled for 3 am)

bosth · 05-05-2012, 10:23 AM

Dude you need a blog or a Twitter account.

Martinus2u · 05-06-2012, 06:47 PM

haters make me only stronger. back on topic: so far I found that issues in two nvidia based machines have not been resolved by the upgrade, and the GM45 based machine (ie. the infamous i915 driver) went belly-up with the x server dying without any trace in the logs.

Solution for all users of similar hardware: upgrade libdrm. I went to 2.4.33 and xorg started working again.

wildwizard · 05-06-2012, 07:41 PM

er the update to -current includes libdrm 2.4.33 perhaps when you try stuff from current you might want to try upgrading everything properly.

Martinus2u · 05-07-2012, 06:54 AM

Quote:

Originally Posted by wildwizard

er the update to -current includes libdrm 2.4.33 perhaps when you try stuff from current you might want to try upgrading everything properly.

ooops, you're right. the package must have got lost when I rolled out the changes in the LAN. I'd better check if I missed out any more packages.

The underlying problem is that I sometimes need to upgrade packages in advance of -current, particularly in the graphics stack, and then the delta management gets more error prone.

onebuck · 05-07-2012, 07:26 AM

Hi,

Quote:

Originally Posted by Martinus2u

ooops, you're right. the package must have got lost when I rolled out the changes in the LAN. I'd better check if I missed out any more packages.

The underlying problem is that I sometimes need to upgrade packages in advance of -current, particularly in the graphics stack, and then the delta management gets more error prone.

Seems to me you would find 'slackpkg' useful;

Quote:

excerpt from 'man slackpkg';
DESCRIPTION
Slackpkg is a tool for those who want to easily install or upgrade packages via the network. With slackpkg, you can have a minimal
installation of Slackware Linux and install/upgrade only those packages you need most.

You don't need to setup NFS or make dozens of CDs for all your computers; all you need to do is to type one command and all of the lat-
est official Slackware packages will be at your fingertips.

INSTRUCTIONS
Slackpkg has many features. It can search for specific files, remove all third-party packages in your system, install packages added to
Slackware since your last update, show package descriptions, etc.

Before you do anything, you will need to uncomment one mirror in /etc/slackpkg/mirrors file and run:

# slackpkg update

The "update" action will download and format the list of files and packages in Slackware. Every time this list is changed, the update
need to be run.

The main features of Slackpkg are the ones directly related to package management: install, upgrade, and remove packages. To do any of
these tasks, the Slackpkg syntax is:

# slackpkg [OPTIONS] <action> {PATTERN|FILE}

You will need to select a mirror in /etc/slackpkg/mirrors;

Quote:

# You only need to select one mirror and uncomment them. Please,
# ONLY ONE mirror can be uncommented each time.
#
# You can include new mirrors in this file. Many people have mirrors
# in their local networks. Slackpkg only needs to point to the
# directory that contains "ChangeLog.txt", and don't forget the
# trailling slash.

Do not forget /etc/slackpkg/blacklist & /etc/slackpkg/slackpkg.conf when necessary.

Quote:

excerpt from /etc/slackpkg/blacklist;
# This is a blacklist file. Any packages listed here won't be
# upgraded, removed, or installed by slackpkg.
#
# The correct syntax is:
#
# To blacklist the package xorg-server-1.6.3-x86_64-1 the line will be:
# xorg-server
#
# DON'T put any space(s) before or after the package name or regexp.
# If you do this, the blacklist will NOT work.

Quote:

excerpt from /etc/slackpkg/slackpkg.conf;
# For configuration options that have only two states, possible values are
# either "on" or "off"

# Remember, the only official Slackware ports are x86, s390 and arm, and
# slackpkg developers don't have s390 boxes for testing. If you are
# testing/using other architectures and have suggestions or patches,
# please let me know (piterpunk@slackware.com)
#
# Select the architecture of your system. Valid values are:
# i#86 (where # is 3, 4, 5 or 6)
# x86_64
# s390
# arm* (* can be v4, v5tejl, and other ARM versions)
# powerpc
#
# The line is commented because slackpkg will try to find your
# architecture automagically. If you want to override what slackpkg
# finds, put the value after the = and uncomment this line
#ARCH=

# The default PKGMAIN is "slackware", but some derived distros use other
# names as the main directory. PKGMAIN is the place with the slackware
# package series (a, ap, n, ... ).
#

You should become familiar with the above 'slackpkg' related files. 'slackpkg' is a great tool!
HTH!

Martinus2u · 05-07-2012, 10:07 AM

Quote:

Originally Posted by onebuck

'slackpkg' is a great tool!

Thanks for the advice. I may look into it again. It will not change my overall process and I still need full manual control over my packages including delta analysis and management of multilib consistency (for which I have extensive tools). For bandwidth reasons I will have to continue to use a local mirror. Slackpkg may be of help in the sense that it persists a blacklist per target machine (provided I remember to keep it up to date - every process and every tool opens the door for user errors

).

dc_eros · 05-07-2012, 05:53 PM

Do you experience VLC problems after the Xorg update? I see green overlay on VLC when playing videos. Not sure if they are specific to video types but I haven't played other videos yet though. Researched and found that it was probably due to acceleration stuff and some video types. Didn't bother as MPlayer is playing fine except that I cannot increase more sound volume

NoStressHQ · 05-08-2012, 02:29 AM

Quote:

Originally Posted by Martinus2u

...For bandwidth reasons I will have to continue to use a local mirror...

??!?! I always have a slackware mirror somewhere on my LAN(s) to limit "foreign bandwidth"... But slackpkg works WELL with a "local" mirror (or a lan mirror)...
I really don't understand why a local mirror would change "anything" to a remote mirror (beside the protocol, but this is a low level detail).

Martinus2u · 05-08-2012, 02:32 PM

Quote:

Originally Posted by dc_eros

Do you experience VLC problems after the Xorg update? I see green overlay on VLC when playing videos. Not sure if they are specific to video types but I haven't played other videos yet though. Researched and found that it was probably due to acceleration stuff and some video types. Didn't bother as MPlayer is playing fine except that I cannot increase more sound volume

no, i haven't noticed any regression with vlc.

Martinus2u · 05-08-2012, 02:36 PM

Quote:

Originally Posted by NoStressHQ

??!?! I always have a slackware mirror somewhere on my LAN(s) to limit "foreign bandwidth"... But slackpkg works WELL with a "local" mirror (or a lan mirror)...
I really don't understand why a local mirror would change "anything" to a remote mirror (beside the protocol, but this is a low level detail).

no argument here. The statement was just for added information.