SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I tried to install on my computer; everything seemed to go well, and quickly,
until it was time to exit setup and hit ctrl alt del, and change boot media to
hard drive. The usual items that scroll by did not seem to be present, what
you normally see in dmesg, but rather info related to irqs, etc. After about
a minute, there was a clunking sound from my speaker, the screen went
blank, then showed "no input signal", and the computer light was still on.
I reinstalled several times, same result. I had configured lilo, thinking
I would install FreeBSD later for dual boot….the only place I had entered
any info about the video display was there, so I thought I'd see what
happened if I didn't install it. The attached photo shows where it
hung up after rebooting.
I have no idea what to do here, other than try to reinstall 13.1, maybe 13.37.
Any help greatly appreciated.
i got that L followed by bunch of 9 screen when my active partition doesn't have a bootable file system...are u able to boot into slackware with the CD using "huge.s root=/dev/sdaX rdinit= ro" ? if yes just make sure your lilo.conf is correct and rerun it.
I did the partitioning, install, and system configuration, and had the problem again.
Leaving the system in that state, I took it to the disk partitioning step sgain,
without partitioning again, since it's already configured, and looked at inittab.
There is no runlevel specified. Triwd to edit, can't access vim.
I have a weird setup, SCSI SATA and PATA (old IDE). I see the 99's when I am trying to boot from the wrong device. Do you have multiple hard disks? Also my solution was to install lilo on a floppy.
One thing I found is that when I boot on a CD-ROM the drive order is one way; and when I boot on the installed Slackware OS the drive order is different. Creates all kinds of problems if one has different drive types.
I have only one drive. The clunking sound seems to occur when everything just "stops". The L 99 problem only occurred when I did not configure lilo during setup.
output of fdisk -l shown, likening when I can determine
I'm trying to install slackware64 13.37 to see if it will install properly.
I burned the iso image on my Macbook Pro, but it doesn't appear
to be automatically bootable like the slackware64 14.0 image I
burned on my desktop. It pauses for a few seconds, showing
since I don't know what to enter to make it boot the 13.37 dvd,
it then tries to run the defective 14.0 install, which leads to
the situation I've previously described.
How can I boot the 13.37 dvd?