Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI 11 Perhaps they just don't have a proper setup or are not using it.
On Sat, Jul 29, 2023 at 04:34:17AM +, Philipp Buehler wrote: > Moin Chris, > > Am 29.07.2023 04:17 schrieb Chris Bennett: > > The network is 108.181.26.176/28. > > > > Right now,the first IP is 108.181.26.178 and the last regular address is > > 108.181.26.190, which might be wrong. I'm too tired to read any more > > man pages or web pages. I needed more than 2hrs of sleep. > > I'm super worn out, so forgive my mistakes. > > > > Any help appreciated. I don't want the next syspatch reboot to fail. > > To save mindboggling counting of 'f' or similar, just write this to > /etc/hostname.em1 > inet 108.181.26.178/28 > The ifconfig called from netstart will figure it out ;-) That's a headups > for everybody, so cc misc@. > Yes, there was a big delay when he put in one f too few. Besides changing IP ranges, they also just started pushing a single IP address that serves as everything, but also a different checkbox for the same thing for Linux only. I know essentially nothing about Linux besides the fact that I quickly tried several, but I didn't like them. I then ran into something mentioning OpenBSD. After reading the website, I saw that OpenBSD was and has been an excellent choice. No regrets. I already know from experience that if I asked them for any details about that networking change, I would NOT get a useful answer. After I got to multiple days, my goal had to be getting able to ssh in and start fixing things. Security through obscurity does not work. So I think it is well worth it to show and get help. I am so tired right now, that my Dad had a problem with sound using YouTube on a Firestick. I couldn't tell him even the simplest step, so I just had him reboot it. I'm going to kill everything that has outside access, get a good night's sleep and then change every password for inside stuff and all emails. Then I'm going to carefully read every man page, etc. until I understand everything fully. Now is the right time for this. Until recently, I only had a laptop stuck at 6.6 and a lousy phone hotspot or an even crappier access to almost useless wifi in places like libraries. Two used computers and a really great phone hotspot make everything good now. Thank you very much. > The current ifconfig em1 shows a bit wild setup for 108.181.26.179; but that > > is likely unintended and the wrong mask/bc will be gone with the above > setting. > > The route output shows several hosts in 108.136/108.137 ranges where there > is no corresponding setup given. > > But to reach the system via 108.181.26.178 again, this looks sound. > > HTH, > -- > pb > > PS: > tyo# cat /etc/hostname.vlan1 > vlandev vio0 > inet 108.181.26.178/28 > tyo# sh /etc/netstart vlan1 > tyo# ifconfig vlan1 > vlan1: flags=8843 mtu 1500 > lladdr fe:e1:bb:6e:63:36 > index 7 priority 0 llprio 3 > encap: vnetid none parent vio0 txprio packet rxprio outer > groups: vlan > media: Ethernet autoselect > status: active > inet 108.181.26.178 netmask 0xfff0 broadcast 108.181.26.191 > PPS: to check quickly on reachability of a gateway directly: > ping -I 108.181.26.178 -t 1 108.181.26.177 > and check arp table accordingly I will try this right now and save this email in the mailbox for important things to keep long term. -- Chris Bennett
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
On Sat, Jul 29, 2023 at 03:45:36AM +, All wrote: > Your network has first usable IP address 108.181.26.177, not > 108.181.26.178. Also, your broadcast address is 108.181.26.191 and not > 108.181.26.190 > Yes, I had things setup with 108.181.26.177 as the first IP, but they changed it. It was extremely frustrating to watch someone making changes that I did not request. They also don't seem to have the capability to read the support messages I sent them while actually making incorrect changes. Perhaps they just don't have a proper setup or are not using it. I could see what they were doing by refreshing the IPMI preview screen. But that really is just a poor set of images. It did let me see the contents of files if I refreshed the image at just the right moment. Getting them to type sh -x /etc/netstart or reboot despite giving them detailed instructions beforehand. It took about 1 1/2hrs to get someone to finally type sh /etc/netstart after doing all of the above. But I have never worked in that field, so I really don't know what goes on in their server farms. There was another issue that I did not know how to deal with. I will mention that in replying to another in this thread. -- Chris Bennett
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
Moin Chris, Am 29.07.2023 04:17 schrieb Chris Bennett: The network is 108.181.26.176/28. Right now,the first IP is 108.181.26.178 and the last regular address is 108.181.26.190, which might be wrong. I'm too tired to read any more man pages or web pages. I needed more than 2hrs of sleep. I'm super worn out, so forgive my mistakes. Any help appreciated. I don't want the next syspatch reboot to fail. To save mindboggling counting of 'f' or similar, just write this to /etc/hostname.em1 inet 108.181.26.178/28 The ifconfig called from netstart will figure it out ;-) That's a headups for everybody, so cc misc@. The current ifconfig em1 shows a bit wild setup for 108.181.26.179; but that is likely unintended and the wrong mask/bc will be gone with the above setting. The route output shows several hosts in 108.136/108.137 ranges where there is no corresponding setup given. But to reach the system via 108.181.26.178 again, this looks sound. HTH, -- pb PS: tyo# cat /etc/hostname.vlan1 vlandev vio0 inet 108.181.26.178/28 tyo# sh /etc/netstart vlan1 tyo# ifconfig vlan1 vlan1: flags=8843 mtu 1500 lladdr fe:e1:bb:6e:63:36 index 7 priority 0 llprio 3 encap: vnetid none parent vio0 txprio packet rxprio outer groups: vlan media: Ethernet autoselect status: active inet 108.181.26.178 netmask 0xfff0 broadcast 108.181.26.191 PPS: to check quickly on reachability of a gateway directly: ping -I 108.181.26.178 -t 1 108.181.26.177 and check arp table accordingly
Re: I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
Your network has first usable IP address 108.181.26.177, not 108.181.26.178. Also, your broadcast address is 108.181.26.191 and not 108.181.26.190 On Saturday, July 29, 2023 at 12:17:47 p.m. GMT+9, Chris Bennett wrote: Hi. My server company either was bought by another company or just hooked up new IP ranges. I have a super cheap server with 13 IP addresses. This only has ancient Java KVM which I can't hook up to, but I can use the console preview only as single refreshable images. So I had to coach them along. I had to really rush due to the cutoff date. I made a few mistakes, inet isn't spelled ine, etc. A power screwup, my fault. Watching someone trying to use ed was amusing. I had to get /home commented out since it needed manual fsck. It was a long day and all night and morning today. Everything is apparently working fine, but a little different than my previous setup. I would like some help to know if this setup will work after a reboot. I really don't want to ask for more help from support. The network is 108.181.26.176/28. Right now,the first IP is 108.181.26.178 and the last regular address is 108.181.26.190, which might be wrong. I'm too tired to read any more man pages or web pages. I needed more than 2hrs of sleep. I'm super worn out, so forgive my mistakes. Any help appreciated. I don't want the next syspatch reboot to fail. Chris Bennett cat /etc/hostname.em1 inet 108.181.26.178 0xfff0 108.181.26.190 inet alias 108.181.26.179 255.255.255.255 inet alias 108.181.26.180 255.255.255.255 inet alias 108.181.26.181 255.255.255.255 inet alias 108.181.26.182 255.255.255.255 inet alias 108.181.26.183 255.255.255.255 inet alias 108.181.26.184 255.255.255.255 inet alias 108.181.26.185 255.255.255.255 inet alias 108.181.26.186 255.255.255.255 inet alias 108.181.26.187 255.255.255.255 inet alias 108.181.26.188 255.255.255.255 inet alias 108.181.26.189 255.255.255.255 #inet alias 108.181.26.190 255.255.255.255 cat /etc/hosts 127.0.0.1 localhost ::1 localhost #108.181.26.177 gateway 108.181.26.178 bennettconstruction.us 108.181.26.179 strengthcouragewisdom.rocks 108.181.26.180 mail.strengthcouragewisdom.rocks 108.181.26.181 freedomforlife.rocks 108.181.26.182 mx.freedomforlife.rocks 108.181.26.183 bsd-sec.dev 108.181.26.184 mx.bennettconstruction.us 108.181.26.185 bsd-sec.com 108.181.26.186 mail.bsd-sec.com 108.181.26.187 cowboyup.xyz 108.181.26.188 mail.cowboyup.xyz 108.181.26.189 capuchado.com 108.181.26.190 # Using for development, unassigned cat /etc/myname bennettconstruction.us cat /etc/mygate 108.181.26.177 route -n show Routing tables Internet: Destination Gateway Flags Refs Use Mtu Prio Iface default 108.181.26.177 UGS 11 25504 - 8 em1 108/8 108.181.26.179 UCn 11 0 - 4 em1 108.136.59.3 00:1f:6d:eb:60:00 UHLc 0 4 - 3 em1 108.136.125.137 00:1f:6d:eb:60:00 UHLc 0 2 - 3 em1 108.136.179.191 00:1f:6d:eb:60:00 UHLc 0 9 - 3 em1 108.136.182.161 00:1f:6d:eb:60:00 UHLc 0 9 - 3 em1 108.136.235.206 00:1f:6d:eb:60:00 UHLc 0 8 - 3 em1 108.136.238.232 00:1f:6d:eb:60:00 UHLc 0 10 - 3 em1 108.136.248.92 00:1f:6d:eb:60:00 UHLc 0 9 - 3 em1 108.137.2.3 00:1f:6d:eb:60:00 UHLc 0 3 - 3 em1 108.137.73.28 00:1f:6d:eb:60:00 UHLc 0 15 - 3 em1 108.137.74.160 00:1f:6d:eb:60:00 UHLc 0 4 - 3 em1 108.137.155.209 00:1f:6d:eb:60:00 UHLc 0 3 - 3 em1 108.181.26.176/28 108.181.26.178 UCn 1 2 - 4 em1 108.181.26.177 00:1f:6d:eb:60:00 UHLch 1 44 - 3 em1 108.181.26.178 00:25:90:6c:43:43 UHLl 0 4741 - 1 em1 108.181.26.179 00:25:90:6c:43:43 UHLl 0 3443 - 1 em1 108.181.26.180 00:25:90:6c:43:43 UHLl 0 4510 - 1 em1 108.181.26.180/32 108.181.26.180 UCn 0 0 - 4 em1 108.181.26.181 00:25:90:6c:43:43 UHLl 0 3004 - 1 em1 108.181.26.181/32 108.181.26.181 UCn 0 0 - 4 em1 108.181.26.182 00:25:90:6c:43:43 UHLl 0 4192 - 1 em1 108.181.26.182/32 108.181.26.182 UCn 0 0 - 4 em1 108.181.26.183 00:25:90:6c:43:43 UHLl 0 4767 - 1 em1 108.181.26.183/32 108.181.26.183 UCn 0 0 - 4 em1 108.181.26.184 00:25:90:6c:43:43 UHLl 0 8119 - 1 em1 108.181.26.184/32 108.181.26.184 UCn 0 0 - 4 em1 108.181.26.185 00:25:90:6c:43:43 UHLl 0 4902 - 1 em1 108.181.26.185/32 108.181.26.185 UCn 0 0 - 4 em1 108.181.26.186 00:25:90:6c:43:43 UHLl 0 3049 - 1 em1 108.181.26.186/
I need help to see if I can reboot new network OK. Wild misadventures with non-OpenBSD support and bad IPMI
Hi. My server company either was bought by another company or just hooked up new IP ranges. I have a super cheap server with 13 IP addresses. This only has ancient Java KVM which I can't hook up to, but I can use the console preview only as single refreshable images. So I had to coach them along. I had to really rush due to the cutoff date. I made a few mistakes, inet isn't spelled ine, etc. A power screwup, my fault. Watching someone trying to use ed was amusing. I had to get /home commented out since it needed manual fsck. It was a long day and all night and morning today. Everything is apparently working fine, but a little different than my previous setup. I would like some help to know if this setup will work after a reboot. I really don't want to ask for more help from support. The network is 108.181.26.176/28. Right now,the first IP is 108.181.26.178 and the last regular address is 108.181.26.190, which might be wrong. I'm too tired to read any more man pages or web pages. I needed more than 2hrs of sleep. I'm super worn out, so forgive my mistakes. Any help appreciated. I don't want the next syspatch reboot to fail. Chris Bennett cat /etc/hostname.em1 inet 108.181.26.178 0xfff0 108.181.26.190 inet alias 108.181.26.179 255.255.255.255 inet alias 108.181.26.180 255.255.255.255 inet alias 108.181.26.181 255.255.255.255 inet alias 108.181.26.182 255.255.255.255 inet alias 108.181.26.183 255.255.255.255 inet alias 108.181.26.184 255.255.255.255 inet alias 108.181.26.185 255.255.255.255 inet alias 108.181.26.186 255.255.255.255 inet alias 108.181.26.187 255.255.255.255 inet alias 108.181.26.188 255.255.255.255 inet alias 108.181.26.189 255.255.255.255 #inet alias 108.181.26.190 255.255.255.255 cat /etc/hosts 127.0.0.1 localhost ::1 localhost #108.181.26.177 gateway 108.181.26.178bennettconstruction.us 108.181.26.179strengthcouragewisdom.rocks 108.181.26.180mail.strengthcouragewisdom.rocks 108.181.26.181freedomforlife.rocks 108.181.26.182mx.freedomforlife.rocks 108.181.26.183bsd-sec.dev 108.181.26.184mx.bennettconstruction.us 108.181.26.185bsd-sec.com 108.181.26.186mail.bsd-sec.com 108.181.26.187cowboyup.xyz 108.181.26.188mail.cowboyup.xyz 108.181.26.189capuchado.com 108.181.26.190# Using for development, unassigned cat /etc/myname bennettconstruction.us cat /etc/mygate 108.181.26.177 route -n show Routing tables Internet: DestinationGatewayFlags Refs Use Mtu Prio Iface default108.181.26.177 UGS 1125504 - 8 em1 108/8 108.181.26.179 UCn 110 - 4 em1 108.136.59.3 00:1f:6d:eb:60:00 UHLc 04 - 3 em1 108.136.125.13700:1f:6d:eb:60:00 UHLc 02 - 3 em1 108.136.179.19100:1f:6d:eb:60:00 UHLc 09 - 3 em1 108.136.182.16100:1f:6d:eb:60:00 UHLc 09 - 3 em1 108.136.235.20600:1f:6d:eb:60:00 UHLc 08 - 3 em1 108.136.238.23200:1f:6d:eb:60:00 UHLc 0 10 - 3 em1 108.136.248.92 00:1f:6d:eb:60:00 UHLc 09 - 3 em1 108.137.2.300:1f:6d:eb:60:00 UHLc 03 - 3 em1 108.137.73.28 00:1f:6d:eb:60:00 UHLc 0 15 - 3 em1 108.137.74.160 00:1f:6d:eb:60:00 UHLc 04 - 3 em1 108.137.155.20900:1f:6d:eb:60:00 UHLc 03 - 3 em1 108.181.26.176/28 108.181.26.178 UCn12 - 4 em1 108.181.26.177 00:1f:6d:eb:60:00 UHLch 1 44 - 3 em1 108.181.26.178 00:25:90:6c:43:43 UHLl 0 4741 - 1 em1 108.181.26.179 00:25:90:6c:43:43 UHLl 0 3443 - 1 em1 108.181.26.180 00:25:90:6c:43:43 UHLl 0 4510 - 1 em1 108.181.26.180/32 108.181.26.180 UCn00 - 4 em1 108.181.26.181 00:25:90:6c:43:43 UHLl 0 3004 - 1 em1 108.181.26.181/32 108.181.26.181 UCn00 - 4 em1 108.181.26.182 00:25:90:6c:43:43 UHLl 0 4192 - 1 em1 108.181.26.182/32 108.181.26.182 UCn00 - 4 em1 108.181.26.183 00:25:90:6c:43:43 UHLl 0 4767 - 1 em1 108.181.26.183/32 108.181.26.183 UCn00 - 4 em1 108.181.26.184 00:25:90:6c:43:43 UHLl 0 8119 - 1 em1 108.181.26.184/32 108.181.26.184 UCn00 - 4 em1 108.181.26.185 00:25:90:6c:43:43 UHLl 0 4902 - 1 em1 108.181.26.185/32 108.181.26.185 UCn00 - 4 em1 108.181.26.186 00:25:90:6c:43:43 UHLl 0 3049 - 1 em1 108.181.26.186/32 108.181.26.186 UCn00 - 4 em1 108.181.26.187 00:25:90:6c:43:43 UHLl
Re: dmesg of ThinkPad P14s G3 (AMD)
On Fri, Jul 28, 2023 at 03:32:38PM +0200, Marco van Hulten wrote: > Doesn't work: > - Wi-Fi (soldered) > "Qualcomm QCNFA765" rev 0x01 at pci2 dev 0 function 0 not configured This is being worked on but will still take a while (not sure how long).
Re: Upgrade: Unbound constraint let fw_update always fail
On Jul 28, 2023 20:00:24 I was still sleeping when suddenly Paul said: > If you really want to go without DNS resolution, I invite you to > travel back a few decades and learn about /etc/hosts. did you hear my "True, the hosts.. Oh Jesus!"... ? Many thx! :D -- Daniele Bonini
Re: Upgrade: Unbound constraint let fw_update always fail
I don't understand - if you configure your system to not have working DNS resolution, then you will not have working DNS resolution. fw_update needs working DNS resolution, so yeah .. if you break the latter, you break the former. Don't break DNS resolution. You really get what you pay for. Having said all that... If you really want to go without DNS resolution, I invite you to travel back a few decades and learn about /etc/hosts. Maybe you can FTP a hosts file from somewhere, for that true historic experience .. but alternatively you can also echo 2a02:898:28:500::3 firmware.openbsd.org | doas tee -a /etc/hosts Good luck with that. Paul 'WEiRD' de Weerd NB: full disclosure, the IP address I gave is the firmware mirror hosted by me; I didn't want to point people to someone else's .. but I also kinda hope noone (else) is foolish enough to break their DNS resolution in such a way to need this kind of tomfoolery. On Tue, Jul 25, 2023 at 09:58:35AM +0200, Daniele B. wrote: | | Hello, | | Just coming from my fresh upgrade to OpenBSD 7.3 and thanks again for | it.. ;) | | No particular problem except my realization that with my settings | (unbound started manually) fw_update goes to fail (all the three | attempts) on each (unattended) upgrade. If fw_update happens to be a | constraint for a successful upgrade, and luckily was not the case this | time, bad times for sure.. | | Any suggestion about it? Thanks! | | | | -- | Daniele Bonini | | -- >[<++>-]<+++.>+++[<-->-]<.>+++[<+ +++>-]<.>++[<>-]<+.--.[-] http://www.weirdnet.nl/
Re: Ryzen 9 (7x000) users: do you experience hangs?
(Apologies for the late reply, I've been off for a few days and have
spent very little time behind a keyboard)
I have such issues.
CPU model:
hw.model=AMD Ryzen 9 7950X 16-Core Processor
Motherboard:
hw.vendor=ASUS
hw.product=ProArt X670E-CREATOR WIFI
Have you experienced crashes:
Yes, after approximately 17 hours of uptime. Could be 16,
could be 18, but that ballpark. I've been trying for months
to identify what causes this, but no luck so far.
dmesg
(at the end)
So far, BIOS updates haven't helped but I see there's a newer BIOS
available again. Will try to update soon, but am not holding my
breath that this will fix things.
Note that (at least for me) it's not really a full crash. There's no
response on the glass console or over the network but since I have
serial console access, when I'm logged in there as root (before the
system gets in this weird state) I can still `reboot -q` (just
`reboot` gets stuck, but the (advised against) use of '-q' allows the
reboot to succeed and the machine reboots cleanly). I'd be interested
if anyone else who has these issues could set up serial console and
see if they get the same behaviour. Alternatively, start a tmux
session as root and do a `sleep ${WAIT_FOR_CRASH}; reboot -q` (with
appropriate values for WAIT_FOR_CRASH, obviously)
Paul
--- dmesg
OpenBSD 7.3-current (GENERIC.MP) #58: Fri Jul 28 15:50:42 CEST 2023
we...@pom.alm.weirdnet.nl:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 136444977152 (130124MB)
avail mem = 132290076672 (126161MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x794a3000 (81 entries)
bios0: vendor American Megatrends Inc. version "1415" date 05/16/2023
bios0: ASUS ProArt X670E-CREATOR WIFI
efi0 at bios0: UEFI 2.8
efi0: American Megatrends rev 0x5001a
acpi0 at bios0: ACPI 6.4Undefined scope: \\_SB_.PCI0.GPP7.UP00.DP40.UP00.DP68
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SSDT SSDT SSDT FIDT MCFG HPET WDRT FPDT VFCT BGRT WPBT
TPM2 SSDT CRAT CDIT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT SSDT SSDT
SSDT
acpi0: wakeup devices GPP3(S4) GPP4(S4) GPP5(S4) GPP6(S4) GP17(S4) XHC0(S4)
XHC1(S4) XHC2(S4) GPP0(S4) GPP1(S4) GPP2(S4) GPP7(S4) UP00(S4) DP40(S4)
UP00(S4) DP00(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimcfg0 at acpi0
acpimcfg0: addr 0xf000, bus 0-127
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 9 7950X 16-Core Processor, 4500.01 MHz, 19-61-02
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line
8-way L2 cache, 32MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 25MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: AMD Ryzen 9 7950X 16-Core Processor, 4500.00 MHz, 19-61-02
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMAP,AVX512IFMA,CLFLUSHOPT,CLWB,AVX512CD,SHA,AVX512BW,AVX512VL,AVX512VBMI,UMIP,PKU,L1DF,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES
cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line
8-way L2 cache, 32MB 64b/line 16-way L3 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 4 (application processor)
cpu2: AMD Ryzen 9 7950X 16-Core Processor, 4500.00 MHz, 19-61-02
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,AVX512F,AVX512DQ,RDSEED,ADX,SMA
Any experiences with OpenBSD and Dell HBA355i (and/or Dell R350)
As per subject really, does anyone on-list have experience with the Dell HBA355i controller and/or Dell350 ? I might have the chance to get my hands on an R350 which ideally I'd like to use with OpenBSD and so wanted to reach out the community to find out if there is anything I should be aware of. Thanks !
Re: Samsung NVMe M.2 SSD 970 EVO Plus fails to attach on VisionFive 2 (JH7110 SoC) board
Zitat von "Peter J. Philipp" : [tying in misc@ for this resource] On Fri, Jul 28, 2023 at 03:26:54PM +0200, develo...@robert-palm.de wrote: Many thanks! Please, will you commit it so I can test it with the next snapshot version ? I have already contacted Robert (?) privately, here it is publically. I have exported my QEMU script on github, in case anyone else needs to compile RISCV64 kernels and images (without having to wait on snapshots): https://github.com/pbug44/openbsd-riscv-misc/blob/master/start-rv64.sh I use this config to compile kernels for riscv64 (on a rpi4b it's slow!). Best Regards, -peter -- Over thirty years experience on Unix-like Operating Systems starting with QNX. Yes, many thanks for your script and kind offer! Excited if this will work - would like to figure out how to do it later on by myself, firstly. Did not do any kernel compile yet :)
Re: Samsung NVMe M.2 SSD 970 EVO Plus fails to attach on VisionFive 2 (JH7110 SoC) board
[tying in misc@ for this resource] On Fri, Jul 28, 2023 at 03:26:54PM +0200, develo...@robert-palm.de wrote: > Many thanks! Please, will you commit it so I can test it with the next > snapshot version ? I have already contacted Robert (?) privately, here it is publically. I have exported my QEMU script on github, in case anyone else needs to compile RISCV64 kernels and images (without having to wait on snapshots): https://github.com/pbug44/openbsd-riscv-misc/blob/master/start-rv64.sh I use this config to compile kernels for riscv64 (on a rpi4b it's slow!). Best Regards, -peter -- Over thirty years experience on Unix-like Operating Systems starting with QNX.
dmesg of ThinkPad P14s G3 (AMD)
Works: - Camera - Audio - Touchscreen - Touchpad, red nub and buttons - Ethernet - HDMI output - Hibernation (ZZZ) Doesn't work: - Wi-Fi (soldered) - Microphone - Suspend (zzz): no S3 Works well otherwise. Work-around for Wi-Fi: I use a phone with USB tethering for wireless network. Work-around for microphone: external headset. OpenBSD 7.3-current (GENERIC.MP) #1318: Thu Jul 27 17:39:18 MDT 2023 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 12619960320 (12035MB) avail mem = 12217798656 (11651MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.3 @ 0x73688000 (70 entries) bios0: vendor LENOVO version "R23ET65W (1.35 )" date 03/21/2023 bios0: LENOVO 21J5002WGE efi0 at bios0: UEFI 2.7 efi0: Lenovo rev 0x1290 acpi0 at bios0: ACPI 6.3 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SSDT SSDT SSDT SSDT SSDT SSDT TPM2 MSDM BATB HPET APIC MCFG SBST WSMT SSDT CRAT CDIT VFCT FPDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT UEFI SSDT IVRS SSDT SSDT BGRT acpi0: wakeup devices GPP5(S4) GPP6(S0) GPP7(S0) LID_(S4) SLPB(S3) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpihpet0 at acpi0: 14318180 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.01 MHz, 19-44-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu1: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu1: smt 1, core 0, package 0 tsc: cpu0/cpu1: sync test failed timecounter: active counter changed: tsc -> acpihpet0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu2: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.01 MHz, 19-44-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,RDRAND,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TCE,TOPEXT,CPCTR,DBKP,PCTRL3,MWAITX,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,PQM,RDSEED,ADX,SMAP,CLFLUSHOPT,CLWB,SHA,UMIP,PKU,IBPB,IBRS,STIBP,STIBP_ALL,IBRS_PREF,IBRS_SM,SSBD,XSAVEOPT,XSAVEC,XGETBV1,XSAVES cpu3: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 512KB 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache cpu3: smt 1, core 1, package 0 cpu4 at mainbus0: apid 4 (application processor) cpu4: AMD Ryzen 7 PRO 6850U with Radeon Graphics, 2700.00 MHz, 19-44-01 cpu4: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,FMA3,CX16,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCN
