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.
Can you post the contents of your /boot/grub/menu.lst file as well as the output of fdisk -l Mr.Waggel, so that we can see what grub is trying to start up?
A default install of slack uses LILO, not grub, unless you specifically choose to install it. I was making the asumption that grub was not installed and that it was probably left over from a previous linux distro. That, coupled with the common error of not installing lilo to the mbr, lead me to what I recommended in post #2. (This happened to me on my first slack install)
Go back to the installation CD or DVD and put KDE in.
I think I may be swimming against the tide by installing Grub in the last few versions of Slackware. I don't have a problem with Lilo, which is the standard boot loader in Slackware, but Lilo has an issue with high partition number say hdc34 or at the top end of a large disk beyond 137Gb. Many a time older versions of Lilo could not recognise the partition Slackware has been installed (pretty common in other distros too) and I have to work around it by going with Grub.
Last night was the third time I put Grub in Slackware. It was version 11 and I installed it in sdb12. The Sata is 200Gb with rougly even spaced partitions, the last being sdb15. I did try to edit the lilo.conf to make it work but have to give up eventually. It kept saying it could not create/establish temporary files/storage. Lilo doesn't give trouble if the distros are installed in partition number lower than 15 and I have written from scratch couple of lilo.conf to make it work before.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.