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.
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?
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?
I need to get LILO to boot a ramdisk in which the root file system is on /dev/ramdisk. I have tried many iterations of lilo.conf files. The following is one that I would think would work because it worked under 2.4 kernels:
I installed Ubuntu 10.04 on a spare partition, but didn't want to install Grub since I'm sure Ubuntu isn't going to be around for more than a little test drive. The problem I have is that lilo doesn't like the initrd.img file, complaining that it's too large. I'm assuming this file should be in the initrd line for the lilo entry. If someone is booting Ubuntu 10.04 with lilo it would be nice to see the lilo entry or any tips.
I'm running Ubuntu 10.10 with Lilo as my boot loader instead of Grub. I want to boot, temporarily, to a command line prompt instead of X-windows. How do I do this? Is there a combination of keys to press when the Lilo screen appears?
I am installing slackware 13 on a machine that already has slackware 64- current. I'm doing this to try LFS which needs a 32 bit host (I know about CFLS, but I'm trying to keep it simple). My current installation is on sda with / being on sda1. My new 32 bit installation is on sdb with / being on sdb2.
I didn't install LILO as I figured it would be easy enough to just edit the current lilo.conf and run lilo after rebooting from the installation and then rebooting again into the new 32 bit install. What keeps happening is that the system boots seemingly fine, but after some wierdness I realized that it is booting a kernel from the 64 bit install on sda1. I'm assuming this is a simple screw up in my lilo.conf but I'm not sure exactly how to fix it.
lilo.conf: Code: # LILO configuration file # generated by 'liloconfig' # # Start LILO global section # Append any additional kernel parameters: append=" vt.default_utf8=0 quiet"
I'm fairly new to Linux so I'm going to need a step-by-step guide to get me out of this rut. The install of Linux was fine but when I booted up I got this error. VFS: Cannot open root device "302" or unknown-block (3,2) append a correct "root=" boot option;here are the available partitions;
0800 78150744 sda driver:sd 0801 47428608 sda1 <-- this is my Windows partition 0802 30719552 sda2 <-- this is my Linux partition 0b00 1048575 sr0 driver:sr 0b01 1048575 sr1 driver:sr
Kernel panic - not syncing:VFS:Unable to mount root fs on unknown-block (3,2) I guessed from reading this error Lilo isn't pointing to the right partition to boot from? How will I fix this? I read another thread about boot problems on these forums and a guy said to do this:
#mkdir /slacktemp #mount /dev/device /slacktemp #chroot /slacktemp #cd /slacktemp/etc <-- for me it told me that doesn't exist #vi lilo.conf <-- couldn't do nothing and was frozen #lilo -v -t -b /dev/device #lilo -v -b /dev/device
The above solution did not work for me. Can anyone shed a light on a Linux rookie?
I am in a situation to boot fedora 15 live cd in to command line mode, not graphical mode, for some testing purpose. how to change argument during booting mode
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 am trying to install Fedora 14 with the LILO bootloader. The live installation disc does not let you select a bootloader during installation. how to install with GRUB2, that will work as well
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?
How can I use Lilo with Fedora with a true way ?I tried some disros with a Pentium 4 machine and SATA harddrive which not accepted GRUB some times, but lilo is working fine.
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 ?
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 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!
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
Triple 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.
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.
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 .....
I 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?
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 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
I 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 ?
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).
