LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 02-08-2011, 02:49 PM   #1
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Rep: Reputation: Disabled
How do I resolve: Lilo install causes error 0x80 during Slack install


Upon install of lilo on Slackware 12.1 - 13.1, if there is a SATA card, or a SATA drive plugged in, even when not using the drive for the slack install I get a 0x80.

I have tried to install to the SATA or the IDE as I am trying to use a BUNCH of old hardware for a cheap RAID box, and since I have 10s of 80gb drives sitting rotting at work, I will use them. I am aware of the IDE speed issue, but running each as a master in a RAID5 w/no slave I get the about same throughput as SATA drives via SaMBa.

Is there a way that you can preconfigure/mod lilo.conf in another console before installing lilo during a Slack install?

Is there a workaround that I have yet to find? Even a link SPECIFIC to the issue would be good. The only way I am able to get this to work is to unplug all cards/cables for anything SATA related and do the install, then plug it all back in, post install. Apparently the address 0x80 is the same addy for 1st SATA and 1st IDE passed from the BIOS but I can't seem to figure out how to get lilo to ignore the faulty BIOS drive address pass DURING or BEFORE install? Please advise.

Last edited by the86d; 02-08-2011 at 03:57 PM. Reason: Clarification...
 
Old 02-08-2011, 07:10 PM   #2
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 16,588
Blog Entries: 27

Rep: Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030Reputation: 5030
This might help:

http://www.mail-archive.com/linux-ra.../msg07817.html
 
Old 02-09-2011, 07:32 AM   #3
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
Thanks, but RAID is not my issue, as I build it manually.

The issue is that the (I assume from researching for the last month) 0x80 is passed from the BIOS as the address that LiLo writes to during the install.

You can fix this POST install with a tweak to lilo.conf, but it is not feesable to unplug all SATA cards AND IDE/SATA drives from the board (aside from the one to install slackware on) just to do the install, then plug them all back in.
 
Old 02-09-2011, 08:05 AM   #4
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,450

Rep: Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039
Quote:
Is there a way that you can preconfigure/mod lilo.conf in another console before installing lilo during a Slack install?
The Slackware installer allows access to another console by using Alt-F2. Use Alt-F1 to switch back.
 
Old 02-09-2011, 09:55 AM   #5
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
It always has, indeed.

Can you pass something like "DO NOT ACCEPT FAULTY HDD ADDRESS PASSOFF FROM THE BIOS" or "PASS COMPETE ADDRESS OF 0x800=/dev/sda 0x801=/dev/hda" to the kernel booting the busybox and then the installer? I know the naming scheme has changed to all HDDs becoming /dev/sd* but long timers may be able to help if they see the above reference as it is an issue too.

The address I am not sure of, this is only per researching this for the last few months in my free time.

Apparently lilo thinks that the 0x80 address is the SATA drive AND IDE drive because the bios passed an incomplete address, which can be fixed AFTER install, but I am looking for a workaround, or fix.

Last edited by the86d; 02-09-2011 at 10:14 AM.
 
Old 02-09-2011, 05:50 PM   #6
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
Has no one had this issue before?
 
Old 02-11-2011, 09:03 AM   #7
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
I guess I need to request help on IRC.

hehee

I thought a Linux forum might be as helpful as the http://e-cigarette-forum.com .

Last edited by the86d; 02-11-2011 at 02:18 PM.
 
Old 02-12-2011, 01:03 PM   #8
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 9,483

Rep: Reputation: Disabled
#slackware on IRC
 
Old 02-14-2011, 11:09 AM   #9
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
#slackware on IRC
ROGER, THX. I have been there numerous times before I knew Linux.

I don't know if IRC is blocked with the content filter here at work... I'll have to try today.
 
Old 02-24-2011, 04:19 PM   #10
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
Here is the actual error, and it only happens when installing to an IDE drive with SATA present... on this board.

Quote:
Fatal: Bios device code 0x80 is being used by two disks
/dev/sdb (0x0810) and /dev/sda (0x8000)

Sorry, but the attempt to install LILO has returned an error, so LILO has
not been correctly installed. You'll have to use a bootdisk to start your
machine instead. It should still be possible to get LILO working by
editing the /etc/lilo.conf and reinstalling LILO manually. See the LILO
man page and documentation in /usr/doc/lilo for more help. The error
message may be seen above.
 
Old 02-24-2011, 11:36 PM   #11
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,450

Rep: Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039Reputation: 2039
From 'man lilo.conf'
Quote:
static-BIOS-codes
Causes the operation of the boot installer and boot loader to bypass the use of Volume-ID information,
and to revert to a mode of operation of versions of LILO from 22.4 backward. With Volume-ID booting
(22.5 and later), the BIOS codes of disks are determined at boot time, not install time; hence they may
be switched around, either by adding or removing disk(s) from the hardware configuration, or by using a
BIOS menu to select the boot device.

With the use of this option, BIOS codes of disks MUST be correctly specified at install time; either
guessed correctly by LILO (which often fails on mixed IDE/SCSI systems), or explicitly specified with
'disk=/dev/XXX bios=0xYY' statements. The use of this option precludes any activity which may switch
around the BIOS codes assigned to particular disk devices, as noted above.

In general, this option should never be used, except as a bug workaround.
My reading of this option is that you will need to have explicit 'disk=/dev/XXX bios=0xYY' statements in lilo.conf when you _install_ the boot loader.
BTW - Could you please check what BIOS codes are actually being reported? There is inconsistency between post #5 and post #10.
 
Old 02-26-2011, 09:40 AM   #12
the86d
Member
 
Registered: Feb 2010
Location: /, /root, & /etc
Distribution: Slackware, Backtrack, Knoppix
Posts: 30

Original Poster
Rep: Reputation: Disabled
Post 5 was from memory, and was in error.

Where does this mount (how should I mount and) where is the lilo.conf that LILO looks for during the install? This is my confusion.

The later post is correct, but post 5 was mentally garbled in my mad search for a fix while getting slammed with other things while at work.
 
  


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
Dual-boot Slack/Ubuntu-install slack over XP-help with weird partition layout & lilo? linus72 Slackware 2 05-23-2009 10:03 AM
boot-as = 0x80? (booting windows from lilo) somae Slackware 4 06-27-2007 03:39 PM
Lilo install error from Slack 11 DVD tehkaao Slackware - Installation 7 03-11-2007 11:55 AM
install LILO after Slack install true_atlantis Slackware 1 04-28-2004 03:06 PM
LILO install error (only happens in Slack) SocialParasite Slackware 6 02-24-2004 05:26 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation

All times are GMT -5. The time now is 02:46 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
Open Source Consulting | Domain Registration