SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello!
I am running Slackware-12.1 with kernel generic-smp-2.6.24.5-smp.
So far (on Slackware 12.0 with generic-smp-2.6.21.5) I used to successfully compile my webcam driver qc-usb-messenger-1.7: http://home.mag.cx/messenger/source/...ger-1.7.tar.gz However, now I get the following error when compiling:
make -C "/lib/modules/2.6.24.5-smp/build" SUBDIRS="/home/marto/build/tmp/qc-usb-messenger-1.7" modules V=1 USER_OPT="-DHAVE_UTSRELEASE_H=1"
make[1]: Entering directory `/usr/src/linux-2.6.24.5'
test -e include/linux/autoconf.h -a -e include/config/auto.conf || ( \
echo; \
echo " ERROR: Kernel configuration is invalid."; \
echo " include/linux/autoconf.h or include/config/auto.conf are missing."; \
echo " Run 'make oldconfig && make prepare' on kernel src to fix it."; \
echo; \
/bin/false)
mkdir -p /home/marto/build/tmp/qc-usb-messenger-1.7/.tmp_versions ; rm -f /home/marto/build/tmp/qc-usb-messenger-1.7/.tmp_versions/*
Any suggestions? Why did the 21.0 kernel work? What could I do? I hope there is a solution that does not require kernel compilation because I am daunted by such a perspective.
Did you upgrade from 12.0 to 12.1 or did you install fresh? What kernel are you using? That test is just seeing if /usr/src/linux/2.6.24.5/include/linux/autoconf.h and /usr/src/linux/2.6.24.5/include/config/auto.conf exist. Do they (they should in a default Slackware 12.1 setup)?
Just cd into the kernel sources at /usr/src/linux-2.6.24.5 and run:
'make oldconfig'
This should generate the missing files which the driver module sources are looking for.
Just cd into the kernel sources at /usr/src/linux-2.6.24.5 and run:
'make oldconfig'
This should generate the missing files which the driver module sources are looking for.
I did that, but the missing file /usr/src/linuc-2.6.24.5/include/config/autoconf.h did not appear. I also ran "make prepare" as suggested in the error message but the file still is not there and the compile is unsuccessful.
Does someone have an idea how to get the
/usr/src/linuc-2.6.24.5/include/config/autoconf.h
file? It seems that this is the problem with the compilation of the driver. I made a fresh Slackware-12.1 install. Do you have this file on your systems?
Is it safe running "make oldconfig" and "make prepare"? I am not familiar with kernel compilation and would at least like to know whether running these two commands on my system has harmed something.
Yes, it safe -the commands just create the default configuration files. Be sure that you only run those commands -don't run 'make clean' or 'make distclean'. 'make distclean' will specifically destroy the two files that qc is looking for.
Thank you for your replies.
I got a little further. Actually the compilation errors are not due to the missing files in the message: in fact the files are in place. The problem comes from incompatibility of the driver with kernels 2.6.24:
I suspected ther might be a patch needed. I tried yesterday to find out a little more about the problem, but since I don't have video hardware and don't run kernel 2.5 it was a little hard to get definitive results.
The patches you linked to are for the full qc-usb-0.6.6 sources. I've modified them so that they apply cleanly to the qc-usc-messenger-1.7 sources.
I'll post the full content here since they are short. To apply them, simply unpack the sources normally and copy the patches into the toplevel directory of the sources. Then apply them with:
Gnashley,
Thank you really very much for your responsiveness. I applied the patches as you suggested but I got the same compilation errors afterwards:
/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.c:3484: error: unknown field 'hardware' specified in initializer
/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.c: In function 'qc_usb_init':
/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.c:3661: error: implicit declaration of function 'LONG'
/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.c:3661: warning: left shift count >= width of type
/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.c:3668: warning: ignoring return value of 'input_register_device', declared with attribute warn_unused_result
make[2]: *** [/home/marto/build/qc-usb/qc-usb-messenger-1.7/qc-driver.o] Error 1
make[1]: *** [_module_/home/marto/build/qc-usb/qc-usb-messenger-1.7] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.24.5'
make: *** [quickcam.ko] Error 2
Anyway, I found that the default quickcam driver that the generic kernel loads is actually quite good. The video image is of a comparable quality (if not even better) than that of the driver I was desperately trying to compile .
I have one more question to ask here. As I am a bit paranoiac about my system, I would like to know what exactly the succession of the following two commands does when issued in the /usr/src/linux-2.6.24.5 directory:
make oldconfig
make prepare
You said that this has made no harm, but I would like to know what modifications they have done to the stock 12.1 system. I can see that the folders include/ and .tmp-version/ and the files .missing-syscalls.d and .config have been modified when I issued the commands. Have other files in the system also been affected? Does this somehow affect the functionality of the system? Most of all I am interested whether it affects software that I compile. I could have installed afresh to make sure that everything is ok, but I think it is more valuable to learn something new than to just reinstall. I would be thankful if you also direct me to some relevant literature.
I am a new user here in this forum and i saw this old post, i know it is old and the owner did not answer if it worked or not, so i just want to share for other users that could have the same problem that i had the same problem and I solve it using the gspca driver the driver simonb1975uk said, to give details I am using debian lenny amd64 and a Logitech Express, I just execute the next command:
apt-get install gspca-modules-2.6.26-2-amd64
And everything work as magic.
My kernel is 2.6.26 I think I had the same problem but I found in the web site my webcam was supported by this driver so I give it a try and averithing work well. Maybe it work for you, another thing I installed from the repository came with my distro i download all the 6 DVD's.
I am using debian lenny amd64 and a Logitech Express, I just execute the next command:
apt-get install gspca-modules-2.6.26-2-amd64
The problem is that my webcam is not express, it Logitech Quickcam Messenger and is recognized as 046d:08f0. This particular kind of camera does not seem to be supported by the driver you mention, at least according to the documentation. Correct me if I am wrong.
The problem is that my webcam is not express, it Logitech Quickcam Messenger and is recognized as 046d:08f0. This particular kind of camera does not seem to be supported by the driver you mention, at least according to the documentation. Correct me if I am wrong.
And have you try it lately?, some time ago this driver did not work for me, but i just try two days ago and i found my camera supported by this driver
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.