SUSE / openSUSEThis Forum is for the discussion of Suse 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.
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.
I successfully loaded Suse 10 on a SATA HD. The install saw that I had XP on another IDE HD, and I was able to happily use GRUB to boot to either Suse 10 or XP with no problems.
I got a beta version of Windows Vista and installed it on a partition on another IDE HD. After this, I lost GRUB---so, I reinstalled Suse 10 on the SATA HD. I got GRUB back, but I can't boot to either XP or Vista. For the Windows OSes, GRUB gives me two choices: "windows1" and "windows2". When I choose either one of them, I just get this message with blinking cursor: "chainloader (hd0,0)+1" Any suggestions?
Just reinstalling grub (from a rescue-CD) would have been sufficient - since windows overwrites the MBR when you install it...
you could post the output of these commands:
fdisk -l
and also the partition table from the other hd (sdb ? sdc ? - I don't know which it is)
cat /boot/grub/menu.lst
or
cat /boot/grub/grub.conf
(maybe just one of these exist on your system...)
nope - it doesn't - its just the half of it...(your grub configuration-file is missing...)
cat /boot/grub/menu.lst
and: what OS is on which disk again?
Here are the results of running the two commands you posted up:
whoomjah@linux:~> su -
Password:
linux:~ # cat/boot/grub/menu.lst
-bash: cat/boot/grub/menu.lst: No such file or directory
linux:~ # cat/boot/grub/grub.conf
-bash: cat/boot/grub/grub.conf: No such file or directory
linux:~ #
It is just not possible that there is no grub.conf or menu.lst
You use grub to boot - and it works - therefore there IS a config-file.
Maybe you have a separate /boot partition - which was not mounted when you issued these commands?
There has to be a directory /boot and therein is your kernel as well as another directory
named grub - and in this directory are grub's files and the config-files
I just saw it - might have been a typo on your answer:
cat/boot/grub/grub.conf is wrong (space missing)
cat /boot/grub/grub.conf is working...
I suggest you do the following (commands - as root):
cp /boot/grub/menu.lst /boot/grub/menu.lst-backup
mind the spaces
This copies the file to menu.lst-backup - that way you will always have the original, which works to boot suse...
then you copy+paste this changed config-file into /boot/grub/menu.lst - so you have this one instead of the old one.
Or you edit in the changed things by hand...use "mc" which is a file-manager with everything built in (F4 lets you edit the file currently selected) or "nano" or "vi" or any other text-editor you like.
It is in a way self-explanatory:
the hide - unhide lines make one windows invisible to the other - because this _could_ cause problems
the "rootnoverivy" lines instruct grub not to try to mount the partition like it does when encountering the "root" statement (present in the entries to boot linux)
Give it a try - the Suse sections are unchanged - so it will still work at least as it was - if not better - which I hope
Code:
#----- start of changed menu.lst ------------
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd2,1)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd2,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=0x317 selinux=0 resume=/dev/sda1 splash=silent showopts
initrd /boot/initrd
title Windows XP
unhide (hd0,0)
hide (hd1,0)
rootnoverify (hd0,0)
chainloader +1
title Windows Vista
unhide (hd1,0)
hide (hd0,0)
rootnoverify (hd1,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
chainloader (fd0)+1
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE LINUX 10.0
root (hd2,1)
kernel /boot/vmlinuz root=/dev/sda2 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
initrd /boot/initrd
#----- end of changed menu.lst ------
-edit-
Sorry - I made a typo myself:
rootnoverivy needs to be rootnoverify
changed it...
With which editor are you familiar?
And how (where) do you read this post? I thought you could just copy+paste it, but maybe not...
You run suse - are you just on console or are you using gnome or kde or another graphical desktop?
What do you mean by:
Quote:
I log in as root, but get permission denied
? What and where are you doing to get this message?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.