Hi,

When using up2date earlier today in order to upgrade the new kernel, the system keeps telling me that the file is corrupted.

I have tried a manual rpm installation, but the same problem is still there.

I know for a fact that lots of people are experiencing this.

Anybody got any ideas?

Thanks

I could install the new kernel (and source and intiscripts) but I was unable to install NVIDIA and NTFS support when booting from the itl. I think I'll wait a while until some more experienced people figure out how to make this work.

This must be the one of the downsides of the Fedora model.... at least I have the old kernel available.

bl

And the answer is,

# rpm --import /usr/share/doc/fedora-release-1/RPM-GPG-KEY-fedora

this imports the necessary key for the rpm package not to complain about the new kernel's signature.

After importing the key, should you want to keep the "old" kernel available (just in case):

# up2date -i kernel --force

That's it: now we have 2 working kernels installed

(Courtesy of a fellow Linux user)

Regards,

Arthur1968

That's a doubleedged sword. Those keys is there for a good reason. To ensure packages are valid, and undamaged (or changed by someone malicious). Every time you do this, you can't be sure if the package you have is good or not.

Here's what I learned last night -

The NVIDIA driver update has the following quirk: If you have the driver installed for the old kernel the installer will not execute the steps requried. Here's what I did

Assuming you have installed before - as root in text mode execute

# export CC=gcc32
#nvidia-installer --force-update

Unfortunately, this downloads the driver again, but it will perfom the install/compile. XF86Config is not touched. If anyone has a more elegant solution let me know.

A quick check of the NTFS site on sourceforge promises the Fedora kernel upgrade release soon. I'll post as soon as I have it. In the meantime, no NTFS support with the new kernel.

bl

Quote:

That's a doubleedged sword. Those keys is there for a good reason. To ensure packages are valid, and undamaged (or changed by someone malicious). Every time you do this, you can't be sure if the package you have is good or not.

In what sense, Teval?. Surely installing security keys improves overall security (this could be a silly question).

What do you think?

Arthur

I noticed this about trying to install the latest kernel:

The kernel RPM installed without a hitch. But the kernel *source* was another matter. The RPM quit loading halfway through its download, and the Update Agent told me, "All finished; press Forward to continue." So I pressed Forward, and the system got all the way to the end of the "Install" process before bailing out.

Without that kernel source code, I cannot build certain drivers (like Linuxant's DriverLoader) that require kernel source code access. So I don't plan to use the new kernel until someone at Fedora attends to this problem.

If you want a compatible kernel all you need is the config file, then download the sources from www.kernel.org and make your own kernel. You can even... make an NTFS module! It's really not that hard to compile a kernel.