#262198669 Re: base64.h problems with rtorent port

​​Мы работаем над вашим запросом. Нам понадобилось чуть больше времени, чтобы решить ваш вопрос #262198669. Еще 24 часа, и мы постараемся к вам вернуться. Приносим извинения за неудобства. Пожалуйста, не отвечайте на это письмо, так как оно сформировано автоматически. Sincerely, Mokka Supp

#262198816 base64.h problems with rtorent port

​​Мы работаем над вашим запросом. Нам понадобилось чуть больше времени, чтобы решить ваш вопрос #262198816. Еще 24 часа, и мы постараемся к вам вернуться. Приносим извинения за неудобства. Пожалуйста, не отвечайте на это письмо, так как оно сформировано автоматически. Sincerely, Mokka Supp

#262198104 Re: base64.h problems with rtorent port

​​Мы работаем над вашим запросом. Нам понадобилось чуть больше времени, чтобы решить ваш вопрос #262198104. Еще 24 часа, и мы постараемся к вам вернуться. Приносим извинения за неудобства. Пожалуйста, не отвечайте на это письмо, так как оно сформировано автоматически. Sincerely, Mokka Supp

Re: base64.h problems with rtorent port

Nice! I will do that, `--with-xmlrpc-tinyxml2` directly on port config ala linux distros. Thanks! Baptiste Daroussin escreveu (sexta, 27/12/2024 à(s) 14:54): > On Fri 27 Dec 14:24, Nuno Teixeira wrote: > > Perfect! > > > > I'm thinking using a radio option where we can select one of xml parsers

Re: base64.h problems with rtorent port

On Fri 27 Dec 14:24, Nuno Teixeira wrote: > Perfect! > > I'm thinking using a radio option where we can select one of xml parsers or > none as supported upstream, defaulting to TINYXML. > > A quick look in repology shows that at least 3 linux distros use directly > `--with-xmlrpc-tinyxml2` with 0

Re: base64.h problems with rtorent port

Perfect! I'm thinking using a radio option where we can select one of xml parsers or none as supported upstream, defaulting to TINYXML. A quick look in repology shows that at least 3 linux distros use directly `--with-xmlrpc-tinyxml2` with 0.15.0 pkgs. I'm ok with simplifying port or keep radio o

Re: base64.h problems with rtorent port

On Fri 27 Dec 12:48, Nuno Teixeira wrote: > Hello Baptiste, > > Yes, this proves that my C skills are awesome :) > > Upstream spotted it too, and in fact, base64.h is missing from tarball. > Now I'm waiting on upstream to find the best and fast way to include > missing file so I can test build. >

Re: base64.h problems with rtorent port

Hello Baptiste, Yes, this proves that my C skills are awesome :) Upstream spotted it too, and in fact, base64.h is missing from tarball. Now I'm waiting on upstream to find the best and fast way to include missing file so I can test build. Thanks very much, Baptiste Daroussin escreveu (sexta,

Re: base64.h problems with rtorent port

27 décembre 2024 à 13:13 "Nuno Teixeira" mailto:edua...@freebsd.org?to=%22Nuno%20Teixeira%22%20%3Ceduardo%40freebsd.org%3E > a écrit: > > Hello, > > Looking for help to figure out a base64.h and tinyxml2: > https://github.com/rakshasa/rtorrent/issues/1353 > > Any help is welcome, thanks > >

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 09/10/2024 07:35, Paul Floyd wrote: … ld-elf.so.1: Shared object "libmd.so.6" not found, … pkgbase context: |

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 10-10-24 11:16, Konstantin Belousov wrote: If you can determine not just the number of taken locks, but also the specific locks that were taken, perhaps you can check that this is the libc exit lock? For the moment I've turned off the check for FreeBSD 15 and above. At present the ExeCo

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 07:34:31PM +, Paul Floyd wrote: > > > On 09-10-24 08:50, Konstantin Belousov wrote: > > > Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the > > backtrace to determine the situation. > > We don't read .gnu.version and the version number hasn't

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On 09-10-24 08:50, Konstantin Belousov wrote: Perhaps you can check for the presence of the symbol exit@FBSD_1.0 in the backtrace to determine the situation. We don't read .gnu.version and the version number hasn't changed as far as I can see. I can check osreldate to get an idea of the

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 10:27:22AM +0200, Paul Floyd wrote: > > > > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov > > wrote: > > > On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > > > The biggest problem is with Helgrind. All apps now generate an extra > > error > > > > > > ==68593

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

> > > I can probably check whether it's the main thread (I assume that this code > doesn't run on subsidiary threads) > No it looks like it can be any thread. A+ Paul

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

> > On Wed, 9 Oct 2024 at 09:08, Konstantin Belousov > wrote: > On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > > The biggest problem is with Helgrind. All apps now generate an extra > error > > > > ==68593== Thread #1: Exiting thread still holds 1 lock > > ==68593==at 0x4BBB5DA:

Re: Problems with FreeBSD-15.0-CURRENT-amd64-20241003

On Wed, Oct 09, 2024 at 06:35:08AM +, Paul Floyd wrote: > Hi > > I don't often update my 15-0-CURRENT VM. I did last week and I'm getting > several issues. > > Firstly, a bit annoying, both pkg and ksh93 fail to run, giving. > ld-elf.so.1: Shared object "libmd.so.6" not found, required by "ks

Problems with FreeBSD-15.0-CURRENT-amd64-20241003

Hi I don't often update my 15-0-CURRENT VM. I did last week and I'm getting several issues. Firstly, a bit annoying, both pkg and ksh93 fail to run, giving. ld-elf.so.1: Shared object "libmd.so.6" not found, required by "ksh93" Next I'm getting a lot of new Valgrind test failures. I haven't d

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > Please see/test: https://github.com/openzfs/zfs/pull/15732 . Looks like that has landed in current: commit f552d7adebb13e24f65276a6c4822bffeeac3993 Merge: 13720136fbf a382e21194c Author: Martin Matuska

Re: ZFS problems since recently ?

John, On 04.01.2024 09:20, John Kennedy wrote: On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote: On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: On 01.01.2024 08:59, John Kennedy wrote: ... My poudriere build did eventually fail as well: ...

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 08:02:04PM -0800, John Kennedy wrote: > On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > > On 01.01.2024 08:59, John Kennedy wrote: > > > ... > > >My poudriere build did eventually fail as well: > > > ... > > > [05:40:24] [01] [00:17:20] Finished d

Re: ZFS problems since recently ?

On Tue, Jan 02, 2024 at 05:51:32PM -0500, Alexander Motin wrote: > On 01.01.2024 08:59, John Kennedy wrote: > > ... > >My poudriere build did eventually fail as well: > > ... > > [05:40:24] [01] [00:17:20] Finished devel/gdb@py39 | gdb-13.2_1: Success > > [05:40:24] Stopping 2 buil

Re: ZFS problems since recently ?

On 01.01.2024 08:59, John Kennedy wrote: On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: markj@ pointed me in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 to https://github.com/openzfs/zfs/pull/15719 So it will probably be fixed sooner or later. The other ZFS crashes I

Re: ZFS problems since recently ?

Am 2024-01-02 08:22, schrieb Kurt Jaeger: Hi! The sysctl for block cloning is vfs.zfs.bclone_enabled. To check if a pool has made use of block cloning: zpool get all poolname | grep bclone One more thing: I have two pools on that box, and one of them has some bclone files: # zpool get a

Re: ZFS problems since recently ?

Hi! > The sysctl for block cloning is vfs.zfs.bclone_enabled. > To check if a pool has made use of block cloning: > zpool get all poolname | grep bclone One more thing: I have two pools on that box, and one of them has some bclone files: # zpool get all ref | grep bclone ref bcloneused

Re: ZFS problems since recently ?

Hi! > Am 2023-12-31 19:34, schrieb Kurt Jaeger: > > I already have > > > > vfs.zfs.dmu_offset_next_sync=0 > > > > which is supposed to disable block-cloning. > > It isn't. This one is supposed to fix an issue which is unrelated to block > cloning (but can be amplified by block cloning). This is

Re: ZFS problems since recently ?

Am 2023-12-31 19:34, schrieb Kurt Jaeger: I already have vfs.zfs.dmu_offset_next_sync=0 which is supposed to disable block-cloning. It isn't. This one is supposed to fix an issue which is unrelated to block cloning (but can be amplified by block cloning). This issue is fixed since some week

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > markj@ pointed me in > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > > > to > > > https://github.com/openzfs/zfs/pull/15719 > > > > > > So it will p

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 08:42:26AM -0800, John Kennedy wrote: > Applying the two ZFS kernel patches fixes that issue: commit 09af4bf2c987f6f57804162cef8aeee05575ad1d (zfs: Fix SPA sysctl handlers) landed too. root@bsd15:~ # sysctl -a | grep vfs.zfs.zio vfs.zfs.zio.deadman_log_a

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > > I can crash mine with "sysctl -a" as well. > > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later. >

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 02:27:17PM +0100, Kurt Jaeger wrote: > Do you have >vfs.zfs.dmu_offset_next_sync=0 I didn't initially, I do now. Like I said, I haven't been following that one 100%. I know it isn't block-clone per say, so much as some underlying problem it pokes with a pointy s

Re: ZFS problems since recently ?

Hi! > On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > > markj@ pointed me in > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > > to > > https://github.com/openzfs/zfs/pull/15719 > > > > So it will probably be fixed sooner or later. > > > > The other ZFS crashes I've

Re: ZFS problems since recently ?

On Mon, Jan 01, 2024 at 06:43:58AM +0100, Kurt Jaeger wrote: > markj@ pointed me in > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 > to > https://github.com/openzfs/zfs/pull/15719 > > So it will probably be fixed sooner or later. > > The other ZFS crashes I've seen are still an issue

Re: ZFS problems since recently ?

Hi! > > I can crash mine with "sysctl -a" as well. markj@ pointed me in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=276039 to https://github.com/openzfs/zfs/pull/15719 So it will probably be fixed sooner or later. The other ZFS crashes I've seen are still an issue. -- p...@freebsd.or

Re: ZFS problems since recently ?

> I can crash mine with "sysctl -a" as well. Smaller test, this is sufficient to crash things: root@bsd15:~ # sysctl vfs.zfs.zio vfs.zfs.zio.deadman_log_all: 0 vfs.zfs.zio.dva_throttle_enabled: 1 vfs.zfs.ziopanic: sbuf_clear makes no sense on sbuf 0xf8002c8

Re: ZFS problems since recently ?

On Sun, Dec 31, 2023 at 07:34:45PM +0100, Kurt Jaeger wrote: > Hi! > > Short overview: > - Had CURRENT system from around September > - Upgrade on the 23th of December > - crashes in ZFS, see > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 > for details > - Reinstalled from scratch

ZFS problems since recently ?

Hi! Short overview: - Had CURRENT system from around September - Upgrade on the 23th of December - crashes in ZFS, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261538 for details - Reinstalled from scratch with new SSDs drives from https://download.freebsd.org/snapshots/amd64/amd64/IS

/var/db/etcupdate/ in hier(7) (was: user problems when upgrading to v15)

On 09/09/2023 17:02, John Baldwin wrote: On 9/2/23 7:11 AM, Dimitry Andric wrote: … … /var/db/etcupdate/conflicts, … Shall I make a simple (non-contentious) pull request for hier(7) to include /var/db/etcupdate/ and the conflicts/ subdirectory? /var/db/etcupdate/ is present by default wi

Re: user problems when upgrading to v15

type exit in single user mode to go multi user mode, the local user still works. After a reboot the local user still works. This local user can also sudo as expected. This wasn't the case for the previous build when I first reported this. However, if I run etcupdate resolve it is still pre

Re: user problems when upgrading to v15

ates perhaps. If I type exit in single user mode to go multi user mode, the local user still works. After a reboot the local user still works. This local user can also sudo as expected. This wasn't the case for the previous build when I first reported this. However, if I run etcupdate resol

Re: user problems when upgrading to v15

de, the local user > still works. After a reboot the local user still works. This local user can > also sudo as expected. This wasn't the case for the previous build when I > first reported this. However, if I run etcupdate resolve it is still > presenting /etc/group and /etc/mas

Re: user problems when upgrading to v15

master/passwd as problems. If this is is expected behavior for current then no big deal. I just wasn't sure. Brian On 8/30/2023 7:35 PM, Graham Perrin wrote: On 31/08/2023 03:31, brian whalen wrote: Understood. I guess I was expecting the update process of etcupdate -p && make in

Re: user problems when upgrading to v15

On 31/08/2023 03:31, brian whalen wrote: Understood. I guess I was expecting the update process of etcupdate -p && make installworld && etcupdate -B to not whack existing users or delete an existing root user's password. I accepted the remote and then recreated users and reset passwords and am

Re: user problems when upgrading to v15

Understood. I guess I was expecting the update process of etcupdate -p && make installworld && etcupdate -B to not whack existing users or delete an existing root user's password. I accepted the remote and then recreated users and reset passwords and am retrying this. BW On 8/30/2023 7:21 PM,

Re: user problems when upgrading to v15

On 31/08/2023 03:00, brian whalen wrote: … I ran etcupdate resolve accepting the remote option and saw 2 issues. The root user's password was deleted. The non root user no longer existed. Logically, remote does not include things such as your root user's password.

Re: pkg problems with v15

On 31/08/2023 02:59, brian whalen wrote: … pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz: Not Found … For 15.0-CURRENT you should use latest; don't expect quarterly. Also, it's probably too soon for latest. 1.

Re: user problems when upgrading to v15

I have seen this twice. Once when going from 13.2 to current 14.0 alpha1 and then to 15, and a 2nd time when going from 13.2 to 15. I have a user that is a member of the wheel group. After I upgraded and ran the post reboot commands in single user mode I was alerted to merge conflicts. I ran e

pkg problems with v15

root@f15:~ # pkg update pkg: Warning: Major OS version upgrade detected.  Running "pkg bootstrap -f" recommended Updating FreeBSD repository catalogue... pkg: http://pkgmir.geo.freebsd.org/FreeBSD:15:amd64/quarterly/meta.txz: Not Found repository FreeBSD has no meta file, using default setting

Re: ps(1) bugs and problems

On 2023-08-15 13:28:07, Jamie Landeg-Jones wrote: The old -d and the new -D'$^' would be the best in that -d would go back to what it was and -D would provide the much needed feature in two variants (possibly more in the future, if needed) while only taking one option-letter. The only problem is

Re: ps(1) bugs and problems

"Piotr P. Stefaniak" wrote: > On 2023-08-11 12:32:02, Jamie Landeg-Jones wrote: > >How about reverting '-d', and adding "-D" for descending, and "-A" for > >ascending? > > I don't like that, because it would take three option-letters in total > to implement the same function in different variant

Re: ps(1) bugs and problems

On 2023-08-11 12:32:02, Jamie Landeg-Jones wrote: How about reverting '-d', and adding "-D" for descending, and "-A" for ascending? I don't like that, because it would take three option-letters in total to implement the same function in different variants. The old -d and the new -D'$^' would

Re: ps(1) bugs and problems

"Piotr P. Stefaniak" wrote: > I thought about this more and the change I proposed in > https://reviews.freebsd.org/D41231 seems unnecessarily complicated, > regardless of which characters will be chosen to denote going up and > down the process tree. ps -D'^$' suggests there are possibly more > c

Re: ps(1) bugs and problems

I thought about this more and the change I proposed in https://reviews.freebsd.org/D41231 seems unnecessarily complicated, regardless of which characters will be chosen to denote going up and down the process tree. ps -D'^$' suggests there are possibly more characters to use and maybe even some ki

Re: ps(1) bugs and problems

On 2023-07-29 00:07:37, Jamie Landeg-Jones wrote: I have a program that produces a list of PIDS, that are supplied via '-p' to /bin/ps and are sorted with '-d'. What language is it written in? What is the use case? After a late upgrade on a particular machine, I've just been bitten by the mod

ps(1) bugs and problems

I have a program that produces a list of PIDS, that are supplied via '-p' to /bin/ps and are sorted with '-d'. After a late upgrade on a particular machine, I've just been bitten by the modifications to "ps" to unconditionaly add recurive descendancy PID lookups to the '-d' option when a pid is sp

Re: problems on new -current install with pkg/ssl

thanks everyone it's working normally now after full buildworld kernel then forced rebuild of all ports from their updated sources --

Re: problems on new -current install with pkg/ssl

On 7/9/23 18:27, void wrote: On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want

Re: problems on new -current install with pkg/ssl

On Sun, 9 Jul 2023 17:17:38 +0100 void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) > I try to use pkg for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and install

Re: problems on new -current install with pkg/ssl

void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use > pkg for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and install it now? [y/N]: y > Bootstrapping p

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: > Hi, > > On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg > for anything and this error > happens: > > # pkg install doas > The package management tool is not yet installed on your system. > Do you want to fetch and

Re: problems on new -current install with pkg/ssl

On Sun, Jul 09, 2023 at 05:17:38PM +0100, void wrote: Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want to fetch and install it now?

problems on new -current install with pkg/ssl

Hi, On a fresh 14-current install (main-n263444-653738e895ba) I try to use pkg for anything and this error happens: # pkg install doas The package management tool is not yet installed on your system. Do you want to fetch and install it now? [y/N]: y Bootstrapping pkg from pkg+http://pkg.FreeBS

Re: Problems with /usr/src/usr.bin/rs/rs.c

> On Nov 25, 2022, at 2:53 AM, Jochen Neumeister wrote: > > Hi, > > > this is a problem on 2 CURRENT Maschines. > > Both stop with this: > > cc -target x86_64-unknown-freebsd14.0 > --sysroot=/usr/obj/usr/src/amd64.amd64/tmp > -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -fno-comm

Problems with /usr/src/usr.bin/rs/rs.c

Hi, this is a problem on 2 CURRENT Maschines. Both stop with this: cc -target x86_64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp -B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin  -O2 -pipe -fno-common -I/usr/src/lib/libarchive/tests -I/usr/src/lib/libarchive -I/usr/obj/usr/src/amd

Re: linux debian jail - network problems

ebsd.org/en/articles/linux-emulation/ <https://docs.freebsd.org/en/articles/linux-emulation/> 2. https://wiki.freebsd.org/Linuxulator <https://wiki.freebsd.org/Linuxulator> > Their are fee problems in the logs.. I dont kbow if they all related only to > netlink (prctl immutable for examp

Re: linux debian jail - network problems

Hi, Thank you for your response.. I wonder if Is it really only netlink problem? Their are fee problems in the logs.. I dont kbow if they all related only to netlink (prctl immutable for example).. I also saw oncompatibilities in socket.c Btw: I tried to enter the link you sent and it asked

Re: linux debian jail - network problems

2022 23:11:58.745 general: notice: running > 22-Feb-2022 23:11:58.795 general: error: socket.c:2405: unexpected error: > 22-Feb-2022 23:11:58.795 general: error: setsockopt(50, IP_RECVTOS) > failed: Protocol not available > 22-Feb-2022 23:12:58.811 general: error: ifiter_getifaddrs.c:79: > unexpected error: > 22-Feb-2022 23:12:58.811 general: error: getting interface addresses: > getifaddrs: Address family not supported by protocol > 22-Feb-2022 23:12:58.811 network: warning: not listening on any interfaces > > Any Idea how to fix this?? > > cbsd@j2> named -V > BIND 9.16.22-Debian (Extended Support Version) > running on Linux x86_64 3.2.0 FreeBSD 12.3-RELEASE-p1 GENERIC > > installing newer versions > > I have also problems with dovecot mail package.. but will leave it for now > > Thanks in advance, > Sami > >

Re: Problems compiling kernel

On 2021-Dec-30, at 13:27, Mark Millard wrote: >> Dear all, >> >> on a system updated yesterday I get >> >> tuexen_at_head:~/freebsd-src % git branch >> * main >> tuexen_at_head:~/freebsd-src % git pull >> Already up to date. >> tuexen_at_head:~/freebsd-src % uname -a >> FreeBSD head 14.0-CURREN

Re: Problems compiling kernel

> Dear all, > > on a system updated yesterday I get > > tuexen_at_head:~/freebsd-src % git branch > * main > tuexen_at_head:~/freebsd-src % git pull > Already up to date. > tuexen_at_head:~/freebsd-src % uname -a > FreeBSD head 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-n252035-63f7f3921bd: > Thu

Re: Problems compiling kernel

> On 30. Dec 2021, at 20:42, Konstantin Belousov wrote: > > On Thu, Dec 30, 2021 at 08:33:09PM +0100, tue...@freebsd.org wrote: >>> On 30. Dec 2021, at 20:26, Michael Gmelin wrote: >>> >>> This should have been resolved today in >>> https://cgit.freebsd.org/src/commit/?id=5e6a2d6eb220d780c9128

Re: Problems compiling kernel

On Thu, Dec 30, 2021 at 08:33:09PM +0100, tue...@freebsd.org wrote: > > On 30. Dec 2021, at 20:26, Michael Gmelin wrote: > > > > This should have been resolved today in > > https://cgit.freebsd.org/src/commit/?id=5e6a2d6eb220d780c9128c81b58f133114061415 > I do have that commit locally in the tre

Re: Problems compiling kernel

> On 30. Dec 2021, at 20:26, Michael Gmelin wrote: > > This should have been resolved today in > https://cgit.freebsd.org/src/commit/?id=5e6a2d6eb220d780c9128c81b58f133114061415 I do have that commit locally in the tree... But I can't build world or kernel. Looking for libc++.so.1 I get tuexen

Re: Problems compiling kernel

This should have been resolved today in https://cgit.freebsd.org/src/commit/?id=5e6a2d6eb220d780c9128c81b58f133114061415 -m > On 30. Dec 2021, at 20:17, tue...@freebsd.org wrote: > Dear all, > > on a system updated yesterday I get > > tuexen@head:~/freebsd-src % git branch > * main > tuexen@h

Problems compiling kernel

Dear all, on a system updated yesterday I get tuexen@head:~/freebsd-src % git branch * main tuexen@head:~/freebsd-src % git pull Already up to date. tuexen@head:~/freebsd-src % uname -a FreeBSD head 14.0-CURRENT FreeBSD 14.0-CURRENT #1 main-n252035-63f7f3921bd: Thu Dec 30 11:33:16 CET 2021

Re: Problems with getting a crash dump

Thanks for the replies! I finally managed to solve the issue. For some reason when I get a panic while i915kms is active I am unable to write `continue` in KDB. Also the KDB prompt was not even displayed so I had no idea that I should write that command. After I added debug.debugger_on_panic=0 to /

Re: Problems in pkg

On Wed, Nov 10, 2021 at 02:01:09PM -0300, Cristian Cardoso wrote: > The problem was actually user nobody, which was deleted from the system. > I recreated and solved the problem. > > Em qua., 10 de nov. de 2021 às 06:36, Baptiste Daroussin > escreveu: > > > > On Mon, Nov 08, 2021 at 03:48:51PM -0

Re: Problems in pkg

The problem was actually user nobody, which was deleted from the system. I recreated and solved the problem. Em qua., 10 de nov. de 2021 às 06:36, Baptiste Daroussin escreveu: > > On Mon, Nov 08, 2021 at 03:48:51PM -0300, Cristian Cardoso wrote: > > I'm trying to use pkg to install/update package

Re: Problems in pkg

On 08/11/2021 18:48, Cristian Cardoso wrote: pkg: Unable to drop privileges: No error: 0 pkg: No signature found Cross-reference for FreeBSD 13.0⋯

Re: Problems with getting a crash dump

On Mon, Nov 08, 2021 at 07:08:31PM +, Alexander wrote: > Hello, I am currently using FreeBSD 14.0-CURRENT and I found a bug that > triggers a kernel panic. I wanted to make a kernel crash dump to further > investigate the issue, but after a few tries I still did not manage to do it. > I started

Re: Problems with getting a crash dump

On Mon, 08 Nov 2021 19:08:31 + Alexander wrote: > Hello, I am currently using FreeBSD 14.0-CURRENT and I found a bug > that triggers a kernel panic. I wanted to make a kernel crash dump to > further investigate the issue, but after a few tries I still did not > manage to do it. I started by f

Problems with getting a crash dump

Hello, I am currently using FreeBSD 14.0-CURRENT and I found a bug that triggers a kernel panic. I wanted to make a kernel crash dump to further investigate the issue, but after a few tries I still did not manage to do it. I started by following the instructions in the FreeBSD Handbook. I checked t

Problems in pkg

I'm trying to use pkg to install/update packages, but I'm getting the following error: # pkg update Updating FreeBSD repository catalogue... Fetching meta.conf: 100%163 B 0.2kB/s00:01 Fetching packagesite.pkg: 100%6 MiB 6.7MB/s00:01 pkg: Unable to drop privileges: No error: 0 p

Re: Problems with realtek NIC

Am 02.05.21 um 01:37 schrieb Greg Rivers: > On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote: >> Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: >>> On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: I using a FreeBSD 14-Current and get random error with my NIC.

Re: Problems with realtek NIC

On Saturday, 1 May 2021 16:45:03 CDT Stefan Esser wrote: > Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: > > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: > >> I using a FreeBSD 14-Current and get random error with my NIC. The > >> watchdog timer send a timeout mess

Re: Problems with realtek NIC

Am 01.05.21 um 21:48 schrieb Greg Rivers via freebsd-current: > On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: >> I using a FreeBSD 14-Current and get random error with my NIC. The watchdog >> timer send a timeout message and I loose connection temporaly. In logs show >> only this

Re: Problems with realtek NIC

On Saturday, 1 May 2021 14:09:46 CDT Nilton Jose Rizzo wrote: > I using a FreeBSD 14-Current and get random error with my NIC. The watchdog > timer send a timeout message and I loose connection temporaly. In logs show > only this message: > Switch to the official Realtek driver in ports: net/rea

Re: Problems with realtek NIC

On 01.05.2021 21.09, Nilton Jose Rizzo wrote: Hi all I using a FreeBSD 14-Current and get random error with my NIC. The watchdog timer send a timeout message and I loose connection temporaly. In logs show only this message: May 1 14:24:18 valfenda kernel: re0: watchdog timeout May 1 14:24:1

Problems with realtek NIC

Hi all I using a FreeBSD 14-Current and get random error with my NIC. The watchdog timer send a timeout message and I loose connection temporaly. In logs show only this message: May 1 14:24:18 valfenda kernel: re0: watchdog timeout May 1 14:24:18 valfenda kernel: re0: link state changed to DO

Re: Problems with Webcam and USB 3.X [solved]

On 4/14/21 5:16 PM, Nilton Jose Rizzo wrote: On 4/14/21 4:27 PM, Nilton Jose Rizzo wrote: "-s uvc_driver.quirks=0x100" When I start webcamd with this, return a LONG list of other variables and webcamd not run. Is it right? Try: "-m uvc_driver.quirks=0x100" It's w

Re: Problems with Webcam and USB 3.X

On 4/14/21 4:27 PM, Nilton Jose Rizzo wrote: "-s uvc_driver.quirks=0x100" When I start webcamd with this, return a LONG list of other variables and webcamd not run. Is it right? Try: "-m uvc_driver.quirks=0x100" --HPS ___ freebsd-current@

Re: Problems with Webcam and USB 3.X

> > Hi, > > The following thread suggests using a UVC quirk: > > https://sourceforge.net/p/linux-uvc/mailman/linux-uvc-devel/?viewmonth=202102 > > Translated to webcamd parameters, it becomes: > > "-s uvc_driver.quirks=0x100" When I start webcamd with this, return a LONG list of other

Re: Problems with Webcam and USB 3.X

On 4/14/21 4:15 PM, Nilton Jose Rizzo wrote: The last version tha I Know that work need libhal, Just do "make config" and de-select HAL support, before building. Webcamd doesn't need it. --HPS ___ freebsd-current@freebsd.org mailing list https://li

Re: Problems with Webcam and USB 3.X

> > On 4/14/21 3:41 PM, Nilton Jose Rizzo wrote: > >> > >> Hi, > >> > Hi, > :< - CUT - >: > Does downgrading webcamd to an older version make it work again? > > I probably need to search for that error message. Maybe it is a known > issue already fixed. So far it looks like a proble

Re: Problems with Webcam and USB 3.X

Hi, The following thread suggests using a UVC quirk: https://sourceforge.net/p/linux-uvc/mailman/linux-uvc-devel/?viewmonth=202102 Translated to webcamd parameters, it becomes: "-s uvc_driver.quirks=0x100" Can you try that? --HPS ___ freebsd-curren

Re: Problems with Webcam and USB 3.X

> > Hi, > > On 4/14/21 1:10 PM, Nilton Jose Rizzo wrote: > > root@valfenda:/usr/ports/multimedia/webcamd # webcamd -d ugem1.3 -m > > uvc_driver.trace=1 > ^^^ ugem -> ugen > > ugen was spelled wrong. Ops .. Sorry. output root@val

Re: Problems with Webcam and USB 3.X

Hi, On 4/14/21 1:10 PM, Nilton Jose Rizzo wrote: root@valfenda:/usr/ports/multimedia/webcamd # webcamd -d ugem1.3 -m uvc_driver.trace=1 ^^^ ugem -> ugen ugen was spelled wrong. --HPS ___ fr

Re: Problems with Webcam and USB 3.X

> > On 4/14/21 3:49 AM, Nilton Jose Rizzo wrote: > >> > >> On 4/14/21 3:05 AM, Nilton Jose Rizzo wrote: > >>> 22:03:30.860068 usbus1.3 > >>> SUBM-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=0,IVAL=0 > >>> 22:03:30.860079 usbus1.3 > >>> DONE-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=13608,IVAL=0,ERR=0 >

Re: Problems with Webcam and USB 3.X

On 4/14/21 3:49 AM, Nilton Jose Rizzo wrote: On 4/14/21 3:05 AM, Nilton Jose Rizzo wrote: 22:03:30.860068 usbus1.3 SUBM-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=0,IVAL=0 22:03:30.860079 usbus1.3 DONE-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=13608,IVAL=0,ERR=0 :< CUT >: Hi, I see

Re: Problems with Webcam and USB 3.X

> > On 4/14/21 3:05 AM, Nilton Jose Rizzo wrote: > > 22:03:30.860068 usbus1.3 > > SUBM-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=0,IVAL=0 > > 22:03:30.860079 usbus1.3 > > DONE-ISOC-EP=0081,SPD=HIGH,NFR=128,SLEN=13608,IVAL=0,ERR=0 :< CUT >: > > Hi, > > I see data is received, so f

Re: Problems with Webcam and USB 3.X

On 4/14/21 3:10 AM, Nilton Jose Rizzo wrote: On 4/14/21 1:38 AM, Nilton Jose Rizzo wrote: The webcamd create two devices ( /dev/video{0,1} ) and the pwcview open the window, but not show image, onle a green screen, but the webcam active LED turn on. But in my old instalation

  1   2   3   4   5   6   7   8   9   10   >