[SuSE Linux] P.S.(Help w/ Linux Boot Menu under Win95)
even if I just call "loadlin hda6" in my autoexec.bat, it still asks me for the name of my kernel image. I type in "zimage" and hten linux boots. But of course as I said in my last posting, it would be nice to have it work as it is supposed to! thanks, chris - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
The documentation that you complain about being so bad, actually says to type linux hda6 NOT loadlin hda6. linux is a batch file in your loadlin directory that appends hda6 onto a longer loadlin command line. Maybe you have not fully read or do not fully understand the documentation. Re-read it with a more positive attitude and I am sure it will work just as it says it will. Kieran
-----Original Message----- From: owner-suse-linux-e@suse.com [<A HREF="mailto:owner-suse-linux-e@suse.com]On">mailto:owner-suse-linux-e@suse.com]On</A> Behalf Of Christopher A. Martin Sent: Wednesday, December 02, 1998 2:41 PM To: suse-linux-e@suse.com Subject: [SuSE Linux] P.S.(Help w/ Linux Boot Menu under Win95)
even if I just call "loadlin hda6" in my autoexec.bat, it still asks me for the name of my kernel image. I type in "zimage" and hten linux boots. But of course as I said in my last posting, it would be nice to have it work as it is supposed to!
thanks, chris - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Or as I've learned, read it, re-read it, then re-read it again... Amazing how I pick something else up each time I re-read the docs!
have not fully read or do not fully understand the documentation. Re-read it with a more positive attitude and I am sure it will work just as it says it will.
Kieran
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
wizard01@impop.bellatlantic.net wrote:
Or as I've learned, read it, re-read it, then re-read it again... Amazing how I pick something else up each time I re-read the docs!
Ya, and sometimes you have to go away and come back a week later to see it....those mental-blocks. Where's my Scientology Manual? - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Okay, after having trouble getting loadlin to work, I decided to try and install LILO. Everything went flawless until I tried to boot my linux config. It started to load, and right after listing the drives, it says "Unable to open Initial Console" and locks up. This, by the way, was exactly what happened when I tried to use *loadlin* exactly the way the book says to. (and was why when trying to get loadlin to work that I was typing "loadlin hda6" as opposed to what the book says "linux hda6" in order to get anything to run---but even that doesn't work now) Any help GREATLY appreciated, Chris - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
You really should become familiar with the SuSE online Support Database. Doing a search on unable to open initial console reveals the following: Symptom: When booting the message Unable to open an initial console appears. The system freezes. Cause: This message appears exactly when it is being tried to open /dev/tty1 while it is not there. Reasons for this: wrong root partition /dev/tty1 got erased You're booting with the bootdisk supplied with version 4.3 of S.u.S.E. Linux 4.3 and the root-filesystem is located on an UMSDOS partition (demo mode) Solution: 1. Wrong root partition : If you boot with LILO, specify the correct root partition at the LILO prompt. In our example this will be /dev/sdb1 : LILO: linux root=/dev/sdb1 You should then adapt /etc/lilo.conf (don't forget to call /sbin/lilo afterwards). 2. /dev/tty1 got erased : Start the rescue system. Mount the root partition on /mnt and recreate the device (see also maddin_devices2.html): mknod -m600 /mnt/dev/tty1 c 4 1 3. For the UMSDOS problem : Get a new bootdisk from ftp.suse.de:/pub/suse43/disks/modboot1. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Chris, I experienced the same (Unable to open Initial Console) on my alternate system a couple of weeks ago. I also submitted this to the list, and read all documentation I could find on lilo, which is very meager considering the absolute importance of its main function - bootstrap an OS, and alternative boot managers. No success! Someone responded to me indicating I needed to mark the partition active. In my case it didn't make sense since the linux kernel is on a separate disk, and by default was marked active. It was marked active by the way. You might try this, if your kernel is on the same disk as the Windows 95 OS, and it is not the first partition. Anyway I had to resort to making a boot floppy with the kernel on it. as lilo is a very unstable product. I have had numerous problems with it over the past 3 years. My problems have been isolated to dual/triple/etc. boot systems, where the linux kernel was not on the first drive or not on the first partition of the first drive. I don't believe lilo gets that much attention due to the fact that once the 'developers' get their system to boot satisfactorily, lilo is no longer on their minds. Good Luck, jpg
Okay, after having trouble getting loadlin to work, I decided to try and install LILO. Everything went flawless until I tried to boot my linux config. It started to load, and right after listing the drives, it says "Unable to open Initial Console" and locks up. This, by the way, was exactly what happened when I tried to use *loadlin* exactly the way the book says to. (and was why when trying to get loadlin to work that I was typing "loadlin hda6" as opposed to what the book says "linux hda6" in order to get anything to run---but even that doesn't work now)
Any help GREATLY appreciated,
Chris -
-- - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Interesting as I haven't had a single problem with my system when it was dual boot or even now with triple boot. I have two machines currently using lilo, one with linux and NT, the other with two different distros of linux and NT. The system I'm on boots NT or win95 from hda and linux from hdb. The other system boots from hda totally now. Perhaps it's a hardware related problem? If so it'd be a bit harder for the programmers to localize without duplicating the problem...
Anyway I had to resort to making a boot floppy with the kernel on it. as lilo is a very unstable product. I have had numerous problems with it over the past 3 years. My problems have been isolated to dual/triple/etc. boot systems, where the linux kernel was not on the first drive or not on the first partition of the first drive. I don't believe lilo gets that much attention due to the fact that once the 'developers' get their system to boot satisfactorily, lilo is no longer on their minds.
Good Luck, jpg
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
wizard01: Not that I'm dissatisfied with SuSE, but I'm curious about the setup of the machine you have with different distros of Linux bootable by LILO (saw the post on Win95 menus). Do you share any of your parititions between distributions? I'm thinking about trying Debian and am curious about being able to share some of my compiled applications between distros. Rick Thompson Computer Resources Coordinator Motley + Associates, P.C. - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (6)
-
camst65+＠pitt.edu -
jpg＠hpcvsjpg.cv.hp.com -
ksullivan＠bfsec.bt.co.uk -
rthompson＠motleypc.com -
wizard01＠impop.bellatlantic.net -
zentara＠mindspring.com