I'll see if I have an adapter that works. I took a photo of the screen and ran it through an online optical character recognition site so I didn't have to fix or type much.
On Mon, Jun 14, 2021, 1:29 PM Stuart Henderson <s...@spacehopper.org> wrote: > On 2021/06/14 20:32, Mark Kettenis wrote: > > > From: Evan Littmann <eblittm...@gmail.com> > > > Date: Sun, 13 Jun 2021 17:28:50 -0700 > > > > > > Hello, > > > > > > I am using OpenBSD 6.9 on an HP EliteDesk 705 G1 desktop mini and it > can't > > > boot after install due to a panic in mii_phy_setmedia related to the > bge > > > driver which might be related to this bug > > > > http://openbsd-archive.7691.n7.nabble.com/possible-bug-in-mii-physubr-c-with-Broadcom-BCM57780-td162423.html > . > > > The full hardware list of this machine is at > > > https://support.hp.com/bg-en/document/c04424260. > > > > > > It boots from a USB thumb drive and installs to disk using the > Broadcom NIC > > > to grab the sets over http, but there is an error while booting the > normal > > > kernel. I can't use ddb as the keyboard doesn't work after the crash. I > > > have tried many keyboards in each of the USB ports and none of them > work. > > > It boots from bsd.rd. > > > > > > I have tried changing the BIOS network adapter settings including > changing > > > autonegotiation and nothing affects this crash. > > > > Not much we can do without a full dmesg unfortunately. > > One way to get that would be to use a USB ethernet adapter and avoid > configuring network on the bge interface when installing. > > > > This is the message: > > > pf enabled > > > starting network > > > panic: mii_phy_setmedia > > > Stopped at db_enter+0x10: popq %rbp > > > TID P UID PRFLAGS PFLAGS CPU COMMAND > > > *390667 43405 0 0x3 0 0K ifconfig > > > db_enter() at db_enter+0x10 > > > panic(ffffffff81e3ccaf) at panic+0x12a > > > mii_phy_setmedia(ffff80000017e800) at mii_phy_setmedia+0x154 > > > ukphy.service(ffff80000017e800,ffff800000465730,2) at > ukphy_service+0x69 > > > mii_mediachg(ffff800000465730) at mii_mediachg+0x58 > > > bge_stop(ffff800000465000,0) at bge_stop+0xc29 > > > bge_init(ffff800000465000) at bge_init+0x2a > > > bge_ioctl(ffff800000465048,8020690c,ffff800000a91900) at > bge_ioctl+0x2d5 > > > in_ifinit(ffff800000465048,ffff800000a91900,ffff800023797410,1) at > > > in_ifinit+0xf3 > > > in_ioctl_change_ifaddr(8040691a,ffff800023797400,ffff800000465048,1) at > > > in_ioctl_change_ifaddr+0x385 > > > in_ioctl(8040691a,ffff800023797400,ffff800000465048,1) at in_ioctl+0xfb > > > ifioctl(fffffd81f70c3008,8040691a,ffff800023797400,ffff8000237b6d28) at > > > ifioctl+0xa2d > > > soo_ioctl(fffffd8218c77870,8040691a,ffff800023797400,ffff8000237b6d28) > at > > > soo_ioctl+0x171 > > > sys_ioctl(ffff8000237b6d28,ffff800023797510,ffff800023797570) at > > > sys_ioctI+0x2d4 end trace frame: 0xffff8000237975d0, count: 0 > > > https://www.openbsd.orgiddb.html describes the minimum info required > in bug > > > reports. Insufficient info makes it difficult to find and fix bugs. > > > ddb{0}> > > Thanks for sending that as text rather than just a photo :) > >
