iwx driver on AX210 (Framework laptop)
Hi there! Trying to get OpenBSD running the the Framework laptop. The issue seems to be the AX210 wireless card which is not supported by the iwx driver that comes with 7.1. I noticed that AX210 *should* be supported according to the commits in the repo as of May 10th - https://github.com/openbsd/src/commit/4735940a108c49d416809fae2ba479d59de40589 I checked the firmware snapshot, and the last one is iwx-firmware-20220110p0.tgz - so, older... (I thought) BUT, the commit message on May 10th (linked above) says that it should work as of snapshot iwx-firmware-20220110 - this seems very strange, the only explanation I could come up with is that the author of the commit published a snapshot with the wrong filename? Fair enough, I loaded the iwx-firmware-20220110p0.tgz snapshot from an USB drive using fw_update. The card still shows up as "not configured" in dmesg. Anything else I could try? Thank you! -- Ioan Bizău http://ibz.me
Re: dhcpleased and ifstated
On Tue, Jul 5, 2022 at 9:56 PM Christer Solskogen < christer.solsko...@gmail.com> wrote: > Now that dhclient is soon to be gone, I wanted to switch to dhcpleased. > But I do have a hard time understanding how I can get that to work together > with CARP and ifstated. > With dhclient, as soon as the master boots, the backup takes over and get > an ip address in an instant from my ISP, but dhcpleased does not. It don't > even get an ipaddress unless I run "dhcpleasectl -w 1 " > (dhcpleased runs in the background) > > Okay, I've obviously thought of dhcpleased wrong. Now dhcpleased works in the background all the time, and a simple "run ifconfig re0 up" instead of starting it in ifstated. But still, it takes 2-3 seconds to get a lease, while with dhclient it was instant.
Re: mSATA in APU2D0
On Jul 06 11:54:02, stu.li...@spacehopper.org wrote: > On 2022-07-06, Jan Stary wrote: > > This is current/amd64 on an APU2D0, dmesg below > > Everything runs just fine from a SD card. > > > > My problem is it does not boot with this mSATA disk in. > > The leds of the mSATA and the leds of the APU keep blinking, > > the console keeps repeating > > Is it in the correct slot? > https://pcengines.github.io/apu2-documentation/APU_mPCIe_capabilities/ Yes
Re: dhcpleased and ifstated
On 2022-07-06 10:09 +02, Christer Solskogen wrote: > On Tue, Jul 5, 2022 at 9:56 PM Christer Solskogen < > christer.solsko...@gmail.com> wrote: > >> Now that dhclient is soon to be gone, I wanted to switch to dhcpleased. >> But I do have a hard time understanding how I can get that to work together >> with CARP and ifstated. >> With dhclient, as soon as the master boots, the backup takes over and get >> an ip address in an instant from my ISP, but dhcpleased does not. It don't >> even get an ipaddress unless I run "dhcpleasectl -w 1 " >> (dhcpleased runs in the background) >> >> > Okay, I've obviously thought of dhcpleased wrong. Now dhcpleased works in > the background all the time, and a simple "run ifconfig re0 up" instead of > starting it in ifstated. But still, it takes 2-3 seconds to get a lease, > while with dhclient it was instant. Are you comparing the same thing? I.e. did dhcpleased get a lease before and does /var/db/dhcpleased/$IF exist? If it then tries to reaquire a lease it goes REBOOTING -> BOUND which involves 2 packets, DHCPREQUEST and DHCPACK. If you did not have a lease before you need to exchange 4 packets which naturaly takes longer. I have not found dhcpleased being faster or slower than dhclient. -- I'm not entirely sure you are real.
mSATA in APU2D0
This is current/amd64 on an APU2D0, dmesg below Everything runs just fine from a SD card. My problem is it does not boot with this mSATA disk in. The leds of the mSATA and the leds of the APU keep blinking, the console keeps repeating PC Engines apu2 coreboot build 2006 BIOS version v4.17.0.1 and it never gets past that. It has booted _once_, but not since. Without the mSATA, it boots fine. I have tested the mSATA disk in other machines and adaptors and it seems to work fine. Is this some kind of HW incompatibility? How can I debug what's happening? Jan OpenBSD 7.1-current (GENERIC.MP) #0: Tue Jun 28 13:07:15 CEST 2022 h...@www.stare.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2112430080 (2014MB) avail mem = 2031108096 (1937MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.0 @ 0x7ee92040 (13 entries) bios0: vendor coreboot version "v4.17.0.1" date 06/22/2022 bios0: PC Engines apu2 acpi0 at bios0: ACPI 6.0 acpi0: sleep states S0 S1 S4 S5 acpi0: tables DSDT FACP SSDT MCFG TPM2 APIC HEST SSDT SSDT DRTM HPET acpi0: wakeup devices PBR4(S4) PBR5(S4) PBR6(S4) PBR7(S4) PBR8(S4) UOH1(S3) UOH2(S3) UOH3(S3) UOH4(S3) UOH5(S3) UOH6(S3) XHC0(S4) acpitimer0 at acpi0: 3579545 Hz, 32 bits acpimcfg0 at acpi0 acpimcfg0: addr 0xf800, bus 0-63 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: AMD GX-412TC SOC, 998.27 MHz, 16-30-01 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu0: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu0: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu0: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: AMD GX-412TC SOC, 998.14 MHz, 16-30-01 cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu1: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu1: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu1: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 2 (application processor) cpu2: AMD GX-412TC SOC, 998.14 MHz, 16-30-01 cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu2: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu2: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu2: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: AMD GX-412TC SOC, 998.31 MHz, 16-30-01 cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,PCLMUL,MWAIT,SSSE3,CX16,SSE4.1,SSE4.2,MOVBE,POPCNT,AES,XSAVE,AVX,F16C,NXE,MMXX,FFXSR,PAGE1GB,RDTSCP,LONG,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,TOPEXT,DBKP,PERFTSC,PCTRL3,ITSC,BMI1,XSAVEOPT cpu3: 32KB 64b/line 2-way I-cache, 32KB 64b/line 8-way D-cache, 2MB 64b/line 16-way L2 cache cpu3: ITLB 32 4KB entries fully associative, 8 4MB entries fully associative cpu3: DTLB 40 4KB entries fully associative, 8 4MB entries fully associative cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 4 pa 0xfec0, version 21, 24 pins ioapic1 at mainbus0: apid 5 pa 0xfec2, version 21, 32 pins acpihpet0 at acpi0: 14318180 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus -1 (PBR4) acpiprt2 at acpi0: bus 1 (PBR5) acpiprt3 at acpi0: bus -1 (PBR6) acpiprt4 at acpi0: bus 2 (PBR7) acpiprt5 at acpi0: bus -1 (PBR8) acpicpu0 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu1 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu2 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu3 at acpi0: C2(0@400 io@0x1771), C1(@1 halt!), PSS acpicpu4 at acpi0: no cpu
Re: mSATA in APU2D0
On 2022-07-06, Jan Stary wrote: > This is current/amd64 on an APU2D0, dmesg below > Everything runs just fine from a SD card. > > My problem is it does not boot with this mSATA disk in. > The leds of the mSATA and the leds of the APU keep blinking, > the console keeps repeating Is it in the correct slot? https://pcengines.github.io/apu2-documentation/APU_mPCIe_capabilities/
Re: iwx driver on AX210 (Framework laptop)
On Wed, Jul 06, 2022 at 09:50:34AM +0300, Ioan Bizău wrote: > Hi there! > > Trying to get OpenBSD running the the Framework laptop. The issue seems to be > the AX210 wireless card which is not supported by the iwx driver that comes > with 7.1. AX210 is only supported in -current. Run sysupgrade -s and then it should work. The 7.1 release does not contain the relevant changes to the driver. To find out, see the commit history of the driver here: https://cvsweb.openbsd.org/src/sys/dev/pci/if_iwx.c The OPENBSD_7_1 tag sits on revision 1.140, any changes above that are only available in -current snapshots.
Re: iwx driver on AX210 (Framework laptop)
On Wed, Jul 06, 2022 at 11:21:29AM +0300, Ioan Bizău wrote: > Yup, I noticed that after checking the commit history. But I was wondering > how I can get a newer snapshot of the driver running in 7.1. I thought > fw_update would help if I get the snapshot from > http://firmware.openbsd.org/firmware/snapshots/ and save it to a USB stick, > but seems it doesn't. > > sysupgrade is not an option since I don't have internet on that machine. > > Is my only other choice then to run -current? Your options are: - run OpenBSD -current (AX210 works with 11n/11ac) - use a supported USB wifi dongle for now, and wait for OpenBSD 7.2 - run Linux (has Intel vendor driver with 11n/11ac/11ax working) - run FreeBSD 13.1 (AX210 probably works but only without 11n/11ac)
Re: iwx driver on AX210 (Framework laptop)
> The 7.1 release does not contain the relevant changes to the driver. > To find out, see the commit history of the driver here: > https://cvsweb.openbsd.org/src/sys/dev/pci/if_iwx.c > The OPENBSD_7_1 tag sits on revision 1.140, any changes above that > are only available in -current snapshots. Yup, I noticed that after checking the commit history. But I was wondering how I can get a newer snapshot of the driver running in 7.1. I thought fw_update would help if I get the snapshot from http://firmware.openbsd.org/firmware/snapshots/ and save it to a USB stick, but seems it doesn't. sysupgrade is not an option since I don't have internet on that machine. Is my only other choice then to run -current?
Re: dhcpleased and ifstated
On Wed, Jul 6, 2022 at 4:47 PM Florian Obser wrote: > > Are you comparing the same thing? I.e. did dhcpleased get a lease before > and does /var/db/dhcpleased/$IF exist? > Both nodes have /var/db/dhcpleased/$IF. If I reboot both firewalls only the master have gotten the lease, until I do a switch over. During a switchover I get this with debug on: tugs# dhcpleased -d -v -v changed iface: re2[3] state_transition[re2] Down -> Down, timo: -1 (when doing the switchover) state_transition[re2] Down -> Down, timo: -1 state_transition[re2] Down -> Rebooting, timo: 1 DHCPREQUEST on re2 iface_timeout[3]: Rebooting state_transition[re2] Rebooting -> Rebooting, timo: 2 DHCPREQUEST on re2 parse_dhcp, from: 00:02:00:01:00:01, to: ff:ff:ff:ff:ff:ff parse_dhcp: 79.160.116.238:67 -> 255.255.255.255:68 It looks to me that it's rebooting twice? What's the correct way of doing this with ifstated? run "ifconfig $IF down" or "ifconfig $IF delete"?
Some framebuffer related questions
Hi there, I have been working on a small library to allow drawing directly to the framebuffer, similar to FreeBSD's old VGL library. Including keyboard handling and in the future I will tackle sound too. I have made a quick port of the GNUBoy gameboy emulator as well as some debug programs here: https://gitlab.com/osen/openbsd_drmfb_gnuboy I have implemented this currently using the DRM framebuffer via libdrm but I am also in the early stages of using wsconsctl/mmap and the framebuffer provided by efifb for some platforms which is working well so far (and the code is so much nicer than libdrm). Just a few questions: 1) From wsdisplay(4) manpage, what is the difference between WSDISPLAYIO_MODE_MAPPED and WSDISPLAYIO_MODE_DUMBFB? Both seem to work by mmap'ing the filedescriptor. 2) When I do mmap of the i.e /dev/ttyC0 file descriptor, I use an offset of 0, so I am not sure where width/height is stored?, I am obviously missing something). Where does the separate ioctl call of WSDISPLAYIO_GINFO get this information? 3) I understand that vgafb(4) exists on macppc and sparc64 but can the vga(4) only do text-mode? Currently I can get a framebuffer on: intel via inteldrm (libdrm) amd via amdgpu/radeondrm (libdrm) raspberry pi via efifb (libdrm) nvidia with EFI via efifb (wsdisplay, mmap) nvidia with BIOS... ? I suppose the way forward for this one will be to pick apart vesafb from Xorg but I was hoping there might be something already in place (admittedly it isn't a common use-case). Any info would be greatly appreciated. That is probably enough questions for now :) Many thanks, Karsten
