On Sun, 2016-07-10 at 18:56 +0200, hikaru.deb...@web.de wrote: > > Yes it should be made clearer, if you are on amd64 and want the 32 bit > > libraries, not all packages should be installed. > > > > Basically you'll want to install libgl1-nvidia-glx-i386 (or > > nvidia-driver-libs-i386 depending on the branch) and their dependencies. > > > > I've updated the wiki. > > Thanks! But that isn't the problem. > fyi, I've switched the test system from i386 to amd64, but the basic problem > remains. > > Maybe I should also tell you some things about my system setup: > The test system is Jessie/amd64 on a USB stick. It is currently plugged into a > computer with a GT218 chip. I know this isn't supportd by 367 anymore, but I > merely want to make sure the driver installation works fine, because later I > want to plug the USB stick into a computer with a GTX 1070 card. I only have > access to this actual target computer sporadically, hence the test system. > > What I did was to install Jessie's nvidia-driver and the X-Server works. I > wanted to use this package list as a template for what I actually need from > 367: > > # dpkg -l | grep nvidia > ii glx-alternative-nvidia 0.5.1 > amd64 allows the selection of NVIDIA as GLX provider > ii libegl1-nvidia:amd64 340.96-1 > amd64 NVIDIA binary EGL libraries > ii libgl1-nvidia-glx:amd64 340.96-1 > amd64 NVIDIA binary OpenGL libraries > ii libgles1-nvidia:amd64 340.96-1 > amd64 NVIDIA binary OpenGL|ES 1.x libraries > ii libgles2-nvidia:amd64 340.96-1 > amd64 NVIDIA binary OpenGL|ES 2.x libraries > ii libnvidia-eglcore:amd64 340.96-1 > amd64 NVIDIA binary EGL core libraries > ii libnvidia-ml1:amd64 340.96-1 > amd64 NVIDIA Management Library (NVML) runtime library > ii nvidia-alternative 340.96-1 > amd64 allows the selection of NVIDIA as GLX provider > ii nvidia-driver 340.96-1 > amd64 NVIDIA metapackage > ii nvidia-driver-bin 340.96-1 > amd64 NVIDIA driver support binaries > ii nvidia-installer-cleanup 20141201+1 > amd64 cleanup after driver installation with the nvidia-installer > ii nvidia-kernel-common 20141201+1 > amd64 NVIDIA binary kernel module support files > ii nvidia-kernel-dkms 340.96-1 > amd64 NVIDIA binary kernel module DKMS source > ii nvidia-modprobe 340.46-1 > amd64 utility to load NVIDIA kernel modules and create device nodes > ii nvidia-settings 340.46-2 > amd64 tool for configuring the NVIDIA graphics driver > ii nvidia-support 20141201+1 > amd64 NVIDIA binary graphics driver support files > ii nvidia-vdpau-driver:amd64 340.96-1 > amd64 Video Decode and Presentation API for Unix - NVIDIA driver > ii xserver-xorg-video-nvidia 340.96-1 > amd64 NVIDIA binary Xorg driver > > > Since apt's dependency resolution isn't available with the self-made packages, > I then wanted to replace all these packages at once via dpkg, which failed due > to dependency problems. To track these down, I wanted to atomize the process. > nvidia-driver seemed to be a good starting point, however it complains during > the installation: > > # dpkg -i nvidia-driver_367.27-1_amd64.deb > dpkg: regarding nvidia-driver_367.27-1_amd64.deb containing nvidia-driver, > pre-dependency problem: > nvidia-driver pre-depends on nvidia-legacy-check (>= 343) > nvidia-legacy-check is not installed. > > dpkg: error processing archive nvidia-driver_367.27-1_amd64.deb (--install): > pre-dependency problem - not installing nvidia-driver > Errors were encountered while processing: > nvidia-driver_367.27-1_amd64.deb > > > So I successfully installed nvidia-legacy-check first: > > # dpkg -i nvidia-legacy-check_367.27-1_amd64.deb > Selecting previously unselected package nvidia-legacy-check. > (Reading database ... 131797 files and directories currently installed.) > Preparing to unpack nvidia-legacy-check_367.27-1_amd64.deb ... > *** The following unsupported devices are present in the machine: > 03:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] > [10de:0a64] (rev a2) > Unpacking nvidia-legacy-check (367.27-1) ... > Setting up nvidia-legacy-check (367.27-1) ... > > > Then I tried to install nvidia-driver, which failed: > > # dpkg -i nvidia-driver_367.27-1_amd64.deb > (Reading database ... 131811 files and directories currently installed.) > Preparing to unpack nvidia-driver_367.27-1_amd64.deb ... > Unpacking nvidia-driver (367.27-1) over (340.96-1) ... > dpkg: error processing archive nvidia-driver_367.27-1_amd64.deb (--install): > trying to overwrite '/DEBIAN/control', which is also in package > nvidia-legacy-check 367.27-1 > Errors were encountered while processing: > nvidia-driver_367.27-1_amd64.deb
legacy-check will not let you progress since that driver does not support your system. This is intentional, that's the purpose of nvidia-legacy-check. You could hack the package before installing it, and remove the pre-depends on it from nvidia-driver if you are really sure you want to do that. > From the output I believe Andreas is right, and that something went wrong > during the package-building process: > > > something went amiss when building the packages, the /DEBIAN directory > > should never be part of the package that gets installed in the > > filesystem (it just belongs into the control archive). > > > Now there actually is a /DEBIAN directory on my system: > > # ls -l /DEBIAN/ > total 24 > -rw-r--r-- 1 root root 702 Jul 9 19:45 control > -rw-r--r-- 1 root root 480 Jul 9 19:45 md5sums > -rwxr-xr-x 1 root root 206 Jul 9 19:45 postrm > -rwxr-xr-x 1 root root 4473 Jul 9 19:45 preinst > -rw-r--r-- 1 root root 1335 Jul 9 19:45 templates > > > I should probably note, that although I have some experience with svn in > general and that I've (re)built packages with debuild before, this is the > first > time I use debian/rules and svn-buildpackage. So I don't fully understand what > I'm doing here, which is why I strictly stuck to the wiki-instructions. That is quite strange, I'm really not sure what could cause that to happen sorry. Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
