Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am a newbie and I realize I have probably dived in at the deep end with this and I need some help swimming.
I used SuSE before, but people kinda kept telling to get a Real Distro. So today, after only having used Linux for two weeks, I made an attempt to install Slack. The installtion process sure is different, heh.
I got till the end, however, having made the partitions and selected things to install and watched it install a lot of stuff that I don't understand, and then I got the instructions to exit the setup and reboot with ctrl alt del. I did that and now I get this at startup
I chickened out though and went back to SuSE. (I'm probably going to give Slack another try a bit further down the line. For now I just need a working computer.) I think maybe I know what I did wrong though. I think I forgot to mount the partitions. Will definitely remember that the next time.
You can add as many distros to you box as you like. All you need is about 5Gb hard disk space per distro. I have 50+ systems and about 42 of them are Linux.
No need to chicken out just add one distro whenever you have time. Grub can boot the whole lot.
Processor: p4 1.6 Ghz 32 bit
Motherboard: Intel 845 GLAD
Samsung 40 GB HDD (IDE)
Samsung CD R/RW drive
USB mouse and Keyboard.
The HDD is partitioned like this:
/dev/hda1 ---> ext3 ----> / (6GB Approx)
/dev/hda2 ---> ext3 ----> /home (15GB Approx.)
/dev/hda3 --->swap ---->swap (300 MB Approx. )....128 MB physical RAM.
The Problem:
The PC hangs at GRUB prompt and beeps the motherboard speaker continuously. It does not respond to KBD.
Before that it installs all the packages without problem.
The standard method to get inside an unbootable Linux is either by its installation CD or boot it up to a Live CD.
In both case you need to boot up a kernel in command shell, mount the distressed distro and change root to it. Say if you boot to a Live CD or Slackware installation CD and in bash shell (your / partition of Slackware is hda1)
mkdir /mnt/hda1
mount /dev/hda1 /mnt/hda1
chroot /mnt/hda1
If the above works you should see the command prompt sign changes slightly, signifying you are now inside the distressed Slackware.
You can then try to replicate the boot loader in the MBR again or in a floppy by stataement
grub-install /dev/hda<---- hda means whole disk
grub-install /dev/fd0<----- enable you to boot from a floppy
However if the boot loader has not been installed properly your /boot/grub/menu.lst may not be complete and the above could only boot up a defective Grub unable to pull Slackware up. The cure to this depends on how bad a state Grub is in.
You can list Slackware's /boot/grub/menu.lst here
Your Slackware 10 should be bootable if the /boot/grub/menu.lst has the following entries
title Slackware
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro
As you haven't seen Slackware boot loader I have a bad feeling that you may not know what Grub looks like because Slackware comes standard with Lilo as the boot loader. I personally downloaded Grub 0.97 and installed it in the last two versions of Slackware. If your Slackware does have a Lilo then it should boot if its /etc/lilo.conf has these entries
Problem solved...i forced LILO to install in MBR...now it's booting fine...but there's another prob....X server won't start....it says inetd socket not found....i checked that inetd was running...wat can be the prob?
The standard command to fire up X-windows is to type
startx
at the terminal. If X-windows has been installed then there is nothing we can do. If X-windows didn't fire up due an error then it is a matter to amend xorg.conf which is stored in /etc/X11 directory.
-------------------------------------
rinkrat248
If you make a Grub floppy unattached to an operating system, described in Chapter 3.1 of Grub Manual using just a Live CD that supports Grub like Ubuntu or Mepis, then you can boot up this floppy and fire up Slackware manually using these lines
root (hdi,j) <-----i=disk No., j=partition No. and Grub counts from 0
kernel /boot/vmlinuz ro root=/dev/hdxy <-------- suppy hdxy as the root partition of Slackare
boot
That is the way I boot up my Slackware 10.1 and 10.2 after the installation.
Grub floppy gets you into a Grub prompt. You can ask Grub to find out where Slackwar stores the kernel by typing
find /boot/vmlinuz <--- Grub will tell you which (hdi,j) got it
Once you fire up Slackware install Lilo again by typing at the terminal
i have had this problem for ages...
either an error 17 or 15, (it changes depending on mood)
the cox is fully useable... i just have to boot with a boiot floppy and it woirks fine
kinda anoying but bearable
hmmm i tried
thge lilo option but now when i boot my machine
it dousent recognise my hard drive at al...
and when i try with the boot disk i get the folowing:
VFS: Cannot open root device "hda1" or 03:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 03:01
i then tryed specifying the following parameters at the boot: prompt
mount root=/dev/hda bare.i
giving the same result.
well i halted my machine for a while and tehn started itr again and lo and behold the HDD was recognised again!
seems that this machine has a habit of this as i remember a simmaliar thing happenning when it still ran Windowz 98 SE
now i get lilo when i start and the annoying bootdisk is out of a job!
for some starnge reason though ttl1 has an image of tux sitting at the top and all text is so minute that you can barley read it! no good if you dont want to use x (using ttl2 works fine though)
i had windows. then i installed suse 10 with grub in mbr. I works perfectly for a week. Today i did an "disk optimicer" from Norton System Wotks in a windows partition and when i restart the pc i have the grub error 17.
I don't have any rescue disk. I only have suse 10 cds
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.