SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
im very new to slackware and linux. i only installed zipslack yesterday and i have encountered a problem while trying to boot.
i have edited autoexec.bat to give me the option to boot linux or windows and the line in the file to boot linux is as follows:
i am unsure as to wether the mem=32m statement is neccesary but i thought id give it a try
the computer is a gateway 2000 solo with 32meg of ram (as stated above) and a 150mhz processor. i extracted the zip into the root of my C drive (fat16) as instructed on the slackware website and edited linux.bat (although i am using autoexec.bat). linux.bat executed from dos (external from windows) brings up the same error message:
Warning: unable to open an initial console.
Kernel panic: No init found. Try passing init= option to kernel.
i searched google and this site for a number of hours for a solution to this problem (which many others seem to have had) but i have not found one that solves my problem.
Any suggestions would be greatly appreciated
Last edited by giddleberry; 10-08-2003 at 02:23 AM.
It's the right place. Problem is, I don't know what's wrong. I have a hidden partition on a 686 and what Windows reports as C on that machine is actually /dev/hda2. If you had two drives, maybe it would be /dev/hdb1. 'No init found' means, basically, that command on C is loading loadlin on C which is loading the kernel on C which is looking for root on /hda1 and not finding it. So the only thing I can think of is either you have the wrong device given or your install was messed up somehow. For instance, you may have needed a 32-bit unzipper and used a 16. Can't remember is that's an issue or not. Or the download may simply have been corrupted.
Hm. Another possibility is you need a FAT32 or something. Zipslack has to do funky stuff with the names regardless, and is intended to also work under plain DOS, so I don't think that would be the issue, though.
One more thought - DOS isn't case sensitive and Linux is. Not sure if loadlin is case-sensitive or not, though. If it's receiving the command with the wrong case and passing it on, maybe that's screwing things up. For instance, in plain DOS everything defaults to uppercase internally, no matter what it looks like. Windows keeps *track* of case, unlike plain DOS, but ignores it. But in Linux, VMLINUZ and vmlinuz are different things. Things like that. *shrug*
I will try to help as best I can, as I am slowly learning more and more about ZipSlack and Slackware itself.
Need to ask a few questions so that I can get a better understanding of the system:
1 How many hard drives do you have in the system?
2 What is the partition structure of each drive in the system?
3 Where did you extract the ZipSlack package to?
4 What OS(s) are you running on the system (DOS, Win 3x, Win9x)?
With this info I can help guide you a little better, and am quite sure we can get you up and running with little trouble!
Hang in there, part of the fun is figuring out how this awesome OS runs
1. just the 1 hard drive
2. i am hoping the answer to this question would be fat16?? tell me if ive answered incorrectly i dont really know much :P from all indications this is hda1
3. i extracted to c:\ which then meant the root folder of linux was c:\linux
4. i am running win98SE
the system is a laptop if that in some way helps and the drive has been compressed using drivespace in windows...
thanks again if ya can help
Last edited by giddleberry; 10-08-2003 at 10:30 AM.