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 ###
11 matches
Mail list logo