device hints - modification, removal keeping

4o4rh

@stephenw10 may not be a problem, but i get a number of errors
e.g. ppc0: cannot reserve I/O port range

because the device has no parallel port.

if i remark them out, it goes away.

# hint.ppc.0.at="isa"
# hint.ppc.0.irq="7"

and this one

kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
driver bug: Unable to set devclass (class: atkbdc devname: (unknown))
# hint.atkbdc.0.at="isa"
# hint.atkbdc.0.port="0x060"
# hint.atkbd.0.at="atkbdc"
# hint.atkbd.0.irq="1"
# hint.psm.0.at="atkbdc"
# hint.psm.0.irq="12"

stephenw10

Right but none of that is actually a problem. Or at least I have never seen it be a problem, are you seeing an issue?

Steve

4o4rh

@stephenw10 well none of the errors, appear to be causing a problem. but it is hard to know if they do or they don't. But i am trying to get a clean boot out of the box, just one of the errors does cause a problem, i'm not immediately aware of.

I will open new threads for the other errors

4o4rh

Found the following error in the log.

pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pcib0: _OSC returned error 0x10
pci0: <ACPI PCI bus> on pcib0

Saw on a freenas forum, to add the below to get rid of this error.
hw.pci.realloc_bars=1

Doesn't make any difference for me.

4o4rh

get the following error in the log, imagine if it can't map the I/O port, this should cause some kind of problems being the r/t clock

atrtc0: <AT realtime clock> port 0x70-0x77 on acpi0
atrtc0: Warning: Couldn't map I/O.
atrtc0: registered as a time-of-day clock, resolution 1.000000s

4o4rh

Get the below errors, and guess they are probably related giving the number of comments on forums about ACPI problems/bugs with various BIOS.

FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
Firmware Warning (ACPI): 32/64X length mismatch in FADT/Gpe0Block: 128/32 (20171214/tbfadt-748)
ioapic0 <Version 2.0> irqs 0-86 on motherboard

acpi0: <ALASKA A M I > on motherboard
acpi0: Power Button (fixed)
unknown: I/O range not supported

stephenw10

All of those things are common on FreeBSD systems and are not an issue.

Please don't spam the board with threads, keep it in one thread where we can try to address this if you really feel it's necessary (it isn't).

Steve

delitrium

@gwaitsi How is this a pfSense problem?

stephenw10

That's a BIOS error. Get a fixed BIOS.

Or ignore it since it's not actually an issue.

Steve

jimp

None of these warrant individual threads. I merged them all. None of these are specific to pfSense. They are between your hardware and FreeBSD. Take this to FreeBSD.