[14:13] <Ng> do we load i915.ko in initramfs? (my actual question is do we default to modesetting being enabled now, I just don't see anything for that in /etc/modprobe.d)
[14:15] <Ng> (and would modesetting jump to the native mode of my laptop's panel, vs grub's 640x480 setting)
[14:19] <tormod> Ng, yes see bug 392039. and yes it should pick the panel native mode
[14:19] <ubottu> Launchpad bug 392039 in initramfs-tools "initramfs scripts hard-coded to load i915; blocks loading non-intel drm modules" [High,Confirmed] https://launchpad.net/bugs/392039
[14:20] <Ng> k
[14:20] <tseliot> Ng: no, we don't. Loading fbcon in the initramfs seems to be enough for me
[14:21] <Ng> ah
[14:21] <jcristau> loading fbcon without an actual fb driver won't do anything though
[14:21] <Ng> so is modeset=1 just the default?
[14:22] <tseliot> jcristau: hence the black screen on boot. KMS works well otherwise
[14:22] <tseliot> Ng: yes, that's the default AFAIK
[14:22] <Ng> ok
[14:22] <tseliot> (At least in ubuntu)
[14:22] <Ng> k
[14:24] <tormod> tseliot, the above bug is not fixed, so the initrd does load i915, right?
[14:25] <tseliot> tormod: if I load fbcon, then yes, I think it does. The resolution changes and KMS works
[14:26] <tseliot> dmesg showed something about KMS but I should check again
[14:26] <tormod> I am more thinking of what it does by default in karmic
[14:27] <tseliot> currently it's not loaded in karmic by default
[14:28] <tseliot> bug #431812
[14:28] <ubottu> Launchpad bug 431812 in sysvinit "i915: black screen on boot---fbcon loading (screen powers off); breaks (recovery mode), fsck, usplash, crypt password" [Critical,Confirmed] https://launchpad.net/bugs/431812
=== ripps_ is now known as ripps