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 |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
10-23-2012, 03:53 PM
|
#1
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Rep: 
|
lilo error while insallation
i m trying to install slackware 14 amd64 on dell inspiron n5110 laptop, everything goes normal during installation but when i get to the part where lilo is installed i get following:
Warning : unable to determine video adapter in use in the present system.
Warning : Video adpater does not support VESA BIOS extensions needed for display of 256 colors.
Fatal: Partition entry not found. (what is meant by that if it means primary partition then i might ask where is root filesystem is being installed?)
i tried all almost all the listed framebuffer options in lilo. including standard.
Last edited by jack_; 10-23-2012 at 03:56 PM.
|
|
|
10-24-2012, 04:57 AM
|
#2
|
Member
Registered: Sep 2008
Location: Ioannina, Greece
Distribution: Gentoo
Posts: 332
Rep:
|
Can you attach your lilo.conf file? Are you installing on mbr or on root partition? From the error message looks like it tries to install on root partition instead of mbr but no partition is specified. The video errors could be ignorable.
|
|
|
10-24-2012, 06:51 AM
|
#3
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
lilo.conf does not get created in /etc, i m trying to install it on mbr.
also i have around 1.05m unusable space that i think is bothering lilo, output from cfdisk kinda look like this:
Code:
Unusable 1.05
sda1 Boot primary ext3 10485 << / partition
sda2 Primary swap 10485
sda3 Primary ntfs 52428
logical Free space 1.05
sda5 NC logical ext3 31457 << i mount /home here
...
how can i fix it without re-partitioning whole disk? its 500gb disk and there is a lot of important data on it.
|
|
|
10-24-2012, 07:24 AM
|
#4
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
ok fixed partition problem. here is lilo.conf
Code:
lba32
append="vt.default_utf8=0"
boot=/dev/sda
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
prompt
timeout = 1200
change-rules
reset
vga = normal
other - /dec/sda3
label = Windows
table = /dev/sda
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
but still got the same problem
Last edited by jack_; 10-24-2012 at 07:33 AM.
|
|
|
10-24-2012, 08:40 AM
|
#5
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
just installed debian everything worked fine.
i really think slackware should get rid of crappy lilo and start using grub.
i m seriously annoyed, what a piece of crap.
|
|
|
10-24-2012, 08:54 AM
|
#6
|
LQ 5k Club
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware64 15; SlackwareARM-current (aarch64); Debian 12
Posts: 8,311
Rep: 
|
If lilo was a "piece of crap" it wouldn't be the default bootloader in Slack.
|
|
|
10-24-2012, 09:30 AM
|
#7
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,848
|
Grub tends to install incorrectly at times also.
|
|
|
10-24-2012, 11:21 AM
|
#8
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
Quote:
Originally Posted by brianL
If lilo was a "piece of crap" it wouldn't be the default bootloader in Slack.
|
Well they need to re-think that.
|
|
|
10-24-2012, 11:27 AM
|
#9
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
Quote:
Originally Posted by colorpurple21859
Grub tends to install incorrectly at times also.
|
agreed but its easy fix. i came across a lot of problems on my friends systems and i fixed them in matter of minutes. plus there is lot of helping material out there and also there are many people who can help you out unlike lilo.
if it is so great how come no one solved my problem? i'll be happy to know how to fix it if anyone can help. i love to learn but don't want to bump my head on brick wall.
|
|
|
10-24-2012, 01:30 PM
|
#10
|
Member
Registered: Sep 2008
Location: Ioannina, Greece
Distribution: Gentoo
Posts: 332
Rep:
|
Quote:
Originally Posted by jack_
ok fixed partition problem. here is lilo.conf
lba32
append="vt.default_utf8=0"
boot=/dev/sda
bmp-colors = 255,0,255,0,255,0
bmp-table = 60,6,1,16
bmp-timer = 65,27,0,255
prompt
timeout = 1200
change-rules
reset
vga = normal
other - /dec/sda3 <- is this correct?
label = Windows
table = /dev/sda
image = /boot/vmlinuz
root = /dev/sda1
label = Linux
read-only
|
Anyway, I'm glad that slackware uses the LiLo and not the crappy Grub. I have never used a system of my own with grub, including Slack, Debian, Gentoo, Ubuntu, Backtrack...
|
|
|
10-24-2012, 05:45 PM
|
#11
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
Quote:
other - /dec/sda3 <- is this correct?
label = Windows
table = /dev/sda
|
yes, and i tried commenting out these lines, still no luck.
thanks for valuable reply.
No disrespect to lilo developers but the thing is when i was learning grub i never got stuck like this. People who uses grub not just say its outstanding, they solve the problem too.
maybe i m annoyed too much, i tried so many things and nothing seems to work.
its very definition of crappy software, no matter what you do it still sucks.
thanks again, looking forward for your reply because it seems you are the only one who is trying to help instead of just apprising lilo.
would you please also hook me up with some material so i can make myself familiar with lilo?
|
|
|
10-24-2012, 07:55 PM
|
#12
|
Member
Registered: Jan 2006
Location: Midwest USA
Distribution: Started with Slackware - 3.0 1995 Kernel 1.2.13 - Now Slackware Current. Also some FreeBSD.
Posts: 126
Rep:
|
Quote:
other - /dec/sda3 <- is this correct?
|
This line should be /dev/sda3
Looks like you have a typo, you typed dec instead of dev. Damn crappy Lilo not able to detect and fix your typo.
Quote:
Fatal: Partition entry not found. (what is meant by that if it means primary partition then i might ask where is root filesystem is being installed?)
|
Well, actually it did detect YOUR error.. that's why you are getting this error message. It doesn't know WTH /dec is.
As has been said, you can ignore the warning video errors.
I have been using Slackware since version 3.0 way back in 1995, have installed it on to many machines to count, servers, desktops laptops.... I have never had an issue with Lilo. But again, I have never dual booted either.
Quote:
thanks again, looking forward for your reply because it seems you are the only one who is trying to help instead of just apprising lilo.
|
People might be more inclined to help if you drop the immature cocky attitude, I understand your frustrated but saying things like Lilo is crappy software and then second guessing the Slackware developers... who have been doing this probably longer than you have been alive... well that is just over the top, next you will be giving advice to Linus on how to fix all the stuff he has screwed up in the kernel!
That said, I hope you get it worked out, really Lilo is quite simple, simpler that Grub, you just need to get familiar with it and watch those typos!
Oh and remember to run "/sbin/lilo -v" after editing and saving lilo.conf.
Here is a clear and simple explanation on how Lilo works:
http://www.control-escape.com/linux/lilo-cfg.html
Last edited by Fred-1.2.13; 10-24-2012 at 08:47 PM.
|
|
|
10-25-2012, 02:40 AM
|
#13
|
Member
Registered: Sep 2008
Location: Ioannina, Greece
Distribution: Gentoo
Posts: 332
Rep:
|
Also, the lilo.conf man page is quite explanatory. Once you get familiar with it, everything will be piece of cake. Even dual, tripple, quadrupel boot. It really isn't crappy, it just demands more user intervention than grub.
One more thing. I'm not familiar with that "table" entry, but will look into that.
Last edited by segmentation_fault; 10-25-2012 at 02:46 AM.
|
|
|
10-25-2012, 06:51 AM
|
#14
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
Quote:
Originally Posted by Fred-1.2.13
This line should be /dev/sda3
Looks like you have a typo, you typed dec instead of dev. Damn crappy Lilo not able to detect and fix your typo. 
|
well typo here not in lilo.conf. i typed it here by looking on the laptop screen. but i double checked its fine and still got the error, also i think it should have worked when i commented windows entry.
I did not manually created lilo.conf file it was generated during installation by setup procedure. i tried to fix it afterwards bit as of now i m failing miserably.
my "immature cocky attitude" was after when i was trying my best to fix the problem and everyone else was jut ignoring the problem and apprising lilo. i m not "second guessing" anyone.
Anyway i was angry at that time. thanks for the help and link, i m looking into it right now.
Last edited by jack_; 10-25-2012 at 07:01 AM.
|
|
|
10-25-2012, 06:55 AM
|
#15
|
Member
Registered: Oct 2012
Location: /
Distribution: Slackware, Debian, Ubuntu, CentOS, OpenSuse
Posts: 35
Original Poster
Rep: 
|
Quote:
Originally Posted by segmentation_fault
Also, the lilo.conf man page is quite explanatory. Once you get familiar with it, everything will be piece of cake. Even dual, tripple, quadrupel boot. It really isn't crappy, it just demands more user intervention than grub.
One more thing. I'm not familiar with that "table" entry, but will look into that.
|
Thanks, i m going to look into it.
|
|
|
All times are GMT -5. The time now is 02:19 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|