-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Austin wrote:
> UP version installs and runs perfectly.
> SMP gives this error on install:
>
> [EMAIL PROTECTED] austin]# urpmi kernel-win4lin-smp-2.4.22.10mdk
> To satisfy dependencies, the following packages are going to be
> installed (2  MB):
> kernel-win4lin-smp-2.4.22.10mdk-3-5mdk.i586
> win4lin-utils-3-5mdk.i586
> Is this OK? (Y/n)
>
> installing
> /var/cache/urpmi/rpms/kernel-win4lin-smp-2.4.22.10mdk-3-5mdk.i586. rpm
> /var/cache/urpmi/rpms/win4lin-utils-3-5mdk.i586.rpm
> Preparing...
> ##################################################
>   1:win4lin-utils
> ##################################################
>   2:kernel-win4lin-smp-
> 2.4.22.10mdk##################################################
> error: %postun(Kernel-Win4Lin3-Mandrake9.1smp_2.4.21.25-01) scriptlet
> failed,  exit status 255

File a bug upstream for Kernel-Win4Lin3-Mandrake9.1smp_2.4.21.25-01

I guess I should try and handle this in %post though, since it will
afect many people ... but it might be Netraverse's perl script having
problems with a lilo.conf which has been modified since you installed
their kernel.

Maybe I shouldn't obsolete Kernel-Win4Lin3, and just provide it? Then it
wouldn't be uninstalled, but there could be problems with rpm and the
/boot/win4lin link, and uninstalling Kernel-Win4Lin3 later could remove
the link on uninstall (which would also give problems).

>
> [EMAIL PROTECTED] austin]# lilo
> Added linux *
> Added linux-nonfb
> Added linux-smp
> Added failsafe
> Added floppy
> Fatal: open /boot/win4lin: No such file or directory

Hmm, I wanted support for multiple win4lin flavours (smp, up,
enterprise), and forgot they installed them all as /boot/win4lin. But
this entry should really have been removed by the %postun that failed above.

>
> [EMAIL PROTECTED] austin]# ls /boot
> boot.0300                           message@
> config@                             message-graphic
> config-2.4.22-10mdksmp              message-text
> config-2.4.22-9mdk                  System.map@
> config-2.4.22-9mdksmp               System.map-2.4.22-10mdksmp
> diag1.img                           System.map-2.4.22-9mdk
> diag2.img                           System.map-2.4.22-9mdksmp
> grub/                               System.map.pre-win4lin@
> initrd-2.4.22-10mdksmp.img          System.map.win4lin-2.4.22-10mdksmp
> initrd-2.4.22-9mdk.img              us.klt
> initrd-2.4.22-9mdksmp.img           vmlinuz@
> initrd.img@                         vmlinuz-2.4.22-10mdksmp
> initrd-smp.img@                     vmlinuz-2.4.22-9mdk
> initrd-win4lin-2.4.22-10mdksmp.img  vmlinuz-2.4.22-9mdksmp
> initrd-win4lin-smp.img@             vmlinuz-smp@
> kernel.h@                           win4lin-2.4.22-10mdksmp
> kernel.h-2.4.22-9mdksmp             win4lin-smp@
> map

Well, there's no winlin, as there should not be. There shouldn't be a
lilo stanza for image=/boot/win4lin anymore. Unfortuntately you're going
to have to clean up after Netraverse kernel.

Could you remove the entry, run lilo, and see if lilo runs ok, if it
boots etc (and I would also like to know the image names lilo has -
there should be a win4lin-smp and a 2422-10mdkw4l or similar.

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/az41rJK6UGDSBKcRAgZaAJ9sGpc/hzYlIfelksXEKVFzKI6bEgCeLdJx
LmYzal5GloeXDic/O5c924g=
=JnEc
-----END PGP SIGNATURE-----

*****************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
*****************************************************************

Reply via email to