Slackware This Forum is for the discussion of Slackware Linux.
|
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.
|
|
|
02-24-2014, 10:27 AM
|
#1
|
Member
Registered: Feb 2014
Posts: 44
Rep:
|
slackware reinstall lilo
Hi there! In my laptop I have windows 7 and slackware installed, and today I crashed my windows boot partition. So I decided to fix it from linux but I also crashed lilo boot manager. Now I managed to repair the windows boot sector with an install dvd, but now I only have windows 7 on boot. Is there a way to reinstall lilo so I can have back both systems at start up?
Last edited by danielxs; 02-24-2014 at 02:15 PM.
|
|
|
02-24-2014, 10:34 AM
|
#2
|
Member
Registered: May 2011
Distribution: Slackware
Posts: 57
Rep:
|
You can chroot into your Slackware installation and reinstall lilo from there. You can use the Slackware install media to do this, or just about any live system out there.
|
|
|
02-24-2014, 10:38 AM
|
#3
|
Senior Member
Registered: Apr 2005
Posts: 2,727
|
You should be able to boot from the Slackware install disc, chroot in and re-run lilo. That should be enough to reinstall it to the mbr.
//edit: gazumped...
Last edited by cynwulf; 02-24-2014 at 10:39 AM.
|
|
|
02-24-2014, 11:58 AM
|
#4
|
Member
Registered: Oct 2003
Location: Guildford, England
Distribution: Slackware64 -current running i3
Posts: 498
Rep:
|
I was actually just reading about this today, the link on slackdocs is here:
http://docs.slackware.com/howtos:sla...oot_from_media
|
|
|
02-24-2014, 12:14 PM
|
#5
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
Thank you rkfb! In fact I was doing chroot procedure for the first time and it's very cool. I followed commands from this link: https://wiki.archlinux.org/index.php/Change_Root I thought archlinux is very symilar with slackware. The point is I couldn't succeed to reconfigure lilo, though I changed /etc/lilo.conf "boot = /dev/sdax" becouse this is what I changed when I crashed lilo. I executed "lilo" command and I had 3 warnings. After reboot, windows started again. I think I will follow the chroot instructions from your link since my system is not arch, but slackware.
Last edited by danielxs; 02-24-2014 at 02:16 PM.
|
|
|
02-24-2014, 12:41 PM
|
#6
|
Senior Member
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223
Rep:
|
When on slackware chroot run "pkgtool" and re-run the lilo script, it will reinstall it on the MBR. Then, re-run the lilo commands.
|
|
|
02-24-2014, 12:48 PM
|
#7
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
I have this warnings: "LBA32 addressing assumed"; "Unable to determine video adapter in use in the present system."; Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation." I had this 3 warnings before, and lilo didn't start. My boot partition is /dev/sda7 ext 4 but windows mbr is in /dev/sfa1 which is ntfs. In lilo.conf I choose /dev/sda7 for boot. What should I do?
Last edited by danielxs; 02-24-2014 at 01:42 PM.
|
|
|
02-24-2014, 01:05 PM
|
#8
|
Member
Registered: Aug 2009
Location: Netherlands
Distribution: Slackware64-current
Posts: 167
Rep:
|
Quote:
Originally Posted by danielxs
I have this warnings: "LBA32 addressing assumed"; "Unable to determine video adapter in use in the present system."; Video adapter does not support VESA BIOS extensions needed for display of 256 colors. Boot loader will fall back to TEXT only operation." I had this 3 warnings before, and lilo didn't start. My boot partition is /dev/sda7 ext 4 but windows mbr is in /dev/sfa1 which is ntfs. In lilo.conf I choose /dev/sda7 for boot. Do I have to format that partition as boot again? What shoul I do?
|
I also get those 3 errors every time I install lilo from chroot. Is your Slack boot partition marked active?
|
|
|
02-24-2014, 01:08 PM
|
#9
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
Thanks a lot moisespredo. I had no ideea I could install scripts when chroot with pkgtool. Everything it's back to normal now. Thanks again to everyone who answered me in this thread. Now I learned a few new tricks
Last edited by danielxs; 02-24-2014 at 01:10 PM.
|
|
|
02-24-2014, 01:18 PM
|
#10
|
Senior Member
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223
Rep:
|
You are welcome
|
|
|
02-24-2014, 01:48 PM
|
#11
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
@JackHair By the way after repairing lilo from chroot--->pkgtool. I looked at /etc/lilo.conf file and the correct boot path is /dev/sda. I belive if I would have tryed to change it for the first time when I executed "lilo" maybe I would have got the same result... I don't know, but executing the lilo install script from pkgtool, I belive it's the right choice.
Last edited by danielxs; 02-24-2014 at 01:50 PM.
|
|
|
02-24-2014, 01:50 PM
|
#12
|
Senior Member
Registered: Nov 2013
Location: Brazil
Distribution: Slackware
Posts: 1,223
Rep:
|
Windows repair thing probably erased lilo off MBR so re-running the script was needed.
|
|
|
02-24-2014, 02:06 PM
|
#13
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
Quote:
Originally Posted by moisespedro
Windows repair thing probably erased lilo off MBR so re-running the script was needed.
|
I'm sure of that, becouse I had this problem before and I was reading somewhere, that windows interpret every linux boot manager as a virus.
But I think I had to do it that way, in order not to lose windows system. So I tryed to "fix" windows boot loader from linux and that's how I crashed lilo and the only solution for me was to repair windows boot loader with windows install dvd, and after that.... your solution Thanks again.
Last edited by danielxs; 02-24-2014 at 02:08 PM.
|
|
|
02-25-2014, 08:19 AM
|
#14
|
Member
Registered: Aug 2009
Location: Netherlands
Distribution: Slackware64-current
Posts: 167
Rep:
|
Quote:
Originally Posted by danielxs
@JackHair By the way after repairing lilo from chroot--->pkgtool. I looked at /etc/lilo.conf file and the correct boot path is /dev/sda. I belive if I would have tryed to change it for the first time when I executed "lilo" maybe I would have got the same result... I don't know, but executing the lilo install script from pkgtool, I belive it's the right choice.
|
I never use pkgtool to install lilo, don't want to install lilo on /dev/sda (my Windows drive). I do it by hand after pkgtool finished it's job. I have lilo installed on the MBR of /dev/sdd.
Quote:
Originally Posted by danielxs
I'm sure of that, becouse I had this problem before and I was reading somewhere, that windows interpret every linux boot manager as a virus.
But I think I had to do it that way, in order not to lose windows system. So I tryed to "fix" windows boot loader from linux and that's how I crashed lilo and the only solution for me was to repair windows boot loader with windows install dvd, and after that.... your solution Thanks again.
|
This is the reason I do the above.
Last edited by JackHair; 02-25-2014 at 08:20 AM.
|
|
|
02-25-2014, 10:39 AM
|
#15
|
Member
Registered: Feb 2014
Posts: 44
Original Poster
Rep:
|
@JackHair I tryed to install lilo without using pkgtool but I failed. I think it requires advanced knowledge or something, but don't be so harsh, after all when a beginner first install slackware will also install lilo in mbr.. /dev/sda by default, and until I crushed windows boot loader with some kind of antyspyware application I had no problem booting in both systems. Even though, with a crushed windows I could have boot slackware. So, if it works and if the team who develop the way to install lilo in slackware in /dev/sda think it's ok, then it's ok for a beginner like me either. I don't know if it counts but my windows boot partition is /dev/sda1 and lilo is installed in partition table /dev/sda. Perhaps there is a difference.
Last edited by danielxs; 02-25-2014 at 12:01 PM.
|
|
|
All times are GMT -5. The time now is 06:29 PM.
|
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
|
|