Description of Problem:
After installing 7.3 Linux from the installation CD (kernal: 2.4.18-3),
loadlin.exe booted Linux from DOS just fine. However, after applying the latest
RPMs (kernal: 2.4.18-5), loadlin.exe merely resets the computer while its
loading the kernal.
Version-Release number of selected component (if applicable):
RAM Disk: 2.4.18-5
Steps to Reproduce:
1. Create a folder containing loadlin.exe, initrd-2.4.18-5.img and vmlinuz-2.4.18-5
2. Exit to DOS and navigate to the folder created in step 1 above.
3. Enter the following command:
LoadLin.exe vmlinuz-2.4.18-5 root=/dev/hda2 ro initrd=initrd-2.4.18-5.img
Distutils is a set of Python build utilities, not the sum of all utilities
shipped with the distribution.
Refiling to anaconda, as they are the ones building the CDs and it's the closest
component I can think of :/.
This would almost have to be a kernel bug (or change in behavior at least) that
loadlin doesn't work with.
nothing is printed, at all ?
arjanv, it begins the load and flashes some text but quickly resets the computer
and begins a reboot.
In reading the documentation in lodlin16.tgz file of the distribution CD, it states:
The loader program works from the DOS prompt or from CONFIG.SYS
under the following conditions:
1. The buffer memory (lowmem + extended) is great enough
to hold the compressed kernel image (zImage or bzImage)
aswell as the initrd image (optional)
2. A) The CPU is not in virtual-8086 mode
B) The EMS driver supports VCPI.
My best guess is that vmlinuz-2.4.18-5 kernel exceeds the limit under condition
#1 above. I tried it without using the RAM disk (initrd-2.4.18-5.img) and the
same error occurs, so it looks like its the kernel that's the culprit.
loadlin.exe v1.6c, from a slackware ftp site, resolved the >1Mb kernel limitation.
Also verified that it works on RH 8.0
*** This bug has been marked as a duplicate of 75311 ***
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.