I just wasted an hour trying to figure out why xorg had strange output but no errors on this laptop, and it’s because I had i915_load=”YES” in /boot/loader.conf instead of i915_load=”YES” in /etc/rc.conf. I’m almost nearly sure I’ve mentioned that before, but if not: here you go.
(though if you never plan to run X, you can put it in loader.conf and everything will just work.)
(Title updated for a more correct sentence)
Been there, done that, put in an Nvidia card on a desktop. Yes, I know that’s not an option on a laptop.
> Been there, done that, put in an Nvidia card on a desktop. Yes, I know that’s not an option on a laptop.
Or you can get a laptop with nvidia and a sufficient battery.
Intel’s drivers have been getting worse for a while. Hope they concentrate on stability soon.
> though if you never plan to run X, you can put it in loader.conf and everything will just work
Is that for the virtual console and does it mean if I put it in rc.conf, the console will be non-functional but Xorg will work?
mikegpu – if you put it in rc.conf, the virtual console will still work. It just loads a few seconds later.
I haven’t tried moving the load of drm.ko into rc.conf to see if that combo works any better yet.
Are you sure you headline is correct?
It seems reversed:
kldload(8) is for loading kernel modules after kernel is booted.
load is for loading modules from loader(8), i.e. before kernel is booted.
/etc/rc.conf is configuration options for after kernel boot.
/boot/loader.conf is configuration options for loader(8).
How about man pages: is working order documented there?
I didn’t find mention of /boot/loader.conf vs /etc/rc.conf in i915(8) (which links to i915kms(8)).
Putting drm_load=”YES” in rc.conf works too. That doesn’t really change anything.
Ok, seem like header should be: “Do kldload i915” or “Don’t load i915 from loader”
Thomas – you are right. It’s a kernel load no matter what; so it’s timing that matters.
Yeah.. encountered that issue, when I upgraded my DFBSD 4.8 to 5.