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.
I'm using bareacpi.i (bare.i would just hang when loading the kernel while it is seeking for the harddrive).
I had installed the system without problems a couple of times from my slack11 dvd from the secondary slave disk. But then yesterday I had ANOTHER go at it (I'm trying things;>...) and it said there were corrupted packages. It happened several times, with different packages each time, then the installer looped repeteadly asking me which packages to install (it happened at least twice), then it began giving corruption errors without stopping installation (I could recognize the error window flying by while the installer was copying the various packages). it even began asking me for other cds (as if I were doing the install from the cd series instead of DVD).
tried from my secondary master (DVD recorder) and no problems.
I redid an image from my Slack11 DVD and checked it against the checksum, everything was right. As a note, I redid the image reading from the secondary SLAVE (the one giving me problems), it even didn't have any read retries/errors...
Uh-oh. So; meanwhile ('twas a long break) I got my hand on a second PC intended to play with tux on it. But there must be some real trouble around me - when an attempt to install Slackware 11 on this machine is made; it is followed by identical results then in the case of my first PC. But what happened before?
Downloaded the SW 11 iso's, checked them against the md5 checksum; burned them (on r media, not rw!) with verifying enabled then rechecked the files on the cd's against the md5 checksums on the root of each disc. So far; no problem (at least, I thought).
Inserted onto the CD-ROM on my new (but in fact old) machine, chose the adaptec.s and after the copying of files started the error messages appeared (starting with acpid-1.0.4-i486-2.tgz).
The target PC:
Motherboard: Asus P2B-DS (i440BX)
CPU: 2x P-III 450 MHz (Katmai)
RAM: 2x 256 MB PC100 SDR
GPU: something from Matrox; AGP
Storage: Adaptec AIC-7890 (on-board SCSI controller) with
ID#1: 9GB WDC HDD (sda)
ID#2: 9GB WDC HDD (sdb)
ID#4: NEC CD-ROM (uhh...src?)
(I may look after more exact specifications if requested)
The next step will be asking someone to burn SW install discs for it seems that the magic is in my cd burner... or not?
(They were recorded on a Teac CD-W540E w/ latest firmware. Note that it works flawlessly and with other installation cd's (xubuntu, gentoo, win2000, winxp) - generally, with all cd's burned with this one no problems occured.)
After the setup starts the copying part from the cd the error messages also start to appear. All the same; except the filename:
Code:
INSTALLPKG ERROR #1
There was a fatal error attempting to install /var/log/mount/slackware/a/acpid-1.0.4-i486-2.tgz. The file may be corrupt, etc.
bioe007:
A friend of mine lend me a cd-set of 10.2, which - he claims - was succesfully used for a few installations. The check against the md5 sums proves this - all ok; but on attempt to install the same error messages appear (with different file at the beginning).
To summarize so far: on 2 different PC's no matter where the install disc came from there seems no way to complete an installation.
Uh-oh. So; meanwhile ('twas a long break) I got my hand on a second PC intended to play with tux on it. But there must be some real trouble around me - when an attempt to install Slackware 11 on this machine is made; it is followed by identical results then in the case of my first PC. But what happened before?
Downloaded the SW 11 iso's, checked them against the md5 checksum; burned them (on r media, not rw!) with verifying enabled then rechecked the files on the cd's against the md5 checksums on the root of each disc. So far; no problem (at least, I thought).
Inserted onto the CD-ROM on my new (but in fact old) machine, chose the adaptec.s and after the copying of files started the error messages appeared (starting with acpid-1.0.4-i486-2.tgz).
The target PC:
Motherboard: Asus P2B-DS (i440BX)
CPU: 2x P-III 450 MHz (Katmai)
RAM: 2x 256 MB PC100 SDR
GPU: something from Matrox; AGP
Storage: Adaptec AIC-7890 (on-board SCSI controller) with
ID#1: 9GB WDC HDD (sda)
ID#2: 9GB WDC HDD (sdb)
ID#4: NEC CD-ROM (uhh...src?)
(I may look after more exact specifications if requested)
The next step will be asking someone to burn SW install discs for it seems that the magic is in my cd burner... or not?
(They were recorded on a Teac CD-W540E w/ latest firmware. Note that it works flawlessly and with other installation cd's (xubuntu, gentoo, win2000, winxp) - generally, with all cd's burned with this one no problems occured.)
Hi,
Since you have been getting the same errors. When you check the
md5sum for the iso, check the cd. You could look at the CdromMd5sumsAfterBurning. A lot of problems can be associated with the original iso and how it is burnt.
BTW, try the huge26 or test26 for the boot kernel. Read the RELEASE_NOTE for Slackware 11.
An update: forgot to mention, but at the last time istallation (with the lend cd's) happened to notice the messages which appeared on the *black* background when a screen *flickered* between those error messages:
Code:
/usr/lib/setup/installpkg: cannot create mount/var/log/setup/temp/
No space left on device
Meanwhile; I finished a FreeBSD installation on this (the P-III) machine (from the same CD-RW medias), which will act as a NFS server to try the slack network install from there on the second PC... maybe not the most *elegant* way - but I did it for fun (...yet)
Later today gonna try the huge26/test26 kernel and if fails, I'll give a try to some live CD's.
A nice day to everyone and thanks for the support so far!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.