Announcement

Collapse
No announcement yet.

Linux 2.6.30 Kernel Released

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linux 2.6.30 Kernel Released

    Phoronix: Linux 2.6.30 Kernel Released

    Just as planned, Linus Torvalds has released the Linux 2.6.30 kernel. Linux 2.6.30 introduces the NILFS2 file-system, new and updated drivers, support for the Microblaze CPU architecture, and many other changes...

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

  • #2
    For all interested, h-online.com has a great overview about the changes and features of the new Linux kernel.
    http://www.h-online.com/open/Fine-tu...eatures/113478

    Comment


    • #3
      I use AMD Catalyst

      Comment


      • #4
        Are there any patches for Catalyst 9.5 to make it compatible for 2.6.30?
        Do i need to compile 2.6.30 with any specific option?

        Comment


        • #5
          Yep. And also a bug correction about latency in I/O scheduler concerning only amd64 builds.

          The bug is not completely corrected, but things seems to be far better then they were with previous kernel releases.

          Here's a link to the post in gentoo forums :
          http://forums.gentoo.org/viewtopic-t...ighlight-.html

          Comment


          • #6
            It is possible to patch fglrx for 2.6.30, when you look at this board you find it Minimal requirement as kernel patch is:
            Code:
            diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c
            index 61ddfa0..3d26c0b 100644
            --- a/arch/x86/mm/tlb.c
            +++ b/arch/x86/mm/tlb.c
            @@ -279,6 +279,7 @@ void flush_tlb_page(struct vm_area_struct *vma, unsigned long va)
            
                    preempt_enable();
             }
            +EXPORT_SYMBOL(flush_tlb_page);
            
             static void do_flush_tlb_all(void *info)
             {
            otherwise you will be out of luck as that symbol is used in the binary part. If somebody has got a better idea then let me know.

            Comment


            • #7
              I've just downloaded and compiled 2.6.30 on my main pc.
              Apparently it doesn't like it much though - kernel panic can't mount FS on /dev/sda2.

              Booting back in 2.6.29 using the same grub settings works fine though.. But only had 5 minutes to investigate so far
              Last edited by henricbl; 06-10-2009, 09:48 AM.

              Comment


              • #8
                Originally posted by henricbl View Post
                I've just downloaded and compiled 2.6.30 on my main pc.
                Apparently it doesn't like it much though - kernel panic can't mount FS on /dev/sda2.

                Booting back in 2.6.29 using the same grub settings works fine though.. But only had 5 minutes to investigate so far
                You're likely to have missed including a filesystem or sata driver or something when going through the kernel config.

                Comment


                • #9
                  You usually don't go through the kernel config at all. You simply clone the current config:

                  zcat /proc/config.gz > .config
                  make oldconfig
                  make -j4
                  make install_modules
                  make install

                  And that's it.

                  Comment


                  • #10
                    Mirv, RealNC:
                    Yep that's what I did. I copied my current .config in to the 2.6.30 folder

                    Comment


                    • #11
                      I'd recommend going through the config anyway (make menuconfig is my favourite). I typically copy the config, then check everything is ok as I've found that it doesn't always work properly. Can't hurt to look at the very least.

                      Comment


                      • #12
                        Yes, it is always better to do a make menuconfig (or equivalent). Besides, I even do a diff (-ruN) to check what is new (kind of a crude way, but works for me).

                        Aside, I was wating for the kernel.org page to be updated.

                        Comment


                        • #13
                          Absolutely not related to anything, but:
                          coverage of a eral release

                          Comment


                          • #14
                            Originally posted by mirv View Post
                            I'd recommend going through the config anyway (make menuconfig is my favourite). I typically copy the config, then check everything is ok as I've found that it doesn't always work properly. Can't hurt to look at the very least.
                            Same here. I always go through menuconfig or xconfig even on minor revisions. Sometimes a new feature or driver is added, something can have moved or whatever. Once you do that a few times you get quicker with just looking if everything is in place. Otherwise one can explain a panic also by a missing command line parameter in grub.conf (menu.lst). Or a specific issue with your HW and a new/reworked driver. But that should be rare. On should check all the output possible when having a panic. Most times I also just forgot an FS in the compilation on my root. Or I moved HDDs around and booted without use of UUIDs.

                            Comment


                            • #15
                              Originally posted by nkef View Post
                              Are there any patches for Catalyst 9.5 to make it compatible for 2.6.30?
                              Do i need to compile 2.6.30 with any specific option?
                              I remember only that I had to cut out fb-drivers since earlier they weren't working well with fglrx and vv. And having to use pci_find_something and export unused/obsolete symblos and stuff. But I have given up on all that since at the moment the free drivers do ok for me, okay, yet lack of 3d and powerplay on newer chips but that's to come soon hopefully. And they just work. With graphic VTs and kernels of all kind. Here they more often need a very recent kernel release to make full use of the HW.

                              Comment

                              Working...
                              X