I'll be checking it out later today - hopefully randr-1.3 will be in x11 at that time.
KMS only took:szczerb wrote:Oh, come on guys, you know I enjoy it ;] I'm just looking forward to it, but also am quite bussy lately so it's always like "do I have the time to rebuild back and forth? oh, what the hell :D"
I'll be checking it out later today - hopefully randr-1.3 will be in x11 at that time.
Yeah, I know. Tried it a few times already but couldn't hibernate and randr wasn't really working.pdw_hu wrote:KMS only took:szczerb wrote:Oh, come on guys, you know I enjoy it ;] I'm just looking forward to it, but also am quite bussy lately so it's always like "do I have the time to rebuild back and forth? oh, what the hell"
I'll be checking it out later today - hopefully randr-1.3 will be in x11 at that time.
CONFIG_FB=y
CONFIG_FRAMEBUFFER_CONSOLE=y (tho i'm not sure this is needed)
CONFIG_DRM_I915_KMS=y
+ newest (non *-9999) stuff from x11 and ~ portage.

It adds eye-candy to the framebuffer console, here is it's homepage. I'd like to know this too. I use natural gentoo on 2.6.28 with vesa, but I think I read on a bugreport that vesa should be disabled when using intel+kms, and KMS should provide the fbsplash support that vesa would have provided. I can't find the bug report, so don't quote me on that.pdw_hu wrote:What's that?szczerb wrote:BTW How about fbsplash? Do you guys have it working right from the beginning (that is just after grub)?Is that the grub image? I haven't used that, but only the ncurses version




I tried this, and it seems this upgrade requires a rebuild of almost everything. So I'm back at libxcb 1.1.mrsaccess wrote:Second, using libxcb 1.2 from x11 overlay, xorg-server can not even start. Maybe it has to do with libXpm being unable to compile against libxcb 1.2 but I don't really know.

Code: Select all
szczerb@nomad ~ $ cat /etc/portage/package.keywords/kms
=media-libs/mesa-7.4_rc1
=x11-apps/mesa-progs-7.3
=x11-base/xorg-server-1.6.0
=x11-drivers/xf86-input-evdev-2.2.0-r1
=x11-drivers/xf86-video-intel-2.6.3-r1
=x11-libs/libXaw-1.0.5
=x11-libs/libXfont-1.4.0
=x11-libs/libXi-1.2.1
=x11-libs/libXrandr-1.2.99.4
=x11-libs/pixman-0.14.0-r1
=x11-proto/randrproto-1.2.99.4You're lucky. X doesn't start at all with 2.6.29 on my eeepc. Someone was more successfull?The first time I start X after a reboot I get this:
http://omploader.org/vMWZrMw

yeah, Donnie wrote about this in his blog too. I´m using --as-needed in one of my boxes and didn´t hit that "problem"; in my eeepc 901 i don´t use --as-needed and got a truckload of packages to rebuilt too.I tried this, and it seems this upgrade requires a rebuild of almost everything. So I'm back at libxcb 1.1.
you are not alone ( although i don´t know what model is yours and i haven´t tried 2.6.29 final yet): if i enable kms in 2.6.29-rc8 , X doesn´t work.You're lucky. X doesn't start at all with 2.6.29 on my eeepc. Someone was more successfull?
Thanks... I tried this. The builtin fb driver is called intel_fb (note the _). It worked better than intelfb - could do the native resolution, but when switching to X, the screen was black, a mouse pointer appeared, and nothing else.pdw_hu wrote:intelfb isn't needed with KMS. And it worksjamapii wrote:Note that I disabled KMS (according to the help it does not work with intelfb) and PAE (by selecting "High Memory Support (4GB)" losing a little RAM on x86).