On 3/10/2014 4:03 PM, Larry Baird wrote:
On Mon, Mar 10, 2014 at 03:49:22PM -0400, Mike Tancsa wrote:
On 3/3/2014 10:48 AM, Larry Baird wrote:
This beta board runs coreboot, which is GPL'ed software. This means that it
is possible to submit a contribution that lets you boot FreeBSD 9.2 and 10.
Working with PC Engines to come up with a solution is the right way.
FWIW, I can boot FreeBSD 9.2 just fine on amd64 hardware (ASUS F2A85-M)
that also starts with coreboot.
FreeBSD has working on the issue from two directions.
1) John Baldwin <[email protected]> has made software changes to FreeBSD
head that work around the issue
(http://svnweb.freebsd.org/base?view=revision&sortby=date&revision=261243).
This issue was to be MFCed a few weeks back.
I am sure that John will MFC it at some point.
2) I worked with Jung-uk Kim <[email protected]> to develop BIOS patches to
give to PC Engines to provide back to SAGE. I received an updated BIOS
with this change the end of last week.
Hi,
I just got one of these boards to evaluate. I was trying to load the
watchdog, but no luck. There seem to be a few other errors too
amdsbwd0: ResetStatus0 = 0xf9
amdsbwd0: ResetStatus1 = 0x0b
amdsbwd0: memory base address = 0xfec000f0
amdsbwd0: <AMD SB8xx Watchdog Timer> at iomem
0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0
amdsbwd0: bus_alloc_resource for ctrl failed
device_attach: amdsbwd0 attach returned 6
USB seems to have some issues as well
device_attach: pcib4 attach returned 6
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> at device 20.5 on pci0
ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
ohci0: Could not map memory
device_attach: ohci0 attach returned 6
pcib4: <ACPI PCI-PCI bridge> at device 21.0 on pci0
pci4: <ACPI PCI bus> on pcib4
ohci0: <AMD SB7x0/SB8x0/SB9x0 USB controller> at device 22.0 on pci0
ohci0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
ohci0: Could not map memory
device_attach: ohci0 attach returned 6
ehci0: <AMD SB7x0/SB8x0/SB9x0 USB 2.0 controller> at device 22.2 on pci0
ehci0: 0x100 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
ehci0: Could not map memory
device_attach: ehci0 attach returned 6
acpi_button0: <Power Button> on acpi0
pmtimer0 on isa0
not sure of the NIC errors are issues too ?
re2: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port
0x3000-0x30ff at device 0.0 on pci3
re2: 0x1000 bytes of rid 0x18 res 3 failed (0, 0xffffffff).
re2: 0x4000 bytes of rid 0x20 res 3 failed (0, 0xffffffff).
re2: could not allocate MSI-X PBA resource
re2: Using 1 MSI message
re2: ASPM disabled
re2: Chip rev. 0x2c000000
re2: MAC rev. 0x00200000
miibus2: <MII bus> on re2
rgephy2: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus2
rgephy2: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,
1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow,
1000baseT-FDX-flow-master, auto, auto-flow
re2: Ethernet address: 00:0d:b9:33:11:c6
Start bios (version ?-20131224_111227-ubuntubuilderx64)
CPU Mhz=1000
10.0-STABLE FreeBSD 10.0-STABLE #2 r262153 i386
You will need to either update the BIOS or patch FreeBSD 10. The
patch associated with:
http://svnweb.freebsd.org/base?view=revision&sortby=date&revision=261243
applies cleanly to FreeBSD 10. The latest BIOS from PC engines for the APU
board is very noisy when it boots. Hopefully the code change will get MFCed
now that the APU board is generally available:
http://www.pcengines.ch/apu.htm
Where can I find the latest BIOS ? Its not on the website
Any reason why this has not been MFC'd ? Is there a downside to having
it applied / running with it ?
---Mike
Larry
--
-------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, [email protected]
Providing Internet services since 1994 www.sentex.net
Cambridge, Ontario Canada http://www.tancsa.com/
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "[email protected]"
