Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed Mandrake 9.0 recently. In fact, I've installed it no less than 5 times in the past two weeks.
Everything works great, except the boot loader.
OK, this is what I have, a Pentium III 733, w/ 256 MB of RAM, two HDs. HD1 is a 9GB FAT32. HD2 has two partitions, first partition(20GB) is FAT32, and 10GB remaining for Linux. I am duel booting Win2k pro and linux.
When I first started I was using LILO, then later I also tried Grub, but both gave me the same problem. Every time I cold boot the machine, I would get a string 010101...s on the screen and it would just hang. Hitting the reset button for a warm boot would solve the problem.
I tried to get around this nonsense by writing the LILO MBR into a file, restore NT MBR and call up the LILO MBR file from within the NT boot loader, SAME SHIT!!!! The only benefit I got out of this is that I can now do a ctrl-alt-delete for warm boot rather than hitting the reset button.
I am running out of ideas, and this is getting old and frustrating. And nope I would rather not rearrange my HDs.
Maybe a look at your lilo.conf (or grub.conf) would be insightful. Does it give out this string even when trying to boot NT from the NT bootloader, or just when you get to the lilo stage? And also did you try disabling PNP aware OS in the bios?
I don't have the lilo.conf right now because I am at work.
It gives the '01010101' string whenever lilo starts up from a cold boot. NT boot loader shows up fine after cold boot until I pick linux. What I do right now is turn on the machine, in NT loader screen, ctrl-alt-del to reboot again, when NT loader comes back up pick linux, then everything would be fine. Once the 010101 shows up, it hangs and will not response to any key strokes.
This is an example using the Windows "ntldr" to boot XP,Debian,Slackware and Minslack (CLI only). I created a softlink from the /boot/image (vmlinuz or bzimage) to "/" in order to forego the pleasure of having 2 bootscreens and
booting straight to the kernel. The examples are from Slackware but they're generic. Here's an example of lilo.conf with everything commented out except the essentials.
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hdb6
#message = /boot/boot_message.txt
#timeout = 1
# Override dangerous defaults that rewrite the partition table:
# Normal VGA console
vga = normal
# End LILO global section
# DOS bootable partition config begins
# DOS bootable partition config ends
# Linux bootable partition config begins
image = /vmlinuz-ide-2.4.18
root = /dev/hdb6
label = Slackware
# Linux bootable partition config ends
Note that the image= is not in the /boot. Run "/sbin/lilo" If you get a "Warning" that this is not the first partition. You did good. Now create your bootsect file.
Copy the bootsect.slk to the drive where "ntldr" and "boot.ini" reside. (Normally C)by using a dos format floppy or e-mail it to yourself.(Not my idea but it was too cool) If your Windows drive is vfat just mount the drive and copy straight to it. Then add a line to "boot.ini" Here's mine.
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
t gives the '01010101' string whenever lilo starts up from a cold boot. NT boot loader shows up fine after cold boot until I pick linux. What I do right now is turn on the machine, in NT loader screen, ctrl-alt-del to reboot again, when NT loader comes back up pick linux, then everything would be fine. Once the 010101 shows up, it hangs and will not response to any key strokes.
Your bootsect.lnx file is no good. Did you install lilo to your root partition? Did you run /sbin/lilo? Did you build a new "bootsect.lnx afterward? The answer to one of these questions is NO. The "010101010" error means bootsect.lnx is empty or corrupted. I have the same "cold boot" problem that you do and it has something to do with the bios and XP but until it becomes more than a minor annoyance I'm gonna leave it alone.
I don't have my lilo.conf with me right now, it's basically the default file minus the windows part. I'll post it when I get home.
However, the important fact here is that my bootsect.lnx is GOOD, because it DOES load up after a warm boot. I did run /sbin/lilo before running "dd" to create the bootsect.lnx file, and it DID bring up the LILO boot menu first before I did my fdisk /mbr in DOS.
I totally agree that this is only a minor annoyance, but.... I don't know.. I am a programmer myself, I don't like seeing bugs lying around, I would like to know there is at least a workaround to this.
Here's my theory on "bootable" CDs,floppys or partitions. When you boot a PC the BIOS searches for the first 512 bytes of "readable" data. The Boot Sequence tells the BIOS where to look first,second and sometimes third depending on the BIOS.
Bootloaders perform the same function whether they're LILO,Grub or Ntldr. When you run /sbin/lilo /etc/lilo.conf tells Lilo what to write to the first the first 512 bytes (image=) as well as where to write (boot=). When I create a symlink from my vmlinuz-bzimage (whichever). The image itself, not the symlink already in the /boot directory to / . I can then change line "image=/boot/vmlinuz" to "image=/vmlinuz-ide-2.4.18" it will boot straight into the kernel instead of loading the Lilo boot screen. I haven't had the chance to test this on Grub. Ntldr seems to read boot.ini and take it's configuration from there but ntldr is still the first 512 bytes of the FIRST primary partition and this is set in stone. When you dual boot 98 and 2K or XP you can put your 2K or XP on a partition other than C but boot.ini AND ntldr will be on C no exceptions. I haven't tested this extensively (only when my job forces me) but there are several "antivirus" and "Go Back" programs that will screw up the first 512 bytes of hda1 no matter what bootloader you use. The reason I said your bootsect.lnx was bad was because ntldr was not reading it correctly from boot.ini but maybe there's something that's preventing the ntldr from working therefore the "hotboot". I think I'm starting to ramble but "HEY",food for thought.