Re: Installing cinelerra on sid
Hi andrea, i've never installed the binary packages, i've always built it from the source. I have this sources.list: deb http://amd64.debian.net/debian/ unstable main contrib non-free deb-src http://amd64.debian.net/debian/ unstable main contrib non-free # Fuentes del cinelerra deb-src http://www.kiberpipa.org/~minmax/cinelerra/builds/sid/ ./ # Repositorio de marillat para amd64 deb http://spello.sscnet.ucla.edu/marillat/ sid main # Para el dvdcss deb ftp://ftp.nerim.net/debian-marillat/ sid main # Sources Marillat deb-src ftp://ftp.nerim.net/debian-marillat/ sid main I'm not sure if cinelerra sources (via apt-get source cinelerra) come from marillat or kiberpipa, anyway... Before the compilation starts i've always changed the command for ./configure in debian/rules, this is my line modified: CFLAGS=$(CFLAGS) CXXFLAGS=$(CXXFLAGS) \ ./configure --prefix=/usr --with-pic And the CFLAGS is: CFLAGS=-ffast-math -O3 -march=athlon64 I hope this can help you. On Mon, 27 Mar 2006 23:01:21 +0200 Andrea Tacchetti [EMAIL PROTECTED] wrote: Installing cinelerra on sid -- There's no religion but sex and music --Sting
Re: Installing cinelerra on sid
Hi every one, I'm trying to install cinelerra on sid, I'm following this guide : http://cvs.cinelerra.org/getting_cinelerra.html Although it fails in solving some dependencies, here is some output from apt: $ sudo apt-get update Hit ftp://ftp.it.debian.org unstable Release.gpg Hit ftp://ftp.nerim.net sid Release.gpg Hit ftp://ftp.it.debian.org unstable Release Get:1 ftp://ftp.nerim.net sid Release [2864B] Hit ftp://ftp.it.debian.org unstable/main Packages Hit ftp://ftp.it.debian.org unstable/contrib Packages Hit ftp://ftp.it.debian.org unstable/non-free Packages Hit ftp://ftp.nerim.net sid/main Packages Hit ftp://ftp.it.debian.org unstable/main Sources Hit ftp://ftp.it.debian.org unstable/contrib Sources Hit ftp://ftp.it.debian.org unstable/non-free Sources Ign http://hackitectura.net ./ Release.gpg Ign http://hackitectura.net ./ Release Ign http://hackitectura.net ./ Packages Ign http://hackitectura.net ./ Sources Hit http://hackitectura.net ./ Packages Hit http://hackitectura.net ./ Sources Scaricato 2864B in 16s (173B/s) Lettura della lista dei pacchetti in corso... $ sudo apt-get install cinelerra Lettura della lista dei pacchetti in corso... Generazione dell'albero delle dipendenze in corso... Alcuni pacchetti non possono essere installati. Questo può voler dire che è stata richiesta una situazione impossibile oppure, se si sta usando la distribuzione unstable, che alcuni pacchetti richiesti non sono ancora stati creati o rimossi da incoming. Poiché è stata richiesta solo una singola operazione è molto facile che il pacchetto semplicemente non sia installabile, si consiglia di inviare un bug report per tale pacchetto. Le seguenti informazioni possono aiutare a risolvere la situazione: I seguenti pacchetti hanno dipendenze non soddisfatte: cinelerra: Dipende: liblame0 (= 3.96.1-1) ma non è installabile Dipende: libmjpegtools0 (= 1:1.8.0) ma non è installabile Dipende: libquicktimehv (= 1:2.0.0) ma non sta per essere installato Dipende: libquicktimehv (= 1:2.0.0-1svn20060213) ma non sta per essere installato hi.well, i'm italian too and the amd64 packaging manteiner.i think you only need to add marillat source in order to get and libfame and libmjpegtools0...then everything should work: deb-src ftp://ftp.nerim.net/debian-marillat/ sid main deb http://spello.sscnet.ucla.edu/marillat/ sid main deb ftp://ftp.nerim.net/debian-marillat/ sid main sto attenta a la listacommentami qualunque problema, ciao vale Sorry for the italian lines, it basically says it failes in finding thoes packages. (cinelerra: Depenso on: [...] but it's not installable / it's not going to be installed) Has anyone of you out there succeded in installing cinelerra under sid? Please let me know how you have done that, or how you think I might solve my problem. Thank you, greetings Takke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing cinelerra on sid
I seguenti pacchetti hanno dipendenze non soddisfatte: cinelerra: Dipende: liblame0 (= 3.96.1-1) ma non è installabile Dipende: libmjpegtools0 (= 1:1.8.0) ma non è installabile Dipende: libquicktimehv (= 1:2.0.0) ma non sta per essere installato Dipende: libquicktimehv (= 1:2.0.0-1svn20060213) ma non sta per essere installato hi.well, i'm italian too and the amd64 packaging manteiner.i think you only need to add marillat source in order to get and libfame and libmjpegtools0...then everything should work: deb-src ftp://ftp.nerim.net/debian-marillat/ sid main deb http://spello.sscnet.ucla.edu/marillat/ sid main deb ftp://ftp.nerim.net/debian-marillat/ sid main sto attenta a la listacommentami qualunque problema, ciao vale Sorry for the italian lines, it basically says it failes in finding thoes packages. (cinelerra: Depenso on: [...] but it's not installable / it's not going to be installed) Has anyone of you out there succeded in installing cinelerra under sid? Please let me know how you have done that, or how you think I might solve my problem. Thank you, greetings Takke -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
AMD64 nvidia kernels in only some distributions
I searched for nvidia-kernel-source and discovered 1.0.7174-3: amd64 for stable 1.0.7174-3: amd64 for unstable Is there any reason I should fear why the same package is not in testing? Or is it just a mistake or inertia resulting from Debian slow-migration policies? -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 nvidia kernels in only some distributions
On Tue, Mar 28, 2006 at 10:35:15AM -0500, [EMAIL PROTECTED] wrote: I searched for nvidia-kernel-source and discovered 1.0.7174-3: amd64 for stable 1.0.7174-3: amd64 for unstable Is there any reason I should fear why the same package is not in testing? Or is it just a mistake or inertia resulting from Debian slow-migration policies? Well if it was following debian, it would have 8178 in unstable right now. non-free is all manual, until it joins debian fully. I hope that finishes soon. Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AMD64 nvidia kernels in only some distributions
On Tue, Mar 28, 2006 at 10:38:27AM -0500, Lennart Sorensen wrote: On Tue, Mar 28, 2006 at 10:35:15AM -0500, [EMAIL PROTECTED] wrote: I searched for nvidia-kernel-source and discovered 1.0.7174-3: amd64 for stable 1.0.7174-3: amd64 for unstable Is there any reason I should fear why the same package is not in testing? Or is it just a mistake or inertia resulting from Debian slow-migration policies? Well if it was following debian, it would have 8178 in unstable right now. non-free is all manual, until it joins debian fully. I hope that finishes soon. Len Sorensen Thanks. Nothing scary, then. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
howto says up to 2.6.11 -- is this outdated?
The Debian GNU/Linux AMD64 HOW-TO from http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html says in the section Is nvidia card supported for sarge, or using a stock kernel up to 2.6.11: go to /usr/src/kernel-headers-2.6.8-11-amd64-k8 (or whatever headers you installed) after you unpacked the nvidia-kernel-source tarball in /usr/src and run MAKEFLAGS=CC=gcc-3.4 make-kpkg --append-to-version -11-amd64-k8 modules_image again, replace -11-amd64-k8 with the flavour of your kernel. Is the restriction on kernels up to 2.6.11 serious? Or is it just out-of-date or extra careful. I'm running etch with linux-image-2.6.12-1-amd64-generic_2.6.12-10_amd64.deb The X I'm trying to get up is xorg. By the way, the system is doing what I got it for just perfectly. It's the most reliable system on my net Getting X up on it would be the icing on the cake. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: howto says up to 2.6.11 -- is this outdated?
Hello Hendrik, I guess it is just outdated. The debianized nvidia driver (1.0.8178-1) works on my AMD64 with kernel 2.6.15-1-amd64-k8 and Xorg 6.9.0 without any problems so far. deb64a:~$ Xorg -version X Window System Version 6.9.0 (Debian 6.9.0.dfsg.1-4 20060117044708 Frederik Schüler [EMAIL PROTECTED]) Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 6.9 Build Operating System: Linux 2.6.15-1-amd64-k8-smp x86_64 [ELF] Current Operating System: Linux deb64a 2.6.15-1-amd64-k8 #2 Tue Mar 7 06:53:26 UTC 2006 x86_64 Build Date: 17 January 2006 @deb64a:~$ ls /usr/src/modules/ nvidia-kernel nvidia-kernel-2.6.15-1-amd64-k8_1.0.8178-1_amd64.deb Alexander On Tue, Mar 28, 2006 at 11:26:57AM -0500, [EMAIL PROTECTED] wrote: The Debian GNU/Linux AMD64 HOW-TO from http://alioth.debian.org/docman/view.php/30192/21/debian-amd64-howto.html says in the section Is nvidia card supported for sarge, or using a stock kernel up to 2.6.11: go to /usr/src/kernel-headers-2.6.8-11-amd64-k8 (or whatever headers you installed) after you unpacked the nvidia-kernel-source tarball in /usr/src and run MAKEFLAGS=CC=gcc-3.4 make-kpkg --append-to-version -11-amd64-k8 modules_image again, replace -11-amd64-k8 with the flavour of your kernel. Is the restriction on kernels up to 2.6.11 serious? Or is it just out-of-date or extra careful. I'm running etch with linux-image-2.6.12-1-amd64-generic_2.6.12-10_amd64.deb The X I'm trying to get up is xorg. By the way, the system is doing what I got it for just perfectly. It's the most reliable system on my net Getting X up on it would be the icing on the cake. -- hendrik -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
scsi controller for external devices
building a workstation with amd64 dual opterons on mainboard tyan k8we s2895sa3nrf and debian testing/unstable, i need a one-connector (fifty pin half pitch) fast scsi controller for external chain of cd, scanner, and backup hd. same chain currently works perfectly with fast scsi controller adaptec aic-7850 (no more available in my country) on AMD Athlon debian 32 testing/unstable. thanks for helping francesco pietra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: howto says up to 2.6.11 -- is this outdated?
On Tue, 28 Mar 2006 18:30:21 +0200, hendrik wrote: Is the restriction on kernels up to 2.6.11 serious? At the time of the writing 2.6.11 was the newest kernel. I am running the nvidia drivers with a 2.6.16 kernel. -- Best Regards, Jack Linux User #264449 Powered by Debian GNU/Linux on AMD64 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: howto says up to 2.6.11 -- is this outdated?
On Tue, 2006-03-28 at 20:34 +0200, Jack Malmostoso wrote: On Tue, 28 Mar 2006 18:30:21 +0200, hendrik wrote: Is the restriction on kernels up to 2.6.11 serious? At the time of the writing 2.6.11 was the newest kernel. I am running the nvidia drivers with a 2.6.16 kernel. -- I am not tried to install the nvidia drivers from http://people.debian.org/~rdonald/nvidia/ but I get an error in the kernel modules compilation /usr/src/modules/nvidia-kernel/nv/nv.c:1640: error: 'mem_map' undeclared (first use in this function) /usr/src/modules/nvidia-kernel/nv/nv.c:1640: error: (Each undeclared identifier is reported only once /usr/src/modules/nvidia-kernel/nv/nv.c:1640: error: for each function it appears in.) Then the compilation stops. Stefano -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi controller for external devices
On Tuesday 28 March 2006 10:25, Francesco Pietra wrote: tyan k8we Fast MB, unless you have all the (external) devices left over, I would't bother with fast scsi as I/O. With that board you have USB2, Firewire 400, and with an add in card firewire 800. That card ad or the devices attched to it becomes the bottleneck for perfornance. If you have to go scsi I would get a cheaper card, I have used a Tekram DC-315U and a SIIG AP-10, both supported by Etch. -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi controller for external devices
thanks a lot for pointing out the bottleneck. is that bottleneck also when no external device is attached to the scsi controller? i intend to connect the scsi chain to the workstation only occasionally for scanning and backup to have access to data by an ordinary pc. normally the scsi chain is connected to the pc. if the scsi controller causes a bottleneck per se, what about accessing the scsi devices attached to the pc from the workstation through the zyxel adsl rooter? i need that motherboard to get the best floating point for the money. with that workstation i am already at the lower limit to do ab inition quantum chemical calculations for large molecules. thank you again francesco pietra On Wednesday 29 March 2006 00:30, Greg Madden wrote: On Tuesday 28 March 2006 10:25, Francesco Pietra wrote: tyan k8we Fast MB, unless you have all the (external) devices left over, I would't bother with fast scsi as I/O. With that board you have USB2, Firewire 400, and with an add in card firewire 800. That card ad or the devices attched to it becomes the bottleneck for perfornance. If you have to go scsi I would get a cheaper card, I have used a Tekram DC-315U and a SIIG AP-10, both supported by Etch. -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.6.16 and nvidia?
this i a knowen bug, nvidia has a patch for this problem http://www.nvnews.net/vbulletin/showthread.php?t=62021 On Thu, 2006-03-23 at 09:32 -0500, Andrew Schulman wrote: I grabbed latest 2.6.16 kernel source today from experimental and tried to compile the available nvidia kernel module. I got: usr/src/modules/nvidia-kernel/nv/nv-linux.h:535:2: #error vmap() appears to be unavailable in this kernel! /usr/src/modules/nvidia-kernel/nv/nv-linux.h:715:2: warning: #warning conftest.sh failed, assuming remap_page_range(4)! Anyone has a hint for me? Hint: search the archives of this list for 'nvidia' within the 3 days or so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: scsi controller for external devices
On Tuesday 28 March 2006 12:56, Francesco Pietra wrote: thanks a lot for pointing out the bottleneck. is that bottleneck also when no external device is attached to the scsi controller? i intend to connect the scsi chain to the workstation only occasionally for scanning and backup to have access to data by an ordinary pc. normally the scsi chain is connected to the pc. if the scsi controller causes a bottleneck per se, what about accessing the scsi devices attached to the pc from the workstation through the zyxel adsl rooter? i need that motherboard to get the best floating point for the money. with that workstation i am already at the lower limit to do ab inition quantum chemical calculations for large molecules. thank you again francesco pietra On Wednesday 29 March 2006 00:30, Greg Madden wrote: On Tuesday 28 March 2006 10:25, Francesco Pietra wrote: tyan k8we Fast MB, unless you have all the (external) devices left over, I would't bother with fast scsi as I/O. With that board you have USB2, Firewire 400, and with an add in card firewire 800. That card ad or the devices attched to it becomes the bottleneck for perfornance. If you have to go scsi I would get a cheaper card, I have used a Tekram DC-315U and a SIIG AP-10, both supported by Etch. -- Greg Madden The card won't cause an issue when the devices are not being used. It is just when using the devices, with fast scsi you have to wait for the results, if applicable, of those operations. It all depends on what you do with your system, I.E. scanning high res color photo photos can create a large file that takes (x)time to transfer over scsi, while the USB2 would transfer much faster 480Mbs or 60MB/s vs the 10-20? MB/s for fast scsi, same with a hard drive. Of course if you don't use those peripherals that much it isn't an issue. -- Greg Madden -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
