On 3/11/25 4:57 AM, Michael Cheponis wrote:
At the risk of sounding incredibly dumb...
Why not have malloc() set some shared state variable, say
malloc_initialized to true (stdbool.h) and have pthread_atfork() block
until malloc_initialized becomes true.
That would deadlock the whole proces
Are you sure this is not the HDMI audio from the graphics card?
Thanks to everone who pointed this out...
Well, I thought I was sure, but decided to check again
The graphics card is
nouveau0 at pci1 dev 0 function 0: vendor 10de product 1287 (rev. 0xa1)
nouveau0: NVIDIA GK208B (b06070b1)
whi
Paul Goyette wrote:
> OK, I'm lost. My brain can't seem to wrap itself around all of the
> pieces...
>
> My hardware is pretty standard, just an ASUS "STRIX" motherboard and
> a sound bar with USB power and stereo jack connected to Line-Out.
>
> As near as I can tell, all of the various devices
Date:Mon, 10 Mar 2025 09:07:44 -0700
From:Brian Buhrow
Message-ID: <202503101607.52ag7i3x023...@nfbcal.org>
| #!/bin/sh
| # Test retrieving command arguments by using numeric values.
|
| arg1=$1
| arg2=$2
| arg3=$3
| arg4=$4
| arg5=$5
| arg6=$6
| a
Hello. Okay. I've figured out my confusion. Thank you so much for
the help!
here are the corrected scripts that work as expected.
#!/bin/sh
# Test retrieving command arguments by using numeric values.
arg1=$1
arg2=$2
arg3=$3
arg4=$4
arg5=$5
arg6=$6
arg6=$6
arg7=$7
arg8=$8
arg9=$9
arg
>>Hello. A /bin/sh script I wrote about 10 years ago under NetBSD-5
>>broke under NetbSD-10.99.12. The issue seems to be a change in the way
>>command line arguments are assigned to the $number variables, i.e. $1,
>>$2, $3, etc.
>
>Looks to me like $11 is being interpreted as ${1}1. I wonder wha
Hello. A /bin/sh script I wrote about 10 years ago under NetBSD-5 broke under
NetbSD-10.99.12.
The issue seems to be a change in the way command line arguments are assigned
to
the $number variables, i.e. $1, $2, $3, etc.
I wrote two scripts, below, to illustrate the issue. Since the new (bad
>Hello. A /bin/sh script I wrote about 10 years ago under NetBSD-5
>broke under NetbSD-10.99.12. The issue seems to be a change in the way
>command line arguments are assigned to the $number variables, i.e. $1,
>$2, $3, etc.
Looks to me like $11 is being interpreted as ${1}1. I wonder what ${11
On Mon, Mar 10, 2025 at 09:35:18AM -0700, Brian Buhrow wrote:
> arg9=$9
> arg10=${10}
> arg10=${10}
> arg11=${11}
That part is good.
> echo "arg9 = $9"
> echo "arg10 = $10"
> echo "arg11 = $11"
But that part has no braces.
Martin
OK, I'm lost. My brain can't seem to wrap itself around all of the
pieces...
My hardware is pretty standard, just an ASUS "STRIX" motherboard and
a sound bar with USB power and stereo jack connected to Line-Out.
As near as I can tell, all of the various devices exist and are
accessible.
Here a
Hi,
On Mon, Mar 10, 2025 at 4:11 PM Paul Goyette wrote:
>
>
> (There's also a hdaudio1 for the display/monitor, but not expected
> to work since there are no embedded speakers.)
>
Are you sure audio1 is not for line out? The graphics card audio is
typically for HDMI. Line out uses some integrat
Hello. I've modified the test script, shown below, as indicated in the
examples.
However, I see no change. For the positional arguments 10 and 11, I should now
see:
testarg10 and testarg11 respectively. Yet I still see the value of $1 followed
by a 0 and 1
respectively.
Do I need t
Paul Goyette wrote:
> hdaudio1 at pci23 dev 0 function 1: HD Audio Controller
> hdafg1 at hdaudio1: ATI R6xx HDMI
> audio1 at hdafg1: playback
What CPU are you using? Does it have an integrated AMD GPU?
Does the motherboard manual state what kind of audio controller is
fitted?
Date:Tue, 11 Mar 2025 11:18:26 -0700
From:Michael Cheponis
Message-ID:
| I thought these were on separate threads?
The relevant calls are from the library constructors, run as part
of initialising the binary's environment, no user level code can
possibly have run
Date:Tue, 11 Mar 2025 15:06:25 -0700
From:Michael Cheponis
Message-ID:
| It's a function of the call order of the initializers, be they constructors
| or other routines that establish the runtime.
Yes. pthread_atfork() isn't a pthread function really, despite
Updating src tree:
P src/distrib/emips/ramdisk/Makefile
P src/distrib/sets/lists/base/mi
P src/distrib/sets/lists/comp/mi
P src/distrib/sets/lists/debug/mi
P src/distrib/sets/lists/debug/module.mi
P src/distrib/sets/lists/man/mi
P src/distrib/sets/lists/manhtml/mi
P src/distrib/sets/lists/modules
Thanks to all those who helped, I've had a good intro to the
audio subsystems.
Enough to figure out that my existing uaudio (an ALC4080) is not
well supported, and that there is no physicalk output for the
internal video-with-audio, and my display doesn't have any way
to play audio arriving in th
Paul Goyette wrote:
>On Mon, 10 Mar 2025, Robert Swindells wrote:
>> Does the motherboard manual state what kind of audio controller is
>> fitted?
>
> ALC4080? 7.1 surround sound
Look for a pci device that matches this in dmesg.boot.
On Mon, Mar 10, 2025 at 04:05:24PM +, Robert Swindells wrote:
> > ALC4080? 7.1 surround sound
>
> Look for a pci device that matches this in dmesg.boot.
Isn't that supposed to be a USB device?
Martin
19 matches
Mail list logo