/usr/src/sys/dev/pci/pcidevs enigma
Hello misc@, I seek help solving the below mystery. Thank you all in advance. On two amd64 hosts that have the same change (add 0xc158 support) in file /usr/src/sys/dev/pci/pcidevs, host z97st executes 'make' in directory /usr/src/sys/dev/pci, whilst host gx470 reports an error w.r.t. the same change (see below). NB: The user prompt on both hosts is split over two lines. The gx470 /var/run/dmesg.boot is appended last below. gx470 host info gx470://usr/src/sys/dev/pci $ date Tue Aug 3 13:24:08 NZST 2021 gx470://usr/src/sys/dev/pci $ sysctl kern.version kern.version=OpenBSD 6.9-current (GENERIC.MP) #159: Sun Aug 1 08:49:29 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP gx470://usr/src/sys/dev/pci $ ls -la /usr/src total 120 drwxrwxr-x 17 root wsrc 512 Aug 3 11:31 . drwxr-xr-x 19 root wheel512 Aug 2 03:22 .. -rw-rw-r--1 aer wsrc 7 May 26 07:06 .gitignore drwxrwxr-x2 aer wsrc 512 Aug 3 11:31 CVS -rw-rw-r--1 aer wsrc3639 Apr 6 2020 Makefile -rw-rw-r--1 aer wsrc 16103 May 3 12:04 Makefile.cross gx470://usr/src/sys/dev/pci $ grep -e PCIE952 pcidevs product OXFORD2 OXPCIE952 0xc110 OXPCIE952 Parallel product OXFORD2 OXPCIE952S 0xc120 OXPCIE952 Serial product OXFORD2 OXPCIE952S_10xc158 OXPCIE952 Serial gx470://usr/src/sys/dev/pci $ touch pcidevs gx470://usr/src/sys/dev/pci $ make /bin/rm -f pcidevs.h pcidevs_data.h awk -f devlist2h.awk pcidevs awk: can't open file devlist2h.awk source line number 1 source file devlist2h.awk *** Error 2 in /usr/src/sys/dev/pci (Makefile:8 'pcidevs.h') gx470://usr/src/sys/dev/pci $ ls -lo Makefile devlist2h.awk pcidevs -rw-rw-r-- 1 aer wsrc -246 Oct 14 1996 Makefile -rw-rw-r-- 1 aer wsrc - 5934 Feb 22 2007 devlist2h.awk -rw-rw-r-- 1 aer wsrc - 385130 Aug 3 13:44 pcidevs z97st host info z97st://usr/src/sys/dev/pci $ date Tue Aug 3 13:37:33 NZST 2021 z97st://usr/src/sys/dev/pci $ sysctl kern.version kern.version=OpenBSD 6.9-current (GENERIC.MP) #159: Sun Aug 1 08:49:29 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP z97st://usr/src/sys/dev/pci $ ls -la /usr/src total 120 drwxrwxr-x 17 root wsrc 512 Jul 27 09:47 . drwxr-xr-x 19 root wheel512 Aug 2 03:22 .. -rw-rw-r--1 aer wsrc 7 May 26 07:06 .gitignore drwxrwxr-x2 aer wsrc 512 Jul 27 09:47 CVS -rw-rw-r--1 aer wsrc3639 Apr 6 2020 Makefile -rw-rw-r--1 aer wsrc 16103 May 3 12:04 Makefile.cross z97st://usr/src/sys/dev/pci $ grep -e PCIE952 pcidevs product OXFORD2 OXPCIE952 0xc110 OXPCIE952 Parallel product OXFORD2 OXPCIE952S 0xc120 OXPCIE952 Serial product OXFORD2 OXPCIE952S_10xc158 OXPCIE952 Serial z97st://usr/src/sys/dev/pci $ make /bin/rm -f pcidevs.h pcidevs_data.h awk -f devlist2h.awk pcidevs z97st://usr/src/sys/dev/pci $ ls -lo Makefile devlist2h.awk pcidevs -rw-rw-r-- 1 aer wsrc -246 Oct 14 1996 Makefile -rw-rw-r-- 1 aer wsrc - 5934 Feb 22 2007 devlist2h.awk -rw-rw-r-- 1 aer wsrc - 385130 Aug 3 13:43 pcidevs Run diff against files. rsync -av ... commands were used to get the above 3 files from each host into the same directory to enable diff to be easily run against them. Host z97st files then had their host ID appended to them. gx470://home/aer/tmp $ ls -l Make* devlist* pcidev* -rw-rw-r-- 1 aer wsrc 246 Oct 14 1996 Makefile -rw-rw-r-- 1 aer wsrc 246 Oct 14 1996 Makefile.z97st -rw-rw-r-- 1 aer wsrc5934 Feb 22 2007 devlist2h.awk -rw-rw-r-- 1 aer wsrc5934 Feb 22 2007 devlist2h.awk.z97st -rw-rw-r-- 1 aer wsrc 385130 Aug 3 13:44 pcidevs -rw-rw-r-- 1 aer wsrc 385130 Aug 3 13:43 pcidevs.z97st gx470://home/aer/tmp $ diff Makefile Makefile.z97st gx470://home/aer/tmp $ diff devlist2h.awk devlist2h.awk.z97st gx470://home/aer/tmp $ diff pcidevs pcidevs.z97st gx470://home/aer/tmp OpenBSD 6.9-current (GENERIC.MP) #159: Sun Aug 1 08:49:29 MDT 2021 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68647477248 (65467MB) avail mem = 66551033856 (63468MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe8980 (59 entries) bios0: vendor American Megatrends Inc. version "F2" date 03/14/2018 bios0: Gigabyte Technology Co., Ltd. X470 AORUS ULTRA GAMING acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT SSDT SSDT CRAT CDIT SSDT MCFG HPET SSDT UEFI BGRT IVRS SSDT SSDT WSMT acpi0: wakeup devices GPP0(S4) GPP1(S4) GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GPP7(S4) GPP8(S4) GPP9(S4) GPPA(S4) GPPB(S4) GPPC(S4) GPPD(S4) GPPE(S4) GPPF(S4) GP17(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 7 2700X Eight-Core Processor, 3700.62 MHz, 17-08-02 cpu0:
Re: nmea/udcf recommendation
Sounds like a good driver to learn from for driver dev stuff. On 8/2/2021 6:11 PM, Christian Weisgerber wrote: > Jan Stary: > >> playing with ntpd a bit, I am looking for a working >> nmea or udcf sensor. Can people please recommend >> an easy to use device known to work? > The Gude mouseCLOCKs were discontinued years ago, so I don't think > you could buy any udcf(4) hardware even if you wanted to, and udcf > is literally the most stupid device possible. Don't believe me? > The hardware supplies a single bit of information that needs to be > polled for changes. In practice, it is read by the kernel at HZ > (= 100 on most archs) times per second, limiting the precision > correspondingly. From ntpd's point of view, a udcf sensor will > frequently jump back and forth by 10 ms. ntpd's frequency correction > is effectively a differentiator, which is not very happy with jumps. > I mean, you can keep time with it, but it's just poor compared to > the ~1 ms precision you get from public NTP servers on the Internet. > > I don't have any practical experience with nmea(4), but I'd like > to draw attention to ldattach(8)'s -t option. Unless your receiver > offers a pulse per second signal, you are limited to a very jittery > timestamp from the serial telegram, mirroring udcf's fundamental > problem. The last time I looked--admittedly it's been a few years-- > if you wanted to have a PPS on a serial port, you had to get some > industrial GPS module and do your own soldering. And you can't do > it over USB. Also, GPS doesn't work well indoors and mounting a > roof antenna presumably does not qualify as "easy to use". > > Basically, OpenBSD does not support any useful sensor devices unless > you are desperate and need to keep time in a remote mountain cabin > without Internet access. >
Re: nmea/udcf recommendation
Jan Stary: > playing with ntpd a bit, I am looking for a working > nmea or udcf sensor. Can people please recommend > an easy to use device known to work? The Gude mouseCLOCKs were discontinued years ago, so I don't think you could buy any udcf(4) hardware even if you wanted to, and udcf is literally the most stupid device possible. Don't believe me? The hardware supplies a single bit of information that needs to be polled for changes. In practice, it is read by the kernel at HZ (= 100 on most archs) times per second, limiting the precision correspondingly. From ntpd's point of view, a udcf sensor will frequently jump back and forth by 10 ms. ntpd's frequency correction is effectively a differentiator, which is not very happy with jumps. I mean, you can keep time with it, but it's just poor compared to the ~1 ms precision you get from public NTP servers on the Internet. I don't have any practical experience with nmea(4), but I'd like to draw attention to ldattach(8)'s -t option. Unless your receiver offers a pulse per second signal, you are limited to a very jittery timestamp from the serial telegram, mirroring udcf's fundamental problem. The last time I looked--admittedly it's been a few years-- if you wanted to have a PPS on a serial port, you had to get some industrial GPS module and do your own soldering. And you can't do it over USB. Also, GPS doesn't work well indoors and mounting a roof antenna presumably does not qualify as "easy to use". Basically, OpenBSD does not support any useful sensor devices unless you are desperate and need to keep time in a remote mountain cabin without Internet access. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: Regarding Openbsd and zoom/hangouts etc
My apologies Theo. On Mon, Aug 2, 2021, at 14:14, Theo de Raadt wrote: > Jonathan Drews wrote: > > > Zoom won't owrk on OpenBSD. > > That is incorrect. > > > Howvever jitsi works great. > > It wasn't a question about jitsi. >
Re: Regarding Openbsd and zoom/hangouts etc
Jonathan Drews wrote: > Zoom won't owrk on OpenBSD. That is incorrect. > Howvever jitsi works great. It wasn't a question about jitsi.
Re: Regarding Openbsd and zoom/hangouts etc
Zoom works just fine. Again I use it on a daily basis for work on chromium and even screen sharing works great. — Antoine > On 2 Aug 2021, at 20:55, Jonathan Drews wrote: > > On Mon, Aug 02, 2021 at 07:04:47PM +0300, Riza Dindir wrote: >> Hello, >> >> I amthinking of using openbsd as my OS, and desktop, giving up windows, >> after I am having trouble updating the system. >> >> I have a question. Is it possible to use zoom, hangouts or other >> conferencing/communication systems using the browser >> (iridium/chrome/firefox, etc) on openbsd? >> > Hi; > > Zoom won't owrk on OpenBSD. You can go their test page and try it for > yourself https://zoom.us/test . Howvever jitsi works great. > > Here are my notes on configuring audio and video on OpenBSD, so it > willwork with jitsi. https://meet.jit.si/ > > The primary reference is: > > https://www.openbsd.org/faq/faq13.html > in addition to the man pages. > To get audio and video working on OpenBSD: > > Add yourself to group wheel in /etc/group. Do as root: > # chmod g+rw /dev/video0 > or whatever your video device is. Find it in dmesg. > > In /etc/sysctl.conf (file is in /etc/examples) add: > > kern.audio.record=1 > kern.video.record=1 > > Add the following lines to /etc/mixerctl.conf (mixerctl.conf > is in /etc/examples). > > # $OpenBSD: mixerctl.conf,v 1.1 2014/07/16 13:21:33 deraadt Exp $ > # > # mixerctl(1) configurable parameters. See mixerctl.conf(5) for > details. > # > > # output volume value for most audio cards > # outputs.master=200 > record.enable=on > > You'll have to experiment as your laptop may not have the same > entries as my mixerctl.conf. Invariably they should begin with > "record." Do # mixerctl -av to find the settings > > As an aid in getting your microphone to work use aucat (see man 1 > aucat). > To do a test recoding do: > $ aucat -o test.wav > to play back the rscording, to see if your microphone is working do: > $ aucat -i test.wav > > I have used Jitsi several times from my OpenBSD T420 Laptop. The > only difficulty was sharing my desktop. Firefox froze when doing > that. My guess is that happens because of pledge. Video and audio > worked great. Response times can be bad if you use Jitsi over WiFi. > I switched to ethernet and my signal strength improved. > > To adjust the volume of the microphone and speakers use cmixer. > cmixer is in packages. > > > Kind regards, > Jonathan >
Re: Regarding Openbsd and zoom/hangouts etc
On Mon, Aug 02, 2021 at 07:04:47PM +0300, Riza Dindir wrote: > Hello, > > I amthinking of using openbsd as my OS, and desktop, giving up windows, > after I am having trouble updating the system. > > I have a question. Is it possible to use zoom, hangouts or other > conferencing/communication systems using the browser > (iridium/chrome/firefox, etc) on openbsd? > Hi; Zoom won't owrk on OpenBSD. You can go their test page and try it for yourself https://zoom.us/test . Howvever jitsi works great. Here are my notes on configuring audio and video on OpenBSD, so it willwork with jitsi. https://meet.jit.si/ The primary reference is: https://www.openbsd.org/faq/faq13.html in addition to the man pages. To get audio and video working on OpenBSD: Add yourself to group wheel in /etc/group. Do as root: # chmod g+rw /dev/video0 or whatever your video device is. Find it in dmesg. In /etc/sysctl.conf (file is in /etc/examples) add: kern.audio.record=1 kern.video.record=1 Add the following lines to /etc/mixerctl.conf (mixerctl.conf is in /etc/examples). # $OpenBSD: mixerctl.conf,v 1.1 2014/07/16 13:21:33 deraadt Exp $ # # mixerctl(1) configurable parameters. See mixerctl.conf(5) for details. # # output volume value for most audio cards # outputs.master=200 record.enable=on You'll have to experiment as your laptop may not have the same entries as my mixerctl.conf. Invariably they should begin with "record." Do # mixerctl -av to find the settings As an aid in getting your microphone to work use aucat (see man 1 aucat). To do a test recoding do: $ aucat -o test.wav to play back the rscording, to see if your microphone is working do: $ aucat -i test.wav I have used Jitsi several times from my OpenBSD T420 Laptop. The only difficulty was sharing my desktop. Firefox froze when doing that. My guess is that happens because of pledge. Video and audio worked great. Response times can be bad if you use Jitsi over WiFi. I switched to ethernet and my signal strength improved. To adjust the volume of the microphone and speakers use cmixer. cmixer is in packages. Kind regards, Jonathan
Re: Regarding Openbsd and zoom/hangouts etc
That would be ENABLE_WASM=yes On Mon, 2021-08-02 at 20:09 +0200, Antoine Jacoutot wrote: > Hi. > > Zoom works in chromium, I now use it on a daily basis. You need to enable > audio and video record using sysctl, change /dev/video0 ownership to your > user and activate web assembly in chromium (just a > matter of exporting a variable which I don’t remember the name right now). > > Cheers! > > — > Antoine > > > On 2 Aug 2021, at 18:23, Riza Dindir wrote: > > > > Hello, > > > > I amthinking of using openbsd as my OS, and desktop, giving up windows, > > after I am having trouble updating the system. > > > > I have a question. Is it possible to use zoom, hangouts or other > > conferencing/communication systems using the browser > > (iridium/chrome/firefox, etc) on openbsd? > > > > Kind Regards, > > Riza Dindir >
Re: Regarding Openbsd and zoom/hangouts etc
Hi. Zoom works in chromium, I now use it on a daily basis. You need to enable audio and video record using sysctl, change /dev/video0 ownership to your user and activate web assembly in chromium (just a matter of exporting a variable which I don’t remember the name right now). Cheers! — Antoine > On 2 Aug 2021, at 18:23, Riza Dindir wrote: > > Hello, > > I amthinking of using openbsd as my OS, and desktop, giving up windows, > after I am having trouble updating the system. > > I have a question. Is it possible to use zoom, hangouts or other > conferencing/communication systems using the browser > (iridium/chrome/firefox, etc) on openbsd? > > Kind Regards, > Riza Dindir
Re: Regarding Openbsd and zoom/hangouts etc
On Aug 02 19:04:47, riza.din...@gmail.com wrote: > I have a question. Is it possible to use zoom, hangouts or other > conferencing/communication systems using the browser > (iridium/chrome/firefox, etc) on openbsd? I have used the web version of google meet and ms teams in chrome. Jan
nmea/udcf recommendation
Hello, playing with ntpd a bit, I am looking for a working nmea or udcf sensor. Can people please recommend an easy to use device known to work? Jan
Regarding Openbsd and zoom/hangouts etc
Hello, I amthinking of using openbsd as my OS, and desktop, giving up windows, after I am having trouble updating the system. I have a question. Is it possible to use zoom, hangouts or other conferencing/communication systems using the browser (iridium/chrome/firefox, etc) on openbsd? Kind Regards, Riza Dindir
