SlackwareThis Forum is for the discussion of Slackware Linux.
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 installed slackware 9. i set up two primary partitions. /dev/hda1 is linux swap and /dev/hda2 is bootable / .
every time the system boots, i get L40 40 40 40 halfway down the screen, then it says insert bootable disk and press any key. When i boot from the disk it works fine. However, i don't want to always boot from the disk. i want to boot from the hard drive, like a "regular" system.
At the boot: prompt, i've tried mount root=/dev/hda2 then ran lilo when the system was up, then rebooted to check if it solved the problem. With my luck, I hadn't solved a thing.
you should be entering it as .......mount root=/dev/hda2 ro
the ro is a flag to mount partition as read only!!
then the system will initilize as read/write on it's own.
I get L 99 99 99 99 99 ... on boot when installing Slack. I simply boot again from install CD (don't run setup) mount partiton on which my slack installation is under /mnt, cp /mnt/etc/lilo.conf /etc , run lilo and reboot. Then it works fine.
all right. i got my old ass acer extensa 390 up and running perfectly with slack 9. what i did was have slack automatically setup lilo and install it on the master boot record. it boots up just fine. however on my desktop, i still get L40 40 40. when i boot with the boot disk i get kernel panic. i will just use the acer until my inspiron 8500 gets in, and i install slackware on it.
This is my first day ever using slackware linux and i must say that i have learned more today than i have in the past year of using red hat and mandrake.
I guess once you go slack, you never go back. at least not for me.
No .. it has something to do with the superuser blocks that lilo saves .... if you hit "ALT - F4" you can clearly see that there is something worng because it says it can't mount the file system the says it too many file systems mounted.
the solution for this is to install lilo into the MBR (Master Boot Record) if you have another OS installed like NT this is NOT Recommaned cause NT will filp out on ya .... but if this box only has slackware on it then install Lilo into the MBR and not the superblock.
Had a somewhat similar problem with installing BasicLinux BL3 onto an Extensa 575CD hdd w/o a CD drive (http://basiclinux.com.ru/).
Even though I kept running the /sbin/lilo liloconfig program and 'hd root=/dev/hda2 ro' at the boot: prompt, I kept getting similar messages as the below. Finally went into fdisk upon a BL3 floppy boot and set active partition as /dev/hda2. Worked fine from there to run just BL3 using MBR.
Decided afterwards to download Slackware/ZipSlack -like Amigo
(http://www.amigolinux.org and LQ Amigo forum) onto this BL3 OS'd Extensa. DOS FDISK'd /dev/hda2 to FAT16, FDISK /MBR'd partition to reset MBR. Then formatted and loaded a bootable DOS, copied Amigo Linux zipped file here, unzipped it, and currently have Amigo running from this DOS partition w/o having to change active partition status again [via lilo and fdisk]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.