On Wed, 12 Oct 2005, Skunk Worx wrote: Try just updating the kernel first. At least we might be able to isolate the problem that way. --g _____________________ ____________________________________________ Greg DeKoenigsberg ] [ the future masters of technology will have Community Relations ] [ to be lighthearted and intelligent. the Red Hat ] [ machine easily masters the grim and the ] [ dumb. --mcluhan

On Thursday 13 October 2005 08:11, Skunk Worx wrote: Hmm, we are talking about updating the parent system, not the repository that will be used for live CD building, right? Well, the kernel that is running on the parent system has nothing to do with the kernel on the live CD system. I'm currently connecting to the internet through the GPRS so I can't download updates and try them by my self... But, there are two things you should pay attention to: 1. What repository are you using for live CD building? FC4 or not? 2. Is the python on the parent system FC4 default, or is maybe updated? Here's the function that is supposed to resolve the kernel version: def get_kernel_version (rootdir): """Returns kernel version that is installed on the destination system""" kernel_version = None clear_rpm_db_files (rootdir) ts = rpm.TransactionSet (rootdir) for mi in ts.dbMatch ('name', 'kernel'): kernel_version = "%s-%s" % (mi['version'], mi['release']) clear_rpm_db_files (rootdir) return kernel_version rootdir is the path to the root of the system. For the above example, it would be rootdir='/tmp/livecd-build_no12/system'. You could also try it out on your local system by calling get_kernel_version('/') Just in case, here's the clear_rpm_db_files function that is used in get_kernel_version(). def clear_rpm_db_files (rootdir): """Removes rpm database files in the destination if they exist""" def rmpath (p): try: os.remove (p) except OSError: pass rmpath (normalize_path ('var/lib/rpm/__db.001', rootdir)) rmpath (normalize_path ('var/lib/rpm/__db.002', rootdir)) rmpath (normalize_path ('var/lib/rpm/__db.003', rootdir)) -- Darko

On Thursday 13 October 2005 18:44, Greg DeKoenigsberg wrote: No, it shouldn't have anything to do with the kernel on the parent system. Hm, we can try, but I think ts object is just the interface to the rpm database. I think it would help if you could edit /usr/share/kadischi/lib/functions.py, replace get_kernel_version function with the following: def get_kernel_version (rootdir): """Returns kernel version that is installed on the destination system""" kernel_version = None clear_rpm_db_files (rootdir) ts = rpm.TransactionSet (rootdir) mi = ts.dbMatch () for hdr in mi: print "%s-%s-%s" % (hdr['name'], hdr['version'], hdr['release']) for mi in ts.dbMatch ('name', 'kernel'): kernel_version = "%s-%s" % (mi['version'], mi['release']) clear_rpm_db_files (rootdir) return kernel_version And then send me the output. Kadischi will fail again, with the same error message, but it will print the list of packages that are present in the rpm database. -- Darko

Is there anyway to replace isolinux with grub bootloader? It'll be pretty nice if it can boot with grub. (Just a suggestions). Thanks..

Roger that, I'll be following the grub howto..sound interesting.. After reading the howto, i notice especially the "root=/xxx" because in normal boot from harddisk usually use. Is it the same "/xxx" as in CD? I also put "rhgb quiet", does rhgb can be applied? How about the "kernel /boot/xx", "splashimage=/boot/xxx" and "initrd /boot/xxx", can be readable when booting from CD? One more thing, the root dev is ram0 right? default=0 timeout=30 splashimage=/boot/splash.xpm.gz title Fedora LiveCD kernel /boot/vmlinuz-2.6.x.x root=/dev/ram0 rhgb quiet initrd /boot/initrd-2.6.x.x It's different when i look at linspire 5.0 menu.lst, the "/boot" have "(cd)" in the beginning: splashimage=(cd)/boot/splash.xpm.gz kernel (cd)/boot/vmlinuz-2.6.10 initrd (cd)/boot/initrd-2.6.10.gz Many thanks.. Ignacio Vazquez-Abrams wrote:

the problem appears to be transient. the latest yum updates have fixed it. will retest tomorrow night to verify. -- SW

On Fri, 2005-10-14 at 14:23 -0700, Skunk Worx wrote: I'm still seeing it on my freshly-updated FC4 system. Somehow no kernel is being installed into the buildroot. -- Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net&gt; http://fedora.ivazquez.net/ gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72

Skunk Worx wrote: i have tried it on three machines (both intel and amd mobos) and can't duplicate this problem. I'm guessing it's a deep problem below kadischi. If anyone can provide more info on the chipset or cpu involved (N/S bridge etc./CPU) I can try to duplicate this bug. -- SW