OpenSUSE Install :: Difference Between GRUB And LILO?
Jul 23, 2010LILO not supported?
Does anyone know the diff between GRUB and LILO?
LILO not supported?
Does anyone know the diff between GRUB and LILO?
Difference between Grub,LILo and Uboot loaders
View 3 Replies View Relatedsince ms dos wasn't meant to be booted from cd (it was used from floppy) and i have tried buring the contents of every ms dos floppy to a cd and no dice i am guessing that it needs a bootloader so i can boot up the setup wizard
before anyone suggests that this thread has nothing to do with linux i will just point out that this thread is asking about grub and that is a linux catagorie
I have one install (Slack 12.2) on /dev/sda11, and GRUB (GNU GRUB 0.97) boots it without a problem. I just installed a new Slack 13.1 on /dev/sda1, and GRUB fails to boot it as follows:Quote:
grub> root(hd0,0)
> Filesystem id type ext2fs, partition type 0x83
grub> kernel /boot/vmlinuz root=/dev/sda1
[code]....
I usually install grub straight away after an install but this time it hasn�t worked for some reason after installing 13.1 on a new lappy. I have tried grub, grub2 (from sbo) and lilo; nothing I install into MBR will boot my slackware installation, I have to use the boot USB stick every time.
grub-legacy would be my preferred one so i�ll ask for help specifically with that. This is what im doing so far -
[Code]...
I have a Dell Inspiron 1721. Recently I replaced Windows Vista Home Edition (32 bit) with Slackware Linux 13.
Lilo wouldn't work, when I turned on the computer it printed "Li" and then 20 lines of 090909... and then the computer would hang up. So I just used my Slackware-boot-flashdrive-thing that I created during installation to boot my computer and told myself that I would fix it later.
Also, when I installed, cfdisk (or it might have been sfdisk) complained that /dev/sda did not contain a valid MS-DOS partition table. fdisk still worked, so I used it to create a new table, and cfdisk worked fine and the installation went along normally.
I reinstalled Slackware about two days later (I realized that I had installed the 32 bit version instead of the 64 bit). Lilo still didn't work.
I thought it might be something wrong with the Slackware DVD, so I downloaded and attempted to install about 4 different distributions. None of the CDs would work. The computer would start up, Linux would start to load, and the computer would freeze.
Xubuntu was the only distro I had that I could get to install. Halfway through the installation, (Surprise!) I got an error, something like "Package Grub failed to install, you will not be able to boot your new operating system".
The rest of the install went fine, so I restarted my computer and tried to use another one of my CDs to boot Xubuntu. I got the error "/dev/sda does not contain a valid partition table", and later "ext4-fs: checksum failed on dev sda at sector...", and "please specify a valid partition for root=". I am absolutely positive that I entered the correct partition, I triple checked and entered other partition names to make sure.
I'd also like to add that the computer makes horrible crunching noises when it starts up and when I do stuff like press keys. So is something seriously wrong with my hardware, or is there another explanation for all of this? Because I really don't want to have to try to repair the computer and can't pay to have it repaired.
I would like to know if there is any differences on how to install and to configure GRUB 2 in the different architectures (BIOS/IBM PC-Compatibles, EFI/MacIntel and Corebbot)? Does the Ubuntu installer automatically recognize the different architectures and install the appropriate GRUB 2 package ('grub-pc', 'grub-efi' or 'grub-coreboot' according to the arch)? Or does it just install 'grub-pc'? Is the location of GRUB 2's configuration files different depending on the arch of the computer? Or are they all located in '/boot/grub/', '/etc/grub/default' and '/etc/grub.d/', no matter the arch of the computer? Are the files' structure and options to configure GRUB 2 ('/etc/grub/default' and the scripts in '/etc/grub.d/') different depending on the arch of the computer?
View 3 Replies View RelatedI'm trying to go from LILO to GRUB (legacy). However, when I try to "sudo grub-install /dev/sdb", I get: [URL]
View 1 Replies View RelatedI work in a very restrictive environment and I want to use linux on my work laptop (currently running Windows XP prof). I am planning to install linux in a dual boot mode but I dont want to install grub/lilo or any other boot loader. i cannot even modify Windows bootloader to boot into linux partition.
Is there a way I can boot into linux partition without installing new boot loader or modifying the current windows boot loader? Any boot CD etc available that can boot into linux partition from my laptops HDD?
I'm looking for an alternative boot loader (for hard drive) to get away from GRUB and LILO. I want something that is not bloated like GRUB and does not require rebuilding a table of block numbers like LILO. Something simple and basic ... like a boot loader should be.
View 8 Replies View RelatedI just installed Slackware 13.37, and it's my first version of Slack.
After installing, Grub was still installed on my system, but since it is supposed to boot an OS that's no longer on the hard drive by default, it drops to the Grub Rescue prompt every time I boot.
How can I boot Slackware from grub, or get lilo to boot my system instead of grub?
This post has been updated with new information. First, here's fdisk -l:
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
[Code]....
I have 2 drives, the first has Slackware 13.0 and FreeBSD 7.2. The second has Windows 7. Lilo configured to boot all three, no issues. Perfect. The first drive has 100GB of free space after FreeBSD and today I decided to install Open Solaris on that free space. The install failed, as in Solaris displayed such a message. I did read the Solaris install docs, etc. And it did mention no to install unless it preceded any Linux Swap partitions. There are, I did, but that's not my issue now.
After rebooting, it amazingly loaded FreeBSD by default. No Slackware. So I booted the slackware DVD, ran fdisk and made Slackware the default boot partition, yada yada. Now when it rebooted it gave a little message down in the left hand corner of the screen like "RRG B" highlighted in a red box. Now pressing enter will cause Windows 7 to boot from the second disk. I mounted the slackware partition from the DVD and am there now. Will just running lilo again put everything back to normal? Apparently Solaris left behind a piece of that ill behaved GRUB! (No flames!!!) :-) How do I make it go away?
I am thinking about maybe trying "LILO" [URL] ....
For my boot loader, from what I have read it sounds even more tempting.
I am totally sick of GRUB, even though it is what seems to be the most popular,and is what normally is used as the "default" when any linux system is installed, that is what the install ISO's use, but anyway, that is another topic, over the years, "grub failing", has been a problem for me , many times.
I saw this (From LILO to GRUB Howto).
I somehow recalled a rule re the location of the boot partitions with LILO being required to be in the first part of the drive (1024 cylinders, it seems) and I found it indeed in an old doc:
Boot Partition: Your boot partition ought to be a primary partition, not a logical partition. This will ease recovery in case of disaster, but it is not technically necessary. It must be of type 0x83 "Linux native". If you are using lilo, your boot partition must be contained within the first 1024 cylinders of the drive. (Typically, the boot partition need only contain the kernel image.) Is this still valid in GRUB, esp in Fedora 10?
I've run Debian on my laptop for quite some time now with no problems. I installed Slack to a new partition created in the free space of my hard drive, and I thik this was my mistake: I let Slack automatically configure the MBR with lilo (can't remember - I should stop operating on the MBR at 4 AM.) Now Slack runs just fine, but upon bootup I would like to be able to boot either Debian or Slack, but instead I just have a Slack splash and the only option is to press enter to boot Slack.
Code:
I believe sda1 is the root directory of my Debian install.
Code:
In the above table, sda10 is the swap I created for Slack and sda3 is the root directory for Slack. All other partitions were there before (my initial Debian install).
Thus my partitions are apparently intact and visible by the MBR (is it correct that the MBR holds the list of partitions on a disk?) but for some reason I don't have the option to boot Debian at all - just Slack.
I have a feeling this is a LILO/GRUB issue, but I don't know where to start.
EDIT: more poking around seems to reveal that it is the configuration of LILO that is the problem. Observe the following output:
Code:
Not much of an expert with computers and completely new with Linux. I am considering installation of openSUSE 11.3 and I know for a fact that my PC can handle the 64-bit version. Questions:
1) Do the 32- and 64-bit versions install with the same kind of software packages?
2) Does the 64-bit version have more/less/equal available software in the repositories for download?
3) If I wanted to set up a workgroup with another PC that has Ubuntu 10.04 LTS and Windows XP Pro (both 32-bit) installed, would it matter which bit version of openSUSE I use? (In terms of ease in creating the workgroup, access of files, etc.)
4) If I install the 32-bit version now, can I switch to the 64-bit version later? What are the caveats?
As I said at the beginning, I am not much literate on these things so I hope I am not asking nonsense questions...
On the downloads page I notice the cd's are not upgradable, but the dvd free version is.. This seems backward to me. The cd's have less stuff so they should be able to be upgraded to the fuller version via the repos - or at least get all the stuff it's missing. Where as the dvd's are stuffed with over 3 gigs of things one would think it should not need any upgrading.
Or are they talking about being upgradable to the paid for version? or something entirely different?
I am new to Linux. I want to set up a home file/media server using Linux and have been investigating the possibility of using OpenSUSE for this task for a couple days now. I posted up some questions over at linux questions, but figured this one would be better suited for the OpenSUSE forum. My question is simple, is there any fundamental difference between OpenSUSE Server, and OpenSUSE desktop?
What I mean is, is there any difference to the basic programming of the operating system. From what I gather, when you install a Linux Distro for a server, it is just a striped down version of the desktop install. It has no GUI, and installs the complete bare minimum of software to get your server up and running. Is this correct? I am asking these questions because, as I said, I am new to Linux. I am not comfortable using command line only, and would very much like to install the desktop version of OpenSUSE, plus Samba, openSSH and Webadmin, then use that configuration for a server. Would setting up OpenSUSE as I stated above be the same as using the server install, just more "bloated?" Or is the server version of OpenSUSE coded differently?For example, comparing Windows Vista to Windows Home Server. Windows Vista isn't practical to use as a home server OS, simply because it was never coded to be one. Where as Home Server comes with software and is setup to be a server.
From what I understand, and I could be wrong, and please correct me if I am. Linux is much different. Any Linux distro can be a server, even the desktop version. You just need to get the proper programs (like Samba, SSH, Webadmin) for the job. The people who use the Server version, simply just want something less bloated then the desktop version, but the desktop version works just as good as a server if you have the proper hardware? I was debating on putting Windows Home server on the machine, but very much want to learn Linux, and figure this is as good of an opportunity as any. It also helps that a desktop install of OpenSUSE takes less resources then Windows Home Server.
Is there a description of the features and differences between the Desktop and Default kernels? Did "Desktop" arrive with 11.2 and 2.6.31? I did not notice it at first. I loaded 11.2 on a desktop machine and both default and desktop kernels were loaded to system, with Desktop set as default in grub. I have been working thru several "strange" behaviors ever since loading 11.2. At the top of my list has been the ability to shutdown the system from remote logins. I normally connect to the system via a Xwindows package (Xmanager). X works fine and I could shutdown via the GUI (Application Launcher - Leave-Shutdown).
When connected via a remote ssh link, either from a windows machine or a different linux machine, attempts to shutdown (shutdown -H now) send the expected messages, close the remote connections but leave the system still powered on but in a no-remote-connectivity state. When I upgraded to KDE 4.3.4 following the Forum Repository guidelines, I could no longer shutdown via the GUI. In searching about, I found that the Desktop kernel was running. Changed grub, rebooted under default, shutdown under GUI works again. So, for starters, I am trying to decide which kernel environment (default or desktop) should be my target for continuing to work thru issues.
openSUSE-11.3-Addon-Lang-i586.iso and openSUSE-11.3-GNOME-LiveCD-i686.iso
Index of /distribution/11.3/iso
And what is openSUSE-11.3-Addon-NonOss-BiArch-i586-x86_64.iso ?
A few upgrades ago, I had also a desktop-kernel installed. I tried starting with the standard and the desktop kernel, but could not see a difference. Why this desktop-kernel and what's the difference with the standard kernel?
HP laptop with Intel(R) Core(TM)2 CPU T5600 - OpenSUSE 11.3 -KDE4.4.4
I've been running openSuse 11.2 for a while on my notebook.Today I turned it off at work and came home. When I tried to turn it on, it boots, shows a black screen written 'GRUB' and then NOTHING. It doesn't complete the boot process.
View 9 Replies View RelatedI'm fairly new to linux, and a few days ago, as I was updating my system, I got the "EBDA is big ; kernel setup stack overlaps LILO second stage" error after reboot. I use a 3- boot, ( Win XP / Debian / Debian) and Windows XP works fine, but I can't launch any of the Debian. I googled the message, and I found this link :
[URL]
The only problem problem is that when I try to chroot, I got another message, "chroot: failed to run command `/bin/bash': No such file or directory" I googled this message too, but found no relevant answers. I am now using a knoppix usb drive to try to repair the lilo, but I ran out of ideas ...
I started another thread about this to get help booting into openSUSE after Fedora rewrote my bootloader and deleted all other entries. I managed to fix it but I never did find out why the following commands caused my system to boot to the grub shell instead of the grub menu.
Code:
grub
root (hd0,3)
setup (hd0)
quit
reboot
Can anyone explain to me why these commands caused my system to boot directly to a grub shell? It's as if there were no /boot/grub/menu.lst files for it to use, but after I got everything back to normal, the files were still there.
If it helps, this is how the drive was setup before and now, except Fedora was on /dev/sda4 and has since been deleted.
Code:
Device Boot Start End Blocks Id System
/dev/sda1 1 262 2104483+ 82 Linux swap / Solaris
/dev/sda2 263 13316 104856255 83 Linux
/dev/sda3 * 13317 14621 10482412+ 83 Linux
I have a used PC that came pre-installed with suse 11.2.Unfortunately, I do not have the install disk to use in case of whatever.I already know that when configuring a dual boot with Windows and Linux, it is recommended to install Windows first.I do not have that luxury now as 11.2 is installed and GRUB is the boot loader.Question is, if I boot the Windows 98 install disk on boot, how to not mess up GRUB and still add Windows 98 to GRUB menu?
One hard drive only here. 98gb free.It seems that W98 install will overwrite GRUB in this situation - causing problems. Maybe not, I don't really know for sure.I just need to install windows 98 on the same hard drive and if possible, have suse and w98 visible on boot in GRUB.
I have installed 11.2 next to my 11.1 version I have a few big problems with 11.2 and I like to completely remove it. there are 2 grub's active now. I want to remove the 11.2 grub and make the 11.1 grub master again, but I do not know where to change this, the MBR points to the 11.2 grub and changing menu.lst probably does not have any effect.
View 6 Replies View Relatedso the safest way to go about this is to assume I know nothing. I mean, I have a rough Idea of what a kernel is, no idea what a shell is, etc. I do consider myself computer savvy, but know NOTHING about linux and thats why I'm Diving in, hopefully not too much, this is just to give you an idea of what we're working with here.
After several install attempts I kept getting a blank screen. Whether it be black,white, or the default gnome desktop (without any icons, and simple things like ctrl+alt+backspace just doesn't work, or anything else for that matter) I was ending up with a blank screen. Driver for moniter....maybe....but I did succesfully install it once, and it worked like a charm...shutdown properly, and the next day after work...Boom, same thing after startup.today I started from scratch and re-installed....samething, until I hit the power button, went from the dvd(iso) and did a fail safe, now my resolution is much better than it was the first time..Actual questions.....what did I do to fix it when failsafe never worked before?
Is there a way to save these settings, so I don't run into the problem again, because I don't even want to turn of my computer at this point?If i'm trying to dive in and learn the command line actions, is there any substancial difference between gnome terminal or hitting "c" to bring up the command line?
What is the difference between MBR and GRUB? Are they the same? Are they different? Do I need both of them?
View 3 Replies View RelatedI have been given a new old computer, Asus K8N-E with a 2GHz AMD Athlon 64.OpenBSD and Debian works like a charm. But with Slackware 13.1, LILO won't be installed properly. There are two disks: a 10GB ATA-drive with the system and a 250GB SATA-drive as a data repository.
Apparently the computer insists that the SATA is the first disk. Subsequently the bootable partition is not on the first disk and disables LILO to be installed. This is when I try to install LILO to a partition. When it is installed to MBR, it says something about overlapping and can't boot.