http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c4
David Rankin changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
InfoProvider|drankinatty@suddenlinkmail. |
|com |
--- Comment #4 from David Rankin 2010-03-30 03:57:09 UTC ---
Michal,
Hmm... You are batting 1000! Looks like somehow, some time ago the initrd
version on my box did get updated to factory. Right now I have:
22:34 ecstasy:~> rpm -q mkinitrd
mkinitrd-2.5.10-16.1
I downgraded to 2.2-19.2, but I'll need a bit more help getting rid of all the
pieces. I think this will fix the problem, but currently here is what happens
after the downgrade:
[22:51 ecstasy:/home/david/suse] # rpm -ivh --force kernel*.rpm
Preparing... ########################################### [100%]
1:kernel-syms ########################################### [ 50%]
2:kernel-default ########################################### [100%]
Setting up /lib/modules/2.6.25.20-0.7-default
egrep: /lib/mkinitrd/setup/02-kms.sh: No such file or directory
egrep: /lib/mkinitrd/setup/83-ibft.sh: No such file or directory
egrep: /lib/mkinitrd/setup/91-clock.sh: No such file or directory
Kernel image: /boot/vmlinuz-2.6.25.20-0.7-default
Initrd image: /boot/initrd-2.6.25.20-0.7-default
/sbin/mkinitrd: line 397: /lib/mkinitrd/setup/02-kms.sh: No such file or
directory
Script /lib/mkinitrd/setup/02-kms.sh failed!
/sbin/mkinitrd failed
error: %post(kernel-default-2.6.25.20-0.7.x86_64) scriptlet failed, exit status
1
I know we shouldn't have kms on 11.0 (should we?? surely not), but it looks
like the factory mkinitrd added additional setup scripts. What should I do now?
Reinstall mkinitrd again with --force? Remove mkinitrd and manually delete
/lib/mkinitrd and then reinstall mkinitrd?
Let me know how best to handle this so I don't screw myself any further :p
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
