Both UK BSD User Groups gone?

[Polarian]

Hello,

A while back I was looking into Linux/BSD groups in the UK, more
specifically in the South. Of course this leads me to the OpenBSD
groups page [1].

Taking a look, there is two groups, one in Manchester and one in
London, success... until I realised the contact detail is a domain,
which is now in parking.

This domain was the contact for both the London and Manchester
groups.

I decided to look into it and found the ukfreebsd mailing list was
somehow tied with the former user groups, I only got a single response
[2] so I think its safe to say these can be removed from the OpenBSD
User Group list, I am not really sure how to request this myself, was
hoping someone could help out?

Lastly, to dip my toe into the ocean, hypothetically, if there was a
meetup/miniconf in London, possibly next year who would be interested in
attending? (please offlist me to show your interest) Seeing how much
interest there would be in this, seen as UK does not seem to have a
single BSD group, meetup or event remaining (if you know of one please
let me know!), which in my opinion is quite depressing, so lets fix that
:D

As a note for the above, there is no residency restrictions (you don't
need to be from/live in the UK) to show interest, but bare in mind it
will only be small and only a single day if something did miraculously
happen, so maybe not show interest if it involves flying across the
globe :)

As extra extra note, this is in no way confirmed, if someone does get
scheduled I will announce it in the future, currently I just need to
know who is interested (pointless setting up infra and discussing it if
nobody is interested).

Thanks for reading,
-- 
Polarian
GPG signature: 0770E5312238C760
Jabber/XMPP: polar...@icebound.dev

[1] https://www.openbsd.org/groups.html
[2] http://mailman.uk.freebsd.org/pipermail/ukfreebsd/2024-October/014267.html

touchpad not working in snapshot

[Eric Auge]

Hello,

I run OpenBSD snapshots on a Framework 13" AMD based laptop that I
upgrade from time to time.
Since October 17th (or around) the touchpad is not working anymore.

mouse are being detected as normal, but no more move registered etc..
In OpenBSD release 7.6 the mouse works as expected.

What did I miss or what did change?
another question would be why 4 keyboards ?!?!?

---
amd-firmware-20240909 microcode update binaries for AMD CPUs
amdgpu-firmware-20240909 firmware binary images for amdgpu(4) driver
amdsev-firmware-20241017 AMD SEV firmware binaries
---

Any ideas?!

Cheers,
Eric.


dmesg.boot
Description: Binary data


wsconsctl.out
Description: Binary data

Re: Minimum supported chipsets of amd64

[Christian Schulte]

On 10/29/24 04:49, Philip Guenther wrote:
> On Mon, Oct 28, 2024 at 11:43 AM Christian Schulte  wrote:
> ...
>> I would really like to understand why this architecture stood the test
>> of time. Just because it boots in 8 bit CPU mode from the 70ties not
>> even capable of beating a 6502?
> <...>
> 
> Building a base of users with computers capable of running a more
> powerful ISA/OS/whatever (while it still supports their existing
> applications), so that application writers believe that there will be
> sufficient user base with that capability to use software written to
> use that power, which drives more people to get those more capable
> computers, has been a huge driver of not just the evolution of x86 but
> of the computer industry as a whole.  x86 made those steps easy for a
> line of ISA evolution; Apple went a different direction and put the
> backwards/forwards compat into their build tools so you could build on
> one arch/OS-version and move to a different one and did that so well
> that they managed to move user bases from m68k to powerpc to x86 to
> arm64 with compat across each transition.  You _do_ understand that
> the set of people who can rebuild all the software they directly use
> is *tiny* and the subset of those for whom doing so is a net positive
> use of the limited time they have between birth is death is
> insubstantial, yes?

This justifies this tiny group of people to enforce everyone to use
technology outdated for more than 4 decades? Just because their
knowledge would become useless and outdated? Deal with it. Learning
about that architecture is exactly about that kind of wasting time you
are talking about. There is no value in forcing anyone to learn about
how PCs in the late 70s or early 80s used to boot the CPU in what
insanity mode whatsoever. Get over it. Want to run DOS or CP/M. Even
your smartphone is capable of doing so. Advocating i368 or AMD64 as
being the most brilliant invention mankind ever has produced is just
insane. It really is full of design flaws. Even an Intel engineer would
agree to this privately.

-- 
Christian

Re: touchpad not working in snapshot

[Eric Auge]

Inlined dmesg.boot

OpenBSD 7.6-current (GENERIC.MP) #389: Fri Oct 25 22:45:36 MDT 2024
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 66349903872 (63276MB)
avail mem = 64315117568 (61335MB)
random: good seed from bootblocks
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 3.6 @ 0x58e75000 (62 entries)
bios0: vendor INSYDE Corp. version "03.05" date 03/29/2024
bios0: Framework Laptop 13 (AMD Ryzen 7040Series)
efi0 at bios0: UEFI 2.9
efi0: INSYDE Corp. rev 0x305
acpi0 at bios0: ACPI 5.0
acpi0: sleep states S0ix S4 S5
acpi0: tables DSDT FACP UEFI SSDT SSDT SSDT ASF! BOOT HPET APIC MCFG
SLIC VFCT SSDT SSDT CRAT CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
SSDT FPDT WSMT TPM2 SSDT MHSP SSDT IVRS SSDT SSDT SSDT SSDT SSDT SSDT
SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT BGRT
acpi0: wakeup devices GPP0(S4) GPP2(S4) GPP5(S4) GPP6(S4) GPP7(S4)
GP11(S4) SWUS(S4) GP12(S4) SWUS(S4)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpihpet0 at acpi0: 14318180 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu0: cpuid 1 
edx=178bfbff
ecx=76f8320b
cpu0: cpuid 6 eax=4 ecx=1
cpu0: cpuid 7.0
ebx=f1bf97a9
ecx=405fce edx=1010
cpu0: cpuid d.1 eax=f
cpu0: cpuid 8001 edx=2fd3fbff
ecx=75c237ff
cpu0: cpuid 8007 edx=e799
cpu0: cpuid 8008
ebx=791ef257
cpu0: cpuid 801F eax=1
cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB
64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=1.1, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu1: smt 1, core 0, package 0
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu2: smt 0, core 1, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu3: smt 1, core 1, package 0
cpu4 at mainbus0: apid 4 (application processor)
cpu4: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu4: smt 0, core 2, package 0
cpu5 at mainbus0: apid 5 (application processor)
cpu5: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu5: smt 1, core 2, package 0
cpu6 at mainbus0: apid 6 (application processor)
cpu6: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu6: smt 0, core 3, package 0
cpu7 at mainbus0: apid 7 (application processor)
cpu7: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu7: smt 1, core 3, package 0
cpu8 at mainbus0: apid 8 (application processor)
cpu8: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu8: smt 0, core 4, package 0
cpu9 at mainbus0: apid 9 (application processor)
cpu9: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu9: smt 1, core 4, package 0
cpu10 at mainbus0: apid 10 (application processor)
cpu10: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu10: smt 0, core 5, package 0
cpu11 at mainbus0: apid 11 (application processor)
cpu11: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu11: smt 1, core 5, package 0
cpu12 at mainbus0: apid 12 (application processor)
cpu12: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu12: smt 0, core 6, package 0
cpu13 at mainbus0: apid 13 (application processor)
cpu13: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu13: smt 1, core 6, package 0
cpu14 at mainbus0: apid 14 (application processor)
cpu14: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.00 MHz,
19-74-01, patch 0a704104
cpu14: smt 0, core 7, package 0
cpu15 at mainbus0: apid 15 (application processor)
cpu15: AMD Ryzen 7 7840U w/ Radeon 780M Graphics, 3300.01 MHz,
19-74-01, patch 0a704104
cpu15: smt 1, core 7, package 0
ioapic0 at mainbus0: apid 33 pa 0xfec0, version 21, 24 pins, can't remap
ioapic1 at mainbus0: apid 34 pa 0xfec01000, version 21, 32 pins, can't remap
acpimcfg0 at acpi0
acpimcfg0: addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (GPP0)
acpiprt2 at acpi0: bus -1 (GPP1)
acpiprt3 at acpi0: bus -1 (GPP2)
acpiprt4 at acpi0: bus -1 (GPP3)
acpiprt5 at acpi0: bus -1 (GPP4)
acpiprt6 at acpi0: bus -1 (GPP5)
acpiprt7 at acpi0: bus 1 (GPP6)
acpiprt8 at acpi0: bus -1 (GPP7)
acpiprt9 at acpi0: bus 2 (GPP8)
acpiprt10 at acpi0: bus -1 (GPP9)
acpiprt11 at acpi0: bus -1 (GPPA)
acpiprt12 at acpi0: bus 3 (GP11)
acpiprt13 at acpi0: bus 98 (GP12)
acpip

Snapshots and packages

[J Doe]

Hello,

I have a basic question about following -current.

I have an OpenBSD 7.5 system.  I want to grab the latest snapshot and update my 
packages.  Is the correct process as follows ?

$ doas sysupgrade -s
$ doas pkg_add -uvi

The OpenBSD FAQ mentions that package updates changes when a snapshot is a 
release candidate.  In that case is the correct process as follows ?

$ doas sysupgrade -s
$ doas pkg_add -D snap

Thanks for your help,

- J

7.5: Caja start up problem after 012_xserver

[Dan]

Hello,

After the latest patch, 012_xserver, installed via syspatch, Caja is not
so friendly:

(caja:87440): dbind-WARNING **: 17:04:10.688: Couldn't connect to
accessibility bus: Empty address '' Could not register the application:
Timeout was reached

and it doesn't start under Xfce.


-Dan

Re: Minimum supported chipsets of amd64

[Anon Loli]

On Tue, Oct 29, 2024 at 12:26:54PM +0100, Christian Schulte wrote:
> On 10/28/24 22:53, Anon Loli wrote:
> > On Mon, Oct 28, 2024 at 05:35:47PM +0100, Christian Schulte wrote:
> >> On 10/24/24 03:01, Mike Larkin wrote:
> >>>
> >>> Every one of us who has worked in this area, at this level, has read those
> >>> 800+ page documents. Sometimes they are many thousands of pages (eg the 
> >>> latest
> >>> Intel SDM or latest ACPI spec).
> >>>
> >>> Tell us what you are doing and what you want to know and maybe we can 
> >>> point
> >>> you to the right docs, but there is no short-cutting reading the reference
> >>> manuals.
> >>>
> >>
> >> I would really like to understand why this architecture stood the test
> >> of time. Just because it boots in 8 bit CPU mode from the 70ties not
> >> even capable of beating a 6502? Just because developers were not
> >> continuously forced to throw away all knowledge and could build upon it?
> >> Seems to be the reason. Intel tried to throw away legacy burdens and got
> >> set straight by AMD. I am currently approaching page 4000 of
> >> documentation. Shaking heads. Unbelievable. What I am lacking so far is
> >> a current PCI bus specification. This seems to not be available to non
> >> members who I am certainly not. Coming from a hardware background,
> >> documents like this
> >>
> >> 
> >>
> >> clearly were a waste of time, at least when your goal is not to produce
> >> mainboards. Well. Normally you would program devices directly. It even
> >> contains write-once-by-firmware registers. It will take some time for me
> >> to understand the reasoning behind this. Not questioning there are no
> >> reasons for doing it that way. I am just trying to make me stop hating
> >> that architecture. I am still failing at this task but I would like to
> >> overcome this. At least it has linear address space. Oh. What a wonder.
> >> Every 68k had this decades ago. Oh sorry. Your comments are very helpful
> >> to me so far so thank you. Because the machine independent parts in the
> >> kernel really are abstractions of formerly machine dependent parts,
> >> understanding the worst case of those - namely x86 and amd64 - will help
> >> me understand those. I am still in the process of reading x86/amd64
> >> documentation even if it make me shake my head every so often.
> >>
> >> Regards,
> >> -- 
> >> Christian
> > 
> > I just wrote a whole big-ass e-mail about how hardware has been shit for
> > decades now.
> > I do not feel like rewriting all of it right now it was a genius e-mail.
> > 
> > I fucking hate when my e-mail client goes bananas because it's terminal 
> > based.
> > Fuck escape sequences and stupid retarded Unix.
> > When do escape sequences actually work as intended? When?
> > 
> > Anyways suckless.org rocks, and should be implied to hardware.
> > 
> > Open Source is Insufficient to Solve Trust Problems in Hardware
> > https://youtube.com/watch?v=Hzb37RyagCQ
> > 
> > How do you know the hardware in front of you actually conforms to the 
> > hardware
> > design you might or might not have?
> > You can't, it's not like software, at least you can't with existing 
> > hardware,
> > watch the video.
> > 
> > Mud towers build on mud foundation are still mud and will collapse under 
> > mud.
> > 
> > This was more-less the important stuff
> > Fuck I hate re-writing emails fuck me!
> > 
> 
> Fuck. Ass. Genius. You maybe want to watch the Youtube Channels of Ben
> Eater [1] or James Sharman [2] for a starting point talking about
> hardware and how to build a CPU from scratch using bread boards. Fuck.
> Ass. Genius. Then start reading about what microelectronics is about or
> even get a degree in microelectronics. Fuck. Ass. Genius.
> 
> [1] 
> [2] 
> 
> -- 
> Christian

Since I am autistic, I have trouble understanding when exactly someone is
making fun of me or what tone they are using, especially trough text.
For the sake of friendliness I shall assume that you said all of that in good
spirit and were not condescending.

I knew about Ben Eater for many years, I am extremely interested in
microelectronics.. I am also interested in chemistry and creating your own
transistors and stuff - silicon, etc. ... but that stuff FOR NOW is
unimportant.
Did not know about James Sharman, though.

There was a dude whomst I forgot about; he created his own RISC-V CPU and
hardware around it - motherborad, even add-in PCI-like daughterboards for stuff
like VGA and keyboard support if I remember correctly.
That computer was a intelligent multi-story, stacked tower - great design,
keeps things separated, cool-looking and organized.

And if I were to create something usable, I shall write a super ultra-simple
guide on how to do it yourself - DIY - unlike best of best manual pages *cough*
*cough*.
So almost everyone cou

Re: Snapshots and packages

[hahahahacker2009]

Vào Th 5, 31 thg 10, 2024 vào lúc 03:35 J Doe
 đã viết:
>
> Hello,
>
> I have a basic question about following -current.
>
> I have an OpenBSD 7.5 system.  I want to grab the latest snapshot and update 
> my packages.  Is the correct process as follows ?
>
> $ doas sysupgrade -s
> $ doas pkg_add -uvi
>

Yes

> The OpenBSD FAQ mentions that package updates changes when a snapshot is a 
> release candidate.  In that case is the correct process as follows ?
>
> $ doas sysupgrade -s
> $ doas pkg_add -D snap
>

TL;DR: when pkg_add -u breaks, run pkg_add -D snap -u instead

When they drop the beta tag (OpenBSD version is not 7.6-beta or
7.6-current or 7.6-stable or whatever, simply 7.6, if I recall correctly
pkg_add will try to fetch packages from the 7.6 directory (instead of
snapshot directory), which contain nothing. You will have to force
it to download packages from the snapshot directory with -D snap.

When the beta tag is dropped, it will be announced on undeadly.org


> Thanks for your help,
>
> - J

Re: Apple Macbook Air (M1) lost bwfm

[Jan Stary]

On Sep 25 15:05:00, h...@stare.cz wrote:
> This is 7.6-beta/arm64 (#179) on an MBA (M1, 2020),
> the last kernel used is this:
> 
> https://github.com/janstary/dmesg/blob/master/apple-macbook-air-A2337.20240915
> 
> While this listing shows
> bwfm0 at pci1 dev 0 function 0 "Broadcom BCM4378" rev 0x03: msi
> and it worked (I pkg_add-u'd the packages after the upgrade),
> now I don't even have bwfm - with this same kernel, or with
> an older /obsd (#31 of May's 7.5).
> 
> I blame the macOS upgrade to 15.0 (24A335) but I can't be sure.
> Is it possible the macOS upgrade did something to the firmware?
> OpenBSD has bwfm-firmware-20200316.1.3p3 installed.

This is to report that after an upgrade to macOS 15.1
and an upgrade of OpenBSD to the latest snapshot, bwfm is back;
dmesg below. I don't know whoch of the two did it - sorry,
I forgot to check after the separate steps.

> Also, I have lost hw.sensors.aplsmc,

That is back too.

Jan



OpenBSD 7.6-current (GENERIC.MP) #225: Wed Oct 30 04:18:27 MDT 2024
dera...@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
real mem  = 7997173760 (7626MB)
avail mem = 7624654848 (7271MB)
random: good seed from bootblocks
mainbus0 at root: Apple MacBook Air (M1, 2020)
efi0 at mainbus0: UEFI 2.10
efi0: Das U-Boot rev 0x20240100
cpu0 at mainbus0 mpidr 0: Apple Icestorm r1p1
cpu0: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu0: 4096KB 128b/line 16-way L2 cache
cpu0: 
TLBIOS+IRANGE,TS+AXFLAG,FHM,DP,SHA3,RDM,Atomic,CRC32,SHA2+SHA512,SHA1,AES+PMULL,SPECRES,SB,FRINTTS,GPI,LRCPC+LDAPUR,FCMA,JSCVT,API+PAC,DPB+DCCVADP,SpecSEI,PAN+ATS1E1,LO,HPDS,VH,IDS,AT,CSV3,CSV2,DIT,AdvSIMD+HP,FP+HP,SSBS+MSR
cpu1 at mainbus0 mpidr 1: Apple Icestorm r1p1
cpu1: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu1: 4096KB 128b/line 16-way L2 cache
cpu2 at mainbus0 mpidr 2: Apple Icestorm r1p1
cpu2: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu2: 4096KB 128b/line 16-way L2 cache
cpu3 at mainbus0 mpidr 3: Apple Icestorm r1p1
cpu3: 128KB 64b/line 8-way L1 VIPT I-cache, 64KB 64b/line 8-way L1 D-cache
cpu3: 4096KB 128b/line 16-way L2 cache
cpu4 at mainbus0 mpidr 10100: Apple Firestorm r1p1
cpu4: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu4: 12288KB 128b/line 12-way L2 cache
cpu5 at mainbus0 mpidr 10101: Apple Firestorm r1p1
cpu5: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu5: 12288KB 128b/line 12-way L2 cache
cpu6 at mainbus0 mpidr 10102: Apple Firestorm r1p1
cpu6: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu6: 12288KB 128b/line 12-way L2 cache
cpu7 at mainbus0 mpidr 10103: Apple Firestorm r1p1
cpu7: 192KB 64b/line 6-way L1 VIPT I-cache, 128KB 64b/line 8-way L1 D-cache
cpu7: 12288KB 128b/line 12-way L2 cache
"asc-firmware" at mainbus0 not configured
"asc-firmware" at mainbus0 not configured
"framebuffer" at mainbus0 not configured
"region95" at mainbus0 not configured
"region94" at mainbus0 not configured
"region57" at mainbus0 not configured
"dcp_data" at mainbus0 not configured
"uat-handoff" at mainbus0 not configured
"uat-pagetables" at mainbus0 not configured
"uat-ttbs" at mainbus0 not configured
"isp-heap" at mainbus0 not configured
apm0 at mainbus0
"opp-table-0" at mainbus0 not configured
"opp-table-1" at mainbus0 not configured
"opp-table-gpu" at mainbus0 not configured
agtimer0 at mainbus0: 24000 kHz
"pmu-e" at mainbus0 not configured
"pmu-p" at mainbus0 not configured
"clock-ref" at mainbus0 not configured
"clock-120m" at mainbus0 not configured
"clock-200m" at mainbus0 not configured
"clock-disp0" at mainbus0 not configured
"clock-dispext0" at mainbus0 not configured
"clock-ref-nco" at mainbus0 not configured
simplebus0 at mainbus0: "soc"
aplpmgr0 at simplebus0
aplpmgr1 at simplebus0
aplmbox0 at simplebus0
apldart0 at simplebus0: 32 bits
apldart1 at simplebus0: 32 bits, locked
apldart2 at simplebus0: 32 bits, locked
aplmbox1 at simplebus0
apldart3 at simplebus0: 32 bits, bypass
apldart4 at simplebus0: 32 bits
apldart5 at simplebus0: 32 bits
apldart6 at simplebus0: 32 bits, bypass
aplintc0 at simplebus0 nirq 896 ndie 1
aplpinctrl0 at simplebus0
aplpinctrl1 at simplebus0
apldog0 at simplebus0
aplmbox2 at simplebus0
aplpinctrl2 at simplebus0
aplpinctrl3 at simplebus0
aplmbox3 at simplebus0
aplefuse0 at simplebus0
apldart7 at simplebus0: 32 bits, bypass
apldart8 at simplebus0: 32 bits, bypass
apldart9 at simplebus0: 32 bits, bypass
apldart10 at simplebus0: 32 bits, bypass
apldart11 at simplebus0: 32 bits
"gpu" at simplebus0 not configured
aplcpu0 at simplebus0
aplcpu1 at simplebus0
apldcp0 at simplebus0
apldrm0 at simplebus0
drm0 at apldrm0
"isp" at simplebus0 not configured
apliic0 at simplebus0
iic0 at apliic0
tipd0 at iic0 addr 0x38
tipd1 at iic0 addr 0x3f
apliic1 at simplebus0
iic1 at apliic1
tascodec0 at iic1 addr 0x31
apliic2 at simplebus0
iic2 at apliic2
tascodec1 at iic2 addr 0x34
"cirrus,cs42l83" at iic2 addr 

Re: Apple Macbook Air (M1) lost bwfm

[Jan Stary]

On Sep 25 14:59:09, stu.li...@spacehopper.org wrote:
> On 2024-09-25, Jan Stary  wrote:
> > This is 7.6-beta/arm64 (#179) on an MBA (M1, 2020),
> > the last kernel used is this:
> >
> > https://github.com/janstary/dmesg/blob/master/apple-macbook-air-A2337.20240915
> >
> > While this listing shows
> > bwfm0 at pci1 dev 0 function 0 "Broadcom BCM4378" rev 0x03: msi
> > and it worked (I pkg_add-u'd the packages after the upgrade),
> > now I don't even have bwfm - with this same kernel, or with
> > an older /obsd (#31 of May's 7.5).
> >
> > I blame the macOS upgrade to 15.0 (24A335) but I can't be sure.
> > Is it possible the macOS upgrade did something to the firmware?
> > OpenBSD has bwfm-firmware-20200316.1.3p3 installed.
> 
> OpenBSD/arm64 on Apple hardware doesn't use firmware from bwfm-firmware,
> there's some process to copy it from MacOS

Is there some other reason why bwfm-firmware is installed then?

Jan

Re: Snapshots and packages

[Anon Loli]

On Wed, Oct 30, 2024 at 03:34:08PM -0400, J Doe wrote:
> Hello,
> 
> I have a basic question about following -current.
> 
> I have an OpenBSD 7.5 system.  I want to grab the latest snapshot and update 
> my packages.  Is the correct process as follows ?
> 
> $ doas sysupgrade -s
> $ doas pkg_add -uvi
> 
> The OpenBSD FAQ mentions that package updates changes when a snapshot is a 
> release candidate.  In that case is the correct process as follows ?
> 
> $ doas sysupgrade -s
> $ doas pkg_add -D snap
> 
> Thanks for your help,
> 
> - J

The easiest way to check that would be using the 1st command you mentioned
`pkg_add -uviargs, then after that do the `pkg_add -D snap args` and see if
anything changes because there would be no change.

I do `pkg_add -D snap` as if I recall correctly it is required 1. after
upgrading to -current and 2. after upgrading to a major version (7.5->7.6), but
I might be wrong.

Also another way to check is by running `pkg-add -u` 3 times in 3 days, and,
well there should not be many changes as packages don't really get updated that
often in the stable branch.

Cheers!



-- 
Anon Loli
#
This mortal strives for omnisciency. Some tags: perfectionist, minimalist,
researcher, scientist, philosopher, developer, autist, anarchist, data hoarder,
99 other tags and interests.

I am always up for conversing as long as you meet these requirements:
1. Use PGP encryption for all data shared,
2. Use a open source operating system, NOT Windows, NOT MacOS,
3. Have a open mind - are ready to let go of any and all imperfect views on
  anything, if they are.
Let's change this world for the better, one action at a time




signature.asc
Description: PGP signature