Become a fan of Slashdot on Facebook

 


Forgot your password?
Close
typodupeerror
×
Upgrades Software Linux

Configuring the 2.6 Linux Kernel 279

Posted by CowboyNeal from the getting-one's-compile-on dept.
An anonymous reader writes "This article is the first in a series by William von Hagen on using the new Linux 2.6 kernel, with a special emphasis on the primary issues in migrating existing drivers, applications, and embedded Linux deployments to a Linux distribution based on the 2.6 kernel. Bill is the author of Linux Filesystems, Hacking the TiVo, SGML for Dummies, Installing Red Hat Linux 7, and is the coauthor of The Definitive Guide to GCC (with Kurt Wall) and The Mac OS X Power Users Guide (with Brian Profitt)." This looks to be a good series for anyone planning to migrate to Linux 2.6, and having done just that myself, I'll attest to wanting more documentation along the way.
This discussion has been archived. No new comments can be posted.

Configuring the 2.6 Linux Kernel More

Configuring the 2.6 Linux Kernel

Comments Filter:

  • Do it the easy way : Get Manadrake 10-beta2 (Score:5, Informative)

    by Anonymous Coward on Saturday February 07, 2004 @09:28AM (#8211296)
    Mandrake 10 will be the first major distro use Kernel 2.6. Download the beta here [mandrakelinux.com].

    Easy to install, just download the ISOs, burn to disk, reboot and the installer will appear.

    Make sure to REPORT ALL BUGS, unless you want to see the LG incident again.
  • I had not trouble installing it in Mandrake 9.1, all I had to do is two changes in ATI's wrapper.

    As for other drivers I need, they're all already included in the kernel.

  • They need a tutorial on this stuff? (Score:4, Insightful)

    by after ( 669640 ) on Saturday February 07, 2004 @09:31AM (#8211317) Journal
    > make menuconfig

    I have never compiled my kernel before, and today I jsut compiled the 2.4 version, installed and later compiled 2.6.1 and installed... all without any problems.

    Enough rant ;)

    I just like the config file method. Does this mean that I can keep my config file (for compiling the kernel) when I upgrade to the next stable? (keeping in mind that I have it customized)

  • slackware users out there (Score:5, Informative)

    by mfivis ( 592345 ) on Saturday February 07, 2004 @09:32AM (#8211324) Homepage
    I found this sticky at linuxquestions.org's forums to be most helpful in doing an easy and straightforward 2.6 compile on a slackware system. LinuxQuestions.org [linuxquestions.org]
    • I found this sticky at linuxquestions.org's forums to be most helpful in doing an easy and straightforward 2.6 compile on a slackware system.

      Compiling kernels on Slackware has always been easy and straightforward. Kernel 2.6 works out of the box (well, as out of the box as you can be for a source tarball) on Slack 9.1, without the need for patches, tweaking daemons etc. It just works. That's one of the reasons I switched to Slack early on when I was learning Linux. It's so simple, it's newbie-friendly.

  • Default (Score:5, Interesting)

    by Grey_14 ( 570901 ) on Saturday February 07, 2004 @09:34AM (#8211329) Homepage
    Whats with the default config for the kernel, it's not blank, it's a specific setup that looks like it's for a P4 with a specific network card and chipset, shouldnt the kernel config be bare? this is referring to source downloaded directly from kernel.org,

    • Re:Default (Score:5, Informative)

      by Torne ( 78524 ) <torne@wolfpuppy.org.uk> on Saturday February 07, 2004 @09:57AM (#8211431)
      The default x86 kernel config always used to be Linus's machine; I don't know if this is still the case. =)
    • I'm not sure how it is now that there are so many more developers on the kerrnel, but the kernel used to have its defaults set up for Linus' workstation. I do know that the default out of the box config was to use SMP, which is not going to work for about 99% of the people out there. I just checked to see if this was still the case, and yes, it does default to SMP. However, when I started configuring the kernel on an Itanium based machine, it did automatically fill in the blanks for setting up an Itanium

  • Usability? (Score:5, Interesting)

    by polyp2000 ( 444682 ) on Saturday February 07, 2004 @09:37AM (#8211339) Homepage Journal
    Is the 2.6 kernel "Usable" yet? By this I mean getting obscure hardware to work such as my USB Midi Interface, and what about proprietary drivers such as Nvidia's, will existing code compiled for 2.4 kernel work? or will you have to recompile stuff (IPTables for example). Im running a gentoo box. I've been toying with updating the kernel to 2.6 and I've been hearing that there are a lot of radical changes to the kernel, the performance enhancements are very exciting to say the least. But what kinds of headaches am I going to have with a real world (used as a desktop as well as a server) system?

    • Re:Usability? (Score:4, Informative)

      by lokedhs ( 672255 ) on Saturday February 07, 2004 @09:40AM (#8211362)
      Well, nVidia has support for their graphics cards on 2.6 [nvidia.com]. As for the other hardware you'll have to google yourself. The nVidia link wasn't paticularily hard to find.

    • Re:Usability? (Score:2, Interesting)

      by Anonymous Coward
      (A +5 Troll ? ..... anyway...)

      AFAIK, for drivers, if it works in 2.4, it's supposed to work in 2.6.

      iptables support is pretty much the same aside from having a gazillion new options to play with, and of course you'll need to recompile the iptable support in the kernel (what else? you're compiling the kernel anyway)

      Well, as far as I've been using 2.6, it's very much "usable", there aren't any show-stopping problems that I've encountered on any 2.6.0 + kernels of yet, and it's quite stable. (I have a 32 da

    • Re:Usability? (Score:4, Informative)

      by Weird O'Puns ( 749505 ) on Saturday February 07, 2004 @09:59AM (#8211440)

      Kernel 2.6 is very usable and stable. I've been running mm-sources since 2.5.5x and haven't had any major problems with it. There's hardly any need for recompiling packages (there are few exceptions though, mostly packages that install some kind of kernel module, svgalib for example). One thing you must do is to replace modutils with module-init-tools.

      Gentoo forums are relly your friend. There are tons of threads concerning 2.4 to 2.6 upgrade, including some howtos.

    • Re:Usability? (Score:5, Informative)

      by Spoing ( 152917 ) on Saturday February 07, 2004 @10:19AM (#8211511) Homepage
      1. Is the 2.6 kernel "Usable" yet?

      In sum, yes. As with any major kernel update you have to have the matching user space parts or many devices will not work. Required documentation is included with the kernel;

      1. README (case sensitive) and

        ./Documentation/Changes (as noted in README)

      Keep in mind that if you don't need support for specific hardware -- say, ISDN or PC-Card/PCMCIA -- you can skip updating those packages.

      Specific comment: Alsa is now the default sound system, and it needs updated supporting tools if you want to get a peep out of your audio. Point for point comments;

      1. By this I mean getting obscure hardware to work such as my USB Midi Interface, -- USB MIDI support is included, though I haven't tried it.

      2. and what about proprietary drivers such as Nvidia's, will existing code compiled for 2.4 kernel work? There are updates, and they work fine; install the same way as with 2.4. Check the normal places on Nvidia's site.

      3. or will you have to recompile stuff (IPTables for example). Im running a gentoo box. I haven't, though I don't have Gentoo (Fedora Core 1).

      4. I've been toying with updating the kernel to 2.6 and I've been hearing that there are a lot of radical changes to the kernel, the performance enhancements are very exciting to say the least. It's better for average use, and low latency apps should work much better (ex: sound processing), though I haven't noticed much of a speed boost. 2.4 was snappy already.

      5. But what kinds of headaches am I going to have with a real world (used as a desktop as well as a server) system? Rebooting. Checking the software versions. Looking at all the possible options in the 2.6.x kernel -- though this is much easier with the updated menus in the confiuration screens ('make xconfig' (QT)/'make gconfig' (GTK)).

      Normal precautions, nothing special.

    • Before doing anything, your hesitancy indicates you may want to backup [sysbotz.com] your system first.

      = 9J =

    • There's a good guide at the gentoo forums [gentoo.org].

      The first thing is pick a kernel; development-sources or mm-sources are the vanilla 2.6 kernel and one of the more expermental patch-sets respectively. Love sources ebuilds are also in the forums, and some people swear by them. Initially, I'd go for development-sources.

      Without repeating everything in the forums guide, you'll need to emerge module-init-tools, and re-emerge the nvidia-kernel ebuild. You shouldn't need to recompile much else. You also can unmerge t

    • kernel 2.6 and gentoo 1.4 (Score:4, Informative)

      by Frogg ( 27033 ) on Saturday February 07, 2004 @12:21PM (#8212152)
      I'm using kernel 2.6.x and gentoo 1.4, and I'm fairly new to linux. All my h/w (nvidia, sblive, adaptec-compat scsi, usb mouse + mp3 player) works very well.

      It wasn't as smooth an upgrade as I'd've liked, but, like I said, I'm fairly new to all this.

      When I first upgraded, I did get a lot of errors/warnings on boot, but I have since fixed them all.

      Ensuring you have the latest versions of hotplug and module-init-tools will help your migration to 2.6, as there are changes to h/w detection and module loading.

      Take care when doing make oldconfig from an earlier gentoo kernel - gentoo kernels have had various performance patched in them for some time, but -- if I recall -- these settings didn't all magically migrate across, as the gentoo kernel build flags and the official kernel build flags have differing names for these features between 2.4 and 2.6. Just remember to check all your options with make menuconfig or similar. Some other build flags have changed names too, including stuff for usb devices and (IIRC) framebuffers -- this will probably only catch you out if you're migrating settings from an older kernel.

      After building and installing my 2.6 kernel, I also installed the latest nvidia package from nvidia's website, and alsa-lib and alsa-utils (both 1.0.2, from portage)

      Also, there are changes to how some system stats/info is handled/reported - ensure you have an up-to-date version of procps, or top might give some cranky info... some tools that monitor memory levels (gkrellm, various gdesklets) will stop working because the output of /proc/meminfo has changed (the first few summary lines have been removed) -- fixes for this don't seem to exist yet.

      Other than the meminfo issue, kernel 2.6 hasn't broken anything (that I've noticed) on my gentoo system, and it appears to work very well.

      (Oh, kernel 2.6 did cause one of my drives to give warnings about unexpected DMAs every few mins, but that totally fixed itself once I stopped overclocking the CPU. The drive was running slower with a mis-firing DMA, but other than the warnings, no problems occured (YMMV). Something in 2.6 must be more timing sensitive or less tolerant of overcranked h/w speeds. NBD: my system is a few years old, the extra ~20% speed increase cannot is insignificant when compared to speeds of a modern CPU - it seemed a lot at the time!)

  • KernelWiki (Score:5, Interesting)

    by Bruha ( 412869 ) on Saturday February 07, 2004 @09:37AM (#8211344) Homepage Journal
    I've considered setting up a wiki for the Kernel to give people a place to file what they've learned about it and share with the general public. Anyone think this would help anyone?
    • I don't know... why don't we set up a wiki to dicuss this ;)

      Seriously, just go ahead and do it. If no one uses it, take it down.

  • is it so much different than 2.4? (Score:4, Interesting)

    by locknloll ( 638243 ) on Saturday February 07, 2004 @09:37AM (#8211345) Homepage
    I've only recently started using Linux on a day-by-day basis, and after installing Debian unstable I switched directly to 2.6, without ever compiling a 2.4 kernel. That worked without a hitch, so now I'm wondering if the difference is so big. I still have an old Pentium I around the house, and I'm thinking of making this one a firewall/IDS... and so far I'm not sure if 2.6 was a little overkill for that one...
    • You need 2.6 on a P1 about as much as you'd need a 500-hp enginge in a Yugo

      • Re:is it so much different than 2.4? (Score:5, Informative)

        by Trelane ( 16124 ) on Saturday February 07, 2004 @10:35AM (#8211565) Journal
        Speaking from experience (P1 100MHz, no MMX, 16MB RAM, 500MB disk), going from 2.4 to 2.5 was a beautiful, beautiful thing. Sure, it'll give you a ton more performance on a high-end box, but it makes a low-end box much more usable.
        • I'll second that. I'm running a Pentium III 667MHz with hardware specs pretty much in line for a system of that vintage. My sister has an AMD Athlon 2200+, decent specs. My system is running 2.6.0, hers runs Windows XP and 2.4.22 (she likes the games on Linux :). Care to guess which system *feels* faster?

          It's mine. Even when I'm compiling the latest kernel or listening to MP3s or running SETI@Home, or even doing all three at once, I have nary a skip or a hitch. The mouse and keyboard stuff is always
    • You can run 2.6 on a Pentium. You might need to set HZ=100 (like 2.4) instead of the default i386 HZ=1000 on 2.6. I've seen reports of people booting their low-memory 486 systems with 2.6 and HZ=100.

      -molo

  • 2.6 breaks KVM support (Score:4, Interesting)

    by Bill Hayden ( 649193 ) on Saturday February 07, 2004 @09:37AM (#8211346) Homepage
    As far as I can tell, there is no way to use a KVM with kernel 2.6 and still have mouse wheel support. It works until you switch away and back to Linux, at which point the mouse goes completely nuts and cannot be revived. Back in 2.4, there were two hacks to revive the mouse in this situation (switch VCs, or set the mouse protocol in X to "AUTO") but neither of these work in 2.6. Windows, needless to say, has no problems. You can supposedly pass a psmouse.noext parameter to the kernel at boot time to fix the craziness, but a) this would remove mouse wheel support, and b) I never got it work anyway. If you know a workaround, please post!

  • Importance of Documentation (Score:4, Insightful)

    by osewa77 ( 603622 ) <naijasms&gmail,com> on Saturday February 07, 2004 @09:42AM (#8211371) Homepage
    If more people put up articles like this to make it easier to use the popular open source software products it'd speed up rate of adoption a lot. If there was one on writing kernel modules ... ;-)

  • Configure your own kernel (Score:4, Interesting)

    by runen ( 689179 ) on Saturday February 07, 2004 @09:42AM (#8211372)
    The problem with building your own kernel is that you will always make it as slim as possible. Then each time you buy a new piece of hardware (USB-mouse, SATA hd, etc) you'll need to build it again (and you've thrown away the original .config of course :). Is there a configure everything (besides what's been specified as built-in) as modules?

    • Re:Configure your own kernel (Score:4, Informative)

      by blackrider ( 459412 ) on Saturday February 07, 2004 @09:46AM (#8211387) Homepage
      It wont solve the main problem, but you can enable the /proc/config.gz option in the 2.6 kernel, so you can access the old config at any time through the /proc interface.

    • Re:Configure your own kernel (Score:2, Informative)

      by Anonymous Coward
      You can always include almost everything as modules.

      Or alternatively you can take a kernel configuration of your favorite distribution and tweak it to your liking. Most distributions will include drivers for all common hardware as modules.

    • Re:Configure your own kernel (Score:5, Informative)

      by Neil Watson ( 60859 ) on Saturday February 07, 2004 @10:34AM (#8211558) Homepage
      When you add new hardware that is not needed at boot (e.g not a bood device), simply build the kernel feature to support your new device as a module. Install the module and you are ready to go. No rebuild or reboot needed. You don't throw away config files. You save them for later use. The config procedure gives an option to save your config to an alternate location.
    • I build slim kernels, but I always build everything I chose not to compile in as a module. Literally, everything. That way, when I get a new or exotic piece of hardware that I want to just start playing with (and not worry about recompiling the kernel), I just plug it in and hotplug gets it, or failing that, a quick modprobe and it's ready to go.

  • ITS AN ADVERT!!! (Score:5, Informative)

    by Anonymous Coward on Saturday February 07, 2004 @09:44AM (#8211378)
    This is just a very loosly disguised advert for TimeSys Linux

    Nothing any monkey cant work out in about five minutes (and if they cant they should not be cross compiling for embedded devices)

    Since most people dont RTFA this isnt a problem, if you are one of the many... dont bother - its S**T

  • More binaries needed (Score:5, Interesting)

    by inf0mike ( 676125 ) on Saturday February 07, 2004 @09:53AM (#8211419) Journal

    I think this will turn out to be a great series of white papers helping people get to grips with the process of configuring and compiling their own kernels, but I have to say that I think there would be faster progress on new kernels if the was some central repository of precompiled binary packages for the major distros throughout the development cycle.

    The truth of the matter is that now linux is gaining wider acceptance, the community is filling up with more and more noobs and we should be doing more to help them understand the "new" (to them) technology. We also need to remember that not everyone who wants to use the software needs to be some sort of guru.

    This article is a great start to moving more people to the new code quicker, but regular up to date debs/rpms for all the current distributions will push that long even faster. I know someone will probably post saying "but there are packed versions for xxxx at somewhere.org", but they are often difficult to find for the noobs who just don't know where to look.

  • 2.6, X, and stuff (Score:5, Informative)

    by NixLuver ( 693391 ) <{stwhite} {at} {kcheretic.com}> on Saturday February 07, 2004 @10:01AM (#8211453) Homepage Journal
    The 'GUIFication' of the Linux kernel is interesting, but not mandatory. Make menuconfig still works, so you don't have to have X. Also, most of the bells and whistles related specifically to application space can be de-selected, so runaway featuritis is at least controlled.

    The 2.6 kernel is noticeably faster on my dual Athlon 2100+mp, at the user interface; X is faster than I've ever seen it before; the realtime scheduling is awesome.

    In short, as soon as you can reasonably do so, I recommend you migrate to the 2.6.x kernel.

  • just in time (Score:3, Funny)

    by POds ( 241854 ) on Saturday February 07, 2004 @10:06AM (#8211469) Homepage Journal
    Seems like just in time, hopfuly some future articles will give some insight into how to get ISAPNP sounds cards to work. For some reason my ISAPNP OPL3SA2 cards can not be found when i either compile support into the kernel or into loadable modules...

    seems like a few other people have this problem. Does anyone know the solution? Will i have to write the addresses of all the ports manualy and switch off ISAPNP for OPL3SA2?

  • One major problem in migration... (Score:4, Informative)

    by ThogScully ( 589935 ) <neilsd@neilschelly.com> on Saturday February 07, 2004 @10:40AM (#8211593) Homepage
    The foremost problem I had in migration was that SCSI emulation with ide-scsi is no longer used for CD burning. I expect many people making the upgrade will run into a problem with that.

    You can use the standard ATAPI ide-cdrom driver now to burn your CDs, but the userspace programs haven't caught up to this in all distros, especially the GUI ones. cdrdao just doesn't work last I checked, and while cdrecord works alright in the newer versions, many GUI frontend burners simply use cdrdao too much to be useful.

    Other problems I had were that lm_sensors changed a bit and I didn't find it important enough to upgrade to newer userspace stuff, but anyone who's relying on them for anything will likely want to know that it's changed and upgrades to userspace are necessary. The only other issue, which was fixed by a quick Googling was that the module system is changed and module-init-tools is now necessary for loading and unloading kernel modules.
    -N

  • That's great (Score:4, Interesting)

    by Apreche ( 239272 ) on Saturday February 07, 2004 @10:51AM (#8211642) Homepage Journal
    I didn't know about xconfig before! I really have to spruce up my install. I'm still using kernel 2.6.0 and I should probably up it to 2.6.2. My problem is I use gentoo and I have to configure the kernel manually. I know HOW to do it as in what make commands to issue in order to get a binary kernel out of the thing. And how to put the kernel in /boot and point my lilo at it. What I'm not always sure on is exactly which configure options I want on and off. The important ones are obvious. Yes I have an athlon. Yes I need my nfornce network card, emu10k1, silicon image sata, pre-emptible kernel etc. etc. But a lot of them I just have no clue. Some options have useful help messages like "if you don't know, just say Y (or N) it wont slow you down". But there are still a zillion modules and options in there that I have no clue if I should use Y M or N.

    We should make a repository of hardware configurations and which options should be turned on depending how you will use it. People should just say hey, I got this machine here with this hardware. I'm using it as a web server, and this is my kernel config. If enough people put there configs in, then people like me could find others with similar or identically matching hardware and use those configs. I'm sure it would also bring to light better configs for most people. I'm sure there's some guy out there not selecting a certain option who should be. And if he posts his config online some geek will be sure to point it out to him.
  • I'm about to get a new machine on which I want to install Linux. Which distro should I install that would already have the 2.6 included? Does Fedora? I'd like to save the time of not having to upgrade and configure a new kernel after just installing 2.4. Suggestions are welcome. Also, I'm a linux newbie so a distro with a good graphical installer is welcome.

  • 2.6 on NForce-based motherboards (Score:5, Informative)

    by FuzzyBad-Mofo ( 184327 ) <fuzzybadNO@SPAMgmail.com> on Saturday February 07, 2004 @02:01PM (#8212953)

    If you are upgrading an NForce-based machine to 2.6.x, save yourself some headaches and add "noapic nolapic" to the Kernel append string. I experienced repeatable hard lockups when doing disk intensive I/O until adding those parameters.

    Also, NVIDIA's nforce package is no longer necessary. The experimental forcedeth driver in 2.6.2 works quite well in my experience, and apparently an Intel sound driver works for the NForce onboard sound.

    See my latest journal entry for my account of migrating MDK 9.1 to a vanilla 2.6.1 kernel.

    • I experienced the same problem and solved it by excluding APIC support in the kernel configuration alltogether.

      I recall reading somewhere that disabling ACPI while keeping APIC enabled should also solve the issue. In other words: the problem apparantly only occurs when BOTH ACPI AND APIC are enabled on systems with Nforce2 chipsets.

      Wasn't there supposed to be a patch out there fixing this issue already? And if so, why hasn't it been merged in the tree by now? I know, I know, the 2.6 tree is still quite yo

Slashdot Top Deals

The truth of a proposition has nothing to do with its credibility. And vice versa.

Close