Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
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!


  Search this Thread
Old 10-04-2004, 02:53 PM   #1
LQ Newbie
Registered: Oct 2004
Posts: 6

Rep: Reputation: 0
The ODDEST Install Prob of ALL: Slackware 10

Hi recently installed Slackware Linux 10.0 following the pretty straightforward instructions on an online faq:

(I tried to post the url, but the system prohibits newbies from posting url's)

Accepting the defaults when prompted. Did two partitions, a mainlinux partition that was 20gig, and one setup as a swap partition that was 2 gig, using CFDISK.

I made the mainlinux partition bootable, than ran setup.

PC by the way is a pretty new IBM ThinkCentre, with a gig of ram, 2.3ghz processer, and 40 gig harddrive space.

So setup went pretty smoothly. Got to the part where you take out the cd and reboot, and when I did that what comes us is a screen full of "80". Yep, just over and over againg, against the black screen, "80" s continuously type across.

Did the install twice, received the same result twice.

Any lightbulbs, advice, shouts of eureka would be appreciated. Wondering if this is a virus, trojan bundled on the distribution cd, or is it some less menacing and easier resolved configuration that requires tweaking.

Any assistance, greatly appreciated. Thanks.
Old 10-04-2004, 02:58 PM   #2
Registered: Oct 2003
Location: San Deigo, CA
Distribution: FC3, Win2k Server, XP Pro & 2003 Server
Posts: 198

Rep: Reputation: 30
sounds like a kernel panic error, is your boot (MBR) in the first 1024 cylinders, if not put it there
Old 10-04-2004, 06:15 PM   #3
LQ Newbie
Registered: Oct 2004
Posts: 6

Original Poster
Rep: Reputation: 0
I'll give it a shot

Originally posted by rakriege
sounds like a kernel panic error, is your boot (MBR) in the first 1024 cylinders, if not put it there
I'm making the leap that recreating the MBR is something that can be adjusted via fdisk, or cfdisk (I thought formatting a new drive would create the mbr, in the correct location without having to specify it).

I'll do some homework and give it a shot. Thanks for the suggestion.
Old 10-04-2004, 06:28 PM   #4
Senior Member
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 52
the mbr is just the first sector of your harddisk. i think
you should run : liloconfig after you booted from a rescue-floppy
( hope you have one ), then pick the expert-mode, answer some Q's, and install it in the mbr.

that should work...

edit: in case of no floppy or even no floppy-drive, use the cd to boot and follow onscreen instructions to get in the installed Slack.


Last edited by egag; 10-04-2004 at 06:31 PM.
Old 10-04-2004, 06:37 PM   #5
LQ Newbie
Registered: Sep 2004
Posts: 27

Rep: Reputation: 15
I had the same problem installing my slackware...

wait a second.... did you say a 2 gig swap!? my lord.... must be some giant sized files you plan to work with. i dont think that would cause the problem, but your swap is probably over sized by any mans measure.

my problem stemmed from a bad install of lilo... however i got a error in the install of it in the setup program so i knew it was going to happen...

i booted off the install cd and entered my kernel at the prompt there the thing where it usually just says press enter to use the bare kernel

once in there i ran the setup again and tried a couple things to get lilo working and i was eventually successful (sorry there was not really a science to it... i just kept messing around until it worked)

anywho... good luck maybe your lilo install is messed up somehow try starting there
Old 10-04-2004, 06:38 PM   #6
Registered: Apr 2002
Location: in a fallen world
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
Blog Entries: 11

Rep: Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911Reputation: 911
From /usr/doc/lilo-22.5.9

LILO start message
- - - - - - - - -

When LILO loads itself, it displays the word "LILO". Each letter is printed 
before or after performing some specific action. If LILO fails at some 
point, the letters printed so far can be used to identify the problem. This 
is described in more detail in the technical overview.

Note that some hex digits may be inserted after the first "L" if a 
transient disk problem occurs. Unless LILO stops at that point, generating 
an endless stream of error codes, such hex digits do not indicate a severe 

  (<nothing>)  No part of LILO has been loaded. LILO either isn't installed 
    or the partition on which its boot sector is located isn't active. 
   L <error> ...   The first stage boot loader has been loaded and started, 
    but it can't load the second stage boot loader. The two-digit error 
    codes indicate the type of problem. (See also section "Disk error 
    codes".) This condition usually indicates a media failure or a geometry 
    mismatch (e.g. bad disk parameters, see section "Disk geometry"). 
   LI   The first stage boot loader was able to load the second stage boot 
    loader, but has failed to execute it. This can either be caused by a 
    geometry mismatch or by moving /boot/boot.b without running the map 
   LIL   The second stage boot loader has been started, but it can't load 
    the descriptor table from the map file. This is typically caused by a 
    media failure or by a geometry mismatch. 
   LIL?   The second stage boot loader has been loaded at an incorrect 
    address. This is typically caused by a subtle geometry mismatch or by 
    moving /boot/boot.b without running the map installer. 
   LIL-   The descriptor table is corrupt. This can either be caused by a 
    geometry mismatch or by moving /boot/map without running the map 
   LILO   All parts of LILO have been successfully loaded. 

Disk error codes
- - - - - - - -

If the BIOS signals an error when LILO is trying to load a boot image, the 
respective error code is displayed. The following BIOS error codes are 

   0x00   "Internal error". This code is generated by the sector read 
    routine of the LILO boot loader whenever an internal inconsistency is 
    detected. This might be caused by corrupt files. Try re-building the 
    map file. Another possible cause for this error are attempts to access 
    cylinders beyond 1024 while using the LINEAR option. See section "BIOS 
    restrictions" for more details and for how to solve the problem. 
   0x01   "Illegal command". This shouldn't happen, but if it does, it may 
    indicate an attempt to access a disk which is not supported by the 
    BIOS. See also "Warning: BIOS drive 0x<number> may not be accessible" 
    in section "Warnings". 
   0x02   "Address mark not found". This usually indicates a media problem. 
    Try again several times. 
   0x03   "Write-protected disk". This should only occur on write 
   0x04   "Sector not found". This typically indicates a geometry mismatch. 
    If you're booting a raw-written disk image, verify whether it was 
    created for disks with the same geometry as the one you're using. If 
    you're booting from a SCSI disk or a large IDE disk, you should check, 
    whether LILO has obtained correct geometry data from the kernel or 
    whether the geometry definition corresponds to the real disk geometry. 
    (See section "Disk geometry".) Removing COMPACT may help too. So may 
    adding LBA32 or LINEAR. 
   0x06   "Change line active". This should be a transient error. Try 
    booting a second time. 
   0x07   "Invalid initialization". The BIOS failed to properly initialize 
    the disk controller. You should control the BIOS setup parameters. A 
    warm boot might help too. 
   0x08   "DMA overrun". This shouldn't happen. Try booting again. 
   0x09   "DMA attempt across 64k boundary". This shouldn't happen, but may 
    inicate a disk geometry mis-match. Try omitting the COMPACT option. You 
    may need to specify the disk geometry yourself. 
   0x0C   "Invalid media". This shouldn't happen and might be caused by a 
    media error. Try booting again. 
   0x10   "CRC error". A media error has been detected. Try booting several 
    times, running the map installer a second time (to put the map file at 
    some other physical location or to write "good data" over the bad 
    spot), mapping out the bad sectors/tracks and, if all else fails, 
    replacing the media. 
   0x11   "ECC correction successful". A read error occurred, but was 
    corrected. LILO does not recognize this condition and aborts the load 
    process anyway. A second load attempt should succeed. 
   0x20   "Controller error". This shouldn't happen. 
   0x40   "Seek failure". This might be a media problem. Try booting again. 
   0x80   "Disk timeout". The disk or the drive isn't ready. Either the 
    media is bad or the disk isn't spinning. If you're booting from a 
    floppy, you might not have closed the drive door. Otherwise, trying to 
    boot again might help. 
   0xBB   "BIOS error". This shouldn't happen. Try booting again. If the 
    problem persists, removing the COMPACT option or adding/removing LINEAR 
    or LBA32 might help. 

If the error occurred during a write operation, the error code (two hex 
digits) is prefixed with a "W". Although write errors don't affect the boot 
process, they might indicate a severe problem, because they usually imply 
that LILO has tried to write to an invalid location. If spurious write 
errors occur on a system, it might be a good idea to configure LILO to run 
read-only (see section "Build-time configuration").

Generally, invalid geometry and attempts to use more than two disks without 
a very modern BIOS may yield misleading error codes. Please check carefully 
if /sbin/lilo doesn't emit any warnings. Then try using the LINEAR or LBA32 
option (see section "Global options").

Old 10-05-2004, 04:23 PM   #7
LQ Newbie
Registered: Oct 2004
Posts: 6

Original Poster
Rep: Reputation: 0
Thanks Guys!

Problem solved, you guys rock! I want to thank Rakriege, you were dead on. It was an MBR issue. During the install I was loading Lilo in root (that choice was coming up as default), rather than in the MBR (which it warns you not to do).

Reran putting Lilo in the correct location as well as a few other tweaks, Slackware is off and running.

Also huge thanks to Egag, Thomasjor, and Tink, you guys were all on the money. And a really heartfelt thumbs up to Grogan of Bitbender forums who posted bar none, the best install instructions for slackware I've seen (and in the last few days I've gone through dozens of them) and lead me right to the issue, and the solution. This guy rules!! I'd post the link, but newbie here, so not permitted to do url's yet.

But definitely do a search for "bitbender" and "grogan" and you should stumble on the site. Thumbs up to all you guys. Great Job!


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
Keyboard Prob on Slackware 10!! Help! Devboy Linux - General 3 12-26-2004 05:52 AM
Slackware install over Mandrake boot prob Sathington Linux - Newbie 2 04-17-2004 12:06 PM
slave hd and Slackware install prob pine0279 Linux - Hardware 2 07-03-2003 04:39 PM
slave hd and Slackware install prob pine0279 Slackware 3 07-03-2003 03:52 PM
Man 9.0 printer ? hardware prob ? install prob romcgill Linux - Hardware 2 02-24-2003 05:54 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 01:39 AM.

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