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 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'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 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 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 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 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:
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 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'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 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'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've a multiboot machine and I recently installed Slackware64-13.1 on sda33. I added menu entry in SUSE boot loader and configured menu list as per [URL].. it returns GrUB error 15. Here is my menu list entry for Slackware -
Code:
###Don't change this comment - YaST2 identifier: Original name: other###
title Slackware64-13.1
root (hd0,32)
kernel /boot/vmlinuz root=/dev/sda33 ro hdd=scsi
savedefault
[Code]...
I'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 finally got everything installed and then slackware setup prompted me to reboot. then i did and it just took me back to windowsxpx64. so then i tried booting off my usb, and it worked, however when i login as root, i just get the bash commandline and not interface or programs or anything. i cannot login as any other user and the setup did not prompt me to make another user account. so how would i activate lilo or make it so i can boot with it to slackware? i rather use grub but for now i would just like to get slackware working right.
View 2 Replies View RelatedLILO 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
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 look after some small office where computers run ubuntu. Sometimes they phone me for help. For that reason, I decided to install ubuntu alongside with my slack.I seem to have problems with lilo configuration. Ubuntu is installed on software raid :
/boot = md0 (raid 1 of sda1+sdb1)
/ = md1 (raid 0 of sda2+sdb2)
That's lilo.conf:
Code:
append=" vt.default_uft8=0"
boot = /dev/sda
bitmap = /boot/slack.bmp
[code]....
Code:
Fatal: open /vmlinuz-2.6.31-9-rt: No such file or directory
I can mount md0 without problems and the file name seems to be correct.
I finally installed Slackware and now I have Windows, Slackware and Ubuntu in my laptop. I installed Ubuntu at the last order and at that time GRUB the default loader. But I feel that I'd like to use lilo more, so I booted into Slackware and run "lilo" and then lilo became the default loader.But then I cannot access Ubuntu anymore. Because in lilo there're no information about Ubuntu. So I added some information about Ubuntu according to that of Windows in lilo. But that failed. I still cannot access Ubuntu. I searched for the posts about this problem, and this is what they say:
Quote:
image=/ub/vmlinuz
label=ubuntu
read-only
root=/dev/sda7
initrd=/ub/initrd.img-2.6.28-13-generic
or something like this. But in my slack I cannot find the image or the initrd.