Asus E45M1-M PRO no longer booting since BIOS update

From: Alastair Hogge <agh_at_riseup.net>
Date: Mon, 08 Feb 2021 22:49:59 -0800
Hello,

Recently I wanted to resurrect and old AMD Bobcat (14h) for use with
kgdb over dconschat. The system booted a
FreeBSD-13.0-ALPHA2-amd64-20210122 without a problem. I noticed the BIOS
was ~9 years old, so I updated the to most recent version, which is ~5
years old. After the BIOS update, Any FreeBSD boot image I have tried as
far back as 11, no longer boots past the printed EFI framebuffer
information. NetBSD-9 and Kunubtu-20.10 all boot OK. I am not having
success with remote debugging via Firewire (I recall it used to be far
easier), even WITH_LOADER_FIREWIRE, I can still not attach a remote gdb
process. 

My other host which is connected to the E45M1 via Firewire reports when
the E45M1 is booting:
fwohci0: fwohci_intr_core: BUS reset
fwohci0: PhysicalUpperBound register is not implemented.  Physical
memory access is limited to the first 4GB
fwohci0: PhysicalUpperBound = 0x00000000
fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=2,
CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1)  (me)
firewire0: bus manager 1
fwohci0: fwohci_intr_core: BUS reset
fwohci0: PhysicalUpperBound register is not implemented.  Physical
memory access is limited to the first 4GB
fwohci0: PhysicalUpperBound = 0x00000000
fwohci0: fwohci_intr_core: node_id=0x00000001, SelfID Count=3,
CYCLEMASTER mode
firewire0: 2 nodes, maxhop <= 1 cable IRM irm(1)  (me)
firewire0: bus manager 1
firewire0: split transaction timeout: tl=0x14 flag=0x04
send: dst=0x00 tl=0x14 rt=0 tcode=0x4 pri=0x0 src=0x000

$ fwcontrol
2 devices (info_len=2)
node           EUI64          status    hostname
   1  00-0f-2e-01-00-00-67-4b      0
  -1  00-0f-2e-01-00-00-67-42      0

$ dmesg -a | grep -A3 Tex
fwohci0: <Texas Instruments TSB82AA2> mem
0xfc904000-0xfc9047ff,0xfc900000-0xfc903fff at device 4.0 on pci10
fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:0f:2e:01:00:00:67:4b

Any ideas on how I can restore FreeBSD on the hardware?

To good health,
Alastair
Received on Tue Feb 09 2021 - 05:50:08 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:27 UTC