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
[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]...
After 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 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 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"
[Code]...
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]....
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'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 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 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 installed Fedora 15 on a primary partition and expected the install to create a partition boot sector, but it didn't. Did I do something wrong or is this not supported?
View 13 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 have been given a new old computer, Asus K8N-E with a 2GHz AMD Athlon 64.OpenBSD and Debian works like a charm. But with Slackware 13.1, LILO won't be installed properly. There are two disks: a 10GB ATA-drive with the system and a 250GB SATA-drive as a data repository.
Apparently the computer insists that the SATA is the first disk. Subsequently the bootable partition is not on the first disk and disables LILO to be installed. This is when I try to install LILO to a partition. When it is installed to MBR, it says something about overlapping and can't boot.
When 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 RelatedRunning openSUSE 13.1, and want to dual boot with Slackware to satisfy a long-held curiosity. However, I'm not sure how to proceed with partitioning; at the moment I have about 20gb for openSUSE root, a swap partition and the rest of the 320gb disk is home. Do I just need to add a root partition for Slackware, or are things more complicated than that?
View 1 Replies View RelatedI'm trying a Windows XP / Slack 13.37 dual-boot install and I wouldn't like to use grub. Then, at first I chose XP and after that LEET, but there was a twice lilo problems. Now I'd like to know:
1)During install what to reply during "Pick Mount Points for /dev/sda1" step, if I use NTFS Windows filesystem?
2)Is NTFS suitable in a XP/Slack dual boot schemes or FAT is in fact better?
I haven't used Slackware before but I used Ubuntu which I dual-booted with Windows XP.
Now I want to dual-boot Windows XP with Slackware. How do I install Slackware on top of my Windows?
My laptop is a ThinkPad my Windows is XP Pro SP3.
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]...
Trying to do an install with encrypted lvm. I have made it to the end of the install and chroot /mnt and then ran mkintrd which added the modules successfully but then when I ran lilo again I got an error saying that said "fatal: can not open: /etc/lilo.conf".
View 1 Replies View RelatedI just received my Slackware 13.1 & the 'Official Guide to Slackware Linux' book. I know that there is a big learning curve to use Slackware and that is why I purchased it - according to Distrowatch, "...if you learn Slackware, you learn Linux!" But, while I am 'learning Linux', I would still like to have a linux distro installed that would be more of a 'no-brainer'.
So the question is, which distro should I install first, Slackware or say, OpenSuse? I know that if I were going to dual-boot with XP, that XP should be installed first - does order matter for 2 linux distros too? Also, are there any points to remember to do during the installation processes so that I end up with a working, dual-boot computer?
I need a small distro... that i can fit into a 1.44 Mb floppy disk... so i can install latest lilo.
View 6 Replies View RelatedI have just installed KDE3.5.10 on S13.1 and have followed all steps required on the site at 'http://slackware.osuosl.org/unsupported/kde-3.5.10-for-slack13.0/' containing the packages, finishing with:
[code]...
You'll probably need to log out and back in again for the profile scripts to add the KDE3 stuff to your $PATH and $XDG_CONFIG_DIRS. When you log back in, KDE3 should start when you run X. Unlike LXDE, this install didn't automatically create a menu entry for gdm. Everything seems to be right, but I can't get the gdm entries I've tried to work. Could somebody who has also installed 3.5.10 kindly post the correct file contents?
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 successfully install backtrack 3 but i cant see windows option anywhere in my lilo boot loader
View 10 Replies View RelatedI have a PC with three HD's. My primary hard drive has a single partition and contains Win XP SP3. I have a second hard drive which I use to store junk (pictures, movies, etc). The third, 60GB HD, I just put into my PC and I wanted to install Fedora 11 onto it. I want to have a dual boot system with WinXP being the default boot. I downloaded the latest build of Fedora 11, created a LiveCD out of it and I tried to install the OS onto this third new hard drive. I installed the OS, I told it to use the entire third HD and to have a dual boot setup and make the WinXP OS be the default boot. The installation seemed to go without any problems. However, after restarting the PC, the PC stops booting right after the DELL screen. It gives me a cursor and that's it. It just sits there. I have tried redoing the install about 4 different times now and no matter how I change the different installation options, I get the same result. Now I can't even boot into XP even after I disconnect the third drive. I am guessing that the dual boot got screwed up; I just don't know how to fix it and more importantly, how to install Fedora, dual boot.
View 15 Replies View Related