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.
Ok i just recently install slackware 8.1 on my system
amd altholon 1.2ghz
256*3 megs of ram (I can never remember 786 or 768)
nvidia geForce2 Pro graphics card
I recently Installed slackware 8.1 on hdb3 in my computer i also installed lilo to the superblock on that partion then set it to be the boot partion. On hda i have my windows2k install and SuSe 8.0 installed. I set hdb to be the hard drive to boot from first and when I do boot to it I get an insteresting result.
the screen fills with 01 01 01 01 01 01 01 01 reapeatly till i rebot the system.
I set lilo to use the standered output in text mode.
Anyone has any information to help it would be apriciated, im getting kicked off the computer im at and will be checking back later today or tonight.
It is definitely a Lilo problem config problem. But not perhaps with Lilo itself. Since you stated that your BIOS allows the the second drive to boot first, and that you installed Lilo to the partition that is marked as bootable, then I suspect it is the Master Boot Record of hdb that is the problem. Perhaps you had installed to MBR prior and now moved it to the partition. In that case the MBR needs to be rewritten or Lilo reconfigured to the MBR of hdb.
Another thing you could do ( suppose it pry works in 8.1 but not sure.. as Im having my own set of problems ) but an alternative would be to install LILO to the superblock as you have done. Then do a "dd if=/dev/hdb3 of=/bootsect.lnx bs=512 count=1" (I usually put this into a script as typing this after every kernel build (expecially if trying diff opts ) gets tiresome). then copy bootsect.lnx to first boot drive and do a "c:\bootsect.lnx= "Linux" " or instead of c:\ use the drive designation.
I think this is explained better and more thoroughly in one of the FAQ's or mini-FAQ's... linux+win2k maybe...
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
I would recommend installing LILO on the MBR of your first disk, telling
the BIOS to boot off the first disk, and using LILO as your boot manager
for all your OSs.
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 50
# Normal VGA console
vga = normal
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/slackware8.1/vmlinuz.188.8.131.52
root = /dev/hda2
label = Slackware8.1-19
image = /boot/slackware8.0/vmlinuz.2.4.19
root = /dev/hdb1
label = Slackware8.0-19
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = windows
table = /dev/hda
# DOS bootable partition config ends
Set your lilo.conf to something like this. If you want two distros, you can
copy all of your kernel images into one directory (/boot on hda, perhaps),
edit /etc/lilo.conf and then run:
You don't have to bother running lilo on both distros, since it's a global
thing, BUT I would make sure the /etc/lilo.conf files are the same
since you don't want to screw up and install the wrong LILO after
recompiling your kernel on one system and not the other. Probably a
better solution is to put lilo.conf in /boot and run:
lilo -C /boot/lilo.conf
(maybe write a shell script to wrap lilo so you get this right each time)
(I haven't checked this last bit, so if someone can correct me if I'm
wrong, that would be good)
If you get error messages, post 'em.