LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Home Forums Tutorials Articles Register
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 06-22-2011, 05:09 PM   #1
jsmith6
Member
 
Registered: Feb 2006
Distribution: Slackware 13.1 / 13.37
Posts: 91

Rep: Reputation: 16
the "L 02 02 02" error on when upgrading to Slack 13.37


I just upgraded from 13.1 to 13.37 and I'm getting the L 02 02 02 error. This means that lilo can't find the partition it's told to boot. It's strange because:

- I haven't tweaked anything in the hardware
- I kept the same partitions, just formated
- I'm using ext3, as with 13.1
- I installed lilo on MBR (while on setup, and later with -M /dev/sda)
- I choose the huge smp kernel, as with 13.1
- I have only two partitions, root (sda1) and swap (sda2)
- the root partition is the active one (asterisk), on fdisk

So I tried:

- reseting the BIOS
- removing the UTF8 setting on lilo.conf
- using the lilo.conf that worked with 13.1

They all failed. I don't even know what to try! Any ideas?

PS: The hardware is a Pentium 4 1500Mhz with 512MB RAM on Asus P4B.

Last edited by jsmith6; 06-23-2011 at 10:58 AM.
 
Old 06-22-2011, 05:27 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,661

Rep: Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784Reputation: 1784
How do you upgrade your Slackware?
I upgraded my virtual machine from 13.1 to -Current and it works fine here
 
Old 06-22-2011, 06:11 PM   #3
jsmith6
Member
 
Registered: Feb 2006
Distribution: Slackware 13.1 / 13.37
Posts: 91

Original Poster
Rep: Reputation: 16
I boot up from the DVD and run setup.

When prompted, I quick-format the ext3 partition and simply continue setup.
 
Old 06-22-2011, 06:34 PM   #4
piratesmack
Member
 
Registered: Feb 2009
Distribution: Slackware, Arch
Posts: 519

Rep: Reputation: 142Reputation: 142
Quote:
Originally Posted by jsmith6 View Post
and later with -M /dev/sda)
I don't think the -M option actually installs LILO to the MBR, it just writes a generic MBR that tries to load boot code from an active partition (useful if you installed LILO or another boot loader to a partition boot sector)

You can boot your system using the Slackware install disc (it gives you instructions when you boot from it). Then check your lilo.conf and reinstall with just '/sbin/lilo'

Last edited by piratesmack; 06-22-2011 at 06:43 PM.
 
Old 06-23-2011, 03:15 AM   #5
jsmith6
Member
 
Registered: Feb 2006
Distribution: Slackware 13.1 / 13.37
Posts: 91

Original Poster
Rep: Reputation: 16
Quote:
Originally Posted by piratesmack View Post
You can boot your system using the Slackware install disc (it gives you instructions when you boot from it).
I've been booting by just pressing ENTER, mounting and chroot'ing my partition. Then I did lilo -v. I just tied your way. Didn't make any difference.

Quote:
Originally Posted by piratesmack View Post
Then check your lilo.conf and reinstall with just '/sbin/lilo'
Well, I've already checked lilo.conf. And again tried with '/sbin/lilo', but no results. I'm all out of ideas. If you can think of a change to make in lilo.conf, I'm all ears!
 
Old 06-23-2011, 10:58 AM   #6
jsmith6
Member
 
Registered: Feb 2006
Distribution: Slackware 13.1 / 13.37
Posts: 91

Original Poster
Rep: Reputation: 16
After everything else failed, I installed again Slack 13.1 (base system) and it booted without any problems.

So then I went and installed Slack 13.37 base system, aaaand... it booted with any problems. That's very strange. I did the same choices, kept the same options.

After that I did one more install of 13.37 to get my typical functional system.

A thanks to everyone who replied.

Problem is solved but I don't know what caused it! So, if anyone has an idea, please tell me.
 
  


Reply



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
".config" and ".kde" folders are being created under root directory (Slack Current) piratesmack Slackware 8 03-12-2011 11:06 PM
"unable to eject" error when trying to safely remove ipod shuffle in slack 12 mattydee Slackware 10 07-06-2007 05:03 PM
ABIT "KN8 ultra" chipset "NFORCE4" & Slack 10.2 k6_400 Slackware 5 09-06-2006 06:13 PM
"su missing" KDE error after upgrading 2.6.8.1-15 to 2.6.15 kernel in Mandrake 10.1 darth_pyro Linux - Software 3 01-16-2006 05:46 PM
Assigning "unique name" to "Extraversion" when upgrading Kernal MatthewASmith79 Linux - Newbie 5 08-26-2004 08:31 AM

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

All times are GMT -5. The time now is 10:39 PM.

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