+ Reply to Thread
Results 1 to 9 of 9

Thread: Linux 2.6.29-rc4 Kernel Released

  1. #1
    Join Date
    Jan 2007
    Posts
    6,690

    Default Linux 2.6.29-rc4 Kernel Released

    Phoronix: Linux 2.6.29-rc4 Kernel Released

    A week and a half has gone by since the release of the 2.6.29-rc3 kernel, but the fourth release candidate for the Linux 2.6.29 kernel is now available. This release is targeted at just addressing regressions, with most of the work being done within Linux drivers and architecture updates...

    http://www.phoronix.com/vr.php?view=NzA1MA

  2. #2
    Join Date
    Jul 2007
    Posts
    59

    Default

    Hopefully we will only see a few more RC's before release, I know there are quite a few people interested in testing out this new filesystem(btrfs). I usually don't compile my own kernels because I feel its a waste of time and energy, but with the introduction of btrfs I might just have to.

  3. #3
    Join Date
    Jan 2007
    Location
    Germany
    Posts
    1,594

    Default

    I am a bit worried that Ubuntu 9.04 is still shipping Linux 2.6.28. Anyone knows if they will switch to 2.6.29? I don't see a reason why they shouldn't.

  4. #4
    Join Date
    Aug 2007
    Posts
    5,495

    Default

    ext4 patches are backported also serveral alsa hacks, no real need to use 2.6.29. You would have to test lots of extra drivers against it. But 2.6.28 is at .4 upgrade level already with lots of bugfixes. In many cases 2.6.28 is a good choice, some have usb troubles with it or some mouse/keyboard problems which did not appear with 2.6.27, but for most users it works fine. Usually you need some bugfix releases till a new kernel is really stable.

  5. #5

    Default

    I would really like to see Ubuntu 9.04 use Linux 2.6.29. Though just since it's newer and gives me more stuff to play with and benchmark

  6. #6
    Join Date
    Jan 2009
    Location
    Columbus, OH, USA
    Posts
    295

    Default

    What, does Ubuntu prevent you from updating the kernel or something?

  7. #7
    Join Date
    Jul 2007
    Posts
    59

    Default

    Quote Originally Posted by Wyatt View Post
    What, does Ubuntu prevent you from updating the kernel or something?
    Ubuntu has always been a pain with compiling your own kernel. Mostly because of all the propitiatory software they include that is stuck to their kernels, so you have to start rebuilding tons of crap. I would say if you wanted to try out 2.6.29 I would use Debian or Slackware for doing it. Something simple that doesn't become intrusive like Ubuntu does.

  8. #8
    Join Date
    Jan 2009
    Location
    Columbus, OH, USA
    Posts
    295

    Default

    Quote Originally Posted by sc3252 View Post
    Ubuntu has always been a pain with compiling your own kernel. Mostly because of all the propitiatory software they include that is stuck to their kernels, so you have to start rebuilding tons of crap. I would say if you wanted to try out 2.6.29 I would use Debian or Slackware for doing it. Something simple that doesn't become intrusive like Ubuntu does.
    Wow, I didn't know that. I guess that's another reason for me to continue staying well-enough away from Ubuntu, then...

    I don't really want to stir up a huge debate or anything, but while "Linux for Human Beings" is a great slogan, if you can't do it without becoming intrusive and difficult is it really still in the spirit of using a Linux-based system?

  9. #9
    Join Date
    Aug 2007
    Posts
    5,495

    Default

    That's definitely incorrect. You can use your own kernel, but you have to create the initrd on your own when you use it or you may NOT use a root partition specification like

    root=UUID=whatever

    that needs an initrd which has udev included. When you use

    root=/dev/sdXY

    then it will boot without initrd if your kernel has support for the root fs and the controller - jaunty does not use modules for those anymore, so it will most likely boot without initrd as will - this does not apply to intrepid and older!

    In order to create an initrd if none was there just do:

    update-initramfs -c -k new-kernel-ver-you-just-installed-manually

    Then update the grub menu using:

    update-grub

    When you really installed the kernel correctly it will boot. Otherwise you made a fault.

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts