Version matching in kernel source and patch source?
I'd like to try to compile my own kernel, using the realtime patch set. At kernel.org, I see that the 6.6 kernel source is 6.6, but the 6.6 realtime patch set is 6.6-rt12. Does that matter, or is it enough that both are given as 6.6? Similarly, if I see that the 6.5 series is at 6.5.10 for the kernel source at kernel.org, and the patch set is 6.5.2-rt8, is that an issue, or do I always need to use patches which match the version numbering completely? Thanks! Scott Denlinger
nvidia-kernel-source 304.88-6
My thanks to the developing classes of Debian who as together or as one (it only takes one) fixed this package that fixed the module that fixed the nvidia driver. Good show. -- CK where should my humble contribution be directed? signature.asc Description: PGP signature
kernel source package with applied patches
Hello, I plan to create a source tarball of the Debian Linux kernel with patches already applied in oder to build a kernel, based on Debian kernel sources, on other, non-Debian based distros. As far as I can tell I must do it the following way. - Download linux-2.6_[version].orig.tar.gz - Download linux-2.6_[version]-[patchlevel].dsc - Download linux-2.6_[version]-[patchlevel].diff.gz - Running dpkg-source -x linux-2.6_[version]-[patchlevel].dsc This produces the directory linux-2.6-[version]. Patches aren't applied yet and can be found at the subdirectory debian/patches. To apply the patches I run - fakeroot debian/rules source Now I can see that the patches are applied. According to http://kernel-handbook.alioth.debian.org/ch-common-tasks.html the patched kernel source is now at debian/build/source. So all I must do is to create a tarball of that subdirectory. Am I correct so far? Regards, Henry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110815154218.20c85c6b.hjen...@gmx.de
Re: Mainline kernel source curiosity
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 20 September 2010, Arthur Machlas was heard to say: My guess is you need to build the header at least, and perhaps the source. It depends on how you're building the modules I suppose. In any case, you'll have to run either fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers fakeroot make-kpkg --append-to-version -curt1.0 kernel_image Ok, I did build the headers as a package, and installed it, so now there's a /usr/src/linux-headers-2.6.36-rc4-curt1.0/ and the same error comes up: /var/log/vbox-install.log Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. Anyway, thank you for the suggestion, I'm sorry it didn't work. I'll take it up at the VirtualBox forum, in case anyone else has had the same difficulty. Curt- - -- Those who torment us for our own good will torment us without end, for they do so with the approval of their consciences. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBTJiyxi9Y35yItIgBAQI9NAf/ZTaPQ9QRZ4QxLknGYJNzxGUwzLUf+6ub D+7MkUsAYGskxKY4/46kZa45w0DYcT+mbZbpCq9jZOYkAlG3LhLY+lr5eK5kMwRa pYWfxxL8YUdZ4b2P4UmqnDgcaDYRL+OGLbt6GNEYIO3XGvm8EefQ76RvyOKmRqN7 JuOW4q4pSidGmGgDSXRq/l2ozqpYmG2LQjEQuRnXJJ7tuTZHNtSZJ5EmBmWITIUl MFC7cXYmU0TsIi2M2xxFM7M3iXJeTBV7VbZW1d6yyLc58usd5tsWau9hA130ABy2 ZsKH924fjPU7F4oFvg+Fd5BeY8BYE+O70ImKbPfIZIrjN2Pz7Zmxxw== =53sG -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009210927.34316.howl...@priss.com
Re: Mainline kernel source curiosity
On 9/21/2010 7:27 AM, Curt Howland wrote: On Monday 20 September 2010, Arthur Machlas was heard to say: My guess is you need to build the header at least, and perhaps the source. It depends on how you're building the modules I suppose. In any case, you'll have to run either fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers fakeroot make-kpkg --append-to-version -curt1.0 kernel_image Ok, I did build the headers as a package, and installed it, so now there's a /usr/src/linux-headers-2.6.36-rc4-curt1.0/ and the same error comes up: /var/log/vbox-install.log Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. Had the same problem! Instead of using --append-to-version, use the version append in *kernel config* make menuconfig, search around for Append to version make-kpkg doesn't monger linux/version.h IIRC. -- Morgan Gangwere Why? Because it breaks the logical flow of conversation, plus makes messages unreadable. Top-Posting is evil. signature.asc Description: OpenPGP digital signature
Mainline kernel source curiosity
Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel. Last time the problem was compiling the kernel at all, which is working just fine now thank you Debian-User. fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image creates the .deb file just fine, it installs fine, but when I run it and try to get the VirtualBox and Nvidia drivers to compile, this is what I get: from vbox-installer.log == Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. == The thing is, there is no such error with 2.6.35.4-curt1.0, nor when it was 35-rc4-curt1.0. So why would it be choking on the custom extension now? I used _exactly_ the same compile command, listed above. from /var/log/nvidia-installer.log === In file included from include/linux/kernel.h:17, from include/linux/sched.h:54, from include/linux/utsname.h:35, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv-linu x.h:27, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:13 : include/linux/bitops.h: In function ‘hweight_long’: include/linux/bitops.h:49: warning: signed and unsigned type in conditional expression In file included from /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess .h:571, from include/linux/poll.h:14, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv-linu x.h:84, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:13 : /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess_32.h: In function ‘ copy_from_user’: /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess_32.h:209: warning: co mparison between signed and unsigned integer expressions /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c: At top level: /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:426: error: unknown fiel d ‘ioctl’ specified in initializer /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:426: warning: initializa tion from incompatible pointer type make[4]: *** [/tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.o] Error 1 make[3]: *** [_module_/tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel] Error 2 make[2]: *** [sub-make] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 - Error. ERROR: Unable to build the NVIDIA kernel module. == Which I guess means I have to wait for Nvidia to fix a signed vs unsigned change in the kernel source. Can folks suggest if it would be worth while reporting this to Nvidia? Curt- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktin5qbwt_-4waqdoanowbvmsv=zxrh=t94lir...@mail.gmail.com
Re: Mainline kernel source curiosity
On Mon, Sep 20, 2010 at 12:25 PM, Curt Howland howl...@priss.com wrote: Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel. Last time the problem was compiling the kernel at all, which is working just fine now thank you Debian-User. fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image My guess is you need to build the header at least, and perhaps the source. It depends on how you're building the modules I suppose. In any case, you'll have to run either fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers fakeroot make-kpkg --append-to-version -curt1.0 kernel_image And install the debs. Alternatively, build both just to be safe fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers kernel_image -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikjm7_zjg48lafvuqa0omvac_lmggazsvhbj...@mail.gmail.com
Re: Mainline kernel source curiosity
On Mon, Sep 20, 2010 at 01:25:45PM -0400, Curt Howland wrote: Last time the problem was compiling the kernel at all, which is working just fine now thank you Debian-User. fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image creates the .deb file just fine, it installs fine, but when I run it and try to get the VirtualBox and Nvidia drivers to compile, this is what I get: from vbox-installer.log == Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. == The thing is, there is no such error with 2.6.35.4-curt1.0, nor when it was 35-rc4-curt1.0. So why would it be choking on the custom extension now? I used _exactly_ the same compile command, listed above. Is this a manifestation of this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591793 I am unsure, but I was under the impression that kernel-package is broken for the most recent kernels. Thanks. Kumar -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100920175012.gf23...@bowser.ece.utexas.edu
Re: Mainline kernel source curiosity
On Mon, 20 Sep 2010 13:25:45 -0400 (EDT), Curt Howland wrote: Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel. Last time the problem was compiling the kernel at all, which is working just fine now thank you Debian-User. fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image creates the .deb file just fine, it installs fine, but when I run it and try to get the VirtualBox and Nvidia drivers to compile, this is what I get: from vbox-installer.log == Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. == The thing is, there is no such error with 2.6.35.4-curt1.0, nor when it was 35-rc4-curt1.0. So why would it be choking on the custom extension now? I used _exactly_ the same compile command, listed above. Curt, I can't address your specific situation, but perhaps my kernel-building web page http://www.wowway.com/~zlinuxman/Kernel.htm will be helpful to you. I have a specific example now for building Nvidia drivers, which is covered near the end of the document under the heading, A specific example. Perhaps your virtualbox problems can be solved in a similar manner. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/885015105.128213.1285006234715.javamail.r...@md01.wow.synacor.com
Re: Mainline kernel source curiosity
On Mon, 20 Sep 2010 13:50:12 -0400 (EDT), Kumar Appaiah wrote: On Mon, Sep 20, 2010 at 01:25:45PM -0400, Curt Howland wrote: == Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. == The thing is, there is no such error with 2.6.35.4-curt1.0, nor when it was 35-rc4-curt1.0. So why would it be choking on the custom extension now? I used _exactly_ the same compile command, listed above. Is this a manifestation of this: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591793 I am unsure, but I was under the impression that kernel-package is broken for the most recent kernels. Curt, I don't know if this is related to the problem or not, but make sure that you don't have CONFIG_LOCALVERSION or CONFIG_LOCALVERSION_AUTO set in your kernel configuration file and make sure that you specify --append-to-version and --revision on *every* invocation of make-kpkg. How are you creating the virtualbox and nvidia packages? Are you using module-assistant? Or are you compiling a kernel source module package using the modules_image target of make-kpkg? If you are using module-assistant (which I don't recommend if you are building out-of-kernel-source-tree kernel module packages for a custom kernel) then you will need to use the kernel_headers target as well as the kernel_image target, then install both before moving on to create the modules package. It is best to install the Debian out-of-kernel-source-tree kernel module source package and use the kernel_image and modules_image targets. Then you don't have to create or install kernel header packages. HTH -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1766196363.128836.1285007540897.javamail.r...@md01.wow.synacor.com
Re: Mainline kernel source curiosity
Le 20/09/2010 19:25, Curt Howland wrote: Hi. Up to date Squeeze, compiling the latest 2.6.36-rc4 kernel. Last time the problem was compiling the kernel at all, which is working just fine now thank you Debian-User. fakeroot make-kpkg --append-to-version -curt1.0 --initrd kernel_image creates the .deb file just fine, it installs fine, but when I run it and try to get the VirtualBox and Nvidia drivers to compile, this is what I get: from vbox-installer.log == Makefile:170: *** Error: /usr/src/linux (version 2.6.36-rc4) does not match the current kernel (version 2.6.36-rc4-curt1.0). Stop. == The thing is, there is no such error with 2.6.35.4-curt1.0, nor when it was 35-rc4-curt1.0. So why would it be choking on the custom extension now? I used _exactly_ the same compile command, listed above. from /var/log/nvidia-installer.log === In file included from include/linux/kernel.h:17, from include/linux/sched.h:54, from include/linux/utsname.h:35, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv-linu x.h:27, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:13 : include/linux/bitops.h: In function ‘hweight_long’: include/linux/bitops.h:49: warning: signed and unsigned type in conditional expression In file included from /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess .h:571, from include/linux/poll.h:14, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv-linu x.h:84, from /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:13 : /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess_32.h: In function ‘ copy_from_user’: /usr/src/linux-2.6.36-rc4/arch/x86/include/asm/uaccess_32.h:209: warning: co mparison between signed and unsigned integer expressions /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c: At top level: /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:426: error: unknown fiel d ‘ioctl’ specified in initializer /tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.c:426: warning: initializa tion from incompatible pointer type make[4]: *** [/tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel/nv.o] Error 1 make[3]: *** [_module_/tmp/selfgz2500/NVIDIA-Linux-x86-256.53/kernel] Error 2 make[2]: *** [sub-make] Error 2 NVIDIA: left KBUILD. nvidia.ko failed to build! make[1]: *** [module] Error 1 make: *** [module] Error 2 - Error. ERROR: Unable to build the NVIDIA kernel module. == Which I guess means I have to wait for Nvidia to fix a signed vs unsigned change in the kernel source. Can folks suggest if it would be worth while reporting this to Nvidia? Curt- Hi, I build my kernels with kernel-package, currently a 2.6.35.4-vanilla64 and have no problem. I build the headers at the same time because some installers will look for it even if the full sources are available (NVidia .run was one of those in my late experience). I now use nvidia (now dkms-ready) from debian Sid and have no problem, VirtualBox from Oracle/Sun repo is doing fine too here. I always check that the links build and source in /lib/modules/$(uname -r) are properly set up. Hope it helps. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c97b945.3040...@googlemail.com
Re: Mainline kernel source curiosity
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 20 September 2010, Arthur Machlas was heard to say: And install the debs. Alternatively, build both just to be safe fakeroot make-kpkg --append-to-version -curt1.0 kernel_headers kernel_image Very interesting. Any idea why building the headers was not needed on previous versions? - -- Those who torment us for our own good will torment us without end, for they do so with the approval of their consciences. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBTJe2Pi9Y35yItIgBAQLl9Af/WL3eUmCyaW+aValViGhBTEk563wiVs7G VWrO+2290PRMESZmuwV0MICtqlUzW7OgIEPvROPTjFohyyCUVm3jOZFxUZVR3nh4 SF1mNDzhysPjXEp+RxSsiWEpobFhdINzEtz5Oezqg9jRl6Po/CuBjTgagrARRRVO KdJSFxJCIwJncA+w0xhTb/kQa6c0KO7/BTq06/Sm79LggvDXoR/LG0B29+Mcz1Ao XqP53VrXRQkujN5XeyoP7PFIcuaRiFqoOpe45zcnEVP05r+SagcGaj+K/gprP9C5 fRE0ZI5bn0L6bPaZUuKzrLUP7HOOr7DPOu8bP9BXb+zpf22pGiLFew== =W3tb -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201009201530.06573.howl...@priss.com
Trouble to build module from nvidia-kernel-source
Hey, I am just wondering if the problem is me or the package. Kernel Package: Package: linux-image-2.6.30-2-amd64 State: installed Automatically installed: no Version: 2.6.30-8 [...] nvidia-kernel-source: [...] Version: 180.44-2 [...] Okay, here my steps: Installing the kernel+headers and nvidia source. # m-a build -k /usr/src/linux-headers-2.6.30-2-amd64/ nvidia-kernel-source This error shows up: [...] /usr/src/modules/nvidia-kernel/nv.c:596: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:597: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:598: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:618: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:632: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:643: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:653: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:663: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:674: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:681: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c: In function ‘nvos_proc_add_warning_file’: /usr/src/modules/nvidia-kernel/nv.c:708: error: ‘struct proc_dir_entry’ has no member named ‘owner’ [...] This method is describde on http://wiki.debian.org/NvidiaGraphicsDrivers and in the documents of the nvidia-kernel-source package. This method worked with linux-image-2.6.29-2-amd64 well. Can anyone confirm this problem? Bye, Thomas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Trouble to build module from nvidia-kernel-source
On Sat, Oct 17, 2009 at 12:56 PM, Thomas Jackowski tho...@jackowski.de wrote: Hey, I am just wondering if the problem is me or the package. Kernel Package: Package: linux-image-2.6.30-2-amd64 State: installed Automatically installed: no Version: 2.6.30-8 [...] nvidia-kernel-source: [...] Version: 180.44-2 [...] Okay, here my steps: Installing the kernel+headers and nvidia source. # m-a build -k /usr/src/linux-headers-2.6.30-2-amd64/ nvidia-kernel-source This error shows up: [...] /usr/src/modules/nvidia-kernel/nv.c:596: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:597: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:598: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:618: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:632: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:643: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:653: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:663: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:674: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:681: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c: In function ‘nvos_proc_add_warning_file’: /usr/src/modules/nvidia-kernel/nv.c:708: error: ‘struct proc_dir_entry’ has no member named ‘owner’ [...] This method is describde on http://wiki.debian.org/NvidiaGraphicsDrivers and in the documents of the nvidia-kernel-source package. This method worked with linux-image-2.6.29-2-amd64 well. Can anyone confirm this problem? Yes. I solved it using package from unstable instead of testing. Cheers -- Mathieu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Trouble to build module from nvidia-kernel-source
Hi, thanks for the advice. That helped. Bye Mathieu Malaterre wrote: On Sat, Oct 17, 2009 at 12:56 PM, Thomas Jackowski tho...@jackowski.de wrote: Hey, I am just wondering if the problem is me or the package. Kernel Package: Package: linux-image-2.6.30-2-amd64 State: installed Automatically installed: no Version: 2.6.30-8 [...] nvidia-kernel-source: [...] Version: 180.44-2 [...] Okay, here my steps: Installing the kernel+headers and nvidia source. # m-a build -k /usr/src/linux-headers-2.6.30-2-amd64/ nvidia-kernel-source This error shows up: [...] /usr/src/modules/nvidia-kernel/nv.c:596: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:597: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:598: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:618: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:632: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:643: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:653: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:663: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:674: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c:681: error: ‘struct proc_dir_entry’ has no member named ‘owner’ /usr/src/modules/nvidia-kernel/nv.c: In function ‘nvos_proc_add_warning_file’: /usr/src/modules/nvidia-kernel/nv.c:708: error: ‘struct proc_dir_entry’ has no member named ‘owner’ [...] This method is describde on http://wiki.debian.org/NvidiaGraphicsDrivers and in the documents of the nvidia-kernel-source package. This method worked with linux-image-2.6.29-2-amd64 well. Can anyone confirm this problem? Yes. I solved it using package from unstable instead of testing. Cheers -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Howto exactly reproduce kernel source tree compatible with binary kernel deb
as I meanwhile could figure out, compiling linux-source-xxx failed because of a mismatch in the gcc versions (gcc 4.3 is installed as the default C compiler, but the binary kernel packages have been compiled using gcc 4.1). I still would like to know, what is the recommended way to use the kernel source ... Regards, Peter For a long time, I always used traditional hand-made kernels, so whenever I needed it (compiling modules from external sources, changing something in the kernel, ...), I naturally had the source tree and configuration matching the currently running kernel lying under /usr/src/linux. Recently, I switched to Debian and also decided to try using the distribution kernel wherever possible. This still looks like a good idea to me, but it quickly turned out, that nevertheless, I need for many purposes the kernel sources. I searched the web (unfortunately, it seems like there were quite some changes in this area, so must recommendations I found were obviously outdated; btw., I am using lenny) and tried several different ways, but could not really find something that works reliable. One plausible-looking attempt for example was, that I installed the package linux-source-2.6.26, unpacked it and copied the configuration from the installed binary kernel package. Unfortunately, the modules compiled from this tree can't be loaded (I couldn't really understand, why; as far as I could tell, everything matched the running kernel ...). I also experimented with kernel-package (with similar results). For the most common case of compiling an external module, I found that the package linux-headers-2.6.26-2-arch, symlinked to /usr/src/linux will do what I need. I am still looking for a way to get the complete kernel source/.config that corresponds to the binary kernel packages, preferably in a way, that it will get updated with every kernel updated and _exactly_ matching the binary kernel, so whatever I compile in this tree can be combined with the binary package. Is there any way to accomplish that? (first of all, open source is about source code ...) Any suggestions are appreciated Regards, Peter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Howto exactly reproduce kernel source tree compatible with binary kernel deb
Hi, For a long time, I always used traditional hand-made kernels, so whenever I needed it (compiling modules from external sources, changing something in the kernel, ...), I naturally had the source tree and configuration matching the currently running kernel lying under /usr/src/linux. Recently, I switched to Debian and also decided to try using the distribution kernel wherever possible. This still looks like a good idea to me, but it quickly turned out, that nevertheless, I need for many purposes the kernel sources. I searched the web (unfortunately, it seems like there were quite some changes in this area, so must recommendations I found were obviously outdated; btw., I am using lenny) and tried several different ways, but could not really find something that works reliable. One plausible-looking attempt for example was, that I installed the package linux-source-2.6.26, unpacked it and copied the configuration from the installed binary kernel package. Unfortunately, the modules compiled from this tree can't be loaded (I couldn't really understand, why; as far as I could tell, everything matched the running kernel ...). I also experimented with kernel-package (with similar results). For the most common case of compiling an external module, I found that the package linux-headers-2.6.26-2-arch, symlinked to /usr/src/linux will do what I need. I am still looking for a way to get the complete kernel source/.config that corresponds to the binary kernel packages, preferably in a way, that it will get updated with every kernel updated and _exactly_ matching the binary kernel, so whatever I compile in this tree can be combined with the binary package. Is there any way to accomplish that? (first of all, open source is about source code ...) Any suggestions are appreciated Regards, Peter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to install kernel source 2.6.8
On Wed, Feb 25, 2009 at 12:51:19AM +, Tzafrir Cohen wrote: On Tue, Feb 24, 2009 at 03:31:38PM -0800, Mike McClain wrote: I've a mostly etch system and wanted to try the 2.6 kernel. snip 2.4.27 and 2.6.8 are from Sarge. 2.2.25 is even older. Thanks for the tip, I hadn't realized 'apt-get update' doesn't update /var/lib/dpkg/available, just pulls down the Packages files. Another thing I find peculiar is that 'apt-get install linux-source-2.6.18 linux-headers-2.6.18-6-486' also pulled down gcc-4.1 and associated packages but left gcc-3.3 as the default so that the build failed when I tried to create a new kernel. What's the reasoning behind that? Thanks, Mike -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
how to install kernel source 2.6.8
I've a mostly etch system and wanted to try the 2.6 kernel. mike@/deb40a:~ uname -a Linux playground 2.4.27 #1 Mon Dec 24 13:55:08 PST 2007 i586 GNU/Linux The only un-commented lines in /etc/apt/sources.list are: deb http://ftp.us.debian.org/debian/ etch main contrib non-free deb-src http://ftp.us.debian.org/debian/ etch main contrib non-free deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib deb http://www.backports.org/debian etch-backports main contrib non-free root@/deb40a:~ apt-get update root@/deb40a:~ grep Package: kernel-source /var/lib/dpkg/available Package: kernel-source-2.4.27 Package: kernel-source-2.2.25 Package: kernel-source-2.6.8 root@/deb40a:~ apt-get install kernel-source-2.6.8 Reading Package Lists... Done Building Dependency Tree... Done Package kernel-source-2.6.8 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source-2.6.8 has no installation candidate -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to install kernel source 2.6.8
On Tue, Feb 24, 2009 at 03:31:38PM -0800, Mike McClain wrote: I've a mostly etch system and wanted to try the 2.6 kernel. mike@/deb40a:~ uname -a Linux playground 2.4.27 #1 Mon Dec 24 13:55:08 PST 2007 i586 GNU/Linux The only un-commented lines in /etc/apt/sources.list are: deb http://ftp.us.debian.org/debian/ etch main contrib non-free deb-src http://ftp.us.debian.org/debian/ etch main contrib non-free deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib deb http://www.backports.org/debian etch-backports main contrib non-free root@/deb40a:~ apt-get update root@/deb40a:~ grep Package: kernel-source /var/lib/dpkg/available Package: kernel-source-2.4.27 Package: kernel-source-2.2.25 Package: kernel-source-2.6.8 2.4.27 and 2.6.8 are from Sarge. 2.2.25 is even older. -- Tzafrir Cohen | tzaf...@jabber.org | VIM is http://tzafrir.org.il || a Mutt's tzaf...@cohens.org.il || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: how to install kernel source 2.6.8
On Tue, 24 Feb 2009 15:31:38 -0800 Mike McClain mike.j...@nethere.com wrote: I've a mostly etch system and wanted to try the 2.6 kernel. ... root@/deb40a:~ apt-get update root@/deb40a:~ grep Package: kernel-source /var/lib/dpkg/available Package: kernel-source-2.4.27 Package: kernel-source-2.2.25 Package: kernel-source-2.6.8 root@/deb40a:~ apt-get install kernel-source-2.6.8 Reading Package Lists... Done Building Dependency Tree... Done Package kernel-source-2.6.8 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source-2.6.8 has no installation candidate Try grepping 'linux-source'; the nomenclature has changed. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Pasting old config file of 18th kernel to new kernel source of 26
i pasted the config file of 18th kernel to kernel source of 26 I ran make oldconfig , eventhough it is querying for the new options present in that source for that i didnt know what to do.. i simply gave enter to that options. Simply pressing enter will enable the options if not shall I continue as it is .. -- bossganesh BOSSTeam CDAC
Re: Pasting old config file of 18th kernel to new kernel source of 26
2008/11/27 boss ganesh [EMAIL PROTECTED]: i pasted the config file of 18th kernel to kernel source of 26 I ran make oldconfig , eventhough it is querying for the new options present in that source for that i didnt know what to do.. i simply gave enter to that options. Simply pressing enter will enable the options if not shall I continue as it is .. The default options (just pressing enter) should be fine unless you really want to use one of those new options. Pressing ? will give you more information on the option to base your decision. Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pasting the old config file to new kernel source for compilation..
2008/11/24 boss ganesh [EMAIL PROTECTED]: I have pasted the config file of 2.6.18 (already compiled working kernel config file) to kernel source of version 2.6.26 , after that also it is asking queries without compiling it when i ran the command make .. why is it happening like that? Did you run make oldconfig? This checks your .config file and asks you questions to new options available in the new kernel source. Be sure to read the file called README, it's in bold for a reason. There is also make help Adrian -- 24x7x365 != 24x7x52 Stupid or bad maths? erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pasting the old config file to new kernel source for compilation..
On 2008-11-24 09:13 +0100, Adrian Levi wrote: 2008/11/24 boss ganesh [EMAIL PROTECTED]: I have pasted the config file of 2.6.18 (already compiled working kernel config file) to kernel source of version 2.6.26 , after that also it is asking queries without compiling it when i ran the command make .. why is it happening like that? Did you run make oldconfig? I don't think that's appropriate when leaping across eight kernel versions, unless you are (or want to become) mad. Better run make menuconfig and hope for the best. This checks your .config file and asks you questions to new options available in the new kernel source. Yes, many hundreds of them, literally. Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pasting the old config file to new kernel source for compilation..
On Mon, Nov 24, 2008 at 11:59:26AM +0530, boss ganesh wrote: I have pasted the config file of 2.6.18 (already compiled working kernel config file) to kernel source of version 2.6.26 , after that also it is asking queries without compiling it when i ran the command make .. why is it happening like that? Each kernel version has a different configuration file because the available options change. It's like saying: I've got a new lock for my door, why doesn't my old key fit anymore? -- http://en.wikipedia.org/wiki/Posting_style -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Pasting the old config file to new kernel source for compilation..
boss ganesh wrote: I have pasted the config file of 2.6.18 (already compiled working kernel config file) to kernel source of version 2.6.26 , after that also it is asking queries without compiling it when i ran the command make .. why is it happening like that? The command you want is make oldconfig. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Pasting the old config file to new kernel source for compilation..
I have pasted the config file of 2.6.18 (already compiled working kernel config file) to kernel source of version 2.6.26 , after that also it is asking queries without compiling it when i ran the command make .. why is it happening like that? -- bossganesh BOSSTeam CDAC
Re: How to get debian kernel source ?
On Mon, 2008-10-06 at 22:06 +0900, J.H.Kim wrote: Is the debian kernel source and the kernel source of same version in kernel archive(www.kernel.org) same? I believe there may be some patches involved. If I want to get debian kernel source code, which source code cd-rom is needed out of 21CDs? Don't download all the CDs unless you're dealing with a machine that has no network connection. Let apt do the heavy lifting. cd /usr/src apt-get source kernel-image-2.6.blah -- Paul Johnson [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
How to get debian kernel source ?
Hi, everyone Is the debian kernel source and the kernel source of same version in kernel archive(www.kernel.org) same? If I want to get debian kernel source code, which source code cd-rom is needed out of 21CDs? Thanks in advance.
Re: How to get debian kernel source ?
J.H.Kim wrote: Hi, everyone Is the debian kernel source and the kernel source of same version in kernel archive(www.kernel.org) same? No, Debian applies some set of patches. If I want to get debian kernel source code, which source code cd-rom is needed out of 21CDs? You can obtain source code without getting a CD, just install 'linux-source' package on your Debian system. -- Eugene V. Lyubimkin aka JackYF signature.asc Description: OpenPGP digital signature
RE: How to get debian kernel source ?
If you go over to http://www.debian.org/distrib/packages you should be able to search for linux-source which will show you the current version of kernel source available. I think this version will vary depending upon the release you are searching under. You might also want to look at the Wiki site at: http://wiki.debian.org/ under Debian Development. -- Lalit Dhiri Linux the root to no GPFs Date: Mon, 6 Oct 2008 22:06:53 +0900 From: [EMAIL PROTECTED] To: debian-user@lists.debian.org Subject: How to get debian kernel source ? Hi, everyone Is the debian kernel source and the kernel source of same version in kernel archive(www.kernel.org) same? If I want to get debian kernel source code, which source code cd-rom is needed out of 21CDs? Thanks in advance. _ Make a mini you and download it into Windows Live Messenger http://clk.atdmt.com/UKM/go/111354029/direct/01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Build non-pae kernel from debian kernel source
Hi all, I'm facing a problem to build a non-pae kernel from debian kernel source. Here's what i have done: #apt-get source linux-2.6 #cd linux-2.6-2.6.18.dfsg.1 #./debian/rules debian/build debian/stamps #make -f debian/rules.gen setup-i386-xen-686 #cd build/build-i386-xen-686 #make menuconfig Here, i have suppressed HIGHMEM support to make a non-pae kenrel then, finish with make-kpkg: #make-kpkg --initrd kernel_image This process finish with an error: dpkg-gencontrol : erreur : le paquet linux-xen0-2.6.18-6-xen-686 n'est pas le fichier de contrômake[1]: *** [debian/linux-xen0-2.6.18-6-xen-686] Erreur 255 make[1]: quittant le répertoire « /usr/src/linux-2.6-2.6.18.dfsg.1/debian/build/build-i386-xen-686 » make: *** [binary/linux-xen0-2.6.18-6-xen-686] Erreur 2 In English it should be: dpkg-gencontrol : error : packet linux-xen0-2.6.18-6-xen-686 is not a control file make[1]: *** [debian/linux-xen0-2.6.18-6-xen-686] Error 255 make[1]: leaving folder « /usr/src/linux-2.6-2.6.18.dfsg.1/debian/build/build-i386-xen-686 » make: *** [binary/linux-xen0-2.6.18-6-xen-686] Error 2 Is there a better way to build a non-pae kernel ? Any idea on this problem ? Thanks for your help :) Wilfried. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-source non dispo
bonsoir jusqu'a présent j'utilisais virtualbox sans probleme a present j'ai un message d'erreur selon lequel il ne trouve pas le kernel-source (aucun paquet ne correspond au kernel-source) et donc pour virtualbox vboxdrv setup echoue mon noyau est 2.6.18.6.686 merci -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel-source non dispo
deny a écrit : bonsoir jusqu'a présent j'utilisais virtualbox sans probleme a present j'ai un message d'erreur selon lequel il ne trouve pas le kernel-source (aucun paquet ne correspond au kernel-source) et donc pour virtualbox vboxdrv setup echoue mon noyau est 2.6.18.6.686 merci j'ai installe le paquetage kernel-headers qui correspond a mon noyau et ca roule désolé pour le bruit -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.org/DebFrFrenchLists Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel source packages..
Many thanks to David, NN_il_Confusion and martin for their suggestions, in particular.. On Sun, Apr 13, 2008 at 08:24:09PM -0700, David Witbrodt wrote: The book is great, but already a bit out of date. Krafft has a website (not recently updated) which includes error corrections and new information here: http://debiansystem.info . . Excellent! Very glad to know about that we site. Thanks! (and to Martin for setting it up) On Mon, Apr 14, 2008 at 07:05:33AM +0200, NN_il_Confusionario wrote: On Mon, Apr 14, 2008 at 12:52:41AM +, Digby Tarvin wrote: Can anyone shed any light on the differences between the various kernel source packages in the repository, kernel-source-* are for sarge and below linux-source-* are for etch and beyond Then do apt-cache show $PACKAGE and read the Description: (for example, difference between linux-source-2.6.18 and linux-tree-2.6.18) . . I'm still a bit of a newbie with the Debian package management stuff. Obviously a bit more reading to do, but it is nice to know there are ways to get the answers to these things... thanks for the clues as to where to look.. On Mon, Apr 14, 2008 at 08:19:41AM +0200, martin f krafft wrote: Try linux-source-*. The kernel packaging has changed substantially since my book was published. I am working on a new edition. Unfortunately, I cannot foresee a release date yet. Must be quite a job keeping up with a moving target like the Debian system... I hate the thought of throwing away my well thumbed first edition, but I suppose it is inevitable. Maybe you should think of putting out a yearly addendum between editions. I'd subscribe ;) Are there, incidentally, any journals out there that are particulalry good for debian users? Can anyone explain what the reasonaing is behind this organization? Did you see kernel-handbook.alioth.debian.org? Thanks, stumbled across a link to this on the debian.org site after I sent the original message. Still reading... Regards, DigbyT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel source packages..
also sprach Digby Tarvin [EMAIL PROTECTED] [2008.04.14.0252 +0200]: The example in my Martin Kraft book refers to: apt-get install kernel-source-2.6.8 but I can't find a 'kernel-source-anything'.. Try linux-source-*. The kernel packaging has changed substantially since my book was published. I am working on a new edition. Unfortunately, I cannot foresee a release date yet. Can anyone explain what the reasonaing is behind this organization? Did you see kernel-handbook.alioth.debian.org? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems (a)bort, (r)etry, (p)retend this never happened digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Kernel source packages..
Can anyone shed any light on the differences between the various kernel source packages in the repository, and which is the best choice for just being able to reproduce the running kernel? The example in my Martin Kraft book refers to: apt-get install kernel-source-2.6.8 but I can't find a 'kernel-source-anything'.. The docs on debian.org suggest apt-get install linux-source-2.6 but looking in the repository I also see linux-source as well as linux-tree-2.6.18-n where n is a number between 1 and 8, and there are also linux-tree-2.6.18.dfag.1-n where n is 9-19, some with 'etch' followed by a digit appaended. The above are all 'v' packages. There is also linux-source-2.6.18 and linux-tree-2.6.18 which are actual packages. Can anyone explain what the reasonaing is behind this organization? Thanks, DigbyT -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel source packages..
Can anyone shed any light on the differences between the various kernel source packages in the repository, and which is the best choice for just being able to reproduce the running kernel? The example in my Martin Kraft book refers to: apt-get install kernel-source-2.6.8 but I can't find a 'kernel-source-anything'.. The book is great, but already a bit out of date. Krafft has a website (not recently updated) which includes error corrections and new information here: http://debiansystem.info If you read the section of the book discussing the naming of kernel-related packages -- including images, headers-only packages, and source packages -- then all of the information is correct... it's just that Debian policy renamed 'kernel-*' to 'linux-*' many moons ago (back at kernel 2.6.12, I believe). See this: http://debiansystem.info/readers/changes/260-package-names HTH, Dave Witbrodt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Kernel source packages..
On Mon, Apr 14, 2008 at 12:52:41AM +, Digby Tarvin wrote: Can anyone shed any light on the differences between the various kernel source packages in the repository, kernel-source-* are for sarge and below linux-source-* are for etch and beyond Then do apt-cache show $PACKAGE and read the Description: (for example, difference between linux-source-2.6.18 and linux-tree-2.6.18) and which is the best choice for just being able to reproduce the running kernel? apt-cache show linux-image-$(uname -r)|grep ^Source: Possibly it will return that the source package for your running kernel is linux-2.6 then (if you use deb-src lines in sources.list) grep -A1 ^Package: linux-2.6 /var/lib/apt/lists/*_Sources|less will show all binary packages produced by the linux-2.6 source package. Chose the linux-source-* or linux-tree-* or whatever you prefer (possibly linux-source-2.6.18 or linux-source-2.6.24). If you want to recompile, also apt-cache show kernel-package might be useful -- Chi usa software non libero avvelena anche te. Digli di smettere. Informatica=arsenico: minime dosi in rari casi patologici, altrimenti letale. Informatica=bomba: intelligente solo per gli stupidi che ci credono. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Trouble trying to find Kernel source...
On Mon, Feb 25, 2008 at 11:56:16PM -0800, tony mollica wrote: I hate to stick my neck out here only because my solution to this problem was just to keep banging away at the keyboard until all the errors went away, and I don't keep notes. There has also been quite a bit on the list about this in the last week or so. Seemed complex. BUT, here is what I remember. The source packages for Debian are linux-source-kernel version and linux-headers-kernel version, the kernel version from 'uname -r'. I took the kernel config from /boot and copied it to the source dir as '.config', ran 'make oldconfig' to use this configuration then ran the kernel compile for a few minutes to make the necessary files for the Nvidia driver builder, then run the Nvidia driver program with the --kernel-source-path=KERNEL-SOURCE-PATH command line option so it finds the kernel source. Pending any minor missing items that were show stoppers but easy to find and install, it built and installed the driver with no problems. have a look at module assist, a simple command like m-i install nvidia will do all that you want dann frazier wrote: [Off-topic for debian-kernel, moving to debian-user] On Tue, Feb 26, 2008 at 12:26:56AM +1100, Frank Charles Gallacher wrote: Greetings, I am trying to install the driver for NVIDIA GeForce 6600 GT graphics video adapter on my PC, running Debian GNU/Linux 40rl i386: kernel version: Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1) gcc version: gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) When I run the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run) It tries to find kernel source from ftp://download.nvidia.com; and fails, then bombs out when it cannot find it installed locally... To build a kernel, I need kernel-source and kernel-devel packages installed; (something called linux-kernel-headers is already installed). When I try to install them, I get: Ni:/home/franx/Desktop# apt-get install kernel-source Reading package lists... Done Building dependency tree... Done Package kernel-source is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source has no installation candidate I've no experience w/ nvidia-installer myself, but you probably just need the header files. An easy way to install the headers for your running kernel is: # apt-get install module-assistant # m-a prepare There are also prebuilt nvidia drivers for this kernel in etch/non-free, but perhaps you need something newer. You might have luck finding someone w/ nvidia-installer experience on this list. my /etc/apt/sources.list looks like: # # deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb http://ftp.au.debian.org/debian/ etch main deb-src http://ftp.au.debian.org/debian/ etch main deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib Can somebody please help me with: 1. Is there a mirror somewhere that has these packages? 2. Have I missed something vitally important?? Thanking you. -- - tony tjm at threedogs.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Does not include installation. signature.asc Description: Digital signature
Re: Trouble trying to find Kernel source...
Thankyou Dan, after installing module assistant, nvidia-installer worked fine... On Mon, 2008-02-25 at 18:03 -0700, dann frazier wrote: [Off-topic for debian-kernel, moving to debian-user] On Tue, Feb 26, 2008 at 12:26:56AM +1100, Frank Charles Gallacher wrote: Greetings, I am trying to install the driver for NVIDIA GeForce 6600 GT graphics video adapter on my PC, running Debian GNU/Linux 40rl i386: kernel version: Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1) gcc version: gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) When I run the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run) It tries to find kernel source from ftp://download.nvidia.com; and fails, then bombs out when it cannot find it installed locally... To build a kernel, I need kernel-source and kernel-devel packages installed; (something called linux-kernel-headers is already installed). When I try to install them, I get: Ni:/home/franx/Desktop# apt-get install kernel-source Reading package lists... Done Building dependency tree... Done Package kernel-source is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source has no installation candidate I've no experience w/ nvidia-installer myself, but you probably just need the header files. An easy way to install the headers for your running kernel is: # apt-get install module-assistant # m-a prepare There are also prebuilt nvidia drivers for this kernel in etch/non-free, but perhaps you need something newer. You might have luck finding someone w/ nvidia-installer experience on this list. my /etc/apt/sources.list looks like: # # deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb http://ftp.au.debian.org/debian/ etch main deb-src http://ftp.au.debian.org/debian/ etch main deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib Can somebody please help me with: 1. Is there a mirror somewhere that has these packages? 2. Have I missed something vitally important?? Thanking you. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Trouble trying to find Kernel source...
[Off-topic for debian-kernel, moving to debian-user] On Tue, Feb 26, 2008 at 12:26:56AM +1100, Frank Charles Gallacher wrote: Greetings, I am trying to install the driver for NVIDIA GeForce 6600 GT graphics video adapter on my PC, running Debian GNU/Linux 40rl i386: kernel version: Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1) gcc version: gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) When I run the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run) It tries to find kernel source from ftp://download.nvidia.com; and fails, then bombs out when it cannot find it installed locally... To build a kernel, I need kernel-source and kernel-devel packages installed; (something called linux-kernel-headers is already installed). When I try to install them, I get: Ni:/home/franx/Desktop# apt-get install kernel-source Reading package lists... Done Building dependency tree... Done Package kernel-source is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source has no installation candidate I've no experience w/ nvidia-installer myself, but you probably just need the header files. An easy way to install the headers for your running kernel is: # apt-get install module-assistant # m-a prepare There are also prebuilt nvidia drivers for this kernel in etch/non-free, but perhaps you need something newer. You might have luck finding someone w/ nvidia-installer experience on this list. my /etc/apt/sources.list looks like: # # deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb http://ftp.au.debian.org/debian/ etch main deb-src http://ftp.au.debian.org/debian/ etch main deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib Can somebody please help me with: 1. Is there a mirror somewhere that has these packages? 2. Have I missed something vitally important?? Thanking you. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Trouble trying to find Kernel source...
I hate to stick my neck out here only because my solution to this problem was just to keep banging away at the keyboard until all the errors went away, and I don't keep notes. There has also been quite a bit on the list about this in the last week or so. Seemed complex. BUT, here is what I remember. The source packages for Debian are linux-source-kernel version and linux-headers-kernel version, the kernel version from 'uname -r'. I took the kernel config from /boot and copied it to the source dir as '.config', ran 'make oldconfig' to use this configuration then ran the kernel compile for a few minutes to make the necessary files for the Nvidia driver builder, then run the Nvidia driver program with the --kernel-source-path=KERNEL-SOURCE-PATH command line option so it finds the kernel source. Pending any minor missing items that were show stoppers but easy to find and install, it built and installed the driver with no problems. dann frazier wrote: [Off-topic for debian-kernel, moving to debian-user] On Tue, Feb 26, 2008 at 12:26:56AM +1100, Frank Charles Gallacher wrote: Greetings, I am trying to install the driver for NVIDIA GeForce 6600 GT graphics video adapter on my PC, running Debian GNU/Linux 40rl i386: kernel version: Linux version 2.6.18-6-686 (Debian 2.6.18.dfsg.1-18etch1) gcc version: gcc (GCC) 4.1.2 20061115 (prerelease) (Debian 4.1.1-21) When I run the nvidia-installer (sh NVIDIA-Linux-x86-169.09-pkg1.run) It tries to find kernel source from ftp://download.nvidia.com; and fails, then bombs out when it cannot find it installed locally... To build a kernel, I need kernel-source and kernel-devel packages installed; (something called linux-kernel-headers is already installed). When I try to install them, I get: Ni:/home/franx/Desktop# apt-get install kernel-source Reading package lists... Done Building dependency tree... Done Package kernel-source is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package kernel-source has no installation candidate I've no experience w/ nvidia-installer myself, but you probably just need the header files. An easy way to install the headers for your running kernel is: # apt-get install module-assistant # m-a prepare There are also prebuilt nvidia drivers for this kernel in etch/non-free, but perhaps you need something newer. You might have luck finding someone w/ nvidia-installer experience on this list. my /etc/apt/sources.list looks like: # # deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb cdrom:[Debian GNU/Linux 4.0 r1 _Etch_ - Official i386 NETINST Binary-1 20070820-20:21]/ etch contrib main deb http://ftp.au.debian.org/debian/ etch main deb-src http://ftp.au.debian.org/debian/ etch main deb http://security.debian.org/ etch/updates main contrib deb-src http://security.debian.org/ etch/updates main contrib Can somebody please help me with: 1. Is there a mirror somewhere that has these packages? 2. Have I missed something vitally important?? Thanking you. -- - tony tjm at threedogs.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel-source package in Etch?
On Mon, Dec 31, 2007 at 10:14:38PM +0100, Rodolfo Medina wrote: In Sarge, in order to configure Debian for my modem, I started with: # apt-get install kernel-source-2.4.27 . Now, in Etch, what should the package be in place of that? I couldn't find it! I tried with ...2.6, ...2.6.18,... but none was the right one. Douglas A. Tutty [EMAIL PROTECTED] writes: In Etch, the Linux kernels are called linux-. However, are you sure in Etch that you need a new kernel for your modem? No, you are right, compiling the kernel was not necessary. See report at: http://forums.debian.net/viewtopic.php?t=22706 Bye Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel-source package in Etch?
Hi to all Debian users. In Sarge, in order to configure Debian for my modem, I started with: # apt-get install kernel-source-2.4.27 . Now, in Etch, what should the package be in place of that? I couldn't find it! I tried with ...2.6, ...2.6.18,... but none was the right one. Thanks for any help Rodolfo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel-source package in Etch?
On 22:14 Mon 31 Dec , Rodolfo Medina wrote: Hi to all Debian users. In Sarge, in order to configure Debian for my modem, I started with: # apt-get install kernel-source-2.4.27 . Now, in Etch, what should the package be in place of that? I couldn't find it! I tried with ...2.6, ...2.6.18,... but none was the right one. they now call the kernel package linux-image-2.6.18-4-686 or something like that and the headers package is linux-headers-2.6.18-4-686 the source package is linux-source-2.6.18 do uname -a to find out what kernel you have then do apt-cache search linux-headers or apt-cache search linux-source mitchell Thanks for any help Rodolfo -- 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]
Re: kernel-source package in Etch?
On Mon, Dec 31, 2007 at 10:14:38PM +0100, Rodolfo Medina wrote: Hi to all Debian users. In Sarge, in order to configure Debian for my modem, I started with: # apt-get install kernel-source-2.4.27 . Now, in Etch, what should the package be in place of that? I couldn't find it! I tried with ...2.6, ...2.6.18,... but none was the right one. In Etch, the Linux kernels are called linux-. However, are you sure in Etch that you need a new kernel for your modem? Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
question about kernel source packages
I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? Everything should be made as simple as possible, but not simpler. Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about kernel source packages
On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote: I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? It's already patched. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about kernel source packages
Quoting Mumia W.. [EMAIL PROTECTED]: On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote: I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? It's already patched. Doublechecking, you are absolutely positive? Everything should be made as simple as possible, but not simpler. Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about kernel source packages
On Tue, 28 Aug 2007 15:15:08 -0400 [EMAIL PROTECTED] wrote: Quoting Mumia W.. [EMAIL PROTECTED]: On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote: I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? It's already patched. Doublechecking, you are absolutely positive? I believe he's correct. From the description of linux-patch-debian-2.6.22: Description: Debian patches to version 2.6.22 of the Linux kernel This package includes the patches used to produce the prepackaged linux-source-2.6.22 package, as well as architecture-specific patches. Note that these patches do NOT apply against a pristine Linux 2.6.22 kernel but only against the kernel tarball linux-2.6_2.6.22.orig.tar.gz from the Debian archive. So the prepackaged kernel source has already been patched. The patch has been applied against the mentioned Debian tarball. All this is AFAICT. Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about kernel source packages
On 08/28/2007 02:15 PM, [EMAIL PROTECTED] wrote: Quoting Mumia W.. [EMAIL PROTECTED]: On 08/28/2007 12:02 PM, [EMAIL PROTECTED] wrote: I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? It's already patched. Doublechecking, you are absolutely positive? Read the files README.Debian and Debian.src.changelog in the kernel source directory. If those files exist, and if their contents suggest that the kernel has been patched (they do here), then the kernel source has already been patched. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
question about kernel source package
I notice there is a source package for the kernel and a package of debian patches. Has the kernel source already been patched or would one need to patch it with all of the included debian patches when building a custom kernel? Everything should be made as simple as possible, but not simpler. Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
On Fri, 17 Aug 2007 06:11:08 +0200 Marcus Blumhagen [EMAIL PROTECTED] wrote: Hi, First of all, please CC me when replying, since I am not subscribed to this list. [...] And as I rarely decompress files, I have forgotten the command to decompress tar/bz2 files . [...] I just wanted to add my ¢2. You may want to evaluate the package named unp and you will never (almost) need to remember any command for decompressing archive files. Just type: unp archive and it automagically extracts it, no matter what kind of archive, provided you have the appropriate archiver program installed. Great little program. Thanks. Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how
Re: Confused about kernel source location
Hi, First of all, please CC me when replying, since I am not subscribed to this list. [...] And as I rarely decompress files, I have forgotten the command to decompress tar/bz2 files . [...] I just wanted to add my ¢2. You may want to evaluate the package named unp and you will never (almost) need to remember any command for decompressing archive files. Just type: unp archive and it automagically extracts it, no matter what kind of archive, provided you have the appropriate archiver program installed. Regards -- Marcus Blumhagen Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction. -- Albert Einstein signature.asc Description: Digital signature
Re: Confused about kernel source location
El Mar, 14 de Agosto de 2007, 8:29 pm, Frank McCormick escribió: On Mon, 13 Aug 2007 14:28:41 -0400 Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: Frank McCormick wrote: I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? Anybody? Where do people dump their kernel source anyway??? Well, the first person that says that the kernel sources must NOT be in /usr/src was Linus, but I think that this only affects things at 'build' time (like build the base system for a distribution) so it's the same put in /kernelsource or /usr/src since the build symlink in /lib/modules/$(uname -r) points to the 'original' source code where the kernel was compiled. My kernels sources are in /kernelsource and I don't have any problems. Saludos. -olr
Re: Confused about kernel source location
On Wed, 15 Aug 2007 10:36:52 +0900 Takehiko Abe [EMAIL PROTECTED] wrote: Frank McCormick wrote: Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? I don't know why. but the kernel package readme (/usr/share/doc/kernel-package/README.gz) also suggests not to build the kernel there. Also the Filesystem Hierarchy Standard (FHS) says that source code may be placed under /usr/src only for reference purposes and should not be build within. Again I don't understand why exactly. [...] The idea is that /usr should be kept read-only. Some administrators even mount /usr read-only on its own partition. -- Liam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
On Tuesday 14 August 2007 21:27, Wayne Topa wrote: Anybody? Where do people dump their kernel source anyway??? I have always put my kernels in /usr/src. First time I've _ever_ heard of DO NOT USE THE /usr/src area. Just what readme did you see _that_ in? From linux-source-2.6.18/README: INSTALLING the kernel: - If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it: * * * * Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be. ===
Re: Confused about kernel source location
Ed Jabbour([EMAIL PROTECTED]) is reported to have said: On Tuesday 14 August 2007 21:27, Wayne Topa wrote: Anybody? Where do people dump their kernel source anyway??? I have always put my kernels in /usr/src. First time I've _ever_ heard of DO NOT USE THE /usr/src area. Just what readme did you see _that_ in? From linux-source-2.6.18/README: INSTALLING the kernel: - If you install the full sources, put the kernel tarball in a directory where you have permissions (eg. your home directory) and unpack it: * * * * Do NOT use the /usr/src/linux area! This area has a (usually incomplete) set of kernel headers that are used by the library header files. They should match the library, and not get messed up by whatever the kernel-du-jour happens to be. === Thanks Ed I'm running 2.6.21-1-amd64 so had to go to another box to check. Yes I see that in the 2.6.18 source. For what it's worth, there is no such README in the 2.6.21-1-amd64 source dir, which is installed in /usr/src, by aptitude. Interesting. Wayne -- Why do we want intelligent terminals when there are so many stupid users? ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
On Mon, 13 Aug 2007 14:28:41 -0400 Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: Frank McCormick wrote: I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? Anybody? Where do people dump their kernel source anyway??? Cheers Frank -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
Frank McCormick([EMAIL PROTECTED]) is reported to have said: On Mon, 13 Aug 2007 14:28:41 -0400 Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: Frank McCormick wrote: I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? Anybody? Where do people dump their kernel source anyway??? I have always put my kernels in /usr/src. First time I've _ever_ heard of DO NOT USE THE /usr/src area. Just what readme did you see _that_ in? Wayne -- Warning, keyboard not found. Press Enter to continue. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
On Tue, 14 Aug 2007, Frank McCormick wrote: On Mon, 13 Aug 2007 14:28:41 -0400 Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: Frank McCormick wrote: I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? Anybody? Where do people dump their kernel source anyway??? Cheers Frank When I compile my own kernels, I usually put them in /usr/local/src/ , then make a symlink from linux-version to kernel. That way, when a new kernel comes out i just remove the symlink from the old to the new. I find it's easier to do it that way when I have to recompile modules, that way I always point the config to /usr/local/src/kernel . I leave /usr/src out, because thats where the debian kernel source files will go if I need to download them and I dont want things to get confused. -+- 8 out of 10 Owners who Expressed a Preference said Their Cats Preferred Techno. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
Frank McCormick wrote: Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? I don't know why. but the kernel package readme (/usr/share/doc/kernel-package/README.gz) also suggests not to build the kernel there. Also the Filesystem Hierarchy Standard (FHS) says that source code may be placed under /usr/src only for reference purposes and should not be build within. Again I don't understand why exactly. If you can use make-kpkg, I think following the instruction detailed in the kernel-package readme is an easy path. I never used that symlink (what is that?). Anybody? Where do people dump their kernel source anyway??? I use /usr/local/src/kernel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Confused about kernel source location
I have taken the first steps towards compiling an Nvidia module for my Quadro-pro card... I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? And as I rarely decompress files, I have forgotten the command to decompress tar/bz2 files . Thanks Cheers -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Confused about kernel source location
Frank McCormick wrote: I have taken the first steps towards compiling an Nvidia module for my Quadro-pro card... I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. And as I rarely decompress files, I have forgotten the command to decompress tar/bz2 files . That's why man exists :) `man tar', and even more simple!: `tar --help'... Anyway tar -jxf linux-2.6.x.x.tar.bz2 Regards, Jose Luis. -- ghostbar on debian linux 'sid' 2.6.22 x86_64-SMP - #382503 Weblog: http://ghostbar.ath.cx/ - http://linuxtachira.org http://debian.org.ve - irc.debian.org #debian-ve #debian-devel-es San Cristóbal, Venezuela. http://chaslug.org.ve Fingerprint = 3E7D 4267 AFD5 2407 2A37 20AC 38A0 AD5B CACA B118 signature.asc Description: OpenPGP digital signature
Re: Confused about kernel source location
On Mon, 13 Aug 2007 14:28:41 -0400 Jose Luis Rivas Contreras [EMAIL PROTECTED] wrote: Frank McCormick wrote: I have taken the first steps towards compiling an Nvidia module for my Quadro-pro card... I downloaded and installed the source for the current kernel, which aptitude dumped into /usr/src. Reading the readme, one of the first things it says is DO NOT USE THE /usr/src area because that is where the headers for libc I guess are stored. What is up here ? Well, I always store there all the sources related with my kernel, modules, etc... I haven't get any problem... BTW, remember doing the symlink to /usr/src/linux from your kernel-source. Well then why the warning from the Kernel developers? And what's this about symlinking? Symlinking what to what ? And as I rarely decompress files, I have forgotten the command to decompress tar/bz2 files . That's why man exists :) `man tar', and even more simple!: `tar --help'... Anyway tar -jxf linux-2.6.x.x.tar.bz2 Thanks for that. I should have RTFM ! Cheers -- Change the world one loan at a time - visit Kiva.org to find out how -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
nvidia-kernel-source and Xen
Hi, I am running Sid + Xen and I am used to patch the nvidia-kernel-source [1] in order to make it Xen friendly [2]. I was surprised to see, when I appliyed the patch that the source are already patched: I mean patch command tells me so. Is Xen compliance included or is it just a mistake I made? [1] http://packages.debian.org/unstable/x11/nvidia-kernel-source [2] http://www.debian-administration.org/articles/493 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: nvidia-kernel-source and Xen
Le Saturday 19 May 2007 11:49:55 Mihamina (R12y) Rakotomandimby, vous avez écrit : Hi, I am running Sid + Xen and I am used to patch the nvidia-kernel-source [1] in order to make it Xen friendly [2]. I was surprised to see, when I appliyed the patch that the source are already patched: I mean patch command tells me so. Is Xen compliance included or is it just a mistake I made? [1] http://packages.debian.org/unstable/x11/nvidia-kernel-source [2] http://www.debian-administration.org/articles/493 It's included in 9755 version. $ aptitude changelog nvidia-kernel-source nvidia-graphics-drivers (1.0.9755-1) unstable; urgency=low * new upstream uploaded to unstable (closes: #415041) * change description to refer only to xorg. (closes: #404599, #402223) * fix Description regarding supported cards. (closes: #416946) * Add Vcs header * Add Xen support (thanks to Marco Nenciarini) (closes: #367326) -- Randall Donald [EMAIL PROTECTED] Sun, 22 Apr 2007 20:26:57 -0700 I thought it was only in experimental, where have you got your version ? In fact, it's in SID now : [EMAIL PROTECTED]:~$ apt-show-versions -a nvidia-kernel-source nvidia-kernel-source1.0.9755-1 install ok installed nvidia-kernel-source1.0.9755-1 sid nvidia-kernel-source/sid uptodate 1.0.9755-1 pgpvoCUZQeuDI.pgp Description: PGP signature
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On 18/04/07, Emmanuele Massimi [EMAIL PROTECTED] wrote: On 18/04/07, Greg Folkert [EMAIL PROTECTED] wrote: On Wed, 2007-04-18 at 08:25 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 07:46 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. One other thing, you MUST have wacom-tools installed to configure and work with the wacom tablets. And YES Emmanuele, I have read the WHOLE thread. Yes, I understand you are not getting input from your tablet. Yes, once you do the modprobe wacom you are not getting any input yet. Have you installed wacom-tools? Have you used them to configure or check to see that your tablet is working properly. the wacom tools include: /usr/bin/wacdump /usr/bin/xidump /usr/bin/xsetwacom And you are sure you are using a **USB** Wacom tablet, not an older **SERIAL** Wacom tablet? One last thing, have you restarted your machine once you have done a: dpkg-reconfigure xserver-xorg And specifying you wacom tablet as an input device. You can have multiple input devices. If you have a USB tablet, I need to know your exact model of your wacom tablet. In order to give you a proper set of input devices for your xorg.conf Cheers. Thanks for your reply. I have installed the wacom-tools and the xserver-xorg-input-wacom packages, and I have configured the input devices in xorg.conf the same way I had on Ubuntu (where my pen tablet used to work), but I still get no input (always after modprobing). I can see the pen tablet
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Thu, 2007-04-19 at 11:52 +0100, Emmanuele Massimi wrote: I have read somewhere that the pen tablet should work out of the box, after modprobing it. So I did a clean re-installation (since in my previous one I did not install the Desktop Environment by default) including the Desktop Environment, just to be sure. I plugged my pen tablet in, and no joy. So I tried installing wacom-tools, and configuring the input devices in xorg.conf. Still, the pen tablet is not working. I really wonder where is the problem. Maybe it is just a little detail I am missing. Should I open a new thread with the title: Debain Etch: Wacom Volito2 not recongnised? That would be good. Also, if you could include a small amount of dumped data from the different programs... that would be good. Include assurances that the pen is indeed still good and whether or not you need the pad option. And any directions you have followed and a link to the previous thread you started (http://lists.debian.org/debian-user/2007/04/msg02765.html) I've been a bit busy, so I haven't had enough time to do some real searching. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On 19/04/07, Greg Folkert [EMAIL PROTECTED] wrote: On Thu, 2007-04-19 at 11:52 +0100, Emmanuele Massimi wrote: I have read somewhere that the pen tablet should work out of the box, after modprobing it. So I did a clean re-installation (since in my previous one I did not install the Desktop Environment by default) including the Desktop Environment, just to be sure. I plugged my pen tablet in, and no joy. So I tried installing wacom-tools, and configuring the input devices in xorg.conf. Still, the pen tablet is not working. I really wonder where is the problem. Maybe it is just a little detail I am missing. Should I open a new thread with the title: Debain Etch: Wacom Volito2 not recongnised? That would be good. Also, if you could include a small amount of dumped data from the different programs... that would be good. Include assurances that the pen is indeed still good and whether or not you need the pad option. And any directions you have followed and a link to the previous thread you started (http://lists.debian.org/debian-user/2007/04/msg02765.html ) I've been a bit busy, so I haven't had enough time to do some real searching. Ok, done. I hope it's fine. Thanks!
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Wed, 2007-04-18 at 07:46 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. One other thing, you MUST have wacom-tools installed to configure and work with the wacom tablets. And YES Emmanuele, I have read the WHOLE thread. Yes, I understand you are not getting input from your tablet. Yes, once you do the modprobe wacom you are not getting any input yet. Have you installed wacom-tools? Have you used them to configure or check to see that your tablet is working properly. the wacom tools include: /usr/bin/wacdump /usr/bin/xidump /usr/bin/xsetwacom And you are sure you are using a **USB** Wacom tablet, not an older **SERIAL** Wacom tablet? One last thing, have you restarted your machine once you have done a: dpkg-reconfigure xserver-xorg And specifying you wacom tablet as an input device. You can have multiple input devices. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Fwd: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On 18/04/07, Greg Folkert [EMAIL PROTECTED] wrote: On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. If it is already in the kernel, why can't I see any input from my pen tablet? Even after running modprobe wacom, nothing happens. That is why I was trying to install wacom-kernel-source: I thought it was missing.
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On 18/04/07, Greg Folkert [EMAIL PROTECTED] wrote: On Wed, 2007-04-18 at 08:25 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 07:46 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. One other thing, you MUST have wacom-tools installed to configure and work with the wacom tablets. And YES Emmanuele, I have read the WHOLE thread. Yes, I understand you are not getting input from your tablet. Yes, once you do the modprobe wacom you are not getting any input yet. Have you installed wacom-tools? Have you used them to configure or check to see that your tablet is working properly. the wacom tools include: /usr/bin/wacdump /usr/bin/xidump /usr/bin/xsetwacom And you are sure you are using a **USB** Wacom tablet, not an older **SERIAL** Wacom tablet? One last thing, have you restarted your machine once you have done a: dpkg-reconfigure xserver-xorg And specifying you wacom tablet as an input device. You can have multiple input devices. If you have a USB tablet, I need to know your exact model of your wacom tablet. In order to give you a proper set of input devices for your xorg.conf Cheers. Thanks for your reply. I have installed the wacom-tools and the xserver-xorg-input-wacom packages, and I have configured the input devices in xorg.conf the same way I had on Ubuntu (where my pen tablet used to work), but I still get no input (always after modprobing). I can see the pen tablet is recognised on /dev/input/wacom and on /dev/input/event$ (where $ changes at every reboot), using wacdump, but there is no evident input, namely, when I move the pen, no digits appear. I have
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Wed, 2007-04-18 at 08:25 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 07:46 -0400, Greg Folkert wrote: On Wed, 2007-04-18 at 09:45 +0200, Florian Kulzer wrote: On Tue, Apr 17, 2007 at 19:21:29 -0400, Greg Folkert wrote: On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. Are you sure that the wacom-kernel-source package is completely obsolete? The package description of xserver-xorg-input-wacom sounds like wacom-kernel-sources is still needed for some models. Go look at them. 2.6.16 is the latest the one in the Debian repository supports. I took the time, looked and actually went through them and found the problems, fixed the postinst script, went through the buildlog. Found that /usr/src/modules/wacom/src/2.6.[17|18|19|20] were all missing. is a quick listing of the directories in the wacom-kernel-source, which isn't a real kernel-source as I've come to know it, it is actually a kpkg building of the modules. princess:/usr/src/modules/wacom/src# ls -l total 504 drwxr-xr-x 2 root root 4096 2007-04-18 07:30 2.4 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.22 drwxr-xr-x 2 root root 119 2007-04-18 07:30 2.4.28 drwxr-xr-x 2 root root85 2007-04-18 07:26 2.4.30x86-64 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.10 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.11 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.13 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.14 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.15 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.16 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.8 drwxr-xr-x 2 root root70 2007-04-18 07:30 2.6.9 Do you see anything missing? The latest version in the /usr/src/modules/wacom/src/2.6.* tree is v1.44. Looked at the actual source in the 2.6.18-12 Linux Kernel source in /usr/src/linux-source-2.6.18/drivers/usb/input. v1.45 is the version in 2.6.18 Looked at the actual source in the 2.6.20-2 Linux Kernel source in /usr/src/linux-source-2.6.20/drivers/usb/input. v1.46 is the version in 2.6.20 So, it looks like it has either been accepted into the mainline kernel, or it has been patched into the Debian source. Either way, wacom-kernel-source is obsoleted or deprecated. One other thing, you MUST have wacom-tools installed to configure and work with the wacom tablets. And YES Emmanuele, I have read the WHOLE thread. Yes, I understand you are not getting input from your tablet. Yes, once you do the modprobe wacom you are not getting any input yet. Have you installed wacom-tools? Have you used them to configure or check to see that your tablet is working properly. the wacom tools include: /usr/bin/wacdump /usr/bin/xidump /usr/bin/xsetwacom And you are sure you are using a **USB** Wacom tablet, not an older **SERIAL** Wacom tablet? One last thing, have you restarted your machine once you have done a: dpkg-reconfigure xserver-xorg And specifying you wacom tablet as an input device. You can have multiple input devices. If you have a USB tablet, I need to know your exact model of your wacom tablet. In order to give you a proper set of input devices for your xorg.conf Cheers. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
Hi all, I've been browsing around, but I couldn't find anything related to this. I have been trying to install the wacom-kernel-source package on Etch, but it fails with the following error: Setting up wacom-kernel-source (0.7.4.1-5) ... /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments Warning: kernel headers don't match running Linux version. Building wacom modules for Linux _CODE 13262 (this may take a few minutes)...dpkg: error processing wacom-kernel-source (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: wacom-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I firstly thought there was an issue with my kernel headers, but I noticed I had the correct ones installed, and then noticed that the actual error was in /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49. Now I am not so experienced, and I don't know exactly what to do, I don't even know whether this is a bug. I am also very puzzled by the contents of line 49: [ $kvers = `uname -r` ] || echo Warning: kernel headers don't match running $kernel version. which seems to output of the warning message I get during the installation. Thanks a lot for your time.
Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
Hi all, I've been browsing around, but I couldn't find anything related to this. I have been trying to install the wacom-kernel-source package on Etch, but it fails with the following error: Setting up wacom-kernel-source (0.7.4.1-5) ... /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments Warning: kernel headers don't match running Linux version. Building wacom modules for Linux _CODE 13262 (this may take a few minutes)...dpkg: error processing wacom-kernel-source (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: wacom-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I firstly thought there was an issue with my kernel headers, but I noticed I had the correct ones installed, and then noticed that the actual error was in /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49. Now I am not so experienced, and I don't know exactly what to do, I don't even know whether this is a bug. I am also very puzzled by the contents of line 49: [ $kvers = `uname -r` ] || echo Warning: kernel headers don't match running $kernel version. which seems to output of the warning message I get during the installation. Thanks a lot for your time.
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
[ Sometimes it takes a short while for messages to show up on the list. Please be patient and don't send the same mail twice within 10 minutes. ] On Tue, Apr 17, 2007 at 15:35:35 +0100, Emmanuele Massimi wrote: Hi all, I've been browsing around, but I couldn't find anything related to this. I have been trying to install the wacom-kernel-source package on Etch, but it fails with the following error: Setting up wacom-kernel-source (0.7.4.1-5) ... /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments Warning: kernel headers don't match running Linux version. Building wacom modules for Linux _CODE 13262 (this may take a few minutes)...dpkg: error processing wacom-kernel-source (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: wacom-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I firstly thought there was an issue with my kernel headers, but I noticed I had the correct ones installed, and then noticed that the actual error was in /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49. Now I am not so experienced, and I don't know exactly what to do, I don't even know whether this is a bug. I am also very puzzled by the contents of line 49: [ $kvers = `uname -r` ] || echo Warning: kernel headers don't match running $kernel version. which seems to output of the warning message I get during the installation. Thanks a lot for your time. You are not the only one with this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418008 I think the problem is caused by line 48: kvers=`head -n 1 $ksrc/include/linux/version.h | cut -c 22- | rev | cut -c 2- | rev` Up to kernel 2.6.17 the first line of $ksrc/include/linux/version.h used to be (for my self-compiled kernel): #define UTS_RELEASE 2.6.17-flo Now this information seems to have been shifted to the file utsrelease.h. This means that the command from line 48 now sets $kvers to _CODE 13262 (or some other number) and this of course fails the version comparison and furthermore causes an error because it contains whitespace. (It would be better to enclose $kvers in quotes in the test condition, I guess.) I would try to change line 48 to: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` and run dpkg-reconfigure wacom-kernel-source again. If this works then we should submit a patch to the bug tracking system, so please report back here how it goes. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
Sorry for my stupid question, but I didn't get how I am supposed to change line 48. I see that you have underlined $ksrc/include/, but I don't really get what I should do with them... Thanks. On 17/04/07, Florian Kulzer [EMAIL PROTECTED] wrote: [ Sometimes it takes a short while for messages to show up on the list. Please be patient and don't send the same mail twice within 10 minutes. ] On Tue, Apr 17, 2007 at 15:35:35 +0100, Emmanuele Massimi wrote: Hi all, I've been browsing around, but I couldn't find anything related to this. I have been trying to install the wacom-kernel-source package on Etch, but it fails with the following error: Setting up wacom-kernel-source (0.7.4.1-5) ... /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments Warning: kernel headers don't match running Linux version. Building wacom modules for Linux _CODE 13262 (this may take a few minutes)...dpkg: error processing wacom-kernel-source (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: wacom-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I firstly thought there was an issue with my kernel headers, but I noticed I had the correct ones installed, and then noticed that the actual error was in /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49. Now I am not so experienced, and I don't know exactly what to do, I don't even know whether this is a bug. I am also very puzzled by the contents of line 49: [ $kvers = `uname -r` ] || echo Warning: kernel headers don't match running $kernel version. which seems to output of the warning message I get during the installation. Thanks a lot for your time. You are not the only one with this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418008 I think the problem is caused by line 48: kvers=`head -n 1 $ksrc/include/linux/version.h | cut -c 22- | rev | cut -c 2- | rev` Up to kernel 2.6.17 the first line of $ksrc/include/linux/version.h used to be (for my self-compiled kernel): #define UTS_RELEASE 2.6.17-flo Now this information seems to have been shifted to the file utsrelease.h. This means that the command from line 48 now sets $kvers to _CODE 13262 (or some other number) and this of course fails the version comparison and furthermore causes an error because it contains whitespace. (It would be better to enclose $kvers in quotes in the test condition, I guess.) I would try to change line 48 to: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` and run dpkg-reconfigure wacom-kernel-source again. If this works then we should submit a patch to the bug tracking system, so please report back here how it goes. -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Tue, Apr 17, 2007 at 20:00:40 +0100, Emmanuele Massimi wrote: Sorry for my stupid question, but I didn't get how I am supposed to change line 48. I see that you have underlined $ksrc/include/, but I don't really get what I should do with them... The underlining with ^^ was only meant to make it easier for you to spot which part of this long line you have to change. The only thing you have to do is to replace the text version.h with utsrelease.h. The rest of line 48 (and the rest of the file) should stay as it is. If your question was meant to be more general, i.e. how can I edit ASCII files, then see for example here: http://newbiedoc.berlios.de/wiki/Using_Joe_as_your_editor Finally, your chances of many people joining in and helping you will improve if you change your posting style. For details, see section 5 of this document: http://people.cornell.edu/pages/kk288/du-guidelines.html On 17/04/07, Florian Kulzer wrote: [ Sometimes it takes a short while for messages to show up on the list. Please be patient and don't send the same mail twice within 10 minutes. ] On Tue, Apr 17, 2007 at 15:35:35 +0100, Emmanuele Massimi wrote: Hi all, I've been browsing around, but I couldn't find anything related to this. I have been trying to install the wacom-kernel-source package on Etch, but it fails with the following error: Setting up wacom-kernel-source (0.7.4.1-5) ... /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments Warning: kernel headers don't match running Linux version. Building wacom modules for Linux _CODE 13262 (this may take a few minutes)...dpkg: error processing wacom-kernel-source (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: wacom-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I firstly thought there was an issue with my kernel headers, but I noticed I had the correct ones installed, and then noticed that the actual error was in /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49. Now I am not so experienced, and I don't know exactly what to do, I don't even know whether this is a bug. I am also very puzzled by the contents of line 49: [ $kvers = `uname -r` ] || echo Warning: kernel headers don't match running $kernel version. which seems to output of the warning message I get during the installation. Thanks a lot for your time. You are not the only one with this issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418008 I think the problem is caused by line 48: kvers=`head -n 1 $ksrc/include/linux/version.h | cut -c 22- | rev | cut -c 2- | rev` Up to kernel 2.6.17 the first line of $ksrc/include/linux/version.h used to be (for my self-compiled kernel): #define UTS_RELEASE 2.6.17-flo Now this information seems to have been shifted to the file utsrelease.h. This means that the command from line 48 now sets $kvers to _CODE 13262 (or some other number) and this of course fails the version comparison and furthermore causes an error because it contains whitespace. (It would be better to enclose $kvers in quotes in the test condition, I guess.) I would try to change line 48 to: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` and run dpkg-reconfigure wacom-kernel-source again. If this works then we should submit a patch to the bug tracking system, so please report back here how it goes. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
Ok, thanks for your delucidation, I looked at both the lines, but I must have skipped that word, in fact I couldn't tell the difference between the two lines. I guess it's time to buy new glasses... Anyways, this is what I get when I run dpkg-reconfigure wacom-kernel-source: /usr/sbin/dpkg-reconfigure: wacom-kernel-source is broken or not fully installed I hope formatting is a bit better now, I'll try my best from now on. Thank you. On 17/04/07, Florian Kulzer [EMAIL PROTECTED] wrote: On Tue, Apr 17, 2007 at 20:00:40 +0100, Emmanuele Massimi wrote: Sorry for my stupid question, but I didn't get how I am supposed to change line 48. I see that you have underlined $ksrc/include/, but I don't really get what I should do with them... The underlining with ^^ was only meant to make it easier for you to spot which part of this long line you have to change. The only thing you have to do is to replace the text version.h with utsrelease.h. The rest of line 48 (and the rest of the file) should stay as it is. If your question was meant to be more general, i.e. how can I edit ASCII files, then see for example here: http://newbiedoc.berlios.de/wiki/Using_Joe_as_your_editor Finally, your chances of many people joining in and helping you will improve if you change your posting style. For details, see section 5 of this document: http://people.cornell.edu/pages/kk288/du-guidelines.html
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Tue, Apr 17, 2007 at 21:34:43 +0100, Emmanuele Massimi wrote: Ok, thanks for your delucidation, I looked at both the lines, but I must have skipped that word, in fact I couldn't tell the difference between the two lines. I guess it's time to buy new glasses... Anyways, this is what I get when I run dpkg-reconfigure wacom-kernel-source: /usr/sbin/dpkg-reconfigure: wacom-kernel-source is broken or not fully installed Try dpkg-reconfigure --force wacom-kernel-source If anything goes wrong then please copy the complete output of this command into a mail and send it to the list. I hope formatting is a bit better now, I'll try my best from now on. You are still top-posting, i.e. you put your text above the text of the message to which you are replying. I know that this style is very common in the business world and it is more or less OK as long as you have a dialog between two persons and both still remember the previous messages. For a mailing list such as debian-user, however, it is better to put the reply at the appropriate position in the older text and to trim the previous message where possible, but not too much. Just look at this mail: Many people will read it without remembering the previous messages. Therefore they cannot know which file we are referring to and which changes I suggested you should make. There are just too many threads going on on debian-user, and hardly anybody has time to look up old messages in the archive. So most people will be mildly annoyed by this message and will quickly delete it. That means nobody joins in with new ideas and nobody can spot mistakes that I may have made, etc. Ergo: top-posting is double-plus-ungood. The whole issue is nowadays complicated by forums such as www.debianhelp.org which sponge off the content of this mailing list (nothing wrong with that) and then feed the questions/reactions of their users back to this list in an inappropriate manner. -- Regards,| http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On 17/04/07, Florian Kulzer [EMAIL PROTECTED] wrote: On Tue, Apr 17, 2007 at 21:34:43 +0100, Emmanuele Massimi wrote: Ok, thanks for your delucidation, I looked at both the lines, but I must have skipped that word, in fact I couldn't tell the difference between the two lines. I guess it's time to buy new glasses... Anyways, this is what I get when I run dpkg-reconfigure wacom-kernel-source: /usr/sbin/dpkg-reconfigure: wacom-kernel-source is broken or not fully installed Try dpkg-reconfigure --force wacom-kernel-source If anything goes wrong then please copy the complete output of this command into a mail and send it to the list. Ok, I have used the --force flag and I went through the installation, which failed. Here is the output (I hope it's not too long): Building wacom modules for Linux 2.6.18-4-686 (this may take a few minutes)... dh_testdir dh_testroot rm -f *-stamp dh_clean dh_testdir dh_testroot /usr/bin/make clean; make[1]: Entering directory `/usr/src/modules/wacom' Making clean in src make[2]: Entering directory `/usr/src/modules/wacom/src' Making clean in 2.4 make[3]: Entering directory `/usr/src/modules/wacom/src/2.4' rm -f *.o core *.core make[3]: Leaving directory `/usr/src/modules/wacom/src/2.4' Making clean in wacomxi make[3]: Entering directory `/usr/src/modules/wacom/src/wacomxi' rm -rf .libs _libs test -z || rm -f rm -f *.o rm -f *.lo make[3]: Leaving directory `/usr/src/modules/wacom/src/wacomxi' Making clean in . make[3]: Entering directory `/usr/src/modules/wacom/src' test -z libwacomcfg.la || rm -f libwacomcfg.la rm -f ./so_locations rm -rf .libs _libs rm -f *.o rm -f *.lo make[3]: Leaving directory `/usr/src/modules/wacom/src' make[2]: Leaving directory `/usr/src/modules/wacom/src' Making clean in . make[2]: Entering directory `/usr/src/modules/wacom' rm -rf .libs _libs rm -f *.lo make[2]: Leaving directory `/usr/src/modules/wacom' make[1]: Leaving directory `/usr/src/modules/wacom' rm -f debian/wacom-kernel-modules-2.6.18-4-686.* debian/control ./configure --disable-libwacomxi \ --disable-wacomdrv \ --disable-libwacomcfg \ --disable-wacdump \ --disable-xidump \ --disable-xsetwacom \ --enable-wacom \ --with-kernel=/usr/src/linux/ checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether to enable maintainer-specific portions of Makefiles... no checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for gawk... (cached) mawk checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ld used by gcc... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking for /usr/bin/ld option to reload object files... -r checking for BSD-compatible nm... /usr/bin/nm -B checking whether ln -s works... yes checking how to recognise dependent libraries... pass_all checking how to run the C preprocessor... gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking dlfcn.h usability... yes checking dlfcn.h presence... yes checking for dlfcn.h... yes checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for cf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for pghpf... no checking for epcf90... no checking for gfortran... no checking for g95... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifort... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for ftn... no checking whether we are using the GNU Fortran 77 compiler... no checking whether accepts -g... no checking the maximum length of command line arguments
Re: Installing wacom-kernel-source on Etch: /var/lib/dpkg/info/wacom-kernel-source.postinst: line 49: [: too many arguments
On Tue, 2007-04-17 at 23:16 +0100, Emmanuele Massimi wrote: [snip] /var/lib/dpkg/info/wacom-kernel-source.postinst has a couple of mistakes relating to recent kernels. line 48 needs to look like this: kvers=`head -n 1 $ksrc/include/linux/utsrelease.h | cut -c 22- | rev | cut -c 2- | rev` But the build still fails for anything after 2.6.16... since that is the last update for the wacom-kernel-source and 2.6.18 (or 20 for me) doesn't exist. Plus, AFAICS, it isn't needed anymore. modprobe tells me: /lib/modules/2.6.18-4-k7/kernel/drivers/usb/input/wacom.ko Also found in for me in: /lib/modules/2.6.20-1-k7/kernel/drivers/usb/input/wacom.ko So, this here results in, what are you trying to do? The following commands, as needed should help you out. sudo /sbin/modprobe wacom or modprobe wacom should do the trick for you. Sorry Florian, I believe you went off on a wild goose chase with Emmanuele, without even knowing it. -- greg, [EMAIL PROTECTED] Novell's Directory Services is a competitive product to Microsoft's Active Directory in much the same way that the Saturn V is a competitive product to those dinky little model rockets that kids light off down at the playfield. -- Thane Walkup signature.asc Description: This is a digitally signed message part
Re: kernel 2.6.20-1 et nvidia-kernel-source
On Thu, Apr 12, 2007 at 03:33:23PM +0200, C. Mourad Jaber wrote: Bonjour, Existe-t-il un patch pour permettre la compilation du module nvidia (1.0.9746) avec le noyau 2.6.20-1 tout fraîchement importé en instable ? S'il y en a un, je ne l'ai pas trouvé :( Par contre, j'ai réussi à compiler le module après recompilation du noyau sans les options CONFIG_HIGHPTE (et/ou CONFIG_PREEMPT_RT) et CONFIG_PARAVIRT, selon des indications trouvées à: http://www.nvnews.net/vbulletin/showthread.php?t=85107highlight=gpl-incompatible Note cependant que je ne suis pas sûr d'avoir trouvé le même problème que toi; essaye d'être plus précis la prochaine fois (comment ça, permettre la compilation? qu'est-ce qui t'empêchait de la faire?). Tiago. -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel 2.6.20-1 et nvidia-kernel-source
Bonjour, Existe-t-il un patch pour permettre la compilation du module nvidia (1.0.9746) avec le noyau 2.6.20-1 tout fraîchement importé en instable ? Merci Mourad -- Lisez la FAQ de la liste avant de poser une question : http://wiki.debian.net/?DebianFrench Vous pouvez aussi ajouter le mot ``spam'' dans vos champs From et Reply-To: To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
module-assistant problem with kernel source
Hello all,
I am trying to use m-a to install ndiswrapper. I am using debian stable
with backports for module-assistant,build-essential,xorg,kde. m-a
prepare says everything is great and I made sure its getting the
linux-headers from backports. My kernel is stock from backports
2.6.18-4-k7 #1 SMP Mon Feb 5 17:45:20 CET 2007 i686 GNU/Linux. When I
run m-a a-i ndiswrapper is says Bad luck, the kernel headers for the
target kernel version could not be found and you did not specify other
valid kernel headers to use. So I tried m-a -k
/usr/src/linux-headers-2.6.18-4-k7/ a-i ndiswrapper That tries to
build and gives me the following log.
/usr/bin/gcc-3.3
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/#define
LINUX_VERSION_CODE 132626/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/#define LINUX_VERSION_CODE 132626/g
;s/#KVERS#/#define LINUX_VERSION_CODE 132626/g ; s/_KVERS_/#define
LINUX_VERSION_CODE 132626/g ; s/##KDREV##//g ; s/#KDREV#//g ;
s/_KDREV_//g' $templ ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean
make[1]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o
misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o divdi3.o
usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/gcc-3.3
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_//g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##//g ;s/#KVERS#//g ; s/_KVERS_//g ; s/##KDREV##//g
; s/#KDREV#//g ; s/_KDREV_//g' $templ ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o
misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o divdi3.o
usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: Nothing to be done for `kdist_config'.
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs lib/modules//misc
# build and install the module
/usr/bin/make KPKG_EXTRAV_ARG= KSRC=/usr/src/linux-headers-2.6.18-4-k7/ \
KVER= \
INST_DIR=debian/ndiswrapper-modules-/lib/modules//misc/ install
make[2]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -C /usr/src/linux-headers-2.6.18-4-k7/
SUBDIRS=/usr/src/modules/ndiswrapper \
NDISWRAPPER_VERSION=1.1 \
EXTRA_VERSION= modules
make[3]: Entering directory `/usr/src/linux-headers-2.6.18-4-k7'
CC [M] /usr/src/modules/ndiswrapper/hal.o
CC [M] /usr/src/modules/ndiswrapper/iw_ndis.o
CC [M] /usr/src/modules/ndiswrapper/loader.o
/usr/src/modules/ndiswrapper/loader.c: In function `register_devices':
/usr/src/modules/ndiswrapper/loader.c:861: warning: assignment from
incompatible pointer type
/usr/src/modules/ndiswrapper/loader.c:873: error: structure has no
member named `owner'
make[4]: *** [/usr/src/modules/ndiswrapper/loader.o] Error 1
make[3]: *** [_module_/usr/src/modules/ndiswrapper] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.18-4-k7'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: *** [binary-modules] Error 2
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
make: *** [kdist_build] Error 2
Any suggestions on how to fix this would be a great help.
Thanks,
Gokee2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
module-assistant problem with kernel source
Hello all,
I am trying to use m-a to install ndiswrapper. I am using debian stable
with backports for module-assistant,build-essential,xorg,kde. m-a
prepare says everything is great and I made sure its getting the
linux-headers from backports. My kernel is stock from backports
2.6.18-4-k7 #1 SMP Mon Feb 5 17:45:20 CET 2007 i686 GNU/Linux. When I
run m-a a-i ndiswrapper is says Bad luck, the kernel headers for the
target kernel version could not be found and you did not specify other
valid kernel headers to use. So I tried m-a -k
/usr/src/linux-headers-2.6.18-4-k7/ a-i ndiswrapper That tries to
build and gives me the following log.
/usr/bin/gcc-3.3
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_/#define
LINUX_VERSION_CODE 132626/g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##/#define LINUX_VERSION_CODE 132626/g
;s/#KVERS#/#define LINUX_VERSION_CODE 132626/g ; s/_KVERS_/#define
LINUX_VERSION_CODE 132626/g ; s/##KDREV##//g ; s/#KDREV#//g ;
s/_KDREV_//g' $templ ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean
make[1]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o
misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o divdi3.o
usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules
make[1]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/gcc-3.3
for templ in ; do \
cp $templ `echo $templ | sed -e 's/_KVERS_//g'` ; \
done
for templ in `ls debian/*.modules.in` ; do \
test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in}
${templ%.modules.in}.backup 2/dev/null || true; \
sed -e 's/##KVERS##//g ;s/#KVERS#//g ; s/_KVERS_//g ; s/##KDREV##//g
; s/#KDREV#//g ; s/_KDREV_//g' $templ ${templ%.modules.in}; \
done
dh_clean
/usr/bin/make clean
make[2]: Entering directory `/usr/src/modules/ndiswrapper'
rm -rf ndiswrapper.ko ndiswrapper.o hal.o iw_ndis.o loader.o
misc_funcs.o ndis.o ntoskernel.o pe_linker.o proc.o wrapper.o divdi3.o
usb.o x86_64_stubs.o \
divdi3.o .*.ko.cmd .*.o.cmd ndiswrapper.mod.[oc] *~ .tmp_versions
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: Nothing to be done for `kdist_config'.
dh_testdir
dh_testroot
dh_clean -k
dh_installdirs lib/modules//misc
# build and install the module
/usr/bin/make KPKG_EXTRAV_ARG= KSRC=/usr/src/linux-headers-2.6.18-4-k7/ \
KVER= \
INST_DIR=debian/ndiswrapper-modules-/lib/modules//misc/ install
make[2]: Entering directory `/usr/src/modules/ndiswrapper'
/usr/bin/make -C /usr/src/linux-headers-2.6.18-4-k7/
SUBDIRS=/usr/src/modules/ndiswrapper \
NDISWRAPPER_VERSION=1.1 \
EXTRA_VERSION= modules
make[3]: Entering directory `/usr/src/linux-headers-2.6.18-4-k7'
CC [M] /usr/src/modules/ndiswrapper/hal.o
CC [M] /usr/src/modules/ndiswrapper/iw_ndis.o
CC [M] /usr/src/modules/ndiswrapper/loader.o
/usr/src/modules/ndiswrapper/loader.c: In function `register_devices':
/usr/src/modules/ndiswrapper/loader.c:861: warning: assignment from
incompatible pointer type
/usr/src/modules/ndiswrapper/loader.c:873: error: structure has no
member named `owner'
make[4]: *** [/usr/src/modules/ndiswrapper/loader.o] Error 1
make[3]: *** [_module_/usr/src/modules/ndiswrapper] Error 2
make[3]: Leaving directory `/usr/src/linux-headers-2.6.18-4-k7'
make[2]: *** [default] Error 2
make[2]: Leaving directory `/usr/src/modules/ndiswrapper'
make[1]: *** [binary-modules] Error 2
make[1]: Leaving directory `/usr/src/modules/ndiswrapper'
make: *** [kdist_build] Error 2
Any suggestions on how to fix this would be a great help.
Thanks,
Gokee2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
Apologies if this question has already been answered, but I have not been able yet to get ANY version of nvidia-glx back on my system! I run a mix of testing and experimental (?), see my sources.list below. The nvidia driver files should come straight from their Maker.. My kernel is 2.6.18, and my X server is Xorg. I have read some hints of changing to unstable to get nvidia-glx, but have never been able to replicate any one of those excercises... When I run apt-get install nvidia-glx it keeps giving messages like nvidia-glx depends on xserver-common so I guess that is still a problem XFree86/Xorg? The rest of the nvidia packages install well, by the way. It is just nvidia-glx whose access is completely denied by apt/xorg or a combination of the two... There are loads of web pages on this, but none of the solutions there seems to work for everyone? Thanks Alle Meije sources.list: # general # TESTING # UK deb ftp://ftp.uk.debian.org/debian/ testing main contrib non-free # if UK is down - NL? # deb ftp://ftp.nl.debian.org/debian/ unstable main contrib non-free # nvidia driver: see http://people.debian.org/~rdonald/index.php # use this source line for unstable drivers deb http://people.debian.org/~rdonald/nvidia unstable nvidia-graphics-drivers deb http://people.debian.org/~rdonald/nvidia unstable nvidia-kernel-common deb http://people.debian.org/~rdonald/nvidia unstable nvidia-settings deb http://people.debian.org/~rdonald/nvidia unstable nvidia-xconfig deb http://people.debian.org/~rdonald/nvidia unstable modules # mplayer # see http://www.debian-multimedia.org/ deb http://www.debian-multimedia.org etch main # root dirs that may contain packages # deb file:/root/ debs/ Subject: Re: when will nvidai-glx and nvidia-kernel-source hit etch? From: Florian Kulzer [EMAIL PROTECTED] Date: Thu, 9 Nov 2006 12:26:22 +0100 To: debian-user@lists.debian.org To: debian-user@lists.debian.org On Thu, Nov 09, 2006 at 10:38:23 +0100, Lubos Vrbka wrote: Florian Kulzer wrote: Now I am confused: me too... $ apt-file search nvidia_drv nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o nvidia-glx-legacy: usr/lib/xorg/modules/drivers/nvidia_drv.o i get empty output from apt-file. Maybe the .so file comes from an older version of nvidia-glx. What is the result of dpkg -S nvidia_drv? nvidia-glx: /usr/lib/xorg/modules/drivers/nvidia_drv.so btw, dpkg -l nvidia-glx gives me 1.0.9625-2 NVIDIA binary XFree86 4.x driver That is the driver from Experimental. (Maybe you mentioned that before and I did not notice.) I have never tried that one myself so there might be some 9xxx-specific issue that I don't know anything about. OK, indeed the name is .so: $ aptitude download nvidia-glx/experimental $ dpkg-deb --contents nvidia-glx_1.0.9625-2_i386.deb | grep nvidia_drv -rw-r--r-- root/root 1064588 2006-10-20 19:55 ./usr/lib/xorg/modules/drivers/nvidia_drv.so The only thing I know for sure from when I switched from the nvidia installer to the Debian packages is that the .so and the .o module do not play nicely together (at least if the .so file comes from the nvidia installer). strange... there is really no .o file in xorg/modules/drivers/ It seems that there is a bug in apt-file: I have Experimental in my sources.list and yet apt-file search did not tell me about the nvidia_drv.so file, and in your case it comes up empty. Anyway, that means my previous statements do not apply to your situation at all. I am sorry for adding to the confusion. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
On Tue, Nov 14, 2006 at 09:30:58 +, Alle Meije Wink wrote: Apologies if this question has already been answered, but I have not been able yet to get ANY version of nvidia-glx back on my system! I run a mix of testing and experimental (?), see my sources.list below. The nvidia driver files should come straight from their Maker.. My kernel is 2.6.18, and my X server is Xorg. I have read some hints of changing to unstable to get nvidia-glx, but have never been able to replicate any one of those excercises... When I run apt-get install nvidia-glx it keeps giving messages like nvidia-glx depends on xserver-common so I guess that is still a problem XFree86/Xorg? The rest of the nvidia packages install well, by the way. It is just nvidia-glx whose access is completely denied by apt/xorg or a combination of the two... You are still trying to install the Sarge version of nvidia-glx which depends on Xfree86 via xserver-common. Take the version from unstable or experimental; these two depend on x11-common and are Xorg compatible: $ apt-cache policy nvidia-glx nvidia-glx: Installed: 1.0.8776-1 Candidate: 1.0.8776-1 Version table: 1.0.9625-2 0 50 http://ftp.debian.org experimental/non-free Packages *** 1.0.8776-1 0 500 http://ftp.nl.debian.org unstable/non-free Packages 100 /var/lib/dpkg/status 1.0.7174-3 0 500 http://ftp.nl.debian.org stable/non-free Packages -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
On Thu, Nov 09, 2006 at 08:00:34 +0100, Lubos Vrbka wrote: hi, actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come from? (i hope i wrote the path correctly) is it part of the binary files from nvidia.com? 'apt-file search' didn't reveal anything relevant. /usr/lib/xorg/modules/drivers/nvidia_drv.so is indeed part of the nvidia binaries and is only installed if you use the nvidia script directly. i think this is not true. i certainly didn't use the nvidia script directly. i used m-a only. If you use the Debian method then nvidia-glx will give you /usr/lib/xorg/modules/drivers/nvidia_drv.o instead. (.o instead of .so) as i wrote above, i did it the debian way (tm). however, no .o file is present in the xorg/modules/drivers. only fbdev_drv.so, nv_drv.so, nvidia_drv.so, riva128_drv.so, vesa_drv.so Now I am confused: $ apt-file search nvidia_drv nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o nvidia-glx-legacy: usr/lib/xorg/modules/drivers/nvidia_drv.o Maybe the .so file comes from an older version of nvidia-glx. What is the result of dpkg -S nvidia_drv? The only thing I know for sure from when I switched from the nvidia installer to the Debian packages is that the .so and the .o module do not play nicely together (at least if the .so file comes from the nvidia installer). -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
Florian Kulzer wrote: Now I am confused: me too... $ apt-file search nvidia_drv nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o nvidia-glx-legacy: usr/lib/xorg/modules/drivers/nvidia_drv.o i get empty output from apt-file. Maybe the .so file comes from an older version of nvidia-glx. What is the result of dpkg -S nvidia_drv? nvidia-glx: /usr/lib/xorg/modules/drivers/nvidia_drv.so btw, dpkg -l nvidia-glx gives me 1.0.9625-2 NVIDIA binary XFree86 4.x driver The only thing I know for sure from when I switched from the nvidia installer to the Debian packages is that the .so and the .o module do not play nicely together (at least if the .so file comes from the nvidia installer). strange... there is really no .o file in xorg/modules/drivers/ regards, -- Lubos [EMAIL PROTECTED] http://www.lubos.vrbka.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
On Thu, Nov 09, 2006 at 10:38:23 +0100, Lubos Vrbka wrote: Florian Kulzer wrote: Now I am confused: me too... $ apt-file search nvidia_drv nvidia-glx: usr/X11R6/lib/modules/drivers/nvidia_drv.o nvidia-glx: usr/lib/xorg/modules/drivers/nvidia_drv.o nvidia-glx-legacy: usr/lib/xorg/modules/drivers/nvidia_drv.o i get empty output from apt-file. Maybe the .so file comes from an older version of nvidia-glx. What is the result of dpkg -S nvidia_drv? nvidia-glx: /usr/lib/xorg/modules/drivers/nvidia_drv.so btw, dpkg -l nvidia-glx gives me 1.0.9625-2 NVIDIA binary XFree86 4.x driver That is the driver from Experimental. (Maybe you mentioned that before and I did not notice.) I have never tried that one myself so there might be some 9xxx-specific issue that I don't know anything about. OK, indeed the name is .so: $ aptitude download nvidia-glx/experimental $ dpkg-deb --contents nvidia-glx_1.0.9625-2_i386.deb | grep nvidia_drv -rw-r--r-- root/root 1064588 2006-10-20 19:55 ./usr/lib/xorg/modules/drivers/nvidia_drv.so The only thing I know for sure from when I switched from the nvidia installer to the Debian packages is that the .so and the .o module do not play nicely together (at least if the .so file comes from the nvidia installer). strange... there is really no .o file in xorg/modules/drivers/ It seems that there is a bug in apt-file: I have Experimental in my sources.list and yet apt-file search did not tell me about the nvidia_drv.so file, and in your case it comes up empty. Anyway, that means my previous statements do not apply to your situation at all. I am sorry for adding to the confusion. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
nvidia-glx is a package, created from the nvidia-graphics-drivers source package. nvidia-graphics-drivers contains the binary .run files from nvidia.com plus some scripting voodoo used in package creation. http://packages.debian.org/unstable/source/nvidia-graphics-drivers shows the four packages created from this source package. m-a a-i nvidia does the following: ... The nvidia-glx package depends on nvidia-kernel-$NVIDIAVERSION - however, this package doesn't actually exist. It's a virtual package, which is provided by nvidia-kernel-$(uname -r)_$NVIDIAVERSION.deb Hence nvidia-glx won't install unless you run m-a a-i nvidia first, in order to provide the kernel module package. thanks for perfect explanation. actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come from? (i hope i wrote the path correctly) is it part of the binary files from nvidia.com? 'apt-file search' didn't reveal anything relevant. best regards, -- Lubos [EMAIL PROTECTED] http://www.lubos.vrbka.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
On Wed, Nov 08, 2006 at 19:40:39 +0100, Lubos Vrbka wrote: nvidia-glx is a package, created from the nvidia-graphics-drivers source package. nvidia-graphics-drivers contains the binary .run files from nvidia.com plus some scripting voodoo used in package creation. http://packages.debian.org/unstable/source/nvidia-graphics-drivers shows the four packages created from this source package. m-a a-i nvidia does the following: ... The nvidia-glx package depends on nvidia-kernel-$NVIDIAVERSION - however, this package doesn't actually exist. It's a virtual package, which is provided by nvidia-kernel-$(uname -r)_$NVIDIAVERSION.deb Hence nvidia-glx won't install unless you run m-a a-i nvidia first, in order to provide the kernel module package. thanks for perfect explanation. actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come from? (i hope i wrote the path correctly) is it part of the binary files from nvidia.com? 'apt-file search' didn't reveal anything relevant. /usr/lib/xorg/modules/drivers/nvidia_drv.so is indeed part of the nvidia binaries and is only installed if you use the nvidia script directly. If you use the Debian method then nvidia-glx will give you /usr/lib/xorg/modules/drivers/nvidia_drv.o instead. (.o instead of .so) If you want to switch to nvidia-glx then you should remove the .so file. -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: when will nvidai-glx and nvidia-kernel-source hit etch?
hi, actually, where does /usr/lib/xorg/modules/drivers/nvidia_drv.so come from? (i hope i wrote the path correctly) is it part of the binary files from nvidia.com? 'apt-file search' didn't reveal anything relevant. /usr/lib/xorg/modules/drivers/nvidia_drv.so is indeed part of the nvidia binaries and is only installed if you use the nvidia script directly. i think this is not true. i certainly didn't use the nvidia script directly. i used m-a only. If you use the Debian method then nvidia-glx will give you /usr/lib/xorg/modules/drivers/nvidia_drv.o instead. (.o instead of .so) as i wrote above, i did it the debian way (tm). however, no .o file is present in the xorg/modules/drivers. only fbdev_drv.so, nv_drv.so, nvidia_drv.so, riva128_drv.so, vesa_drv.so regards, -- Lubos [EMAIL PROTECTED] http://www.lubos.vrbka.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
kernel source trees
Where's my source tree? How do I get one if I don't have one? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
