On Wed, Jul 09, 2003 at 07:59:55PM +0200, Go, Jeffrey wrote:
> Can anyone point me to the docs on how to upgrade the kernel on a RH 7.3 ?
# up2date -u kernel --force
--
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]
Member #1, Red Hat Community Ambassador Program
--
redhat-list maili
there is a good how to at the linux document project; it is not RH
specific, but it showed me enough to get on the right path to greater
problems...
I am finding that kernel upgrading is tricky.
http://www.tldp.org/Kernel-HOWTO/index.html
G
On Wed, 2003-07-09 at 19:59, Go, Jeffrey wrote:
> Hi A
Hi All,
Can anyone point me to the docs on how to upgrade the kernel on a RH 7.3 ?
Thanks
jeff
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
On Fri, Apr 20, 2001 at 10:54:34AM +0200, Tomás García Ferrari wrote:
> I'm trying to upgrade the kernel on my system to kernel-2.2.19-6.2.1. I'm
> having this behavior:
>
> > [root@ex K]# rpm -ivh kernel-2.2.19-6.2.1.i386.rpm
> > error: cannot open Depends index using db1 - Invalid argument (22)
Hi,
I'm trying to upgrade the kernel on my system to kernel-2.2.19-6.2.1. I'm
having this behavior:
> [root@ex K]# rpm -ivh kernel-2.2.19-6.2.1.i386.rpm
> error: cannot open Depends index using db1 - Invalid argument (22)
> Segmentation fault
What does it means? How can I solve it?
Thanks for
Ups...! You've got me! ;)
Thank you!
Tomas Garcia Ferrari
Bigital
http://bigital.com
> And I repeat...your "Boot image:" line is pointing to
> /boot/vmlinux-2.2.16-3. Lilo is complaining that that kernel file is too
> big. Edit the "Boot image:" line to read "/boot/vmlinuz-2.2.16-3" so that
And, of course, I read this just after firing off a reply. D'oh!!!
On Wed, 31 Jan 2001, Tomás García Ferrari wrote:
> Now I understand!
>
> Thanks indeed. (I feel a little bit stupid because I didn't notice the
> diference between 'vmlinux-2.2.16-3' and 'vmlinuz-2.2.16-3'...)
>
> Thanks again!
On Wed, 31 Jan 2001, Tomás García Ferrari wrote:
> As well, Mike Burger says:
> >> Also, instead of /boot/vmlinux-2.2.16-3, see if /boot/vmlinuz-2.2.16-3
> >> exists...if so, change the "Boot image:" line to read vmlinuz, instead.
> >> It's a compressed kernel, and lilo won't complain.
>
> It exi
Now I understand!
Thanks indeed. (I feel a little bit stupid because I didn't notice the
diference between 'vmlinux-2.2.16-3' and 'vmlinuz-2.2.16-3'...)
Thanks again!
Tomás
Ps: It worked.
Tomas Garcia Ferrari
Bigital
http://bigital.com
> No, what they're saying is that the entry in lilo.conf
No, what they're saying is that the entry in lilo.conf is incorrect. It
needs to by vmlinuz-2.2.16-3, unless you've made a symlink from
vmlinuz-2.2.16-3 to vmlinux-2.2.16-3.
> On Wednesday 31 January 2001 06:38, Tomás García Ferrari opined:
> > Then I add in /etc/lilo.conf this:
> > > image=/boot
Hello,
Mike Burger says:
>> Try using -U instead of -i. It looks like rpm is saying it can't install
>> because it already exists...howerver, -U is upgrade...which may very well
>> work.
and Uncle Meat says:
>> Well, if the above is accurate, you don't have the new kernel installed. I
>> saw so
On Wednesday 31 January 2001 06:38, Tomás García Ferrari opined:
> Hi,
>
> I am trying to upgrade the kernel to kernel-2.2.16-3. I did it like this:
> > [root@host RPMS]# rpm -Uvh kernel-source-2.2.16-3.i386.rpm
> > kernel-headers-2.2.16-3.i386.rpm
> > kernel-source
> > #
Try using -U instead of -i. It looks like rpm is saying it can't install
because it already exists...howerver, -U is upgrade...which may very well
work.
Also, instead of /boot/vmlinux-2.2.16-3, see if /boot/vmlinuz-2.2.16-3
exists...if so, change the "Boot image:" line to read vmlinuz, instead.
Hi,
I am trying to upgrade the kernel to kernel-2.2.16-3. I did it like this:
> [root@host RPMS]# rpm -Uvh kernel-source-2.2.16-3.i386.rpm
> kernel-headers-2.2.16-3.i386.rpm
> kernel-source ##
> kernel-headers ###
I asked myself the same question. And since I could not find the answer, what I did to
keep
the same config is :
- unpack redhat kernel source rpm
- did make xconfig-> Save config to file : myconfig
- cp myconfig -> new kernel source
- did make xconfig in the new kernel source -> Load config
sultant
Pearson Computer Systems Pty. Ltd.
-Original Message-
From: Hidong Kim [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, 11 January 2000 10:52 AM
To: [EMAIL PROTECTED]
Subject: Re: Upgrading the kernel..
Hi, Jamie,
Did you use 'make xconfig' to configure your new kernel? In
On Mon, Jan 10, 2000 at 05:48:19PM -0800, Todd A. Jacobs wrote:
> On Mon, 10 Jan 2000, Hidong Kim wrote:
>
> > menu of xconfig, there's a button called Save Configuration to File.
>
> I think the question was more to do with the configuration of the
> Red Hat supplied kernel. His question is on
On Mon, 10 Jan 2000, Hidong Kim wrote:
> menu of xconfig, there's a button called Save Configuration to File.
I think the question was more to do with the configuration of the Red Hat
supplied kernel. His question is one I've wondered myself: where does Red
Hat store the kernel configuration it
Hi, Jamie,
Did you use 'make xconfig' to configure your new kernel? In the main
menu of xconfig, there's a button called Save Configuration to File.
Click this and give it a file name. Then the next time you compile a
new kernel, click the Load Configuration from File button in the xconfig
mai
I've recently upgraded my kernel a rebuilt it and supprising was able to
boot the system. BUT!! During the upgrade it didn't keep my existing
kernel configuration so I lost access to a few devices and features.
So my question is, is it spose to keep my existing configuration and I
just did so
20 matches
Mail list logo
