Kernel 2.6.12 released
 

Get it from kernel.org or selected mirrors. No full changelog as linux lost it =)
Let it rip!

cool!

He lost it :D

I am assuming you mean Linus btw ;)

Cool

Linus didn't lose it...you need to read his announcement more closely.
They stopped using BitKeeper and Linus wrote his own software, which
he calls git. So now the changes are in 2 places, but he tells you in the
announcement on LKML how to "puzzle it together" to get all the changes.

There are a couple of "gotchas" in this one so far. If you've written udev
rules, then you should have udev upgraded to udev-0.58 and with some
sound cards ALSA settings are changed when recompiling. I have a
Creative Labs SB Audigy ES, and after installing 2.6.12 I only had sound
from the front speakers of my 5.1 setup. That was easily solved by running
alsamixer again and adjusting the mixers.

Error
 

Downloaded the kernel image with .bz or .bz2 extension and extracted ,but it produces a single file called "patch" which is not recognisable to any tools

it's just simple text file with many comment and then some bash script and then the acctual c/asm code but all in a single file ,

Now what to do?

You got just the patch file, and not the full kernel. To get the full
kernel source go to the Linux Kernel mirrors ... and btw, it's now
at 2.6.12.1 :)

Edit:
And put it somewhere under your /home directory...I use
~/build/ and after you extract it read Linus' instructions in
the ./linux-2.6.12.1/README file. Don't use /usr/src/linux
like so many of these guides online say...they're wrong.

Here's a good guide, but I wouldn't use that System.map
symlink business at the very bottom of his instructions.
Otherwise, his guide is right.

Error in starting XServer in 2.6.12.1 kernel
 

Recently I downloaded and compiled the 2.6.12.1 Kernel (kernel-2.6.12.1.tar.bz2) and set it up properly in "grub.conf" as I am using the GRUB for booting. (I followed the README instruction in the kernel package).


After I start booting it gives no error and i can see familiar
loding XXXXX [OK]

and then when it switches to Graphics mode (i.e. XServer) it just hangs showing only the cross (X) cursor in black background . Instead of loading the GUI Login screen.


I had setup all necessery files (such as system.map, vmlinuz.2.6.12.1 ,initrd-2.6.12.1.img etc).




No error is presented in bootup screen, only problem is in loading XServer.
I am using Fedora Core 3 with Intel 865GBF motherboard with on board graphics card.

Can any body help me????????

I don't use GrUB, cause I never could figure it out...sorry.
But you should start your own thread. This one is for a
different reason, and you'll not get the exposure your
problem deserves here.

Agreed - technical questions related to kernel upgrades are better off in a separate thread, since they are not directly related to to news or a discussion about the changes/new features available in the latest kernel. My recommendation would be to first search for existing threads about this kernel (in the Software forum), but if no relevant threads are found, to start a new one. Good luck with it -- J.W.

I've heard this a couple of times but I can't understand WHY it is so bad. I am using another directory to build the kernel but I still want to know the reason why I am doing it. :P

The most important reason I can tell you is because Linus Torvalds says don't build in /usr/src/linux so I don't. I followed a well used guide in LQ once. It didn't work, so I stopped and read Linus README file that came with the kernel sources. I was building 2.4.18 iirc.

Here's two references, one which is almost 5 years old, the other which comes with every kernel source you get from The Linux Kernel Archives:
So, may I quote Linus from his instructions?
Let me ask all those who advise to build in /usr/src/linux a question.

Why do you all continue to persist in doing it your way, rather than following the instructions of the man who wrote the kernel?

Is this the way you guys do everything in *nix? Just strike out and follow any old guide on the internet, rather than reading the README of the man who wrote the program? Maybe that's why the same thread topics are continually repeated in forum after forum...too few people reading, and referencing, the instructions that come with the product.

I just built 2 new kernels this afternoon, and built them on both boxen where I always build them ... ~/build/linux-2.x.x.x/

Every night when my crontab backs up my ~/ directories, I've got all my kernels right there. If for any reason I have to install Slackware again, I only issue:
and I'm back in business again.

I fail to understand why anyone would build anywhere except where the instructions say to build...