Slackware's lilo runs from sdb1. I installed ubuntu studio on sda3.
I can't boot it from lilo.
Code:
boot = /dev/sda
image = /boot/vmlinuz
root = /dev/sdb1
abel = Slack64-cu-sdb1
read-only
[Code]....
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 RelatedIm planning on installing a beta of my favorite distro to /dev/hdb from a mounted iso on an /dev/hda partition.Im not exactly a newbie, but i cant say i have ever done this before. Anyone aware of any issues i might encounter? Is lilo ok booting from one drive to another? Is it ok to just install lilo on the mbr of /dev/hda to boot a distro on /dev/hdb?
View 4 Replies View RelatedI have to computers: 'A' (linux) and 'B' (windos). On 'A' I have a linux system that i copy over to a movable disk on which i install the lilo bootloader. Now when I move the disk to 'B' I am able to boot into the new linux system, however I would like to have an item in the lilo boot menu from which I can boot the windows system on 'B' also. And now the tricky part: I would like to create this item when the disk is still on 'A' where windows is not present.
I have tried using "disk = /dev/hda1 inaccessible" without any luck.Is it possible to "cheat" lilo into adding an item pointing to a disk that is not present on your system ?
I cannot boot into the Windows 7 partition, which I guess is /dev/sda1. I have Slackware installed on /dev/sda2 which boots fine, my /etc/lilo.conf looks like
Code:
/etc/# Start LILO global section compact
[code]....
Old Setup: I HAD Ubuntu 10.04 (Fresh Install) and Vista. These were booted using GRUB as installed by Ubuntu.
New Setup: I have added Slackware. This has replaced Grub with LILO.
Problem: I have setup liloconfig so recognize each OS. Vista works great, so does Slackware. However, when I select Ubuntu: "Ubuntu is in Low Graphics Mode". Followed by a system crash.
Question: Ideally id like to simply stick with LILO. Is there a simple way to achieve this?
Note: some, on other sites, have suggested installing GRUB from Ubuntu LIVECD, however I am concerned, since I have no boot disk for my Vista that I might make it impossible to boot Vista if a GRUB problem is encountered. So ideally, id like to simply figure out how to work with LILO since it already works with Slackware, and Vista.
Here's the set up.
1. Got an EXISTING LILO... VL 5.8 (/dev/hdc3)
2. Installed VL6.0 and installed its own lilo on Boot sector (/dev/hdc13)
3. Everytime I choose VL6.0 in my existing LILO (/dev/hdc3) it still goes to VL6.0's LILO. The question is, how can I remove the VL6.0 so if i choose this on my existing lILO. It will just boot straight.
VL6.0 LILO:
root:# cat /etc/lilo.conf
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hdc13
#default = linux
#compact
#prompt
#timeout = 0 .....
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).
Something caused my Fedora 11 system to reboot this evening, only it keeps trying to boot from a CD/DVD. I get to a prompt that says "Boot from CD/DVD" and then it appears just to wait. I can insert my Fedora 11 installation disk and boot from it in rescue mode, and then I can see my entire file system, so I don't think the hard drive has failed. The system just doesn't seem to want to boot from the HD any more. I can get to a command line using the Fedora rescue mode, but I don't know what to do once I'm there.
one additional note. Around a month and a half ago I deleted some files by mistake and wanted to try to recover them. I tried a bunch of approaches that I came across (none worked), and I do remember that one of them had instructions to unmount a portion of the filesystem to protect it from being overwritten before I could recover the files.
Unfortunately, at this point I have no real memory of exactly what I did, but the system has been working fine since then. I would have thought that I had rebooted since then, but it's possible that this is the first time I've rebooted. Could I have unmounted some part of the file system such that it would still by unmounted even when rebooting? How can I check this from the command line I get in rescue mode? (My file system gets mounted under /mnt/sysimage/)
I have been given a new system, but want to try moving my old server's system / boot drive directly to it, rather than re-install.
All of the hardware is different, what am I letting myself in for? What should I prepare for?
Existing system OS is Ubuntu 10.04 Server, non-specific install from live CD.
I've done this before on Win XP and it was a nightmare, but I suppose that's not really designed for that sort of thing. I'm hoping that linux will be easier.
I've just installed the new Fedora 11 (just released) through a Live CD having 3 partitions created:
"/boot" - ext3,
"/" - lvm (part 1)
swap - lvm (part 2)
now, I want to add my new Fedora system entry to my "central" lilo.conf, resident on another linux distribution. So, i've done
[Code]...
my lilo fedora entry boots fine but... at the middle of "after boot" loading the system hangs and stops the usual driver detection, etc (normally, it hangs on the CDROM detection or USB 2.0 camera detection).
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:
i successfully install backtrack 3 but i cant see windows option anywhere in my lilo boot loader
View 10 Replies View RelatedI've for quite a while been going forward with making my own linux system with a purpose of being USB bootable. A lot of it has been taken from LFS and molded to my needs. The purpose of this is to, most of all, learn. My aim is to have a small linux system, bootable on most systems and able to run burnintest in textmode. This will be run of a vfat formatted pen drive with syslinux. The rootfs is run from a ext2 image file. My current image is bootable and is able to run burnintest, I do however still have some polishing to do.
I began this project by using uClibc and my image would be tiny enough to be run from a single initrd (20mb ~). What I didn't consider is the fact that burnintest is pre compiled using glibc, so had to re-do everything with a different c library.. After doing this I realized i no longer would be able to boot simply from ram as loading ~80mb to ram takes quite a lot of time during boot. I'd really like to keep the rootfs in an image file for easier management and I so far haven't found a way to mount this roofs image.
My Toshiba Satellite 5205-S705 laptop with Win XP Home sp3 has a non-working cd drive, is riddled with viruses, and isn't capable of booting to a USB drive. (please no comments about paperweights etc., it's all I have!) I want to install a Linux dual-boot version that is heavy on antivirus scanning support. Since I can't boot to an .iso disk, is there any other way to do this? I can transfer files to it via USB thumbdrive or download via Internet.
View 9 Replies View RelatedI have one distro installed, LILO as the boot loader, and i wonder if it's possible to duplicate the lilo entries with an option which executes some script or command during, or after the boot.Actually, i installed a Slackware + autolaunching virtual machine, but i have two VM, so i need to autolaunch one of them. May i choose it from the very beginning ?
View 9 Replies View RelatedI have minor problem with upgrading a hard drive. I am running an old pentium lll with two hard drives. On the first hard drive I have two partitions of around 90GB each. On the first partition is installed winXP and on the second partition I have Suse 10.3, both booted by grub and living happily side by side. My second hard drive (which is formatted for windows is only 4GB.
My problem arises when I try to replace the 4GB with a 80Gb hard drive. When I disconnect the 4GB drive the system fails to boot up and complains with error 21.
I just joined the forum today. I'm not a linux beginner per se (about 4 years experience, now running Ubuntu Lucid on my laptop and windoze-free) and I built the desktop PC I'm typing this on six years ago. However, this is my first HTPC build and my first KnoppMyth install, and I've probably done something foolish.
This was an attempt at a fresh KnoppMyth 5.5 install on a virgin system. Hardware details:
MB: GIGABYTE|GA-880GMA-UD2H R
CPU: AMD|PH II X4 925 AM3 RT
RAM: 2Gx2|GSKILL F3-10666CL7D-4GBRH
HD: 1T|WD 7K 64M SATAIII WD1002FAEX - OEM
CD: BLU-RAY BURNER LG | WH10LS30 OEM - OEM
[Code]..
Basically, I just wish I had never bothered with KM5.5 and I want a do-over to go back to the beginning and put the LinHES 6.03 CD in and just do the installation. Since I can't do this, I'd like to at least be able to wipe everything I did and start fresh. Recall that I couldn't boot from CDROM even before I made the daft remove of LILO. The only time I successfully booted from CD was the very first time I turned on the machine to install KM5.5
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?
Is there a way to run the lilo command from the ubuntu 10.10 boot cd? It doesn't get the directories right, as it has / mounted as the ramdisk memory file system, and / can't be demounted since it's busy. I can install lilo in the ram after booting from the cd with sudo apt-get install lilo. Mounting / to my sdb1 partition (where Ubuntu is installed) does not get the proper "maps" for the lilo command, since the cd ramdisk / takes priority. I prefer not to use grub, as I wish to use windows vista's bcd(edit) as the main boot selector and it won't boot grub from bcd to a partition; at least I couldn't get it to work in 11.04. I got lilo to work from the vista's bcd menu in 11.04, but had many glitches. Windows allows this type of proceedure from its recovery cds.
View 4 Replies View Relatedbefore i start messing with anything, i figured i better ask before i get myself into trouble. ive been searching around and havent seemed to have found anyone with a setup similar to what i am trying to do. here's what i'm doing:
i have two identical 20gb drives, hda and hdb. hda1 is root. i am setting up either rsync, dd, or cpio to copy hda1 to hdb1 possibly once a month with a cron job. I just want to have a monthly backup of root in case hda1 ever fails. no, i do not want to use fakeraid or mdadm to set up a raid1 array, just want a monthly backup. should hda fail, and i need to set hdb as first boot device in bios, and boot off of that, i need to have a working lilo on that drive as well. if i copy the boot sector with lilo off of hda onto hdb, the boot= parameter in lilo would still be pointing to hda, and not hdb.
so is there a way to set two multiple boot drives in lilo? if not, how would i go about installing a separate lilo on hdb with its own conf? i was thinking something along the lines of modifying lilo.conf on hdb1 to point boot=/dev/hdb and root=/dev/hdb1 and chroot to hdb and run lilo -v? and if i do the above, and i do boot off of hdb1, will everything work as it should? what about needing to modify fstab for / being on hdb1 now?
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'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've been using lilo to dual boot linux/windows and I'm trying to add another linux distribution/partition. So far my lilo config looks like this :
other = /dev/sda
label = Windows
table = /dev/sda1
image = /boot/vmlinuz
root = /dev/sda4
label = Linux
read-only
I have installed another linux partition in /dev/sda2 which suggested to install grub with the following configuration :root (hd0,1) kernel /boot/vmlinuz26 root=/dev/sda2 ro initrd /boot/kernel26.img. Since I wanted to be sure that at I would be able to boot in at least one of my linux I didn't intall grub. I'd like to know how I should change my lilo config to be able to boot in my second linux partition.
[Code]...
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]....
I've got a linux system on a floppy that boots into a console via which I can mount a Ubuntu 8.04 cdrom (live cd); however after this I can't seem to figure out howto get the ubuntu system to start, any ideas?By the way the system cannot boot from a cd-drive nor can it boot via a usb device..
View 2 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).