I have slackware one one partition with lilo. Today I've installed Windows 7 on another partition and now I have to fix lilo. How can I do that? Can I reinstall it from the slackdvd ?
View 1 RepliesJust 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 successfully install backtrack 3 but i cant see windows option anywhere in my lilo boot loader
View 10 Replies View RelatedI installed SW 13.1. Install and config completed without issue. When I attempt to boot, POST completes, and bootup stalls. Only a blinking cursor is visible. Any pointers on how to resolve this/achieve a succesfull bootup?
View 4 Replies View Relatedi have slackware 12.0 and kernel 2.6.21.5.LILO was the natural choice off of the CD set to load Linux.now, i want to load windows into a non-formatted partition on the HDD.i understand though, that windows will overwrite the MBR and put NT stuff in there thus wipeing out my access to Linux .i can't find the thread that deals with where to move LILO so that the Windows installation routine does NOT wipe out the MBR and LILO along with it,
View 2 Replies View RelatedI 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 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'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'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 ...
My computer has Debian 5.0.4 (with kernel linux-2.6.26-2-AMD) installed. Processor is AMD64 athlon dual-core CPU. I am trying to install RTLinux-3.2-wr. Below is what I did:
1) download a clean kernel : linux-2.6.26.8.tar.gz and patch : patch-2.6.26.8-rt16.gz
2) configure and build the kernel with the patch applied
3) reboot with the new kernel
"uname -r" shows "2.6.26.8-rt16"
4) download and unpack RTLinux-3.2-wr.tar.bz2 into /usr/src/rtlinux-3.2-wr, the execute the following commands:
cd /usr/src/rtlinux-3.2-wr
make menuconfig
I get an error message "Makefile: 66: schedulers/x86/Makefile: No such file or directory", which is caused by line 66 "include schedulers/$(ARCH)/Makefile" in file /usr/src/rtlinux-3.2-wr/Makefile. When I go to directory "/usr/src/rtlinux-3.2-wr/schedulers", I find that there is no "x86" subfolder. The existing four subfolders are "alpha", "i386", "ppc" and "mips" respectively. What should I do to "make menuconfig" successfully?
I've got a linux driver for by Broadcom 802.11 wireless card which I downloaded from the broadcom website. It's in a tar.gz format and I have NO idea what to do with that. My ubuntu machine has no internet access at all so none of the solutions I'v been able to find that deal with these broadcom drivers will work for me (because they all seem to require internet).
So, maybe someone could point me to a walkthrough for intalling a driver that is in tar.gz?
I tried this command:
And got these lines:
Why the package not found.
I 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 attempted to install slackware 13 on my laptop and was moderately successful. However in the process of attempting to configure it I appear to have messed something up. After reading about the problems I'm having I decided it would probably be easier to remove the current installation and start over.
I am now trying to install fedora from the dvd, but for some reason the computer will not boot the dvd. I have set the bios to boot from the drive first, and have tried burning the dvd twice, but every time the dvd spins up and shortly thereafter the computer loads lilo. Have I simply burned the dvd wrong twice? I used disk manager on mac os x and the disc reads just fine on the mac that burned it, but still no luck booting.
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.
I wanted to put password in lilo.conf file. I added this line but doesn't seem to work out Code: password=vickey. I also did Code: lilo -v Is there any thing missing
View 8 Replies View RelatedTriple booting. Windows 7 Evaluation, Xubuntu 9.10 and I just installed Absolute. Xubuntu uses Grub 2. I was going to do three things. Install Lilo to Absolutes /boot, go inot Xubuntu and reinstall Grub 2 to /boot and then just install GAG boot loader to load all three. Instead I was distracted and installed Lilo to the MBR by accident, which overwrote GRUB 2.
I can boot into Absolute fine and Windows 7 fine but the problem I am having is with Grub 2. The Xubuntu Live CD is not working for some reason, I mean it won't boot. I downloaded it twice and burnt it to disc both times. I am not sure why at this point.
So how do I add Xubuntu 9.10 to Lilo. If I try and do it manually or any other way it starts to boot Absolute instead and then freezes, even though I am pointing it to my Xubuntu partition. I am leaving something out. It has been a long time since I used Lilo and even then I was just as clueless.
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]....
since 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 a SATA boot disk with LILO installed. This disk is kinda like a recovery disk in that its supposed to boot up on any x86 PC. I'm however having trouble getting it to boot on a HP Probook laptop. I get the LILO 99 99 99 ... problem upon bootup.
I've already specified the linear option in my lilo.conf, which according to the LILO error codes might fix the problem but didn't.
Quote:
0x99: Invalid Second Stage
Mismatch between drive and BIOS geometry, or a bad map file. Some evidence that LINEAR needs to be set on the disk (see LiloNotes)
I've tried specifying the lba32 option instead, but get the same problem.
I've tried the solutions at this LILO Error Codes wiki, i.e. lilo -g and lilo -M /dev/sda
Neither solution worked.
Does anyone know how to get this working? Or recommend another BIOS independent boot loader? I was using nuni in the past for my IDE version, but nuni doesn't support SATA drives.
fyi I'm booting up the disk and running LILO on another laptop that boots it up, before plugging it into the Probook to test.
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]....
A few years ago I built a small Slackware system and, for storage, I used using a 2Gb Compact Flash card plugged into the primary IDE interface. Initially, I made a bootable CD rom, booted the new system from that, copied the file system to the CF card and then ran LILO to install a boot sector on the CF 'disk' /dev/hda. That all worked well enough.
The only trouble is that the CF card, being an early one, is rather slow and so I've just bought an Innodisk 2Gb Disk-on-Module which ought to be much faster. I have plugged that into the secondary IDE interface, I've run cfdisk to make a partition, formatted it using mkreiserfs and copied all of the contents of the CF card on /dev/hda to the new device on /dev/hdc. So far, so good. But...Now I need to run LILO from the existing CF card in /dev/hda to put a boot sector on the new /dev/hdc. Then I want to move the new device from /dev/hdc and put it in /dev/hda once it's bootable.
I'm stuck to know how to configure LILO to install a new boot sector on /dev/hdc. I don't appear to be able to make LILO understand what I'm trying to do. If I change the line 'boot = /dev/hda' in lilo.conf to 'boot = /dev/hdc', LILO aborts with an error message.
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 .....
Im 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 edited /etc/lilo.conf file and changed timeout setting to 30 (in tenth of seconds so 3 seconds) but when I reboot old value - 2 minutes is displayed.Is anything else I need to change?
View 1 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 have one machine with two disks that I'd like to install Slackware on. I'd like to have the root folder and installed folders on hdb, and just have have hda as a disk I can use for storage (without any home directories, etc.). My problem is, I don't know how to make this boot, as I think LILO is installed on the primary drive, but the boot folder is located on hdb. I tried doing this before and was having problems booting, so I was just going to go through the whole process again, but don't really know the correct procedures.
View 2 Replies View RelatedI'm receiving the following error message when running LILO under SystemRescueCD after installing Slackware 12.2 (the slackware setup hung when installing LILO so I am trying to install manually - I have re-run setup, including formatting all drives again):FATAL: Trying to map files from unnamed device 0x0010 (NFS/Raid mirror down?)Let me know if any more information is necessary and thank you in advance for any help you can provide.
View 7 Replies View RelatedI'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:
For the past 4 days Ive been trying to install ubuntu 10.10 64bit with no success. I am a total newbee when it comes to linux so I will be needing your kind help with it.At first I installed ubuntu to one of my portable drives with no problems, but now I want to install it to my hard drive and have a dual boot between windows XP and Ubuntu.
When I arrive to the manual partitioning part is where I get lost. I have totally destroyed my windows installation 5 times already ( thank god for norton ghost for restoring my windows installation. )
I have read several articles and blog posts regarding a dual boot system with windows and Ubuntu but none of them cover my specific situation so I keep getting lost and screwing things up.
[Code]...