Tryton build fail and stdarg.h
Hello everyone, I was trying to build Tryton on 6.2 and it fails complaining that stdarg.h is not found, this is related to the libxml2. Can somebody please point me to the right direction through this? Further, what other option can I try as free and pen source ERP for OpenBSD 6.2? Looking forward for your advise. Thanks.
Re: Hard disk controller not recognized
On 02/12/18 12:07, Xianwen Chen wrote: Dear OpenBSD users, I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The installation was done by taking out the hard drive and hook it through a USB reader to another machine. I boot the hard drive through Legacy Boot menu. The boot process stops with root device: It is possible to boot through bsd.rd. However, the hard drive is not recognized there. Here is the dmesg from bsd.rd: [snip] Xianwen, Obviously the best thing is for IT to release the BIOS control to you, but if they won't, get a USB SATA disk interface, and try to use that. Your IT department might have figured out how to interfere with that too, but that might be a solution. You'd have to keep that external disk and its interface with you, but at least you could use OpenBSD. --STeve Andre'
Re: Why is so slow the download speed in OpenBSD?
I've tried different channels and also different modes, I even replaced the 6.2 firmware with the snapshot (the snapshot version is a little bit bigger in size) hoping that it will work better. To be sure with the configuration I used the same channel and mode with which in other OS (Windows) is working well. So now I'm even more close to the idea that it is a bug in the firmware. If somebody can guaranty that it is not from the firmware than it should be a configuration issue, but as I stated before I have not touched anything related to network configuration, I just made a fresh install and the basic config to set up xfce, that's all. Probably I will fill out a bug report. Thanks for the support, If you have some other ideas please let me know. On Monday, February 12, 2018 2:48 PM, "ed...@pettijohn-web.com" wrote: Try different channels. See the wireless section of ifconfig(8). On Feb 12, 2018 3:02 AM, Zsolt Kantor wrote: > > I tried that, but as Edgar said it downloaded all the firmware's from the > site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. > > I want to send a bug report, but (with a big b) the question is who gonna > debug the firmware, because as I know those firmware's are non-free code, so > maybe it is not even the 'job' of the OpenBSD developers to fix the error. > > > On Monday, February 12, 2018 5:41 AM, Tom Smyth > wrote: > > > > Hi Zolt > > when your laptop is on line try > > fw_update -a > command to update firmware... you probably were not online when the > firmware update command ran (on first boot after install) > See what happens when you run that command .. > > Thanks > Tom Smyth > > On 11 February 2018 at 23:15, Zsolt Kantor wrote: > > Below I provide full information from ifconfig, route and a full dmesg. By > > the way, I think this is a BUG in the wireless firmware that I'm using > > (downloaded from the OpenBSD firmware site). I say this because I found > > this line in the dmesg output: wpi0: fatal firmware error > > > > So below are the outputs. > > > > ifconfig output: > > > > lo0: flags=8049 mtu 32768 > > index 4 priority 0 llprio 3 > > groups: lo > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff00 > > re0: flags=8802 mtu 1500 > > lladdr 00:1f:16:03:90:fe > > index 1 priority 0 llprio 3 > > media: Ethernet autoselect (none) > > status: no carrier > > wpi0: flags=8843 mtu 1500 > > lladdr 00:1f:3c:8d:aa:a2 > > index 2 priority 4 llprio 3 > > groups: wlan egress > > media: IEEE802.11 autoselect (DS1 mode 11g) > > status: active > > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey > displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > > enc0: flags=0<> > > index 3 priority 0 llprio 3 > > groups: enc > > status: active > > pflog0: flags=141 mtu 33136 > > index 5 priority 0 llprio 3 > > groups: pflog > > > > > > > > route -n show output: > > > > Routing tables > > > > Internet: > > DestinationGatewayFlags Refs Use Mtu Prio > > Iface > > default192.168.0.1UGS3 450 -12 wpi0 > > 224/4 127.0.0.1 URS0 12 32768 8 lo0 > > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > > 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 > > 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > > 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 > > > > Internet6: > > DestinationGatewayFlags > > Refs Use Mtu Prio Iface > > ::/96 ::1UGRS > > 00 32768 8 lo0 > > ::/104 ::1UGRS > > 00 32768 8 lo0 > > ::1::1UHhl > > 14 34 32768 1 lo0 > > ::127.0.0.0/104::1UGRS > > 00 32768 8 lo0 > > ::224.0.0.0/100::1UGRS > > 00 32768 8 lo0 > > ::255.0.0.0/104::1UGRS > > 00 32768 8 lo0 > > :::0.0.0.0/96 ::1UGRS > > 00 32768 8 lo0 > > 2002::/24 ::1UGRS > > 00 32768 8 lo0 > > 2002:7f00::/24 ::1
Re: tor inside vmm, horribly slow?!
> Am 12.02.2018 um 00:38 schrieb Jiri B : > > Hi, > > has anybody tried to run tor inside vmm guest? > > it's horrible slow, just doing 'tor-resolve $dnsname' takes > sometimes ages. Perhaps this has nothing to do with vmm. I am not a computer expert, just a normal user (so please don't ask me to difficult questions), but I run tor on my computer at home (so it's real hardware and no vmm). Since upgrading OpenBSD from | OpenBSD 6.2-current (GENERIC.MP) #399: Fri Feb 2 18:28:58 MST 2018 |dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP to | OpenBSD 6.2-current (GENERIC.MP) #4: Sat Feb 10 18:04:19 MST 2018 |dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP my tor server also has problems. /var/log/daemon: | Feb 11 20:15:50 server Tor[54286]: Your system clock just jumped 115 seconds forward; assuming established circuits no longer work. | Feb 11 20:16:02 server Tor[54286]: Tor has successfully opened a circuit. Looks like client functionality is working. | Feb 11 20:16:02 server Tor[54286]: Tor has successfully opened a circuit. Looks like client functionality is working. | Feb 11 20:24:43 server Tor[54286]: Your system clock just jumped 299 seconds forward; assuming established circuits no longer work. | Feb 11 20:26:24 server Tor[54286]: tor_assertion_failed_: Bug: src/or/channel.c:1503: channel_closed: Assertion CHANNEL_CONDEMNED(chan) failed; aborting. (on Tor 0.3.2.9 9e8b762fcecfece6) | Feb 11 20:26:24 server Tor[54286]: Bug: Assertion CHANNEL_CONDEMNED(chan) failed in channel_closed at src/or/channel.c:1503. (Stack trace not available) (on Tor 0.3.2.9 9e8b762fcecfece6) dmesg: OpenBSD 6.2-current (GENERIC.MP) #4: Sat Feb 10 18:04:19 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8351621120 (7964MB) avail mem = 8091496448 (7716MB) enter_shared_special_pages: entered idt page va 0x8001 pa 0x1d5c000 enter_shared_special_pages: entered kutext page va 0x81833000 pa 0x1833000 enter_shared_special_pages: entered kutext page va 0x81834000 pa 0x1834000 enter_shared_special_pages: entered kutext page va 0x81835000 pa 0x1835000 enter_shared_special_pages: entered kudata page va 0x81acb000 pa 0x1acb000 cpu_enter_pages: entered tss+gdt page at va 0x81aa2000 pa 0x1aa2000 cpu_enter_pages: entered t.stack page at va 0x81aa3000 pa 0x1aa3000 cpu_enter_pages: cif_tss.tss_rsp0 = 0x81aa33e0 mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xedc10 (87 entries) bios0: vendor LENOVO version "FBKTCQAUS" date 12/16/2017 bios0: LENOVO ThinkServer TS140 acpi0 at bios0: rev 2 acpi0: sleep states S0 S5 acpi0: tables DSDT FACP APIC FPDT FIDT TCPA DBGP LUFT SSDT SSDT MCFG HPET SSDT SSDT ASF! DMAR EINJ ERST HEST BERT BGRT acpi0: wakeup devices UAR1(S0) PXSX(S0) RP01(S0) PXSX(S0) PXSX(S0) PXSX(S0) RP04(S0) PXSX(S0) PXSX(S0) PXSX(S0) PXSX(S0) GLAN(S0) EHC1(S0) EHC2(S0) XHC_(S0) HDEF(S0) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat lapic_map: entered lapic page va 0x81aa6000 pa 0xfee0 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz, 3492.47 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpitimer0: recalibrated TSC frequency 3292379149 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE cpu1 at mainbus0cpu_enter_pages: entered tss+gdt page at va 0x80002200 pa 0x10f184000 cpu_enter_pages: entered t.stack page at va 0x800022001000 pa 0x10f185000 cpu_enter_pages: cif_tss.tss_rsp0 = 0x8000220013e0 : apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E3-1226 v3 @ 3.30GHz, 3491.92 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0cpu_enter_pages: entered tss+gdt page at va 0x800022011000 pa 0x10f18f000 cpu_enter_pages: entered t.stack page at va 0x800022012000 pa 0x10f19 cpu_enter_pages: cif_tss.tss_rsp0 = 0x8000220123e0
Re: Flask app with chrooted httpd
On Mon, 12 Feb 2018 14:42:53 +0100 > Did anyone use httpd to serve a flask app (python)? > I found this [1], but its a little outdated (python < 3) and makes me > wonder about safety, because of all those dependencies copied in > chroot. > > Any advice ? It seems python requires RWX mem by default. Ridiculous considering it is a relatively new tool. Relegates it to, avoid for anything important for me. If you still wish to use it, you will likely need to add the wxallowed mount option to the partition your chroot is on these days. Otherwise you will see messages about the kernel killing it in /var/log/messages There was a recent discussion about a non wrx port, not sure what that would break or not or maybe just affect performance.
Re: Flask app with chrooted httpd
Why not a virtualenv? Just don’t use system python that need packages on applications anywhere on anything. On Mon, 12 Feb 2018 at 20:56, Thuban wrote: > I forgot the link, my bad: > > [1] : http://www.hydrus.org.uk/journal/openbsd-httpd.html >
Re: Flask app with chrooted httpd
I forgot the link, my bad: [1] : http://www.hydrus.org.uk/journal/openbsd-httpd.html signature.asc Description: PGP signature
Re: For a FFS on an SSD, which of "-o" nil, "sync" &/ "softdep" is more data-safe and fast?
> Hi! > > If I understand mount(8) (http://man.openbsd.org/mount) right, FFS > mounts have a metadata I/O mode and a data I/O mode. By default, > metadata is accessed synchronously and data is accessed > asynchronously. > > "-o sync" will force both to synchronous mode, and "-o softdep" would > change the metadata I/O mode to the alternative softdep access mode. No. softdep and async are different concepts. Default: metadata, data accordingly: sync, async not that there is async - not softdep You can do the oposite by options: nosync, noasync It would mean asynchronous mode for metadata and synchronous for data - which is stupid (slow and dangerous), so don't. I think default are quite good for SSD. Maybe add noatime for some partitions.
Re: Hard disk controller not recognized
Dear Mestre, Thank you. I agree! Sincerely, Xianwen On 2/12/18, Ricardo Mestre wrote: > Hi Xianwen, > > I guess this is one of "you're-on-your-own" cases, the BIOS being locked by > IT I'm even surprised you're allowed to install a different OS on the > machine. > > For starters I'd speak directly with them and check what are you allowed or > not to do with the machine. > > /mestre > > On Monday, 12 February 2018, Xianwen Chen wrote: >> Dear Mike, >> >> From the output of dmesg, I guess so. The BIOS is locked by IT >> administrators. Is there some way that I can use OpenBSD while the >> controller is set to RAID mode? >> >> Sincerely, >> Xianwen >> >> On 2/12/18, Mike Larkin wrote: >> > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: >> >> Dear OpenBSD users, >> >> >> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The >> >> installation was done by taking out the hard drive and hook it through >> >> a USB reader to another machine. >> >> >> >> I boot the hard drive through Legacy Boot menu. The boot process stops >> >> with >> >> root device: >> >> >> >> It is possible to boot through bsd.rd. However, the hard drive is not >> >> recognized there. >> >> >> >> Here is the dmesg from bsd.rd: >> >> >> >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 >> >> >> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD >> >> real mem = 17064423424 (16273MB) >> >> avail mem = 16543502336 (15777MB) >> >> mainbus0 at root >> >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) >> >> bios0: vendor Dell Inc. version "A16" date 01/18/2016 >> >> bios0: Dell Inc. Latitude E6330 >> >> acpi0 at bios0: rev 2 >> >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR >> >> ASF! SSDT SLIC BGRT >> >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> >> cpu0 at mainbus0: apid 0 (boot processor) >> >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz >> >> cpu0: >> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT >> >> cpu0: 256KB 64b/line 8-way L2 cache >> >> cpu0: TSC frequency 2891029960 Hz >> >> cpu0: apic clock running at 99MHz >> >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE >> >> cpu at mainbus0: not configured >> >> cpu at mainbus0: not configured >> >> cpu at mainbus0: not configured >> >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins >> >> acpiprt0 at acpi0: bus 0 (PCI0) >> >> acpiprt1 at acpi0: bus -1 (P0P1) >> >> acpiprt2 at acpi0: bus 1 (RP01) >> >> acpiprt3 at acpi0: bus 2 (RP02) >> >> acpiprt4 at acpi0: bus -1 (RP05) >> >> acpiprt5 at acpi0: bus 11 (RP06) >> >> acpiprt6 at acpi0: bus -1 (RP07) >> >> acpiprt7 at acpi0: bus -1 (RP08) >> >> acpiprt8 at acpi0: bus -1 (PEG0) >> >> acpiprt9 at acpi0: bus -1 (PEG1) >> >> acpiprt10 at acpi0: bus -1 (PEG2) >> >> acpiprt11 at acpi0: bus -1 (PEG3) >> >> acpiprt12 at acpi0: bus 3 (RP03) >> >> acpiprt13 at acpi0: bus 7 (RP04) >> >> acpiec0 at acpi0 >> >> acpicpu at acpi0 not configured >> >> acpitz at acpi0 not configured >> >> "INT3F0D" at acpi0 not configured >> >> "DLLK0533" at acpi0 not configured >> >> "DLL0533" at acpi0 not configured >> >> "PNP0401" at acpi0 not configured >> >> "SMO8810" at acpi0 not configured >> >> "*pnp0c14" at acpi0 not configured >> >> "PNP0C0D" at acpi0 not configured >> >> "PNP0C0C" at acpi0 not configured >> >> "PNP0C0E" at acpi0 not configured >> >> "ACPI0003" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "DELLABCE" at acpi0 not configured >> >> "PNP0C31" at acpi0 not configured >> >> pci0 at mainbus0 bus 0 >> >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 >> >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 >> >> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) >> >> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi >> >> usb0 at xhci0: USB revision 3.0 >> >> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev >> >> 3.00/1.00 addr 1 >> >> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured >> >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address >> >> b8:ca:3a:d8:5f:2e >> >> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 >> >> int >> >> 16 >> >> usb1 at ehci0: USB revision 2.0 >> >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev >> >> 2.00/1.00 addr 1 >> >> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not >> >> configured >> >> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi >> >> pci1 at ppb0 bus 1 >> >> ppb1 at pci0 dev 28 function 1 "Intel 7 Series P
Re: OpenBSD Memory protection mechanisms that are not enabled by default?
There is no default malloc.conf file for good reasons. The performance impacts are substantial. Additionally they stop bad behavior by aborting the program. If you are not a programmer then you will be hard pressed to fix the relevant applications. Michael On Mon, Feb 12, 2018 at 9:51 AM Hess THR wrote: > Hello! > > Besides the "S" option for malloc.conf and increasing kern.stackgap_random > and removing the wxallowed mount option, what else memory-related hardening > mechanism are in OpenBSD that can be turned on and it is not enabled by > default? > > Even options would be useful if we have to re-compile the kernel, if > minimal source code modification is needed. > > Tried to get lists/ideas from grsecurity (if there is any, that is not > already used in OpenBSD), but it is hard when you are not a programmer. > > Many thanks. > >
Re: Hard disk controller not recognized
Dear Peter, Thank you. There is probably such an option in BIOS. Unfortunately I do not have access to BIOS at the moment, because it is locked by administrators of my IT department. Sincerely, Xianwen On 2/12/18, Peter N. M. Hansteen wrote: > On 02/12/18 18:07, Xianwen Chen wrote: >> Dear OpenBSD users, >> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The >> installation was done by taking out the hard drive and hook it through >> a USB reader to another machine. >> >> I boot the hard drive through Legacy Boot menu. The boot process stops >> with >> root device: >> >> It is possible to boot through bsd.rd. However, the hard drive is not >> recognized there. > > I'm guessing that for some reason or the other the controller is set to > 'hardware raid' mode (which OpenBSD does not support) instead of a more > useful SATA mode: > >> pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA, >> channel 0 wired to native-PCI, channel 1 wired to native-PCI >> pciide0: using apic 2 int 19 for native-PCI interrupt > > See if the BIOS offers a choice of modes for the controller, hopefully > there is a SATA option. > > - Peter > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. >
Re: Hard disk controller not recognized
Thank you Mike! Sincerely, Xianwen On 2/12/18, Mike Larkin wrote: > On Mon, Feb 12, 2018 at 05:25:57PM +, Xianwen Chen wrote: >> Dear Mike, >> >> >From the output of dmesg, I guess so. The BIOS is locked by IT >> administrators. Is there some way that I can use OpenBSD while the >> controller is set to RAID mode? >> >> Sincerely, >> Xianwen >> > > not that I know of > >> On 2/12/18, Mike Larkin wrote: >> > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: >> >> Dear OpenBSD users, >> >> >> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The >> >> installation was done by taking out the hard drive and hook it through >> >> a USB reader to another machine. >> >> >> >> I boot the hard drive through Legacy Boot menu. The boot process stops >> >> with >> >> root device: >> >> >> >> It is possible to boot through bsd.rd. However, the hard drive is not >> >> recognized there. >> >> >> >> Here is the dmesg from bsd.rd: >> >> >> >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 >> >> >> >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD >> >> real mem = 17064423424 (16273MB) >> >> avail mem = 16543502336 (15777MB) >> >> mainbus0 at root >> >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) >> >> bios0: vendor Dell Inc. version "A16" date 01/18/2016 >> >> bios0: Dell Inc. Latitude E6330 >> >> acpi0 at bios0: rev 2 >> >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR >> >> ASF! SSDT SLIC BGRT >> >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> >> cpu0 at mainbus0: apid 0 (boot processor) >> >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz >> >> cpu0: >> >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT >> >> cpu0: 256KB 64b/line 8-way L2 cache >> >> cpu0: TSC frequency 2891029960 Hz >> >> cpu0: apic clock running at 99MHz >> >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE >> >> cpu at mainbus0: not configured >> >> cpu at mainbus0: not configured >> >> cpu at mainbus0: not configured >> >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins >> >> acpiprt0 at acpi0: bus 0 (PCI0) >> >> acpiprt1 at acpi0: bus -1 (P0P1) >> >> acpiprt2 at acpi0: bus 1 (RP01) >> >> acpiprt3 at acpi0: bus 2 (RP02) >> >> acpiprt4 at acpi0: bus -1 (RP05) >> >> acpiprt5 at acpi0: bus 11 (RP06) >> >> acpiprt6 at acpi0: bus -1 (RP07) >> >> acpiprt7 at acpi0: bus -1 (RP08) >> >> acpiprt8 at acpi0: bus -1 (PEG0) >> >> acpiprt9 at acpi0: bus -1 (PEG1) >> >> acpiprt10 at acpi0: bus -1 (PEG2) >> >> acpiprt11 at acpi0: bus -1 (PEG3) >> >> acpiprt12 at acpi0: bus 3 (RP03) >> >> acpiprt13 at acpi0: bus 7 (RP04) >> >> acpiec0 at acpi0 >> >> acpicpu at acpi0 not configured >> >> acpitz at acpi0 not configured >> >> "INT3F0D" at acpi0 not configured >> >> "DLLK0533" at acpi0 not configured >> >> "DLL0533" at acpi0 not configured >> >> "PNP0401" at acpi0 not configured >> >> "SMO8810" at acpi0 not configured >> >> "*pnp0c14" at acpi0 not configured >> >> "PNP0C0D" at acpi0 not configured >> >> "PNP0C0C" at acpi0 not configured >> >> "PNP0C0E" at acpi0 not configured >> >> "ACPI0003" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "PNP0C0A" at acpi0 not configured >> >> "DELLABCE" at acpi0 not configured >> >> "PNP0C31" at acpi0 not configured >> >> pci0 at mainbus0 bus 0 >> >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 >> >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 >> >> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) >> >> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi >> >> usb0 at xhci0: USB revision 3.0 >> >> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev >> >> 3.00/1.00 addr 1 >> >> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured >> >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address >> >> b8:ca:3a:d8:5f:2e >> >> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 >> >> int >> >> 16 >> >> usb1 at ehci0: USB revision 2.0 >> >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev >> >> 2.00/1.00 addr 1 >> >> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not >> >> configured >> >> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi >> >> pci1 at ppb0 bus 1 >> >> ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi >> >> pci2 at ppb1 bus 2 >> >> iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev >> >> 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 >> >> ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi >> >> pci3 at ppb2 bus 3 >> >> ppb3
Re: Hard disk controller not recognized
Hi Xianwen, I guess this is one of "you're-on-your-own" cases, the BIOS being locked by IT I'm even surprised you're allowed to install a different OS on the machine. For starters I'd speak directly with them and check what are you allowed or not to do with the machine. /mestre On Monday, 12 February 2018, Xianwen Chen wrote: > Dear Mike, > > From the output of dmesg, I guess so. The BIOS is locked by IT > administrators. Is there some way that I can use OpenBSD while the > controller is set to RAID mode? > > Sincerely, > Xianwen > > On 2/12/18, Mike Larkin wrote: > > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: > >> Dear OpenBSD users, > >> > >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The > >> installation was done by taking out the hard drive and hook it through > >> a USB reader to another machine. > >> > >> I boot the hard drive through Legacy Boot menu. The boot process stops > >> with > >> root device: > >> > >> It is possible to boot through bsd.rd. However, the hard drive is not > >> recognized there. > >> > >> Here is the dmesg from bsd.rd: > >> > >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 > >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > >> real mem = 17064423424 (16273MB) > >> avail mem = 16543502336 (15777MB) > >> mainbus0 at root > >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) > >> bios0: vendor Dell Inc. version "A16" date 01/18/2016 > >> bios0: Dell Inc. Latitude E6330 > >> acpi0 at bios0: rev 2 > >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR > >> ASF! SSDT SLIC BGRT > >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > >> cpu0 at mainbus0: apid 0 (boot processor) > >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz > >> cpu0: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT > >> cpu0: 256KB 64b/line 8-way L2 cache > >> cpu0: TSC frequency 2891029960 Hz > >> cpu0: apic clock running at 99MHz > >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE > >> cpu at mainbus0: not configured > >> cpu at mainbus0: not configured > >> cpu at mainbus0: not configured > >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > >> acpiprt0 at acpi0: bus 0 (PCI0) > >> acpiprt1 at acpi0: bus -1 (P0P1) > >> acpiprt2 at acpi0: bus 1 (RP01) > >> acpiprt3 at acpi0: bus 2 (RP02) > >> acpiprt4 at acpi0: bus -1 (RP05) > >> acpiprt5 at acpi0: bus 11 (RP06) > >> acpiprt6 at acpi0: bus -1 (RP07) > >> acpiprt7 at acpi0: bus -1 (RP08) > >> acpiprt8 at acpi0: bus -1 (PEG0) > >> acpiprt9 at acpi0: bus -1 (PEG1) > >> acpiprt10 at acpi0: bus -1 (PEG2) > >> acpiprt11 at acpi0: bus -1 (PEG3) > >> acpiprt12 at acpi0: bus 3 (RP03) > >> acpiprt13 at acpi0: bus 7 (RP04) > >> acpiec0 at acpi0 > >> acpicpu at acpi0 not configured > >> acpitz at acpi0 not configured > >> "INT3F0D" at acpi0 not configured > >> "DLLK0533" at acpi0 not configured > >> "DLL0533" at acpi0 not configured > >> "PNP0401" at acpi0 not configured > >> "SMO8810" at acpi0 not configured > >> "*pnp0c14" at acpi0 not configured > >> "PNP0C0D" at acpi0 not configured > >> "PNP0C0C" at acpi0 not configured > >> "PNP0C0E" at acpi0 not configured > >> "ACPI0003" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "DELLABCE" at acpi0 not configured > >> "PNP0C31" at acpi0 not configured > >> pci0 at mainbus0 bus 0 > >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 > >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 > >> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) > >> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi > >> usb0 at xhci0: USB revision 3.0 > >> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev > >> 3.00/1.00 addr 1 > >> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured > >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address > >> b8:ca:3a:d8:5f:2e > >> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int > >> 16 > >> usb1 at ehci0: USB revision 2.0 > >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev > >> 2.00/1.00 addr 1 > >> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not > >> configured > >> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci1 at ppb0 bus 1 > >> ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci2 at ppb1 bus 2 > >> iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev > >> 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 > >> ppb2 at pci0 dev 28 function 2 "Intel
Re: Hard disk controller not recognized
On Mon, Feb 12, 2018 at 05:25:57PM +, Xianwen Chen wrote: > Dear Mike, > > >From the output of dmesg, I guess so. The BIOS is locked by IT > administrators. Is there some way that I can use OpenBSD while the > controller is set to RAID mode? > > Sincerely, > Xianwen > not that I know of > On 2/12/18, Mike Larkin wrote: > > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: > >> Dear OpenBSD users, > >> > >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The > >> installation was done by taking out the hard drive and hook it through > >> a USB reader to another machine. > >> > >> I boot the hard drive through Legacy Boot menu. The boot process stops > >> with > >> root device: > >> > >> It is possible to boot through bsd.rd. However, the hard drive is not > >> recognized there. > >> > >> Here is the dmesg from bsd.rd: > >> > >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 > >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > >> real mem = 17064423424 (16273MB) > >> avail mem = 16543502336 (15777MB) > >> mainbus0 at root > >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) > >> bios0: vendor Dell Inc. version "A16" date 01/18/2016 > >> bios0: Dell Inc. Latitude E6330 > >> acpi0 at bios0: rev 2 > >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR > >> ASF! SSDT SLIC BGRT > >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > >> cpu0 at mainbus0: apid 0 (boot processor) > >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz > >> cpu0: > >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT > >> cpu0: 256KB 64b/line 8-way L2 cache > >> cpu0: TSC frequency 2891029960 Hz > >> cpu0: apic clock running at 99MHz > >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE > >> cpu at mainbus0: not configured > >> cpu at mainbus0: not configured > >> cpu at mainbus0: not configured > >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > >> acpiprt0 at acpi0: bus 0 (PCI0) > >> acpiprt1 at acpi0: bus -1 (P0P1) > >> acpiprt2 at acpi0: bus 1 (RP01) > >> acpiprt3 at acpi0: bus 2 (RP02) > >> acpiprt4 at acpi0: bus -1 (RP05) > >> acpiprt5 at acpi0: bus 11 (RP06) > >> acpiprt6 at acpi0: bus -1 (RP07) > >> acpiprt7 at acpi0: bus -1 (RP08) > >> acpiprt8 at acpi0: bus -1 (PEG0) > >> acpiprt9 at acpi0: bus -1 (PEG1) > >> acpiprt10 at acpi0: bus -1 (PEG2) > >> acpiprt11 at acpi0: bus -1 (PEG3) > >> acpiprt12 at acpi0: bus 3 (RP03) > >> acpiprt13 at acpi0: bus 7 (RP04) > >> acpiec0 at acpi0 > >> acpicpu at acpi0 not configured > >> acpitz at acpi0 not configured > >> "INT3F0D" at acpi0 not configured > >> "DLLK0533" at acpi0 not configured > >> "DLL0533" at acpi0 not configured > >> "PNP0401" at acpi0 not configured > >> "SMO8810" at acpi0 not configured > >> "*pnp0c14" at acpi0 not configured > >> "PNP0C0D" at acpi0 not configured > >> "PNP0C0C" at acpi0 not configured > >> "PNP0C0E" at acpi0 not configured > >> "ACPI0003" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "PNP0C0A" at acpi0 not configured > >> "DELLABCE" at acpi0 not configured > >> "PNP0C31" at acpi0 not configured > >> pci0 at mainbus0 bus 0 > >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 > >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 > >> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) > >> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi > >> usb0 at xhci0: USB revision 3.0 > >> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev > >> 3.00/1.00 addr 1 > >> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured > >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address > >> b8:ca:3a:d8:5f:2e > >> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int > >> 16 > >> usb1 at ehci0: USB revision 2.0 > >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev > >> 2.00/1.00 addr 1 > >> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not > >> configured > >> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci1 at ppb0 bus 1 > >> ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci2 at ppb1 bus 2 > >> iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev > >> 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 > >> ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci3 at ppb2 bus 3 > >> ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci4 at ppb3 bus 7 > >> ppb4 at pci0 dev 28 function 5 "Intel 7 Series PCIE" rev 0xc4: msi > >> pci5 at ppb4 bus 11 > >>
Re: Hard disk controller not recognized
Dear Mike, >From the output of dmesg, I guess so. The BIOS is locked by IT administrators. Is there some way that I can use OpenBSD while the controller is set to RAID mode? Sincerely, Xianwen On 2/12/18, Mike Larkin wrote: > On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: >> Dear OpenBSD users, >> >> I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The >> installation was done by taking out the hard drive and hook it through >> a USB reader to another machine. >> >> I boot the hard drive through Legacy Boot menu. The boot process stops >> with >> root device: >> >> It is possible to boot through bsd.rd. However, the hard drive is not >> recognized there. >> >> Here is the dmesg from bsd.rd: >> >> OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 >> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD >> real mem = 17064423424 (16273MB) >> avail mem = 16543502336 (15777MB) >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) >> bios0: vendor Dell Inc. version "A16" date 01/18/2016 >> bios0: Dell Inc. Latitude E6330 >> acpi0 at bios0: rev 2 >> acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR >> ASF! SSDT SLIC BGRT >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> cpu0 at mainbus0: apid 0 (boot processor) >> cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz >> cpu0: >> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT >> cpu0: 256KB 64b/line 8-way L2 cache >> cpu0: TSC frequency 2891029960 Hz >> cpu0: apic clock running at 99MHz >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE >> cpu at mainbus0: not configured >> cpu at mainbus0: not configured >> cpu at mainbus0: not configured >> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins >> acpiprt0 at acpi0: bus 0 (PCI0) >> acpiprt1 at acpi0: bus -1 (P0P1) >> acpiprt2 at acpi0: bus 1 (RP01) >> acpiprt3 at acpi0: bus 2 (RP02) >> acpiprt4 at acpi0: bus -1 (RP05) >> acpiprt5 at acpi0: bus 11 (RP06) >> acpiprt6 at acpi0: bus -1 (RP07) >> acpiprt7 at acpi0: bus -1 (RP08) >> acpiprt8 at acpi0: bus -1 (PEG0) >> acpiprt9 at acpi0: bus -1 (PEG1) >> acpiprt10 at acpi0: bus -1 (PEG2) >> acpiprt11 at acpi0: bus -1 (PEG3) >> acpiprt12 at acpi0: bus 3 (RP03) >> acpiprt13 at acpi0: bus 7 (RP04) >> acpiec0 at acpi0 >> acpicpu at acpi0 not configured >> acpitz at acpi0 not configured >> "INT3F0D" at acpi0 not configured >> "DLLK0533" at acpi0 not configured >> "DLL0533" at acpi0 not configured >> "PNP0401" at acpi0 not configured >> "SMO8810" at acpi0 not configured >> "*pnp0c14" at acpi0 not configured >> "PNP0C0D" at acpi0 not configured >> "PNP0C0C" at acpi0 not configured >> "PNP0C0E" at acpi0 not configured >> "ACPI0003" at acpi0 not configured >> "PNP0C0A" at acpi0 not configured >> "PNP0C0A" at acpi0 not configured >> "PNP0C0A" at acpi0 not configured >> "DELLABCE" at acpi0 not configured >> "PNP0C31" at acpi0 not configured >> pci0 at mainbus0 bus 0 >> pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 >> vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 >> wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) >> xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi >> usb0 at xhci0: USB revision 3.0 >> uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev >> 3.00/1.00 addr 1 >> "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured >> em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address >> b8:ca:3a:d8:5f:2e >> ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int >> 16 >> usb1 at ehci0: USB revision 2.0 >> uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev >> 2.00/1.00 addr 1 >> "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not >> configured >> ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi >> pci1 at ppb0 bus 1 >> ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi >> pci2 at ppb1 bus 2 >> iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev >> 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 >> ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi >> pci3 at ppb2 bus 3 >> ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi >> pci4 at ppb3 bus 7 >> ppb4 at pci0 dev 28 function 5 "Intel 7 Series PCIE" rev 0xc4: msi >> pci5 at ppb4 bus 11 >> sdhc0 at pci5 dev 0 function 0 vendor "O2 Micro", unknown product >> 0x8221 rev 0x05: apic 2 int 17 >> sdhc0: SDHC 2.0, 50 MHz base clock >> sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma >> ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int >> 21 >> usb2 at ehci1: USB revi
Re: Hard disk controller not recognized
On 02/12/18 18:07, Xianwen Chen wrote: > Dear OpenBSD users, > > I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The > installation was done by taking out the hard drive and hook it through > a USB reader to another machine. > > I boot the hard drive through Legacy Boot menu. The boot process stops with > root device: > > It is possible to boot through bsd.rd. However, the hard drive is not > recognized there. I'm guessing that for some reason or the other the controller is set to 'hardware raid' mode (which OpenBSD does not support) instead of a more useful SATA mode: > pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA, > channel 0 wired to native-PCI, channel 1 wired to native-PCI > pciide0: using apic 2 int 19 for native-PCI interrupt See if the BIOS offers a choice of modes for the controller, hopefully there is a SATA option. - Peter -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: Hard disk controller not recognized
On Mon, Feb 12, 2018 at 05:07:15PM +, Xianwen Chen wrote: > Dear OpenBSD users, > > I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The > installation was done by taking out the hard drive and hook it through > a USB reader to another machine. > > I boot the hard drive through Legacy Boot menu. The boot process stops with > root device: > > It is possible to boot through bsd.rd. However, the hard drive is not > recognized there. > > Here is the dmesg from bsd.rd: > > OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 17064423424 (16273MB) > avail mem = 16543502336 (15777MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) > bios0: vendor Dell Inc. version "A16" date 01/18/2016 > bios0: Dell Inc. Latitude E6330 > acpi0 at bios0: rev 2 > acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR > ASF! SSDT SLIC BGRT > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2891029960 Hz > cpu0: apic clock running at 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE > cpu at mainbus0: not configured > cpu at mainbus0: not configured > cpu at mainbus0: not configured > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (P0P1) > acpiprt2 at acpi0: bus 1 (RP01) > acpiprt3 at acpi0: bus 2 (RP02) > acpiprt4 at acpi0: bus -1 (RP05) > acpiprt5 at acpi0: bus 11 (RP06) > acpiprt6 at acpi0: bus -1 (RP07) > acpiprt7 at acpi0: bus -1 (RP08) > acpiprt8 at acpi0: bus -1 (PEG0) > acpiprt9 at acpi0: bus -1 (PEG1) > acpiprt10 at acpi0: bus -1 (PEG2) > acpiprt11 at acpi0: bus -1 (PEG3) > acpiprt12 at acpi0: bus 3 (RP03) > acpiprt13 at acpi0: bus 7 (RP04) > acpiec0 at acpi0 > acpicpu at acpi0 not configured > acpitz at acpi0 not configured > "INT3F0D" at acpi0 not configured > "DLLK0533" at acpi0 not configured > "DLL0533" at acpi0 not configured > "PNP0401" at acpi0 not configured > "SMO8810" at acpi0 not configured > "*pnp0c14" at acpi0 not configured > "PNP0C0D" at acpi0 not configured > "PNP0C0C" at acpi0 not configured > "PNP0C0E" at acpi0 not configured > "ACPI0003" at acpi0 not configured > "PNP0C0A" at acpi0 not configured > "PNP0C0A" at acpi0 not configured > "PNP0C0A" at acpi0 not configured > "DELLABCE" at acpi0 not configured > "PNP0C31" at acpi0 not configured > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 > vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 > wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) > xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi > usb0 at xhci0: USB revision 3.0 > uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev > 3.00/1.00 addr 1 > "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured > em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address > b8:ca:3a:d8:5f:2e > ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 > usb1 at ehci0: USB revision 2.0 > uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev > 2.00/1.00 addr 1 > "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured > ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi > pci1 at ppb0 bus 1 > ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi > pci2 at ppb1 bus 2 > iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev > 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 > ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi > pci3 at ppb2 bus 3 > ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi > pci4 at ppb3 bus 7 > ppb4 at pci0 dev 28 function 5 "Intel 7 Series PCIE" rev 0xc4: msi > pci5 at ppb4 bus 11 > sdhc0 at pci5 dev 0 function 0 vendor "O2 Micro", unknown product > 0x8221 rev 0x05: apic 2 int 17 > sdhc0: SDHC 2.0, 50 MHz base clock > sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma > ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 21 > usb2 at ehci1: USB revision 2.0 > uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev > 2.00/1.00 addr 1 > "Intel QM77 LPC" rev 0x04 at pci0 dev 31 function 0 not configured > pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA, > channel 0 wired to native-PCI, channel 1 wired to native-PCI > pciide0: using apic 2 int 19 for na
Hard disk controller not recognized
Dear OpenBSD users, I am not able to run OpenBSD 6.2 amd64 on a Dell Latitude E6330. The installation was done by taking out the hard drive and hook it through a USB reader to another machine. I boot the hard drive through Legacy Boot menu. The boot process stops with root device: It is possible to boot through bsd.rd. However, the hard drive is not recognized there. Here is the dmesg from bsd.rd: OpenBSD 6.2 (RAMDISK_CD) #132: Tue Oct 3 21:26:51 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 17064423424 (16273MB) avail mem = 16543502336 (15777MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xecad0 (98 entries) bios0: vendor Dell Inc. version "A16" date 01/18/2016 bios0: Dell Inc. Latitude E6330 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP APIC FPDT TCPA MCFG HPET SSDT SSDT SSDT DMAR ASF! SSDT SLIC BGRT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 2891.03 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2891029960 Hz cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1.2, IBE cpu at mainbus0: not configured cpu at mainbus0: not configured cpu at mainbus0: not configured ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (P0P1) acpiprt2 at acpi0: bus 1 (RP01) acpiprt3 at acpi0: bus 2 (RP02) acpiprt4 at acpi0: bus -1 (RP05) acpiprt5 at acpi0: bus 11 (RP06) acpiprt6 at acpi0: bus -1 (RP07) acpiprt7 at acpi0: bus -1 (RP08) acpiprt8 at acpi0: bus -1 (PEG0) acpiprt9 at acpi0: bus -1 (PEG1) acpiprt10 at acpi0: bus -1 (PEG2) acpiprt11 at acpi0: bus -1 (PEG3) acpiprt12 at acpi0: bus 3 (RP03) acpiprt13 at acpi0: bus 7 (RP04) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured "INT3F0D" at acpi0 not configured "DLLK0533" at acpi0 not configured "DLL0533" at acpi0 not configured "PNP0401" at acpi0 not configured "SMO8810" at acpi0 not configured "*pnp0c14" at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0C" at acpi0 not configured "PNP0C0E" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C0A" at acpi0 not configured "DELLABCE" at acpi0 not configured "PNP0C31" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 vga1 at pci0 dev 2 function 0 "Intel HD Graphics 4000" rev 0x09 wsdisplay1 at vga1 mux 1: console (80x25, vt100 emulation) xhci0 at pci0 dev 20 function 0 "Intel 7 Series xHCI" rev 0x04: msi usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration 1 interface 0 "Intel xHCI root hub" rev 3.00/1.00 addr 1 "Intel 7 Series MEI" rev 0x04 at pci0 dev 22 function 0 not configured em0 at pci0 dev 25 function 0 "Intel 82579LM" rev 0x04: msi, address b8:ca:3a:d8:5f:2e ehci0 at pci0 dev 26 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 16 usb1 at ehci0: USB revision 2.0 uhub1 at usb1 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel 7 Series HD Audio" rev 0x04 at pci0 dev 27 function 0 not configured ppb0 at pci0 dev 28 function 0 "Intel 7 Series PCIE" rev 0xc4: msi pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 2 iwn0 at pci2 dev 0 function 0 "Intel Centrino Ultimate-N 6300" rev 0x35: msi, MIMO 3T3R, MoW, address 3c:a9:f4:01:ed:24 ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 3 ppb3 at pci0 dev 28 function 3 "Intel 7 Series PCIE" rev 0xc4: msi pci4 at ppb3 bus 7 ppb4 at pci0 dev 28 function 5 "Intel 7 Series PCIE" rev 0xc4: msi pci5 at ppb4 bus 11 sdhc0 at pci5 dev 0 function 0 vendor "O2 Micro", unknown product 0x8221 rev 0x05: apic 2 int 17 sdhc0: SDHC 2.0, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed, dma ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 21 usb2 at ehci1: USB revision 2.0 uhub2 at usb2 configuration 1 interface 0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel QM77 LPC" rev 0x04 at pci0 dev 31 function 0 not configured pciide0 at pci0 dev 31 function 2 "Intel 82801HBM RAID" rev 0x04: DMA, channel 0 wired to native-PCI, channel 1 wired to native-PCI pciide0: using apic 2 int 19 for native-PCI interrupt "Intel 7 Series SMBus" rev 0x04 at pci0 dev 31 function 3 not configured isa0 at mainbus0 pckbc0 at isa0 port 0x60/5 irq 1 irq 12 pckbd0 at pckbc0 (kbd slot) wskbd0 at pckbd0: console keyboard, using wsdisplay1 uhub3 at uhub1 port 1 configuration 1 interface 0 "v
Re: signify-openbsd to crypt'ly verify install62.iso in linux
> To keep it neat, let's say both files are in /data/bsd-stuff, so we > have: > /data/bsd-stuff/install62.iso > /data/bsd-stuff/SHA256.sig where did you download the public key?
OpenBSD Memory protection mechanisms that are not enabled by default?
Hello! Besides the "S" option for malloc.conf and increasing kern.stackgap_random and removing the wxallowed mount option, what else memory-related hardening mechanism are in OpenBSD that can be turned on and it is not enabled by default? Even options would be useful if we have to re-compile the kernel, if minimal source code modification is needed. Tried to get lists/ideas from grsecurity (if there is any, that is not already used in OpenBSD), but it is hard when you are not a programmer. Many thanks.
Re: Syn flood crashed my LAN
Agreed about ubnt vs tplink vs cisco... most use either broadcom or marvel chipsets Stuart I was sugesting based on rated performance of the chipsets in the datasheets of the managed switch... as opposed to a cheap un managed one the other thing i for got to mention which was part of my advice was that the ability to check counters on each interface can indicate where the packets are being dropped are the being dropped beween switch ports or on the open bas firewall etc On 12 Feb 2018 1:59 PM, "Stuart Henderson" wrote: > On 2018-02-12, Tom Smyth wrote: > > Regards D-Link... I would recommend that you use > > a decent managed switch (based on Tech Specs as opposed > > to Branding, > > you can pick up cost effective ubnt edgeswitches or > > Tplink (fully managed Switches) which would offer linerate switching > > or if you want to have a branded switch get one second hand for best > value > > They're all use one of a couple of pretty similar switch chips anyway. > > Without doing more to figure out *how* it broke I don't think it's possible > to say that one brand is going to react better than another. > > >
Re: Syn flood crashed my LAN
On 2018-02-12, Tom Smyth wrote: > Regards D-Link... I would recommend that you use > a decent managed switch (based on Tech Specs as opposed > to Branding, > you can pick up cost effective ubnt edgeswitches or > Tplink (fully managed Switches) which would offer linerate switching > or if you want to have a branded switch get one second hand for best value They're all use one of a couple of pretty similar switch chips anyway. Without doing more to figure out *how* it broke I don't think it's possible to say that one brand is going to react better than another.
Flask app with chrooted httpd
Hi, Did anyone use httpd to serve a flask app (python)? I found this [1], but its a little outdated (python < 3) and makes me wonder about safety, because of all those dependencies copied in chroot. Any advice ? Regards -- thuban
Re: Syn flood crashed my LAN
From my seat, he learned that his configuration of PF lacks SYN flooding protection. He also learned that he needs a managed switch: cisco SF and SG series are affordable and deliver ddos protection. Sent from ProtonMail Mobile On Mon, Feb 12, 2018 at 07:22, Bruno Flueckiger wrote: > On 12.02.18 01:26, Martin Hanson wrote: > Hi, > > I have a home network that > is segmented into 3 different zones using a NIC with 4 ports sitting on an > OpenBSD firewall/dhcp server. One port is connected to the Internet (ISP > router) and each of the three others has a D-Link DGS-1005D switch connected > to each. > > So.. > > LAN1 = 192.168.1.0 > LAN2 = 192.168.2.0 > LAN3 = > 192.168.3.0 > > Learning more about networking I wanted to test a SYN flood > so I set up a couple of boxes on LAN1 and LAN3 to flood a box on LAN2. I used > "hping3" with the "S" and "flood" options. > > Running a regular ping in a > terminal I could see how the response time decreased and eventually the box > began to loose packages. > > However after a while it seemed like the entire > internal network went down. > > No box on any LAN could get an IP address > from the DHCP server on the OpenBSD box. > > I eventually rebooted the > OpenBSD box, but that didn't immediately help, and only after powering down > the switches and powering the switches on again, everything worked again. > > > I have been looking through the PF documentation to see if PF somehow blocks > SYN flooding, but I am not using synproxy on any rules. > > What could cause > such a "melt down" of the entire network because of a SYN flood to a box? > > > I suspect that the D-Link switches are pretty bad and maybe are the cause of > the problem? > > I eventually will try again to see if I can determine what's > causing the "melt down", but I want to know if anyone perhaps has experienced > similar results during some testing? > > Many thanks in advance. > > Kind > regards, > > Martin You run a denial of service attack against your home > network. As a result your network denials service. Sounds like you have > proven that syn flooding is an effective denial of service attack in your > network. Yes, your switches cannot handle the amount of traffic you putting > on them. No, your switches are not the problem. Your syn flooding of the > network is causing the problem. Cheers, Bruno -- I really hope this whole > thing works, I won't be able to test everything beforehand
Re: Why is so slow the download speed in OpenBSD?
Try different channels. See the wireless section of ifconfig(8). On Feb 12, 2018 3:02 AM, Zsolt Kantor wrote: > > I tried that, but as Edgar said it downloaded all the firmware's from the > site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. > > I want to send a bug report, but (with a big b) the question is who gonna > debug the firmware, because as I know those firmware's are non-free code, so > maybe it is not even the 'job' of the OpenBSD developers to fix the error. > > > On Monday, February 12, 2018 5:41 AM, Tom Smyth > wrote: > > > > Hi Zolt > > when your laptop is on line try > > fw_update -a > command to update firmware... you probably were not online when the > firmware update command ran (on first boot after install) > See what happens when you run that command .. > > Thanks > Tom Smyth > > On 11 February 2018 at 23:15, Zsolt Kantor wrote: > > Below I provide full information from ifconfig, route and a full dmesg. By > > the way, I think this is a BUG in the wireless firmware that I'm using > > (downloaded from the OpenBSD firmware site). I say this because I found > > this line in the dmesg output: wpi0: fatal firmware error > > > > So below are the outputs. > > > > ifconfig output: > > > > lo0: flags=8049 mtu 32768 > > index 4 priority 0 llprio 3 > > groups: lo > > inet6 ::1 prefixlen 128 > > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > > inet 127.0.0.1 netmask 0xff00 > > re0: flags=8802 mtu 1500 > > lladdr 00:1f:16:03:90:fe > > index 1 priority 0 llprio 3 > > media: Ethernet autoselect (none) > > status: no carrier > > wpi0: flags=8843 mtu 1500 > > lladdr 00:1f:3c:8d:aa:a2 > > index 2 priority 4 llprio 3 > > groups: wlan egress > > media: IEEE802.11 autoselect (DS1 mode 11g) > > status: active > > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey > displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > > enc0: flags=0<> > > index 3 priority 0 llprio 3 > > groups: enc > > status: active > > pflog0: flags=141 mtu 33136 > > index 5 priority 0 llprio 3 > > groups: pflog > > > > > > > > route -n show output: > > > > Routing tables > > > > Internet: > > Destination Gateway Flags Refs Use Mtu Prio > > Iface > > default 192.168.0.1 UGS 3 450 - 12 wpi0 > > 224/4 127.0.0.1 URS 0 12 32768 8 lo0 > > 127/8 127.0.0.1 UGRS 0 0 32768 8 lo0 > > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > > 192.168.0/24 192.168.0.101 UCn 1 0 - 8 wpi0 > > 192.168.0.1 70:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > > 192.168.0.255 192.168.0.101 UHb 0 0 - 1 wpi0 > > > > Internet6: > > Destination Gateway Flags > > Refs Use Mtu Prio Iface > > ::/96 ::1 UGRS > > 0 0 32768 8 lo0 > > ::/104 ::1 UGRS > > 0 0 32768 8 lo0 > > ::1 ::1 UHhl > > 14 34 32768 1 lo0 > > ::127.0.0.0/104 ::1 UGRS > > 0 0 32768 8 lo0 > > ::224.0.0.0/100 ::1 UGRS > > 0 0 32768 8 lo0 > > ::255.0.0.0/104 ::1 UGRS > > 0 0 32768 8 lo0 > > :::0.0.0.0/96 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:7f00::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:e000::/20 ::1 UGRS > > 0 0 32768 8 lo0 > > 2002:ff00::/24 ::1 UGRS > > 0 0 32768 8 lo0 > > fe80::/10 ::1 UGRS > > 0 0 32768 8 lo0 > > fec0::/10 ::1 UGRS > > 0 0 32768 8 lo0 > > fe80::1%lo0 fe80::1%lo0 UHl > > 0 0 32768 1 lo0 > > ff01::/16 ::1 UGRS > > 0 0 32768 8 lo0 > > ff01::%lo0/32 ::1 Um > > 0 1 32768 4 lo0 > > ff02::/16 ::1 UGRS > > 0
Re: tor inside vmm, horribly slow?!
On Mon, Feb 12, 2018 at 12:38:00AM -0800, Mike Larkin wrote: > > > > it's horrible slow, just doing 'tor-resolve $dnsname' takes > > > > sometimes ages. > > > > [...] > [...] > > What did the guest pick for timecounter? (sysctl kern.timecounter.hardware) > > Your hardware is nearly a decade old. I wouldn't be surprised if vmm > picked some ancient timecounter hardware. For the example below, my guest > chose 'tsc' (I have a 2013-era Ivy Bridge CPU). All my hosts/VMs are > -current. And we know if your hardware is shit, we do the best we can but > no promises as to how precise time is going to be. With tsc timecounter, > my VMs that have been up for weeks have drifted maybe a second or two from > the host. > > [...] > > In other words, I don't see anything odd here. The vm appears to actually > be running faster than the host. I'm not concerned about the 2-3 second > difference on the first resolve. I bet if I ran it a hundred times I'd see > things pretty much the same. Mike, thank you for your time. The VM picked 'tsc' as timecounter. Putting CC Pascal, Tor port maintainer, as I am suspicious that this slowness is related to what tor itself is doing in that time. Pascal, any idea what could cause slowness of tor when using onion service inside VMM? Info below (plus history https://marc.info/?l=openbsd-misc&m=151839235419514&w=2): Feb 12 10:30:25 onion Tor[96278]: connection_connect_sockaddr: Connection to socket established (sock 4). Feb 12 10:32:55 onion Tor[96278]: connection_edge_reached_eof: conn (fd 4) reached eof. Closing. Feb 12 10:32:55 onion Tor[96278]: Your system clock just jumped 151 seconds forward; assuming established circuits no longer work. ^^^ 2 mins gap? Tor tests, if this is general issue or not. - scenario 1 * loop date + tor-resolve $dnsname + sleep 1 * torsocks curl -s -I http://www.openbsd.org ^^ this works ok - scenario 2 make tor to have local onion service with httpd enabled * install -d -o _tor -g _tor -m 700 /var/tor/onion * modify /etc/tor/torrc: Log debug syslog HiddenServiceDir /var/tor/onion/ HiddenServicePort 80 127.0.0.1:80 * enable httpd & tor * loop date + tor-resolve $dnsname + sleep 1 * get your .onion service address cat /var/tor/onion/hostname * access your .onion service from other (tor)browser ... Feb 12 10:30:24.519 [warn] Got SOCKS5 status response '4': host is unreachable Mon Feb 12 10:30:26 CET 2018 129.128.5.194 Mon Feb 12 10:32:58 CET 2018 129.128.5.194 Mon Feb 12 10:33:00 CET 2018 ... ^^ tor-resolve $dnsnanme gets slow downed in a while, 2 mins gap Feb 12 10:30:24 onion Tor[96278]: rend_service_rendezvous_has_opened: Done building circuit 2327426966 to rendezvous with cookie D92E6387 for service Feb 12 10:30:24 onion Tor[96278]: internal circ (length 4): $0FBE018DADAB416DE17A10C5D4AD3EBF0E243561(open) $BF50E09EED25B82861CF95E1AAA42DCFEF53E5D1(open) $F80FDE27EFCB3F6A7B4E2CC517133DBFFA78BA2D(open) $CCF0E904BAD135F6B2180BD89D19E487F83786A5(open) Feb 12 10:30:24 onion Tor[96278]: connection_handle_listener_read: New SOCKS connection opened from 127.0.0.1. Feb 12 10:30:24 onion Tor[96278]: rep_hist_note_used_port: New port prediction added. Will continue predictive circ building for 1967 more seconds. Feb 12 10:30:24 onion Tor[96278]: connection_edge_process_inbuf: data from edge while in 'waiting for circuit' state. Leaving it on buffer. Feb 12 10:30:24 onion Tor[96278]: exit circ (length 3): $0FBE018DADAB416DE17A10C5D4AD3EBF0E243561(open) $594252BFEE13625AC120F50F3015CB3C1DA55690(open) $1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA(open) Feb 12 10:30:24 onion Tor[96278]: pathbias_count_use_attempt: Used circuit 2 is already in path state use succeeded. Circuit is a General-purpose client currently open. Feb 12 10:30:24 onion Tor[96278]: link_apconn_to_circ: Looks like completed circuit to [scrubbed] does allow optimistic data for connection to [scrubbed] Feb 12 10:30:24 onion Tor[96278]: connection_ap_handshake_send_resolve: Address sent for resolve, ap socket 4, n_circ_id 2260876578 Feb 12 10:30:25 onion Tor[96278]: connection_connect_sockaddr: Connection to socket established (sock 4). Feb 12 10:32:55 onion Tor[96278]: connection_edge_reached_eof: conn (fd 4) reached eof. Closing. Feb 12 10:32:55 onion Tor[96278]: Your system clock just jumped 151 seconds forward; assuming established circuits no longer work. ^^ 2 mins gap So just slow HW issue? Jiri
Re: Why is so slow the download speed in OpenBSD?
I tried that, but as Edgar said it downloaded all the firmware's from the site, even those I'm not needing, eg. radeondrm, but I'm using inteldrm. I want to send a bug report, but (with a big b) the question is who gonna debug the firmware, because as I know those firmware's are non-free code, so maybe it is not even the 'job' of the OpenBSD developers to fix the error. On Monday, February 12, 2018 5:41 AM, Tom Smyth wrote: Hi Zolt when your laptop is on line try fw_update -a command to update firmware... you probably were not online when the firmware update command ran (on first boot after install) See what happens when you run that command .. Thanks Tom Smyth On 11 February 2018 at 23:15, Zsolt Kantor wrote: > Below I provide full information from ifconfig, route and a full dmesg. By > the way, I think this is a BUG in the wireless firmware that I'm using > (downloaded from the OpenBSD firmware site). I say this because I found this > line in the dmesg output: wpi0: fatal firmware error > > So below are the outputs. > > ifconfig output: > > lo0: flags=8049 mtu 32768 > index 4 priority 0 llprio 3 > groups: lo > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 > inet 127.0.0.1 netmask 0xff00 > re0: flags=8802 mtu 1500 > lladdr 00:1f:16:03:90:fe > index 1 priority 0 llprio 3 > media: Ethernet autoselect (none) > status: no carrier > wpi0: flags=8843 mtu 1500 > lladdr 00:1f:3c:8d:aa:a2 > index 2 priority 4 llprio 3 > groups: wlan egress > media: IEEE802.11 autoselect (DS1 mode 11g) > status: active > ieee80211: nwid zsolt chan 11 bssid 70:4f:57:2c:b1:04 -42dBm wpakey displayed> wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp > inet 192.168.0.101 netmask 0xff00 broadcast 192.168.0.255 > enc0: flags=0<> > index 3 priority 0 llprio 3 > groups: enc > status: active > pflog0: flags=141 mtu 33136 > index 5 priority 0 llprio 3 > groups: pflog > > > > route -n show output: > > Routing tables > > Internet: > DestinationGatewayFlags Refs Use Mtu Prio Iface > default192.168.0.1UGS3 450 -12 wpi0 > 224/4 127.0.0.1 URS0 12 32768 8 lo0 > 127/8 127.0.0.1 UGRS 00 32768 8 lo0 > 127.0.0.1 127.0.0.1 UHhl 1 3101 32768 1 lo0 > 192.168.0/24 192.168.0.101 UCn10 - 8 wpi0 > 192.168.0.170:4f:57:2c:b1:04 UHLch 2 267 - 7 wpi0 > 192.168.0.101 00:1f:3c:8d:aa:a2 UHLl 0 831 - 1 wpi0 > 192.168.0.255 192.168.0.101 UHb00 - 1 wpi0 > > Internet6: > DestinationGatewayFlags > Refs Use Mtu Prio Iface > ::/96 ::1UGRS > 00 32768 8 lo0 > ::/104 ::1UGRS > 00 32768 8 lo0 > ::1::1UHhl > 14 34 32768 1 lo0 > ::127.0.0.0/104::1UGRS > 00 32768 8 lo0 > ::224.0.0.0/100::1UGRS > 00 32768 8 lo0 > ::255.0.0.0/104::1UGRS > 00 32768 8 lo0 > :::0.0.0.0/96 ::1UGRS > 00 32768 8 lo0 > 2002::/24 ::1UGRS > 00 32768 8 lo0 > 2002:7f00::/24 ::1UGRS > 00 32768 8 lo0 > 2002:e000::/20 ::1UGRS > 00 32768 8 lo0 > 2002:ff00::/24 ::1UGRS > 00 32768 8 lo0 > fe80::/10 ::1UGRS > 00 32768 8 lo0 > fec0::/10 ::1UGRS > 00 32768 8 lo0 > fe80::1%lo0fe80::1%lo0UHl > 00 32768 1 lo0 > ff01::/16 ::1UGRS > 00 32768 8 lo0 > ff01::%lo0/32 ::1Um > 01 32768 4 lo0 > ff02::/16 ::1UGRS > 00 32768 8 lo0 > ff02::%lo0/32 ::1Um > 01 32768 4 lo0 > > > > dmesg output: > OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb 2 23:02:19 CET 2018 > r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2121072640 (2022MB) > avail mem =
Re: tor inside vmm, horribly slow?!
On Mon, Feb 12, 2018 at 03:07:31AM -0500, Jiri B wrote:
> On Sun, Feb 11, 2018 at 04:47:02PM -0800, Mike Larkin wrote:
> > > has anybody tried to run tor inside vmm guest?
> > >
> > > it's horrible slow, just doing 'tor-resolve $dnsname' takes
> > > sometimes ages.
> > > [...]
> > > is it related to vmm ssl issue reported in the past?
> >
> > no
> >
> > > [...]
> > This report sucks. no dmesg, no information about what the VM config is,
> > what
> > version the guest is, what version the host is, etc.
>
> Big apologize, I thought it could be something known.
> Info below. Thank you for help.
>
> Jiri
>
What did the guest pick for timecounter? (sysctl kern.timecounter.hardware)
Your hardware is nearly a decade old. I wouldn't be surprised if vmm
picked some ancient timecounter hardware. For the example below, my guest
chose 'tsc' (I have a 2013-era Ivy Bridge CPU). All my hosts/VMs are
-current. And we know if your hardware is shit, we do the best we can but
no promises as to how precise time is going to be. With tsc timecounter,
my VMs that have been up for weeks have drifted maybe a second or two from
the host.
In any case, in my amd64 VM, the first time I do your command I see this:
time tor-resolve www.openbsd.org
129.128.5.194
0m20.30s real 0m00.00s user 0m00.00s system
And the second time:
time tor-resolve www.openbsd.org
129.128.5.194
0m00.20s real 0m00.00s user 0m00.00s system
Now, on the host, the first time:
time tor-resolve www.openbsd.org
129.128.5.194
0m17.54s real 0m00.00s user 0m00.01s system
And the second time on the host:
time tor-resolve www.openbsd.org
129.128.5.194
0m00.54s real 0m00.00s user 0m00.02s system
In other words, I don't see anything odd here. The vm appears to actually
be running faster than the host. I'm not concerned about the 2-3 second
difference on the first resolve. I bet if I ran it a hundred times I'd see
things pretty much the same.
-ml
> Another try inside vmm guest:
> ~
>
> # time tor-resolve www.openbsd.org
> 129.128.5.194
> 0m00.14s real 0m00.00s user 0m00.00s system
> # time tor-resolve www.openbsd.org
> 129.128.5.194
> 0m52.96s real 0m00.00s user 0m00.00s system
>
> # tail /var/log/daemon
> Feb 12 08:19:59 onion Tor[21861]: Bootstrapped 100%: Done
> Feb 12 08:20:04 onion ntpd[51629]: adjusting local clock by 0.384653s
> Feb 12 08:23:01 onion ntpd[51629]: adjusting local clock by -0.063873s
> Feb 12 08:42:58 onion Tor[21861]: Your system clock just jumped 150 seconds
> forward; assuming established circuits no longer work.
> Feb 12 08:42:59 onion Tor[21861]: Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Feb 12 08:42:59 onion Tor[21861]: Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Feb 12 08:45:55 onion Tor[21861]: Your system clock just jumped 150 seconds
> forward; assuming established circuits no longer work.
> Feb 12 08:45:57 onion Tor[21861]: Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Feb 12 08:45:57 onion Tor[21861]: Tor has successfully opened a circuit.
> Looks like client functionality is working.
> Feb 12 08:47:05 onion ntpd[51629]: adjusting clock frequency by -7.934969 to
> -23.542969ppm
>
> VMM:
>
>
> (Originally I forgot 'group internal' in vm.conf, so I put tap1 into group
> 'internal' manually via ifconfig.)
>
> vm "onion" {
> disable
> owner jirib
> memory 512M
> boot $kernel
> local interface tap
> disk $onion_osdisk
> disk $onion_datadisk
> }
>
> Networking on host:
> ~~~
>
> # route -nv show -inet | grep ^default
> default176.74.xxx.xxx UGS538658 - 8 em0
> "internet4"
>
> # sysctl net.inet.ip.forwarding
>
>
> net.inet.ip.forwarding=1
>
> em0: flags=8843 mtu 1500
> lladdr 90:e2:ba:xx:xx:xx
> index 1 priority 0 llprio 3
> groups: public egress
> media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
> status: active
> inet 176.74.xxx netmask 0xffe0 broadcast 176.74.xxx
>
> tap1: flags=8843 mtu 1500
> lladdr fe:e1:ba:d2:f7:28
> description: vm2-if0-onion
> index 17 priority 0 llprio 3
> groups: tap internal
> status: active
> inet 100.64.2.2 netmask 0xfffe
>
> PF on host (uses 'group internal'):
> ~~~
>
> # pfctl -sr | egrep '(on egress.*nat-to|on internal.*all)'
> pass out quick on egress from any to route "internet4" flags S/SA nat-to
> (egress) round-robin
> pass in quick on internal all flags S/SA
>
> Storage on host:
>
>
Re: tor inside vmm, horribly slow?!
On Sun, Feb 11, 2018 at 04:47:02PM -0800, Mike Larkin wrote:
> > has anybody tried to run tor inside vmm guest?
> >
> > it's horrible slow, just doing 'tor-resolve $dnsname' takes
> > sometimes ages.
> > [...]
> > is it related to vmm ssl issue reported in the past?
>
> no
>
> > [...]
> This report sucks. no dmesg, no information about what the VM config is, what
> version the guest is, what version the host is, etc.
Big apologize, I thought it could be something known.
Info below. Thank you for help.
Jiri
Another try inside vmm guest:
~
# time tor-resolve www.openbsd.org
129.128.5.194
0m00.14s real 0m00.00s user 0m00.00s system
# time tor-resolve www.openbsd.org
129.128.5.194
0m52.96s real 0m00.00s user 0m00.00s system
# tail /var/log/daemon
Feb 12 08:19:59 onion Tor[21861]: Bootstrapped 100%: Done
Feb 12 08:20:04 onion ntpd[51629]: adjusting local clock by 0.384653s
Feb 12 08:23:01 onion ntpd[51629]: adjusting local clock by -0.063873s
Feb 12 08:42:58 onion Tor[21861]: Your system clock just jumped 150 seconds
forward; assuming established circuits no longer work.
Feb 12 08:42:59 onion Tor[21861]: Tor has successfully opened a circuit. Looks
like client functionality is working.
Feb 12 08:42:59 onion Tor[21861]: Tor has successfully opened a circuit. Looks
like client functionality is working.
Feb 12 08:45:55 onion Tor[21861]: Your system clock just jumped 150 seconds
forward; assuming established circuits no longer work.
Feb 12 08:45:57 onion Tor[21861]: Tor has successfully opened a circuit. Looks
like client functionality is working.
Feb 12 08:45:57 onion Tor[21861]: Tor has successfully opened a circuit. Looks
like client functionality is working.
Feb 12 08:47:05 onion ntpd[51629]: adjusting clock frequency by -7.934969 to
-23.542969ppm
VMM:
(Originally I forgot 'group internal' in vm.conf, so I put tap1 into group
'internal' manually via ifconfig.)
vm "onion" {
disable
owner jirib
memory 512M
boot $kernel
local interface tap
disk $onion_osdisk
disk $onion_datadisk
}
Networking on host:
~~~
# route -nv show -inet | grep ^default
default176.74.xxx.xxx UGS538658 - 8 em0
"internet4"
# sysctl net.inet.ip.forwarding
net.inet.ip.forwarding=1
em0: flags=8843 mtu 1500
lladdr 90:e2:ba:xx:xx:xx
index 1 priority 0 llprio 3
groups: public egress
media: Ethernet autoselect (100baseTX full-duplex,rxpause,txpause)
status: active
inet 176.74.xxx netmask 0xffe0 broadcast 176.74.xxx
tap1: flags=8843 mtu 1500
lladdr fe:e1:ba:d2:f7:28
description: vm2-if0-onion
index 17 priority 0 llprio 3
groups: tap internal
status: active
inet 100.64.2.2 netmask 0xfffe
PF on host (uses 'group internal'):
~~~
# pfctl -sr | egrep '(on egress.*nat-to|on internal.*all)'
pass out quick on egress from any to route "internet4" flags S/SA nat-to
(egress) round-robin
pass in quick on internal all flags S/SA
Storage on host:
'disk's are located on softraid RAID1 array:
1# bioctl sd8
Volume Status Size Device
softraid0 2 Online 536871947776 sd8 RAID1
0 Online 536871947776 2:0.0 noencl
1 Online 536871947776 2:1.0 noencl
# dmesg | grep ^sd[23]
sd2 at scsibus1 targ 2 lun 0: SCSI3 0/direct
fixed naa.5000c5009387182f
sd2: 953869MB, 512 bytes/sector, 1953525168 sectors
sd3 at scsibus1 targ 3 lun 0: SCSI3 0/direct
fixed naa.5000c500939203ed
sd3: 953869MB, 512 bytes/sector, 1953525168 sectors
dmesg on host:
~~
with disabled lm driver because of issue with bad fan RPM.
OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 10 00:05:49 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8564375552 (8167MB)
avail mem = 8297807872 (7913MB)
enter_shared_special_pages: entered idt page va 0x8001 pa 0x1d5a000
enter_shared_special_pages: entered kutext page va 0x81831000 pa
0x1831000
enter_shared_special_pages: entered kutext page va 0x81832000 pa
0x1832000
enter_shared_special_pages: entered kutext page va 0x81833000 pa
0x1833000
enter_shared_special_pages: entered kudata page va 0x81ac8000 pa
0x1ac8000
cpu_enter_pages: entered tss+gdt page at va 0x81ab4000 pa 0x1ab4000
cpu_enter_pages: entered t.stack page at va 0x81ab5000 pa 0x1ab5000
cpu_ente
