From: Tuxedo on
Henrik Carlqvist wrote:

[...]

> If so, I have no better idea than to stick to Slackware 12.2 and hope that
> the intel issues will be resolved in future versions of the kernel and X
> included in upcoming versions of Slackware.

I agree this is the best available option in this time of age. It appears
that 12.2 is still well maintained in terms of number of pre-packaged
programs in various third-party repositories. However, even in 12.2 after
running in DRI mode and thereafter logging out of X the text in the console
flickers strangely and I have no idea what the cause may be, but something
is definitely not 100% right under the hood. At best it's just a wrongly
configured xorg.conf, meaning that xorgsetup gets the values wrong on my
particular hardware. According to the article linked at distrowatch there
are "48 combinations of settings for different features in the 2.6.x and
2.7.x Intel video drivers". Will dive into xorg.conf the manual way next...

Tuxedo


From: Mike Jones on
Responding to Tuxedo:

> Mike Jones wrote:
>
> [...]
>
>> Have you tried 'xorgsetup' at all? Its more like the old way of doing
>> things. Don't forget to check through your new xorg.conf and add back
>> bits you might need, like maybe prefered gamma settings, etc.
>
> Sure I did, however, it failed in making DRI work with any of the
> drivers, and the hard part is knowing what is necessary to add manually
> to xorg.conf, as well as finding the values relating to the hardware.
> This information isn't exactly written anywhere on Intel's or Samsung's
> websites.
>
> So far it is only DRI that isn't working and this is obviously because
> the drivers are broken to begin with. I'm pretty sure it would work on a
> much older Linux system. I've searched countless forums and found many
> people having similar problems but could not find a clear solution
> anywhere.
>
> Tuxedo


Ah. I have indeed been installing on older hardware.

Looks like the same routine as with S12.0 Wait for the bugs to be ironed
out before deploying, which'll mean S13.1 = patched, and S13.2 = final.

--
*=( http://www.thedailymash.co.uk/
*=( For all your UK news needs.
From: Tuxedo on
Mike Jones wrote:

[...]

> Ah. I have indeed been installing on older hardware.
>
> Looks like the same routine as with S12.0 Wait for the bugs to be ironed
> out before deploying, which'll mean S13.1 = patched, and S13.2 = final.

Can't wait for the release :-)

Tuxedo


From: Richard Herbert on
On Sun, 03 Jan 2010 13:31:41 +0100, Tuxedo wrote:

> Hi,
>
> Is it possible to open a .txz package on Slackware 12.2? I'd like to
> test the various Intel Xorg drivers in a 12.2 environment of my
> hardware, meaning the drivers from the extra directory on the 13.0 DVD:
>
> xf86-video-intel-2.5.1-i486-1.txz
> xf86-video-intel-2.6.3-i486-1.txz
> xf86-video-intel-2.7.1-i486-1.txz
> xf86-video-intel-2.8.1-i486-1.txz
>
> Or are these also available somewhere in a .tgz package format?
>
> Is one of the above drivers the same version that comes pre-installed on
> Slackware 12.2? If so, which one?
> Thanks,
> Tuxedo

I keep seeing these questions about .txz packages. Simply download and
installpkg xz-4.999.9beta-i486-1.tgz from slackware/current. You'll also
need pkgtools-13.0-noarch-3.tgz, but you can get that from /current as
well. I've been using this combo in 12.2 with no problems whatsoever.

Richard Herbert
From: Martin on
Richard Herbert wrote:

> I keep seeing these questions about .txz packages. Simply download and
> installpkg xz-4.999.9beta-i486-1.tgz from slackware/current. You'll also
> need pkgtools-13.0-noarch-3.tgz, but you can get that from /current as
> well. I've been using this combo in 12.2 with no problems whatsoever.

I would add the packages "file" and "tar" to the list, the latter for the -J
option. I believe at the time of introducing txz (April 2009) a few other
packages where mentioned in the changelog, but you can probably ignore them
for your purpose.

Ark doesn't handle txz "in one go" to this day. ;-)

Martin