Beta

Slashdot: News for Nerds

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Kernel 2.2.1 RPMS

CmdrTaco posted more than 15 years ago | from the stuff-to-smash-around dept.

Red Hat Software 38

An anonymous reader writes "rawhide.redhat.com has finally put the 2.2.1 RPMS on their site. It seems to be Kernel 2.2.1 release 3. "

cancel ×

38 comments

/.'d already (0)

Anonymous Coward | more than 15 years ago | (#2009786)

I just tried to get to their instructions posted yesterday and got timed out. Are they already /.'d?

Kernel is Screwy (0)

Anonymous Coward | more than 15 years ago | (#2009787)

I got the kernel RPMs yesterday and you know what? It did me no good! Sure now I'm using a 2.2.1 kernel, but I'd much rather have compiled one myself. Funny story about that...Redhat 5.2 is supposed to be kernel 2.2 "ready" according to redhat. And for the most part it is.....but I got the kernel 2.2.1 source and guess what it won't compile, d'oh! Well I guess this is just another way of showing that it's always best to do things yourself, otherwise they won't be done right. Shame on RedHat for tricking stupid people like me. Oh well, I'm off to try and compile my kernel.

nonsense (0)

Anonymous Coward | more than 15 years ago | (#2009788)

Sorry, you're talking nonsense. The kernel isn't linked against any libc. It provides its own implementations of functions like strlen().

Here they are (0)

Anonymous Coward | more than 15 years ago | (#2009789)

Try Rufus: rufus.w3.org (homepage)
Or : http://rufus.w3.org/linux/RPM/rawhide/1.0/i386/Red Hat/RPMS/kernel-2.2.1-3.i386.html (downloadpage)

Have fun!

been there (0)

Anonymous Coward | more than 15 years ago | (#2009790)

I pulled it down 2 days ago. The RH 5.2 upadte rpms, plus the rpms from the rawhide ftp site are running just fine in an old amd 5x86 133 box. It's just a storage box for mp3's, so not a big load, but no problems so far.

i no see them? (0)

Anonymous Coward | more than 15 years ago | (#2009791)

Is this running on anyone's RH5.2 system?

Rawhide.redhat.com packages are experimental! (0)

Anonymous Coward | more than 15 years ago | (#2009792)

You shouldn't blindly assume rawhide stuff will work. Treat it with caution.

get your .debs here (0)

Anonymous Coward | more than 15 years ago | (#2009793)

for anyone who's interested, Debian's had .debs available [debian.org] for some time now...

2.2.1 "release 3" (0)

Anonymous Coward | more than 15 years ago | (#2009794)

Perhaps you misunderstand the RPM package number
and release number. The package number (in this case 2.2.1) refers to the pristine linux-2.2.1.tar.gz tarball embedded in the src.rpm. The release number refers to changes in how the tarball is patched, configured, or installed in the spec file (with version comments hopefully logged in the %changelog section).

Once again, early birds get screwed (0)

Anonymous Coward | more than 15 years ago | (#2009795)

Guys, wait for the CD. Only 2% of you could possibly need the new kernel - for everyone else you simply causing yourself grief for no real reason!

SRPMS (0)

Anonymous Coward | more than 15 years ago | (#2009796)

If you want it to work, then just get the kernel SRPM, and tweak it you your hearts content.

rpm --rebuild kernel-2.2.1-3.src.rpm if you are lazy...

Kernel is Screwy (0)

Anonymous Coward | more than 15 years ago | (#2009797)

RedHat have an example kernel 2.2.1 configuration
that I got last night. When I ran make bzImage it
bailed out with bad reference errors, so I went back to my standard config and all went well (on 2.2.2-pre5).

Kairuri

bugger off (0)

Anonymous Coward | more than 15 years ago | (#2009798)

live on the edge ?!?!? ... are you *seriously* telling me that *trying hard* to get a kernel to compile is like some sort of macho sport ? .. get a life..

Seems quite reasonable to get a CD as it saves on long downloads !

2.2.1 "release 3" (0)

Anonymous Coward | more than 15 years ago | (#2009799)

The world and her husband read slashdot....

one more thing... (0)

Anonymous Coward | more than 15 years ago | (#2009800)

smp = symmetrical multi-processing

Dear Idiot, (0)

Anonymous Coward | more than 15 years ago | (#2009801)

>As in, 2.2.2-pre2?

No, as in the third RPM Red Hat has made of the 2.2.1 kernel.

> What is it about RedHat that stops them understanding about "PRE-releases"?

What is it about Slashtwatters that they always want to dis Red Hat when it's obvious they have not a clue what's going on?

Once again, early birds get screwed (0)

Anonymous Coward | more than 15 years ago | (#2009802)

How wrong!! I have (after a bit of... fun) upgraded my kernel to 2.2 (from sources, not RPMS) it's the best upgrade I've done to my computer in a while. Everything is MUCH faster. Ny rough estimates is that Netscape loads in 4 seconds, where it used to take 10+

I think that anyone that's up to trying new kernels should go for it!! The difference is huge!

Upgrade Motivation Survey (0)

Anonymous Coward | more than 15 years ago | (#2009803)

I am taking a survey on redhat-list asking why everyone is upgrading. The response hasn't been tremendous, but I will tally next friday and report there.

I didnt have any probs (0)

Anonymous Coward | more than 15 years ago | (#2009804)

But I can see where newbies would be getting screwed :). one thing just remember to have a fallback if you kernel is hosin.

2.2.1 and system lock ups (0)

Anonymous Coward | more than 15 years ago | (#2009805)

My plus several people I know have been experincing complete system lock ups when using Kernel 2.2.1, It compiled no problem for me. But after 2-3 days of up times, the system just freezes itself completly. Me thinks 2.2.1 isn't all that stable.

Kernel 2.2 don't work at all! (0)

Anonymous Coward | more than 15 years ago | (#2009806)

Every time I try to boot using the new kernel, i get only so far and then my monitor goes berserk!
Colours and lines everywhere! I have a feeling it might be my DVD Video card, maybe the new kernel sees it and thinks its a primary? (I have three video cards: Voodoo, Diamond Monster, & Creative DVD)

Kernel 2.2 don't work at all! (0)

Anonymous Coward | more than 15 years ago | (#2009807)

I have an 8 meg ATI Xpert.....hmmmmm

2.2.1 "release 3" (1)

stevied (169) | more than 15 years ago | (#2009808)

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?

kpkg benefits? (1)

Daniel (1678) | more than 15 years ago | (#2009809)

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 [brown.edu] ), 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?

Daniel

Try this on RH 5.2.. (1)

florin (2243) | more than 15 years ago | (#2009810)

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 ftp.kernel.org. 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..

Upgrade Motivation Survey (1)

David Bice (3723) | more than 15 years ago | (#2009811)

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:

ppp-compress-21
ppp-compress-24
ppp-compress-56

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)?

No Problems for Me (1)

Bolen (4896) | more than 15 years ago | (#2009812)

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 kernel.org 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.?

what glibc? (1)

datazone (5048) | more than 15 years ago | (#2009813)

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 no see them? (1)

datazone (5048) | more than 15 years ago | (#2009814)

i just went looking, but unless i am completly blind, i do not see them....

any idea where exactly they are?

one more thing... (1)

datazone (5048) | more than 15 years ago | (#2009815)

in the directory, there are two particular rpms that i would like to know what they do. the first is:
kernel-BOOT-2.2.1-3.i386.rpm
and the other is:
kernel-smp-2.2.1-3.i386.rpm

i guess that the smp rpm is one with smp support already compiled in, but what does the other one do?

actually it's version 2.2.1-ac5 (1)

cthonious (5222) | more than 15 years ago | (#2009816)

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?

what glibc? They don't even have it (1)

Rahul (5626) | more than 15 years ago | (#2009817)

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?

Rawhide means "Experimental" (1)

DarkDave (7642) | more than 15 years ago | (#2009818)

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 ftp.kernel.org, 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.

sound in 2.2 (1)

woggo (11781) | more than 15 years ago | (#2009819)

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?


wog

2.0.34+ supports FAT32 (1)

Tim Sutherland (11914) | more than 15 years ago | (#2009820)

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.

Laptops and 2.2 (1)

OliverH (13654) | more than 15 years ago | (#2009821)

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

been there (1)

cmoss (14324) | more than 15 years ago | (#2009822)

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

2.2.1 with ROCKET FUEL! (1)

gnut (18602) | more than 15 years ago | (#2009823)

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 kernel.org.

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.
Check for New Comments
Slashdot Account

Need an Account?

Forgot your password?

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>
Create a Slashdot Account

Loading...