Re: ugold(4) temperature and humidity entries disappeared from sysctl hw.sensors

. Still don't understand why this was at all required and why several snapshot upgrades, and reboots, didn't resolve the issue :^/ Either way, sorry for the noise. Cheers, Raf On Thu, Jun 27, 2024 at 09:12:14AM BST, Raf Czlonka wrote: > >Synopsis:ugold(4) temperature and humidity e

ugold(4) temperature and humidity entries disappeared from sysctl hw.sensors

>Synopsis: ugold(4) temperature and humidity entries disappeared from >sysctl hw.sensors >Category: system kernel >Environment: System : OpenBSD 7.5 Details : OpenBSD 7.5-current (GENERIC.MP) #152: Wed Jun 26 20:42:02 MDT 2024

Re: fix closing tag in plus75.html

On Wed, Apr 10, 2024 at 02:17:24AM BST, Ryan Freeman wrote: > Hi, this fixes the closing tag on the -current line. > > -ryan > > 18:14 ryan@build-amd64:/usr/src/www$ cvs diff -uNp plus75.html > Index: plus75.html > === > RCS file:

Re: lost ugold humidity sensor after upgrade

FWIW, it now works here, too :^) Thanks for a prompt fix, Miod! Cheers, Raf On Tue, Apr 18, 2023 at 08:40:14PM BST, Paul de Weerd wrote: > On Tue, Apr 18, 2023 at 03:52:02PM +, Miod Vallat wrote: > | > After updating my RPi4 to a newer snap, it lost its humidity sensor. > | > > | > dmesg

Re: lost ugold humidity sensor after upgrade

On Tue, Apr 18, 2023 at 08:56:46AM BST, Paul de Weerd wrote: > After updating my RPi4 to a newer snap, it lost its humidity sensor. > > dmesg from before and after the update both detect this: > > uhidev1 at uhub1 port 2 configuration 1 interface 1 "RDing TEMPERHUM1V1.2" > rev 2.00/0.01 addr 3

[OT] RFC0123 vs RFC 0123 [Was: Re: unwind ignores 'force' directive for zone home.arpa]

On Tue, Feb 07, 2023 at 12:15:25PM GMT, Theo Buehler wrote: > > > + > > + /* RFC 8375 */ > > All other comments do not have a space after RFC RFC 7322 (RFC Style Guide), whilst it only applies to RFCs themselves, reads[0]: However, the proper textual naming of an RFC contains a

Re: Picard Error

On Wed, Feb 09, 2022 at 03:28:08PM GMT, Rasmus Liland wrote: > Hi! Maybe try installing it locally > through pip [1] > > pip3.10 install picard > > or maybe try installing py-yaml [2] ? Hi Rasmus, This has been both: already addressed[0] on ports@, as well as fixed in tree[1]. [0]

Re: apm not responding

Hello, There's quite a bit to unpick here - some errors, some assumptions. On Tue, Feb 08, 2022 at 04:50:55AM GMT, u...@mailo.com wrote: > > Noticed that my laptop ThinkPad T530 doesn't hibernate: > > ZZZ > Hibernating system... > > blinking cursor and nothing more, equal outcome with regular

Re: ASUS ZenBook S: SSD unrecognized, possible new iwx variant

On Wed, Jun 02, 2021 at 09:52:36AM BST, Alexandre Ratchov wrote: > > There's no hotplug support for audio (yet), so if you plug the USB > device while programs are using the internal device, you need to > manually tell sndiod to switch to it, ex: Until then, hotplugd(8) seems to be working just

Re: dhcplease fails to acquire a lease with a trunk interface

On Sat, Mar 06, 2021 at 08:59:16AM GMT, Florian Obser wrote: > On Sat, Mar 06, 2021 at 06:41:44AM +, Adam Steen wrote: > > >Synopsis: dhcpleased does not acquire a lease > > >Category: networking > > >Environment: > > System : OpenBSD 6.9 > > Details : OpenBSD 6.9-beta

Re: Fwd: Re: ssh_config(5) ProxyJump option not working in the latest snapshot

Thanks for sorting it all out, fellas! Raf On Mon, Dec 21, 2020 at 11:10:03PM GMT, Damien Miller wrote: > ugh, that's embarassing > > ok & thanks djm > > On Mon, 21 Dec 2020, Theo Buehler wrote: > > > On Mon, Dec 21, 2020 at 10:15:33AM +0100, Theo Buehler wrote: > > > On Mon, Dec 21, 2020 at

ssh_config(5) ProxyJump option not working in the latest snapshot

Hello, ssh_config(5) "ProxyJump" option stopped working after upgrading to the latest snapshot: Build date: 1608330967 - Fri Dec 18 22:36:07 UTC 2020 OpenBSD 6.8-current (GENERIC.MP) #230: Fri Dec 18 15:27:10 MST 2020

Re: Fwd: X11 crashes on suspend; log file includes "can't switch keyboard to raw mode"

On Thu, Oct 08, 2020 at 04:12:33AM BST, James Cook wrote: > On Wed, Jul 29, 2020 at 12:59:41AM +, James Cook wrote: > > >Synopsis: X11 crashes on suspend; log file includes "can't switch > > >keyboard to raw mode" > > FYI, this still happens on -current, including the garbage appearing

Re: "splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

On Thu, Apr 02, 2020 at 07:03:17PM BST, Stefan Sperling wrote: > On Thu, Apr 02, 2020 at 06:21:27PM +0100, Raf Czlonka wrote: > > On Thu, Apr 02, 2020 at 12:51:45PM BST, Stefan Sperling wrote: > > Hi Stefan, > > > > After I got it to timeout, I ran /etc/netstart and unp

Re: "splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

On Thu, Apr 02, 2020 at 12:51:45PM BST, Stefan Sperling wrote: > On Thu, Apr 02, 2020 at 12:40:46PM +0100, Raf Czlonka wrote: > > On Thu, Apr 02, 2020 at 12:30:15PM BST, Stefan Sperling wrote: > > > On Thu, Apr 02, 2020 at 11:43:34AM +0100, Raf Czlonka wrote: > &

Re: "splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

On Thu, Apr 02, 2020 at 12:30:15PM BST, Stefan Sperling wrote: > On Thu, Apr 02, 2020 at 11:43:34AM +0100, Raf Czlonka wrote: > > I've just tested it but, whilst I don't get a panic when I *un*plug > > the USB NIC, I *do* get the same panic when I *plug* it back in :^( > >

Re: "splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

On Thu, Apr 02, 2020 at 01:52:23AM BST, Raf Czlonka wrote: > On Mon, Mar 30, 2020 at 12:21:58PM BST, Stefan Sperling wrote: > > On Sun, Mar 29, 2020 at 01:15:37PM +0100, Raf Czlonka wrote: > > > > > When I unplugged the NIC at that point, I got a panic: > >

Re: "splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

On Mon, Mar 30, 2020 at 12:21:58PM BST, Stefan Sperling wrote: > On Sun, Mar 29, 2020 at 01:15:37PM +0100, Raf Czlonka wrote: > > >Synopsis: "splassert: ieee80211_free_node: want 7 have 4" followed by > > >"zyd0: device timeout" > > >

Re: autoinstall vs install behaviour and response file

On Tue, Mar 31, 2020 at 10:25:53AM BST, Stuart Henderson wrote: > On 2020/03/31 11:05, Renaud Allard wrote: > > Hello, > > > > I was trying to autoinstall OpenBSD over an existing installation of linux. > > So I used a modified (with upobsd) bsd.rd containing an auto_install.conf. > > But it

"splassert: ieee80211_free_node: want 7 have 4" followed by "zyd0: device timeout"

>Synopsis: "splassert: ieee80211_free_node: want 7 have 4" followed by >"zyd0: device timeout" >Category: kernel >Environment: System : OpenBSD 6.6 Details : OpenBSD 6.6-current (GENERIC.MP) #86: Sat Mar 28 14:42:23 MDT 2020

Re: unwind reports no signature or no DNSSEC

On Wed, Feb 05, 2020 at 03:14:41PM GMT, Florian Obser wrote: > > I'm sure you had(!) a different issue than Solene. unwind correctly > detects that your dhcp provided nameserver can only do resolving and > strips dnssec records while the recursor can do validation. > > On December 18th I enabled

Re: unwind reports no signature or no DNSSEC

On Mon, Feb 03, 2020 at 07:29:02PM GMT, Florian Obser wrote: > On Mon, Feb 03, 2020 at 07:58:24PM +0100, Solene Rapenne wrote: > > On Mon, Feb 03, 2020 at 07:52:29PM +0100, Florian Obser wrote: > > > On Mon, Feb 03, 2020 at 06:16:54PM +0100, Solene Rapenne wrote: > > > > I re-enabled unwind today

panic: kernel diagnostic assertion "pg != NULL" failed: file "/usr/src/sys/kern/vfs_biomem.c", line 308

>Synopsis: panic: kernel diagnostic assertion "pg != NULL" failed: file >"/usr/src/sys/kern/vfs_biomem.c", line 308 >Category: kernel >Environment: System : OpenBSD 6.6 Details : OpenBSD 6.6-current (GENERIC.MP) #493: Wed Nov 27 22:27:15 MST 2019

Re: weekly(8) isn't able to run locate.updatedb(8) anymore

On Tue, Sep 10, 2019 at 05:53:34PM BST, Todd C. Miller wrote: > On Tue, 10 Sep 2019 16:56:42 +0100, Raf Czlonka wrote: > > > How about ditching dirname(1)? > > dirname(1) handles files in the root directory as well as files > with no directory correctly, your diff does not.

Re: weekly(8) isn't able to run locate.updatedb(8) anymore

On Tue, Sep 10, 2019 at 05:13:31PM BST, Kurt Mosiejczuk wrote: > On Tue, Sep 10, 2019 at 05:03:54PM +0100, Raf Czlonka wrote: > > On Tue, Sep 10, 2019 at 04:58:19PM BST, Kurt Mosiejczuk wrote: > > > On Tue, Sep 10, 2019 at 04:56:42PM +0100, Raf Czlonka wrote: > > > >

Re: weekly(8) isn't able to run locate.updatedb(8) anymore

On Tue, Sep 10, 2019 at 04:58:19PM BST, Kurt Mosiejczuk wrote: > On Tue, Sep 10, 2019 at 04:56:42PM +0100, Raf Czlonka wrote: > > > How about ditching dirname(1)? > > File may not exist yet, in which case -w will be false, even if we > have permissions to create it. As per

Re: weekly(8) isn't able to run locate.updatedb(8) anymore

On Tue, Sep 10, 2019 at 04:10:57PM BST, Todd C. Miller wrote: > On Tue, 10 Sep 2019 09:42:16 +0200, Sebastien Marie wrote: > > > the use of '-' is documented has a valid option, and weekly(8) uses it > > in order to run locate.updatedb(8) has 'nobody' and have the output in > > tempfile under

Re: your mail

On Tue, Jun 11, 2019 at 09:51:31AM BST, Solene Rapenne wrote: > On Fri, Oct 12, 2018 at 08:59:46PM +0200, n...@sup-logistik.de wrote: > > >Synopsis: > >certificate is not yet valid> > > >Category: > > >Environment: > > System : OpenBSD 6.5 > > Details :

Re: current May 12 -> May 13 snapshot using sysupgrade is not automatic.

Hi Karel, The changed that broke it has been reverted[0]. Got bitten by it yesterday myself. This should get it working: # rm -fr /tmp/.sysupgrade.* # sysupgrade -n # mv /tmp/.sysupgrade.*/* /home/_sysupgrade The following snapshot won't be affected. [0]

Re: Starting xenodm(1) causes a crash - drops to ddb(4)

Hi all, Just an FYI. Last week, I've upgraded to (then) the latest snapshot and started xenodm(1) - the system doesn't crash any more and X11 works fine again. Thanks, Raf On Mon, Nov 12, 2018 at 03:06:10PM GMT, Raf Czlonka wrote: > >Synopsis:Starting xenodm(1) causes a crash -

Re: "Intel I219-V" rev 0x30: msiem0: The EEPROM Checksum Is Not Valid

On Sat, Jan 05, 2019 at 08:53:04AM GMT, Jonathan Gray wrote: > On Fri, Jan 04, 2019 at 09:56:15PM -0600, Brian Conway wrote: > > Greetings. I have a hot-off-the-presses Intel NUC model NUC8i5BEH > > (https://www.intel.com/content/www/us/en/products/boards-kits/nuc/kits/nuc8i5beh.html). > > For

Starting xenodm(1) causes a crash - drops to ddb(4)

>Synopsis: Starting xenodm(1) causes a crash - drops to ddb(4) >Category: system >Environment: System : OpenBSD 6.4 Details : OpenBSD 6.4-current (GENERIC.MP) #436: Sun Nov 11 23:59:55 MST 2018

Re: httpd: location - bug on sparc64

On Sun, Oct 14, 2018 at 08:35:08PM BST, Andrew Grillet wrote: > >location ".well-known/acme-challenge/*" { ^^ Andrew, You're missing (forward) slash ('/') there. Regards, Raf

Re: update63.html completeness

Hi John, Unless changes to the filesystem are required, there's no need for a fresh install: pkg_add sysclean :^) R On Fri, Apr 13, 2018 at 11:13:12PM BST, j...@bitminer.ca wrote: > On 2018-04-13 14:08, Stuart Henderson wrote: > > On 2018/04/13 20:29, Theo Buehler wrote: > > > On Thu, Apr 12,

System crashes on a daily basis - seems to be related to iwn

>Synopsis: Machine panics daily - seems to be iwn-related >Category: system kernel amd64 >Environment: System : OpenBSD 6.2 Details : OpenBSD 6.2-current (GENERIC.MP) #402: Tue Feb 6 19:26:10 MST 2018

Re: autoupgrade issues?

Hi jungle Boogie, What happens if you unmount wd0a before you run autoinstall? Is there enough space in bsd.rd for your auto_upgrade.conf file? What happens if you do a regular upgrade "by hand"? Personally, I'd keep old bsd.rd just in case, and rename the new one to something like bsd.up or

Re: syspatch not installing 6.1 binary patches

R0me0, Syspatch has been around *since* 6.1 - yes. Like Bryan already mentioned, binary patches are *only* available for the most recent release, though - it being 6.2. Cheers, Raf On Wed, Feb 07, 2018 at 07:33:16PM GMT, R0me0 *** wrote: > Hello, I got confused, since I already applied a lot

Re: Amusing quirk, maybe qualifies as bug: NTPD will not work on a machine that has an incorrect system date already, as NTPD uses TLS and TLS is time-sensitive

On Sun, Oct 15, 2017 at 07:49:48AM BST, ti...@openmailbox.org wrote: > > 2017-10-15 6:01 GMT+02:00 : > > > >> >> So to sum up, my best impression presently is that time validation > >> >> should be disabled for TLS certificates within NTPD. > >> > Not going to change. > >>

Re: xenodm issues on -current

Hi, Simply remove the intel(4) Xorg driver in the /etc/xorg.conf (or wherever you save your config) and use drm one. This, however, brings back the issues with unaccelerated vncviewer. Regards, Raf On Wed, Jul 26, 2017 at 07:11:39AM BST, jungle boogie wrote: > Hi All, > > I loaded up the

Re: regression using vncviewer (net/ssvnc) on inteldrm

On Fri, Jul 14, 2017 at 08:19:37AM BST, Paul de Weerd wrote: > On Thu, Jul 13, 2017 at 09:30:27PM +0100, Stuart Henderson wrote: > | > > Section "Device" > | > >Identifier "Intel Graphics" > | > >Driver "intel" > | > > EndSection > | > > | > Is this regression important enough to

Re: X crashes after suspend/resume cycle and keyboard becomes unusable

On Tue, Mar 21, 2017 at 01:29:59AM GMT, Mike Larkin wrote: > On Tue, Mar 21, 2017 at 01:23:07AM +0000, Raf Czlonka wrote: > > >Synopsis: X crashes after suspend/resume cycle and keyboard becomes > > >unusable > > >Category: system > > >Environ

X crashes after suspend/resume cycle and keyboard becomes unusable

>Synopsis: X crashes after suspend/resume cycle and keyboard becomes >unusable >Category: system >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-beta (GENERIC.MP) #37: Fri Mar 17 07:46:47 MDT 2017

Re: USB HID device numbering mismatch between usbdevs(8) and usbhidaction(1)

On Mon, Mar 20, 2017 at 03:19:12PM GMT, Martin Pieuchot wrote: > Hello Raf, > > On 20/03/17(Mon) 12:54, Raf Czlonka wrote: > > >Synopsis: usbdevs(8) and usbhidaction(1) do not agree on HID device > > >numbering > > >Category: system kernel > > >E

USB HID device numbering mismatch between usbdevs(8) and usbhidaction(1)

>Synopsis: usbdevs(8) and usbhidaction(1) do not agree on HID device >numbering >Category: system kernel >Environment: System : OpenBSD 6.1 Details : OpenBSD 6.1-beta (GENERIC.MP) #40: Sun Mar 19 19:40:41 MDT 2017

Re: rcctl set flags bug?

Hi Edgar, This is by design - the flags you are trying to set simply match the default ones: # unset flags if they match the default enabled ones [ "${_args}" = "$(svc_getdef ${_svc} ${_var})" ] && \ unset _args Regards, Raf On Tue, Aug 02, 2016 at 05:30:40AM

Re: Bug report recovery

On Thu, Jul 28, 2016 at 04:01:12PM BST, Jake Swensen wrote: > Hello, Hi Jake, > Yesterday I submitted a bug, about HDMI video output in Gnome, with the > sendbug command. By mistake I sent it before filling out some fields but > it included a lot of other detailed information > including steps

ssh(1) dumps core if ControlPath defined

>Synopsis: ssh(1) dumps core when ControlPath used in ~/.ssh/config >Category: system >Environment: System : OpenBSD 6.0 Details : OpenBSD 6.0-beta (GENERIC.MP) #2280: Mon Jul 11 05:20:56 MDT 2016

Re: getent(1) hosts - does DNS lookups

On Wed, Jun 08, 2016 at 10:59:00AM BST, Marcus MERIGHI wrote: > I would not expect getent(1) ("get entries from administrative > database") to do network DNS lookups. Yes, it even says so in the man page man 1 getent The order in which entries are looked up is defined by the

Re: Building ports as a regular user fails with PLIST_DB & other permission errors

On Mon, Mar 21, 2016 at 03:03:15PM GMT, Karl O. Pinc wrote: > Hello, Hi Karl, > This is something of an FYI. > > OpenBSD 5.8-stable. > > I tried following the instructions in ports(7) > and the FAQ to build ports as an ordinary user. > I added to /etc/mk.conf: > > WRKOBJDIR=/usr/obj/ports >

'w -a' dumps core if IP address does not resolve

>Synopsis: 'w -a' dumps core if IP address does not resolve >Category: system >Environment: System : OpenBSD 5.9 Details : OpenBSD 5.9-current (GENERIC) #1601: Fri Mar 18 10:35:21 MDT 2016

Re: ACPI thinkpad brightness regression

On Wed, Feb 10, 2016 at 07:10:41PM GMT, Martin Pieuchot wrote: > On 09/02/16(Tue) 21:06, Christian Weisgerber wrote: > > On 2016-02-09, Martin Pieuchot wrote: > > > > > Since brightness support has been added to acpithinkpad(4) I can easily > > > trigger a regression on my

Closing the lid suspends the system only the first time

>Synopsis: Closing the lid suspends the system only the first time >Category: system kernel >Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8-current (GENERIC.MP) #1410: Fri Oct 2 15:26:22 MDT 2015

Re: add RDing TEMPERHUM1V1.x (0x0c45:0x7402) to ugold(4) [was: uthum(4) - TEMPerHUM sensors not available through sysctl(8)]

On Sun, Jul 05, 2015 at 09:10:17AM BST, Joerg Jung wrote: Thanks for testing! No worries! It looks like your newer RDing TEMPERHUM1V1.2 has a different chip. As far as Google knows, it seems to be a si7006, which requires a slightly different formula with the temperature and humidity

Re: uthum(4) - TEMPerHUM sensors not available through sysctl(8)

On Sat, Jul 04, 2015 at 04:18:54PM BST, Joerg Jung wrote: Can you try the diff below please? Building kernel with this should make your device working, attaching as ugold(4) and providing the hygrometer values as well. Thanks for a quick reply and the diff, Joerg. Indeed, the device now

Re: uthum(4) - TEMPerHUM sensors not available through sysctl(8)

On Tue, Jun 30, 2015 at 09:40:14AM BST, Joerg Jung wrote: On Mon, Jun 29, 2015 at 09:50:19PM +0100, Raf Czlonka wrote: Synopsis: uthum(4) - TEMPerHUM sensors not available through sysctl(8) Category: system kernel Environment: System : OpenBSD 5.8 Details : OpenBSD

uthum(4) - TEMPerHUM sensors not available through sysctl(8)

Synopsis: uthum(4) - TEMPerHUM sensors not available through sysctl(8) Category: system kernel Environment: System : OpenBSD 5.8 Details : OpenBSD 5.8-beta (GENERIC) #952: Thu Jun 25 21:33:40 MDT 2015

Re: install57.iso does not recognize a burned image of itself in an attached CD-R drive

On Tue, May 19, 2015 at 06:18:08AM BST, James Hartley wrote: On Mon, May 18, 2015 at 11:56 PM, Raf Czlonka rczlo...@gmail.com wrote: You are booting from the first optical drive. I am installing from the second optical drive. The first does not read discs burned with this USB drive

Re: install57.iso does not recognize a burned image of itself in an attached CD-R drive

On Tue, May 19, 2015 at 09:15:25AM BST, James Hartley wrote: It appears that when the boot device is selected, that device is being identified incorrectly as cd0. Incorrectly? According to whom? ;^) The installer (bsd.rd) provides a very clear information from which medium it is booting and

Re: install57.iso does not recognize a burned image of itself in an attached CD-R drive

On Tue, May 19, 2015 at 03:58:55AM BST, James Hartley wrote: Description: This appears to be a regression. I previously have been able to install via a burned image of install57.iso without resorting to copying the filesets to another accessible device. With

Re: Volume buttons stop working after suspend/resume cycle

On Thu, Feb 05, 2015 at 08:39:43AM GMT, Raf Czlonka wrote: On Thu, Feb 05, 2015 at 08:07:01AM GMT, Paul Irofti wrote: Press the volume, brightness, display switch and see if anything pops-up in your dmesg. Brightness is indeed in the F-key row and it is Fn-key activated but the last

Re: Volume buttons stop working after suspend/resume cycle

On Thu, Feb 05, 2015 at 08:07:01AM GMT, Paul Irofti wrote: Did you press the function key buttons before and after suspend? Volume Up/Down are separate buttons at the front of the laptop - not Fn-activated keys in the F-keys row. There's also a physical mute button just left of those two - this

Re: Volume buttons stop working after suspend/resume cycle

On Tue, Feb 03, 2015 at 08:54:07PM GMT, Paul Irofti wrote: First of all you should update to -current. I have now installed the latest snapshot and built a kernel fresh from CVS sources. Then you should apply the following diff and let me know the result. No joy, I'm afraid :^( Raf

Re: Volume buttons stop working after suspend/resume cycle

On Tue, Feb 03, 2015 at 09:08:38PM GMT, Paul Irofti wrote: If it fails, please be kind enough to also apply the following debug diff and supply the output on your dmesg when you press the volume keys before and after suspend. Applied but I failed to see any debug info. All this does is

Audio volume level set to '0,0' after suspend/resume cycle

Synopsis: Audio volume level is being set to '0,0' after suspend/resume cycle Category: system Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-stable (GENERIC) #0: Tue Jan 27 00:09:23 GMT 2015

Volume buttons stop working after suspend/resume cycle

Synopsis: Volume buttons stop working after suspend/resume cycle Category: kernel Environment: System : OpenBSD 5.6 Details : OpenBSD 5.6-stable (GENERIC) #0: Tue Jan 27 00:09:23 GMT 2015

Re: xrandr won't set DPI

On Tue, Jan 27, 2015 at 02:37:28AM GMT, Ted Unangst wrote: Running in vmware, when I run xrandr --dpi 96 it prints an error: xrandr: Failed to get size of gamma for default output And doesn't appear to change the DPI setting. (I test dpi by running xterm -fa Courier New and observing if