Solved Cant boot from new kernel

wokko7

wokko7

Hi guys,
Running FreeBSD-11-CURRENT and I have been updating/building base with make buildworld etc.
But I cannot boot from kernel, I need to boot from kernel.old.
When I boot from /boot/kernel and it switches modes I get 'no signals found'.
Not sure how to debug this or what to do.
Any ideas would be much appreciated.
If you need any logs, I will upload what you need.
Thank you
David

Code: 
uname -a
'FreeBSD Ghost 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r297297: Sun Mar 27 13:06:52 AEDT 2016  root@Ghost:/usr/obj/usr/src/sys/GENERIC  amd64'

svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: https://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 298089
Node Kind: directory
Schedule: normal
Last Changed Author: pfg
Last Changed Rev: 298089
Last Changed Date: 2016-04-16 08:31:22 +1000 (Sat, 16 Apr 2016)
 
Hi,
try to update your sources and compile the kernel again. See if it solves the problem.
Did you modified the kernel configuration?
 
Thanks tetragir for your reply,
I have tried a few times updating sources and rebuilding the kernel but the same thing happens.
I am using GENERIC kernel.
 
I thought I would add my /boot/loader.conf just in case something is wrong or needs adding/removing from it.
Code: 
cat /boot/loader.conf
kern.vty=vt
radeonkms_load="YES"
radeonkmsfw_TAHITI_pfp_load="YES"
radeonkmsfw_TAHITI_me_load="YES"
radeonkmsfw_TAHITI_ce_load="YES"
radeonkmsfw_TAHITI_rlc_load="YES"
radeonkmsfw_TAHITI_mc_load="YES"
snd_hda_load="YES"
usb_load="YES"
umass_load="YES"
lindev_load="YES"
vmm_load="YES"
nmdm_load="YES"
if_bridge_load="YES"
if_tap_load="YES"

I have rebuilt the kernel a few times today but still the same, it is like radeonkms doesn't switch modes. And it cant get the signal out to my monitor.
 
Well, try to remove all radeonkms stuff. This is known to work unreliably. In my case, it just lead to non-functional 3D acceleration, but maybe other bugs are possible. It works perfectly when the modules are auto-loaded by starting the X-Server.
 
You must log in or register to reply here.
Back
Top