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.
|
 |
04-02-2006, 06:22 AM
|
#1
|
Member
Registered: Mar 2006
Posts: 71
Rep:
|
Booting windows&slack
Hi
I just installed slack 10.2 on my system.When I turn my PC on,I get a black screen with some text that begins with ''GNU GRUB''...I think that this is the bootloader,right?You can type commands there.So how can I boot slack and windows from there?
thanx in advance
|
|
|
04-02-2006, 06:27 AM
|
#2
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
I don't know man. Lilo is the default bootloader for Slackware. What did you do?
|
|
|
04-02-2006, 06:38 AM
|
#3
|
Member
Registered: Mar 2006
Posts: 71
Original Poster
Rep:
|
Quote:
Originally Posted by Randux
I don't know man. Lilo is the default bootloader for Slackware. What did you do?
|
I think I know the answer myself.I installed lilo into superblock.You have to install it to MBR right?
|
|
|
04-02-2006, 06:43 AM
|
#4
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
If you installed Lilo to the superblock and you're getting a grub message, it means that this is not the first time someone did something on that pc.
Always keep a live CD around. Kanotix is great, Slax is good.
Boot from the live CD. Either find your lilo.conf in the filesystem of your Slackware (or other) linux system and fix it or make a new one.
lilo -v -t -b /dev/hda # test without installing anything
lilo -v -b /dev/hda # when above runs cleanly, install in MBR
P.S. Since you have the Slackware installation CD, use it. Boot into it and then at the prompt start editing a lilo.conf. I can't remember what editors come on the Slackware boot disc (if any) but I hope you know vi.
If not, chroot into your Slackware system:
mkdir /mnt/myslack
mount /dev/hdan /mnt/myslack # where "n" in "hdan" is Slackware partition number
chroot /mnt/myslack # now you are running in your Slackware system
use whatever you need to fix the /etc/lilo.conf and run lilo as above
edit: fixed spelling error in Kanotix
Last edited by Randux; 04-03-2006 at 04:45 AM.
|
|
|
04-02-2006, 07:16 AM
|
#5
|
Member
Registered: Mar 2006
Posts: 71
Original Poster
Rep:
|
Quote:
Originally Posted by Randux
If you installed Lilo to the superblock and you're getting a grub message, it means that this is not the first time someone did something on that pc.
Always keep a live CD around. Kantox is great, Slax is good.
Boot from the live CD. Either find your lilo.conf in the filesystem of your Slackware (or other) linux system and fix it or make a new one.
lilo -v -t -b /dev/hda # test without installing anything
lilo -v -b /dev/hda # when above runs cleanly, install in MBR
P.S. Since you have the Slackware installation CD, use it. Boot into it and then at the prompt start editing a lilo.conf. I can't remember what editors come on the Slackware boot disc (if any) but I hope you know vi.
If not, chroot into your Slackware system:
mkdir /mnt/myslack
mount /dev/hdan /mnt/myslack # where "n" in "hdan" is Slackware partition number
chroot /mnt/myslack # now you are running in your Slackware system
use whatever you need to fix the /etc/lilo.conf and run lilo as above
|
Thanx!It works now.
|
|
|
04-02-2006, 07:24 AM
|
#6
|
Senior Member
Registered: Feb 2006
Location: Siberia
Distribution: Slackware & Slamd64. What else is there?
Posts: 1,705
Rep:
|
Thanks for letting us know!
|
|
|
04-02-2006, 07:05 PM
|
#7
|
LQ Veteran
Registered: Mar 2003
Location: Boise, ID
Distribution: Mint
Posts: 6,642
Rep:
|
Excellent - congrats on solving the problem Deelk and thanks for posting back with the update, as it will be very helpful to future readers who encounter the same situation
|
|
|
All times are GMT -5. The time now is 03:50 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
|
|