Cant install Slackware 11 on dell dimension 4100 creepy!
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.
Distribution: server=slackware or CentOS; desktop=Suse
Posts: 6
Rep:
Installing Slackware 11 or 12 on older system with older BIOS
I spent several hours trying to install Slackware 12.0 on an older machine. Only recently did I learn about the "-boot-load-size 4" vs "-boot-load-size 32" issue. Apparently, older BIOS can't do the 32. Slackware and Slackware 12 official ISO images were both made with 32. My solution was to mount the standard Slack 12.0 DVD on a different machine, copy the contents to a directory, then create a new iso image with "-boot-load-size 4":
I spent several hours trying to install Slackware 12.0 on an older machine. Only recently did I learn about the "-boot-load-size 4" vs "-boot-load-size 32" issue. Apparently, older BIOS can't do the 32. Slackware and Slackware 12 official ISO images were both made with 32. My solution was to mount the standard Slack 12.0 DVD on a different machine, copy the contents to a directory, then create a new iso image with "-boot-load-size 4":
Distribution: server=slackware or CentOS; desktop=Suse
Posts: 6
Rep:
Quote:
Originally Posted by onebuck
Hi,
Did you try booting with another earlier Slackware release install cd then swap with Slackware 12 cd1?
Yes, I tried booting a 10.2 CD and installing, but that version is 2.4 kernel; slack 12.0 is 2.6 kernel. It complained during the install about incompatible glibc (wrong kernel).
I'm curious about the reason why they started using the larger "boot-load-size 32" in Slack 11. Is there any advantage?
Yes, I tried booting a 10.2 CD and installing, but that version is 2.4 kernel; slack 12.0 is 2.6 kernel. It complained during the install about incompatible glibc (wrong kernel).
I'm curious about the reason why they started using the larger "boot-load-size 32" in Slack 11. Is there any advantage?
I should have been specific with the release. If you use the Slackware 11 then swap out with the Slackware 12 cd1, you will be able to boot. Read the Slackware 11 Release Note.
Quote:
Originally Posted by jessica6
I'm curious about the reason why they started using the larger "boot-load-size 32" in Slack 11. Is there any advantage?
Quote:
excerpt from 'man mkisofs';
-boot-load-size load_sectors
Specifies the number of "virtual" (512-byte) sectors to load in
no-emulation mode. The default is to load the entire boot file.
Some BIOSes may have problems if this is not a multiple of 4.
Thank you so much for posting this. I've had problems with my old Pentium III ever since Slackware 11 was released. I did what you posted and it worked like a charm! I did some tweaks to it. Instead of just copying to kernels, and I just went ahead and copied the whole cdrom and burned it. That worked just fine.
You're very welcome...this was an interesting problem since
it required not just that one read the readme's and release notes
and the isolinux readme for Slack 10.2 -- 11.0 But to notice
what was changed! If not for the slack usenet group and
William Hunt's post on alt.os.linux.slackware that lead me to this,
I'd still be scratching my head :-)
Actually, its kinda fun to burn your own custom slackware iso's :-)
--Lawrence
Last edited by letitgo; 02-12-2008 at 05:50 PM.
Reason: spelling
Distribution: server=slackware or CentOS; desktop=Suse
Posts: 6
Rep:
Quote:
Originally Posted by onebuck
Hi,
I should have been specific with the release. If you use the Slackware 11 then swap out with the Slackware 12 cd1, you will be able to boot. Read the Slackware 11 Release Note.
Obvious as to why the increase from 4 to 32!
Still not clear to me why 32 is better than 4. With 4, it installed great. I'd imagine the installation would have been satisfactory with 4 on a newer system as well. Sorry if I missed something in the translation!
But I'm happy with my slack12 DVD that works on all systems, new and old alike.
I mount cd's on /mnt/cdrom, so with the first install cd for Slackware 10.2 mounted, consider this quote from the *isolinux* readme at:
/mnt/cdrom/isolinux/README.TXT
Quote:
Techincally the --boot-load-size should be a lot bigger, like 20 or so
in order to hold the isolinux.bin boot block. However, setting it to
4 causes it to load on more BIOSes. I don't know why, but I've had so
many people report this to me that I'm inclined to believe it. But, if
the resulting discs don't boot in your machine and you find that using
a more correct value here fixes it, please let me know! If it's going
to be broken for some BIOSes either way, I'd rather be correct.
I should note that this is not a part of Slackware 11.0. Seeing that
as a difference in Slack 10.2 vs. 11.0-12.0 is the clue that solves the
mystery...
In the *isolinux* readme for Slack 11.0, this is the mkisofs example:
Hello all. Just like to say this is my first post, and what a helpful bunch of people this looks like!
Anyway, here's my problem...
I currently have an old computer lying about which I want to run Slackware 12.1 (to be used mainly for web surfing etc). Specs:
PIII 450MHz
SuperMicro P6SBA motherboard (BIOS updated to latest official version)
Plextor CD-RW drive (bit vague I know, but issue is with BIOS)
I can boot Slackware versions up to 10.2, but no later. I have come to the decision that I am faced with the boot sector problem discussed earlier (yep - I read the whole thread).
I have tried the following with no success:-
Booting with a Slackware 10.2, then swithcing to 12.1
Booting from USB or other devices
Using Smart Boot Manager (and other boot programs, actually)
I have read the instruction on how to create an image with a smaller boot sector, but I have absolutely no idea how to do this. I only have one computer (the one mentioned above) and it is currently running Windows XP Pro, so the image-making instructions make no sense to me!
Is there a simple way for me to create a CD which will boot on my old machine from within windows?
Annoying problem isn't it? Let me clear this away first: is the
Slackware 12.1 install disk a CD image, and not a DVD, and does it
have the correct md5 checksum? I know this sounds obvious, but if
you or someone else burned the disk from the web, mistakes are possible.
I read that you only have the one computer, but if you have access to
another newer one, a quick check is to try the 12.1 disk in a newer
computer to see if it boots.
When a 10.2 disk boots, you mentioned that swapping to the 12.1
disk did not work. Jessica6 reported that the installer complained
about the glibc version. Is that what happened? I.E,, after
linux loads, and the welcome text and boot prompt appears, and you
accept the default bare.i kernel for 10.2 by hitting enter, what
happens when you swap out the 10.2 disk and type setup?
Note that the 12.1 default smp kernel will not work for your hardware.
If you get that far, later you must use huge.s for 12.1 on your
machine.
Oh, let me speak to your question about creating an altered 12.1
boot disk on windows: I don't know how to do that. (sorry)
Just as an aside, if you only wish for limited uses, why not use 10.2?
It kept me happy for quite awhile :-)
Finally, if all else fails, and 10.2 installs, 10.2 can be used to
create a boot disk with the -boot-load-size 4 attribute that might
work for you to get 12.1 Check the instructions in
12.1 dsk1 /isolinux/README
You could also use the upgrade procedure from 10.2 to 12.1, but
carefully read the instructions first. This does involve a 2.4
to a 2.6 kernel, maybe a new initrd and some lilo edits. The docs
are in 12.1 install dsk1 UPGRADE.txt
HTH,
--Lawrence
Last edited by letitgo; 07-30-2008 at 03:50 PM.
Reason: corrected version numbers
The ISO size is about 30 MB for the Slackware 12.1 install ISO. These ISOS were built with the -boot-load-size 4 so they may just boot on your computer.
What you need is a copy of the Slackware DVD's /slackware directory somewhere on the hard disk. The ISO is so small because it does not contain a single package, just the kernels and the setup files. During installation, you can point setup to a "pre-mounted partition"... which implies that after booting and before running 'setup' you must manually mount the disk partition (can be vfat or ntfs too) where you copied the Slackware package directory.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.