Date: Wed, 16 Dec 2015 19:54:10 +0000 (UTC) From: Kostya Berger <bergerkos@yahoo.co.uk> To: Allan Jude <allanjude@freebsd.org>, Freebsd-current <freebsd-current@freebsd.org> Subject: Re: webcamd & cuse4bsd Message-ID: <1187331091.3652142.1450295650956.JavaMail.yahoo@mail.yahoo.com> In-Reply-To: <232365240.2892263.1450218301239.JavaMail.yahoo@mail.yahoo.com> References: <56707005.3060403@freebsd.org> <232365240.2892263.1450218301239.JavaMail.yahoo@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, this seems to be either hardware or software (driver code) bug. After `usbconfig -d ugen1.4 reset` webcamd restarting sometimes creates the= device /dev/video0 -- sometimes,, but not every time. More often than not = it doesn't. So there's no method seen in this behaviour so far. I wonder ho= w I could debug this. Sent from Yahoo Mail on Android=20 =20 On Wed, Dec 16, 2015 at 1:22, Kostya Berger<bergerkos@yahoo.co.uk> wrote:= Ok, I failed to make it clear enough: the module is loaded on boot.=C2= =A0This was what was actually meant by the expression "when the system star= ts". By contrast, loading on demand is... well, loading "on demand". These = are two ways of starting a program, "on demand", as opposite to "when the s= ystem starts". Please, correct me if I'm wrong here.Yet the situation is as= I described. That's what I'm actually reporting. Just now I've done a rebo= ot, and here we go again: all modules loaded, /dev/cuse persent, the messag= e telling me "webcam is already running on ugen1.4.0" (my web-camera) -- an= d NO /dev/video0. Though it hits me now, there are 3 devices /dev/usb/1.4.*. Maybe 1.4.0 is n= ot the correct one? Sent from Yahoo Mail on Android=20 =20 On Tue, Dec 15, 2015 at 23:54, Allan Jude<allanjude@freebsd.org> wrote: = On 2015-12-15 14:13, Kostya Berger wrote: > You misread my message, sorry. I said the devices are not created EVERY > TIME the system starts. Rather, it becomes A MATTER OF CHANCE. That is, > sometimes they are, sometimes they aren't. > (with the modules not loaded it would be stable NO) >=20 >=20 > Sent from Yahoo Mail on Android > <https://overview.mail.yahoo.com/mobile/?.src=3DAndroid>; >=20 >=C2=A0 =C2=A0 On Tue, Dec 15, 2015 at 23:01, Allan Jude >=C2=A0 =C2=A0 <allanjude@freebsd.org> wrote: >=20 >=C2=A0 =C2=A0 On 2015-12-15 13:37, Kostya Berger wrote: >=20 >=C2=A0 =C2=A0 > There is this problem I'm experiencing with webcamd (set t= o >=C2=A0 =C2=A0 webcamd_enable=3DYES) and cuse4bsd: special devices /dev/vid= eo0 and >=C2=A0 =C2=A0 /dev/cuse are NOT cteated every time on system start. Rather= , it >=C2=A0 =C2=A0 becomes a matter of chance.Have the same problem on RELEASE = & STABLE >=C2=A0 =C2=A0 as well. >=C2=A0 =C2=A0 > >=C2=A0 =C2=A0 > Sent from Yahoo Mail on Android >=C2=A0 =C2=A0 > _______________________________________________ >=C2=A0 =C2=A0 > freebsd-current@freebsd.org <javascript:return> mailing li= st >=C2=A0 =C2=A0 > https://lists.freebsd.org/mailman/listinfo/freebsd-current >=C2=A0 =C2=A0 > To unsubscribe, send any mail to >=C2=A0 =C2=A0 "freebsd-current-unsubscribe@freebsd.org <javascript:return> >=C2=A0 =C2=A0 " >=C2=A0 =C2=A0 > >=20 >=C2=A0 =C2=A0 In /boot/loader.conf try adding: >=20 >=C2=A0 =C2=A0 cuse_load=3D"YES" >=20 >=C2=A0 =C2=A0 this will load the module, and should ensure the devices are= available >=C2=A0 =C2=A0 before webcamd starts. >=20 >=C2=A0 =C2=A0 --=20 >=C2=A0 =C2=A0 Allan Jude >=20 The module is loaded 'on demand', but obviously something it not loading it on-demand when you want it. Forcing it to always be loaded, should solve your problem. --=20 Allan Jude =20 =20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1187331091.3652142.1450295650956.JavaMail.yahoo>