bzDisk compression Q; boot debug Q

First I have a question about the compression of bzDisk. While trying to debug the reason for a modular boot failure versus a successful non-module boot (XFS filesystem for root), I found that I can mount my initial ramdisk on loopback as a means of examining which modules are available to it. However, it doesn't actually point out which modules were loaded at the time when a filesystem mount fails. Viewing ramdisk is via:
gzip -dc your.img > somefile
mount -o loop somefile somedir

Question 1, how hard would it be to cause failure of mount of root filesystem to also output a list of current modules it has loaded?

Question 2, apparently ramdisk uses gzip compression; the name of the kernel from make bzImage seems to maybe refer to bzip2 compression. Is the kernel image using gzip or bzip2 compression for bzImage? Would anything be gained in reducing boot size requirements by running bzip2 compression for any initial ramdisk, versus gzip compression?

D. Stimits, [email protected]