X1 Thinkpad Tablet Freeze on Boot
First time actually submitting a bug so let me know if there's anything I missed, or if this is the wrong way to submit it- Trying to install OpenBSD on Thinkpad Tablet X1 Gen 3 currently. Every boot gets hung on "entry point at 0x1001000". Can't get to dmesg or I'd try to give more specifics. Have tried: - Regular install via USB and install65.fs (both current and stable) - Taking SSD out and installing via my already working OpenBSD machine - Installing via CD - Throwing a bsd.rd in an EFI partition and trying to boot it via GRUB - Booting an external hard drive with working OpenBSD system on it Any help would be welcome at this point- not a programmer by trade, but if someone can direct me to at least how to debug it, I can try to put a temporary fix together and send it to someone who knows what the hell they're doing.
Re: X1 Thinkpad Tablet Freeze on Boot
Ah- I'm just now seeing the note about the screen going black after the kernel loads into memory, and doing some more digging shows the same kind of issue when CSM isn't enabled. Unfortunately they had said that CSM wasn't supported with the tablet... https://forums.lenovo.com/t5/ThinkPad-Tablets/Unable-to-enable-CSM-in-BIOS/m-p/4472630 Any ideas where to go from here? Either way I appreciate the advice. At least I know where to start looking! On Mon, Jul 15, 2019 at 1:43 PM Todd C. Miller wrote: > You probably need to make some changes to the bios settings, if you > haven't already done so. Try disabling "secure boot" and enabling > "CSM Support" and see if that makes a difference. > > Some of the info at https://jcs.org/2017/09/01/thinkpad_x1c may > also be applicable. > > - todd >
Re: xenodm having issues when launching a wm
Are you using a modified xorg.conf.d, and mind showing your xsession? On Thu, Aug 22, 2019 at 2:58 PM kaletaa wrote: > Hello, > xenodm is having issues while starting a dwm session, > I'm using a Thinkpad x220, OpenBSD 6.5 > > dmesg > > > OpenBSD 6.5 (GENERIC.MP) #3: Sat Apr 13 14:48:43 MDT 2019 > dera...@amd64.openbsd.org > :/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 4156157952 (3963MB) > avail mem = 4020576256 (3834MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.6 @ 0xdae9c000 (65 entries) > bios0: vendor LENOVO version "8DET55WW (1.25 )" date 11/01/2011 > bios0: LENOVO 42912XG > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP SLIC SSDT SSDT SSDT HPET APIC MCFG ECDT ASF! TCPA > SSDT SSDT UEFI UEFI UEFI > acpi0: wakeup devices LID_(S3) SLPB(S3) IGBE(S4) EXP4(S4) EXP7(S4) > EHC1(S3) EHC2(S3) HDEF(S4) > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpihpet0 at acpi0: 14318179 Hz > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 797.54 MHz, 06-2a-07 > 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,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu0: 256KB 64b/line 8-way L2 cache > 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.1.2, IBE > cpu1 at mainbus0: apid 1 (application processor) > cpu1: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 797.41 MHz, 06-2a-07 > 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 1, core 0, package 0 > cpu2 at mainbus0: apid 2 (application processor) > cpu2: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 797.42 MHz, 06-2a-07 > 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu2: 256KB 64b/line 8-way L2 cache > cpu2: smt 0, core 1, package 0 > cpu3 at mainbus0: apid 3 (application processor) > cpu3: Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, 797.41 MHz, 06-2a-07 > 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,x2APIC,POPCNT,DEADLINE,AES,XSAVE,AVX,NXE,RDTSCP,LONG,LAHF,PERF,ITSC,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu3: 256KB 64b/line 8-way L2 cache > cpu3: smt 1, core 1, package 0 > ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins > acpimcfg0 at acpi0 > acpimcfg0: addr 0xf800, bus 0-63 > 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 5 (EXP4) > acpiprt5 at acpi0: bus 13 (EXP5) > acpiprt6 at acpi0: bus -1 (EXP7) > acpicpu0 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu1 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu2 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpicpu3 at acpi0: C3(200@109 io@0x416), C2(500@80 io@0x414), C1(1000@1 > halt), PSS > acpipwrres0 at acpi0: PUBS, resource for EHC1, EHC2 > acpitz0 at acpi0: critical temperature is 99 degC > acpibtn0 at acpi0: LID_ > acpibtn1 at acpi0: SLPB > acpipci0 at acpi0 PCI0: 0x 0x0011 0x0001 > acpicmos0 at acpi0 > tpm0 at acpi0: TPM_ addr 0xfed4/0x5000: device 0x104a rev 0x4e > acpibat0 at acpi0: BAT0 model "45N1023" serial 15921 type LION oem "SANYO" > acpiac0 at acpi0: AC unit offline > acpithinkpad0 at acpi0 > "PNP0C14" at acpi0 not configured > "PNP0C14" at acpi0 not configured > acpidock0 at acpi0: GDCK not docked (0) > acpivideo0 at acpi0: VID_ > acpivout at acpivideo0 not configured > acpivideo1 at acpi0: VID_ > cpu0: Enhanced SpeedStep 797 MHz: speeds: 2601, 2600, 2400, 2200, 2000, > 1800, 1600, 1400, 1200, 1000, 800 MHz > pci0 at mainbus0 bus 0 > pchb0 at pci0 dev 0 function 0 "Intel Core 2G Host" rev 0x09 > inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics
Re: AMDGPU in current issue
Thanks for the advice!
Do you happen to have a link to the commit amdgpu is at currently?
On Wed, Sep 4, 2019 at 9:44 AM Jonathan Gray wrote:
> Look for individual post 4.19 linux commits that are relevant.
> We have in the past taken small patches to enable more
> generations of hardware.
>
> On Wed, Sep 04, 2019 at 08:11:24AM -0500, Charlie Burnett wrote:
> > Hey,
> > I???ve been trying to write a patch to get vega 20 working, but due to a
> > screw up on my end I lost the progress I???d made. Before I start over
> again,
> > I was wondering if you had any advice on how to do it? Before, I was
> trying
> > to more or less just port the vega 20 hwmgr files in from FreeBSD drm
> next
> > which is at linux drm 5.0 as well as the other files which seemed to
> > mention Vega 20 or seemed to be needed to compile. I wasn???t having much
> > luck as you can imagine, and currently I???m still in university so my
> > experience with kernel patching isn???t fantastic, I was wondering if you
> > might have any advice where to begin if I???m having to start from
> scratch?
> > Best regards,
> > Charlie Burnett
> >
> > On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote:
> >
> > > On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> > > > Hey-
> > > > I'd been messing around with the AMDGPU on current (which I'm aware
> is
> > > very
> > > > experimental) and had very few issues with it using a Vega 56 GPU. I
> > > > recently swapped to another Vega GPU (Radeon VII) and have issues
> with
> > > the
> > > > display not showing anything. Still boots fine, in that I can still
> enter
> > > > commands (i.e. reboot) so it has to be a display issue. I tried
> searching
> > > > for the diff where the firmware was added which I'm certain I saw
> (for
> > > Vega
> > > > 20) but can't seem to find it in the commit history. Anyone have a
> fix
> > > for
> > > > it, and if not, who should I talk to if I wanted to help get it
> working?
> > > I
> > > > saw most of the AMDGPU commits have been by @jonathangray if he
> would be
> > > > the best option.
> > > > Thanks!
> > >
> > > vega20 firmware was added when ports/sysutils/firmware/amdgpu was
> > > updated to 20190312.
> > >
> > > vega20 is marked as experimental in the version of drm we have, but we
> > > don't currently check the flag on probe like linux does.
> > >
> > > The following diff will prevent amdgpu from matching on devices
> > > in the amdgpu_pciidlist table with the AMD_EXP_HW_SUPPORT flag
> > > (currently these are all vega20 ids).
> > >
> > > Index: sys/dev/pci/drm/include/drm/drm_drv.h
> > > ===
> > > RCS file: /cvs/src/sys/dev/pci/drm/include/drm/drm_drv.h,v
> > > retrieving revision 1.2
> > > diff -u -p -r1.2 drm_drv.h
> > > --- sys/dev/pci/drm/include/drm/drm_drv.h 25 Jul 2019 05:48:16
> > > - 1.2
> > > +++ sys/dev/pci/drm/include/drm/drm_drv.h 2 Aug 2019 03:29:58
> -
> > > @@ -291,5 +291,7 @@ static inline bool drm_drv_uses_atomic_m
> > > intdrm_dev_register(struct drm_device *, unsigned long);
> > > void drm_dev_unregister(struct drm_device *);
> > > intdrm_getpciinfo(struct drm_device *, void *, struct drm_file *);
> > > +const struct drm_pcidev*drm_find_description(int, int,
> > > +const struct drm_pcidev *);
> > >
> > > #endif
> > > Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
> > > ===
> > > RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c,v
> > > retrieving revision 1.3
> > > diff -u -p -r1.3 amdgpu_kms.c
> > > --- sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 4 Jul 2019 03:39:07
> -
> > > 1.3
> > > +++ sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 2 Aug 2019 03:35:35
> -
> > > @@ -1337,10 +1337,23 @@ int amdgpu_debugfs_firmware_init(struct
> > > int
> > > amdgpu_probe(struct device *parent, void *match, void *aux)
> > > {
> > > + struct pci_attach_args *pa = aux;
> > > + const struct drm_pcidev *id_entry;
> > > + unsigned long flags = 0;
> > > +
> > > if (amdgpu_fatal_error)
> > > return 0;
> > > - if (drm_pciprobe(aux, amdgpu_pciidlist))
> > > - return 20;
> > > +
> > > + id_entry = drm_find_description(PCI_VENDOR(pa->pa_id),
> > > + PCI_PRODUCT(pa->pa_id), amdgpu_pciidlist);
> > > + if (id_entry != NULL) {
> > > + flags = id_entry->driver_data;
> > > + if (flags & AMD_EXP_HW_SUPPORT)
> > > + return 0;
> > > + else
> > > + return 20;
> > > + }
> > > +
> > > return 0;
> > > }
> > >
> > >
> > >
>
Re: AMDGPU in current issue
Hey,
I’ve been trying to write a patch to get vega 20 working, but due to a
screw up on my end I lost the progress I’d made. Before I start over again,
I was wondering if you had any advice on how to do it? Before, I was trying
to more or less just port the vega 20 hwmgr files in from FreeBSD drm next
which is at linux drm 5.0 as well as the other files which seemed to
mention Vega 20 or seemed to be needed to compile. I wasn’t having much
luck as you can imagine, and currently I’m still in university so my
experience with kernel patching isn’t fantastic, I was wondering if you
might have any advice where to begin if I’m having to start from scratch?
Best regards,
Charlie Burnett
On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote:
> On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> > Hey-
> > I'd been messing around with the AMDGPU on current (which I'm aware is
> very
> > experimental) and had very few issues with it using a Vega 56 GPU. I
> > recently swapped to another Vega GPU (Radeon VII) and have issues with
> the
> > display not showing anything. Still boots fine, in that I can still enter
> > commands (i.e. reboot) so it has to be a display issue. I tried searching
> > for the diff where the firmware was added which I'm certain I saw (for
> Vega
> > 20) but can't seem to find it in the commit history. Anyone have a fix
> for
> > it, and if not, who should I talk to if I wanted to help get it working?
> I
> > saw most of the AMDGPU commits have been by @jonathangray if he would be
> > the best option.
> > Thanks!
>
> vega20 firmware was added when ports/sysutils/firmware/amdgpu was
> updated to 20190312.
>
> vega20 is marked as experimental in the version of drm we have, but we
> don't currently check the flag on probe like linux does.
>
> The following diff will prevent amdgpu from matching on devices
> in the amdgpu_pciidlist table with the AMD_EXP_HW_SUPPORT flag
> (currently these are all vega20 ids).
>
> Index: sys/dev/pci/drm/include/drm/drm_drv.h
> ===
> RCS file: /cvs/src/sys/dev/pci/drm/include/drm/drm_drv.h,v
> retrieving revision 1.2
> diff -u -p -r1.2 drm_drv.h
> --- sys/dev/pci/drm/include/drm/drm_drv.h 25 Jul 2019 05:48:16
> - 1.2
> +++ sys/dev/pci/drm/include/drm/drm_drv.h 2 Aug 2019 03:29:58 -
> @@ -291,5 +291,7 @@ static inline bool drm_drv_uses_atomic_m
> intdrm_dev_register(struct drm_device *, unsigned long);
> void drm_dev_unregister(struct drm_device *);
> intdrm_getpciinfo(struct drm_device *, void *, struct drm_file *);
> +const struct drm_pcidev*drm_find_description(int, int,
> +const struct drm_pcidev *);
>
> #endif
> Index: sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c
> ===
> RCS file: /cvs/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c,v
> retrieving revision 1.3
> diff -u -p -r1.3 amdgpu_kms.c
> --- sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 4 Jul 2019 03:39:07 -
> 1.3
> +++ sys/dev/pci/drm/amd/amdgpu/amdgpu_kms.c 2 Aug 2019 03:35:35 -
> @@ -1337,10 +1337,23 @@ int amdgpu_debugfs_firmware_init(struct
> int
> amdgpu_probe(struct device *parent, void *match, void *aux)
> {
> + struct pci_attach_args *pa = aux;
> + const struct drm_pcidev *id_entry;
> + unsigned long flags = 0;
> +
> if (amdgpu_fatal_error)
> return 0;
> - if (drm_pciprobe(aux, amdgpu_pciidlist))
> - return 20;
> +
> + id_entry = drm_find_description(PCI_VENDOR(pa->pa_id),
> + PCI_PRODUCT(pa->pa_id), amdgpu_pciidlist);
> + if (id_entry != NULL) {
> + flags = id_entry->driver_data;
> + if (flags & AMD_EXP_HW_SUPPORT)
> + return 0;
> + else
> + return 20;
> + }
> +
> return 0;
> }
>
>
>
Re: AMDGPU in current issue
My apologies for bothering the mailing list once more-
I found the relevant commit for this in the linux git history, and found
the relevant changes. I added those changes locally on my machine, however
when I compile I get the following:
ld -T ld.script -X --warn-common -nopie -o bsd ${SYSTEM_HEAD} vers.o ${OBJS}
ld: error: undefined symbol: psp_v11_0_set_psp_funcs
>>> referenced by amdgpu_psp.c:62
(/usr/src/sys/dev/pci/drm/amd/amdgpu/amdgpu_psp.c:62)
>>> amdgpu_psp.o:(psp_sw_init)
ld: error: undefined symbol: vega20_smu_funcs
>>> referenced by hwmgr.c:164
(/usr/src/sys/dev/pci/drm/amd/powerplay/hwmgr/hwmgr.c:164)
>>> hwmgr.o:(hwmgr_early_init)
ld: error: undefined symbol: vega20_hwmgr_init
>>> referenced by hwmgr.c:165
(/usr/src/sys/dev/pci/drm/amd/powerplay/hwmgr/hwmgr.c:165)
>>> hwmgr.o:(hwmgr_early_init)
ld: error: undefined symbol: nbio_v7_4_funcs
>>> referenced by soc15.c:501
(/usr/src/sys/dev/pci/drm/amd/amdgpu/soc15.c:501)
>>> soc15.o:(soc15_set_ip_blocks)
ld: error: undefined symbol: nbio_v7_4_funcs
>>> referenced by soc15.c:501
(/usr/src/sys/dev/pci/drm/amd/amdgpu/soc15.c:501)
>>> soc15.o:(soc15_set_ip_blocks)
*** Error 1 in /usr/src/sys/arch/amd64/compile/GENERIC.MP (Makefile:1426
'bsd': @echo ld -T ld.script -X --warn-common -nopie -o bsd '${SYST...)
>From what I can tell, these all mention functions added in new files added
from the linux drm... is there anything in particular I need to do to make
sure the compiler picks up the relevant files, or maybe something to the
Makefile? I can post a diff of what I've done so far if that would be
useful.
Thanks again for all the help.
On Wed, Sep 4, 2019 at 9:44 AM Jonathan Gray wrote:
> Look for individual post 4.19 linux commits that are relevant.
> We have in the past taken small patches to enable more
> generations of hardware.
>
> On Wed, Sep 04, 2019 at 08:11:24AM -0500, Charlie Burnett wrote:
> > Hey,
> > I???ve been trying to write a patch to get vega 20 working, but due to a
> > screw up on my end I lost the progress I???d made. Before I start over
> again,
> > I was wondering if you had any advice on how to do it? Before, I was
> trying
> > to more or less just port the vega 20 hwmgr files in from FreeBSD drm
> next
> > which is at linux drm 5.0 as well as the other files which seemed to
> > mention Vega 20 or seemed to be needed to compile. I wasn???t having much
> > luck as you can imagine, and currently I???m still in university so my
> > experience with kernel patching isn???t fantastic, I was wondering if you
> > might have any advice where to begin if I???m having to start from
> scratch?
> > Best regards,
> > Charlie Burnett
> >
> > On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote:
> >
> > > On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote:
> > > > Hey-
> > > > I'd been messing around with the AMDGPU on current (which I'm aware
> is
> > > very
> > > > experimental) and had very few issues with it using a Vega 56 GPU. I
> > > > recently swapped to another Vega GPU (Radeon VII) and have issues
> with
> > > the
> > > > display not showing anything. Still boots fine, in that I can still
> enter
> > > > commands (i.e. reboot) so it has to be a display issue. I tried
> searching
> > > > for the diff where the firmware was added which I'm certain I saw
> (for
> > > Vega
> > > > 20) but can't seem to find it in the commit history. Anyone have a
> fix
> > > for
> > > > it, and if not, who should I talk to if I wanted to help get it
> working?
> > > I
> > > > saw most of the AMDGPU commits have been by @jonathangray if he
> would be
> > > > the best option.
> > > > Thanks!
> > >
> > > vega20 firmware was added when ports/sysutils/firmware/amdgpu was
> > > updated to 20190312.
> > >
> > > vega20 is marked as experimental in the version of drm we have, but we
> > > don't currently check the flag on probe like linux does.
> > >
> > > The following diff will prevent amdgpu from matching on devices
> > > in the amdgpu_pciidlist table with the AMD_EXP_HW_SUPPORT flag
> > > (currently these are all vega20 ids).
> > >
> > > Index: sys/dev/pci/drm/include/drm/drm_drv.h
> > > ===
> > > RCS file: /cvs/src/sys/dev/pci/drm/include/drm/drm_drv.h,v
> > > retrieving revision 1.2
> > > diff -u -p -r1.2 drm_drv.h
> > > --- sys/
Re: AMDGPU in current issue
Hey, apologies to continually bother you with this, but I've gotten a driver that compiles and detects the card... however it seems to be having powerplay table issues, I was wondering if this was ever an issue when initially porting, and if so how'd you go about fixing it? Leaving the powerplay untouched and only altering the amdgpu subdirectory results in this error in the following error in dmesg: initializing kernel modesetting (VEGA20 0x1002:0x66AF 0x1002:0x081E 0xC1). amdgpu_device_resize_fb_bar: stub amdgpu: [powerplay] smc start failed amdgpu: [powerplay] powerplay hw init failed [drm] *ERROR* hw_init of IP block failed -22 drm:pid0:amdgpu_device_init *ERROR* amdgpu_device_ip_init failed drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init efifb0 at mainbus0: 3440x1440, 32bpp wsdisplay0 at efifb0 mux 1: console (std, vt100 emulation), using wskbd0 wskbd1: connecting to wsdisplay0 wskbd2: connecting to wsdisplay0 wskbd3: connecting to wsdisplay0 wskbd4: connecting to wsdisplay0 wsdisplay0: screen 1-5 added (std, vt100 emulation) Compiling the kernel with the additional powerplay changes relevant to vega 20 results in a similar message, although instead of the "hw_init" having issues, it complains about "Unmatch PPTable version, vbios update may be needed". I'd post a diff, but trying to generate a diff through cvs isn't picking up the files I've added even with the --new-file option, but I'm rather unfamiliar with cvs/diff in general so it's probable I screwed the pooch on that part somehow. Any help would be very much appreciated, and thanks for the help you've given already! On Wed, Sep 4, 2019 at 8:04 PM Jonathan Gray wrote: > amdgpu tracks the linux-4.19.y (lts) branch of linux-stable > currently this is 4.19.69 > > On Wed, Sep 04, 2019 at 10:28:51AM -0500, Charlie Burnett wrote: > > Thanks for the advice! > > Do you happen to have a link to the commit amdgpu is at currently? > > > > On Wed, Sep 4, 2019 at 9:44 AM Jonathan Gray wrote: > > > > > Look for individual post 4.19 linux commits that are relevant. > > > We have in the past taken small patches to enable more > > > generations of hardware. > > > > > > On Wed, Sep 04, 2019 at 08:11:24AM -0500, Charlie Burnett wrote: > > > > Hey, > > > > I???ve been trying to write a patch to get vega 20 working, but due > to a > > > > screw up on my end I lost the progress I???d made. Before I start > over > > > again, > > > > I was wondering if you had any advice on how to do it? Before, I was > > > trying > > > > to more or less just port the vega 20 hwmgr files in from FreeBSD drm > > > next > > > > which is at linux drm 5.0 as well as the other files which seemed to > > > > mention Vega 20 or seemed to be needed to compile. I wasn???t having > much > > > > luck as you can imagine, and currently I???m still in university so > my > > > > experience with kernel patching isn???t fantastic, I was wondering > if you > > > > might have any advice where to begin if I???m having to start from > > > scratch? > > > > Best regards, > > > > Charlie Burnett > > > > > > > > On Thu, Aug 1, 2019 at 11:06 PM Jonathan Gray wrote: > > > > > > > > > On Fri, Aug 02, 2019 at 03:11:54AM -0500, Charlie Burnett wrote: > > > > > > Hey- > > > > > > I'd been messing around with the AMDGPU on current (which I'm > aware > > > is > > > > > very > > > > > > experimental) and had very few issues with it using a Vega 56 > GPU. I > > > > > > recently swapped to another Vega GPU (Radeon VII) and have issues > > > with > > > > > the > > > > > > display not showing anything. Still boots fine, in that I can > still > > > enter > > > > > > commands (i.e. reboot) so it has to be a display issue. I tried > > > searching > > > > > > for the diff where the firmware was added which I'm certain I saw > > > (for > > > > > Vega > > > > > > 20) but can't seem to find it in the commit history. Anyone have > a > > > fix > > > > > for > > > > > > it, and if not, who should I talk to if I wanted to help get it > > > working? > > > > > I > > > > > > saw most of the AMDGPU commits have been by @jonathangray if he > > > would be > > > > > > the best option. > > > > > > Thanks! > > > > > > > > > > vega20 firmware was added when ports/sysutils/firmw
Re: Desktop full text search
Try pdfgrep and catdoc in ports/pkg for documents I’d say, you could probably rig up a simple shell script to do it automatically... unfortunately don’t know what program(s) would be faster than grep? On Wed, Sep 18, 2019 at 3:26 PM Oriol Demaria wrote: > Exactly I do the same... but is falling short or too slow. :) > > --- > Oriol Demaria > 2FFED630C16E4FF8 > > On 18/09/2019 17:01, Charlie Burnett wrote: > > I use Gnome as a DE but I still just do it through a terminal- > > grep -R * “foo” > > from whatever directory I wanna find the text in, replace foo with the > > text > > you want. > > > > On Wed, Sep 18, 2019 at 10:38 AM Oriol Demaria > > wrote: > > > >> So finding some code between large amounts of repos can be tricky. I > >> don't use Gnome or KDE so I was wondering what do people use for this. > >> Been looking at the ports and I see Xapian and others. Any advice on > >> a nice setup? > >> > >> Regards, > >> > >> -- > >> Oriol Demaria > >> 2FFED630C16E4FF8 > >> > >> >
AMDGPU in current issue
Hey- I'd been messing around with the AMDGPU on current (which I'm aware is very experimental) and had very few issues with it using a Vega 56 GPU. I recently swapped to another Vega GPU (Radeon VII) and have issues with the display not showing anything. Still boots fine, in that I can still enter commands (i.e. reboot) so it has to be a display issue. I tried searching for the diff where the firmware was added which I'm certain I saw (for Vega 20) but can't seem to find it in the commit history. Anyone have a fix for it, and if not, who should I talk to if I wanted to help get it working? I saw most of the AMDGPU commits have been by @jonathangray if he would be the best option. Thanks!
UEFI Issue
Hey, I'm looking to get OpenBSD working in UEFI only mode on newer Thinkpad X1 devices, because for whatever reason it hangs when loading into memory without CSM enabled, and some of the X1 devices no longer have a CSM option. Does anyone have a fix, or advice on where I would start looking if I was going to patch it myself?
Re: UEFI Issue
Yeahhh... I've just decided to return it and get a X1 6th gen and just get a supported wacom usb drawing tablet for notes, no OpenBSD is kind of a dealbreaker for me. Also keyboard on it was screwy and didn't work half the time even with Windows so not the best machine. And Legacy mode was also a no-go, as there was no legacy mode and any and all CSM support had been disabled, which is rather frustrating. Also, tried booting through rEFInd, grub, took the hard drive out and installed it on a different machine, none worked sadly. Oddly enough, certain Linux distros seemed to have a similar issue (namely the most recent Gentoo minimal iso) so I'm guessing there was something really weird with the EFI on it. I've got a few old/cheap machines with issues along the same lines, I'll try to figure out what the issue was if I can. I appreciate all y'all's help though! On Fri, Jul 19, 2019 at 8:14 AM Kristjan Komloši wrote: > On Tue, 2019-07-16 at 18:32 +0000, Charlie Burnett wrote: > > Hey, I'm looking to get OpenBSD working in UEFI only mode on newer > > Thinkpad > > X1 devices, because for whatever reason it hangs when loading into > > memory > > without CSM enabled, and some of the X1 devices no longer have a CSM > > option. Does anyone have a fix, or advice on where I would start > > looking if > > I was going to patch it myself? > New Lenovo laptops are getting kinda infamous for their comically bad > UEFI implementations. They hardly boot anything but Windows. You may be > on a blind path there. > > Try disabling secure boot if you haven't done so already, and try > chainloading OpenBSD through a boot manager like rEFInd (I've been > booting OpenBSD with it for a long time, albeit with CSM support). > > -- > Kristjan Komloši > Mail: kristjan.koml...@gmail.com > Tel: +386 31 679 339 > >
Anyone gotten touchscreen on Thinkpad X1 working?
Hey all, I recently picked up an X1 carbon 6th gen that happened to have the touchscreen option on it. Everything works great otherwise, but I don't seem to have any luck on the touchscreen issue. I don't see anything relevant in dmesg either, shown below. Any ideas? OpenBSD 6.6-current (GENERIC.MP) #618: Thu Jan 23 23:58:32 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 17031843840 (16242MB) avail mem = 16503181312 (15738MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x5a63b000 (62 entries) bios0: vendor LENOVO version "N23ET66W (1.41 )" date 09/02/2019 bios0: LENOVO 20KGSCVN00 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SSDT SSDT TPM2 UEFI SSDT SSDT HPET APIC MCFG ECDT SSDT SSDT BOOT BATB SLIC SSDT SSDT SSDT LPIT WSMT SSDT SSDT SSDT DBGP DBG2 MSDM NHLT ASF! FPDT UEFI WPBT acpi0: wakeup devices GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) RP06(S4) PXSX(S4) RP07(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpihpet0 at acpi0: 2399 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1790.09 MHz, 06-8e-0a 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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1795.83 MHz, 06-8e-0a 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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1795.83 MHz, 06-8e-0a 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,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1795.83 MHz, 06-8e-0a 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,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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz, 1795.82 MHz, 06-8e-0a cpu4: 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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz,
Re: wpa_supplicant error
Well, I’m a dumbass. I just needed to swap out “psk” for “password” in my file. All working now. On Tue, Feb 4, 2020 at 4:59 PM Charlie Burnett wrote: > Well, I at least have a tangible error now. Observing through wpa_cli, I > get the following: > <3>CTRL-EVENT-EAP-STATUS status=‘eap parameter needed’ parameter=‘PASSWORD’ > <3>CTRL-REQ-PASSWORD-0: Password needed for SSID eduroam > <3>CTRL-EVENT-EAP-FAILURE EAP authentication failed > Authentication with $BSSID timed out. > > Out of curiosity I switched it to WPA2-PSK and it says it successfully > associated, however I can’t ping anything and trying to use dhclient just > results in it timing out/sleeping. > > I know my password is correct as well > > On Mon, Feb 3, 2020 at 4:42 AM Raf Czlonka wrote: > >> On Sun, Feb 02, 2020 at 09:42:52PM GMT, Charlie Burnett wrote: >> > Hey @misc, >> > I've used OpenBSD on my desktop and server for a while, however they >> both >> > have an Ethernet connection. I recently got my hands on a thinkpad x1 >> 6th >> > gen in order to ensure compatibility with OpenBSD. I can connect fine >> via >> > the /etc/hostname.if with /etc/netstart, however I need to be able to >> > connect to eduroam for class. I was using linux on my past laptop, >> however >> > I connected through wpa_supplicant on it. I copied my >> wpa_supplicant.conf >> > over, however whenever I try to connect to a network I get hung up in >> the >> > same spot. The conf works fine on linux, so the credentials are correct. >> > I've also ensured the interface was up with "doas ifconfig iwm0 up" >> Here's >> > the output from attempting to connect with "doas wpa_supplicant -i iwm0 >> -c >> > /etc/wpa_supplicant.conf -D openbsd -dd": >> > wpa_supplicant v2.9 >> > Successfully initialized wpa_supplicant >> > Initializing interface 'iwm0' conf '/etc/wpa_supplicant.conf' driver >> > 'openbsd' ctrl_interface 'N/A' bridge 'N/A' >> > Configuration file '/etc/wpa_supplicant.conf' -> >> '/etc/wpa_supplicant.conf' >> > Reading configuration file '/etc/wpa_supplicant.conf' >> > ctrl_interface='/var/run/wpa_supplicant' >> > ctrl_interface_group='wheel' >> > eapol_version=2 >> > ap_scan=1 >> > fast_reauth=1 >> > update_config=1 >> > Line: 11 - start of a new network block >> > ssid - hexdump_ascii(len=): HOME >> > key_mgmt: 0x2 >> > PSK - hexdump(len=): [REMOVED] >> > Line: 19 - start of a new network block >> > ssid - hexdump_ascii(len=7): eduroam >> > scan_ssid=1 (0x1) >> > key_mgmt: 0x1 >> > eap methods - hexdump(len=): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 >> 00 00 >> > phase2 - hexdump_ascii(len=): >> > 61 75 74 68 3d 4d 53 43 48 41 50 56 32auth=MSCHAPV2 >> > auth_alg: 0x1 >> > identity - hexdump_ascii(len=): >> > ca_cert - hexdump_ascii(len=): >> > 2f 65 74 63 2f 73 73 6c 2f 63 65 72 74 73 2f 41 /etc/ssl/certs/A >> > 64 64 54 72 75 73 74 5f 45 78 74 65 72 6e 61 6c ddTrust_External >> > 5f 52 6f 6f 74 2e 70 65 6d_Root.pem >> > password - hexdump_ascii(len=): [REMOVED] >> > Line: 32 - start of a new network block >> > ssid - hexdump_ascii(len=): HOME2 >> > PSK - hexdump(len=): [REMOVED] >> > Priority group 0 >> >id=0 ssid='HOME' >> >id=1 ssid='eduroam' >> >id=2 ssid='HOME2' >> > Add interface iwm0 to a new radio N/A >> > iwm0: Failed to attach pkt_type filter >> > iwm0: Own MAC address: 38:00:25:6c:76:6d >> > iwm0: RSN: flushing PMKID list in the driver >> > iwm0: Setting scan request: 0.10 sec >> > ENGINE: Loading builtin engines >> > ENGINE: Loading builtin engines >> > EAPOL: SUPP_PAE entering state DISCONNECTED >> > EAPOL: Supplicant port status: Unauthorized >> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE >> > EAPOL: SUPP_BE entering state INITIALIZE >> > EAP: EAP entering state DISABLED >> > ctrl_interface_group=0 (from group name 'wheel') >> > iwm0: Added interface iwm0 >> > iwm0: State: DISCONNECTED -> DISCONNECTED >> > iwm0: Using OpenBSD - overriding ap_scan configuration >> > EAPOL: disable timer tick >> > >> > Here is the output after sending a ctrl-C to the terminal: >> > ^Ciwm0: Removing interface iwm0 >> > iwm0: Request to deauthenticate - bssid=00:00:00:00:00:00 >> > pend
Process Isolation
Hey y'all, Sorry if this has been answered before but I couldn't find a satisfactory answer searching for it, and this is more of an academic question. So security focused Linux distros like Qubes go to extremes to compartmentalize/isolate any and all programs it can. FreeBSD has it's jail program which is seemingly the gold standard for process isolation when you can't be bothered to go to the extent Qubes does. I've been trying to read as much OpenBSD source as I can as I find some of the security tricks y'all've come up with damn interesting. I know that once upon a time we had sysjail, but nowadays we have just have chroot which most systems do. What is OpenBSD's solution to this? I'm sure I've read through it I just didn't realize the purpose. I apologize if this was a question I've somehow missed the answer to!
wpa_supplicant error
Hey @misc,
I've used OpenBSD on my desktop and server for a while, however they both
have an Ethernet connection. I recently got my hands on a thinkpad x1 6th
gen in order to ensure compatibility with OpenBSD. I can connect fine via
the /etc/hostname.if with /etc/netstart, however I need to be able to
connect to eduroam for class. I was using linux on my past laptop, however
I connected through wpa_supplicant on it. I copied my wpa_supplicant.conf
over, however whenever I try to connect to a network I get hung up in the
same spot. The conf works fine on linux, so the credentials are correct.
I've also ensured the interface was up with "doas ifconfig iwm0 up" Here's
the output from attempting to connect with "doas wpa_supplicant -i iwm0 -c
/etc/wpa_supplicant.conf -D openbsd -dd":
wpa_supplicant v2.9
Successfully initialized wpa_supplicant
Initializing interface 'iwm0' conf '/etc/wpa_supplicant.conf' driver
'openbsd' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant.conf' -> '/etc/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant.conf'
ctrl_interface='/var/run/wpa_supplicant'
ctrl_interface_group='wheel'
eapol_version=2
ap_scan=1
fast_reauth=1
update_config=1
Line: 11 - start of a new network block
ssid - hexdump_ascii(len=): HOME
key_mgmt: 0x2
PSK - hexdump(len=): [REMOVED]
Line: 19 - start of a new network block
ssid - hexdump_ascii(len=7): eduroam
scan_ssid=1 (0x1)
key_mgmt: 0x1
eap methods - hexdump(len=): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 00 00
phase2 - hexdump_ascii(len=):
61 75 74 68 3d 4d 53 43 48 41 50 56 32auth=MSCHAPV2
auth_alg: 0x1
identity - hexdump_ascii(len=):
ca_cert - hexdump_ascii(len=):
2f 65 74 63 2f 73 73 6c 2f 63 65 72 74 73 2f 41 /etc/ssl/certs/A
64 64 54 72 75 73 74 5f 45 78 74 65 72 6e 61 6c ddTrust_External
5f 52 6f 6f 74 2e 70 65 6d_Root.pem
password - hexdump_ascii(len=): [REMOVED]
Line: 32 - start of a new network block
ssid - hexdump_ascii(len=): HOME2
PSK - hexdump(len=): [REMOVED]
Priority group 0
id=0 ssid='HOME'
id=1 ssid='eduroam'
id=2 ssid='HOME2'
Add interface iwm0 to a new radio N/A
iwm0: Failed to attach pkt_type filter
iwm0: Own MAC address: 38:00:25:6c:76:6d
iwm0: RSN: flushing PMKID list in the driver
iwm0: Setting scan request: 0.10 sec
ENGINE: Loading builtin engines
ENGINE: Loading builtin engines
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: Supplicant port status: Unauthorized
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
ctrl_interface_group=0 (from group name 'wheel')
iwm0: Added interface iwm0
iwm0: State: DISCONNECTED -> DISCONNECTED
iwm0: Using OpenBSD - overriding ap_scan configuration
EAPOL: disable timer tick
Here is the output after sending a ctrl-C to the terminal:
^Ciwm0: Removing interface iwm0
iwm0: Request to deauthenticate - bssid=00:00:00:00:00:00
pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) state=DISCONNECTED
iwm0: State: DISCONNECTED -> DISCONNECTED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
iwm0: WPA: Clear old PMK and PTK
iwm0: Cancelling scan request
iwm0: Cancelling authentication timeout
Remove interface iwm0 from radio
Remove radio
iwm0: CTRL-EVENT-TERMINATING
And here's my wpa_supplicant.conf (with ssid's and psk's removed):
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
eapol_version=2
ap_scan=1
fast_reauth=1
update_config=1
network={
ssid="HOME"
psk=PASSWORD
}
# Eduroam
network={
ssid="eduroam"
scan_ssid=1
key_mgmt=WPA-EAP
eap=PEAP
phase2="auth=MSCHAPV2"
auth_alg=OPEN
identity="burne...@umn.edu"
ca_cert="/etc/ssl/certs/AddTrust_External_Root.pem"
password="Here I am, here I remain."
}
network={
ssid="HOME2"
psk=PASSWORD
}
Any help would be very much appreciated!
Re: wpa_supplicant error
Yep I've been using that for a while, however I don't believe it's possible
to connect to eduroam through hostname.if config files :/
On Sun, Feb 2, 2020 at 4:01 PM Edgar Pettijohn
wrote:
> Try without wpa_supplicant
>
> /etc/hostname.iwm0
> nwid yournwid wpakey yourwpakey
> dhcp
>
> sh /etc/netstart
>
> On Feb 2, 2020 3:42 PM, Charlie Burnett wrote:
> >
> > Hey @misc,
> > I've used OpenBSD on my desktop and server for a while, however they both
> > have an Ethernet connection. I recently got my hands on a thinkpad x1 6th
> > gen in order to ensure compatibility with OpenBSD. I can connect fine via
> > the /etc/hostname.if with /etc/netstart, however I need to be able to
> > connect to eduroam for class. I was using linux on my past laptop,
> however
> > I connected through wpa_supplicant on it. I copied my wpa_supplicant.conf
> > over, however whenever I try to connect to a network I get hung up in the
> > same spot. The conf works fine on linux, so the credentials are correct.
> > I've also ensured the interface was up with "doas ifconfig iwm0 up"
> Here's
> > the output from attempting to connect with "doas wpa_supplicant -i iwm0
> -c
> > /etc/wpa_supplicant.conf -D openbsd -dd":
> > wpa_supplicant v2.9
> > Successfully initialized wpa_supplicant
> > Initializing interface 'iwm0' conf '/etc/wpa_supplicant.conf' driver
> > 'openbsd' ctrl_interface 'N/A' bridge 'N/A'
> > Configuration file '/etc/wpa_supplicant.conf' ->
> '/etc/wpa_supplicant.conf'
> > Reading configuration file '/etc/wpa_supplicant.conf'
> > ctrl_interface='/var/run/wpa_supplicant'
> > ctrl_interface_group='wheel'
> > eapol_version=2
> > ap_scan=1
> > fast_reauth=1
> > update_config=1
> > Line: 11 - start of a new network block
> > ssid - hexdump_ascii(len=): HOME
> > key_mgmt: 0x2
> > PSK - hexdump(len=): [REMOVED]
> > Line: 19 - start of a new network block
> > ssid - hexdump_ascii(len=7): eduroam
> > scan_ssid=1 (0x1)
> > key_mgmt: 0x1
> > eap methods - hexdump(len=): 00 00 00 00 19 00 00 00 00 00 00 00 00 00
> 00 00
> > phase2 - hexdump_ascii(len=):
> > 61 75 74 68 3d 4d 53 43 48 41 50 56 32auth=MSCHAPV2
> > auth_alg: 0x1
> > identity - hexdump_ascii(len=):
> > ca_cert - hexdump_ascii(len=):
> > 2f 65 74 63 2f 73 73 6c 2f 63 65 72 74 73 2f 41 /etc/ssl/certs/A
> > 64 64 54 72 75 73 74 5f 45 78 74 65 72 6e 61 6c ddTrust_External
> > 5f 52 6f 6f 74 2e 70 65 6d_Root.pem
> > password - hexdump_ascii(len=): [REMOVED]
> > Line: 32 - start of a new network block
> > ssid - hexdump_ascii(len=): HOME2
> > PSK - hexdump(len=): [REMOVED]
> > Priority group 0
> >id=0 ssid='HOME'
> >id=1 ssid='eduroam'
> >id=2 ssid='HOME2'
> > Add interface iwm0 to a new radio N/A
> > iwm0: Failed to attach pkt_type filter
> > iwm0: Own MAC address: 38:00:25:6c:76:6d
> > iwm0: RSN: flushing PMKID list in the driver
> > iwm0: Setting scan request: 0.10 sec
> > ENGINE: Loading builtin engines
> > ENGINE: Loading builtin engines
> > EAPOL: SUPP_PAE entering state DISCONNECTED
> > EAPOL: Supplicant port status: Unauthorized
> > EAPOL: KEY_RX entering state NO_KEY_RECEIVE
> > EAPOL: SUPP_BE entering state INITIALIZE
> > EAP: EAP entering state DISABLED
> > ctrl_interface_group=0 (from group name 'wheel')
> > iwm0: Added interface iwm0
> > iwm0: State: DISCONNECTED -> DISCONNECTED
> > iwm0: Using OpenBSD - overriding ap_scan configuration
> > EAPOL: disable timer tick
> >
> > Here is the output after sending a ctrl-C to the terminal:
> > ^Ciwm0: Removing interface iwm0
> > iwm0: Request to deauthenticate - bssid=00:00:00:00:00:00
> > pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING)
> state=DISCONNECTED
> > iwm0: State: DISCONNECTED -> DISCONNECTED
> > EAPOL: External notification - portEnabled=0
> > EAPOL: External notification - portValid=0
> > iwm0: WPA: Clear old PMK and PTK
> > iwm0: Cancelling scan request
> > iwm0: Cancelling authentication timeout
> > Remove interface iwm0 from radio
> > Remove radio
> > iwm0: CTRL-EVENT-TERMINATING
> >
> >
> > And here's my wpa_supplicant.conf (with ssid's and psk's removed):
> > ctrl_interface=/var/run/wpa_supplicant
> > ctrl_interface_group=wheel
> > eapol_version=2
> > ap_scan=1
> > fast_reauth=1
> > update_config=1
> >
> > network={
> > ssid="HOME"
> > psk=PASSWORD
> > }
> >
> > # Eduroam
> > network={
> > ssid="eduroam"
> > scan_ssid=1
> > key_mgmt=WPA-EAP
> > eap=PEAP
> > phase2="auth=MSCHAPV2"
> > auth_alg=OPEN
> > identity="burne...@umn.edu"
> > ca_cert="/etc/ssl/certs/AddTrust_External_Root.pem"
> > password="Here I am, here I remain."
> > }
> >
> > network={
> > ssid="HOME2"
> > psk=PASSWORD
> > }
> >
> > Any help would be very much appreciated!
>
Re: wpa_supplicant error
Well, I at least have a tangible error now. Observing through wpa_cli, I get the following: <3>CTRL-EVENT-EAP-STATUS status=‘eap parameter needed’ parameter=‘PASSWORD’ <3>CTRL-REQ-PASSWORD-0: Password needed for SSID eduroam <3>CTRL-EVENT-EAP-FAILURE EAP authentication failed Authentication with $BSSID timed out. Out of curiosity I switched it to WPA2-PSK and it says it successfully associated, however I can’t ping anything and trying to use dhclient just results in it timing out/sleeping. I know my password is correct as well On Mon, Feb 3, 2020 at 4:42 AM Raf Czlonka wrote: > On Sun, Feb 02, 2020 at 09:42:52PM GMT, Charlie Burnett wrote: > > Hey @misc, > > I've used OpenBSD on my desktop and server for a while, however they both > > have an Ethernet connection. I recently got my hands on a thinkpad x1 6th > > gen in order to ensure compatibility with OpenBSD. I can connect fine via > > the /etc/hostname.if with /etc/netstart, however I need to be able to > > connect to eduroam for class. I was using linux on my past laptop, > however > > I connected through wpa_supplicant on it. I copied my wpa_supplicant.conf > > over, however whenever I try to connect to a network I get hung up in the > > same spot. The conf works fine on linux, so the credentials are correct. > > I've also ensured the interface was up with "doas ifconfig iwm0 up" > Here's > > the output from attempting to connect with "doas wpa_supplicant -i iwm0 > -c > > /etc/wpa_supplicant.conf -D openbsd -dd": > > wpa_supplicant v2.9 > > Successfully initialized wpa_supplicant > > Initializing interface 'iwm0' conf '/etc/wpa_supplicant.conf' driver > > 'openbsd' ctrl_interface 'N/A' bridge 'N/A' > > Configuration file '/etc/wpa_supplicant.conf' -> > '/etc/wpa_supplicant.conf' > > Reading configuration file '/etc/wpa_supplicant.conf' > > ctrl_interface='/var/run/wpa_supplicant' > > ctrl_interface_group='wheel' > > eapol_version=2 > > ap_scan=1 > > fast_reauth=1 > > update_config=1 > > Line: 11 - start of a new network block > > ssid - hexdump_ascii(len=): HOME > > key_mgmt: 0x2 > > PSK - hexdump(len=): [REMOVED] > > Line: 19 - start of a new network block > > ssid - hexdump_ascii(len=7): eduroam > > scan_ssid=1 (0x1) > > key_mgmt: 0x1 > > eap methods - hexdump(len=): 00 00 00 00 19 00 00 00 00 00 00 00 00 00 > 00 00 > > phase2 - hexdump_ascii(len=): > > 61 75 74 68 3d 4d 53 43 48 41 50 56 32auth=MSCHAPV2 > > auth_alg: 0x1 > > identity - hexdump_ascii(len=): > > ca_cert - hexdump_ascii(len=): > > 2f 65 74 63 2f 73 73 6c 2f 63 65 72 74 73 2f 41 /etc/ssl/certs/A > > 64 64 54 72 75 73 74 5f 45 78 74 65 72 6e 61 6c ddTrust_External > > 5f 52 6f 6f 74 2e 70 65 6d_Root.pem > > password - hexdump_ascii(len=): [REMOVED] > > Line: 32 - start of a new network block > > ssid - hexdump_ascii(len=): HOME2 > > PSK - hexdump(len=): [REMOVED] > > Priority group 0 > >id=0 ssid='HOME' > >id=1 ssid='eduroam' > >id=2 ssid='HOME2' > > Add interface iwm0 to a new radio N/A > > iwm0: Failed to attach pkt_type filter > > iwm0: Own MAC address: 38:00:25:6c:76:6d > > iwm0: RSN: flushing PMKID list in the driver > > iwm0: Setting scan request: 0.10 sec > > ENGINE: Loading builtin engines > > ENGINE: Loading builtin engines > > EAPOL: SUPP_PAE entering state DISCONNECTED > > EAPOL: Supplicant port status: Unauthorized > > EAPOL: KEY_RX entering state NO_KEY_RECEIVE > > EAPOL: SUPP_BE entering state INITIALIZE > > EAP: EAP entering state DISABLED > > ctrl_interface_group=0 (from group name 'wheel') > > iwm0: Added interface iwm0 > > iwm0: State: DISCONNECTED -> DISCONNECTED > > iwm0: Using OpenBSD - overriding ap_scan configuration > > EAPOL: disable timer tick > > > > Here is the output after sending a ctrl-C to the terminal: > > ^Ciwm0: Removing interface iwm0 > > iwm0: Request to deauthenticate - bssid=00:00:00:00:00:00 > > pending_bssid=00:00:00:00:00:00 reason=3 (DEAUTH_LEAVING) > state=DISCONNECTED > > iwm0: State: DISCONNECTED -> DISCONNECTED > > EAPOL: External notification - portEnabled=0 > > EAPOL: External notification - portValid=0 > > iwm0: WPA: Clear old PMK and PTK > > iwm0: Cancelling scan request > > iwm0: Cancelling authentication timeout > > Remove interface iwm0 from radio > > Remove radio > > iwm0: CTRL-EVENT-TERMINATING > > > > Hi Charlie, > > eduroam works just fine on OpenBSD with wpa_supplic
Trouble recognizing Surface Book Keyboard
Hey y’all, I recently got a surface book for a real good price since I was due for an upgrade, and since I usually run OpenBSD on my daily machine I went ahead and installed it. I’m aware that the wireless card isn’t supported, but I’ve got a usb one that works fine. During the installation it had no trouble using the keyboard. After the reboot however the keyboard and trackpad were non responsive. I can use a usb keyboard while booted but can’t figure out why it won’t pick up the actual keyboard. Any help would be greatly appreciated! Attached the dmesg below. OpenBSD 6.6-current (RAMDISK_CD) #542: Fri Dec 27 08:43:35 MST 2019 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 8495235072 (8101MB) avail mem = 8233758720 (7852MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.1 @ 0x8be35000 (15 entries) bios0: vendor Microsoft Corporation version "91.2706.768" date 04/18/2019 bios0: Microsoft Corporation Surface Book acpi0 at bios0: ACPI 5.0 acpi0: tables DSDT FACP SSDT TPM2 MSDM SSDT HPET APIC MCFG LPIT SSDT SSDT SSDT DMAR NHLT FPDT WSMT BGRT acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-6300U CPU @ 2.40GHz, 2295.32 MHz, 06-4e-03 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,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, 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, 120 pins acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (RP01) acpiprt2 at acpi0: bus -1 (RP02) acpiprt3 at acpi0: bus -1 (RP03) acpiprt4 at acpi0: bus -1 (RP04) acpiprt5 at acpi0: bus 1 (RP05) acpiprt6 at acpi0: bus -1 (RP06) acpiprt7 at acpi0: bus -1 (RP07) acpiprt8 at acpi0: bus -1 (RP08) acpiprt9 at acpi0: bus 2 (RP09) acpiprt10 at acpi0: bus -1 (RP10) acpiprt11 at acpi0: bus -1 (RP11) acpiprt12 at acpi0: bus 3 (RP12) acpiprt13 at acpi0: bus -1 (RP13) acpiprt14 at acpi0: bus -1 (RP14) acpiprt15 at acpi0: bus -1 (RP15) acpiprt16 at acpi0: bus -1 (RP16) acpiprt17 at acpi0: bus -1 (RP17) acpiprt18 at acpi0: bus -1 (RP18) acpiprt19 at acpi0: bus -1 (RP19) acpiprt20 at acpi0: bus -1 (RP20) acpiprt21 at acpi0: bus -1 (RP21) acpiprt22 at acpi0: bus -1 (RP22) acpiprt23 at acpi0: bus -1 (RP23) acpiprt24 at acpi0: bus -1 (RP24) acpiec0 at acpi0 acpicpu at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpitz at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured acpipwrres at acpi0 not configured "PNP0A08" at acpi0 not configured "ACPI0003" at acpi0 not configured "PNP0C0A" at acpi0 not configured "PNP0C0A" at acpi0 not configured "MSHW0029" at acpi0 not configured "MSHW0040" at acpi0 not configured acpicmos0 at acpi0 "INT344B" at acpi0 not configured "MSHW0030" at acpi0 not configured "MAX34407" at acpi0 not configured "INT3472" at acpi0 not configured "INT33BE" at acpi0 not configured "INT3472" at acpi0 not configured "INT347A" at acpi0 not configured "INT3472" at acpi0 not configured "INT347E" at acpi0 not configured "MSHW0085" at acpi0 not configured "MSHW0005" at acpi0 not configured "MSHW0080" at acpi0 not configured "MSHW0036" at acpi0 not configured "MSHW0041" at acpi0 not configured "MSHW0042" at acpi0 not configured "MSHW0045" at acpi0 not configured "MSHW0076" at acpi0 not configured "INT33A1" at acpi0 not configured "PNP0C0D" at acpi0 not configured "IFX0562" at acpi0 not configured cpu0: using VERW MDS workaround pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel Core 6G Host" rev 0x08 "Intel HD Graphics 520" rev 0x07 at pci0 dev 2 function 0 not configured vendor "Intel", unknown product 0x1919 (class multimedia subclass miscellaneous, rev 0x01) at pci0 dev 5 function 0 not configured "Intel Core GMM" rev 0x00 at pci0 dev 8 function 0 not configured xhci0 at pci0 dev 20 function 0 "Intel 100 Series xHCI" rev 0x21: msi, xHCI 1.0 usb0 at xhci0: USB revision 3.0 uhub0 at usb0 configuration
Re: Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd
Ryzen 3 Vega is based on the Raven architecture, which has worked for me on machines before so I'm not sure you'd have much issue with it, I'd imagine it'd just work "out of the box". Wireless is up in the air, since the card didn't seem to be listed on the specifications online. On Mon, May 25, 2020 at 10:49 AM flint pyrite wrote: > You probably should check for wifi compatibility. > > On Sun, May 24, 2020 at 9:50 PM Digital Crow > wrote: > > > Help, i want to ask if my Asus Vivobook Ryzen 3 , Vega 3 can run openbsd > > I have problems with freebsd i can't run xorg it has a problem with efi > > framebuffer and amdgpu driver. > > It seems that this laptop can boot only efi partitions there's no setting > > on bios about csm or anything else related to it. > > Is it possible openbsd would work ? > > Also is the process the same as freebsd ? > > I need to install drm-kmod and add kld_list amdgpu on rc.conf > > The openbsd installer create efi boot partition ? > > I think this laptop can boot only efi partitions > > >
AMDGPU
Hi, Wasn’t sure who to tell this to, but with Vega 20 hardware under -current, there is an issue with the firmware, where it cannot load. Manually installing the latest amdgpu firmware from kernel.org fixes this seemingly. There's also an issue that I've been unable to figure out for a while here as well, in that undergoing a CPU intensive task will freeze up the entire system. Disabling all power management options and setting the amdgpu_vm_update_mode to 3 lessens the occurrence of this, and using an HDMI connection instead of a DisplayPort with said modifications seemingly eliminates it. Just switching amdgpu_vm_update_mode to 3 without anything else leads to issues, in which when launching X in which only a small square of seemingly random pixels are displayed. Using a vanilla kernel, only "Waiting for fences timed out!" appears. However, turning on amdgpu_debug_vm in amdgpu_drv.c will output quite a few DRM errors for "gmc_v9_0_process_interrupt", sometimes in the tens of thousands. Any hang ups require a hard reboot. With amdgpu_vm_update_mode set to 3, the crash occurs differently in that whichever windows are using a bunch of GPU/CPU time turn a lime green color. They're completely functional at first, however if I keep putting heavy loads on both the screen becomes pixelated on any changed pixels for those windows. I have a huge amount of logs for these, however from a couple weeks of trying to fix it myself they didn't offer much beyond what was stated in this email. Best regards, Charlie
Re: AMDGPU
For sure, whatever helps! Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sdma_v4_0: Failed to load firmware "amdgpu/vega20_sdma.bin" Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load sdma firmware! Jun 27 18:58:21 tabr /bsd: drm:pid0:psp_v11_0_init_microcode *ERROR* psp v11.0: Failed to load firmware "amdgpu/vega20_sos.bin" Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* Failed to load psp firmware! Jun 27 18:58:21 tabr /bsd: [drm] *ERROR* sw_init of IP block failed -2 Jun 27 18:58:21 tabr /bsd: drm:pid0:amdgpu_device_init *ERROR* amdgpu_device_ip_init failed Jun 27 18:58:21 tabr /bsd: drm:pid0:amdgpu_attachhook *ERROR* Fatal error during GPU init That's with the old firmware, and yeah that's with the newest firmware. I had to use newer firmware on your newdrm branch as well. Let me know how I can help! :) On Mon, Jun 29, 2020 at 11:50 PM Jonathan Gray wrote: > On Mon, Jun 29, 2020 at 11:13:49PM -0500, Charlie Burnett wrote: > > Hi, > > > > Wasn’t sure who to tell this to, but with Vega 20 hardware under > -current, > > there is an issue with the firmware, where it cannot load. Manually > > installing the latest amdgpu firmware from kernel.org fixes this > seemingly. > > can you show the output when the 20200421 firmware failed to load? > you are referring to the following in linux-firmware 20200619 and later? > > commit f73f82cd4b7506a22a9aa1aa19e009fac3092eef > Author: Alex Deucher > Date: Mon Jun 15 17:33:26 2020 -0400 > > amdgpu: add vega20 TA firmware from 20.20 release > > Based on internal commit: > c6aa2bdaa30af815fc257f2b0e50f6c66d74045c > > Signed-off-by: Alex Deucher > Signed-off-by: Josh Boyer > > amdgpu/vega20_ta.bin | Bin 0 -> 54016 bytes > 1 file changed, 0 insertions(+), 0 deletions(-) > > commit 9ecaba882d78501d2ab2f6bd9407409128b351ed > Author: Alex Deucher > Date: Mon Jun 15 17:30:20 2020 -0400 > > amdgpu: update vega20 firmware from 20.20 release > > Based on internal commit: > c6aa2bdaa30af815fc257f2b0e50f6c66d74045c > > Signed-off-by: Alex Deucher > Signed-off-by: Josh Boyer > > amdgpu/vega20_asd.bin | Bin 147968 -> 160256 bytes > amdgpu/vega20_ce.bin| Bin 9344 -> 9344 bytes > amdgpu/vega20_me.bin| Bin 17536 -> 17536 bytes > amdgpu/vega20_mec.bin | Bin 268048 -> 268048 bytes > amdgpu/vega20_mec2.bin | Bin 268048 -> 268048 bytes > amdgpu/vega20_pfp.bin | Bin 21632 -> 21632 bytes > amdgpu/vega20_sdma.bin | Bin 17408 -> 17408 bytes > amdgpu/vega20_sdma1.bin | Bin 17408 -> 17408 bytes > amdgpu/vega20_smc.bin | Bin 262912 -> 262912 bytes > amdgpu/vega20_sos.bin | Bin 170896 -> 174992 bytes > 10 files changed, 0 insertions(+), 0 deletions(-) > > > There's also an issue that I've been unable to figure out for a while > here > > as well, in that undergoing a CPU intensive task will freeze up the > entire > > system. Disabling all power management options and setting the > > amdgpu_vm_update_mode to 3 lessens the occurrence of this, and using an > > HDMI connection instead of a DisplayPort with said modifications > seemingly > > eliminates it. Just switching amdgpu_vm_update_mode to 3 without anything > > else leads to issues, in which when launching X in which only a small > > square of seemingly random pixels are displayed. Using a vanilla kernel, > > only "Waiting for fences timed out!" appears. However, turning on > > amdgpu_debug_vm in amdgpu_drv.c will output quite a few DRM errors for > > "gmc_v9_0_process_interrupt", sometimes in the tens of thousands. Any > hang > > ups require a hard reboot. With amdgpu_vm_update_mode set to 3, the crash > > occurs differently in that whichever windows are using a bunch of GPU/CPU > > time turn a lime green color. They're completely functional at first, > > however if I keep putting heavy loads on both the screen becomes > pixelated > > on any changed pixels for those windows. I have a huge amount of logs for > > these, however from a couple weeks of trying to fix it myself they didn't > > offer much beyond what was stated in this email. > > this is similar to what is seen on vega10 and other parts >
AMDGPU Bug
Hi, I'm still getting the issue from earlier where X freezes entirely and I can't get it to work, though I've got no clue what's triggering it now, there seem to be no *regular* outputs to /var/log/messages with the crash. However, I was trying to trigger the bug earlier so I could hopefully provide more information, and I got a the same VM_L2_PROTECTION_FAULT_STATUS as before, but now with an added "[drm] *ERROR* Failed to initialize parser -88!". Here I tried running blender to put some load on the GPU. I say new because I was able to fix this bug by restarting X, and my display got real buggy though I was able to still move the cursor, although not interact with it. I can send a picture of the display if that's helpful, though it seemed to just have random pixels all over the screen. Below is the error that got kicked out when doing this, though I can't see any difference from last time. drm:pid27591:gmc_v9_0_process_interrupt *ERROR* [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32820, for process pid 0 thread gnome-shell pid 37788) drm:pid27591:gmc_v9_0_process_interrupt *ERROR* in page starting at address 0x800108a64000 from client 27 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* VM_L2_PROTECTION_FAULT_STATUS:0x003C0041 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* MORE_FAULTS: 0x1 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* WALKER_ERROR: 0x0 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* PERMISSION_FAULTS: 0x4 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* MAPPING_ERROR: 0x0 drm:pid27591:gmc_v9_0_process_interrupt *ERROR* RW: 0x1 Let me know if there's any other info I can give that would help! :)
DHCPD issue
Hi, I've set up a good deal of openbsd firewalls in a professional environment before with little to no issue. I'm trying to set one up for me personally though, and am having some bizarre issues, with no clue where to begin trying to fix them. This is on an APU unit from PC Engines. I've managed to figure out a couple things when trying to debug this: 1. I cannot connect to the internet properly unless only em0 (which is the ethernet port I have connected to the external network) has a hostname file- I have to either add back the hostname files after boot and run /etc/netsetup or manually set up the internal network ports through ifconfig. 2. Even once the box is connected properly to the network, its' seemingly unable to assign leases to other clients, attempting to connect to it through another OpenBSD machine results in it timing out while getting a lease. 3. Using the same exact config, I ran it behind a standard proprietary router (linksys) that connects fine externally. Using that, the box functions as expected. 4. Using an openwrt router I get similar errors. 5. I'm using both config that I've used on external networks as well as subnetworks on a corporate network that worked, and the default config from the setting up a router page for a sanity check. 6. I assumed it was DHCP, but nonetheless as a sanity check I had pf pass through anything and everything, worked internally as well as externally. I'm at a complete loss- seeing as it occurs on openwrt I assume that its' probably because of however the hell my landlord set up the network, but anyone remotely have an idea how to begin debugging this? I don't like particularly having a proprietary router running especially without a firewall I trust. Best, Charlie
Chromium with WebAssembly flavor?
Hi, I wasn't sure if this was worthy of ports or not, so I wanted to throw this out here first. I don't like Zoom, and I understand WebAssembly has some inherent issues in it, but I imagine a good number of people don't have a choice and have to use it as well in light of the current state of things. On top of this, Citrix apps need it enabled as well. Wouldn't it be reasonable to make a flavor with ENABLE_WASM set for chromium then? Compiling chrome manually with the flag is a beast, and my laptop will usually throw a kernel panic before it'll finish compiling, plus as a package it's updated quite regularly which means it needs to be recompiled quite regularly. Best regards, Charlie
Re: Chromium with WebAssembly flavor?
Ah, well now I feel dumb... my sincere apologies for the spam then. Thanks for the help, I had no idea! :) On Sat, Jan 30, 2021 at 7:40 AM Thomas Frohwein wrote: > On Fri, Jan 29, 2021 at 09:44:26PM -0600, Charlie Burnett wrote: > > Hi, > > I wasn't sure if this was worthy of ports or not, so I wanted to throw > this > > out here first. I don't like Zoom, and I understand WebAssembly has some > > inherent issues in it, but I imagine a good number of people don't have a > > choice and have to use it as well in light of the current state of > things. > > On top of this, Citrix apps need it enabled as well. Wouldn't it be > > reasonable to make a flavor with ENABLE_WASM set for chromium then? > > I think you misunderstand how this works. ENABLE_WASM is for the runtime > environment; you don't need to rebuild the whole port. In fact, if set > ENABLE_WASM for a build of the port, it likely still won't enable > WebAssembly. > > Take an example webpage that checks for WebAssembly (for example [1]): > > $ chrome > > => "WebAssembly is not supported in your browser" > > $ ENABLE_WASM=1 chrome > > => "WebAssembly is supported in your browser" > > > Compiling chrome manually with the flag is a beast, and my laptop will > > usually throw a kernel panic before it'll finish compiling, plus as a > > package it's updated quite regularly which means it needs to be > recompiled > > quite regularly. > > Best regards, > > Charlie > > [1] https://d2jta7o2zej4pf.cloudfront.net/ >
Gigenet Mirror x*69.tgz Failing to Verify Sets
Hi, Currently the gigenet mirror is failing to verify for all four X packages on snapshot. They verify fine when I point it towards cdn.openbsd.org, but this is the case for both when trying to install from both bsd.rd and an install iso. This is in a VM but I wouldn't see how that'd affect it. Oddly enough, I just upgraded my personal machine earlier today without any issues. Not sure what would need to be done about it, but I figured someone oughta be told! Best Regards, Charlie Burnett
