Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
New ATI drivers out 7.11 aka 8.43.x
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4, 5  Next  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
Dark Defender
n00b
n00b


Joined: 27 Dec 2006
Posts: 74

PostPosted: Wed Nov 21, 2007 7:48 pm    Post subject: New ATI drivers out 7.11 aka 8.43.x Reply with quote

http://www.phoronix.com/scan.php?page=article&item=922&num=1

Ebuild soon? :D

EDIT: NVM...


Last edited by Dark Defender on Wed Nov 21, 2007 8:05 pm; edited 1 time in total
Back to top
View user's profile Send private message
Dottout
l33t
l33t


Joined: 07 Mar 2006
Posts: 882

PostPosted: Wed Nov 21, 2007 7:57 pm    Post subject: Reply with quote

https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_711_linux.html official release notes
edit:
Quote:
New Features

This release of the ATI Catalyst™ Linux driver introduces early-look support for the following new operating systems:

* Red Hat Enterprise Linux 4.6 (tested with Snapshot 6)
* Red Hat Enterprise Linux 5.1 (tested with Snapshot 7)
* Ubuntu 7.10
* RedFlag 6.0 DT (tested with RC)
* OpenSUSE 10.3 (tested with RC1)

Resolved Issues

The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:

* Launching a new terminal un RHEL5 32bit version no longer results in an inconsistent background colors appearing each time the window is minimized and maximized
* The kernel module is now working on kernel version 2.6.23
* An error message no longer appears during installation if dash is used as /bin/sh


1month for this shit?
Back to top
View user's profile Send private message
Dark Defender
n00b
n00b


Joined: 27 Dec 2006
Posts: 74

PostPosted: Wed Nov 21, 2007 8:04 pm    Post subject: Reply with quote

Dottout wrote:
https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/catalyst_711_linux.html official release notes
edit:
Quote:
New Features

This release of the ATI Catalyst™ Linux driver introduces early-look support for the following new operating systems:

* Red Hat Enterprise Linux 4.6 (tested with Snapshot 6)
* Red Hat Enterprise Linux 5.1 (tested with Snapshot 7)
* Ubuntu 7.10
* RedFlag 6.0 DT (tested with RC)
* OpenSUSE 10.3 (tested with RC1)

Resolved Issues

The following section provide a brief description of resolved issues with the latest version of the ATI Catalyst™ Linux software suite. These include:

* Launching a new terminal un RHEL5 32bit version no longer results in an inconsistent background colors appearing each time the window is minimized and maximized
* The kernel module is now working on kernel version 2.6.23
* An error message no longer appears during installation if dash is used as /bin/sh


1month for this shit?

And the driver still leaks on my 1900xt... 700mb in 2 min when running glxgears :X
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Wed Nov 21, 2007 8:10 pm    Post subject: Reply with quote

x11-drivers/ati-catalyst-7.11
Code:
# Copyright 1999-2007 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

IUSE="acpi multilib"

inherit eutils multilib linux-mod toolchain-funcs versionator

DESCRIPTION="Ati precompiled drivers for recent chipsets"
HOMEPAGE="http://www.ati.com"
ATI_URL="https://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/"
SRC_URI="${ATI_URL}/ati-driver-installer-${PV/./-}-x86.x86_64.run"

LICENSE="AMD GPL-2 QPL-1.0 as-is"
KEYWORDS="~amd64 ~x86"

# The portage dep is for COLON_SEPARATED support in env-update.
# The eselect dep (>=1.0.9) is for COLON_SEPARATED in eselect env update.
RDEPEND="x11-base/xorg-server
   !x11-apps/ati-drivers-extra
   >=app-admin/eselect-1.0.9
   app-admin/eselect-opengl
   =virtual/libstdc++-3.3*
   amd64? ( multilib? ( app-emulation/emul-linux-x86-compat ) )
   acpi? (
      x11-apps/xauth
      sys-power/acpid
   )
   >=sys-apps/portage-2.1.1-r1"

DEPEND="${RDEPEND}
   x11-proto/xf86miscproto
   x11-proto/xf86vidmodeproto"

EMULTILIB_PKG="true"

QA_EXECSTACK_x86="usr/lib/dri/fglrx_dri.so
   usr/lib/opengl/ati/lib/libGL.so.1.2
   opt/bin/amdcccle"
QA_EXECSTACK_amd64="usr/lib64/dri/fglrx_dri.so
   usr/lib32/dri/fglrx_dri.so
   usr/lib64/opengl/ati/lib/libGL.so.1.2
   usr/lib32/opengl/ati/lib/libGL.so.1.2
   opt/bin/amdcccle"
QA_TEXTRELS_x86="usr/lib/dri/fglrx_dri.so
   usr/lib/xorg/modules/drivers/fglrx_drv.so
   usr/lib/opengl/ati/lib/libGL.so.1.2"
QA_TEXTRELS_amd64="
   usr/lib64/opengl/ati/lib/libGL.so.1.2
   usr/lib32/opengl/ati/lib/libGL.so.1.2
   usr/lib64/dri/fglrx_dri.so
   usr/lib32/dri/fglrx_dri.so"

S="${WORKDIR}"

pkg_setup() {
   #check kernel and sets up KV_OBJ
   MODULE_NAMES="fglrx(video:${S}/common/lib/modules/fglrx/build_mod/2.6.x)"
   BUILD_TARGETS="kmod_build"
   linux-mod_pkg_setup
   BUILD_PARAMS="GCC_VER_MAJ=$(gcc-major-version) KVER=${KV_FULL} KDIR=${KV_DIR}"

   if ! kernel_is 2 6; then
      eerror "Need a 2.6 kernel to compile against!"
      die "Need a 2.6 kernel to compile against!"
   fi

   if ! linux_chkconfig_present MTRR; then
      ewarn "You don't have MTRR support enabled, the direct rendering will not work."
   fi

   if linux_chkconfig_builtin DRM; then
      ewarn "You have DRM support enabled builtin, the direct rendering will not work."
   fi

   if ! linux_chkconfig_present AGP && \
      ! linux_chkconfig_present PCIEPORTBUS; then
      ewarn "You need AGP and/or PCI Express support for direct rendering to work."
   fi

   if linux_chkconfig_present PARAVIRT; then
      eerror "The current ati-drivers don't compile when having"
      eerror "paravirtualization active due to GPL symbol export"
      eerror "restrictions."
      eerror "Please disable it:"
      eerror "   CONFIG_PARAVIRT=n"
      eerror "in /usr/src/linux/.config or"
      eerror "   Processor type and features -->"
      eerror "      [ ] Paravirtualization support (EXPERIMENTAL)"
      eerror "in 'menuconfig'"
      die "CONFIG_PARAVIRT enabled"
   fi

   if linux_chkconfig_present SLUB; then
      ewarn  "You have selected support for the SLUB allocator. Suspending is"
      ewarn  "known to be broken with this allocator and ati-drivers. If you"
      ewarn  "need support for Suspend-To-Ram or Suspend-To-Disk, select SLAB"
      ewarn  "instead. To do this enable CONFIG_SLAB and disable CONFIG_SLUB"
      ewarn  "in /usr/src/linux/.config or select"
      ewarn  "      General setup  --->"
      ewarn  "         Choose SLAB allocator (SLUB)  --->"
      ewarn  "            (X) SLAB"
      ewarn  "in 'menuconfig'"
   fi

   # xorg-server 1.1 and its prereleases correspond to xorg 7.1.
   if has_version ">=x11-base/xorg-server-1.0.99"; then
      BASE_DIR="${S}/x710"
   else
      BASE_DIR="${S}/x690"
   fi

   if use amd64 ; then
      BASE_DIR="${BASE_DIR}_64a"
      # This is used like $(get_libdir) for paths in ati's package.
      PKG_LIBDIR=lib64
      ARCH_DIR="${S}/arch/x86_64"
   else
      PKG_LIBDIR=lib
      ARCH_DIR="${S}/arch/x86"
   fi
}

src_unpack() {
   local src="${DISTDIR}/${A}"
   # This is apparently a nonstandard makeself archive, so extract
   # the offset by hand.
   local offset=$(grep -am1 SKIP "${src}" | sed -e 's/SKIP="\([0-9]\+\)"/\1/')

   #Switching to a standard way to extract the files since otherwise no signature file
   #would be created
   sh "${src}" --extract "${S}" 2&>1 /dev/null

   # These are the userspace utilities that we also have source for.
   # We rebuild these later.
   rm \
      "${ARCH_DIR}"/usr/X11R6/bin/{fgl_glxgears,fglrx_xgamma} \
      "${ARCH_DIR}"/usr/X11R6/${PKG_LIBDIR}/libfglrx_gamma* \
      || die "bin rm failed"

   if use acpi; then
      sed -i \
         -e "s:/var/lib/xdm/authdir/:/etc/X11/xdm/authdir/:" \
         -e "s:/var/lib/gdm/:/var/gdm/:" \
         -e "s/#ffff#/#ffff##:.*MIT-MAGIC-COOKIE/" \
         "${S}/common/etc/ati/authatieventsd.sh" \
         || die "sed failed."

      # Adjust paths in the script from /usr/X11R6/bin/ to /opt/bin/
      epatch "${FILESDIR}"/ati-powermode-opt-path.patch
   fi

   pushd common/lib/modules/fglrx/build_mod >/dev/null
   ln -s "${ARCH_DIR}"/lib/modules/fglrx/build_mod/libfglrx_ip.a.GCC$(gcc-major-version) \
      || die "symlinking precompiled core failed"

   convert_to_m 2.6.x/Makefile || die "convert_to_m failed"

   # When built with ati's make.sh it defines a bunch of macros if
   # certain .config values are set, falling back to less reliable
   # detection methods if linux/autoconf.h is not available. We
   # simply use the linux/autoconf.h settings directly, bypassing the
   # detection script.
   sed -i -e 's/__SMP__/CONFIG_SMP/' *.c *h || die "SMP sed failed"
   sed -i -e 's/ifdef MODVERSIONS/ifdef CONFIG_MODVERSIONS/' *.c *.h \
      || die "MODVERSIONS sed failed"
   popd >/dev/null

   mkdir extra || die "mkdir failed"
   cd extra
   unpack ./../common/usr/src/ati/fglrx_sample_source.tgz
   sed -i -e 's:include/extensions/extutil.h:X11/extensions/extutil.h:' \
      lib/fglrx_gamma/fglrx_gamma.c || die "include fixup failed"
   # Add a category.
   mv programs/fglrx_gamma/fglrx_xgamma.{man,1} || die "man mv failed"
   cd ..

}

src_compile() {
   linux-mod_src_compile

   einfo "Building fgl_glxgears"
   cd "${S}"/extra/fgl_glxgears
   # These extra libs/utils either have an Imakefile that does not
   # work very well without tweaking or a Makefile ignoring CFLAGS
   # and the like. We bypass those.

   # The -DUSE_GLU is needed to compile using nvidia headers
   # according to a comment in ati-drivers-extra-8.33.6.ebuild.
   "$(tc-getCC)" -o fgl_fglxgears ${CFLAGS} ${LDFLAGS} -DUSE_GLU \
      -I"${S}"/common/usr/include fgl_glxgears.c \
      -lGL -lGLU -lX11 -lm || die "fgl_glxgears build failed"

   einfo "Building fglrx_gamma lib"
   cd "${S}"/extra/lib/fglrx_gamma
   "$(tc-getCC)" -shared -fpic -o libfglrx_gamma.so.1.0 ${CFLAGS} ${LDFLAGS} \
      -DXF86MISC -Wl,-soname,libfglrx_gamma.so.1.0 fglrx_gamma.c \
      -lXext || die "fglrx_gamma lib build failed"
   ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so || die "ln failed"
   ln -s libfglrx_gamma.so.1.0 libfglrx_gamma.so.1 || die "ln failed"

   einfo "Building fglrx_gamma util"
   cd "${S}"/extra/programs/fglrx_gamma
   "$(tc-getCC)" -o fglrx_xgamma ${CFLAGS} ${LDFLAGS} \
      -I../../../common/usr/X11R6/include -L../../lib/fglrx_gamma \
      fglrx_xgamma.c -lm -lfglrx_gamma -lX11 \
      || die "fglrx_gamma util build failed"

}

src_install() {
   linux-mod_src_install

   # We can do two things here, and neither of them is very nice.

   # For direct rendering libGL has to be able to load one or more
   # dri modules (files ending in _dri.so, like fglrx_dri.so).
   # Gentoo's mesa looks for these files in the location specified by
   # LIBGL_DRIVERS_PATH or LIBGL_DRIVERS_DIR, then in the hardcoded
   # location /usr/$(get_libdir)/dri. Ati's libGL does the same
   # thing, but the hardcoded location is /usr/X11R6/lib/modules/dri
   # on x86 and amd64 32bit, /usr/X11R6/lib64/modules/dri on amd64
   # 64bit. So we can either put the .so files in that (unusual,
   # compared to "normal" mesa libGL) location or set
   # LIBGL_DRIVERS_PATH. We currently do the latter. See also bug
   # 101539.

   # The problem with this approach is that LIBGL_DRIVERS_PATH
   # *overrides* the default hardcoded location, it does not extend
   # it. So if ati-drivers is merged but a non-ati libGL is selected
   # and its hardcoded path does not match our LIBGL_DRIVERS_PATH
   # (because it changed in a newer mesa or because it was compiled
   # for a different set of multilib abis than we are) stuff breaks.

   # We create one file per ABI to work with "native" multilib, see
   # below.

   echo "COLON_SEPARATED=LIBGL_DRIVERS_PATH" > "${T}/03ati-colon-sep"
   doenvd "${T}/03ati-colon-sep"

   # All libraries that we have a 32 bit and 64 bit version of on
   # amd64 are installed in src_install-libs. Everything else
   # (including libraries only available in native 64bit on amd64)
   # goes in here.

   # There used to be some code here that tried to detect running
   # under a "native multilib" portage ((precursor of)
   # http://dev.gentoo.org/~kanaka/auto-multilib/). I removed that, it
   # should just work (only doing some duplicate work). --marienz
   if has_multilib_profile; then
      local OABI=${ABI}
      for ABI in $(get_install_abis); do
         src_install-libs
      done
      ABI=${OABI}
      unset OABI
   else
      src_install-libs
   fi

   # This is sorted by the order the files occur in the source tree.

   # X modules.
   exeinto /usr/$(get_libdir)/xorg/modules/drivers
   doexe "${BASE_DIR}"/usr/X11R6/${PKG_LIBDIR}/modules/drivers/fglrx_drv.so
   exeinto /usr/$(get_libdir)/xorg/modules/linux
   doexe "${BASE_DIR}"/usr/X11R6/${PKG_LIBDIR}/modules/linux/libfglrxdrm.so
   exeinto /usr/$(get_libdir)/xorg/modules
   doexe "${BASE_DIR}"/usr/X11R6/${PKG_LIBDIR}/modules/{esut.a,glesx.so}

   # Arch-specific files.
   # (s)bin.
   into /opt
   if use acpi; then
      dosbin "${ARCH_DIR}"/usr/sbin/atieventsd
   fi
   # We cleaned out the compilable stuff in src_unpack
   dobin "${ARCH_DIR}"/usr/X11R6/bin/*

   # lib.
   exeinto /usr/$(get_libdir)
   # Everything except for the libGL.so installed in src_install-libs.
   doexe $(find "${ARCH_DIR}"/usr/X11R6/${PKG_LIBDIR} \
      -maxdepth 1 -type f -name '*.so*' -not -name 'libGL.so*')
   insinto /usr/$(get_libdir)
   doins $(find "${ARCH_DIR}"/usr/X11R6/${PKG_LIBDIR} \
      -maxdepth 1 -type f -not -name '*.so*')

   # Common files.
   # etc.
   insinto /etc/ati
   # Everything except for the authatieventsd.sh script.
   doins common/etc/ati/{logo*,control,atiogl.xml,signature}
   if use acpi; then
      doins common/etc/ati/authatieventsd.sh
   fi

   # include.
   insinto /usr
   doins -r common/usr/include
   insinto /usr/include/X11/extensions
   doins common/usr/X11R6/include/X11/extensions/fglrx_gamma.h

   # Just the atigetsysteminfo.sh script.
   into /usr
   dosbin common/usr/sbin/*

   # data files for the control panel.
   insinto /usr/share
   doins -r common/usr/share/ati
   insinto /usr/share/pixmaps
   doins common/usr/share/icons/ccc_{large,small}.xpm
   make_desktop_entry amdcccle 'ATI Catalyst Control Center' \
      ccc_large.xpm System

   # doc.
   dohtml -r common/usr/share/doc/fglrx

   if use acpi; then
      doman common/usr/share/man/man8/atieventsd.8

      pushd common/usr/share/doc/fglrx/examples/etc/acpi >/dev/null

      exeinto /etc/acpi
      doexe ati-powermode.sh
      insinto /etc/acpi/events
      doins events/*

      popd >/dev/null
   fi

   # Done with the "source" tree. Install tools we rebuilt:
   dobin extra/fgl_glxgears/fgl_fglxgears
   newdoc extra/fgl_glxgears/README README.fgl_glxgears

   dolib extra/lib/fglrx_gamma/*so*
   newdoc extra/lib/fglrx_gamma/README README.libfglrx_gamma

   dobin extra/programs/fglrx_gamma/fglrx_xgamma
   doman extra/programs/fglrx_gamma/fglrx_xgamma.1
   newdoc extra/programs/fglrx_gamma/README README.fglrx_gamma

   # Gentoo-specific stuff:

   if use acpi; then
      newinitd "${FILESDIR}"/atieventsd.init atieventsd \
         || die "Failed to install atieventsd.init.d"
      echo 'ATIEVENTSDOPTS=""' > "${T}"/atieventsd.conf
      newconfd "${T}"/atieventsd.conf atieventsd
   fi
}

src_install-libs() {
   if [[ "${ABI}" == "amd64" ]]; then
      local pkglibdir=lib64
      local MY_ARCH_DIR="${S}/arch/x86_64"
   else
      local pkglibdir=lib
      local MY_ARCH_DIR="${S}/arch/x86"
   fi
   einfo "ati tree '${pkglibdir}' -> '$(get_libdir)' on system"

   local ATI_ROOT=/usr/$(get_libdir)/opengl/ati
   # To make sure we do not miss a spot when these change.
   local libmajor=1 libminor=2
   local libver=${libmajor}.${libminor}

   # The GLX libraries
   # (yes, this really is "lib" even on amd64/multilib --marienz)
   exeinto ${ATI_ROOT}/lib
   doexe "${MY_ARCH_DIR}"/usr/X11R6/${pkglibdir}/libGL.so.${libver}
   dosym libGL.so.${libver} ${ATI_ROOT}/lib/libGL.so.${libmajor}
   dosym libGL.so.${libver} ${ATI_ROOT}/lib/libGL.so

   # Same as the xorg implementation (eselect opengl does not fall
   # back to xorg-x11 if we omit this symlink, meaning no glx).
   dosym ../xorg-x11/extensions ${ATI_ROOT}/extensions

   # DRI modules, installed into the path used by recent versions of mesa.
   exeinto /usr/$(get_libdir)/dri
   doexe "${MY_ARCH_DIR}"/usr/X11R6/${pkglibdir}/modules/dri/fglrx_dri.so

   # Make up a libGL.la. Ati does not provide one, but mesa does. If
   # a (libtool-based) libfoo is built with libGL.la present a
   # reference to it is put into libfoo.la, and compiling
   # (libtool-based) things that link too libfoo.la will complain if
   # libGL.la disappears. So if we do not make up a libGL.la
   # switching between mesa and ati becomes painful.
   #
   # According to the libtool manual the "revision" should be updated
   # whenever the code changes. We construct this from the version
   # (8.37.6 becomes 83706).
   local revision=$(printf '%d%02d%02d' $(get_version_components))
   sed -e "s:\${libmajor}:${libmajor}:g" \
      -e "s:\${libminor}:${libminor}:g" \
      -e "s:\${libdir}:$(get_libdir):g" \
      -e "s:\${revision}:${revision}:g" \
      "${FILESDIR}"/libGL.la.in > "${D}"/${ATI_ROOT}/lib/libGL.la \
      || die "sed failed to make libGL.la"

   local envname="${T}"/04ati-dri-path
   if [[ -n ${ABI} ]]; then
      envname="${envname}-${ABI}"
   fi
   echo "LIBGL_DRIVERS_PATH=/usr/$(get_libdir)/dri" > "${envname}"
   doenvd "${envname}"
}

pkg_postinst() {
   ewarn "If you experience screen corruption with this driver, try putting"
   ewarn '      Option "XAANoOffscreenPixmaps" "true"'
   ewarn "in the Device Section of /etc/X11/xorg.conf."

   /usr/bin/eselect opengl set --use-old ati

   elog "To switch to ATI OpenGL, run \"eselect opengl set ati\""
   elog "To change your xorg.conf you can use the bundled \"aticonfig\""
   elog
   elog "If you experience unexplained segmentation faults and kernel crashes"
   elog "with this driver and multi-threaded applications such as wine,"
   elog "set UseFastTLS in xorg.conf to either 0 or 1, but not 2."
   elog
   # (to get the LIBGL_DRIVERS_PATH)
   elog "You will have to source /etc/profile (or logout and back in) for dri"
   elog "to work, unless you previously had ati-drivers installed."
   # DRM module
   linux-mod_pkg_postinst
   # Warning per bug #199720
   elog "***** Warning *****"
   elog "ATI has stated this is not a complete release version and should"
   elog "not be distributed. Although it is the version presented on their"
   elog "website for certain chipsets/cards. Due to this version being"
   elog "incomplete, some users will experience \"(EE) No devices detected.\""
   elog "errors. This is known and please mask this version locally if you"
   elog "experience that. For further information please see the following"
   elog "http://www2.ati.com/drivers/linux/linux_8.42.3.html"
}

pkg_postrm() {
   linux-mod_pkg_postrm
   /usr/bin/eselect opengl set --use-old xorg-x11
}

_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
Dottout
l33t
l33t


Joined: 07 Mar 2006
Posts: 882

PostPosted: Wed Nov 21, 2007 8:15 pm    Post subject: Reply with quote

thank you rmh3093, fast as the light :D (obviously Im a zen-sources user eheh)
edit: on ati x1400 I lost 100-150 fps with glxgears..
Back to top
View user's profile Send private message
bigmauler
Apprentice
Apprentice


Joined: 25 Apr 2005
Posts: 177
Location: Seattle, WA

PostPosted: Wed Nov 21, 2007 11:15 pm    Post subject: Reply with quote

what should I name this and where should I put this ebuild if I want to build it?
_________________
Never take raisins from a rabbit
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Wed Nov 21, 2007 11:35 pm    Post subject: Reply with quote

This driver version seems to be an easy bump.
I've also corrected the warnings patch and the 2.6.23 patch (one hunk still applies).
I will post those in the appropriate bug report.

Unfortunately the SONAME problem still exists.
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Thu Nov 22, 2007 12:22 am    Post subject: Reply with quote

Berniyh wrote:
This driver version seems to be an easy bump.
I've also corrected the warnings patch and the 2.6.23 patch (one hunk still applies).
I will post those in the appropriate bug report.

Unfortunately the SONAME problem still exists.


the 2.6.23 patch is not needed....

i didnt look into the warnings patch, but it compiles with out it so I dont get its point
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Thu Nov 22, 2007 12:25 am    Post subject: Reply with quote

bigmauler wrote:
what should I name this and where should I put this ebuild if I want to build it?


its just an ebuild... you can put it anywhere you want really

because 7.11 is newer than 8.42 but 8.42 is greater numerically than 7.11 I renamed the ebuild to ati-catalyst

....you can do what ever you want
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Thu Nov 22, 2007 12:31 am    Post subject: Reply with quote

rmh3093 wrote:
Berniyh wrote:
This driver version seems to be an easy bump.
I've also corrected the warnings patch and the 2.6.23 patch (one hunk still applies).
I will post those in the appropriate bug report.

Unfortunately the SONAME problem still exists.


the 2.6.23 patch is not needed....

i didnt look into the warnings patch, but it compiles with out it so I dont get its point

A warnings patch is never needed. ;)
If would be needed, it would fix errors, not warnings.

You're right, none of those patches is "needed", but I had a look at them, to see which
hunks will still apply and corrected them.

BTW, you should remove the emul dep in the ebuild, it is not needed anymore.
I also think you could remove the warning about screen corruptions in the ebuild, but
since it won't do any harm I would leave it there for now, at least until someone runs
this driver for at least three days without corruptions.
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Thu Nov 22, 2007 12:37 am    Post subject: Reply with quote

Berniyh wrote:
rmh3093 wrote:
Berniyh wrote:
This driver version seems to be an easy bump.
I've also corrected the warnings patch and the 2.6.23 patch (one hunk still applies).
I will post those in the appropriate bug report.

Unfortunately the SONAME problem still exists.


the 2.6.23 patch is not needed....

i didnt look into the warnings patch, but it compiles with out it so I dont get its point

A warnings patch is never needed. ;)
If would be needed, it would fix errors, not warnings.

You're right, none of those patches is "needed", but I had a look at them, to see which
hunks will still apply and corrected them.

BTW, you should remove the emul dep in the ebuild, it is not needed anymore.
I also think you could remove the warning about screen corruptions in the ebuild, but
since it won't do any harm I would leave it there for now, at least until someone runs
this driver for at least three days without corruptions.


I wasnt really attempting to make a portage worthy ebuild... just something that would get the driver installed on peoples boxes.... with the versioning change I figured there would be bigger isssues to worry about
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
n3Cre0
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jan 2007
Posts: 129

PostPosted: Thu Nov 22, 2007 11:47 am    Post subject: Reply with quote

Installed it, used it, removed it. It messed up my dock and conky for me when I zoomed out. Weird glitches.
Switched back to 8.42.3, I guess I'll be using this one for a long while.
I had hoped they would have fixed the slow firefox scrolling and AIGLX compatibility with xorg-server 1.4, but no.. they've chosen to rename the driver (makes more sense, I admit) and mess some things up (for me)
_________________
OS: Linux 2.6.26 i686 Gentoo v2.0.0 Sound: HDA Intel
CPU: Intel(R) Pentium(R) M processor 1.73GHz (GenuineIntel)
Disk: 95.23GB Video: ATI Radeon Mobility X700 XL with Catalyst 8.08 RAM: 1011MB
Back to top
View user's profile Send private message
Insanity5902
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas

PostPosted: Thu Nov 22, 2007 3:03 pm    Post subject: Reply with quote

n3Cre0 wrote:
Installed it, used it, removed it. It messed up my dock and conky for me when I zoomed out. Weird glitches.
Switched back to 8.42.3, I guess I'll be using this one for a long while.
I had hoped they would have fixed the slow firefox scrolling and AIGLX compatibility with xorg-server 1.4, but no.. they've chosen to rename the driver (makes more sense, I admit) and mess some things up (for me)


Few things 1) ATI/AMD still recommends to use 8.40.4 for distrubution. 2) according the phoronix, there was actually some bug fixes that where suppose to come into this one, amd's report of the release is really kind of vauge in this aspect.

I believe some of my issues with 8.42.3 was 64bit related

Starting with the 8.41.7 the code base was changed a lot and lots of problems where interduced, I haven't been able to get anything higher then 8.40.4 to even run with decent performance, not even including the beryl type effects.

I probably won't be updating my ati driver from 8.40.4 for a few more months. I will continue to follow the release. I might give 7.12 a try, as 7.11 seemed to be more of a foundation to build off of release, the a performance or bug. I'll still give it a try but i'm not expecting to be happy with the performance of aiglx still

The only reason I want to switch off of 8.40.4 is to get rid of XGL and move to AIGLX, maybe one day :D
_________________
GibbonsR.net | OpenLaptops.org

Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
Insanity5902
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas

PostPosted: Thu Nov 22, 2007 3:12 pm    Post subject: Reply with quote

just read through the first 10 pages or say of the thread over on phoronix forums ... yeah, i am not giving it a try. I'll wait for 7.12 or 8.1
_________________
GibbonsR.net | OpenLaptops.org

Join the adopt an unanswered post initiative today
Back to top
View user's profile Send private message
beso_1717
Apprentice
Apprentice


Joined: 19 Jul 2007
Posts: 263

PostPosted: Thu Nov 22, 2007 8:05 pm    Post subject: Reply with quote

you've forgotten to add the block dep on ati-drivers so that ati-drivers would have to be uninstalled before installing ati-catalyst.
also it should be added a line in xorg-server's ebuild in which you point out on ati-drivers or ati-catalyst. or better, you could call the driver, ati-driver and block the drivers > di 8.0 (this would be only a temporary stuff of 2 or 3 months before the gentoo devs decide on how to treat this naming issue).
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Thu Nov 22, 2007 8:23 pm    Post subject: Reply with quote

beso_1717 wrote:
you've forgotten to add the block dep on ati-drivers so that ati-drivers would have to be uninstalled before installing ati-catalyst.
also it should be added a line in xorg-server's ebuild in which you point out on ati-drivers or ati-catalyst. or better, you could call the driver, ati-driver and block the drivers > di 8.0 (this would be only a temporary stuff of 2 or 3 months before the gentoo devs decide on how to treat this naming issue).

I wouldn't bet, that this goes in portage as "ati-catalyst".
(I also wouldn't bet on the opposite side. ;))
Back to top
View user's profile Send private message
beso_1717
Apprentice
Apprentice


Joined: 19 Jul 2007
Posts: 263

PostPosted: Thu Nov 22, 2007 9:04 pm    Post subject: Reply with quote

Quote:
I wouldn't bet, that this goes in portage as "ati-catalyst".
(I also wouldn't bet on the opposite side. ;))


that's why i've said that it should be adopted one of these 2 things to make it still run.
the 8.42 got in portage and i'd expect also the catalyst to go into portage.
i think that the best thing is to make the ebuild as ati-drivers-7.11 and mask the packages over it in package.mask
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Thu Nov 22, 2007 9:13 pm    Post subject: Reply with quote

beso_1717 wrote:
Quote:
I wouldn't bet, that this goes in portage as "ati-catalyst".
(I also wouldn't bet on the opposite side. ;))


that's why i've said that it should be adopted one of these 2 things to make it still run.
the 8.42 got in portage and i'd expect also the catalyst to go into portage.
i think that the best thing is to make the ebuild as ati-drivers-7.11 and mask the packages over it in package.mask

I really only meant the name.

The ebuild is fine.

Masking the packages "above" (8.*) isn't really a good idea, since ATI recommends to ship out 8.40.4 and because firegl
cards are still not supported with the current release.

One option would be to rename the current ebuilds to 7.8.40.4 (and similar).
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Fri Nov 23, 2007 12:29 am    Post subject: Reply with quote

beso_1717 wrote:
you've forgotten to add the block dep on ati-drivers so that ati-drivers would have to be uninstalled before installing ati-catalyst.
also it should be added a line in xorg-server's ebuild in which you point out on ati-drivers or ati-catalyst. or better, you could call the driver, ati-driver and block the drivers > di 8.0 (this would be only a temporary stuff of 2 or 3 months before the gentoo devs decide on how to treat this naming issue).


I didnt forget I chose not too, you all should be skilled enough to emerge a basic ebuild.... thats gentoo 101
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
hirakendu
Guru
Guru


Joined: 24 Jan 2007
Posts: 386
Location: san diego

PostPosted: Fri Nov 23, 2007 1:30 am    Post subject: Reply with quote

haha. gentoo 101 :D.
_________________
Helium Sources || Gentoo Minimal Livecd
Back to top
View user's profile Send private message
cocoliso
n00b
n00b


Joined: 07 Mar 2004
Posts: 68

PostPosted: Fri Nov 23, 2007 4:18 am    Post subject: Reply with quote

when i try to digest the ebuild i am getting this error

Code:
usr/local/portage/x11-drivers/ati-catalyst/ati-catalyst-7.11.ebuild: line 138: syntax error near unexpected token `||'
/usr/local/portage/x11-drivers/ati-catalyst/ati-catalyst-7.11.ebuild: line 138: `       || die "bin rm failed"'
 *
 * ERROR: x11-drivers/ati-catalyst-7.11 failed.
 * Call stack:
 *   ebuild.sh, line 1590:  Called die
 * The specific snippet of code:
 * QA Notice: 'sed' called in global scope: x11-drivers/ati-catalyst-7.11
 * QA Notice: 'sed' called in global scope: x11-drivers/ati-catalyst-7.11
 *   source ${EBUILD} || die "error sourcing ebuild"
 *  The die message:
 *   error sourcing ebuild

_________________
Computers are useless.
Back to top
View user's profile Send private message
cocoliso
n00b
n00b


Joined: 07 Mar 2004
Posts: 68

PostPosted: Fri Nov 23, 2007 4:35 am    Post subject: Reply with quote

ehmm jeje my mistake bad copy&paste :oops:
_________________
Computers are useless.
Back to top
View user's profile Send private message
seren
Guru
Guru


Joined: 27 Aug 2005
Posts: 448
Location: Wisconsin

PostPosted: Fri Nov 23, 2007 6:03 am    Post subject: Reply with quote

the best method for the ebuild is to use the name 8.43 and put in the ebuild this for
SCR_URI
Code:
SRC_URI="http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-7-11-x86.x86_64.run"
Back to top
View user's profile Send private message
Berniyh
l33t
l33t


Joined: 07 Jun 2006
Posts: 677

PostPosted: Fri Nov 23, 2007 7:39 am    Post subject: Reply with quote

seren wrote:
the best method for the ebuild is to use the name 8.43 and put in the ebuild this for
SCR_URI
Code:
SRC_URI="http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-7-11-x86.x86_64.run"

Uuuhm.... No.

That way you _will_ carry that renaming issue around all the time, that is not a solution.
It's just a stupid (sorry) workaround.
Back to top
View user's profile Send private message
rmh3093
Advocate
Advocate


Joined: 06 Aug 2003
Posts: 2138
Location: Albany, NY

PostPosted: Fri Nov 23, 2007 8:36 am    Post subject: Reply with quote

Berniyh wrote:
seren wrote:
the best method for the ebuild is to use the name 8.43 and put in the ebuild this for
SCR_URI
Code:
SRC_URI="http://a248.e.akamai.net/f/674/9206/0/www2.ati.com/drivers/linux/ati-driver-installer-7-11-x86.x86_64.run"

Uuuhm.... No.

That way you _will_ carry that renaming issue around all the time, that is not a solution.
It's just a stupid (sorry) workaround.


why don't you all call it what ever you want and stick it in an overlay and call it day..... let the gentoo dev's spend the next 2 months figuring this out
_________________
Do not meddle in the affairs of wizards, for they are subtle and quick to anger.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page 1, 2, 3, 4, 5  Next
Page 1 of 5

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum