Post the output of

rpm -qa 'kernel*'

and show how much space you have left in /boot. The initrd image is created at run-time after package installation. You should be able to erase the 20.9 kernel package and reinstall it (with up2date or manually, doesn't matter).

Ok.. I did remove it (I still have the 2.4.20-20.9smp kernel in my up2date directory).
What I was wondering.. since I had to do the " linux dd " at install and specify my Acard aec6885 raid card and install the driver, could that be why the new kernel isn't being seen?
Do I have to compile a kernel based on the updated with the drivers?

Thanks for the reply

D.

No. That would not explain, why simple installation of a new kernel package didn't update the bootloader entries and didn't create the initrd image. But you're right, you may need to re-install the driver after a kernel upgrade.

Assuming you have enough free space in /boot, you can find out what you get when you go into the up2date spool directory and run rpm -ivh kernel-smp-2.4.20-20.9.i686.rpm (or whatever the file name is) to install the new kernel manually. It should add an entry in /boot/grub/grub.conf and also create a new initrd image in /boot. It won't remove the already installed kernels. So, don't fear anything.

Thanks for all the help misc
I will try the manual install tonight.

D.

OK...sorry to burden you all with another up2date problem, but I have been trying now for some days to fix this and am not getting anywhere....

I have updated to the new certificate (as described earlier)
I have updated the rpm's (as described earlier)

But I still get the same error message...

"There was some sort of I/O error: unsupported XML-RPC protocol. Exception exceptions.RuntimeError: 'Maximum recursion depth exceeded' in <method Server._del_ of Server instance at 81e5970> ignored

Can someone help??? I have no idea what this means....!

Are you behind a proxy server? What's your set-up and check the output of rpm -q up2date.

https://rhn.redhat.com/help/faq/#61
How do I use RHN behind a firewall or HTTP proxy?

If you do not have any way to access an HTTPS site on the Internet, you will not be able to use RHN. But, if you do have access, but via an HTTP proxy only, you can configure the HTTP proxy by setting the "proxyUrl" and "enableProxy" settings in the configuration files for rhn_register and/or up2date.

Refer to the RHN User Guide for specific instructions:
http://rhn.redhat.com/help/basic/up2date-config.html

well, I gave up on this red-hat-up-2-date service. Running RH8 it totally @#$( my system after updating. I guess it was too much drop and drag, click here and there.
:-)
/christian/

RH9 - up2date isn't up2date! ( post #1)

Hi All!

As per this bug fix for up2date:
https://rhn.redhat.com/help/latest-up2date.pxt

I installed the latest up2date.. and then attempted to update my package profile on the RHN servers with:

up2date -p

as root. It returned the following:

Error communicating with server. The message was:
Proxy Authentication Required


I am behind a firewall, so I tried the command with the correct proxy details:
up2date -p --proxy=proxy.monash.edu.au:8080 --proxyUser=user --proxyPassword=password
and still I got:

Error communicating with server. The message was:
Proxy Authentication Required

When I launch "RedHat Network Alert Icon" the "Available Updates" tab it does show some available updates but when I click "Launch up2date" either a) nothing happens at all or b) I get asked for the root password and then nothing happens.

Any ideas on what I can do to fix this would be most appreciated!

Rob

Hi

I updated my SSL cert weeks ago but just updated from RH8 to RH9 and up2date simply won't run. From the terminal it sits there looking like it's doing something before "timing out" and giving me a new blank terminal line. Several other programs do this including rhn register and network device control.

I don't get any error messages at all. The command up2date -p works though.

Thanks in advance.

Regards
Kingsley

I fixed it. I installed and ran aptget which updated everything except the kernel. Then up2date ran and I updated that. My network device control now runs without segmentation faults too. Still have some problems but I think I can work them out.

Kingsley

I update to kernel-2.4.20-20.9 and when I try to install the NVIDIA drivers I get an error saying that it cant find the kernel header files and I need to install the kernel source rpm. I have installed kernel-2.4.20-20.9 about 20 times.

No need to install that 20 times. Just install the package named kernel-source-2.4.20-20.9.i386.rpm once. up2date kernel-source

Btw, that problem does not belong into this thread.

Found some interesting but silly news about Up2Date from the Red Hat site. "Updates only via Red Hat Network. Last updates end April 2004." Here is the link with some interesting topics regarding our support from Red Hat http://www.redhat.com/software/whichproduct/ I really like reading the far right column and the future of Red Hat...

I guess with the Fedora Project, Red Hat is phasing out support for all of Redhat 9 and previous versions. Am I reading this correctly?

Silly Sam

No, since the Fedora Project is not the reason for the end-of-life dates of Red Hat Linux products. You're very late with your discovery. The end-of-life dates of Red Hat Linux products are known for a quite long time already. They've been published at http://www.redhat.com/errata almost a year ago and discussed in many places. Apparently, you have missed all of that. But it is correct that there won't be a Red Hat Linux 10.

Misc,

Then why is Red Hat discontinuing to support a product less than a year old (Release March 2003 )?

I for one am a newbie as indicated by my previous posts, and did not see this discontinued support anywhere in the Up2date forum. I am merely trying to just inform some of the others users out there who may not be aware of this or did not read the Fedora Project: Announcing New Direction.


This is very frustrating because everyone want to get away from the M$ empire, but when Red Hat pulls a stunt like this, dropping support makes newbies a little weary. What I was looking for and failed to place in my previous post is what alternative is their for us who would like to continue to use Red Hat 9 or is this basically the end of it?

I guess we are both late then with this information since it was posted 40 days after your original post in the Fedora Project: Announcing New Direction.

Sincerely,
Silly Sam