amd64/163442: boot/loader.conf not processed at boot time

John Baldwin jhb at freebsd.org
Tue Dec 20 13:01:02 UTC 2011


On Monday, December 19, 2011 1:26:06 pm Thomas D. Dean wrote:
> On Mon, 2011-12-19 at 07:30 +0000, Rainer Hurling wrote:
> >  
> >  For me it is nvidia_load="YES" and cpuctl_load="YES" which works in 
> >  /boot/loader.conf. Could you please try it?
> 
> Sorry, typo - I am not posting email from that machine, yet.
> 
> I tried nvidia_load="YES" and cpuctl_load="YES" in /boot/loader.conf
> The modules were not loaded at boot time.  I can manually load the
> modules after login.
> 
> # ssh <ip address> cat /boot/loader.conf  
> cpuctl_load="YES"
> nvidia_load="YES"
> linux_load="YES"
> 
> I checked for strange characters.
> # ssh <ip address> hd /boot/loader.conf
> 00000000  63 70 75 63 74 6c 5f 6c  6f 61 64 3d 22 59 45 53  |
> cpuctl_load="YES|
> 00000010  22 0a 6e 76 69 64 69 61  5f 6c 6f 61 64 3d 22 59
> |".nvidia_load="Y|
> 00000020  45 53 22 0a 6c 69 6e 75  78 5f 6c 6f 61 64 3d 22  |
> ES".linux_load="|
> 00000030  59 45 53 22 0a                                    |YES".|
> 00000035
> 
> I am up-to-date with cvsup and supfile containing
>    *default release=cvs tag=RELENG_9

You need to try to capture a verbose dmesg.  Also, try booting with
the beastie menu disabled so you can see any errors from the loader when it 
tries to load the modules.

-- 
John Baldwin


More information about the freebsd-amd64 mailing list