PF Sense 2.4 with Asrock J3455-ITX
-
Just got this board and having the same issue on every reboot I have to start in safemode. I may have to reinstall and try the fix posted
-
that or install hyper v server and run it in a vm on same
https://www.techarp.com/bios-guide/hpet-mode/
-
did the latest 2.4.0-p1 fix it?
-
did the latest 2.4.0-p1 fix it?
Just tried 2.4.1 and still had the issue..
Cant even see it in the bugs list on the redmine page, so it seems we are left for stranded :'(
-
I have no issue with USB, my bios is reset to standard.
the only change I made was on " /boot/loader.conf "upgrade to 2.4.1 run without any problems
I guess, i am just lucky with the board -
unfortunately 2.4.1 had the same USB problems for me, but I just realized that I tested it with CSM enabled (support for legacy BIOS). I will try with that option disabled and see…
This will take some time as cutting internet access does not bode well with the family.Edit : correct definition of CSM
-
This worked for me:
Boot from image
- At first loader menu choose to boot in safe mode (6,3)
- Reboot (1) - Complete installation in safe mode
- Before final reboot choose to add manual changes (goes to prompt)
- Edit and add to /boot/loader.conf ( hint.hpet.0.clock="0" )
it survived reboot and upgrade.
Just tried this and it worked! (2.4.2)
For all the newbies out there this is what I had to write to get into the config file
edit /boot/loader.conf
also I got a promt during the loading screen, there i hit "Enter" and wrote "exit" before hitting enter once more and after that the loading of the installer continues. - At first loader menu choose to boot in safe mode (6,3)
-
Please don't use /boot/loader.conf, it gets overwritten on every single update of the system. Use /boot/loader.conf.local instead.
-
I am in the same dilemma on Asrock J3455B ITX. Currently, I am on 2.3.5 and there is an upgrade to 2.4.1.
Can I just go to Edit/Boot/loader.conf.local and paste hint.hpet.0.clock="0" on GUI and do the upgrade to 2.4.1? Or do I have to do a clean install?
-
You can leave the entry in /boot/loader.conf.local, the update/upgrade procedure won't touch the file in any way.