LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
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!

Notices


Reply
  Search this Thread
Old 10-25-2012, 08:15 AM   #16
colorpurple21859
Senior Member
 
Registered: Jan 2008
Location: florida
Distribution: slackware64-current, puppy, ubuntu
Posts: 1,905

Rep: Reputation: 262Reputation: 262Reputation: 262

Have you tried rerunning liloconfig as root after booting your slackware from the either the installation cd/dvd or debian grub? Sometimes installing lilo by running liloconfig from the installed slackware will work, when installing lilo from the installation cd/dvd will not.
 
Old 10-25-2012, 08:38 AM   #17
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
Anyway i was angry at that time. thanks for the help and link, i m looking into it right now.
Hey no problem Jack! I was sure your Fatal error about the partition was due to the /dec... it all fit so perfectly!

I'm not sure were to point you now... but the post about running liloconfig seems like a good idea.

I am not positive but I think you could boot off the install CD/DVD and mount your Linux partition manually (there are on screen instructions when you first boot).

Then if you get it mounted you could run liloconfig. If nothing else maybe when you try to do the manual mount you might discover something else about the partition setup.

Keep at it and keep us posted!
 
Old 10-25-2012, 08:40 AM   #18
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by colorpurple21859 View Post
Have you tried rerunning liloconfig as root after booting your slackware from the either the installation cd/dvd or debian grub? Sometimes installing lilo by running liloconfig from the installed slackware will work, when installing lilo from the installation cd/dvd will not.
yes, that was the first thing i did when i got the erro. thanks
 
Old 10-25-2012, 08:44 AM   #19
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Fred-1.2.13 View Post
Hey no problem Jack! I was sure your Fatal error about the partition was due to the /dec... it all fit so perfectly!

I'm not sure were to point you now... but the post about running liloconfig seems like a good idea.

I am not positive but I think you could boot off the install CD/DVD and mount your Linux partition manually (there are on screen instructions when you first boot).

Then if you get it mounted you could run liloconfig. If nothing else maybe when you try to do the manual mount you might discover something else about the partition setup.

Keep at it and keep us posted!
finally i got i working,

commented these lines:
Code:
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255

table = /dev/sda
chroot
lilo -v volla!

no idea what those lines were about, any ideas?

thanks all of you guys.

Last edited by jack_; 10-25-2012 at 08:47 AM.
 
Old 10-25-2012, 08:53 AM   #20
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
finally i got i working,

commented these lines:
Code:
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255

table = /dev/sda
chroot
lilo -v volla!

no idea what those lines were about, any ideas?

thanks all of you guys.
Sweet! The lilo.conf file explains what those are, very weird... I have never ran into this!!

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

Basically indicates the Menu color and where the screen the other stuff is printed. It could be it had trouble with your resolution so it was trying to put these pieces in a place that was out of range with your resolution.

Not a very good explanation but that's the but I can figure looking at it!

EDIT: Thinking about it I wonder if it was just that Table line causing the problem? You might try uncommenting everything but the Table line and see if that works alone to fix it. It would be interesting to know..

I looked at my lilo.conf and I do not have the table= line. I also do not see it on the lilo page I linked you to. I wonder where it came from?

I would be willing to bet table=/dev/sda is the problem. And it fits the Fatal partition error message... but I thought I had that figured out before

Did you mean to type label=? That's the only thing that comes close. If your lilo.conf really has table= then that surely is the issue.

Last edited by Fred-1.2.13; 10-25-2012 at 09:09 AM.
 
Old 10-25-2012, 09:09 AM   #21
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Fred-1.2.13 View Post
Sweet! The lilo.conf file explains what those are, very weird... I have never ran into this!!

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used. We don't specify it here, as there's just one column.
bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
bmp-timer = 65,27,0,255

Basically indicates the Menu color and where the screen the other stuff is printed. It could be it had trouble with your resolution so it was trying to put these pieces in a place that was out of range with your resolution.

Not a very good explanation but that's the but I can figure looking at it!

EDIT: Thinking about it I wonder if it was just that Table line causing the problem? You might try uncommenting everything but the Table line and see if that works alone to fix it. It would be interesting to know..

I looked at my lilo.conf and I do not have the table= line.
thanks, more strange thing is after booting into system only the table entry is causing problem, i have uncommitted the other lines and its working fine but when i un-comment table entry it displays error again and i looked here:
http://linux.die.net/man/5/lilo.conf

it says something about partition table, care to elaborate?
 
Old 10-25-2012, 09:11 AM   #22
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
EDIT: Thinking about it I wonder if it was just that Table line causing the problem? You might try uncommenting everything but the Table line and see if that works alone to fix it. It would be interesting to know..

I looked at my lilo.conf and I do not have the table= line. I also do not see it on the lilo page I linked you to. I wonder where it came from?

I would be willing to bet table=/dev/sda is the problem. And it fits the Fatal partition error message... but I thought I had that figured out before

Did you mean to type label=? That's the only thing that comes close. If your lilo.conf really has table= then that surely is the issue.
you got it right.
the thing is when during installation i commented all three lines of windows entry including table it didn't worked.
 
Old 10-25-2012, 09:16 AM   #23
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
you got it right.
the thing is when during installation i commented all three lines of windows entry including table it didn't worked.
Is it possible you forgot to run lilo -v after commenting them out the first time? I have ran into that where I make a lilo change then reboot and not see the change, then realizing that I forgot to run lilo -v.
 
Old 10-25-2012, 09:20 AM   #24
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Fred-1.2.13 View Post
Is it possible you forgot to run lilo -v after commenting them out the first time? I have ran into that where I make a lilo change then reboot and not see the change, then realizing that I forgot to run lilo -v.
i never rebooted after installation with error on hand (i kinda knew what is going to happen after reboot so why bother). i just run lilo but i m sure -v is not a problem.
 
Old 10-25-2012, 09:24 AM   #25
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
thanks, more strange thing is after booting into system only the table entry is causing problem, i have uncommitted the other lines and its working fine but when i un-comment table entry it displays error again and i looked here:
http://linux.die.net/man/5/lilo.conf

it says something about partition table, care to elaborate?
I looked at the man page you linked... the best I can figure is the table= option is used when booting a different OS, like Windows or maybe it's just for old weird OS's like OS2, which is probably why I have never seen it before, however I do not see it in any of the dual boot example lilo.conf files I have looked at.

Very strange how it showed up in yours...
 
Old 10-25-2012, 09:25 AM   #26
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
i never rebooted after installation with error on hand (i kinda knew what is going to happen after reboot so why bother). i just run lilo but i m sure -v is not a problem.
Yeah the -v is just for verbose output and is optional. Weird stuff... but glad you got it going!!
 
1 members found this post helpful.
Old 10-25-2012, 09:29 AM   #27
jack_
Member
 
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Fred-1.2.13 View Post
Yeah the -v is just for verbose output and is optional. Weird stuff... but glad you got it going!!
Thanks alot for your help man.
 
Old 10-25-2012, 09:39 AM   #28
Fred-1.2.13
Member
 
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware 14.2 RC 2. Also some FreeBSD.
Posts: 116

Rep: Reputation: 52
Quote:
Originally Posted by jack_ View Post
Thanks alot for your help man.
No problem! Glad to help! Stuff like this is what makes Linux fun! You might want to mark this thread as Solved so others know you got it figured out.

Last edited by Fred-1.2.13; 10-25-2012 at 09:41 AM.
 
  


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
Error output with LILO while updating my lilo.config adilturbo Linux - General 4 10-17-2006 05:10 PM
Internal Error during Insallation agari Mandriva 3 03-16-2006 04:25 AM
Insallation Problem StarWolfe Linux - Newbie 2 04-16-2005 10:40 PM
Problem with insallation gkoussoulas Red Hat 2 02-22-2004 03:05 PM
PCTel Modem Insallation.. Nawaf0 Linux - Hardware 13 10-27-2003 04:08 PM


All times are GMT -5. The time now is 08:35 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration