LINUX.ORG.RU
Форум — Talks  

[nvidia] 295.33

 


0

0

кактус-лог

    * Added support for the following GPUs:

        * GeForce GTX 680
        * GeForce GT 630M
        * GeForce GT 620

    * Fixed a VDPAU bug where decoding some H.264 streams would cause hardware
      errors on lower-end products, resulting in corruption and poor
      performance.

    * Fixed a bug that caused DisplayPort audio to stop working after monitors
      are hotplugged on GeForce GT 520.

    * Improved compatibility with recent Linux kernels.

    * Fixed a behavior change that prevented ConnectedMonitor from being usable
      with DisplayPort connectors.

    * Marked the GVO Clone mode NV-CONTROL attributes:

        NV_CTRL_GVO_DISPLAY_X_SCREEN
        NV_CTRL_GVO_X_SCREEN_PAN_X
        NV_CTRL_GVO_X_SCREEN_PAN_Y

      as deprecated.  They will be removed in a future release.  To display
      an X screen over GVO, it is recommended to use GVO with MetaModes,
      instead.

    * Fixed a bug that caused DisplayPort devices to not be listed in
      Xorg.*.log.  For example, if only DisplayPort devices are attached, the
      log file would contain

        (--) NVIDIA(0): Connected display device(s) on NVIDIA GPU at PCI:2:0:0
        (--) NVIDIA(0):     none

    * Added support for 3D Vision ready displays that have a NVIDIA 3D Vision
      infrared emitter built inside the panel itself.

    * Fixed a bug that caused OpenGL applications to crash with some libc
      versions, such as eglibc 2.15.

    * Fixed a bug that caused HDMI audio to stop working on AppleTV devices when
      an X server was started.
а я в ребут
будем посмотреть :3
бага с прелинком нет - это есть хорошо

★★★★

Последнее исправление: megabaks (всего исправлений: 1)
← [Ъ]Самодельный компьютер
Свободная бытовая техника? →
  1 2 →
Ответ на: комментарий от anTaRes

Да там вообщем-то все тоже самое: 

* Package:    x11-drivers/nvidia-drivers-295.33
 * Repository: local-overlay
 * Maintainer: cardoe@gentoo.org jer@gentoo.org,spock@gentoo.org
 * USE:        elibc_glibc gtk kernel_linux userland_GNU x86
 * FEATURES:   sandbox
 * Determining the location of the kernel source code
 * Found kernel source directory:
 *     /usr/src/linux
 * Found kernel object directory:
 *     /lib/modules/3.3.0-gentoo/build
 * Found sources for kernel version:
 *     3.3.0-gentoo
 * Checking for MTRR support ...
 [ ok ]
>>> Unpacking source...
>>> Unpacking NVIDIA-Linux-x86-295.33.run to /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work
>>> Source unpacked in /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work ...
 * Converting /kernel/Makefile.kbuild to use M= instead of SUBDIRS= ...
 [ ok ]
>>> Source prepared.
>>> Configuring source in /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work ...
>>> Source configured.
>>> Compiling source in /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work ...
 * Preparing nvidia module
make -j5 HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS= IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux SYSOUT=/lib/modules/3.3.0-gentoo/build CC=i686-pc-linux-gnu-gcc clean module 
If you are using a Linux 2.4 kernel, please make sure
you either have configured kernel sources matching your
kernel or the correct set of kernel headers installed
on your system.

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the "KBUILD_OUTPUT" or
the "O" KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

Depending on where and how the kernel sources (or the
kernel headers) were installed, you may need to specify
their location with the SYSSRC environment variable or
the equivalent nvidia-installer command line option.

*** Unable to determine the target kernel version. ***

make: *** [select_makefile] Ошибка 1
emake failed
 * ERROR: x11-drivers/nvidia-drivers-295.33 failed (compile phase):
 *   Unable to emake HOSTCC=i686-pc-linux-gnu-gcc CROSS_COMPILE=i686-pc-linux-gnu- LDFLAGS=  IGNORE_CC_MISMATCH=yes V=1 SYSSRC=/usr/src/linux           SYSOUT=/lib/modules/3.3.0-gentoo/build CC=i686-pc-linux-gnu-gcc clean module
 * 
 * Call stack:
 *     ebuild.sh, line   85:  Called src_compile
 *   environment, line 3669:  Called linux-mod_src_compile
 *   environment, line 2626:  Called die
 * The specific snippet of code:
 *               eval "emake HOSTCC=\"$(tc-getBUILD_CC)\"                                               CROSS_COMPILE=${CHOST}-                                       LDFLAGS=\"$(get_abi_LDFLAGS)\"                                           ${BUILD_FIXES}                                          ${BUILD_PARAMS}                       ${BUILD_TARGETS} " || die "Unable to emake HOSTCC="$(tc-getBUILD_CC)" CROSS_COMPILE=${CHOST}- LDFLAGS="$(get_abi_LDFLAGS)" ${BUILD_FIXES} ${BUILD_PARAMS} ${BUILD_TARGETS}";
 * 
 * If you need support, post the output of 'emerge --info =x11-drivers/nvidia-drivers-295.33',
 * the complete build log and the output of 'emerge -pqv =x11-drivers/nvidia-drivers-295.33'.
 * This ebuild is from an overlay named 'local-overlay': '/usr/local/portage/'
 * The complete build log is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-295.33/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/x11-drivers/nvidia-drivers-295.33/temp/environment'.
 * S: '/var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work/'

bsdfun ★★★★★
()

Вчера только везде поставил 295.20... so sloooooow...

coldy ★★
()
Ответ на: комментарий от bsdfun

If you are using a Linux 2.6 kernel, please make sure
you have configured kernel sources matching your kernel
installed on your system. If you specified a separate
output directory using either the «KBUILD_OUTPUT» or
the «O» KBUILD parameter, make sure to specify this
directory with the SYSOUT environment variable or with
the equivalent nvidia-installer command line option.

можно читать и как Linux 3.х kernel

anTaRes ★★★★
()
Ответ на: комментарий от anTaRes

Собрал, опакетил, установил, перезагрузился в kernel-3.3; запустил SMPlayer с backend'ом mplayer2, выставил использование VDPAU, открыл файлик в ~ 7,2 ГиБ; таскаю окна ― тормозят, как и на 295.20 (и, скорее всего, ещё раньше)!

Это не тот баг.

carasin ★★★★★
() 
>>> Preparing source in /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/work ...
 * Applying 256.35-unified-arch.patch ...

 * Failed Patch: 256.35-unified-arch.patch !
 *  ( /usr/portage/x11-drivers/nvidia-drivers/files/256.35-unified-arch.patch )
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/x11-drivers/nvidia-drivers-295.33/temp/256.35-unified-arch.patch.out

 * ERROR: x11-drivers/nvidia-drivers-295.33 failed (prepare phase):
 *   Failed Patch: 256.35-unified-arch.patch!

кто столкнулся с подобным?

Ведро 3.2.1-gentoo-r2

leg0las ★★★★★
()
Ответ на: комментарий от leg0las

unified-arch не наложить
там таких конструкций просто нет

megabaks ★★★★
() автор топика
Ответ на: комментарий от megabaks

а хер - после синка дерева всё отвалилось
один дебил неглядя бампнул
потом замаскировали
потом и сломали что-то
ппц

megabaks ★★★★
() автор топика
Ответ на: комментарий от anTaRes

Я, конечно, не силён в BASH'е (впрочем, как и вообще в ЯП), но по моей ссылке это: 

    CFLAGS="$BASE_CFLAGS $MACH_CFLAGS $OUTPUT_CFLAGS -I$HEADERS $AUTOCONF_CFLAGS"
    if [ "$ARCH" = "i386" -o "$ARCH" = "x86_64" ]; then
        CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include -I$SOURCES/arch/x86/include/generated"
    elif [ "$ARCH" = "ARMv7" ]; then
        CFLAGS="$CFLAGS -I$SOURCES/arch/arm/include -I$SOURCES/arch/arm/include/generated"
    fi
А вот патч для 295.20: 
diff -Naur kernel-orig/conftest.sh kernel/conftest.sh
--- kernel/conftest.sh  2011-12-22 04:20:25.000000000 -0500
+++ kernel/conftest.sh  2012-01-20 18:02:25.280700816 -0500
@@ -126,7 +126,7 @@
     CFLAGS="$BASE_CFLAGS $MACH_CFLAGS $OUTPUT_CFLAGS -I$HEADERS $AUTOCONF_CFLAGS"
 
     if [ "$ARCH" = "i386" -o "$ARCH" = "x86_64" -o "$ARCH" = "x86" ]; then
-        CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include"
+        CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include -I$SOURCES/arch/x86/include/generated"
     elif [ "$ARCH" = "ARMv7" ]; then
         CFLAGS="$CFLAGS -I$SOURCES/arch/arm/include"
     fi

carasin ★★★★★
()
Ответ на: комментарий от G-UNiX 
apt-cache policy xserver-xorg-video-nvidia
xserver-xorg-video-nvidia:
  Установлен: 295.33-1
  Кандидат:   295.33-1
  Таблица версий:
 *** 295.33-1 0
        500 http://ftp.debian.org/debian/ sid/non-free i386 Packages
        100 /var/lib/dpkg/status
warteraum ★
()
Ответ на: комментарий от carasin

а вот то что по ссылке 

--- kernel/conftest.sh.orig	2012-03-17 22:56:28.000000000 +0100
+++ kernel/conftest.sh	2012-03-23 14:18:41.000000000 +0100
@@ -126,9 +126,9 @@
     CFLAGS="$BASE_CFLAGS $MACH_CFLAGS $OUTPUT_CFLAGS -I$HEADERS $AUTOCONF_CFLAGS"
 
     if [ "$ARCH" = "i386" -o "$ARCH" = "x86_64" ]; then
-        CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include -I$SOURCES/arch/x86/include/generated"
+        CFLAGS="$CFLAGS -I$SOURCES/arch/x86/include -I$OUTPUT/arch/x86/include/generated"
     elif [ "$ARCH" = "ARMv7" ]; then
-        CFLAGS="$CFLAGS -I$SOURCES/arch/arm/include -I$SOURCES/arch/arm/include/generated"
+        CFLAGS="$CFLAGS -I$SOURCES/arch/arm/include -I$OUTPUT/arch/arm/include/generated"
     fi
     if [ -n "$BUILD_PARAMS" ]; then
         CFLAGS="$CFLAGS -D$BUILD_PARAMS"

anTaRes ★★★★
()
Ответ на: комментарий от carasin

Хотя, там по ссылке говорится уже о 295.33, типа бага в нём. Нихрена не понял: у меня собралось на 3.2 и 3.3 (без этого патча) без проблем и работает.

Короче, можете объяснить, на что влияет эта бага?

carasin ★★★★★
()
Ответ на: комментарий от carasin

если $SOURCES != $OUTPUT то никаких $SOURCES/arch/x86/include/generated не будет

я не телепат , но возможно у товарища выше ядришко собирается в другую директорию , дабы сохранить девственную чистоту сырцов . хз
потому и не находит include/generated

anTaRes ★★★★
()
Ответ на: комментарий от anTaRes

Примерно понятно, спасибо.

Значит, проблема проявляется не у всех.

carasin ★★★★★
()
Вы не можете добавлять комментарии в эту тему. Тема перемещена в архив.
  1 2 →
← [Ъ]Самодельный компьютер
Talks
Свободная бытовая техника? →