Startx doesn't find screens
Hi to everybody, I'm facing this problem after the complete installation of OpenBSD 6.7: if I try to launch startx, an error occur and tells that "no screens found". My setup is asus kgpe-d16 with coreboot, nvidia quadro 600 as a video graphic card and I had disable the embedded VGA with the relative jumper (otherwise the machine doesn't start at all). During the installation process, I choose all the default options except for the question about X windows system being started by xenodm (default: no, my choose: yes) The Xorg.0 log file content is the below: [ 47.339] X.Org X Server 1.20.8 X Protocol Version 11, Revision 0 [ 47.339] Build Operating System: OpenBSD 6.7 amd64 [ 47.339] Current Operating System: OpenBSD Mypc 6.7 GENERIC.MP#182 amd64 [ 47.340] Build Date: 07 May 2020 11:44:28AM [ 47.340] [ 47.340] Current version of pixman: 0.38.4 [ 47.340] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 47.340] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 47.340] (==) Log file: "/home/server/.local/share/xorg/Xorg.0.log", Time: Sun Oct 25 15:07:01 2020 [ 47.341] (==) Using config file: "/etc/X11/xorg.conf" [ 47.341] (==) Using system config directory "/usr/X11R6/share/X11/xorg.conf.d" [ 47.341] (==) No Layout section. Using the first Screen section. [ 47.341] (==) No screen section available. Using defaults. [ 47.341] (**) |-->Screen "Default Screen Section" (0) [ 47.341] (**) | |-->Monitor "" [ 47.342] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 47.342] (**) | |-->Device "Card0" [ 47.342] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 47.342] (==) Automatically adding devices [ 47.342] (==) Automatically enabling devices [ 47.342] (==) Not automatically adding GPU devices [ 47.342] (==) Max clients allowed: 256, resource mask: 0x1f [ 47.342] (==) FontPath set to: /usr/X11R6/lib/X11/fonts/misc/, /usr/X11R6/lib/X11/fonts/TTF/, /usr/X11R6/lib/X11/fonts/OTF/, /usr/X11R6/lib/X11/fonts/Type1/, /usr/X11R6/lib/X11/fonts/100dpi/, /usr/X11R6/lib/X11/fonts/75dpi/ [ 47.342] (==) ModulePath set to "/usr/X11R6/lib/modules" [ 47.342] (II) The server relies on wscons to provide the list of input devices. If no devices become available, reconfigure wscons or disable AutoAddDevices. [ 47.342] (II) Loader magic: 0xee1285dd000 [ 47.342] (II) Module ABI versions: [ 47.342] X.Org ANSI C Emulation: 0.4 [ 47.342] X.Org Video Driver: 24.1 [ 47.342] X.Org XInput driver : 24.1 [ 47.342] X.Org Server Extension : 10.0 [ 47.343] (--) Using wscons driver on /dev/ttyC4 [ 47.353] (WW) checkDevMem: failed to open /dev/xf86 and /dev/mem (Permission denied) Check that you have set 'machdep.allowaperture=1' in /etc/sysctl.conf and reboot your machine refer to xf86(4) for details [ 47.353] linear framebuffer access unavailable [ 47.353] (II) LoadModule: "glx" [ 47.354] (II) Loading /usr/X11R6/lib/modules/extensions/libglx.so [ 47.357] (II) Module glx: vendor="X.Org Foundation" [ 47.357] compiled for 1.20.8, module version = 1.0.0 [ 47.357] ABI class: X.Org Server Extension, version 10.0 [ 47.357] (II) LoadModule: "wsfb" [ 47.358] (II) Loading /usr/X11R6/lib/modules/drivers/wsfb_drv.so [ 47.358] (II) Module wsfb: vendor="X.Org Foundation" [ 47.358] compiled for 1.20.8, module version = 0.4.1 [ 47.358] ABI class: X.Org Video Driver, version 24.1 [ 47.358] (II) wsfb: driver for wsdisplay framebuffer: wsfb [ 47.358] (WW) Falling back to old probe method for wsfb [ 47.358] (II) wsfb(0): using default device [ 47.358] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 47.358] (EE) wsfb(0): no way to get depth info: Inappropriate ioctl for device [ 47.358] (II) UnloadModule: "wsfb" [ 47.358] (EE) Screen(s) found, but none have a usable configuration. [ 47.358] (EE) Fatal server error: [ 47.358] (EE) no screens found(EE) [ 47.358] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 47.358] (EE) Please also check the log file at "/home/server/.local/share/xorg/Xorg.0.log" for additional information. [ 47.359] (EE) [ 47.360] (EE) Server terminated with error (1). Closing log file. The dmesg content is the below: OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 68568186880 (65391MB) avail mem = 66477481984 (63397MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xb7fba020 (17 entries) bios0: vendor coreboot version "4.11-ab8edda14a622ab46bdfd01b877d75c7bd385a4d" date 09/09/2020 bios0: ASUS KGPE-D16 acpi0 at bios0: ACPI 4.0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP SSDT MCFG APIC SRAT SLIT SRAT SLIT IVRS HPET SPMI acpi0: wakeup devices
Re: man netstart(8) OpenBSD-6.8
Rachel, you could submit something to be helpful if you like, fill the gap that
you see. Only 60 devs and most of the man page content is incredibly up to
date and valuable.
So I for one look forward to you adding your entry into the netstart man page
for community review.
Please don't forget all G703 types, and any algorithms behind the l1 to L3
protocols, like preference level on BGP attributes per physical type, maybe add
in the voltages as well. You know push and pull 0 and 1 0-15 and - voltage
ranges etc for each as well.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, 25 October 2020 09:42, Rachel Roch wrote:
> 25 Oct 2020, 01:25 by dera...@openbsd.org:
>
> > Rachel Roch rr...@tutanota.de wrote:
> >
> > > Is it just me or is the man entry for netstart(8) missing a reference to
> > > wg(4) ?
> >
> > ... and 300 other network interfaces.
> > In otherwords, no, it should not be there.
>
> OK smart alec, then why bother enumerating any of the non-physical interfaces
> on the man page ?
>
> Afterall, the man page does state at the head of the list "During the system
> boot, netstart is executed. netstart performs the following operations, in
> the sequence given".
>
> There is little point giving a half-assed description. Either you enumerate
> ALL the non-physical interfaces, or otherwise you treat them the same way as
> the physical ones ("Configure all the physical interfaces").
>
> Otherwise you are failing to explain what happens to any of your "300 other
> interfaces". Enumerate or don't enumerate, I don't care ... but surely it is
> sensible to pay some reference to them.
>
> Sheesh !
Re: man netstart(8) OpenBSD-6.8
Rachel, you could submit something to be helpful if you like, fill the gap that
you see. Only 60 devs and most of the man page content is incredibly up to
date and valuable.
So I for one look forward to you adding your entry into the netstart man page
for community review.
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Sunday, 25 October 2020 09:42, Rachel Roch wrote:
> 25 Oct 2020, 01:25 by dera...@openbsd.org:
>
> > Rachel Roch rr...@tutanota.de wrote:
> >
> > > Is it just me or is the man entry for netstart(8) missing a reference to
> > > wg(4) ?
> >
> > ... and 300 other network interfaces.
> > In otherwords, no, it should not be there.
>
> OK smart alec, then why bother enumerating any of the non-physical interfaces
> on the man page ?
>
> Afterall, the man page does state at the head of the list "During the system
> boot, netstart is executed. netstart performs the following operations, in
> the sequence given".
>
> There is little point giving a half-assed description. Either you enumerate
> ALL the non-physical interfaces, or otherwise you treat them the same way as
> the physical ones ("Configure all the physical interfaces").
>
> Otherwise you are failing to explain what happens to any of your "300 other
> interfaces". Enumerate or don't enumerate, I don't care ... but surely it is
> sensible to pay some reference to them.
>
> Sheesh !
Re: Startx doesn't find screens
On 2020-10-25 10:35, d.verdi wrote: > Hi to everybody, > I'm facing this problem after the complete installation of OpenBSD 6.7: > if I try to launch startx, an error occur and tells that "no screens found". ... > The Xorg.0 log file content is the below: ... > Check that you have set 'machdep.allowaperture=1' > in /etc/sysctl.conf and reboot your machine > refer to xf86(4) for details MIGHT help. ... > [ 47.358] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support > [ 47.358] (EE) wsfb(0): no way to get depth info: Inappropriate ioctl for > device > [ 47.358] (II) UnloadModule: "wsfb" > [ 47.358] (EE) Screen(s) found, but none have a usable configuration. ... > The dmesg content is the below: thanks! > OpenBSD 6.7 (GENERIC.MP) #182: Thu May 7 11:11:58 MDT 2020 previous release... ... > vga1 at pci1 dev 0 function 0 vendor "NVIDIA", unknown product 0x0df8 rev 0xa1 > wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) > wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ... > > Thank you very much for the support > Dav > One -- 6.8 was just released. Don't install an old release. Two -- you seem to have a board that hasn't been seen much in the wild by OpenBSD developers...and an nvidia at that. 6.8 *might* help with that. Or better, a snapshot. But if this is an add-in card, I'd suggest reinstalling it to your local trash can or maybe a windows machine and and getting a better supported, non-nvidia card installed. Nick.
Re: man netstart(8) OpenBSD-6.8
Jason McIntyre wrote: > On Sun, Oct 25, 2020 at 10:16:54AM -0600, Theo de Raadt wrote: > > Jason McIntyre wrote: > > > > > whereas /etc/netstart is actually doing: > > > > > > - configure non-physical: (1) > > > aggr trunk svlan vlan carp pppoe > > > - routing (2) > > > - rest of non-physical: (3) > > > tun tap gif etherip gre egre mobileip pflow wg > > > > > > we could try to keep this list up to date, but it may be easier to just > > > generally describe what netstart is doing. > > > > I think we goes wrong by trying to maintain these as lists, and part of > > where this goes wrong is weak definition of the reasons for the > > ordering. (Meaning, the developers who tweak netstart to handle the > > concerns I'm about to describe, don't tend to think about the manual > > page). > > > > The (1) list of non-physical can probably be called "link-layer control > > interfaces". Or let's find a name for this. These devices mutate the > > presentation of other devices. That's why their configuration needs to > > be done before the physical device. > > > > (2) The physical device is then brought up, including IP addressing. The > > things in (1) need to be done beforehands, or the physical device is > > participating in the wrong layer of network. > > > > the (3) list of non-physical devices are layer-2 or layer-3 and operate > > on devices which are already configured with some some sort of > > "addressing" configured. > > > > It would be nice to have our networking people come up with nice names > > for group (1) and (2); words which succinctly describe the > > classification like I've done above. We need to increase understanding > > of this order, rather than just abstractly listing names of devices with > > complicated behaviours. > > > > Once that is done, I still think it is problematic for us to list all > > devices in each catagory: > > > > a) new subsystems will be forgotten > > b) the order of instantiation will sometimes be listed wrong -- for some > >of these the order is highly significant. > > > > We can try to list as many as possible, but people who want the precise > > list (and order) should look in the netstart code. The lists will get > > long and wrong. If we find we cannot maintain the lists correctly > > because it is duplicated information, man page wording like "such as" > > could be used, also something which leads people to consider the script > > source as authoritative, ie. have them go read the script > > > > ok, here is a start. > > i have left the description as "non-physical", because i think that is > clear. we could easily amend it. ifconfig.8 create talks about "network > pseudo-devices" - that could be a possibility. You've deleted all the interface names, so now there are no examples. I disagree strongly. That creates a hurdle and people won't learn how our network pieces are configured into a multi-layer stack.
Re: man netstart(8) OpenBSD-6.8
On Sun, Oct 25, 2020 at 10:16:54AM -0600, Theo de Raadt wrote: > Jason McIntyre wrote: > > > whereas /etc/netstart is actually doing: > > > > - configure non-physical: (1) > > aggr trunk svlan vlan carp pppoe > > - routing (2) > > - rest of non-physical: (3) > > tun tap gif etherip gre egre mobileip pflow wg > > > > we could try to keep this list up to date, but it may be easier to just > > generally describe what netstart is doing. > > I think we goes wrong by trying to maintain these as lists, and part of > where this goes wrong is weak definition of the reasons for the > ordering. (Meaning, the developers who tweak netstart to handle the > concerns I'm about to describe, don't tend to think about the manual > page). > > The (1) list of non-physical can probably be called "link-layer control > interfaces". Or let's find a name for this. These devices mutate the > presentation of other devices. That's why their configuration needs to > be done before the physical device. > > (2) The physical device is then brought up, including IP addressing. The > things in (1) need to be done beforehands, or the physical device is > participating in the wrong layer of network. > > the (3) list of non-physical devices are layer-2 or layer-3 and operate > on devices which are already configured with some some sort of > "addressing" configured. > > It would be nice to have our networking people come up with nice names > for group (1) and (2); words which succinctly describe the > classification like I've done above. We need to increase understanding > of this order, rather than just abstractly listing names of devices with > complicated behaviours. > > Once that is done, I still think it is problematic for us to list all > devices in each catagory: > > a) new subsystems will be forgotten > b) the order of instantiation will sometimes be listed wrong -- for some >of these the order is highly significant. > > We can try to list as many as possible, but people who want the precise > list (and order) should look in the netstart code. The lists will get > long and wrong. If we find we cannot maintain the lists correctly > because it is duplicated information, man page wording like "such as" > could be used, also something which leads people to consider the script > source as authoritative, ie. have them go read the script > ok, here is a start. i have left the description as "non-physical", because i think that is clear. we could easily amend it. ifconfig.8 create talks about "network pseudo-devices" - that could be a possibility. jmc Index: netstart.8 === RCS file: /cvs/src/share/man/man8/netstart.8,v retrieving revision 1.23 diff -u -p -r1.23 netstart.8 --- netstart.8 7 Mar 2018 09:54:23 - 1.23 +++ netstart.8 25 Oct 2020 16:39:04 - @@ -64,20 +64,12 @@ Configure the loopback interface. .It Configure all the physical interfaces. .It -Configure the following non-physical interfaces: -.Xr trunk 4 , -.Xr vlan 4 , -.Xr pfsync 4 , -and -.Xr carp 4 . +Configure any non-physical interfaces which need to be set up +before default routes are in place. .It Initialize the routing table and set up the default routes. .It -Configure the remaining non-physical interfaces: -.Xr pppoe 4 , -.Xr gif 4 , -and -.Xr gre 4 . +Configure the remaining non-physical interfaces. .It Configure all .Xr bridge 4
Re: man netstart(8) OpenBSD-6.8
Jason McIntyre wrote: > whereas /etc/netstart is actually doing: > > - configure non-physical: (1) > aggr trunk svlan vlan carp pppoe > - routing (2) > - rest of non-physical: (3) > tun tap gif etherip gre egre mobileip pflow wg > > we could try to keep this list up to date, but it may be easier to just > generally describe what netstart is doing. I think we goes wrong by trying to maintain these as lists, and part of where this goes wrong is weak definition of the reasons for the ordering. (Meaning, the developers who tweak netstart to handle the concerns I'm about to describe, don't tend to think about the manual page). The (1) list of non-physical can probably be called "link-layer control interfaces". Or let's find a name for this. These devices mutate the presentation of other devices. That's why their configuration needs to be done before the physical device. (2) The physical device is then brought up, including IP addressing. The things in (1) need to be done beforehands, or the physical device is participating in the wrong layer of network. the (3) list of non-physical devices are layer-2 or layer-3 and operate on devices which are already configured with some some sort of "addressing" configured. It would be nice to have our networking people come up with nice names for group (1) and (2); words which succinctly describe the classification like I've done above. We need to increase understanding of this order, rather than just abstractly listing names of devices with complicated behaviours. Once that is done, I still think it is problematic for us to list all devices in each catagory: a) new subsystems will be forgotten b) the order of instantiation will sometimes be listed wrong -- for some of these the order is highly significant. We can try to list as many as possible, but people who want the precise list (and order) should look in the netstart code. The lists will get long and wrong. If we find we cannot maintain the lists correctly because it is duplicated information, man page wording like "such as" could be used, also something which leads people to consider the script source as authoritative, ie. have them go read the script
OBSD 6.8 boot hang on azalia, acpi vs msi issue?
Hi, I updated a box with a VIA VE-900 chipset (VIA Nano X2 CPU) from 6.7 to 6.8 which then hung during first boot with 6.8. The last line was for azalia. I rebooted and disabled azalia which allowed the 6.8 boot to complete. Comparing the dmesg with that from 6.7 showed that the change was from using acpi to msi for the device. Also that the on board NIC is no longer seen under 6.8. The re device is seen by find but doesn't appear from the boot process, either taken out by disabling azalia or a separate problem. (I stuck a usb wifi dongle on the box to finish the upgrade process.) Here is the diff between the two dmesgs: -- *** ../dmesg/dmesg6.7Sat May 30 09:05:59 2020 --- dmesg6.8-noazalia Sat Oct 24 18:01:12 2020 *** *** 39,51 acpiprt1 at acpi0: bus 1 (NBP0) acpiprt2 at acpi0: bus 5 (NBP3) acpiprt3 at acpi0: bus 6 (P0P4) ! acpicpu0 at acpi0: C1(1000@1 halt), PSS ! acpicpu1 at acpi0: C1(1000@1 halt), PSS ! acpipci0 at acpi0 PCI0: _OSC failed acpiac0 at acpi0: AC unit online acpicmos0 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB acpivideo0 at acpi0: VUMA acpivout0 at acpivideo0: LCD_ cpu0: Enhanced SpeedStep 1400 MHz: speeds: 1400, 1200, 1100, 1000, 900, 800 MHz --- 47,59 acpiprt1 at acpi0: bus 1 (NBP0) acpiprt2 at acpi0: bus 5 (NBP3) acpiprt3 at acpi0: bus 6 (P0P4) ! acpipci0 at acpi0 PCI0 acpiac0 at acpi0: AC unit online acpicmos0 at acpi0 acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB + acpicpu0 at acpi0: C1(1000@1 halt), PSS + acpicpu1 at acpi0: C1(1000@1 halt), PSS acpivideo0 at acpi0: VUMA acpivout0 at acpivideo0: LCD_ cpu0: Enhanced SpeedStep 1400 MHz: speeds: 1400, 1200, 1100, 1000, 900, 800 MHz *** *** 61,78 vga1 at pci0 dev 1 function 0 "VIA Chrome9 HD" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ! azalia0 at pci0 dev 1 function 1 "VIA HD Audio" rev 0x00: apic 4 int 17 ! azalia0: no supported codecs ! ppb0 at pci0 dev 3 function 0 "VIA VX900 PCIE" rev 0x00: apic 4 int 3 pci1 at ppb0 bus 1 ! ppb1 at pci0 dev 3 function 1 "VIA VX900 PCIE" rev 0x00: apic 4 int 7 pci2 at ppb1 bus 2 ! ppb2 at pci0 dev 3 function 2 "VIA VX900 PCIE" rev 0x00: apic 4 int 11 pci3 at ppb2 bus 3 ! ppb3 at pci0 dev 3 function 3 "VIA VX900 PCIE" rev 0x00: apic 4 int 15 pci4 at ppb3 bus 5 - re0 at pci4 dev 0 function 0 "Realtek 8168" rev 0x06: RTL8168E/8111E (0x2c00), apic 4 int 12, address c8:9c:dc:54:5f:77 - rgephy0 at re0 phy 7: RTL8169S/8110S/8211 PHY, rev. 4 pchb8 at pci0 dev 3 function 4 "VIA VX900 PCIE" rev 0x00 pciide0 at pci0 dev 15 function 0 "VIA VX900 IDE" rev 0x00: ATA133, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 3 int 21 for native-PCI interrupt --- 69,83 vga1 at pci0 dev 1 function 0 "VIA Chrome9 HD" rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) ! "VIA HD Audio" rev 0x00 at pci0 dev 1 function 1 not configured ! ppb0 at pci0 dev 3 function 0 "VIA VX900 PCIE" rev 0x00: msi pci1 at ppb0 bus 1 ! ppb1 at pci0 dev 3 function 1 "VIA VX900 PCIE" rev 0x00: msi pci2 at ppb1 bus 2 ! ppb2 at pci0 dev 3 function 2 "VIA VX900 PCIE" rev 0x00: msi pci3 at ppb2 bus 3 ! ppb3 at pci0 dev 3 function 3 "VIA VX900 PCIE" rev 0x00: msi pci4 at ppb3 bus 5 pchb8 at pci0 dev 3 function 4 "VIA VX900 PCIE" rev 0x00 pciide0 at pci0 dev 15 function 0 "VIA VX900 IDE" rev 0x00: ATA133, channel 0 configured to native-PCI, channel 1 configured to native-PCI pciide0: using apic 3 int 21 for native-PCI interrupt *** *** 92,100 pchb9 at pci0 dev 17 function 7 "VIA VX800 Host" rev 0x00 ppb4 at pci0 dev 19 function 0 "VIA VX800" rev 0x00 pci5 at ppb4 bus 6 ! azalia1 at pci0 dev 20 function 0 "VIA HD Audio" rev 0x20: apic 3 int 17 ! azalia1: codecs: VIA/0x0397 ! audio0 at azalia1 usb1 at uhci0: USB revision 1.0 uhub1 at usb1 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 --- 97,103 pchb9 at pci0 dev 17 function 7 "VIA VX800 Host" rev 0x00 ppb4 at pci0 dev 19 function 0 "VIA VX800" rev 0x00 pci5 at ppb4 bus 6 ! "VIA HD Audio" rev 0x20 at pci0 dev 20 function 0 not configured usb1 at uhci0: USB revision 1.0 uhub1 at usb1 configuration 1 interface 0 "VIA UHCI root hub" rev 1.00/1.00 addr 1 usb2 at uhci1: USB revision 1.0 I have been running OBSD since 5.1 on this box without problem. Checking back through the dmesgs this is the first time msi has been used instead of acpi. Is the issue switching to use msi, or not using acpi as before? Any suggestins for things to try? I can live without sound but using the onboard NIC would be nice. Happy to try patches, but will need a while to setup builds from source. Here is the full dmesg from the 6.8 boot with azalia
Hugo package issue: data folder not detected
not sure if misc is the right place for this question. I installed the Hugo web framework from packages in 6.7. I’m trying to add data files to and it seems like the data files are silently ignored. Anybody else encountered this problem? Seems like the version I installed also likes the data folder to be capitalised. Couldn’t find anything online that indicates this to be a generic Hugo problem. regards
Re: man netstart(8) OpenBSD-6.8
25 Oct 2020, 01:25 by dera...@openbsd.org:
> Rachel Roch wrote:
>
>> Is it just me or is the man entry for netstart(8) missing a reference to
>> wg(4) ?
>>
>
> ... and 300 other network interfaces.
>
> In otherwords, no, it should not be there.
>
OK smart alec, then why bother enumerating any of the non-physical interfaces
on the man page ?
Afterall, the man page does state at the head of the list "During the system
boot, netstart is executed. netstart performs the following operations, in the
sequence given".
There is little point giving a half-assed description. Either you enumerate
ALL the non-physical interfaces, or otherwise you treat them the same way as
the physical ones ("Configure all the physical interfaces").
Otherwise you are failing to explain what happens to any of your "300 other
interfaces". Enumerate or don't enumerate, I don't care ... but surely it is
sensible to pay some reference to them.
Sheesh !
Re: ssl/libssl certificate validation broken?
On 22 Oct 22:59, Daniel Jakots wrote: > On Thu, 22 Oct 2020 21:49:20 -0500, "Rafael Possamai" > wrote: > > > >Hi Bob, it was in the middle of the night and I got quite kinda > > >stressed because all services depending on our ldap proxy stopped > > >working after the upgrade and it took me a while to figure the > > >problem out. > > > > Perhaps this is unsolicited advice, but maybe you can setup a test > > system first, perform major upgrade on it to make sure everything > > works. If so, then do it in production. > > > > Even better, try -current a few weeks before release (a possible hint > is -beta). This way you can get any encountered bug fixed in time for > -release. Your prod but also every one else will benefit from it. > > Cheers, > Daniel > That's a very good advice. I have for most services a very similiar setup at home (even with ldap). I run always -current at my workstations - one workstation is updated more or less daily and if that works I upgrade the 2nd one (important for ports too). At home I regularly install snapshots (~ every 2nd week) - because before I implement something at work I usually try and test that also at home - often with "cutting edge" features. When upgrading at work I always upgrade dev first. And all infrastructure critical services are "carped" so even when upgrading prod then node by node***. But exactly in this ssl case this failed for me with this bug. At home I use letsencrypt certs so that means ssl used /etc/ssl/cert.pem. The same for my dev landscape where I stored the L2 ca also in /etc/ssl/cert.pem (without remembering that I did that once). So unfortunately dev and prod were not 100% identical :( But lesson learned. I did already tons of automatization (salt/git) so I will focus more on that again (when I have the time ...). ***Also the latest bug in carp load balancing couldn't be properly detected in this way because in a mixed setup 6.7/6.8 it worked :/ -- wq: ~uw
Re: ssl/libssl certificate validation broken?
On 22 Oct 21:49, Rafael Possamai wrote: > >Hi Bob, it was in the middle of the night and I got quite kinda stressed > >because all services depending on our ldap proxy stopped working after the > >upgrade and it took me a while to figure the problem out. > > Perhaps this is unsolicited advice, but maybe you can setup a test system > first, perform major upgrade on it to make sure everything works. If so, then > do it in production. > That's a very good advice and I have such a setup. But unfortunately exactly in this case this didn't work because in my dev/test landscape I have other ssl certs (different domain name) which were stored in /etc/ssl/cert.pem :/ -- wq: ~uw
Re: man netstart(8) OpenBSD-6.8
On Sun, Oct 25, 2020 at 09:42:39AM +0100, Rachel Roch wrote:
>
> 25 Oct 2020, 01:25 by dera...@openbsd.org:
>
> > Rachel Roch wrote:
> >
> >> Is it just me or is the man entry for??netstart(8) missing a reference to
> >> wg(4) ?
> >>
> >
> > ... and 300 other network interfaces.
> >
> > In otherwords, no, it should not be there.
> >
>
> OK smart alec, then why bother enumerating any of the non-physical interfaces
> on the man page ???
>
> Afterall, the man page does state at the head of the list "During the system
> boot, netstart is executed. netstart performs the following operations, in
> the sequence given".??
>
> There is little point giving a half-assed description.?? Either you enumerate
> ALL the non-physical interfaces, or otherwise you treat them the same way as
> the physical ones ("Configure all the physical interfaces").
>
> Otherwise you are failing to explain what happens to any of your "300 other
> interfaces".?? Enumerate or don't enumerate, I don't care ... but surely it
> is sensible to pay some reference to them.
>
> Sheesh !
>
hi.
a diff would have been clearer - personally i originally thought you
were expecting an Xr in SEE ALSO for wg(4).
now i see you are on about the devices listed in DESCRIPTION.
unfortunately that list looks out of date and incomplete (or, always
possible, i have failed to understand the processing in netstart).
we currently have:
- configure non-physical:
trunk vlan pfsync carp
- routing
- rest of non-physical:
pppoe gif gre
whereas /etc/netstart is actually doing:
- configure non-physical:
aggr trunk svlan vlan carp pppoe
- routing
- rest of non-physical:
tun tap gif etherip gre egre mobileip pflow wg
we could try to keep this list up to date, but it may be easier to just
generally describe what netstart is doing.
i'll wait a little to see whether:
- i've understood what netstart is doing correctly
- there are compelling reasons to swing one way or the other
...then offer a diff.
jmc
