Elias Rajczyk <[EMAIL PROTECTED]> writes: > We actually haven't had any response from user space thusfar, contact to > the root system is limited to reading the partition table of hda and file > system detection.
Hmm. Last I checked adding swap space was user space functionality. I know the stock kernel does not have an option for it. > So far the only kernel panic we've seen occurred when physically reducing > the memory to 64M while commandline had mem=192m, the panic said "No init > found. Try passing init= option to kernel". O.k. So you don't have reboot on panic set, but you are getting a reboot from somewhere. > Most of the time the system just > gets stuck after adding swap and usually reset is generated. > Running the same kernel on a Linux PC with BIOS yields commad prompt right > after the "Adding swap" message. We were also able to get linux boot and > login after putting BIOS in our configuration (easy with compact flash) > using the kernel on hda. Hmm. I wonder if your problem might not be that someone has changed the layout of your kernel parameters, and the code we have to bypass setup.S is broken because of this. Your setup seems just about strange enough for this to be true. > Maybe LILO is behind this? Possible. I don't see it running from LinuxBIOS at all but... LILO (as a bootloader) will not work under linuxBIOS it makes BIOS calls. > It is on hda to enable chosing between boot/root > systems on hda1 and hda2. > Otherwise maybe we miss some functionality in the kernel, we needed to be > sober as we only have 512K in compact flash. Eric
