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]...
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.
I've installed FreeBSD (sdc1) and DesktopBSD (sdc4). When I try to boot DesktopBSD it boots FreeBSD.here is menu.lst
###Don't change this comment - YaST2 identifier: Original name: other###
title FreeBSD 8.1
rootnoverify (hd2,0)
chainloader +1
###Don't change this comment - YaST2 identifier: Original name: other###
title DesktopBSD-1.7-amd64
[Code]...
I guess the chainloader boots 1st ufs slice and ignores the other. I've installed GrUB in FreeBSD and when I try to boot with different menu 'configfile /boot/grub/menu.lst' it returns error 17. This is probably due to inability reading ufs.
I have an install of slack64 13.37. I am unable to find grub in the repo via slackpkg search grub. It doesn't seem to be in the release package list either. Ditto the extra and testing repo. Has it been removed?
View 4 Replies View RelatedI 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?
Slackware is my main desktop, however, I decided to give Fedora 15 a try and overwrote the MBR installing it with grub. Now I want to keep fedora and its grub, just I can't get slackware to boot.Fdisk:
Code:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
[code]....
I started a thread asking for advice in the hardware forum. I didn't want to post a duplicate thread, but I was unable to get it moved here, so I'm kindly asking you slackers to help me install the aforementioned driver.
View 1 Replies View RelatedI am a slackware 13.1 user , and for the first time today I tried to use slackpkg to update my chromium ( I did everything by hand before ), but unfortunately it did something .... while it was prompting everything it was doing , I saw it removing all my main utilities such as exec, grep, sh .... After the operation completed , I was unable to run anything , everything I clicked on generated the message ( I dont actually remember clearly ) KDE/init/ ' unable to open terminal' Now that I rebooted my system , I get the following error :
++ Kernel Panic - Not syncing : no init found , Try passing init = option to kernel.
Ive looked up some forums and the ways they suggest does not work.
I boot my slackware through usb and I don't install lilo. I want to add slackware to fedora grub.conf.I have tried some methods,but failed. How can I do? fedora grub.conf
Quote:
title Fedora (2.6.35.10-72.fc14.x86_64)
root (hd0,5)
kernel /vmlinuz-2.6.35.10-72.fc14.x86_64 ro root=UUID=5cc13bf9-725f-
[cod3e]....
I'm using slackware 13 and now i want to add slackware 13 to grub .How do i have to do it ? Slackware is great to learn because i've a lot of linux using slackware than using any other distro. But some programs are dependant on other which i was not able to install, they call it dependencies. Even though compiling from source is great but runnning the program is a problem as the program terminates may be because of some dependency not installed.The same goes with sbopkg and others ..As of now i'm thinking of installing Ubuntu along with Slackware13 as this system is used by everybody in the family. How to add slackware to Ubuntu's grub.......
View 3 Replies View RelatedMy Slackware boots using the huge kernel. I am not using LILO; I am using GRUB from the extras directory on the DVD. I followed the tutorial @ [URL] up to the point where it discusses modifying LILO. My /boot/grub/menu.lst reads, in part:
# Linux bootable partition config begins
title Slackware Linux on (/dev/sda7)
root (hd0,6)
kernel /boot/vmlinuz root=/dev/sda7 ro vga=normal
# Linux bootable partition config ends
This boots the huge kernel. What changes must I make to the above menu.lst entry to boot using the generic kernel?
I use Alien Bob's mirror-slackware-current.sh with an excludes.txt to only download the parts of current that I want. Unfortunately it is not working for part of the exclude.txt file and I am at a loss to know why.
The excludes.txt is
Quote:
slackware64/e
slackware64/f
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txt
slackware64/kdei/kde-l10n-ar-4.5.5-noarch-3.txz
[code]...
This ignores e/ f/ y/ testing/ pasture/ source/ and usb-and-pxe-installers/ It also ignores most of kdei/ and /extra It is meant to ignore most of extra/source and just download the source for flash-player-plugin, but it is ignoring all of extra/source/, however the same syntax is working for kdei/ and extra/.
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.
i got a problem in my laptop so i moved the hdd from a laptop to another one like it slack worked but win 7 didn't so i booted slack moved my files from the windows partition to the slack one the i formated the windows sector now i can't go to the Slackware and boot it and i have my files in the /home/root/Desktop so i did try to boot a live cd but i can't access to this file.
View 1 Replies View RelatedI downloaded NetSecL today to try it out and see what it contains. At first I tried installing it to USB, which after reboot gave me a kernel panic. So I tried installing to my spare laptop, dedicated for testing. Installation went flawless, no errors whatsoever, but when I rebooted the strangest thing happened.
Half of my screen was filled with 07 07 07 and nothing else. No errors on screen, nothing. Not even the LILO boot screen, which I got when booting from USB (just before the kernel panic).
I've used this particular laptop (HP Compaq NX7010) lots of times with a variety of OS and LiveCD, just to try and test, and never have I seen this before.
what this strange behaviour is? I tried installing another OS but got the same behaviour, so I booted from GParted LiveCD, formatted the disk and created a new partition table. After that I was able to install whatever OS I wanted (except the NetSecL).
I try to install Slackware to my IDE hard drive and boot first from Slackware DVD. After I loaded huge.s kernel, and tried to partition the hard drive using fdisk by entering "fdisk /dev/hda", I found out that the partition size is max to 3 Gigs instead of 80 Gigs.
I think the kernel is looking at my boot disk, which is around 3 Gigs. How can I make so that it looks at my IDE drive instead at my boot drive? Is there any manual that shows me how to install Linux from scratch this means I want to wipe out all my hard disk and install Slackware Linux there?
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 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 RelatedSometimes, when I need to affect some quick changes on my box, I boot up in runlevel 1 by adding "single" to my kernel line in the Grub menu. I use Grub because I also have Vista+RHEL+CentOS for operational reasons and then Slack for everything else.Since I upgraded to Slack13 I noticed that this was not working. I assumed that it was because I had installed on a encrypted LV, so I tried it on VirtualBox installs. I tried both on GRUB and LILO on the Virtual Slack. I tried both the 32 and 64 bit versions. It does not work.
View 10 Replies View RelatedIn light of my previous achievement in wireless networking, I've decided to create a larger issue for myself to solve. Which hopefully I can get some help with. Because my system is totally kisspoped up, for those of you who get what that means. I was trying to install GRUB via the .txz package and it created a mirrored image of the /boot folder. Which for some reason contained the / folder. Which in turn held /boot and all the other folders / is expected to contain.
Now, trying to remove the extra /boot folder proved difficult, but once I finally was able to figure it out, I remembered I could removepkg and that would probably mend the situation. However, I was already 20-something percent through moving the files to trash. Now when I checked /, /boot was gone from there. Along with various other folders. SO! Apparently the /tmp/boot folder created was in reality the /boot folder, albeit in the wrong place and having the wrong contents. Somehow, one folder existed as two different versions of itself at the same point in time. Much as a Time Lord might. Deleting one made the other vanish with it.
Good news:I removed it via Thunar and it should be in the root user's trash /home and some other folders had yet to be trashed when I hit cancel, so I can still use some things Bad news:I never ran X as root, so I don't know if it HAS a trash folder I can only use things already started up because the binaries are gone, but the configuration files in /home are still there (although /usr/bin remains)
Ideally, there would be a big UNDO button somewhere in this long row of function keys. Reasonably, there should be some kind of restoration tool. Realistically, I think I'm going to have to reinstall the system, which wasn't easy in the first place due to my faulty disc bay which detects discs at will.
I updated my kernel in slackware current but can't install lilo, when i was with my old kernel it gave an error about not finding the sda drives (they were named hda before the upgrade).I booted into the slackware 13.0 dvd and modified fstab and lilo.conf replacing hda with sda but lilo still gives an error of not finding sda drives.How can i install lilo so i can boot into my sistem??
View 14 Replies View RelatedI 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]...
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?
A friend of mine threw me an OLPC (original model with 1GB of storage) that he was trying to put slackware in. He managed to install a minimal installation, but now it asks for the e2fstools (the stuff to run fsck on ext(2/3/4) partitions) which he didn't install (he formatted the "disk" as a single jfs partition). Is there any reason why it would want to have those tools given that there are no ext(2/3/4) type filesystems in that machine? And is there any specific init script (or udev rule) that can be edited to make it not try and check ext(2/3/4) partitions?
View 4 Replies View RelatedI successfully managed to install slackware on a laptop with a broken optical drive, no floppy drive and no option to boot from USB stick, with the invaluable help of AlienBOB's guide: some of the packages could not be installed during the installation. The fatal errors seems to occur randomly and the packages that I later had to install by hand were the following:-git-java (can't recall exactly what it was about)-linux-howtos-kdebase-workspace
View 4 Replies View RelatedI have, for awhile, had Ubuntu 10.04 as my main OS. I decided to go back to SW13.1, and added it in as dual-boot, with grub2 as my bootloader.
grub sees/boots SW fine.
But SW boots in 640x480, and is fugly, to say the least.
How do I change this? Grub currently runs at 1024x768. And in lilo, it's easy as pie to change the kernel boot resolution.
How do I do this in grub2? (Notice I said grub2, because it's MUCH different than grub, as far as config files and the like)
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 ?
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
I am running the latest suse release downloaded directly from their website. I ran the installation after buring the dvd and everything seemed to be working fine. after the installation i ran updates and used it for a little bit. When i shut it down that night and went to restart it I got an error that stated the OS wasnt there. I then went through the installation and everything and it retained the information from the installation before (web history etc.) but for some reason every time I reboot or shut it down the system is not able to read the startup information from the hard drive and will not come on without me re installing it.
View 9 Replies View RelatedI've setup a dualboot-system. SUSE 11.2 starts automatically and works well all the time.
But when I want to use XP (yeah, sometimes I do that...), in about 40% of all cases it won't be loaded when chosen in GRUB. Just a black screen without anything else.Then I need to restart and in the 2nd trial it works!