* [gentoo-user] kernel 2.6.9r9 v4l missing
@ 2004-12-05 15:10 J. Patrick Campbell
2004-12-05 15:29 ` Holly Bostick
0 siblings, 1 reply; 3+ messages in thread
From: J. Patrick Campbell @ 2004-12-05 15:10 UTC (permalink / raw
To: gentoo-user
i'm on udev and have compiled in support for my webcam and video for linux
yet my /dev/v4l and /dev/video0 are missing.
sorry if someone already answered, my router locked up overnight so i've
been bouncing email.
how do i create devices with udev? didn't see anything on the gentoo udev
guide.
Thanks,
~P
--
http://patrickcampbell.us
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] kernel 2.6.9r9 v4l missing
2004-12-05 15:10 [gentoo-user] kernel 2.6.9r9 v4l missing J. Patrick Campbell
@ 2004-12-05 15:29 ` Holly Bostick
2004-12-05 15:45 ` J. Patrick Campbell
0 siblings, 1 reply; 3+ messages in thread
From: Holly Bostick @ 2004-12-05 15:29 UTC (permalink / raw
To: gentoo-user
J. Patrick Campbell wrote:
> i'm on udev and have compiled in support for my webcam and video for linux
> yet my /dev/v4l and /dev/video0 are missing.
> sorry if someone already answered, my router locked up overnight so i've
> been bouncing email.
> how do i create devices with udev? didn't see anything on the gentoo udev
> guide.
>
> Thanks,
>
> ~P
Inexpert suggestion; corrections gratefully accepted:
Udev creates devices on the fly. This means that it creates the devices
when something calls for them to be created.
The easiest way I find to create devices like this (devices which will
be used later, but are not "called" by anything during boot) is to make
the drivers for such devices modular rather than compiling them directly
in, and then adding them to /etc/modules.autoload.d/kernel-2.6; that
way, when the module loads, the device is created. This is how I get my
Sidewinder gamepad to work (creating the device /dev/js0), for example--
if I compile support directly into the kernel, udev isn't running when
the driver is loaded, because the device is detected during an earlier
stage of the boot process, so no device is created. I suppose I could
create a device in the udev config, but I have no interest in that,
since it's not a "special device that udev doesn't know about" (which is
the situation in which you are supposed to specifically configure udev
to create a device). It's supposed to do it automatically; this way, it
does.
I would suggest that you modularize your video devices as well.
Hope this helps.
Holly
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [gentoo-user] kernel 2.6.9r9 v4l missing
2004-12-05 15:29 ` Holly Bostick
@ 2004-12-05 15:45 ` J. Patrick Campbell
0 siblings, 0 replies; 3+ messages in thread
From: J. Patrick Campbell @ 2004-12-05 15:45 UTC (permalink / raw
To: gentoo-user
On Sun, December 5, 2004 10:29 am, Holly Bostick said:
> J. Patrick Campbell wrote:
>> i'm on udev and have compiled in support for my webcam and video for
>> linux
>> yet my /dev/v4l and /dev/video0 are missing.
>> sorry if someone already answered, my router locked up overnight so i've
>> been bouncing email.
>> how do i create devices with udev? didn't see anything on the gentoo
>> udev
>> guide.
>>
>> Thanks,
>>
>> ~P
>
> Inexpert suggestion; corrections gratefully accepted:
>
> Udev creates devices on the fly. This means that it creates the devices
> when something calls for them to be created.
>
> The easiest way I find to create devices like this (devices which will
> be used later, but are not "called" by anything during boot) is to make
> the drivers for such devices modular rather than compiling them directly
> in, and then adding them to /etc/modules.autoload.d/kernel-2.6; that
> way, when the module loads, the device is created. This is how I get my
> Sidewinder gamepad to work (creating the device /dev/js0), for example--
> if I compile support directly into the kernel, udev isn't running when
> the driver is loaded, because the device is detected during an earlier
> stage of the boot process, so no device is created. I suppose I could
> create a device in the udev config, but I have no interest in that,
> since it's not a "special device that udev doesn't know about" (which is
> the situation in which you are supposed to specifically configure udev
> to create a device). It's supposed to do it automatically; this way, it
> does.
>
> I would suggest that you modularize your video devices as well.
>
> Hope this helps.
> Holly
>
> --
Holly,
Thanks for you reply.
I don't know what'sup with my kernel 2.6.9r9 but i just recompiled 2.6.9r4
and all is working great. Cam is working again.
The only problem i see is i got a clock skew error message when compiling
the newer kernel so i wonder if that messed things up? Although make
menuconfig showed the ibm cam drivers loaded, when i zcat /proc/config.gz
it showed the driver not being there. So i'm sticking with the older
kernel for now.
Thanks,
~P
> gentoo-user@gentoo.org mailing list
>
>
--
http://patrickcampbell.us
--
gentoo-user@gentoo.org mailing list
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-12-05 15:46 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-05 15:10 [gentoo-user] kernel 2.6.9r9 v4l missing J. Patrick Campbell
2004-12-05 15:29 ` Holly Bostick
2004-12-05 15:45 ` J. Patrick Campbell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox