View previous topic :: View next topic |
Author |
Message |
ddave n00b
Joined: 24 Dec 2003 Posts: 9
|
Posted: Wed Dec 24, 2003 11:55 pm Post subject: V4L inclusion |
|
|
Hey, I was just wondering a few things.
1. How can I check whether or not I have V4L support in my kernel? (2.4.20-gentoo-r6).
2. I'm pretty sure I don't have it, so if i don't, what would be the best way to add it? I'm a newbie :s
I used "genkernel", no options, to build the kernel (I started from stage 3). Is there any way to add V4L support without having to recompile the kernel?
If there isn't, will it take the same amount of time as my "genkernel" did? (a tad longer for V4L of course). I just don't want to have to start from an earlier stage or something and it take me significantly longer than it did when I first built it.
By the way, I want it to use a logitech quickcam express USB.
I'de appreciate any input, thanks |
|
Back to top |
|
|
Angrybob Guru
Joined: 19 Apr 2003 Posts: 575
|
Posted: Thu Dec 25, 2003 12:53 am Post subject: |
|
|
run the following command (no need to be root)
Code: |
grep V4L /usr/src/linux/.config
|
this shows all config lines that contain V4L. One of them should look like CONFIG_V4L=y or CONFIG_V4L_something=y
If there is a "y" or "m" after that then V4L is compiled into the kernel (or as a module for "m") |
|
Back to top |
|
|
ddave n00b
Joined: 24 Dec 2003 Posts: 9
|
Posted: Thu Dec 25, 2003 12:59 am Post subject: |
|
|
That's a no-go. It just comes up with nothing at all.
So what will it take to get V4L support? I know probably recompiling the kernel, but i'm a bit fuzzy on that. Can I just boot from the cd, and start from "genkernel" again, but ad "--config" and enable V4L support through there? If that's possible it may only take 5 hours to compile instead of many more from a stage 1 etc. :s |
|
Back to top |
|
|
Jerri Guru
Joined: 03 Apr 2003 Posts: 353
|
Posted: Thu Dec 25, 2003 4:30 am Post subject: |
|
|
Perhaps its time you learn how to compile your own kernel. I'll give you a brief summary of how to work things, but its up to you to reviews the docs.
To start off, I made a little script to automate kernel compilation (very simple):
Code: | #!/bin/bash
make clean
make menuconfig
make dep
make bzImage
make modules
make modules_install
|
save this file as /usr/src/linux/kernel-auto
run it with the command (as root) sh kernel-auto
This will bring up a menu to configure your own kernel. To make things easy, we will use your config file that genkernel provided. Go to "Load an Alternate Configuration File" and type in /usr/src/linux/.config. If we compiled it at this stage, it would compile an exact replica of the kernel you are now running. To add support for V4L, go to
Multimedia devices ---> Video For Linux. You can include it in your kernel, or load it as a module. If you select it as a module (M) then you have to add "videodev" (without quotations) to modules.autoload (probably found under /etc/modules.autoload.d/kernel-2.4).
Once you have finished any modifications to your new kernel, save the new config, then exit menuconfig. The script will take care of actually compiling your kernel and modules. Once it has completed, you will have to mount your /boot partition (if you followed gentoo's install guide) and copy your new kernel there.
Your new kernel is found here:
/usr/src/linux/arch/i386/boot/bzImage
After copying, remember to run lilo -v (only if you are running lilo as your boot manager)
Now reboot.
Hopefully this helps to get the ball rolling
good luck. |
|
Back to top |
|
|
Angrybob Guru
Joined: 19 Apr 2003 Posts: 575
|
Posted: Thu Dec 25, 2003 1:12 pm Post subject: |
|
|
Jerri wrote: | Go to "Load an Alternate Configuration File" and type in /usr/src/linux/.config |
if you're compiling the kernel in /usr/src/linux then there's no need for that since it will automatically load that file |
|
Back to top |
|
|
Jerri Guru
Joined: 03 Apr 2003 Posts: 353
|
Posted: Thu Dec 25, 2003 8:16 pm Post subject: |
|
|
Quite right. Perhaps I should have mentioned that its always a good Idea to save your new kernel config to a different file. If you decide to recompile a new kernel (one that is atleast stable) you can start with a working config, just sub .config with your saved config file. |
|
Back to top |
|
|
teknomage1 Veteran
Joined: 05 Aug 2003 Posts: 1239 Location: Los Angeles, CA
|
Posted: Thu Dec 25, 2003 8:18 pm Post subject: |
|
|
If all you need is the v4l modules you can probably get away with just turning on v4l and running make modules and make modules_install. that's why modules were invented after all |
|
Back to top |
|
|
ddave n00b
Joined: 24 Dec 2003 Posts: 9
|
Posted: Fri Dec 26, 2003 2:19 am Post subject: |
|
|
Thanks for your help everyone.
I've recompiled and added V4L as modules. insmod works well, and ./quickcam.sh comes up with a few "module already exists" etc. but seems to load correctly. The problem i'm having now is that I've downloaded videograb for use for it, but I have no /dev/video* files that I can point it to.
I also checked dmesg, and several times it comes up with:
usb.c: USB device not responding, giving up (error=71)
This is a second-hand camera. I'm starting to think the camera is just rooted. |
|
Back to top |
|
|
ddave n00b
Joined: 24 Dec 2003 Posts: 9
|
Posted: Fri Dec 26, 2003 2:51 am Post subject: |
|
|
Ok my dad has told me that he saw it work before he got given it, so it's not broken. I'm sorry for being persistant about this, but it's one of those things that i just HAVE to get working, for the sake of beating this thing.
Here's the situation:
I have no /dev/video, no /dev/video0, and no V4L entries anywhere.
/proc/video/quickcam exists as a directory.
What I have in "lsmod" is this:
Code: |
serial (autoclean)
isa_pnp (autoclean) [serial]
mod_quickcam
videodev [mod_quickcam]
uhci (unused)
usb-ohci (unused)
usbcore [mod_quickcam uhci usb-ohci
via-rhine
|
doing cat /proc/bus/usb/devices comes up with two "products":
Code: |
S: Product=USB UHCI-alt Root Hub
...
S: Product=USB OHCI Root Hub
|
Any ideas? |
|
Back to top |
|
|
|