Re: Unable to boot encrypted drive
On Friday 06 January 2017 15:23:32 Timo Myyrä wrote: > Here's the output of installboot on running system: > $ doas installboot -v sd1 > Using / as root > installing bootstrap on /dev/rsd1c > using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot > sd1: softraid volume with 1 disk(s) > sd1: installing boot loader on softraid volume > /usr/mdec/boot is 6 blocks x 16384 bytes > sd0a: installing boot blocks on /dev/rsd0c, part offset 1104 > master boot record (MBR) at sector 0 > partition 0: type 0xEF offset 64 size 960 > partition 3: type 0xA6 offset 1024 size 1000205876 > /usr/mdec/biosboot will be written at sector 1024 > > and heres from bsd.rd shell: > Using /mnt as root > installing bootstrap on /dev/rsd1c > using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot > sd1: softraid volume with 1 disk(s) > sd1: installing boot loader on softraid volume > /mnt/usr/mdec/boot is 6 blocks x 16384 bytes > sd0a: installing boot blocks on /dev/rsd0c, part offset 1104 > master boot record (MBR) at sector 0 > partition 0: type 0xEF offset 64 size 960 > partition 3: type 0xA6 offset 1024 size 1000205876 > /mnt/usr/mdec/biosboot will be written at sector 1024 > > Looking at the output it seems to just copy the regular boot files and skips > processing EFI stuff. And as the system boots with EFI it uses the old > bootloader and hence the problems with opening the crypto volume. Correct - it is installing the MBR/PBR boot block and boot loader, rather than the EFI one. > Should there be check to see if the booted device has i partition with efi > folder and copy the EFI bootloader in that case? The code in question is the findgptefisys() function in src/usr.sbin/installboot/i386_installboot.c. It is likely that there is something up with your disk configuration (missing protective MBR, incorrect GPT header, incorrect GPT signature, corrupt checksum, etc) that is making it think that this is an MBR system, rather than a GPT one. That said, it is also possible that it is a bug/corner case... If you're able to sprinkle some printf's through that function and determine what check is failing, it would help narrow down the issue. You probably also want to check the MBR and GPT to see what is actually on the disk.
Re: Non-free firmware without asking the user
06.01.2017, 23:26, "Theo de Raadt" : > If you don't want such firmwares loaded onto the hardware, then don't > buy the hardware that needs it. > > There is your choice. > > I see no value in asking a user the question. I have misunderstood the purpose and use of the term "free" of OpenBSD then. "OpenBSD strives to provide code that can be freely used, copied, modified, and distributed by anyone and for any purpose", apparently there exists exceptions to this then. Of course it doesn't say anything like, "OpenBSD strives to ONLY provide.." Sorry, my mistake! > END OF CONVERSATION. > >> I know that we cannot trust the hardware vendors and that all the hardware >> is running firmware on ROMS, except some which are provided be the kernel. >> >> However, I fail to understand the reason for this patch: >> >> >> http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/miniroot/install.sub?f=h#rev1.654 >> >> It was really nice when OpenBSD asked during installation. >> >> Yes, it can be argued that since we cannot get any open hardware at all it >> doesn't matter whether the firmware is located on a ROM or if it's installed >> by the kernel, but if we use that logic we might as well just use whatever >> binary driver blob the vendors make for everything, right? >> >> If no, then why not, what's the difference between running closed source >> firmware and closed source drivers? >> >> During a Debian installation, or even a Linux Mint installation, the user >> gets the choice whether he wants to install these "non-free firmware blobs". >> >> What have I misunderstood? >> >> Kind regards, >> >> Martin
Re: relayd[66834]: relayd: socketpair: Too many open files
Just wanted to report back that as advertised 6.0-current from 2016-01-05
solved the problem described below.
Thanks Theo, Reyk, Peter, et al.
On Tue, Jan 3, 2017 at 1:16 PM, Kevin wrote:
> Hey gang,
>
> So I'm putting a new firewall in place and have run into issues with
> getting relayd to start using:
>
> # /etc/rc.d/relayd start
>
> When I try starting it like that inevitably I get:
>
> relayd(failed)
>
> checking the log files tells me:
>
> relayd: socketpair: Too many open files
>
> Having trolled through pages of SERPs, I can't find an answer; however, in
> the interest of science, if I do this:
>
> # ulimit -n 512
> # /usr/sbin/relayd
>
> it starts perfectly.
>
> Anyone care to give me a quick strike with the clue stick, please?
>
> Oh yah, here's my relayd.conf
>
> # Example.com
> # 145.176.20.136
> exm_chi01="192.168.2.0"
> exm_chi02="192.168.2.1"
>
> table{ $exm_chi01, $exm_chi02 }
>
> #=#
> # Servers #
> #=#
> redirect "Example.com" {
> listen on 145.176.20.162 port 80 interface vio0
> pftag RELAYD-Example.com
> forward to check tcp
> }
>
>
> For what it's worth, I'm using a hosts file to point example.com to my IP
> for the time being, as I can't pull the real sites down and move them 'til
> this is working.
>
> Also of interest: pf seems to be working as advertised, as does relayd
> when it's started with the ulimit cranked up.
>
>
> Thanks,
> Kevin
Non-free firmware without asking the user
Hi, I know that we cannot trust the hardware vendors and that all the hardware is running firmware on ROMS, except some which are provided be the kernel. However, I fail to understand the reason for this patch: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/miniroot/install.sub?f=h#rev1.654 It was really nice when OpenBSD asked during installation. Yes, it can be argued that since we cannot get any open hardware at all it doesn't matter whether the firmware is located on a ROM or if it's installed by the kernel, but if we use that logic we might as well just use whatever binary driver blob the vendors make for everything, right? If no, then why not, what's the difference between running closed source firmware and closed source drivers? During a Debian installation, or even a Linux Mint installation, the user gets the choice whether he wants to install these "non-free firmware blobs". What have I misunderstood? Kind regards, Martin
Re: Non-free firmware without asking the user
This has been discussed repeatedly on the mailing lists. Drivers run in user oder kernel space and should interface with devices sanely (and safely). Whereas in the case of closed firmware, as you said yourself, it doesn’t really matter where it is loaded from. > On 06 Jan 2017, at 22:45, Martin Hanson wrote: > > Hi, > > I know that we cannot trust the hardware vendors and that all the hardware is running firmware on ROMS, except some which are provided be the kernel. > > However, I fail to understand the reason for this patch: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/miniroot/install.sub?f=h #rev1.654 > > It was really nice when OpenBSD asked during installation. > > Yes, it can be argued that since we cannot get any open hardware at all it doesn't matter whether the firmware is located on a ROM or if it's installed by the kernel, but if we use that logic we might as well just use whatever binary driver blob the vendors make for everything, right? > > If no, then why not, what's the difference between running closed source firmware and closed source drivers? > > During a Debian installation, or even a Linux Mint installation, the user gets the choice whether he wants to install these "non-free firmware blobs". > > What have I misunderstood? > > Kind regards, > > Martin
Re: Non-free firmware without asking the user
> Martin Troll Troll Troll!
Re: Non-free firmware without asking the user
If you don't want such firmwares loaded onto the hardware, then don't buy the hardware that needs it. There is your choice. I see no value in asking a user the question. END OF CONVERSATION. > I know that we cannot trust the hardware vendors and that all the hardware is > running firmware on ROMS, except some which are provided be the kernel. > > However, I fail to understand the reason for this patch: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/distrib/miniroot/install.sub?f=h#rev1.654 > > It was really nice when OpenBSD asked during installation. > > Yes, it can be argued that since we cannot get any open hardware at all it > doesn't matter whether the firmware is located on a ROM or if it's installed > by the kernel, but if we use that logic we might as well just use whatever > binary driver blob the vendors make for everything, right? > > If no, then why not, what's the difference between running closed source > firmware and closed source drivers? > > During a Debian installation, or even a Linux Mint installation, the user > gets the choice whether he wants to install these "non-free firmware blobs". > > What have I misunderstood? > > Kind regards, > > Martin
Re: VPS default gateway in a different subnet than host
A brief follow-up. >From Zion VPS: "We have already started giving access to OpenBSD CDROM image to all clients in VPS control panel. We will prepare a template (click and ready) in the upcoming weeks." Thanks, Matthew, Martin and everyone! Yours, Jyri
Re: iwn problem on Thinkpad T410
Well, a little more experimenting with this machine and a couple of Linux live cds leads me to conclude that the wifi hardware in this machine is sick. The symptoms I reported are not an OpenBSD problem. /Don Allen On Fri, Jan 6, 2017 at 12:58 PM, Donald Allen wrote: > I just installed release 6.0 on this machine, and I get the same error. > > /Don Allen > > On Fri, Jan 6, 2017 at 12:06 PM, Donald Allen > wrote: > >> I just installed current from the most recent snapshot on a Thinkpad >> T410. Wireless networking doesn't work. During the install, I had an >> ethernet cable plugged in and configured the em0 interface (I use static ip >> addresses), so I could download the firmware. The firmware got loaded >> during the install, but to be sure, I ran fw_update after booting the >> installed system, which did nothing. After setting up /etc/hostname.iwn0 >> and saving away hostname.em0, I rebooted. Networking failed to initialize >> properly, with the message >> >> iwn0: could not load firmware .text section >> >> Here's the output of ls /etc/firmware/iwn*: >> >> /etc/firmware/iwn-100 >> /etc/firmware/iwn-1000 >> /etc/firmware/iwn-105 >> /etc/firmware/iwn-135 >> /etc/firmware/iwn-2000 >> /etc/firmware/iwn-2030 >> /etc/firmware/iwn-4965 >> /etc/firmware/iwn-5000 >> /etc/firmware/iwn-5150 >> /etc/firmware/iwn-6000 >> /etc/firmware/iwn-6005 >> /etc/firmware/iwn-6030 >> /etc/firmware/iwn-6050 >> /etc/firmware/iwn-license >> >> And the dmesg: >> >> OpenBSD 6.0-current (GENERIC.MP) #8: Sat Dec 3 22:18:48 MST 2016 >> bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> real mem = 4062691328 <(406)%20269-1328> (3874MB) >> avail mem = 3935006720 (3752MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) >> bios0: vendor LENOVO version "6IET83WW (1.43 )" date 04/12/2012 >> bios0: LENOVO 2522AN4 >> acpi0 at bios0: rev 2 >> acpi0: sleep states S0 S3 S4 S5 >> acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA >> SSDT SSDT SSDT >> acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) >> EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) >> acpitimer0 at acpi0: 3579545 Hz, 24 bits >> acpiec0 at acpi0 >> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat >> cpu0 at mainbus0: apid 0 (boot processor) >> cpu0: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.55 MHz >> cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO >> V,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,POPCNT,AES,NXE,LONG,LAHF,PERF, >> ITSC,SENSOR,ARAT >> cpu0: 256KB 64b/line 8-way L2 cache >> cpu0: smt 0, core 0, package 0 >> mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges >> cpu0: apic clock running at 133MHz >> cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE >> cpu1 at mainbus0: apid 1 (application processor) >> cpu1: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz >> cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO >> V,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,POPCNT,AES,NXE,LONG,LAHF,PERF, >> ITSC,SENSOR,ARAT >> cpu1: 256KB 64b/line 8-way L2 cache >> cpu1: smt 1, core 0, package 0 >> cpu2 at mainbus0: apid 4 (application processor) >> cpu2: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz >> cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO >> V,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,POPCNT,AES,NXE,LONG,LAHF,PERF, >> ITSC,SENSOR,ARAT >> cpu2: 256KB 64b/line 8-way L2 cache >> cpu2: smt 0, core 2, package 0 >> cpu3 at mainbus0: apid 5 (application processor) >> cpu3: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz >> cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMO >> V,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,POPCNT,AES,NXE,LONG,LAHF,PERF, >> ITSC,SENSOR,ARAT >> cpu3: 256KB 64b/line 8-way L2 cache >> cpu3: smt 1, core 2, package 0 >> ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins >> acpimcfg0 at acpi0 addr 0xe000, bus 0-255 >> acpihpet0 at acpi0: 14318179 Hz >> acpiprt0 at acpi0: bus 0 (PCI0) >> acpiprt1 at acpi0: bus -1 (PEG_) >> acpiprt2 at acpi0: bus 2 (EXP1) >> acpiprt3 at acpi0: bus 3 (EXP2) >> acpiprt4 at acpi0: bus -1 (EXP3) >> acpiprt5 at acpi0: bus 5 (EXP4) >> acpiprt6 at acpi0: bus 13 (EXP5) >> acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), >> C1(1000@3 mwait.1), PSS >> acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), >> C1(1000@3 mwait.1), PSS >> acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205
Re: iwn problem on Thinkpad T410
I just installed release 6.0 on this machine, and I get the same error. /Don Allen On Fri, Jan 6, 2017 at 12:06 PM, Donald Allen wrote: > I just installed current from the most recent snapshot on a Thinkpad T410. > Wireless networking doesn't work. During the install, I had an ethernet > cable plugged in and configured the em0 interface (I use static ip > addresses), so I could download the firmware. The firmware got loaded > during the install, but to be sure, I ran fw_update after booting the > installed system, which did nothing. After setting up /etc/hostname.iwn0 > and saving away hostname.em0, I rebooted. Networking failed to initialize > properly, with the message > > iwn0: could not load firmware .text section > > Here's the output of ls /etc/firmware/iwn*: > > /etc/firmware/iwn-100 > /etc/firmware/iwn-1000 > /etc/firmware/iwn-105 > /etc/firmware/iwn-135 > /etc/firmware/iwn-2000 > /etc/firmware/iwn-2030 > /etc/firmware/iwn-4965 > /etc/firmware/iwn-5000 > /etc/firmware/iwn-5150 > /etc/firmware/iwn-6000 > /etc/firmware/iwn-6005 > /etc/firmware/iwn-6030 > /etc/firmware/iwn-6050 > /etc/firmware/iwn-license > > And the dmesg: > > OpenBSD 6.0-current (GENERIC.MP) #8: Sat Dec 3 22:18:48 MST 2016 > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4062691328 <(406)%20269-1328> (3874MB) > avail mem = 3935006720 (3752MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) > bios0: vendor LENOVO version "6IET83WW (1.43 )" date 04/12/2012 > bios0: LENOVO 2522AN4 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA > SSDT SSDT SSDT > acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) > EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpiec0 at acpi0 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.55 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,POPCNT,AES,NXE,LONG, > LAHF,PERF,ITSC,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 133MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 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, > CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG, > LAHF,PERF,ITSC,SENSOR,ARAT > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 1, core 0, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz > cpu2: 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,POPCNT,AES,NXE,LONG, > LAHF,PERF,ITSC,SENSOR,ARAT > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 5 (application processor) > cpu3: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz > cpu3: 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,POPCNT,AES,NXE,LONG, > LAHF,PERF,ITSC,SENSOR,ARAT > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 2, package 0 > ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 addr 0xe000, bus 0-255 > acpihpet0 at acpi0: 14318179 Hz > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEG_) > acpiprt2 at acpi0: bus 2 (EXP1) > acpiprt3 at acpi0: bus 3 (EXP2) > acpiprt4 at acpi0: bus -1 (EXP3) > acpiprt5 at acpi0: bus 5 (EXP4) > acpiprt6 at acpi0: bus 13 (EXP5) > acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), > C1(1000@3 mwait.1), PSS > acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), > C1(1000@3 mwait.1), PSS > acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), > C1(1000@3 mwait.1), PSS > acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), > C1(1000@3 mwait.1), PSS > acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 > acpitz0 at acpi0: critical temperature is 100 degC > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: SLPB > "PNP0303" at acpi0 not configured > "LEN0015" at acpi0 not configured > "SMO1200" at
Re: iwn problem on Thinkpad T410
On Fri, Jan 06, 2017 at 12:06:24PM -0500, Donald Allen wrote: > I just installed current from the most recent snapshot on a Thinkpad T410. > Wireless networking doesn't work. During the install, I had an ethernet > cable plugged in and configured the em0 interface (I use static ip > addresses), so I could download the firmware. The firmware got loaded > during the install, but to be sure, I ran fw_update after booting the > installed system, which did nothing. After setting up /etc/hostname.iwn0 > and saving away hostname.em0, I rebooted. Networking failed to initialize > properly, with the message > > iwn0: could not load firmware .text section > > Here's the output of ls /etc/firmware/iwn*: > > /etc/firmware/iwn-100 > /etc/firmware/iwn-1000 > /etc/firmware/iwn-105 > /etc/firmware/iwn-135 > /etc/firmware/iwn-2000 > /etc/firmware/iwn-2030 > /etc/firmware/iwn-4965 > /etc/firmware/iwn-5000 > /etc/firmware/iwn-5150 > /etc/firmware/iwn-6000 > /etc/firmware/iwn-6005 > /etc/firmware/iwn-6030 > /etc/firmware/iwn-6050 > /etc/firmware/iwn-license Let's rule out the obvious: Is the firmware image corrupt? SHA1 checksums on my system are: $ sha1 /etc/firmware/iwn-* SHA1 (/etc/firmware/iwn-100) = 5f85593988e9542ca9246e3130c449ed638b6afe SHA1 (/etc/firmware/iwn-1000) = a824bb5f10b28ce71cef91836cbd25760ea9b4a3 SHA1 (/etc/firmware/iwn-105) = dc733a79244337c037525654d421983376e93c33 SHA1 (/etc/firmware/iwn-135) = 4493a7b9d5d297b692e44aa3b0031ebff76014c6 SHA1 (/etc/firmware/iwn-2000) = 9e1b8d630cdffad7706f31087444980a8cc48fb5 SHA1 (/etc/firmware/iwn-2030) = 7508670d5c0a2056e06e3197b9501636e76cf6bf SHA1 (/etc/firmware/iwn-4965) = 86b4ff04133b2b44412833234dc1dfbb502a4b7a SHA1 (/etc/firmware/iwn-5000) = 22bf6093ed8204027cc3207c739d2cab9cc92ea3 SHA1 (/etc/firmware/iwn-5150) = 0b41795a98272d125998d8bc1c0d478a4e5ef71e SHA1 (/etc/firmware/iwn-6000) = a337927d149bf7b2072f79f8325011fe5b3dad68 SHA1 (/etc/firmware/iwn-6005) = 1936ad5fe2551ac9d6551be0d85984c1f5cc5cf7 SHA1 (/etc/firmware/iwn-6030) = 0c5dbfed5f50ef39b56827651f572bea25bfc27e SHA1 (/etc/firmware/iwn-6050) = 0a881b0100ac82b7eab25d5a297f003fcd76ee7b SHA1 (/etc/firmware/iwn-license) = a988c3a968dc9689d9cf5770c639a0e2f598c5ae $ pkg_info | grep iwn-firmware iwn-firmware-5.11p1 firmware binary images for iwn(4) driver
iwn problem on Thinkpad T410
I just installed current from the most recent snapshot on a Thinkpad T410. Wireless networking doesn't work. During the install, I had an ethernet cable plugged in and configured the em0 interface (I use static ip addresses), so I could download the firmware. The firmware got loaded during the install, but to be sure, I ran fw_update after booting the installed system, which did nothing. After setting up /etc/hostname.iwn0 and saving away hostname.em0, I rebooted. Networking failed to initialize properly, with the message iwn0: could not load firmware .text section Here's the output of ls /etc/firmware/iwn*: /etc/firmware/iwn-100 /etc/firmware/iwn-1000 /etc/firmware/iwn-105 /etc/firmware/iwn-135 /etc/firmware/iwn-2000 /etc/firmware/iwn-2030 /etc/firmware/iwn-4965 /etc/firmware/iwn-5000 /etc/firmware/iwn-5150 /etc/firmware/iwn-6000 /etc/firmware/iwn-6005 /etc/firmware/iwn-6030 /etc/firmware/iwn-6050 /etc/firmware/iwn-license And the dmesg: OpenBSD 6.0-current (GENERIC.MP) #8: Sat Dec 3 22:18:48 MST 2016 bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 4062691328 (3874MB) avail mem = 3935006720 (3752MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xe0010 (78 entries) bios0: vendor LENOVO version "6IET83WW (1.43 )" date 04/12/2012 bios0: LENOVO 2522AN4 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP SSDT ECDT APIC MCFG HPET ASF! SLIC BOOT SSDT TCPA SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) EXP5(S4) EHC1(S3) EHC2(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpiec0 at acpi0 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.55 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,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 133MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.1, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 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,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz cpu2: 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,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 5 (application processor) cpu3: Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz, 2926.01 MHz cpu3: 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,POPCNT,AES,NXE,LONG,LAHF,PERF,ITSC,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 1, core 2, package 0 ioapic0 at mainbus0: apid 1 pa 0xfec0, version 20, 24 pins acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus -1 (EXP3) acpiprt5 at acpi0: bus 5 (EXP4) acpiprt6 at acpi0: bus 13 (EXP5) acpicpu0 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu1 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu2 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpicpu3 at acpi0: C3(350@245 mwait.3@0x20), C2(500@205 mwait.3@0x10), C1(1000@3 mwait.1), PSS acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 acpitz0 at acpi0: critical temperature is 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB "PNP0303" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured acpibat0 at acpi0: BAT0 model "42T4801" serial 8844 type LION oem "Panasonic" acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 "*pnp0c14" at acpi0 not configured "PNP0C14" at acpi0 not configured acpivideo0 at acpi0: VID_ acpivout0 at acpivideo0: LCD0 acpivideo1 at acpi0: VID_ cpu0: Enhanced SpeedStep 2926 MHz: speeds: 2667, 2666, 2533, 2399, 2266, 2133, 1999, 186
Re: Using "Pretty" permalinks with httpd in wordpress
This was my hack.
http://www.h-i-r.net/2016/04/pretty-wordpress-permalinks-under.html
tl;dr:
1) ln -s index.php posts
2) null out "security.limit_extensions" in the php_fpm config, restart FPM.
Beware the potential abuses of this.
3) Set up an explicit location clause for "/posts*" that uses the fastcgi
socket for FPM.
4) Configure wordpress permalinks with a custom structure that includes
/posts
On Fri, Jan 6, 2017 at 7:42 AM, Atanas Vladimirov wrote:
> On 06.01.2017 13:35, Jiri B wrote:
>
>> On Fri, Jan 06, 2017 at 01:32:10PM +0200, Atanas Vladimirov wrote:
>>
>>> Hi,
>>>
>>> I can't figure it out.
>>> Is it possible to use Wordpress with OpenBSD httpd and configure both
>>> for "Pretty" permalinks.
>>> Does anyone have a working setup?
>>> Thanks for your time,
>>> Atanas
>>>
>>
>> Help testing this diff http://marc.info/?l=openbsd-te
>> ch&m=148370177214134&w=2
>>
>> j.
>>
> I know about the diff and I'm testing it right now.
> The problem is that I really don't know what to put in
> httpd.conf.
> I try to "translate" Wordpress .htaccess with no luck:
>
> # BEGIN WordPress
>
> RewriteEngine On
> RewriteBase /
> RewriteRule ^index\.php$ - [L]
> ^^^ this rule doesn't rewrite index.php
> RewriteCond %{REQUEST_FILENAME} !-f
> RewriteCond %{REQUEST_FILENAME} !-d
> RewriteRule . /index.php [L]
> ^^^ this rule rewrites any single character to /index.php
> if %{REQUEST_FILENAME} is not a real file or directory
>
> # END WordPress
>
> Do I read/understand the .htaccess file correctly?
> In my httpd.conf:
> .
> # art-katerina.com
> server "art-katerina.com" {
> listen on * tls port 443
> alias www.art-katerina.com
> directory index index.php
> root "/domains/art-katerina.com/"
> hsts
> log {
> access "art-katerina-access.log",
> error "art-katerina-error.log",
> style combined
> }
> location "/.well-known/acme-challenge/*" {
> root "/acme"
> root strip 2
> }
> tls {
> certificate "/etc/ssl/acme/art-katerina.com/fullchain.pem"
> key "/etc/ssl/acme/private/art-katerina.com/privkey.pem"
> }
> location "*.php" {
> fastcgi socket "/run/php-fpm.sock"
> }
> location match "(.)" {
> pass rewrite "/index.php"
> fastcgi socket "/run/php-fpm.sock"
> }
> .
Re: Using "Pretty" permalinks with httpd in wordpress
On 06.01.2017 13:35, Jiri B wrote:
On Fri, Jan 06, 2017 at 01:32:10PM +0200, Atanas Vladimirov wrote:
Hi,
I can't figure it out.
Is it possible to use Wordpress with OpenBSD httpd and configure both
for "Pretty" permalinks.
Does anyone have a working setup?
Thanks for your time,
Atanas
Help testing this diff
http://marc.info/?l=openbsd-tech&m=148370177214134&w=2
j.
I know about the diff and I'm testing it right now.
The problem is that I really don't know what to put in
httpd.conf.
I try to "translate" Wordpress .htaccess with no luck:
# BEGIN WordPress
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
^^^ this rule doesn't rewrite index.php
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
^^^ this rule rewrites any single character to /index.php
if %{REQUEST_FILENAME} is not a real file or directory
# END WordPress
Do I read/understand the .htaccess file correctly?
In my httpd.conf:
.
# art-katerina.com
server "art-katerina.com" {
listen on * tls port 443
alias www.art-katerina.com
directory index index.php
root "/domains/art-katerina.com/"
hsts
log {
access "art-katerina-access.log",
error "art-katerina-error.log",
style combined
}
location "/.well-known/acme-challenge/*" {
root "/acme"
root strip 2
}
tls {
certificate
"/etc/ssl/acme/art-katerina.com/fullchain.pem"
key "/etc/ssl/acme/private/art-katerina.com/privkey.pem"
}
location "*.php" {
fastcgi socket "/run/php-fpm.sock"
}
location match "(.)" {
pass rewrite "/index.php"
fastcgi socket "/run/php-fpm.sock"
}
.
Re: Unable to boot encrypted drive
Joel Sing writes:
> On Friday 06 January 2017 12:24:02 Timo Myyrä wrote:
>> And found it. Seems the efi partitions boot loader isn't updated.
>
> It should be - `installboot -r /mnt ${disk}` is run at the end of the
upgrade.
>
>> Manually copying the efi bootloader fixed the boot:
>> https://blog.jasper.la/openbsd-uefi-bootloader-howto/
>>
>> Why isn't the installer handling this?
>
> I cannot immediately see any reason why it should not be, but I do not have
a
> GPT machine available to test/verify - I presume there are no failures
> reported towards the end of the upgrade?
>
> Can you try running `installboot -v` against the softraid volume?
>
> If that works, can you boot bsd.rd, drop into a shell, mount the root volume
> on /mnt, then run `installboot -v -r /mnt` against the root disk?
Upgrades have seem to been successful when I've done them. I've used the
normal,
boot bsd.rd, do upgrade cycle for a while and haven't noticed any errors.
Here's the output of installboot on running system:
$ doas installboot -v sd1
Using / as root
installing bootstrap on /dev/rsd1c
using first-stage /usr/mdec/biosboot, second-stage /usr/mdec/boot
sd1: softraid volume with 1 disk(s)
sd1: installing boot loader on softraid volume
/usr/mdec/boot is 6 blocks x 16384 bytes
sd0a: installing boot blocks on /dev/rsd0c, part offset 1104
master boot record (MBR) at sector 0
partition 0: type 0xEF offset 64 size 960
partition 3: type 0xA6 offset 1024 size 1000205876
/usr/mdec/biosboot will be written at sector 1024
and heres from bsd.rd shell:
Using /mnt as root
installing bootstrap on /dev/rsd1c
using first-stage /mnt/usr/mdec/biosboot, second-stage /mnt/usr/mdec/boot
sd1: softraid volume with 1 disk(s)
sd1: installing boot loader on softraid volume
/mnt/usr/mdec/boot is 6 blocks x 16384 bytes
sd0a: installing boot blocks on /dev/rsd0c, part offset 1104
master boot record (MBR) at sector 0
partition 0: type 0xEF offset 64 size 960
partition 3: type 0xA6 offset 1024 size 1000205876
/mnt/usr/mdec/biosboot will be written at sector 1024
Looking at the output it seems to just copy the regular boot files and skips
processing EFI stuff. And as the system boots with EFI it uses the old
bootloader and hence the problems with opening the crypto volume.
Should there be check to see if the booted device has i partition with efi
folder and copy the EFI bootloader in that case?
In any case, I have following options on BIOS if they have any relation to
this:
UEFI/Legacy boot: UEFI only
CMS Support: yes
Timo
Re: usermod: Invalid password: `*'
On Thu, 05 Jan 2017 08:22:04 -0700 Todd C. Miller wrote: > This works in -current. I've verified that it works with rev 1.112 > of user.c but OpenBSD 6.0 has user.c rev 1.111. > Thanks Todd. Superb the super devs have swiftly solved it! (This operation ran fine from my rc.firsttime script up to 5.9.) Do you think there would be an errata about this for 6.0? Personally, I've only a few more machines to install 6.0 on, so I'll script this (which works): # usermod -L daemon -s /bin/ksh operator and after install manually vipw(8) operator's password to 13 stars. (Here, operator runs dump(8) scripts & related rdist cron jobs, etc.) Cool, -- Craig Skinner | http://linkd.in/yGqkv7
Re: Unable to boot encrypted drive
On Friday 06 January 2017 12:24:02 Timo Myyrä wrote:
> And found it. Seems the efi partitions boot loader isn't updated.
It should be - `installboot -r /mnt ${disk}` is run at the end of the
upgrade.
> Manually copying the efi bootloader fixed the boot:
> https://blog.jasper.la/openbsd-uefi-bootloader-howto/
>
> Why isn't the installer handling this?
I cannot immediately see any reason why it should not be, but I do not have a
GPT machine available to test/verify - I presume there are no failures
reported towards the end of the upgrade?
Can you try running `installboot -v` against the softraid volume?
If that works, can you boot bsd.rd, drop into a shell, mount the root volume
on /mnt, then run `installboot -v -r /mnt` against the root disk?
Re: Using "Pretty" permalinks with httpd in wordpress
On Fri, Jan 06, 2017 at 01:32:10PM +0200, Atanas Vladimirov wrote: > Hi, > > I can't figure it out. > Is it possible to use Wordpress with OpenBSD httpd and configure both > for "Pretty" permalinks. > Does anyone have a working setup? > Thanks for your time, > Atanas Help testing this diff http://marc.info/?l=openbsd-tech&m=148370177214134&w=2 j.
Using "Pretty" permalinks with httpd in wordpress
Hi, I can't figure it out. Is it possible to use Wordpress with OpenBSD httpd and configure both for "Pretty" permalinks. Does anyone have a working setup? Thanks for your time, Atanas
Re: Unable to boot encrypted drive
timo.my...@wickedbsd.net (Timo Myyrä) writes: > Martin Ziemer writes: > >>> I recently changed my FDE passphrase and now my laptop won't boot. >>> Bootloader just gives me "invalid passphrase" when I try to unlock it on boot. >>> Its a bit odd as I can boot usb stick and manually open the drive and upgrade >>> the openbsd installation on it. It just won't work on the boot. >> Some weeks ago I had a similar problem. The problem started, because >> i changed the password from an system running an newer snapshot than >> the encrypted System. (So "invalid passphrase" can also mean "too new >> fde") >> >> The solution for me was starting an update from a new bsd.rd. After >> the update everything was fine again. > > Hmm, seems to be something with the boot version. > When I boot my installation I get: > EFIBOOT 3.29 and I can't unlock the volume. > > I'm bit stuck on how to proceed, I downloaded miniroot60.fs from amd64 snapshots > and made bootable stick. I can boot the system with it, manually unlock the drive and do > an upgrade. But after the upgrade I still can't boot the system. Shouldn't the > upgrade update the boot version as well? > > Timo And found it. Seems the efi partitions boot loader isn't updated. Manually copying the efi bootloader fixed the boot: https://blog.jasper.la/openbsd-uefi-bootloader-howto/ Why isn't the installer handling this? Timo
Re: Unable to boot encrypted drive
Martin Ziemer writes: >> I recently changed my FDE passphrase and now my laptop won't boot. >> Bootloader just gives me "invalid passphrase" when I try to unlock it on >> boot. >> Its a bit odd as I can boot usb stick and manually open the drive and upgrade >> the openbsd installation on it. It just won't work on the boot. > Some weeks ago I had a similar problem. The problem started, because > i changed the password from an system running an newer snapshot than > the encrypted System. (So "invalid passphrase" can also mean "too new > fde") > > The solution for me was starting an update from a new bsd.rd. After > the update everything was fine again. Hmm, seems to be something with the boot version. When I boot my installation I get: EFIBOOT 3.29 and I can't unlock the volume. I'm bit stuck on how to proceed, I downloaded miniroot60.fs from amd64 snapshots and made bootable stick. I can boot the system with it, manually unlock the drive and do an upgrade. But after the upgrade I still can't boot the system. Shouldn't the upgrade update the boot version as well? Timo
Re: Unable to boot encrypted drive
> I recently changed my FDE passphrase and now my laptop won't boot. > Bootloader just gives me "invalid passphrase" when I try to unlock it on boot. > Its a bit odd as I can boot usb stick and manually open the drive and upgrade > the openbsd installation on it. It just won't work on the boot. Some weeks ago I had a similar problem. The problem started, because i changed the password from an system running an newer snapshot than the encrypted System. (So "invalid passphrase" can also mean "too new fde") The solution for me was starting an update from a new bsd.rd. After the update everything was fine again.
Re: Unable to boot encrypted drive
On Fri, Jan 06, 2017 at 10:45:20AM +0200, Timo Myyrä wrote: > Hi, > > I recently changed my FDE passphrase and now my laptop won't boot. > Bootloader just gives me "invalid passphrase" when I try to unlock it on boot. > Its a bit odd as I can boot usb stick and manually open the drive and upgrade > the openbsd installation on it. It just won't work on the boot. > > Would this be related to recent boot changes or would it be different issue? Check http://www.openbsd.org/faq/current.html 2016/09/19 - softraid crypto switched to bcrypt PBKDF -Otto > > Timo > > OpenBSD 6.0-current (RAMDISK_CD) #106: Thu Jan 5 20:38:21 MST 2017 > bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD > real mem = 16973611008 (16187MB) > avail mem = 16455446528 (15693MB) > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (68 entries) > bios0: vendor LENOVO version "G7ETA4WW (2.64 )" date 10/08/2015 > bios0: LENOVO 2355C16 > acpi0 at bios0: rev 2 > acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT > ASF! UEFI UEFI POAT SSDT SSDT DMAR SSDT UEFI DBG2 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2594.56 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,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: TSC frequency 2594564560 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 > acpiec0 at acpi0 > acpiprt0 at acpi0: bus 0 (PCI0) > acpiprt1 at acpi0: bus -1 (PEG_) > acpiprt2 at acpi0: bus 2 (EXP1) > acpiprt3 at acpi0: bus 3 (EXP2) > acpiprt4 at acpi0: bus 4 (EXP3) > acpiprt5 at acpi0: bus -1 (EXP5) > acpiprt6 at acpi0: bus -1 (EXP6) > acpiprt7 at acpi0: bus -1 (EXP7) > acpiprt8 at acpi0: bus -1 (EXP8) > acpicpu at acpi0 not configured > acpipwrres at acpi0 not configured > acpitz at acpi0 not configured > "PNP0C0D" at acpi0 not configured > "PNP0C0E" at acpi0 not configured > "LEN0071" at acpi0 not configured > "LEN0015" at acpi0 not configured > "SMO1200" at acpi0 not configured > "PNP0C0A" at acpi0 not configured > "ACPI0003" at acpi0 not configured > "LEN0078" at acpi0 not configured > "LEN0068" at acpi0 not configured > "PNP0C14" at acpi0 not configured > "PNP0C14" at acpi0 not configured > "PNP0C14" at acpi0 not configured > "INT3392" at acpi0 not configured > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 > "Intel HD Graphics 4000" rev 0x09 at pci0 dev 2 function 0 not configured > 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 > 3c:97:0e:60:8d:ca > 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 2 > ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi > pci2 at ppb1 bus 3 > iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, > MIMO 2T2R, MoW, address 60:67:20:f8:17:f4 > ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi > pci3 at ppb2 bus 4 > sdhc0 at pci3 dev 0 function 0 "Ricoh 5U823 SD/MMC" rev 0x04: apic 2 int 18 > sdhc0: SDHC 3.0, 50 MHz base clock > sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed > ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 > 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 > ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 > ahci0: port 0: 6.0Gb/s > ahci0: port 1: 1.5Gb/s > scsibus0 at ahci0: 32 targets > sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct > fixed naa.50025388400c34c6 > sd0: 488386MB, 512 bytes/sector, 1000215216 sectors, thin > cd0 at scsibus0 targ 1 lun 0: ATAPI 5/cdrom > removable > "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)
Unable to boot encrypted drive
Hi, I recently changed my FDE passphrase and now my laptop won't boot. Bootloader just gives me "invalid passphrase" when I try to unlock it on boot. Its a bit odd as I can boot usb stick and manually open the drive and upgrade the openbsd installation on it. It just won't work on the boot. Would this be related to recent boot changes or would it be different issue? Timo OpenBSD 6.0-current (RAMDISK_CD) #106: Thu Jan 5 20:38:21 MST 2017 bu...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 16973611008 (16187MB) avail mem = 16455446528 (15693MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xdae9c000 (68 entries) bios0: vendor LENOVO version "G7ETA4WW (2.64 )" date 10/08/2015 bios0: LENOVO 2355C16 acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SLIC TCPA SSDT SSDT SSDT HPET APIC MCFG ECDT FPDT ASF! UEFI UEFI POAT SSDT SSDT DMAR SSDT UEFI DBG2 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-3320M CPU @ 2.60GHz, 2594.56 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,LONG,LAHF,PERF,ITSC,FSGSBASE,SMEP,ERMS,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 2594564560 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 acpiec0 at acpi0 acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PEG_) acpiprt2 at acpi0: bus 2 (EXP1) acpiprt3 at acpi0: bus 3 (EXP2) acpiprt4 at acpi0: bus 4 (EXP3) acpiprt5 at acpi0: bus -1 (EXP5) acpiprt6 at acpi0: bus -1 (EXP6) acpiprt7 at acpi0: bus -1 (EXP7) acpiprt8 at acpi0: bus -1 (EXP8) acpicpu at acpi0 not configured acpipwrres at acpi0 not configured acpitz at acpi0 not configured "PNP0C0D" at acpi0 not configured "PNP0C0E" at acpi0 not configured "LEN0071" at acpi0 not configured "LEN0015" at acpi0 not configured "SMO1200" at acpi0 not configured "PNP0C0A" at acpi0 not configured "ACPI0003" at acpi0 not configured "LEN0078" at acpi0 not configured "LEN0068" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "PNP0C14" at acpi0 not configured "INT3392" at acpi0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 3G Host" rev 0x09 "Intel HD Graphics 4000" rev 0x09 at pci0 dev 2 function 0 not configured 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 3c:97:0e:60:8d:ca 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 2 ppb1 at pci0 dev 28 function 1 "Intel 7 Series PCIE" rev 0xc4: msi pci2 at ppb1 bus 3 iwn0 at pci2 dev 0 function 0 "Intel Centrino Advanced-N 6205" rev 0x34: msi, MIMO 2T2R, MoW, address 60:67:20:f8:17:f4 ppb2 at pci0 dev 28 function 2 "Intel 7 Series PCIE" rev 0xc4: msi pci3 at ppb2 bus 4 sdhc0 at pci3 dev 0 function 0 "Ricoh 5U823 SD/MMC" rev 0x04: apic 2 int 18 sdhc0: SDHC 3.0, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed ehci1 at pci0 dev 29 function 0 "Intel 7 Series USB" rev 0x04: apic 2 int 23 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 ahci0 at pci0 dev 31 function 2 "Intel 7 Series AHCI" rev 0x04: msi, AHCI 1.3 ahci0: port 0: 6.0Gb/s ahci0: port 1: 1.5Gb/s scsibus0 at ahci0: 32 targets sd0 at scsibus0 targ 0 lun 0: SCSI3 0/direct fixed naa.50025388400c34c6 sd0: 488386MB, 512 bytes/sector, 1000215216 sectors, thin cd0 at scsibus0 targ 1 lun 0: ATAPI 5/cdrom removable "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 efifb0 at mainbus0: 1600x900, 32bpp wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 umass0 at uhub0 port 1 configuration 1 interface 0 "SanDisk Corporation Cruzer Mini" rev 2.00/0.20 addr 2 umass0: using SCSI over Bulk-Only scsibus1 at umass0: 2 targets, initiator 0 sd1 at scsibus1 targ 1 lun 0: SCSI2 0/direct removable s
