Slackware :: Dual Boot With Lilo On Btrfs - Slackware 13.1?
May 29, 2010
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]...
View 13 Replies
ADVERTISEMENT
Jul 18, 2011
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.
View 17 Replies
View Related
Dec 16, 2010
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 Related
Jan 19, 2010
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]...
View 16 Replies
View Related
Feb 27, 2010
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"
[Code]...
View 2 Replies
View Related
Nov 8, 2010
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?
View 5 Replies
View Related
Jun 18, 2011
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?
View 5 Replies
View Related
Jan 1, 2010
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?
View 4 Replies
View Related
Nov 29, 2010
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.
View 8 Replies
View Related
Oct 27, 2010
I installed Slackware 13.1 and Windows server 2008, I also installed LILO in MBR, I Found I can boot into slackware, but can't boot into Server 2008. then I　use command bootsect/fixmbr. now I can boot into server 2008, but the problem is I can't boot into slackware. I try to install lilo to supper sector. it's not works. I only can boot my slackware by a USB stick.who can help me to solve this problem? I really need these two systems.
View 5 Replies
View Related
Aug 16, 2010
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 Related
Apr 14, 2010
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]....
View 2 Replies
View Related
Mar 1, 2010
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?
View 14 Replies
View Related
Sep 19, 2010
My new job requires I use Windows and as such I put a second HDD in my laptop for the purposes of Window/Work The issue is that Windows will not install on this second disc (Windows cannot create partition or install to disc). I got around this by installing Windows to the first disc, then the second then putting Slackware back on the first but then I suffer the "Bootmgr cannot be found, press ctrl + alt + delete to restart".
I am using Lilo and I have never really had an issue dual booting them on the same disc (Admittedly over a year ago) but it is of the utmost important I have them on separate Discs. Has anyone encountered this and/or know a way around?
View 4 Replies
View Related
May 8, 2010
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?
View 13 Replies
View Related
Mar 14, 2011
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 Related
Jan 21, 2010
So I got slackware 13 from the website and created 4 partitions (primary) and left some (100GB) space as I planned to install windows 7 in that. After installing slack, when I booted from windows DVD (rtm) in partition section it said I already have 4 primary partition so windows cannot used the rest of space despite the fact that it was free (windows even grayed all options like new partition and format etc. for that space). So I thought I'd create 2-3 primary partition for linux (slackware) so that windows can use the free space and make it a primary partition.
So, Next I formatted with slack (3 partition, 2 Primary, 1 extended, total space for slack 50GB) and after its installation I worked my way with windows, but it just created one partition of 100Gb, won't let me create any saying all primary partitions are created. Anyway, I created that partition and installed windows 7. But it messed up my lilo (slack won't show in boot menu) neither can I create any new partition.
After all I reformatted again created 2 partitions for windows (that actually became 3 as windows 7 create 100Mb separate partition for system). Installed windows correctly. Then I booted with slack , which allowed only creating 1 partition as 3 were already there. So I created 1 extended partition, in which I created 4 partition 1 to mount for /boot (100M), 1 for /swap (3G), 1 for home (10G), 1 for / (35G) everything worked fine till I reached last point to install lilo. At that point it said cannot install Lilo (I tried all options simple, expert, install to MBR etc.) but it just won't install. Anyway, after that it said you can install it manually so I clicked OK. Then it said setup complete, remove disk and press alt+ctrl+del to reboot, which I did. But there is just windows 7, no slack ?
View 9 Replies
View Related
Jan 24, 2010
I'm trying to take my current windows7 (x64) setup and make it into a dual-boot setup with slackware 13.0 (x32) and am hitting a brickwall. I guess I would like to know if I can salvage the situation without formating my windows drive. I fully intend to, but I had hoped to not do it this month. I'd like to get dual boot going so I can master it and acquire all the files/drivers I'll want and then format and do it 100% right next time.
Currently I have windows setup on a 3x 500gb Raid0 onboard array which itself has been flawless. After I shrunk my current partition size to give me about 25gb of free space I proceeded to setup Linux, and I was unable to perform the cfdisk portion for partitioning the array for Linux.
I tried using cfdisk:
/dev/hdx (a1-a3,b1-b3)
/dev/sdx (a1-a3,b1-b3)
I even attempted to locate with: cat proc/partition and tried using cfdisk on every device it located. It always said it was either an unknown partition table and should I start at zero, or bad partition. I was of course too concerned over my windows setup (which has almost 1tb of stuff I have not backed up) to go any further into the unknown.
PS: I have used Slackware before, back at 8.1, 10, and even a very brief interlude at 12.0, this is my first attempt on this computer however with 13.0, it is currently running fine on my laptop and my PS3 (Laptop is even dual booting 7/Slack13. Albeit without raid)
Phenom 9850
M2N-SLI Deluxe (Nvidia AM2)
4x1gb of 1066 kingston hyperX
3x500gb WD Caviar Black Sata2 3.0
View 3 Replies
View Related
Mar 20, 2011
I was interested in the idea of the btrfs subvolumes, so I made a virtual machine and installed Slackware as per the instructions here: [URL] It all went very well, but when I tried to switch from the huge kernel to the generic kernel and use the initrd.gz generated from step 29 (except that I used 2.6.37.4-smp instead of whatever's there) in lilo.conf, it failed to boot. I also noticed that in the instructions themselves, the poster doesn't actually add the initrd.gz to lilo.conf, so I'm guess the huge kernel has everything it needs to boot properly.
View 13 Replies
View Related
Jun 21, 2011
what do I have:2x 150GB drives (sda) on a raid card (raid 1)for the OS (slack 13.37)2x 2TB drives (sdb) on that same raid card (raid 1, too)2x 1.5TB drives (sdc,sdd) directly attached to MoBo2x 750GB drives (sde,sdf) attached to MoBo too.if i got about it the normal way, i'd create softRAID 1 out of the the 1.5TB and the 750GB drives and LVM all the data arrays (2TB+1.5TB+750GB) to get a unified disk.If I use btrfs will I be able to do the same? mean I have read how to create raid arrays with mkfs.btrfs and that some lvm capability is incorporated in the filesystem. but will it understand what I want it to do, if i just say
Code:
mkfs.btrfs /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1
probably not, eh?
View 3 Replies
View Related
Apr 11, 2011
For various reasons, I have to learn my way around CentOS. I have an old computer (P3) with Slackware on it. I threw in a second HDD that I had lying around and installed CentOS to it. I was figuring that I'd just decline installing GRUB or point GRUB to Slackware as the second OS and end up with dual boot.
The CentOS install, though, blew right past that part with offering me any options. It put a small boot partition on the CentOS drive and now the box boots straight into CentOS.
I've spent the better part of the day trying to get GRUB to boot the Slackware drive and had no luck, though I've learned a lot about GRUB error messages.
By the way, CentOS uses GRUB v 0.97.
Question: someone could point me to a reference.
Here's the output of fdisk -l on that computer (/dev/sda is a 4GB SCSI disk that was originally the boot disk for Windows 2000 server on that computer):
Code:
Here's the currentGRUB file. I added the section about Slackware. I've also tried pointing it at:
Code:
I've also tried:
Code:
Code:
Slackware's LILO:
It's been six months or more since I used this computer. It's my experiment-er "play" computer and I had taken the HDD out to test a computer for one of the members of my LUG, so I can't remember exactly how I configured the LILO install, but, if I did what I usually do, I installed it to the MBR of /dev/hda. I have considered just blowing away LILO, but I'd be happier if I could just use GRUB to call LILO.
View 7 Replies
View Related
Jun 29, 2011
how to on enable ling separate X sessions with dual monitors in slackware? In rhel all I have to do is enable it under the nvidia-settings... In slackware it does not work that well... to what I understand you have to configure a separate x session...
View 11 Replies
View Related
May 26, 2011
I plan to get a new Macbook Pro some time this summer, and I was hoping I would be able to dual-boot Slackware and Mac OS X as easily as I do on my current Sony laptop. Is there anyone here who has already succeeded in dual-booting Mac OS X and Slackware, preferably on a laptop?
View 12 Replies
View Related
May 16, 2011
I 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 Related
Apr 22, 2011
Slackware 13.0 32-bit is installed on /dev/sda5 with lilo written to that partition. Everything works and I have a nice lilo boot menu (for a WinXP bootable partion). Recently I installed Slack 13.0 64-bit on /dev/sdb5. This also succeeded (apparently). After reboot I was presented with my old boot menu, selected the 32-bit Linux option (/dev/sda5) and after login went to /etc/lilo.conf where I entered a boot stanza for /dev/sdb5 (64-bit linux), and then ran /sbin/lilo. No errors flagged. After reboot there was a 64-bit entry in the boot menu, but when selected it led to kernel panic. Further although I can mount /dev/sdb5 from the 32-bit partition there is nothing in it except lost+found.
So the current position is that I can't access my 64-bit linux partition (/dev/sdb5) to change anything in it (even boot: root=/dev/sdb5 at the boot prompt doesn't seem to work).how do I obtain access to /dev/sdb5? Second question is what items do I need in the 32-bit lilo.conf boot stanza so as to be able to boot to that 64 linux partition?
PS: OK I noticed one warning when I ran lilo.....
bash-3.1# lilo
Warning: LBA32 addressing assumed
Added Slack *
Added Slack64
[code]....
Maybe the problem is with the 32-bit addressing? How do I get lilo to use LBA32 for the 32-bit partition (/dev/sda5) and LBA64 addressing for the 64-bit partition (/dev/sdb5)?
View 5 Replies
View Related
Mar 9, 2010
after installing slackware 13 and LILO i have a dual boot options when i start my laptop. I dont have windows os on it so i want to remove the dual boot. i've tried to edit the lilo.conf to remove the dual boot or the prompt but wasn't successful. i've also tried to edit boot_message.txt this is my LILO.conf
[Code].....
View 8 Replies
View Related
Dec 16, 2010
I never tried Slackware and is curious about it.Have some questions to ask:
1)can it dual boot with windows 7? It uses Grub bootloader?
2)does it have MP3 and flashplayer plugins? It has Amarok?
3)does it have Qt compiler?
4) does it play DVD movies? Blue ray?
5) does it support USB 3.0 ?
View 14 Replies
View Related
Apr 7, 2011
I had an old laptop which ran Slackware-current, but it died. As a replacement I got a great Toshiba Qosmio laptop with Win7 SP1. Now 13.37 is nearing, and I would like to install it on a dual-boot setting with Win7. In my other laptop, I dual-booted it with XP SP3, and I remember partitioning the HDD, then putting LILO on the first sector of the root partition (instead of putting it on the boot sector).Now, I have to dual boot it with Win7 and therefore I ask: What is the best strategy for dual-booting? Are there some caveats that I need to be aware of?
View 8 Replies
View Related
May 26, 2010
I had a perfectly working basic 13.0 install on hda4; I installed 13.1 on hda1 and added lilo with an entry for each using expert mode during setup but now neither will boot from this lilo (both try but fail along the way; 13.0 comes up with some errors about sda and 13.1 screen turns black and does nothing) During the 13.0 startup it seemed to use the 13.1 kernel as there was a penguin in the top left instead of the "cat wearing a mask" image that usually shows when it boots.
I think 13.1 installed perfectly and the screen going black is another issue (I don't know why I think that but I just feel it did, it gets further along in boot up)I've managed to get 13.0 back up and bootable by chrooting in and reinstalling lilo but strangely I had to go into its lilo.conf and change sda4 back to hda4 (before this install it had been hda4 and I can't understand why it had changed) I'm running an advent 7101 laptop and have had 12.2 and 13.0 dual booting previously.
View 2 Replies
View Related
Mar 14, 2010
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.
View 3 Replies
View Related
