Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Red Hat Software Businesses

Kernel 2.2.1 RPMS 38

An anonymous reader writes " has finally put the 2.2.1 RPMS on their site. It seems to be Kernel 2.2.1 release 3. "
This discussion has been archived. No new comments can be posted.

Kernel 2.2.1 RPMS

Comments Filter:
  • As in, 2.2.2-pre2?

    What is it about RedHat that stops them understanding about "PRE-releases"? I.e. ones Linus doesn't want the world and her husband using, only the developers?
  • I have kernel-package installed and I really am into having as much stuff as possible on my system registered with dpkg (I even make WindowMaker themes into .debs []), but I don't know why I would want to use kernel-package? What are the benefits over make install, given that kernels only install a couple of files in /boot and a directory in /lib/modules?

  • What worked for me on 5.2: Get all update rpms for your CPU from the 5.2 updates directory and also get the kernel-2.2 directory from there. Contrary to what the name says this does not (did not?) contain actual kernel rpms but other rpms that are required for 2.2 on RedHat.

    Then, download a regular kernel-2.2.1.tar.gz (or bzip) from a place like Rm /usr/src/linux (it's just a link to /usr/src/linux-2.0.36) and extract the kernel tar file to /usr/src. It will extract to plain 'linux', so after extraction mv it to /usr/src/linux-2.2.1 and make a link (ln -s /usr/src/linux-2.2.1 /usr/src/linux). Then you can go into the dir and make your config as usual.

    Note the file /usr/src/linux/Documentation/Changes, it has an extensive list of minimum version numbers of all sorts of support files that you need. If you've gotten all the update rpms from the Red Hat site your Linux system will be almost completely up to the requirements listed. The 2 or 3 minor differences don't seem to hinder my system.

    Don't forget to put the zImage in the right place and to rerun lilo after you compile your kernel. Then have a look at the file /lib/modules/2.0.36-3/.rhkvmtag and make a similar one in /lib/modules/2.2.1. Use something like 'strings /usr/src/linux/vmlinux | grep "Linux version"' to get the proper text. Now you should be ready to go..
  • Dammit, I accidently hit the Submit button to early (by some freak combination of keystrokes: tab, then space, I think). :-)

    As I was going to say I'm getting these new messages in /var/log/messages when I try to dial out to my ISP under the new 2.2.0 kernel (I'm not sure what revision is). I don't remember those messages verbatim (I'm not at my own machine right now), but they say that modprobe couldn't find modules of these names:


    Or something like that, I'm not sure if I remember the numbers at the ends correctly.

    Anyway, pppd seems to work fine and successfully dials in to my ISP. I just wondered what might be causing the messages. I checked /lib/modules/net and I saw that ppp.o and ppp_deflate.o were in there. Anybody else getting strange messages like these? Could it be that pppd needs updating (I think the number to mine is: 2.3.5)?

  • Perhaps I'm just lucky. I printed off the Redhat directions linked by /. on Friday (2/19/99), downloaded the required RPM updates, downloaded the latest source tar ball, spent a LOT of time tweaking the config parameters and reading the config parameter help messages, built my kernel, and it WORKED the first time.

    Indeed, I'm running 2.2.1 on Redhat 5.2 as I type this. This system is a generic Pentium 133 (no MMX) with 48MB ram.

    My next step will be to upgrade my other system--a Pentium II/450 running S.u.S.E 5.3. Has anyone spotted upgrade instructions for S.u.S.E.?
  • arn't they linked against the newest glibc?
    if so, then if will screw your sytstem up something royal. anyway, let me get it anyway... i hope they have the src rpm to it, that way i can link it against my libs...
    so i believe....
  • i just went looking, but unless i am completly blind, i do not see them....

    any idea where exactly they are?
  • in the directory, there are two particular rpms that i would like to know what they do. the first is:
    and the other is:

    i guess that the smp rpm is one with smp support already compiled in, but what does the other one do?
  • They all fscked up ... the kernel headers and sources RPMS are 2.2.1-ac5; the kernel RPM is 2.2.1-3, the pcmcia stuff is compiled against 2.2.1-ac5 .

    I had a hell of a time getting it to work (NONE of the modules would load, it's a long story) and dumped and went back to 2.0.36.

    Also, why can't we have "i386" only kernel tarballs or RPMs? It would certainly make them smaller/easier to download.

    I think laptop users should especially avoid this for now ... any laptop users out there using 2.2?

  • They don't even have a non-corrupt copy of the glibc RPMS, no SRPMS, and the same case for a buch of other packages. What's up here? Too much crack in somebody's coffee?
  • From my experience, running kernel 2.2.x or 2.1.x on top of Redhat 5.2 is best done by getting the kernel source from, or your local mirror where available. I've also managed to get them running on my Alpha box running 5.1. I upgraded to EGCS 1.1.1 on both machines, and checked to make sure I had the latest stable libc installed. Other than that, I had no problems getting the kernel compiled and running.
  • I'm running a SB16 PnP which worked fine under 2.0.36, but which doesn't work under 2.2. I get the fabled "device or resource busy" when initializing the sb module. Has anyone had any luck with a similar setup?

  • I believe FAT32 support came in at 2.0.34, I'm
    sure someone will correct me if I am wrong. 2.0.36
    definitely has support for FAT32. The end of your
    message was snipped, but try upgrading pppd.
  • I have 2.2.1 running on a Toshiba Satellite 4000 CDT. I could not get the RawHide packages to work, so I compiled it myself. No problems thus far
  • After downloading and compiling 2.2.1 I had problems with the printer as well.(RH5.2)

    I had to do two things to fix it, the new kernel printer drivers get installed as /dev/lp0 for the first parallel port regardless of the I/O, interrupt settings. Change your printer configuration to point to /dev/lp0 instead of /dev/lp1.

    The other problem was in my selection of the kernel config. I selected Parallel Port support/pc style hardware from the General setup menu but I missed "parallel printer support" under the character devices menu.

    Hope this helps,

    Chuck Moss
  • Hey, just follow the instructions, upgrade the modules they have, make the bootdisk for safety, (personally I always have a way to back out in LILO), and download the tar file from

    It was a cake walk. And guess what?

    I realized after building and booting it, that I did not remember to back out of PGCC and use gcc.

    HA HA HA. My kernel is screaming and its compiled with

    pgcc -06 -funroll-all -mpentiumpro -march=pentiumpro -fno-reduce-strength

    I made it with the make bzImage and it never even hiccupped.

    Im on a pII 300 with 96M and a 8M Matrox MII. Ultra Wide Cheetah drive. I did have to make a initrd-2.2.1.img for my aic7870.

    Rocket fuel 'o kernel. I am a satisfied customer.

    Thank you Linus, Al, and all involved. It was worth the wait.

If a thing's worth having, it's worth cheating for. -- W.C. Fields