I have a WD 80GB ATAPI hard disk for my operatings systems.
The partition table is :
First i installed Windows and then Slackware.
The problem is that in MBR , looks that lilo never installed and when my pc starts, the lilo menu never load it . Boots directly to windows.
What i should do, in order to have the lilo menu in startup?
I have a PC with 2 Hard drives one of which has Windows XP Pro installed. I installed Red Hat Linux 7.2 on the other drive choosing LILO as the boot loader. When I reboot LILO only displays Red Hat 7.2 When I boot Red Hat and go into KDE boot settings I can see that hda has Windows NT. hdb has Red Hat 7.2. I then tried to make the Windows NT partition the default entry. When I try to confirm this an error displays warning me of danger if I proceed. Is there any way to make LILO recognize Windows (preferably without having to reinstall Red Hat), perhaps by installing another bootloader application!
View 2 Replies View Relatedi successfully install backtrack 3 but i cant see windows option anywhere in my lilo boot loader
View 10 Replies View RelatedI have two hard drives, one (hard drive C) is 250GB and is the first hard disk. The second (hard drive Z) is 1000 GB and is the second hard disk in order. There used to be windows XP on C and Windows 7 on Z.
Because I installed 7 to Z from XP which is on C, it put the Windows Boot Loader on hard disk C. I didn't know this until now.
When I installed Fedora, I gave it all of C to install on. That messed up something because the Windows Boot Loader was on that drive, so grub didn't list it in the OS's to load. I had to add it manually, and got it working correctly so it had an entry for the partition that Windows 7 was on. This didn't work however, because Windows 7 on drive Z didn't have it's NTLDR on that drive, so now I have a 7 installation without an NTLDR on Z and a Fedora install on C. I am sure grub is working properly because when I change the load order of the hard drives to load Z first, it gives the same error:
NTLDR is missing
Press Ctrl + Alt + Delete to restart
or something along those lines.
Is there a way to get Z to have an NTLDR again and be able too boot Windows 7? I really hope I didn't mess up my entire 7 installation because of this.
I'm familiar with editing Grub's "menu.lst" file to add additional OS's to the boot list. Does Slackwares Lilo have a similar config file ? I need to add a second physical drive with Windows 7 on it to the boot options in Lilo. If it's not a config file, how do I add a second os to it ? Slack and Windows are both already installed on two different physical drives so I won't be installing, I just need to add the Windows drive to Lilo.
View 5 Replies View RelatedI 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 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 installed ubuntu using wubi and then I tried installing grub 2 but it failed. I need a way to reinstall the mbr sp it will load the windows 7 loader from the first partition.
View 1 Replies View RelatedWhen I installed Slackware, I did not install LILO. Instead, in my LMDE, I ran: grub-install --recheck /dev/sda, then I ran: update-grub, then: reboot. This worked ok, although I have 4 grub enteries for Slackware - who knows why, but there are 4.I decided to install grub from the Slackware DVD. I copied the extras/source/grub folder to home and as su, ran pkgtool and selected grub from /tmp.From the root directory, as su, I did: rub-install --recheck /dev/sda but when I tried: update-grub (or grub-update), I got: command not found. I rebooted... (probably should not have done that)Grub menu sort of appeared with not boot options.I rebooted into Slackware from the Slackware DVD and now I am writing this from my Slackware installation.
View 5 Replies View RelatedI'm trying to install Puppy 525 on my Slackware 13.37 PC as a dual-boot using LILO. Puppy is living, all on it's own, in sda6, a 6 GiB partition. It got there by using the Puppy Universal Installer and selecting a 'Full' install, not a 'Frugal' install. I cannot find 'LILO' type instructions, only 'GRUB' type instructions.
Has anyone succeeded in doing a hard drive install of Puppy with the LILO boot loader?
Edit: I'll probably regret it, but I used Puppy's GRUB installer.
I just did a fresh install of slack 13.1 on a separate drive to the one I was previously using. I've been having trouble getting lilo to work, so that I can choose between either drive. Lilo is currently installed to /dev/sda, with the old system on /dev/sda1 and the new installation on /dev/sdb1. I keep getting errors like these:
Code: Fatal: Trying to map files from unnamed device 0x0011 (NFS/RAID mirror down ?)
I managed to install lilo from the old system by copying the kernel image from the new system into the /boot/ directory and running lilo. I am now on the new system and trying the same thing in reverse but it isn't working. I have searched around a bit and there's a lot of talk of chroot-ing into the other partition to run lilo. I don't understand why the process isn't working both ways though. I can't run lilo on my new installation even with the two kernel images in the local /boot/ folder. Is this something to do with btrfs or am I missing something to do with lilo? This is my lilo.conf file. I am trying to run lilo using this file from my new installation on /dev/sdb1 and getting the error given above.
[Code]...
i installed slackware 13.1, previously i had slackware 13, i made the following partitions:
[Code]...
everything went fine until i rebooted slackware after installation. lilo didnt boot at all, just a black screen. i booted with the DVD, and checked the lilo config file. the contents on lilo looks fine, just like any other lilo on google. for example i have this: boot = /dev/sda
i installed lilo on the MBR., i then changed this to boot = /dev/sda1 , on root and nothing same thing lilo always complains at the end: Partition entry not found , but how come , /etc/fstab shows all partitions are mounted ,( i am doing this in KDE environment). i reinstalled again , same thing. I also get a warning: video doesnt not support VESA mode, i changed to vga = normal again it complains that video doesnt support vesa even when i set it to normal, (note that i am running lilo after i made those changes, even rebooting , and same thing happens.
when i installed lilo, it let me choose video modes for the boot screen because lilo showed that my video card supports vesa mode, but then it doesnt boot at all. did slackware 13.1 changed so much that my laptop is no longer supported?? everything was fine with slackware 13 or is it because slackware needs a separate /boot partition, if so how come i just installed slackware 13 with just / and swap?
I 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?
I have a question that is really probably a lilo question, but here goes. Can you use lilo to boot different linuxes on separate hard drives. Like this.
/dev/hda1 - Slackware 13 with lilo in MBR
/dev/hdb1 - Puppy linux
Here is my lilo image area:
[Code]...
Boots Slackware ok, but when booting puppy it screws up and seems to be printing the boot messages for the Slackware kernel on hda1. Now, how do I tell lilo to find the puppy kernel?
I have a laptop that I have installed Slack-current on, I am currently using the usb image to boot from. Windows7 is installed on sda2 and sda2 has been marked with the bootable flag, I would like to use lilo to boot the laptop do i install lilo to sda or to sda2?Will win7 still be able to boot using lilo as the boot loader ?
Another issue i noted during install is that the kernel panicked using the dvd to install with an error stating it could not read from the booting device, I eventually used the usb-pxe install to load the system however since 13.1 i have not been able to load a system using the dvd.
I currently have a Slackware system an am using Lilo. I just installed Fedora 13 on a different root partition to play around with, I chose not to install Grub. How can I add an entry to Lilo to boot Fedora? Almost everything I am reading online says to use Grub and not Lilo, is there a reason for this?
View 12 Replies View RelatedI have Windows on sda1 and just installed Slackware on sda2. There also is a hda data drive, which usually appears first on drive lists. During installation, LILO gave an error (I tried installing both to MBR and root, both times the error was about something like "root: (N6").
Then I did the following
-boot with installation cd
-hugesmp.s root=/dev/sda2 rdinit= ro
-login
[code]....
My problems with Ubuntu seem to always be caused by a problem with Windows.
My laptop has two hdd's with Windows XP on the first and Linux Mint 10 on the second.
I had to reinstall XP on the first and now mint won't load at all.
I ran the boot info script and her it is:
Code:
I installed Sabayon Linux and it's bootloader, but I did not like it. How do I remove it and its bootloader so only Ubuntus remains?
View 1 Replies View RelatedAfter I complete a big project I'm working on I'm going to be wiping and re-doing my desktop machine, probably in the next day or three. I'm going to be setting up a dual-boot; my first in about three years. I'll be using separate hard disks for this, and installing Slackware second on the bigger of the two drives. When I've done this in the past I've used Grub; Is there anything I need to know or pitfalls I need to avoid doing it with Lilo?
View 5 Replies View RelatedI have just install both fedora 12 and slackware 13 on my laptop I did not install lilo because fedora uses grub I am able to use slackware by using the the DVD and booting from the command prompt I have attached my grub .conf file also when i boot from cd the command is as follows
[Code]...
I am trying to dual-boot windows xp and ubuntu 8.04LTS from two separate hard drives, on a compaq d510 evo SFF. With research, the best way to do that seemed to be to upgrade to Grub 2 and all would be well...not so much. I installed each OS with the other hard drive removed, fyi. I believe that this tells me that I SHOULD be able to boot off either drive, if I could get Grub 2 to recognize...
Code:
steve@Stewie:~$ sudo fdisk -l
Disk /dev/sda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xb788b788 .....
Code:
steve@Stewie:~$ sudo update-grub
Updating /boot/grub/grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.24-27-generic
Found initrd image: /boot/initrd.img-2.6.24-27-generic
Found linux image: /boot/vmlinuz-2.6.24-26-generic
Found initrd image: /boot/initrd.img-2.6.24-26-generic
Found memtest86+ image: /boot/memtest86+.bin
done
I have also tried adding the proper code to the 40 custom file, and while I could at least get it to acknowledge my changes, I couldn't seem to find the magic code to get it right....
The other thing I tried was adding GRUB_DISABLE_OS_PROBER=false
to /etc/default/grub
and last but not least, here is my results.txt from the boot info script. I also tried uninstalling/reinstalling grub 2, perhaps I created issues there?
Code:
Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary:
=> No known boot loader is installed in the MBR of /dev/sda
=> Windows is installed in the MBR of /dev/sdb
Just installed Slackware 13.37 and am trying to get dual boot to work properly. I have edited /etc/lilo.conf to point the Windows section to what I believe should be the correct partition (/dev/sda2) Here is the relevant section
Code:
# LILO configuration file
# Windows bootable partition config begins
other = /dev/sda2
[code]....
I have mounted /dev/sda2 to /ntfs-c as suggested during install and when I browse through there I see the files from my windows setup so it is in fact the correct partition. When I load Windows on boot, however, it is pointing to the recovery partition (/dev/sda1).
i want to install opensuse on my new lap top i partition my hard (600gb) with 5 parts:
c: 97 gb
d: 150 gb
e: 150 gb
f: 100 gb
g: 50 gb
and 38 gb unlocated part
in opensuse instalation , the yast makes a 2gb for swap 14gb = root , 21 gb = home, but in Instalation Overview under Booting has a red error: the Boot loader Installed On a Partition that does not Lie Entirely Blew 128 GB .The system maight Not Boot;
I'm trying to dual boot Win7 and Ubuntu WITHOUT using Grub. This is to support Bitlocker encryption.
I followed this guide, and now when I select Ubuntu I get a Grub> prompt and no ubuntu.
I feel like I'm halfway there, I just need to get Grub to load correctly or something.
One thing I notice and hope someone here can steer me in the right direction. When I start up my computer I have the list of options to choose from, if I choose to boot into Win 7 I am the presented again with another boot menu from windows. I would like to remove the Windows boot loader.
View 4 Replies View RelatedI'm using slackware 13 and now i want to add slackware 13 to grub .How do i have to do it ? Slackware is great to learn because i've a lot of linux using slackware than using any other distro. But some programs are dependant on other which i was not able to install, they call it dependencies. Even though compiling from source is great but runnning the program is a problem as the program terminates may be because of some dependency not installed.The same goes with sbopkg and others ..As of now i'm thinking of installing Ubuntu along with Slackware13 as this system is used by everybody in the family. How to add slackware to Ubuntu's grub.......
View 3 Replies View RelatedI have 2 HDDs:
HDD 1 (sda) with Windows XP installed on sda1 and four more partions.
HDD 2 (sdb) with three NTFS-Partitions (sdb1, 5 and 6) and Ubuntu 10.04 (sdb7) + Swap-Partition (sdb8).
I would like to boot Ubuntu using the Windows XP boot loader, i.e., having an entry there to choose Ubuntu and start my installation of Ubuntu 10.04. I have installed Ubuntu 10.04 on sdb7 and told the installer to install the grub2 boot loader to /dev/sdb (should it have been /dev/sdb7?). When using the boot selection option of my bios and choosing the second HDD Ubuntu starts without problems.
I used dd if=/dev/sdb of=bootsect.lnx bs=512 count=1 to copy the mbr of my second HDD and copied the file bootsect.lnx to my c: drive. Then added C:ootsect.lnk = "Ubuntu Linux" to my Windows boot.ini. When rebooting my computer I get the option "Ubuntu Linux" in the XP boot loader. Choosing it I come to a black screen with a blinking white cursor. All I want to do is not use Grub 2 as my primary boot loader but instead leave my WinXP installation untouched and start Ubuntu from within WinXP boot loader. This has been working just fine with my old Ubuntu installation.
I want to update syslinux to version 4.03 on my system, so I took a look at the SlackBuild.
I noticed that the SlackBuild rebuilds everything including the actual boot loader with 'make -j4', but there's a note in the docs directory (distrib.txt) that asks not to do that:
Quote:
For creators of Linux distributions:
Syslinux is a notoriously hard program to debug, since it runs outside of any operating system, and has a tendency to expose BIOS and hardware bugs on various systems. Therefore, I would appreciate if you would resist the temptation of recompiling the Syslinux bootloader itself (ldlinux.asm) if at all possible. If you do that, I will have to refer any bug reports I receive back to the respective distributor.
However, I have no such concerns about recompiling the installer programs, and in fact, with both libc 5 and libc 6 in common use in the Linux world today I understand if you wish to relink the Linux-based installer against your system version of libc. Therefore a special makefile targets "make installer" has been included with the Syslinux distribution, starting with version 1.42.
To rebuild the installer programs *only*, starting from a freshly untarred distribution copy of Syslinux, do:
make clean
make installer
If you want to remove all intermediate files, including the ones obtained from assembling ldlinux.asm and which are included in the distribution, do "make spotless".
I thought I'd report this in case it was unnoticed by Pat and the team. If not I apologize for wasting your time
Can I separately install a third party boot loader which can boot both Windows and Linux (Ubuntu) . I want to use a boot loader other than the boot loaders which come with these operating systems. I am trying this out of curiosity.
View 4 Replies View Related