boot/device.hints
-
You can set device hints in loader.conf.local and they will be kept.
Neither device.hints nor device.hints.local is retained though as far as I'm aware. I spent some time testing it a while ago.
Steve
-
@stephenw10
Thank you so much :) ! -
Do I just copy the entire contents of device.hints to loader.conf.local?
My problem is I can't boot unless I comment out:
#hint.uart.0.at="isa" #hint.uart.0.port="0x3F8" #hint.uart.0.flags="0x10" #hint.uart.0.irq="4" #hint.uart.1.at="isa" #hint.uart.1.port="0x2F8" #hint.uart.1.irq="3" -
@stephenw10 said in boot/device.hints:
You can set device hints in loader.conf.local and they will be kept.
I read this thread and something is not quiet clear to me: setting device hints in loader.conf.local - OK, but how deactivate existent hints (in /boot/device.hints) in loader.conf local? In my opinion the deactivation has to be done every time a update/upgrade is taking place.
-
Indeed, I can't see any way to unset a hint. But you could set it to something else. Or in this case if it won't boot with the uarts setup at the standard locations you could disable them entirely:
hint.uart.0.disabled="1" hint.uart.1.disabled="1"Steve
-
This is what I do to get it to boot initially and then edit the device.hints for future reboots but it doesn't stick through upgrades/updates.
Here is the link I found to help me to get it to bootup the first time. It was a head scratcher for a little while:
https://www.neelc.org/posts/hp-t740-freebsd/
I was just checking to see if there was a way to not have to do this through upgrades. I'm not even sure what those are for lol
-
Ok, well I would try:
hint.uart.0.at="0" hint.uart.1.at="0"But setting it disabled there is probably just as good. There is probably some resource conflict caused by the serial ports on the device for some reason.
Steve
-
Yes these work for first boot if you interrupt no problem, they just don't persist without commenting out the above lines and those don't persist through updates/upgrades.
Just a pain because this is setup in a closet without a keyboard and monitor, so there is no way to update/upgrade without taking it out of the closet etc...
-
Right which is why you need to put them in /boot/loader.conf.local which is maintained across an upgrade.
-
Ohhh okay, took me a while to get there lol
So just add:
hint.uart.0.disabled="1" hint.uart.1.disabled="1"to the loader.conf.local and all should be good?
-
You'll have to test to know if that works. Be sure to have console access in case it doesn't boot!
-
-
@stephenw10
This did work!Thank you so much :)
-
Great to hear.
-
@stephenw10 said in boot/device.hints:
Right which is why you need to put them in /boot/loader.conf.local which is maintained across an upgrade.
Would you please so friendly and take a minute on top to this file called /boot/loader.conf.local please.
If I write something in, like the thread opener his line,
and I have several different line to put in for several things
and I want comment this line for what they are standing,
how to do this without problems? as an example:set CPU Frequent high up to 1400 MHz hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 hint.acpi_perf.0.disabled=1 -
The octothorpe
#indicates a comment so you could do:# CPU Power and Frequency settings set CPU Frequent high up to 1400 MHz hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 hint.acpi_perf.0.disabled=1 -
@stephenw10
Thank you!Here is none active and;
# set CPU Frequent high up to 1400 MHz #hint.p4tcc.0.disabled=1 #hint.acpi_throttle.0.disabled=1 #hint.acpi_perf.0.disabled=1here are all active, is this rigt?
# set CPU Frequent high up to 1400 MHz hint.p4tcc.0.disabled=1 hint.acpi_throttle.0.disabled=1 hint.acpi_perf.0.disabled=1I will try out this for my new installation on CP Engines APU to tune the CPU is able going something between
1000Mhz and 1400Mhz against default 600Mhz to 1000Mhz. -
That's correct.
-
Thank you very much for that information.
