Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
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.
Hi, I have slackware current installed, and I have an extra partition I was gonna try slamd64 on, but I downloaded the first 2 slamd64 isos, which I think is all I need, then I burned them as images in k3b, but for some reason they won't boot, do I have to do anything special with the iso images to make them boot, or what's going on with it?
yeah I did, it checks the cdrom, then it sits there and hangs for a minute, then it just goes into lilo.
I downloaded the iso image twice, in case the md5sum was lying to me, and it still didnt boot.
Now if k3b worked, I'd try an older release, I downloaded the rc3 cd1, and am trying to get k3b or some other util to work again :X it's just strang, maybe it has something to do with k3b, it does burn as low as 3x, when I set it to 52x on my 52x burner.
nvm I know the reason, but not the solution, I burned it in xcdroast, to see if it would work, and when it completed, it said possibility of 25 buffer underruns, but it was the only thing I had open, so I'm going into windows to burn it, but does anyone know how to fix that problem?
That is * the problem of it burning slow, making the whole pc slow, and getting buffer underruns.
and it burns at under half the speed I tell it to.
I downloaded and burned them using nero in windows.
Got a better connection at work and did it there.
I had some other problems with SLAMD64 linked to my seagate SATA hdd. Could for some reason not get the mkswap part to work and got a segmentation fault error. This is described in an other thread here at linuxquestions.org. Dodged the problem by keeping my existing Slack install and did not toutch the swap partition during the slamd64 install.
I had the same problem with the RC4 ISO, it seems a problem some BIOSes and the El-Torito settings used on the ISO. You can boot the CD using Smart Bootmanager. Grab sbootmgr.dsk from the rootdisks/ directory on the Slack CDs or a Slack FTP site, and write the image to a floppy disk with:
dd if=sbootmgr.dsk of=/dev/fd0
Then boot with the floppy disk, and choose to boot the CD-ROM.
I just got a hp dv5k laptop, my old one was a compaq. I have slackware 10.1 and windows xp. Slackware boots fine, but it sucks not being able the additional 32 bits on my processor, which seems much slower in a 32-bit enviroment. So i tried installing slamd64 10.2, it gets to the boot prompt, loads the bare.i img, and init, then starts to detect hardware, then the screen goes blank, any suggestions?