LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-23-2002, 07:18 PM   #1
gamer11
LQ Newbie
 
Registered: Oct 2002
Posts: 3

Rep: Reputation: 0
Slackware 8.1 problems


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.

Thank you in advance!
 
Old 10-23-2002, 09:03 PM   #2
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

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

Hope it helps.
 
Old 10-23-2002, 09:42 PM   #3
BlueWWWeb
LQ Newbie
 
Registered: Oct 2002
Location: Wonder Lake, IL
Distribution: Slackware
Posts: 7

Rep: Reputation: 0
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...
 
Old 10-24-2002, 01:11 AM   #4
moses
Senior Member
 
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152

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

My /etc/lilo.conf:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
delay = 50
append="hdd=ide-scsi idebus=66"
# Normal VGA console
vga = normal
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/slackware8.1/vmlinuz.2.4.19.3
root = /dev/hda2
label = Slackware8.1-19
read-only
image = /boot/slackware8.0/vmlinuz.2.4.19
root = /dev/hdb1
label = Slackware8.0-19
read-only
# 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:
lilo
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.
 
Old 10-24-2002, 05:34 PM   #5
gamer11
LQ Newbie
 
Registered: Oct 2002
Posts: 3

Original Poster
Rep: Reputation: 0
Thank you for your replies im going to try the moses's suggestion and add the config lines to my exsisting lilo install on suse 8.0

Will post back if it works
 
Old 10-24-2002, 09:01 PM   #6
Excalibur
Senior Member
 
Registered: Jun 2002
Location: Northern VA, USA
Distribution: Ubuntu
Posts: 1,180

Rep: Reputation: 45
I think SuSE uses grub to handle the boot management. But grub is also capable of handling it. Configure through YAST and you should be OK.
 
Old 10-24-2002, 09:07 PM   #7
MasterC
Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 64
Actually, Excalibur, on my setup for SuSE 8.0 (which was basic, at best) it installed LILO to my surprise.

So I think it can go either way, might be a user choice during the install.

Cool
 
  


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
slackware 10.1 problems scales Linux - Newbie 21 08-18-2005 04:45 PM
Slackware problems. isuckwithlinux Linux - Software 2 11-06-2003 10:55 PM
Slackware 9.0 problems Devboy Linux - Newbie 4 11-04-2003 03:59 AM
Slackware Problems XPediTioN Slackware 13 07-25-2003 03:45 PM
Slackware problems amp2000 Linux - Software 4 03-02-2002 01:38 PM


All times are GMT -5. The time now is 10:31 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration