Re: The spkr driver
Appreciate the notice Warner. :) Yes, I use it on various devices: - as a clock signal to indicate the time, different pitch each 1/4 & hour (aka a chiming clock, very useful when busy) - advice when a box has completed booting - advice when snort (& others) thinks there's a problem using different duration and pitch. I'm Pavlovian trained. audio/beep and audio/yell are good friends that need their benefactor Mr Speaker to remain alive, please. ;) I'm rarely current but always stable (12.1), happy to test (on: Haswell, Nehalem, Nehemiah (32bit)) Regards. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
> On 28. Aug 2020, at 21:00, Charles Sprickman via freebsd-stable > wrote: > > > >>> On Aug 28, 2020, at 12:36 PM, Eugene Grosbein wrote: >>> >>> 28.08.2020 23:25, Warner Losh wrote: >>> >>> I'd like to retire the spkr driver. It was a cute hack before sound cards >>> were ubiquitous, but it's not been kept up to date, and it's not clear that >>> it still works It is still Giant locked, and though it's not a huge >>> effort to do the locking I literally have no way to test it that I trust... >>> >>> Is anybody using it these days for anything? If not, I'd propose we >>> de-orbit it before 13. If so, I need people to test patches to remove >>> Giant... >> >> spkr works just fine in my stable/11 systems. I use it for routers on modern >> fanless hardware >> to audio signalling like successfull completition of reboot (going to >> multi-user mode). > > Is this what pfsense/opnsense uses for the “booting complete” signal as well? > > If so, it’s very handy. Yes, please keep it if possible - especially for servers without other sound equipment attached it is very useful. I‘m usually not that much into testing but I could reactivate two little servers I have at home and test in my spare time if that helps. Thanx! Holger > Charles > >> >> I'd like to keep it working. I'm ready to test patches. However, my CURRENT >> system lives in bhyve for the moment. >> Though, I could try running CURRENT with one of my less important wireless >> AP systems built as NanoBSD, >> so I can build and boot CURRENT-based image. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
Hi, > On 28 Aug 2020, at 19:47, Kurt Jaeger wrote: > > Hi! > >> I'd like to retire the spkr driver. It was a cute hack before sound cards >> were ubiquitous, but it's not been kept up to date, and it's not clear that >> it still works It is still Giant locked, and though it's not a huge >> effort to do the locking I literally have no way to test it that I trust... > > It works on PC Engines APU devices, and together with morse, it's > very, very cool 8-} > > So, please keep it and un-giant it, if possible. What he said. I’d be happy to test changes. > -- > p...@opsec.eu+49 171 3101372Now what ? -- Bob Bishop r...@gid.co.uk ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
29.08.2020 1:59, Charles Sprickman wrote: >> spkr works just fine in my stable/11 systems. I use it for routers on modern >> fanless hardware >> to audio signalling like successfull completition of reboot (going to >> multi-user mode). > > Is this what pfsense/opnsense uses for the “booting complete” signal as well? Can't tell (never used pfsense/opnsense), but possible. > If so, it’s very handy. Yes, it is. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
> On Aug 28, 2020, at 12:36 PM, Eugene Grosbein wrote: > > 28.08.2020 23:25, Warner Losh wrote: > >> I'd like to retire the spkr driver. It was a cute hack before sound cards >> were ubiquitous, but it's not been kept up to date, and it's not clear that >> it still works It is still Giant locked, and though it's not a huge >> effort to do the locking I literally have no way to test it that I trust... >> >> Is anybody using it these days for anything? If not, I'd propose we >> de-orbit it before 13. If so, I need people to test patches to remove >> Giant... > > spkr works just fine in my stable/11 systems. I use it for routers on modern > fanless hardware > to audio signalling like successfull completition of reboot (going to > multi-user mode). Is this what pfsense/opnsense uses for the “booting complete” signal as well? If so, it’s very handy. Charles > > I'd like to keep it working. I'm ready to test patches. However, my CURRENT > system lives in bhyve for the moment. > Though, I could try running CURRENT with one of my less important wireless AP > systems built as NanoBSD, > so I can build and boot CURRENT-based image. > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
Hi! > I'd like to retire the spkr driver. It was a cute hack before sound cards > were ubiquitous, but it's not been kept up to date, and it's not clear that > it still works It is still Giant locked, and though it's not a huge > effort to do the locking I literally have no way to test it that I trust... It works on PC Engines APU devices, and together with morse, it's very, very cool 8-} So, please keep it and un-giant it, if possible. -- p...@opsec.eu+49 171 3101372Now what ? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
On 2020-08-28 09:25, Warner Losh wrote: Greetings, I'd like to retire the spkr driver. It was a cute hack before sound cards were ubiquitous, but it's not been kept up to date, and it's not clear that it still works It is still Giant locked, and though it's not a huge effort to do the locking I literally have no way to test it that I trust... Is anybody using it these days for anything? If not, I'd propose we de-orbit it before 13. If so, I need people to test patches to remove Giant... I still use it for important events, as alerts that something needs attention on any one of my servers. It's easier to distinguish, and while many boards include more complex sound. The speaker is "cheap" and easy to use. I should be able to help test. Thanks for the heads-up! --Chris Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: The spkr driver
28.08.2020 23:25, Warner Losh wrote: > I'd like to retire the spkr driver. It was a cute hack before sound cards > were ubiquitous, but it's not been kept up to date, and it's not clear that > it still works It is still Giant locked, and though it's not a huge > effort to do the locking I literally have no way to test it that I trust... > > Is anybody using it these days for anything? If not, I'd propose we > de-orbit it before 13. If so, I need people to test patches to remove > Giant... spkr works just fine in my stable/11 systems. I use it for routers on modern fanless hardware to audio signalling like successfull completition of reboot (going to multi-user mode). I'd like to keep it working. I'm ready to test patches. However, my CURRENT system lives in bhyve for the moment. Though, I could try running CURRENT with one of my less important wireless AP systems built as NanoBSD, so I can build and boot CURRENT-based image. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
The spkr driver
Greetings, I'd like to retire the spkr driver. It was a cute hack before sound cards were ubiquitous, but it's not been kept up to date, and it's not clear that it still works It is still Giant locked, and though it's not a huge effort to do the locking I literally have no way to test it that I trust... Is anybody using it these days for anything? If not, I'd propose we de-orbit it before 13. If so, I need people to test patches to remove Giant... Warner ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
How prevent GEOM providers to use adaX labels?
Hello. I have two disk with next partitions: #gpart show => 40 11721045088 ada0 GPT (5.5T) 40 1024 1 freebsd-boot (512K) 1064 16777216 2 freebsd-swap (8.0G) 16778280 11704266848 3 freebsd-zfs (5.5T) => 40 11721045088 ada1 GPT (5.5T) 40 1024 1 freebsd-boot (512K) 1064 16777216 2 freebsd-swap (8.0G) 16778280 11704266848 3 freebsd-zfs (5.5T) Then these partitions are combined on GEOM and ZFS mirrors: #gmirror status NameStatus Components mirror/swap COMPLETE ada0p2 (ACTIVE) ada1p2 (ACTIVE) #zpool status pool: zroot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 841G in 0 days 01:26:32 with 0 errors on Sat Jan 11 18:41:40 2020 config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 errors: No known data errors I try to change using adaX labels to diskid labels on both mirrors: first I disabled load gmirror via boot/loader.conf and etc/fstab, then i boot from live-cd and import/export zfs pool: ... #zpool import -d /dev/diskid -o altroot=/tmp/zroot zroot #zpool export #reboot After reboot to normal mode I see, that zpool change their adaX labels to diskid labels: #zpool status pool: zroot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 841G in 0 days 01:26:32 with 0 errors on Sat Jan 11 18:41:40 2020 config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 diskid/DISK-SERIAL1p3 ONLINE 0 0 0 diskid/DISK-SERIAL2p3 ONLINE 0 0 0 errors: No known data errors Then I've destroying gmirror and re-created it with diskid labels: #gmirror destroy swap #gmirror label -v -b round-robin swap diskid/DISK-SERIAL1p2 #gmirror insert swap diskid/DISK-SERIAL2p2 #gmirror status NameStatus Components mirror/swap COMPLETE diskid/DISK-SERIAL1p2 (ACTIVE) diskid/DISK-SERIAL2p2 (ACTIVE) But after I've re-enabled gmirror in boot/loader.conf and /etc/fstab and rebooted, I've see adaX labels on both mirrors: #gmirror status NameStatus Components mirror/swap COMPLETE ada0p2 (ACTIVE) ada1p2 (ACTIVE) #zpool status pool: zroot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 841G in 0 days 01:26:32 with 0 errors on Sat Jan 11 18:41:40 2020 config: NAMESTATE READ WRITE CKSUM zroot ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 ada0p3 ONLINE 0 0 0 ada1p3 ONLINE 0 0 0 errors: No known data errors It look's like gmirror loaded before zfs and use search gmirror on adaX first instead diskid labels. Is there a way to prevent gmirror use adaX labels? #uname -rv 12.1-STABLE FreeBSD 12.1-STABLE r361496 GENERIC #sysctl kern.geom.label kern.geom.label.disk_ident.enable: 1 kern.geom.label.gptid.enable: 1 kern.geom.label.gpt.enable: 1 kern.geom.label.ufs.enable: 1 kern.geom.label.ufsid.enable: 1 kern.geom.label.reiserfs.enable: 1 kern.geom.label.ntfs.enable: 1 kern.geom.label.msdosfs.enable: 1 kern.geom.label.iso9660.enable: 1 kern.geom.label.flashmap.enable: 1 kern.geom.label.ext2fs.enable: 1 kern.geom.label.debug: 0 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
