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!
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.
Goodmorning Paul,
I wondered about the RO as well, but reading the GRUB documentation it says this part is passed to the kernel commandline. (I just used it as written in the O'Reilly book).
As you see it is NOT in the menu.lst.
Last night I also tried to repair the bootloader. I told you there was a error message. Now I just checked the menu.lst and there I see :
***********************
# Modified by YaST2. Last modification on Fri Oct 28 23:53:10 2005
color white/blue black/light-gray
default 0
timeout 8
gfxmenu (null)/
###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (null)/ root= vga=0x31a splash=silent desktop resume=/dev/hda1 showopts
initrd (null)/
**************************
See the device (null) ???? So yast-repair must have had problems!!!!
I think for the moment we must leave GRUB as it is and go another way. Preferable WITHOUT any bootloader!!!
Last test for grub.
I created a GRUB boot floppy according to the official GRUB manual (http://www.gnu.org/software/grub/):
# cd /usr/lib/grub/i386-pc
# dd if=stage1 of=/dev/fd0 bs=512 count=1
1+0 records in
1+0 records out
# dd if=stage2 of=/dev/fd0 bs=512 seek=1
153+1 records in
153+1 records out
#
I booted from this floppy and then I gave the following commands :
grub > root (hd0,1)
grub > find /boot/grub/stage1
After the find command nothing happens anymore and I have to reset the system.
It seems there are problems with the HDD with this Mobo.
I went into another direction now.
I installed LiLo, configured it and wrote a new MBR using "lilo -v".
When I reboot LiLo stalls with just a "L". Does this give a clue???
I still believe with the swap of the Mobo went something wrong what not can be repaired by yast.
Maybe a driver missing???
Hello Peter, I Think I know now where your problem is comming from:
The swap device is a raw-partition. It doesn't about files inside. It is like an additional memory and overwright everything. Put your swapspace to an other place
maybe on the second disk for testing rewrite grub or lilo (but I have no expieriance
with lilo). Try out this, I wait for your answer berfore I go to sleep(think CET+5 tomorrow CET+6)
Regards
Paul
If you don't know how to this:
Look into your /etc/fstab
check for /dev/swap
copy this line and replace the new diskparameters.
Don't forget to comment the old entry with #
Hello Paul,
Thanks for your answer but remember it was all working fine before I changed the MoBo.
For the moment I don't want to change the disk partitions because the system is still working fine. Just need to boot it manually by the install CD.
But thanks for your hint. Will keep it in my mind.
I am going out soon, so I won't check this before tomorrow.
GRUB and LILO always conflict with Windows. And GNU GRUB is not so robust, causing many problems during boot.
So try GRUB for DOS please. It is a cross-platform boot loader based on GNU GRUB. The GRUB.EXE can be started from DOS/Win9x; and GRLDR can be started from BOOT.INI of Windows NT/2K/XP/2003; and even more, the GRUB.EXE can be started from LINUX via the KEXEC tool.
By using GRUB.EXE or GRLDR, you don't have to touch your MBR. It is the safest way coexisting with DOS/Windows.
You needn't install GRUB for DOS. Just run GRUB.EXE from DOS, or append a line of "C:\GRLDR=START GRUB" into your BOOT.INI(restart and select the "START GRUB" menu item), that will do.
Hello TB,
Thanks for your answer. My system does NOT have a DOS/Windows environment, just linux, but I will have a look and see if I can build a boot floppy.
Will post the results here.
There are two floppy images in the GRUB4DOS release, both are 1.44M. One is FAT12 formated and the other is EXT2 formated. You can use either of them to create a bootable floppy and boot to GRUB. Or you can use your DOS floppy and simply copy GRUB.EXE onto it.
Sorry it take so long for me to respond, but I have been on vacation for a while (If you want to see the pictures : http://sa2006.envim.com) .
After I went back I decided to install Suse 10.0. When finished it all worked fine. I suppose the Suse 9.1 did not have the right drivers for the (new)MoBo. Now this item is solved (Suses 10.0 upgrade gave me new hassels).
For now, thank you all for your usefull suggestions...
Peter...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.