Re: Advice on serial port communication
On Tue, 25 May 2021 08:29:52 -0700 Joseph Olatt wrote: [Accidentally dropped CC… re-sending] > Any advice on how I cat get to the U-Boot (which is what I presume you > mean by the "TI boot-loader") prompt? Nope, by "TI boot-loader", I mean "TI boot-loader", which is burned into a ROM that exists on the die of the SoC. It has no prompt: it just reads some GPIO pins, initialises the appropriate interface based on the pins it sees pulled high/low then goes hunting for a boot sector. U-Boot is the boot-loader it is failing to load in this case. -- Stuart Longland (aka Redhatter, VK4MSL) I haven't lost my mind... ...it's backed up on a tape somewhere.
Re: Advice on serial port communication
Hi Stuart, Thank you for responding. Please see my response/question below. On Tue, May 25, 2021 at 09:54:06AM +1000, Stuart Longland wrote: > On Tue, 25 May 2021 09:38:21 +1000 > Stuart Longland wrote: > > > Maybe it can't find the boot-loader? > > To clarify??? (yes, half asleep this morning)??? TI boot-loader cannot find > the OS boot-loader??? not that it can't find itself. So, I have actually tried to power up the device without pressing the button by the SD card reader. That also resulted in a bunch of "C"s. Any advice on how I cat get to the U-Boot (which is what I presume you mean by the "TI boot-loader") prompt? I am going to try to let the "C"s run for a lot longer and see if I can reach the boot prompt. Thank you, joseph > -- > Stuart Longland (aka Redhatter, VK4MSL) > > I haven't lost my mind... > ...it's backed up on a tape somewhere.
Re: Advice on serial port communication
Hi Joseph, I can confirm that if I hold down the BOOT button on the BBB and power up with no micro SD card in the slot, this is exactly what I see. Using a known good OpenBSD SD card in the slot, it boots as expected. HTH, David On 25/05/21 16:29, Joseph Olatt wrote: > Hi Stuart, > > Thank you for responding. > > Please see my response/question below. > > On Tue, May 25, 2021 at 09:54:06AM +1000, Stuart Longland wrote: >> On Tue, 25 May 2021 09:38:21 +1000 >> Stuart Longland wrote: >> >>> Maybe it can't find the boot-loader? >> >> To clarify??? (yes, half asleep this morning)??? TI boot-loader cannot find >> the OS boot-loader??? not that it can't find itself. > > So, I have actually tried to power up the device without pressing the > button by the SD card reader. That also resulted in a bunch of "C"s. > > Any advice on how I cat get to the U-Boot (which is what I presume you > mean by the "TI boot-loader") prompt? I am going to try to let the "C"s > run for a lot longer and see if I can reach the boot prompt. > > Thank you, > joseph > > >> -- >> Stuart Longland (aka Redhatter, VK4MSL) >> >> I haven't lost my mind... >> ...it's backed up on a tape somewhere. > >
Re: vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)
Hi Dave, You're right, name of VM is the same like in vm.conf. VM with different name starts correctly. But the message about 'operation already in progress' slightly confuses me. Martin ‐‐‐ Original Message ‐‐‐ On Tuesday, May 25, 2021 10:57 AM, Dave Voutila wrote: > Martin martin...@protonmail.com writes: > > > Try to start VM from previously (<6.9) working command as below: > > $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm > > Now I have trouble with it on 6.9amd64 with 1-5 patches installed. > > $ doas rcctl status vmd > > vmd(ok) > > command above returns: > > vmctl start: vm command failed: Operation already in progress > > Common cause of this is having the vm already defined in vm.conf. Run > vmd with verbose logging, ideally in the foreground, and please share > the output. > > > Even if "$ vmctl check" shows ALL machines are stopped > > if I stopped vmd I see proper error with non active vmd.sock > > $ doas rcctl stop vmd > > vmd(ok) > > vmctl: connect: /var/run/vmd.sock: connection refused
Re: aucat -c playback channels confusion
On Tue, May 25, 2021 at 03:45:17PM +0200, Jan Stary wrote: > This is current/amd64. I am trying to use the -c option of aucat, > specifying the channels to be played from a multichannel file. > > As an example, here is a quad audio file produced by sox: > > $ sox -n -b 16 quad.wav synth 10 sin 200 sin 300 sin 400 sin 600 gain -6 > $ soxi quad.wav > > Input File : 'quad.wav' > Channels : 4 > Sample Rate: 48000 > Precision : 16-bit > Duration : 00:00:10.00 = 48 samples ~ 750 CDDA sectors > File Size : 3.84M > Bit Rate : 3.07M > Sample Encoding: 16-bit Signed Integer PCM > > > Now trying to use aucat -c to play the individual channels > doesn't seem to do what it says: > > $ aucat -dd -c 0:0 -i quad.wav > quad.wav: skipped unknown chunk > quad.wav,pst=cfg: play, chan 0:3, 48000Hz, s16le, bytes 80..3840080, vol 32768 > default: 48000Hz, play 0:3, 36 blocks of 480 frames > quad.wav,pst=cfg: allocated 17280 frame buffer > cmap: nch = 4, ostart = 0, onext = 0, istart = 0, inext = 0 > quad.wav,pst=ini: chain initialized > quad.wav,pst=run: started > started > ^Cquad.wav,pst=ini: stopped > stopped > quad.wav,pst=ini: closed > > > Indeed quad.wav has channels 0:3, but why does auact play channels 0:3 > with -c 0:0 specified? Specifying other channels seem even more confusing: > > $ aucat -dd -c 2:2 -i quad.wav > quad.wav: skipped unknown chunk > quad.wav,pst=cfg: play, chan 2:5, 48000Hz, s16le, bytes 80..3840080, vol 32768 > default: 48000Hz, play 0:5, 36 blocks of 480 frames > quad.wav,pst=cfg: allocated 17280 frame buffer > cmap: nch = 4, ostart = 2, onext = 0, istart = 0, inext = 0 > quad.wav,pst=ini: chain initialized > quad.wav,pst=run: started > started > ^Cquad.wav,pst=ini: stopped > stopped > quad.wav,pst=ini: closed > > Now it considers quad.wav to have channels 2 to 5 > and it plays channels 0:5, given -c 2:2. > > Maybe I am misunderstanding the -c option > (or what the -dd messages say): > > -c min:max The range of audio file channel numbers. > The default is 0:1, i.e. stereo. > > When playing a file with aucat -i, does that mean > "use these channels from the file"? > > If not, how does one specify "play just channel 2, out of 0,1,2,3"? > > There is a chunk that aucat skips; this is what sndfile-info says: > > File : quad.wav > Length : 384080 > RIFF : 384072 > WAVE > fmt : 40 > Format: 0xFFFE => WAVE_FORMAT_EXTENSIBLE > Channels : 4 > Sample Rate : 48000 > Block Align : 8 > Bit Width : 16 > Bytes/sec : 384000 > Valid Bits: 16 > Channel Mask : 0x33 (L, R, Ls, Rs) > Subformat > esf_field1 : 0x1 > esf_field2 : 0x0 > esf_field3 : 0x10 > esf_field4 : 0x80 0x0 0x0 0xAA 0x0 0x38 0x9B 0x71 > format : pcm > fact : 4 > frames : 48000 > data : 384000 > End > > > Sample Rate : 48000 > Frames : 48000 > Channels: 4 > Format : 0x00130002 > Sections: 1 > Seekable: TRUE > Duration: 00:00:01.000 > Signal Max : 16424 (-6.00 dB) > > > With 1 second instead of 10 seconds of audio (synth 1) the file > is small enough, I am attaching it. > > Thanks for any clue. > Hi, The -c, -e, and -r options are used to specify file's channels, encoding and rate in case they are undefined, typically for raw data files. The .wav file header of quad.wav contains the number of channels (but not the initial channel). So, in your example, the number of channel is taken from the .wav header, that's why you hear all channels. The -c option is used only to determine the starting channel. For output .wav files -c make sense, though. For instance: aucat -n -i quad.wav -c 1:1 -o quad-1.wav extracts channel 1 into a mono file. Here -c 1:1 specifies channels selection of the output file. Then, playing quad-1.wav will, in turn, play channel 1 of the quad.wav file.
Re: email dkim signing failing with 6.8
Awesome!! This worked, thanks a lot! On 23/05/2021 14:57, Thomas Bohl wrote: Am 23.05.2021 um 12:32 schrieb flipchan: Yeah, it was all working until I upgraded to 6.8, can someone else that is running opensmtpd with dkim send me their smtpd.conf? I assume I have written some rule wrong, not sure where doe The config is all over the place. There is the rspamd filter and there is DKIM tagging with a match rules order that can't reach the tagging. It's like Martijn van Duren said, you are clearly using rspamd and not dkimproxy_out, which means your debugging is way off. But thinks got easier anyway. Please install filter-dkimsign. # pkg_add opensmtpd-filter-dkimsign Remove everything dkim and rspamd from your current smtpd.conf. Add filter "dkimsg" proc-exec "filter-dkimsign -d example.com -s default \ -k /var/dkimproxy/default.private -c relaxed/relaxed" \ user _dkimsign group _dkimsign and edit the line listen on vio0 port 587 hostname example.com tls-require pki mail.example.com auth filter "rspamd" to listen on vio0 port 587 hostname example.com tls-require pki mail.example.com auth filter "dkimsg" Or # cat /etc/mail/smtpd.conf table aliases file:/etc/mail/aliases pki mail.example.com cert "/etc/ssl/mail.example.com.crt" pki mail.example.com key "/etc/ssl/private/mail.example.com.key" filter "dkimsg" proc-exec "filter-dkimsign -d example.com -s default \ -k /var/dkimproxy/default.private -c relaxed/relaxed" \ user _dkimsign group _dkimsign listen on vio0 port 587 hostname example.com tls-require pki mail.example.com auth filter "dkimsg" listen on vio0 port 25 hostname example.com tls pki mail.example.com action "mbox" mbox alias action "relay" relay match from any for domain example.com action "mbox" match for local action "mbox" match auth from any for any action "relay" If you really need rspamd for spam filtering add it back in and add the filter only to "listen on vio0 port 25". Otherwise uninstall it, since even in "standby" it produces lots of DNS traffic. HTH
aucat -c playback channels confusion
This is current/amd64. I am trying to use the -c option of aucat, specifying the channels to be played from a multichannel file. As an example, here is a quad audio file produced by sox: $ sox -n -b 16 quad.wav synth 10 sin 200 sin 300 sin 400 sin 600 gain -6 $ soxi quad.wav Input File : 'quad.wav' Channels : 4 Sample Rate: 48000 Precision : 16-bit Duration : 00:00:10.00 = 48 samples ~ 750 CDDA sectors File Size : 3.84M Bit Rate : 3.07M Sample Encoding: 16-bit Signed Integer PCM Now trying to use aucat -c to play the individual channels doesn't seem to do what it says: $ aucat -dd -c 0:0 -i quad.wav quad.wav: skipped unknown chunk quad.wav,pst=cfg: play, chan 0:3, 48000Hz, s16le, bytes 80..3840080, vol 32768 default: 48000Hz, play 0:3, 36 blocks of 480 frames quad.wav,pst=cfg: allocated 17280 frame buffer cmap: nch = 4, ostart = 0, onext = 0, istart = 0, inext = 0 quad.wav,pst=ini: chain initialized quad.wav,pst=run: started started ^Cquad.wav,pst=ini: stopped stopped quad.wav,pst=ini: closed Indeed quad.wav has channels 0:3, but why does auact play channels 0:3 with -c 0:0 specified? Specifying other channels seem even more confusing: $ aucat -dd -c 2:2 -i quad.wav quad.wav: skipped unknown chunk quad.wav,pst=cfg: play, chan 2:5, 48000Hz, s16le, bytes 80..3840080, vol 32768 default: 48000Hz, play 0:5, 36 blocks of 480 frames quad.wav,pst=cfg: allocated 17280 frame buffer cmap: nch = 4, ostart = 2, onext = 0, istart = 0, inext = 0 quad.wav,pst=ini: chain initialized quad.wav,pst=run: started started ^Cquad.wav,pst=ini: stopped stopped quad.wav,pst=ini: closed Now it considers quad.wav to have channels 2 to 5 and it plays channels 0:5, given -c 2:2. Maybe I am misunderstanding the -c option (or what the -dd messages say): -c min:max The range of audio file channel numbers. The default is 0:1, i.e. stereo. When playing a file with aucat -i, does that mean "use these channels from the file"? If not, how does one specify "play just channel 2, out of 0,1,2,3"? There is a chunk that aucat skips; this is what sndfile-info says: File : quad.wav Length : 384080 RIFF : 384072 WAVE fmt : 40 Format: 0xFFFE => WAVE_FORMAT_EXTENSIBLE Channels : 4 Sample Rate : 48000 Block Align : 8 Bit Width : 16 Bytes/sec : 384000 Valid Bits: 16 Channel Mask : 0x33 (L, R, Ls, Rs) Subformat esf_field1 : 0x1 esf_field2 : 0x0 esf_field3 : 0x10 esf_field4 : 0x80 0x0 0x0 0xAA 0x0 0x38 0x9B 0x71 format : pcm fact : 4 frames : 48000 data : 384000 End Sample Rate : 48000 Frames : 48000 Channels: 4 Format : 0x00130002 Sections: 1 Seekable: TRUE Duration: 00:00:01.000 Signal Max : 16424 (-6.00 dB) With 1 second instead of 10 seconds of audio (synth 1) the file is small enough, I am attaching it. Thanks for any clue. Jan
vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)
Hi list, Try to start VM from previously (<6.9) working command as below: $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm Now I have trouble with it on 6.9amd64 with 1-5 patches installed. $ doas rcctl status vmd vmd(ok) command above returns: vmctl start: vm command failed: Operation already in progress Even if "$ vmctl check" shows ALL machines are stopped if I stopped vmd I see proper error with non active vmd.sock $ doas rcctl stop vmd vmd(ok) vmctl: connect: /var/run/vmd.sock: connection refused Any suggestions can help. Martin
Re: vmctl start: vm command failed: Operation already in progress (no one VM run in the same time)
Martin writes: > Try to start VM from previously (<6.9) working command as below: > > $ doas /usr/sbin/vmctl start -m 8G -c -n vmlan -d /path/to/vm.qcow2 vm > > Now I have trouble with it on 6.9amd64 with 1-5 patches installed. > > $ doas rcctl status vmd > vmd(ok) > > command above returns: > vmctl start: vm command failed: Operation already in progress Common cause of this is having the vm already defined in vm.conf. Run vmd with verbose logging, ideally in the foreground, and please share the output. > > Even if "$ vmctl check" shows ALL machines are stopped > > if I stopped vmd I see proper error with non active vmd.sock > $ doas rcctl stop vmd > vmd(ok) > > vmctl: connect: /var/run/vmd.sock: connection refused >
