I've been using the 2.6.x series of the kernel for quite some time and have been really happy with it, but with patching to the latest rc I ran into a little bit of a problem.

With my current configuration, which has been working since the first 2.6 stable, I haven't run into any problems. Right after patching to 2.6.3-rc1 though, I have been getting an error after trying to make the image. Any ideas or did I just do something bad?

root@Slackware:/usr/src/linux# make bzImage
SPLIT include/linux/autoconf.h -> include/config/*
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/asm-i386/asm_offsets.h
CHK include/linux/compile.h
CC drivers/video/fbmem.o
drivers/video/fbmem.c: In function `unregister_framebuffer':
drivers/video/fbmem.c:1282: error: structure has no member named `class_dev'
make[2]: *** [drivers/video/fbmem.o] Error 1
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2

if your just doing make oldconfig then try actually configuring it through menuconfig lately 2.6 has been going through a lot of configuration style changes, other than that it may well be that someone entirely broke the code with this revision so i suggest that you wait for the next one or final 2.6.3 or use the -mm branch which will get the fix for that more quickly or will have backed out the offending patch personally i dont see much gain in using the -rc tree unless your a developer its rare that they have something wonderful in there that is worth going through the problems and if you want to stay up to date just use -mm or some other patchset which keeps very current between releases

my favorite patchset is
http://forums.gentoo.org/viewtopic.php?t=132765
go there and you will find more than willing support for any problems as well as very current releases, they are based on 2.6.2-mm1 currently but have many of the patches from newer revisions plus a plethora of other wonderful goodies

and you should always remember the above when dealing with these prepatches ...

Nice of you to mention that . I just wanted to see if anyone has duplicated the error. After some playing around and it no longer seems my mistake, then perhaps I could report as a bug. Thanks for the advice though

Did you patch to a clean 2.6.2 tree? If not sure then start over with a fresh kernel install.

I just built 2.6.3-rc1 last night while I was asleep, and while I'm at work now and can't check, a quick look this morning seemed OK. I have framebuffer enabled for VIA chipset.

Sounds like a plan, but its 3:54am here and its time for sleep