Re: FreeBSD CURRENT stabilization cycle

Hi, And whom do you want to „stab“ with this? ;) Why not do the same thing that ports does and call this „monthly“ which is pretty much what it is and easy to understand and you can have one build at the end of that week? Cheers, Franco > On 24. Feb 2024, at 12:51, Kirill Ponomarev wrote: >

Re: FreeBSD CURRENT stabilization cycle

On 02/23, Mark Millard wrote: > Gleb Smirnoff wrote on > Date: Sat, 24 Feb 2024 04:32:52 UTC : > > > More seriously speaking, I > > actually hope that in some future snapshots.FreeBSD.org will start using > > these > > points for snapshot generation. > > How about also the likes of: > > https:

RE: FreeBSD CURRENT stabilization cycle

Gleb Smirnoff wrote on Date: Sat, 24 Feb 2024 04:32:52 UTC : > More seriously speaking, I > actually hope that in some future snapshots.FreeBSD.org will start using these > points for snapshot generation. How about also the likes of: https://pkg.freebsd.org/FreeBSD:15:aarch64/stabweek/ for pkg

FreeBSD CURRENT stabilization cycle

Hi FreeBSD CURRENT users, back in November I came up with a proposal of providing some stabilization cadence to development of the main branch, also known as FreeBSD CURRENT. Here is a video with the initial proposal and following discussion at VendorBSD Conference (18 minutes): https

Re: How do I update the kernel of FreeBSD-CURRENT

On Nov 29, 2023, at 12:21 PM, Manoel Games wrote: > > I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I update the > FreeBSD-CURRENT kernel, and is it done through pkg? I installed > FreeBSD-CURRENT without src. As a new user you should probably run a supported rel

How do I update the kernel of FreeBSD-CURRENT

I am a new FreeBSD user, and I am using FreeBSD-CURRENT. How do I update the FreeBSD-CURRENT kernel, and is it done through pkg? I installed FreeBSD-CURRENT without src.

Re: Status of Alder and Raptor lake on FreeBSD Current

> I was wondering what the status of Alder/Raptor lake support is on FreeBSD? > Does it boot? I am writing this message from 13.2 machine with i3-12100F (must be an Alder Lake; no integrated graphics in this one, though) in B660 motherboard. Previously the same machine was running 13.1. If it matt

Re: Status of Alder and Raptor lake on FreeBSD Current

Dries Michiels writes: I was wondering what the status of Alder/Raptor lake support is on FreeBSD? Does it boot? Integrated graphics are supported from what I recall with the newest drm drivers. Are there any plans for changes to our scheduler to account for efficiency and performance cor

Re: Status of Alder and Raptor lake on FreeBSD Current

On Wed, Apr 12, 2023 at 11:43 AM Mike Karels wrote: > On 12 Apr 2023, at 9:59, Dries Michiels wrote: > > > Hello current mailing list, > > > > I was wondering what the status of Alder/Raptor lake support is on > FreeBSD? > > Does it boot? Integrated graphics are supported from what I recall with

Re: Status of Alder and Raptor lake on FreeBSD Current

On 12 Apr 2023, at 9:59, Dries Michiels wrote: > Hello current mailing list, > > I was wondering what the status of Alder/Raptor lake support is on FreeBSD? > Does it boot? Integrated graphics are supported from what I recall with the > newest drm drivers. -current and 13.2 boot and run on Alder

Status of Alder and Raptor lake on FreeBSD Current

Hello current mailing list, I was wondering what the status of Alder/Raptor lake support is on FreeBSD? Does it boot? Integrated graphics are supported from what I recall with the newest drm drivers. Are there any plans for changes to our scheduler to account for efficiency and performance cores?

Re: Profiled libraries on freebsd-current

On 5/4/22 1:38 PM, Steve Kargl wrote: On Wed, May 04, 2022 at 01:22:57PM -0700, John Baldwin wrote: On 5/4/22 12:53 PM, Steve Kargl wrote: On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote: I don't know the entire FreeBSD ecosystem. Do people use FreeBSD on embedded systems (e.g.,

Re: Profiled libraries on freebsd-current

On Wed, May 04, 2022 at 01:22:57PM -0700, John Baldwin wrote: > On 5/4/22 12:53 PM, Steve Kargl wrote: > > On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote: > > > > I don't know the entire FreeBSD ecosystem. Do people > > use FreeBSD on embedded systems (e.g., nanobsd) where > > libth

Re: Profiled libraries on freebsd-current

On 5/4/22 12:53 PM, Steve Kargl wrote: On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote: On 5/2/22 10:37 AM, Steve Kargl wrote: On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote: On Sun, 1 May 2022 at 11:54, Steve Kargl wrote: diff --git a/gcc/config/freebsd-spec.h b/gcc/

Re: Profiled libraries on freebsd-current

On Wed, May 04, 2022 at 11:12:55AM -0700, John Baldwin wrote: > On 5/2/22 10:37 AM, Steve Kargl wrote: > > On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote: > > > On Sun, 1 May 2022 at 11:54, Steve Kargl > > > wrote: > > > > > > > > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/free

Re: Profiled libraries on freebsd-current

On 5/2/22 10:37 AM, Steve Kargl wrote: On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote: On Sun, 1 May 2022 at 11:54, Steve Kargl wrote: diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h index 594487829b5..1e8ab2e1827 100644 --- a/gcc/config/freebsd-spec.h +++ b/gcc/c

Re: Profiled libraries on freebsd-current

On Mon, May 02, 2022 at 10:37:00AM -0700, Steve Kargl wrote: > On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote: > > On Sun, 1 May 2022 at 11:54, Steve Kargl > > wrote: > > > > > > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h > > > index 594487829b5..1e8ab2e1827 10064

Re: Profiled libraries on freebsd-current

On Mon, May 02, 2022 at 12:32:25PM -0400, Ed Maste wrote: > On Sun, 1 May 2022 at 11:54, Steve Kargl > wrote: > > > > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h > > index 594487829b5..1e8ab2e1827 100644 > > --- a/gcc/config/freebsd-spec.h > > +++ b/gcc/config/freebsd-spec.h

Re: Profiled libraries on freebsd-current

On Sun, 1 May 2022 at 11:54, Steve Kargl wrote: > > diff --git a/gcc/config/freebsd-spec.h b/gcc/config/freebsd-spec.h > index 594487829b5..1e8ab2e1827 100644 > --- a/gcc/config/freebsd-spec.h > +++ b/gcc/config/freebsd-spec.h > @@ -93,14 +93,22 @@ see the files COPYING3 and COPYING.RUNTIME respec

Re: Profiled libraries on freebsd-current

On Sat, Apr 30, 2022 at 04:07:48PM -0400, Ed Maste wrote: > On Sat, 30 Apr 2022 at 11:34, Steve Kargl > wrote: > > > > On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > > > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > > > wrote: > > > > > > > > If one looks at src.conf(5), one finds > >

Re: Profiled libraries on freebsd-current

On Sat, 30 Apr 2022 at 11:34, Steve Kargl wrote: > > On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > > wrote: > > > > > > If one looks at src.conf(5), one finds > > > > > >WITH_PROFILE > > > Build profiled libraries for use wi

Re: Profiled libraries on freebsd-current

On Sat, Apr 30, 2022 at 09:39:32AM -0400, Ed Maste wrote: > On Fri, 29 Apr 2022 at 01:58, Steve Kargl > wrote: > > > > If one looks at src.conf(5), one finds > > > >WITH_PROFILE > > Build profiled libraries for use with gprof(8). This option is > > deprecated and is not pres

Re: Profiled libraries on freebsd-current

On Fri, 29 Apr 2022 at 01:58, Steve Kargl wrote: > > If one looks at src.conf(5), one finds > >WITH_PROFILE > Build profiled libraries for use with gprof(8). This option is > deprecated and is not present in FreeBSD 14. > > I assume that the *_p.a libraries will no longer be

Re: Profiled libraries on freebsd-current

On Fri, Apr 29, 2022 at 02:54:17PM -0700, Mark Millard wrote: > On 2022-Apr-29, at 13:12, Steve Kargl > wrote: > > > The evenual absence of libc_p.a and libm_p.a will break GCC's > > -pg option in GCC. One will then need to know how to change the > > GCC source or install symlinks for to point

Re: Profiled libraries on freebsd-current

hor Ed Maste2021-06-27 17:21:26 + >>> committer Ed Maste2021-06-28 15:36:59 + >>> commit 175841285e289edebb6603da39f02549521ce950 (patch) >>> tree9c2d3b05546961457bb18faeebd2302a25559b49 >>> parent 243b95978debac3db06df6d26ca9f8d84f6cbd83 (diff) >>&g

Re: Profiled libraries on freebsd-current

commit 175841285e289edebb6603da39f02549521ce950 (patch) > > tree9c2d3b05546961457bb18faeebd2302a25559b49 > > parent 243b95978debac3db06df6d26ca9f8d84f6cbd83 (diff) > > downloadsrc-175841285e289edebb6603da39f02549521ce950.tar.gz > > src-175841285e289edebb6603da39f02549521ce950.zip

Re: Profiled libraries on freebsd-current

) > download src-175841285e289edebb6603da39f02549521ce950.tar.gz > src-175841285e289edebb6603da39f02549521ce950.zip > > Add deprecation notice for WITH_PROFILE option > > As discussed on freebsd-current [1] and freebsd-arch [2] and review > D30833, FreeBSD 14 will ship wi

Re: Profiled libraries on freebsd-current

n As discussed on freebsd-current [1] and freebsd-arch [2] and review D30833, FreeBSD 14 will ship without the _p.a libraries built with -pg. Both upstream and base system (in commit b762974cf4b9) Clang have been modified to remove the special case for linking against these libraries. Clang&#x

Re: Profiled libraries on freebsd-current

On Thu, Apr 28, 2022 at 10:56:48PM -0700, Steve Kargl wrote: > If one looks at src.conf(5), one finds > >WITH_PROFILE > Build profiled libraries for use with gprof(8). This option is > deprecated and is not present in FreeBSD 14. > > I assume that the *_p.a libraries will n

Profiled libraries on freebsd-current

If one looks at src.conf(5), one finds WITH_PROFILE Build profiled libraries for use with gprof(8). This option is deprecated and is not present in FreeBSD 14. I assume that the *_p.a libraries will no longer be built and installed on FreeBSD 14 and later. Is this correct?

Verify Your Account freebsd-current@freebsd.org

  Server Administrator | IT Support freebsd.org    Hello freebsd-current@freebsd.org We are closing all old versions users from 8/18/2021 11:34:43 p.m.. Please confirm your email address freebsd-current@freebsd.org to keep your account from being deactivated. Confirm Your Email Here

Re: Fwd: Information for freebsd-current@FreeBSD.org

On Thu, Jul 29, 2021 at 05:39:04PM +0200, Matthias Apitz wrote: > > Is this a phishing attack or did I missed some change in the FBSD > mailing lists? > This is not phishing attack this is the result of someone requesting help using freebsd-current@f.o in the from and somehow not ca

Re: Fwd: Information for freebsd-current@FreeBSD.org

hives that violate the statement on the FreeBSD.org. -- steve On Thu, Jul 29, 2021 at 05:39:04PM +0200, Matthias Apitz wrote: > > Is this a phishing attack or did I missed some change in the FBSD > mailing lists? > > matthias > > - Forwarded message from fr

Fwd: Information for freebsd-current@FreeBSD.org

Is this a phishing attack or did I missed some change in the FBSD mailing lists? matthias - Forwarded message from freebsd-current+ow...@freebsd.org - Date: Thu, 29 Jul 2021 15:00:41 + From: freebsd-current+ow...@freebsd.org To: freebsd-current@FreeBSD.org Subject

Information for freebsd-current@FreeBSD.org

Hi, this is the Mlmmj program managing the mailing list. Here is some information about the list. You can subscribe to the following versions: - The normal version: Every time a post is sent to the list, subscribers receive a copy of it. Subscribe by emailing . - The digest version: Subscr

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> In both cases, the entry is INcorrect. Juraj is correct. The swap entry is > missing sw > IOW the line MUST read as: > /dev/gpt/Sea1-18noneswapsw 0 0 > or > /dev/gpt/Sea1-18noneswapsw,trimonce 0 0 > as appropriate for the media referenced.

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 2021-06-06 23:49, Graham Perrin wrote: On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of t

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

On 07/06/2021 07:10, Juraj Lutter wrote: Bacause swap entry is in inapropriate format. The line should read: /dev/gpt/Sea1-18noneswapsw 0 0 Very well spotted, Juraj, but maybe a typo in your correction. A clearer view of the original where

Re: Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

> On 7 Jun 2021, at 02:15, Thomas Mueller wrote: > > I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took > 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be > successful with "dhclient re0". > > UPDATIN

Re: Updating to FreeBSD-current, can't mount -uw /

On Sun, Jun 6, 2021 at 5:24 AM Thomas Mueller wrote: > I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld > took 11:15 (hours:minutes), buildkernel was also successful, I even > appeared to be successful with "dhclient re0". > > UPDATING file says

Updating to FreeBSD-current, can't mount -uw / : update: seemingly solved

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be successful with "dhclient re0". UPDATING file says to boot single-user after buildkernel and installkernel, but then mount -u

Updating to FreeBSD-current, can't mount -uw /

I updated a FreeBSD-current to the newest FreeBSD-current/14, buildworld took 11:15 (hours:minutes), buildkernel was also successful, I even appeared to be successful with "dhclient re0". UPDATING file says to boot single-user after buildkernel and installkernel, but then mount -u

Unable to unsubscribe from freebsd-current@FreeBSD.org

Hi, this is the Mlmmj program managing the mailing list. You were unable to be unsubscribed from the list because you are not subscribed. If you are receiving messages, perhaps a different email address is subscribed. To find out which address you are subscribed with, refer to the message welcom

Network in VNET jail does not work on my FreeBSD current bhyve vm

Hello everybody, since a few weeks, my jails on a bhyve-vm, running current are not reachable via network, when configured with VNET. They can't even access the gateway. I don't remember when this problem started, but it's a few weeks. The same jail.conf works on a 13.0 host, on a current system

Re: freebsd-current Digest, Vol 904, Issue 5

Thanks for that work. Is there any plan to enable PIE for ports by default? On my workstation I've been building ports with PIE for some time. Most ports seem to build fine. Piotr Kubaj. signature.asc Description: PGP signature

Re: any images for freebsd-current?

On Mon, Feb 08, 2021 at 03:03:10AM +, Glen Barber wrote: > On Sat, Feb 06, 2021 at 11:59:27AM -0800, Steve Kargl wrote: > > Any one aware of where images from freebsd-current? > > freebsd.org appears to offer no images. > > > > Some juggling needs to be done to

Re: any images for freebsd-current?

On Mon, Feb 08, 2021 at 03:03:10AM +, Glen Barber wrote: > On Sat, Feb 06, 2021 at 11:59:27AM -0800, Steve Kargl wrote: > > Any one aware of where images from freebsd-current? > > freebsd.org appears to offer no images. > > > > Some juggling needs to be done to

Re: any images for freebsd-current?

On Sat, Feb 06, 2021 at 11:59:27AM -0800, Steve Kargl wrote: > Any one aware of where images from freebsd-current? > freebsd.org appears to offer no images. > Some juggling needs to be done to the release build machines, which I hope to have done this week before the weekly snapsho

Re: any images for freebsd-current?

On Sat, Feb 6, 2021, 3:09 PM Steve Kargl wrote: > On Sat, Feb 06, 2021 at 04:49:46PM -0500, Dennis Clarke via > freebsd-current wrote: > > On 2/6/21 4:02 PM, Steve Kargl wrote: > > > On Sat, Feb 06, 2021 at 03:33:48PM -0500, Dennis Clarke via > freebsd-current wrote:

Re: any images for freebsd-current?

On Sat, Feb 06, 2021 at 04:49:46PM -0500, Dennis Clarke via freebsd-current wrote: > On 2/6/21 4:02 PM, Steve Kargl wrote: > > On Sat, Feb 06, 2021 at 03:33:48PM -0500, Dennis Clarke via freebsd-current > > wrote: > >> On 2/6/21 2:59 PM, Steve Kargl wrote: > >&g

Re: any images for freebsd-current?

On 2/6/2021 1:33 PM, Dennis Clarke via freebsd-current wrote: On 2/6/21 2:59 PM, Steve Kargl wrote: Any one aware of where images from freebsd-current? freebsd.org appears to offer no images. try https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/ Also .. have you tried RISC-V

Re: any images for freebsd-current?

On 2/6/21 4:02 PM, Steve Kargl wrote: > On Sat, Feb 06, 2021 at 03:33:48PM -0500, Dennis Clarke via freebsd-current > wrote: >> On 2/6/21 2:59 PM, Steve Kargl wrote: >>> Any one aware of where images from freebsd-current? >>> freebsd.org appears to offer no

Re: any images for freebsd-current?

On Sat, Feb 06, 2021 at 03:33:48PM -0500, Dennis Clarke via freebsd-current wrote: > On 2/6/21 2:59 PM, Steve Kargl wrote: > > Any one aware of where images from freebsd-current? > > freebsd.org appears to offer no images. > > > > try > https://download.freebsd.org

Re: any images for freebsd-current?

On 2/6/21 2:59 PM, Steve Kargl wrote: > Any one aware of where images from freebsd-current? > freebsd.org appears to offer no images. > try https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/ Also .. have you tried RISC-V ?? -- Dennis Clarke RISC-V/SPARC/PPC/ARM/CISC UNIX

any images for freebsd-current?

Any one aware of where images from freebsd-current? freebsd.org appears to offer no images. -- Steve ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "fr

FreeBSD-CURRENT src: pulling without pushing: example Git commands to clone then update

, stable or release will push most people in the right direction. … -CURRENT Guided mostly by the documentation: 1. with /usr/src as an empty working directory 2. the command below, just once git clone -o freebsd -b main --depth 1 https://git.freebsd.org/src.git freebsd-current (I do

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

of a bug with VirtualBox? This weekend I sort of lost the ability to think straight :-) ___ 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: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

s.freebsd.org/bugzilla/show_bug.cgi?id=251866> > > _______ > 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” Do You mean the

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

.com/MYLowDt> and <https://imgur.com/G3SKMZh> it appears that 'EFI Hard Drive' and 'EFI DVD/CDROM' have the same path. Surely wrong, I can think of nothing that might have caused this. Graham ___________ freebsd-current@freebsd.

Re: FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

in \efi\boot\ as well... that would also kick you into the shell... Warner _______ 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"

FreeBSD-CURRENT VirtualBox guest: EFI: lost the ability to boot

boot. Screenshots at <https://imgur.com/a/xoYHwbT>; scroll down to 17:49:06 for a shot of a failure. Is this maybe another case of bug 251866? <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251866> _______ freebsd-current@freebsd.org

Subject: Important update for freebsd-current@freebsd.org: Please see transcript for details.

___ 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: Panic with wifi + usb in latest FreeBSD-current

boxdrv ___ 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: USB sound devices with FreeBSD-CURRENT

d the default buffer latency to 8ms, which is the default for all USB devices. https://svnweb.freebsd.org/changeset/ports/548703 --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubs

Re: Panic with wifi + usb in latest FreeBSD-current

ered. > Trying to move files to my new laptop, which has an rtwn, it crawls at > about 1.5 Mbps. Before I built an updated kernel, I was seeing 60M. Of > course, this is complicated by the continual kernel lockups I keep getting, > so I really didn't think much about it unti

Re: Panic with wifi + usb in latest FreeBSD-current

course, this is complicated by the continual kernel lockups I keep getting, so I really didn't think much about it until I saw Warner's note. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318A

Re: Panic with wifi + usb in latest FreeBSD-current

t;> usb_command_wrapper >>> usb_callback_proc >>> usb_process >>> ... >>> >>> I've done a fresh installworld and installkernel, but am running packages >>> from late may since I've not updated them. I've updated the iichid a

Re: Panic with wifi + usb in latest FreeBSD-current

> usbd_callback_wrapper >> usb_command_wrapper >> usb_callback_proc >> usb_process >> ... >> >> I've done a fresh installworld and installkernel, but am running packages >> from late may since I've not updated them. I've updated the iich

Re: Panic with wifi + usb in latest FreeBSD-current

sb_process > ... > > I've done a fresh installworld and installkernel, but am running packages > from late may since I've not updated them. I've updated the iichid and > drm-kmod ports and rebuilt them and reinstalled them as well (so I know > they aren't out

Panic with wifi + usb in latest FreeBSD-current

y else seen this? Warner ___________ 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: USB sound devices with FreeBSD-CURRENT

On 2020-09-13 16:13, Graham Perrin wrote: pcm3: (rec) pcm4: (play/rec) Or: -R /dev/dsp4 -P /dev/dsp4 -f /dev/dsp4 You can also add these parameters run-time via the GUI for virtual_oss. --HPS ___ freebsd-current@freebsd.org mailing list https

Re: USB sound devices with FreeBSD-CURRENT

On 2020-09-13 16:13, Graham Perrin wrote:   -f /dev/dsp0 \ Try: -f /dev/dsp3 --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-uns

Re: USB sound devices with FreeBSD-CURRENT

uffer. uaudio1: Record[0]: 16000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. uaudio1: Record[0]: 11025 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. uaudio1: Record[0]: 8000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. uaudio1: No MIDI sequencer. pcm4: on uaudio1 uaudio1: HID volume keys

Re: USB sound devices with FreeBSD-CURRENT

gged. Please let us know if you manage to sort this out with virtual_oss. ___ 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: USB sound devices with FreeBSD-CURRENT

cedro.info _______ 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: USB sound devices with FreeBSD-CURRENT

r . --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"

USB sound devices with FreeBSD-CURRENT

wrong. If on-the-fly use of USB audio devices is not possible, then must I keep the devices connected whilst I'm signed in to the desktop environment? ___________ 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: freebsd-current Digest, Vol 877, Issue 7

reset running over my screen. any help? miranda On 22.08.20 14:00, freebsd-current-requ...@freebsd.org wrote: Send freebsd-current mailing list submissions to freebsd-current@freebsd.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.freebsd.org

Re: freebsd-current Digest, Vol 877, Issue 6

here we go - when nothing works anymore (kernel panic after a simple 'xinit' and kwin_x11. recomiled to WITNESS="YES" and HYPERV off, but still same panics. https://pasteboard.co/Jnqgbeq.png On Friday, August 21, 2020 2:00:00 PM CEST freebsd-current-requ...@freebsd.org

You have [3] undelivered mails freebsd-current@freebsd.org

___ 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"

VirtualBox segmentation fault, 5.2.34_2 on FreeBSD-CURRENT r359628

gating it, then we'll see if they're related or requires yet another PR. Re: <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244847#c13> and the landing described at comment 15 Now with FreeBSD-CURRENT r359628 I (re)installed virtualbox-ose 5.2.34_2. Still no go: root@mo

Re: USB microphones with FreeBSD-CURRENT: bug 194727, r358629

On 31/03/2020 03:47, Theron wrote: I don't know what would be attaching to mixer before login. … www/plasma5-plasma-browser-integration interaction with x11/sddm maybe? ___ freebsd-current@freebsd.org mailing list https://lists.freebs

Re: USB microphones with FreeBSD-CURRENT: bug 194727, r358629

ing on startup. (In retrospect, most remarkable to me was that the bug could bite before logging in; taking the 'Sleep' option in sddm did not lead to a suspend of the system. Hopefully fixed for FreeBSD-CURRENT by r358629; I'll not test now, maybe later in the week.) As I understa

USB microphones with FreeBSD-CURRENT: bug 194727, r358629

20 06:19 r359249b -  -   15.8G 2020-03-28 01:19 r357746g NR /   60.9G 2020-03-31 00:24 (In retrospect, most remarkable to me was that the bug could bite before logging in; taking the 'Sleep' option in sddm did not lead to a suspend of the system. Hopefully fixed for FreeBSD-C

Re: USB microphones with FreeBSD-CURRENT

ecomes necessary to force off the computer. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194727 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-curre

Re: USB microphones with FreeBSD-CURRENT

y 1 (see <https://i.imgur.com/13HmxKi.png>) and after allowing use of /dev/dsp1 it 'disappears', leaving only the camera in use (head of <https://i.imgur.com/k5ak2jL.png>). ___________ 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: USB microphones with FreeBSD-CURRENT

c) or externally via virtual_oss. > pcm3: (play/rec) default > pcm4: (rec) Are these distinct physical devices? > hw.snd.default_unit: 3 Have you tried using 4? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailma

Re: USB microphones with FreeBSD-CURRENT

ues? mixer -f /dev/mixerN Are you sure the volume is set high enough? --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"

USB microphones with FreeBSD-CURRENT

in@momh167-gjp4-8570p:~ % ___________ 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"

VirtualBox segmentation fault, 5.2.34_1 on FreeBSD-CURRENT r359249

.34_1 Mar 24 08:19:51 momh167-gjp4-8570p pkg[49646]: virtualbox-ose reinstalled: 5.2.34_1 -> 5.2.34_1 grahamperrin@momh167-gjp4-8570p:~ % grep -v \# /usr/local/etc/poudriere.d/make.conf WITHOUT_LLVM_TARGET_ALL= MESA_LLVM_VER=${LLVM_DEFAULT} grahamperrin@momh167-gjp4-8570p:~ % ______

Re: VirtualBox segmentation fault, FreeBSD-CURRENT r359068

e'll see if they're related or requires yet another PR. _______ 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: Running FreeBSD Current without performance penalties

ds, Ronald. _______ 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"

Running FreeBSD Current without performance penalties

Hello, Is there anything else that needs to be done besides building with `-DMALLOC_PRODUCTION` and `KERNCONF=GENERIC-NODEBUG` in order to build current and avoid any performance penalties due to debugging flags? ___ freebsd-current@freebsd.org

Re: freebsd-current Digest, Vol 832, Issue 4

d begin to a "sudden death", having XFCE in reserve. On 2019-10-10 14:00, freebsd-current-requ...@freebsd.org wrote: > Send freebsd-current mailing list submissions to >     freebsd-current@freebsd.org > > To subscribe or unsubscribe via the World Wide Web, visit >  

FreeBSD CURRENT buildworld in virtualbox guest crashes FreeBSD host

Please forgive the crosspost, I don't know where the problem actually belongs. For the last several months I've had a problem where doing a buildworld on FreeBSD CURRENT running as a virtualbox guest is crashing a the FreeBSD current host. This doesn't always happen, but there is

Re: Inability to build FreeBSD-current amd64

extensions -c /usr/src/contrib/llvm/tools/llvm-mca/Views/DispatchStatistics.cpp -o Views/DispatchStatistics.o error: unable to open output file 'Views/DispatchStatistics.o': 'No such file or directory' 1 error generated. *** Error code 1 I switched to the other computer wi

Re: Inability to build FreeBSD-current amd64

t. If you've posted the error you're getting, I've missed it, however. 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: Inability to build FreeBSD-current amd64

t from August 2, 2017, or try to build 12-STABLE from my 11.1-STABLE host. Would I do better to build amd64 or i386 from amd64 host? I presently have no FreeBSD i386 installation, only amd64. Tom _______ freebsd-current@freebsd.org mailing list https://li

Re: Inability to build FreeBSD-current amd64

d for llvm ports in certain ports builds, however, such as firefox and mesa. 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: Inability to build FreeBSD-current amd64

build. WITH_CLANG_EXTRAS worked back in July-August 2017, but it may have ballooned since then beyond FreeBSD buildability. Tom ___________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscri

  1   2   3   4   >