Linux - NewbieThis 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!
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
^yea, look at my previous post (last post on 1st page) I gave that one a shot on my own and it worked. Thanks so much man. I don't know why you guys actually help n00b's out so much, but it's a big help.
I am getting the same error as penguin. This must be a big issue with suse.
What does chainloader stand for ?
From the GRUB manual:
— Command: chainloader [--force] file
Load file as a chain-loader. Like any other file loaded by the filesystem code, it can use the blocklist notation to grab the first sector of the current partition with `+1'. If you specify the option --force, then load file forcibly, whether it has a correct signature or not. This is required when you want to load a defective boot loader, such as SCO UnixWare 7.1
Basically it is used to boot the OS that is installed in the first primary partition.
Windows likes to be the "only" OS installed in the system, in the first primary partition, so you have use first the map command so Windows thinks it's installed in the first hard disk and then the chainloader command to let it think that it's booting from the first primary partition.
I finally got it figured out. I had to change the windows tag in menu.lst to this.
and finally it's working, and my grub bootloader is successfully loading windows and suse.
I'm extremely happy and would like to than everyone here and at the forums on www.glug.us
thank you so much victorh and everyone else that helped me in this thread.
I just tried the same thing and this is what it is giving me
Error 11: Unrecognized device string
does anyone know what the problem is?
below is my menu.lst file
# Modified by YaST2. Last modification on Fri Mar 10 04:19:44 UTC 2006
color white/blue black/light-gray
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
kernel /boot/vmlinuz root=/dev/sda2 vga=0x317 selinux=0 resume=/dev/sda1 splash=silent showopts
###Don't change this comment - YaST2 identifier: Original name: windows###
title Windows XP
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
kernel /boot/vmlinuz root=/dev/sda2 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 edd=off 3
Hi Envision5000, the reason I ask about the bios boot order is because it's possible you have changed the hard disks from master to slave, for example if you have installed Windows in the first hard disk (master), and then you have changed this hard disk to be slave. Did you do something like that? Could you explain us how did you install windows and then Linux, in that time did you do some change in hard disks?
A reason that could explain your problem, is that GRUB is not recognizing correctly the order of the hard disks, one more thing could you post the content of the file /boot/grub/device.map:
Finally can you post the content of the file C:\boot.ini, in your Windows system?