Re: xscreensaver-settings crashes in OpenBSD 7.2
Maybe Linux-drm messed it up? On Fri, Nov 11, 2022 at 10:35 AM Luke Small wrote: > xscreensaver-settings crashes in OpenBSD 7.2 > > Graphics card shows as radeon 7450 in the dmesg, > "radeondrm0 at pci3 dev 0 function 0 "ATI Radeon HD 7450" rev 0x00", > but it is a radeon hd 6450 exactly like this one: > > > https://www.amazon.com/MSI-Profile-PCI-Express-R6450-MD1GD3-LP/dp/B004X6ABTM > > the screensavers mostly work, but I can't get to the settings menu gui. > > I've moved .xscreensaver and it didn't work either. > > This is the results of running xscreensaver-settings in a terminal : > > $ xscreensaver-settings --debug > xscreensaver-settings: 14:45:30: DISPLAY=:0 > xscreensaver-settings: 14:45:30: added "/usr/local/libexec/xscreensaver" > to $PATH > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: (pref changed) > xscreensaver-settings: 14:45:30: list selection changed > xscreensaver-settings: 14:45:30: scheduling preview "gibson -root -delay > 32743 -speed 2.477 -columns 6" > xscreensaver-settings: 14:45:30: reading > /usr/local/share/xscreensaver/config/gibson.xml... > xscreensaver-settings: 14:45:30: scheduling preview "gibson --root --delay > 32743 --speed 2.477 --columns 6" > xscreensaver-settings: 14:45:30: reading > /usr/local/share/xscreensaver/config/gibson.xml... > xscreensaver-settings: 14:45:30: scheduling preview "gibson --root --delay > 32743 --speed 2.477 --columns 6" > xscreensaver-settings: 14:45:30: select list elt 91 > xscreensaver-settings: 14:45:30: scheduling preview "gibson -root -delay > 32743 -speed 2.477 -columns 6" > xscreensaver-settings: 14:45:30: reading > /usr/local/share/xscreensaver/config/gibson.xml... > xscreensaver-settings: 14:45:30: scheduling preview "gibson --root --delay > 32743 --speed 2.477 --columns 6" > xscreensaver-settings: 14:45:31: xscreensaver-gl-visual says the GL visual > is 0x21. > xscreensaver-settings: 14:45:31: using non-default visual 0x21 > > xscreensaver-settings: 14:45:31: X error: > xscreensaver-settings: Failed request: BadMatch (invalid parameter > attributes) > xscreensaver-settings: Major opcode: 42 (X_SetInputFocus) > xscreensaver-settings: Resource id:0x83 > xscreensaver-settings: Serial number: 450 / 451 > > > > > > /etc/X11/xorg.conf : (I've tried a variation on the radeon settings and > reset them with rcctl restart xenodm, etc.) > > Section "Files" > FontPath "/usr/X11R6/lib/X11/fonts/misc/" > FontPath "/usr/X11R6/lib/X11/fonts/TTF/" > FontPath "/usr/X11R6/lib/X11/fonts/OTF/" > FontPath "/usr/X11R6/lib/X11/fonts/Type1/" > FontPath "/usr/X11R6/lib/X11/fonts/WinFonts/" > # FontPath "/usr/X11R6/lib/X11/fonts/100dpi/" > FontPath "/usr/X11R6/lib/X11/fonts/75dpi/" > FontPath "/usr/local/share/fonts/spleen" > EndSection > > Section "ServerFlags" > Option "DontZap" "true" > EndSection > > Section "Device" > Identifier "radeoncard" > Driver "radeon" > Option "TearFree" "true" > Option "DRI" "2" > Option "AccelMethod" "EXA" > Option "EXAVSync" "true" > EndSection > > > > > dmesg: > > OpenBSD 7.2 (GENERIC.MP) #0: Wed Oct 26 12:01:47 MDT 2022 > r...@syspatch-72-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/ > GENERIC.MP > real mem = 51513982976 (49127MB) > avail mem = 49935368192 (47622MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0x9e000 (88 entries) > bios0: vendor American Megatrends Inc. version "2.1b" date 05/04/12 > bios0: Supermicro X8DTH-i/6/iF/6F > acpi0 at bios0: ACPI 4.0 > acpi0: sleep states S0 S1 S4 S5 > acpi0: tables DSDT FACP APIC MCFG SLIT SPMI OEMB SRAT HPET DMAR SSDT > acpi0: wakeup devices NPE2(S4) NPE3(S4) NPE4(S4) NPE5(S4) NPE6(S4) > NPE7(S4) NPE8(S4) NPE9(S4) NPEA(S4) P0P1(S4) USB0(S4) USB1(S4) USB2(S4) > USB5(S4) EUSB(S4) USB3(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Xeon(R) CPU X5675 @ 3.07GHz, 3067.04 MHz, 06-2c-02 > cpu0: >
Re: cdn.openbsd.org not synced
> Pierre-Edouard p...@pywy.fr wrote: > > > User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:102.0) Gecko/20100101 > > > Hi, > > I'm using cdn.openbsd.org as installurl, and last update of packages > > is stuck to 30th Oct. > > > > Switching back to ftp.openbsd.org solves the issue. > > Is there an issue with the sync or did the cdn has been discontinued? > > > cdn.openbsd.org says: > > 0ad-0.0.26p0.tgz 14-Nov-2022 05:28 55535229 > 0ad-data-0.0.26.tgz 14-Nov-2022 05:29 1761278663 > 1oom-1.0.tgz 14-Nov-2022 05:28 965935 > 2048-cli-0.9.1.tgz 14-Nov-2022 05:28 9696 > ... Hi Pierre-Edouard, The CDN connects you to a specific server based on your computer's location and possibly other factors (latancy, etc). It's possible that specific CDN endpoint was out of date at the time of your scan; whereas the scan Theo did almost certainly hit a more up to date endpoint. Picking an up-to-date mirror by hand like you did is understandable. Kevin
Re: Ctrl key doesn't interrupt boot
On 2022-11-14, Harald Dunkel wrote: > Hi folks, > > according to boot(8) holding the Ctrl key is supposed to interrupt > boot before /etc/boot.conf is read. But it doesn't. I see boot's > message on VGA that it switches over to serial (as mentioned in > boot.conf), and then it doesn't boot for a reason I would like to > investigate. The screen stays black. > > I am sure that console redirection is turned off in the BIOS. > OpenBSD is version 7.2. USB Keyboard. Timing for this is extremely touchy on some machines. You may do better if you tap it repeatedly starting from a little before the time the bios hands over to the boot loader. -- Please keep replies on the mailing list.
Re: cdn.openbsd.org not synced
Pierre-Edouard wrote: User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:102.0) Gecko/20100101 > Hi, > I'm using cdn.openbsd.org as installurl, and last update of packages > is stuck to 30th Oct. > > Switching back to ftp.openbsd.org solves the issue. > Is there an issue with the sync or did the cdn has been discontinued? cdn.openbsd.org says: 0ad-0.0.26p0.tgz 14-Nov-2022 05:28 55535229 0ad-data-0.0.26.tgz14-Nov-2022 05:29 1761278663 1oom-1.0.tgz 14-Nov-2022 05:28 965935 2048-cli-0.9.1.tgz 14-Nov-2022 05:28 9696 ...
cdn.openbsd.org not synced
Hi, I'm using cdn.openbsd.org as installurl, and last update of packages is stuck to 30th Oct. Switching back to ftp.openbsd.org solves the issue. Is there an issue with the sync or did the cdn has been discontinued? Cheers,
Re: Ctrl key doesn't interrupt boot
On 2022-11-14 13:54:18, Nick Holland wrote: Wild guess, but I suspect that your BIOS isn't setting the marker that /boot uses to see the pressing of the CTRL key on your system with a USB keyboard. /boot is pretty much dependent upon your system BIOS doing The Right Thing, as the OS hasn't loaded yet. So other than looking at Other Things, I'm not sure there's an OpenBSD fix for this. Do you think it would be possible to introduce a 3sec timeout to press the fabulous "any" key on pc0 to avoid that boot switches over to com0? Apparently boot can read the USB keyboard if the boot prompt is not redirected to com0. Does your machine accept a PS/2 keyboard? If so, does CTRL work as expected there? No PS/2 socket. Its an Axiomtek network appliance. Regards Harri
Re: Ctrl key doesn't interrupt boot
On 11/14/22 06:40, Harald Dunkel wrote: Hi folks, according to boot(8) holding the Ctrl key is supposed to interrupt boot before /etc/boot.conf is read. But it doesn't. I see boot's message on VGA that it switches over to serial (as mentioned in boot.conf), and then it doesn't boot for a reason I would like to investigate. The screen stays black. I am sure that console redirection is turned off in the BIOS. OpenBSD is version 7.2. USB Keyboard. Every helpful hint is highly appreciated. Harri Wild guess, but I suspect that your BIOS isn't setting the marker that /boot uses to see the pressing of the CTRL key on your system with a USB keyboard. /boot is pretty much dependent upon your system BIOS doing The Right Thing, as the OS hasn't loaded yet. So other than looking at Other Things, I'm not sure there's an OpenBSD fix for this. Does your machine accept a PS/2 keyboard? If so, does CTRL work as expected there? Nick.
Re: CyberPower cp1500PPFCLCD
On 11/14/22 3:35 AM, Stuart Henderson wrote: That is just for APC UPS. I know it's supposed to be just for APC UPSes, but it's my understanding that apcupsd works, at least for some, CyberPower UPSes.
Ctrl key doesn't interrupt boot
Hi folks, according to boot(8) holding the Ctrl key is supposed to interrupt boot before /etc/boot.conf is read. But it doesn't. I see boot's message on VGA that it switches over to serial (as mentioned in boot.conf), and then it doesn't boot for a reason I would like to investigate. The screen stays black. I am sure that console redirection is turned off in the BIOS. OpenBSD is version 7.2. USB Keyboard. Every helpful hint is highly appreciated. Harri
Re: CyberPower cp1500PPFCLCD
On 2022-11-14, ITwrx wrote: > On 11/13/22 12:56 PM, Peter Fraser wrote: >> My sensorsd.conf contains >> >> hw.sensors.upd0.percent0:low=99.00%:command=/etc/ups-shutdown %2 >> >> The 99.00% was to allow me to test it easily >> >> As far as I could tell there is no way to ask sensorsd to only run a program >> when the UPS is not charging and the % left is less than a value. >> >> At this point one of two things happened. Either then upd0 values disappear >> from sysctl or the system dies with no messages, and I have to do a hard >> reset. >> >> Does anyone have any ideas of what is going on and how to fix it. > > I accidentally sent the below to the op directly before. Sorry about that. > >> I just wanted to make sure you know about apcupsd [1]. It may work for your >> UPS, even though it's not APC branded. It's in the OpenBSD repos. >> >> http://www.apcupsd.org/ That is just for APC UPS. There is NUT which has much wider device support, but the original issue seems to be with the USB stack rather than upd and may affect userland software too. -- Please keep replies on the mailing list.
