Re: webcamd not started automatically
On 2/18/21 4:49 PM, Steve Wills wrote: Hi, On 2/18/21 9:14 AM, Jakob Alvermark wrote: It used to start webcamd for both of them, now it is only started for the built in Chicony. I have a similar problem. I have 3 cameras (one Logitech and two USB UVD things) and now it only starts webcamd for one. I can start it manually for the other two. I don't have the details now, but it seemed like when I started it for the second or third device, it said it was already running until I tried again. Yes, there is something going on when you try to start multiple instances. My cameras are at ugen1.7 and ugen2.4 # service webcamd start ugen1.7 webcamd 4778 - - Attached to ugen1.7[0] # service webcamd start ugen2.4 webcamd already running? (pid=4779). # service webcamd stop Stopping webcamd. Waiting for PIDs: 4779 # service webcamd start ugen2.4 webcamd 4830 - - Attached to ugen2.4[0] # service webcamd start ugen1.7 webcamd already running? (pid=4831). # ls /var/run/webcamd.* /var/run/webcamd.1.7.0.pid /var/run/webcamd.2.4.0.pid # cat /var/run/webcamd.1.7.0.pid 4778 # cat /var/run/webcamd.2.4.0.pid 4830 Jakob ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: webcamd not started automatically
Hi, On 2/18/21 9:14 AM, Jakob Alvermark wrote: It used to start webcamd for both of them, now it is only started for the built in Chicony. I have a similar problem. I have 3 cameras (one Logitech and two USB UVD things) and now it only starts webcamd for one. I can start it manually for the other two. I don't have the details now, but it seemed like when I started it for the second or third device, it said it was already running until I tried again. Thanks, Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: webcamd not started automatically
On 2/18/21 3:14 PM, Jakob Alvermark wrote: It used to start webcamd for both of them, now it is only started for the built in Chicony. Can you share your configuration? Any errors printed in dmesg? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: webcamd not started automatically
On 2/18/21 3:09 PM, Hans Petter Selasky wrote: On 2/18/21 3:04 PM, Jakob Alvermark wrote: Hi, Webcamd is not started automatically for my Logitech webcam as it used to do. Starting it from the command line works fine. It works for the built in webcam on the ThinkPad, (Chicony) The change happened somewhere between n244736-dba7b0ef928 and n244835-c31480a1f66 Hi, What is your configuration? webcamd_enable="YES" in rc.conf Yes. Did you update the webcamd package to be w/o hal support? Yes. I have two cameras, the built in Chicony and the externa Logitech. It used to start webcamd for both of them, now it is only started for the built in Chicony. Jakob ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: webcamd not started automatically
On 2/18/21 3:04 PM, Jakob Alvermark wrote: Hi, Webcamd is not started automatically for my Logitech webcam as it used to do. Starting it from the command line works fine. It works for the built in webcam on the ThinkPad, (Chicony) The change happened somewhere between n244736-dba7b0ef928 and n244835-c31480a1f66 Hi, What is your configuration? webcamd_enable="YES" in rc.conf Did you update the webcamd package to be w/o hal support? --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
webcamd not started automatically
Hi, Webcamd is not started automatically for my Logitech webcam as it used to do. Starting it from the command line works fine. It works for the built in webcam on the ThinkPad, (Chicony) The change happened somewhere between n244736-dba7b0ef928 and n244835-c31480a1f66 Thanks, Jakob ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel: don't know how to make cleandir in drm-current-kmod
On 2021-02-18 09:41, Ruslan Makhmatkhanov wrote: Niclas Zeising wrote on 2/18/21 9:55 AM: On 2021-02-18 06:32, Ruslan Makhmatkhanov wrote: Hello, trying to build kernel from commit f61e92ca5a23450bc28169bbdd71d7674df98c19 (HEAD -> main, origin/main, origin/HEAD) Author: Glen Barber Date: Wed Feb 17 23:00:03 2021 -0500 world built ok, but then I have this on make kernel: ===> zlib (cleandir) rm -f export_syms machine x86 zlib.ko zlib.kld zcalloc.o zlib_mod.o adler32.o compress.o crc32.o deflate.o inffast.o inflate.o inftrees.o trees.o uncompr.o zutil.o offset.inc genoffset.o rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS ===> drm-current-kmod (cleandir) make[3]: don't know how to make cleandir. Stop make[3]: stopped in /usr/local/sys/modules/drm-current-kmod *** Error code 2 Stop. make[2]: stopped in /usr/obj/mnt/hdd/src/amd64.amd64/sys/Z1 *** Error code 1 Stop. make[1]: stopped in /mnt/hdd/src *** Error code 1 Stop. make: stopped in /mnt/hdd/src Tried to reinstall drm-current-kmod to not avail. Can you check that you have the folder /usr/local/sys/modules/drm-current-kmod, and that there are sources inside? drm-current-kmod no longer installs sources by default, please check if you have enabled that option locally. Regards That's what was installed by the package from official repo. Now I built it locally with making sure SOURCE option is enabled and kernel now builds. Thanks. So, was it some temporary decision to exclude sources from the package by default, or since now I should manually build drm-kmod package at every update? We disabled the source option because it caused too much issues. It catches people by surprise sometimes when the drm-kmod modules are rebuilt automatically with the kernel, even when they are not in /usr/src. The biggest problem though is that the general workflow often is to rebuild the world, then the kernel, then update ports. This means that the drm-kmod srources won't be updated before the kernel is built, causing build failures (if you need an updated drm-kmod because of changes in the kernel). Generally, the recommended way is to first buildworld/buildkernel, install the new kernel, remove the old drm-current-kmod before booting the new kernel, and then rebuild drm-current-kmod from ports with the new kernel. Regards -- Niclas ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: buildkernel: don't know how to make cleandir in drm-current-kmod
Niclas Zeising wrote on 2/18/21 9:55 AM: On 2021-02-18 06:32, Ruslan Makhmatkhanov wrote: Hello, trying to build kernel from commit f61e92ca5a23450bc28169bbdd71d7674df98c19 (HEAD -> main, origin/main, origin/HEAD) Author: Glen Barber Date: Wed Feb 17 23:00:03 2021 -0500 world built ok, but then I have this on make kernel: ===> zlib (cleandir) rm -f export_syms machine x86 zlib.ko zlib.kld zcalloc.o zlib_mod.o adler32.o compress.o crc32.o deflate.o inffast.o inflate.o inftrees.o trees.o uncompr.o zutil.o offset.inc genoffset.o rm -f machine x86 .depend .depend.* GPATH GRTAGS GSYMS GTAGS ===> drm-current-kmod (cleandir) make[3]: don't know how to make cleandir. Stop make[3]: stopped in /usr/local/sys/modules/drm-current-kmod *** Error code 2 Stop. make[2]: stopped in /usr/obj/mnt/hdd/src/amd64.amd64/sys/Z1 *** Error code 1 Stop. make[1]: stopped in /mnt/hdd/src *** Error code 1 Stop. make: stopped in /mnt/hdd/src Tried to reinstall drm-current-kmod to not avail. Can you check that you have the folder /usr/local/sys/modules/drm-current-kmod, and that there are sources inside? drm-current-kmod no longer installs sources by default, please check if you have enabled that option locally. Regards There was something in there: rm@cf:/usr/local> ls -R /usr/local/sys/modules/drm-current-kmod linuxkpi /usr/local/sys/modules/drm-current-kmod/linuxkpi: gplv2 /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2: include src /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include: asm linux /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/asm: fpu /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/asm/fpu: api.h /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/include/linux: llist.h shrinker.h /usr/local/sys/modules/drm-current-kmod/linuxkpi/gplv2/src: linux_llist.c That's what was installed by the package from official repo. Now I built it locally with making sure SOURCE option is enabled and kernel now builds. Thanks. So, was it some temporary decision to exclude sources from the package by default, or since now I should manually build drm-kmod package at every update? -- Regards, Ruslan T.O.S. Of Reality ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
