LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This 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!

Notices


Reply
  Search this Thread
Old 02-13-2003, 10:08 AM   #1
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Rep: Reputation: 0
Question boot loader problem


Hi,

I am a newb, yes I am.

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.

Please send help!!!!
 
Old 02-13-2003, 10:57 AM   #2
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Original Poster
Rep: Reputation: 0
OK, I missed something else,
HD1 is IDE1 primary (hda)
DVD is IDE1 secondary
CDRW is IDE2 primary
HD2 is IDE2 secondary (hdd)

Why? because that was the only way I could fit the cabling inside this POS Dell case.
 
Old 02-13-2003, 03:30 PM   #3
mocnicom
LQ Newbie
 
Registered: Feb 2003
Location: Center of the Universe
Distribution: Gentoo
Posts: 25

Rep: Reputation: 15
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?
 
Old 02-13-2003, 03:44 PM   #4
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Original Poster
Rep: Reputation: 0
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.

Last edited by rzee; 02-13-2003 at 03:54 PM.
 
Old 02-13-2003, 04:42 PM   #5
mocnicom
LQ Newbie
 
Registered: Feb 2003
Location: Center of the Universe
Distribution: Gentoo
Posts: 25

Rep: Reputation: 15
If it only happens from a cold boot it may be bios related, although I could be wrong.
 
Old 02-13-2003, 05:06 PM   #6
Proud
Senior Member
 
Registered: Dec 2002
Location: England
Distribution: Used to use Mandrake/Mandriva
Posts: 2,794

Rep: Reputation: 116Reputation: 116
NT boot loader goes to Linux boot loader? Is that right? Surely one or the other. Linux one unless NT-based windows OS.
 
Old 02-13-2003, 05:46 PM   #7
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Original Poster
Rep: Reputation: 0
Yes, that's right, save the LILO MBR to a file, then in your NT loader file, boot.ini or something like that, put in a line like
c:\linuxbootloaderfilename = "blah blah blah..."

It basically executes the codes in that file, no big surprise there.
 
Old 02-14-2003, 12:24 AM   #8
Allen614
Member
 
Registered: Dec 2002
Location: Plains
Distribution: Slackware 13
Posts: 465

Rep: Reputation: 30
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
append="hdc=ide-scsi"
boot = /dev/hdb6
#message = /boot/boot_message.txt
#prompt
#timeout = 1
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# 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
read-only
# 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.

root@whatever#dd if=/dev/hdb6 of=/bootsect.slk bs=512 count=1

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.

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect
C:\bootsect.dbn ="Debian"
C:\bootsect.slk="Slackware"
C:\bootsect.slm="Minslack"

Reboot and pic your flavor.
 
Old 02-14-2003, 09:17 AM   #9
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Original Poster
Rep: Reputation: 0
err... still, no answer to my problem..
 
Old 02-14-2003, 09:36 AM   #10
Allen614
Member
 
Registered: Dec 2002
Location: Plains
Distribution: Slackware 13
Posts: 465

Rep: Reputation: 30
Quote:
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.
 
Old 02-14-2003, 09:54 AM   #11
Allen614
Member
 
Registered: Dec 2002
Location: Plains
Distribution: Slackware 13
Posts: 465

Rep: Reputation: 30
Post your lilo.conf and maybe we can straighten it out.
 
Old 02-14-2003, 10:09 AM   #12
rzee
LQ Newbie
 
Registered: Feb 2003
Location: NY
Distribution: Mandrake
Posts: 17

Original Poster
Rep: Reputation: 0
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.

Last edited by rzee; 02-14-2003 at 10:16 AM.
 
Old 02-14-2003, 12:49 PM   #13
Allen614
Member
 
Registered: Dec 2002
Location: Plains
Distribution: Slackware 13
Posts: 465

Rep: Reputation: 30
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Boot loader problem euaruksakul Linux - Newbie 10 01-13-2007 12:31 PM
Problem with Boot up loader blackman890 Mandriva 1 04-09-2005 08:12 PM
problem with boot loader makaveli0129 Mandriva 1 11-02-2004 12:20 AM
boot loader problem boombastic Linux - Newbie 4 08-21-2004 04:00 PM
Problem with boot loader alexr186 Linux - Software 4 06-17-2004 09:43 AM


All times are GMT -5. The time now is 11:57 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration