Solved

Unable to install driver under Debian 7.1.0

Matthew Bennetts shared this problem 3 years ago

I have a brand new install of Debian Wheezy (7.1.0) and can't get the driver to install. The git clone is missing a "make install" task:

  1. make install
  2. make: *** No rule to make target `install'. Stop.

And trying to install using the prebuilt packages fails with:

  1. sudo dpkg -i solo6010-dkms_2.4.8-5_all.deb
  2. Selecting previously unselected package solo6010-dkms.
  3. (Reading database ... 147980 files and directories currently installed.)
  4. Unpacking solo6010-dkms (from solo6010-dkms_2.4.8-5_all.deb) ...
  5. Setting up solo6010-dkms (2.4.8-5) ...
  6. Removing all [solo6010-2.4.8] DKMS Modules
  7. Error! There are no instances of module: solo6010
  8. 2.4.8 located in the DKMS tree.
  9. Done.
  10. Adding [solo6010-2.4.8] Module to DKMS build system
  11. Doing initial module build
  12. Error! Bad return status for module build on kernel: 3.2.0-4-amd64 (x86_64)
  13. Consult /var/lib/dkms/solo6010/2.4.8/build/make.log for more information.
  14. dpkg: error processing solo6010-dkms (--install):
  15. subprocess installed post-installation script returned error exit status 10
  16. Errors were encountered while processing:
  17. solo6010-dkms

So, what now?

Regards,

Matt

Comments (4)

photo
1

What does /var/lib/dkms/solo6010/2.4.8/build/make.log show?

photo
1

I seem to have the same issue:

Debian 7

Linux tritium 3.12-1-amd64 #1 SMP Debian 3.12.9-1 (2014-02-01) x86_64 GNU/Linux

  1. # dpkg -i solo6010-dkms_2.4.8-6_all.deb

    (Reading database ... 182348 files and directories currently installed.)

    Preparing to unpack solo6010-dkms_2.4.8-6_all.deb ...

    Removing all [solo6010-2.4.8] DKMS Modules

    Done.

    Unpacking solo6010-dkms (2.4.8-6) over (2.4.8-6) ...

    Setting up solo6010-dkms (2.4.8-6) ...

    Removing all [solo6010-2.4.8] DKMS Modules

    Error! There are no instances of module: solo6010

    2.4.8 located in the DKMS tree.

    Done.

    Adding [solo6010-2.4.8] Module to DKMS build system

    Doing initial module build

    Error! Bad return status for module build on kernel: 3.12-1-amd64 (x86_64)

    Consult /var/lib/dkms/solo6010/2.4.8/build/make.log for more information.

    dpkg: error processing package solo6010-dkms (--install):

    subprocess installed post-installation script returned error exit status 10

    Errors were encountered while processing:

    solo6010-dkms

And, from the make.log

  1. # less /var/lib/dkms/solo6010/2.4.8/build/make.log

    DKMS make.log for solo6010-2.4.8 for kernel 3.12-1-amd64 (x86_64)

    Wed Feb 12 20:40:11 EST 2014

    make: Entering directory `/usr/src/linux-headers-3.12-1-amd64'

    LD /var/lib/dkms/solo6010/2.4.8/build/built-in.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-core.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-i2c.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-p2m.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-v4l2.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-tw28.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-gpio.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-disp.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-enc.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-v4l2-enc.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-g723.o

    CC [M] /var/lib/dkms/solo6010/2.4.8/build/solo6x10-eeprom.o

    make[3]: *** No rule to make target `/var/lib/dkms/solo6010/2.4.8/build/videobuf-dma-contig.o', needed by `/var/lib/dkms/solo6010/2.4.8/build/solo6x10-edge.o'. Stop.

    make[2]: *** [_module_/var/lib/dkms/solo6010/2.4.8/build] Error 2

    make[1]: *** [sub-make] Error 2

    make: *** [all] Error 2

    make: Leaving directory `/usr/src/linux-headers-3.12-1-amd64'

    /var/lib/dkms/solo6010/2.4.8/build/make.log (END)

Any help would be appreciated.

Regards

Del

photo
1

Seems to be a missing makefile (videobuf.mk): see my response to this thread.

photo
1

Cleaning up old threads, if this is still an issue please respond so we can look into it.