Problem booting huge.s on old computer
As one can see here, I already encountered problems which turned out to be caused by de Slack Image itself.
However, now that I'm able to boot from the CD (thanks to SBM), I encounter another (Slack-specific) problem. Because hugesmp.s causes the boot-procedure to auto-reset (happened on several older computers, maybe due to low memory?), I use huge.s to boot into the installer. However, although huge.s solved my problems on the other old systems, it also encounters problems on this machine. This is the message I recieve: Code:
checking if image is initramfs... it is The system is an old P1 133Mhz with 16MB RAM and a 850MB HD. It was good enough to run Slack 10.2, so I figure it should be possible to run 12.0 as well. I guess the huge.s kernel is too big. Can anyone confirm? How can I solve this problem? |
Try to build your own kernel. Copy the config from the Pat (sources) and start to remove unnecessary support for hardware.
EDIT: Sorry, just realized the problem.. What about to modify the iso of the first CD and insert YOUR kernel? It's not TOO hard. I remember there is a guide to convert the ISO's cd's to bootable DVD, the procedure will be same to make your CD bootable. "unzip" the iso to a folder, add your kernel > burn it. (share your work vi torrent :) ) Also what about to install some older Slack and then upgrade with YOUR kernel? |
that is a very old PC, if Slackware-12 can not be made to run on it you may be able to get Slackware-11 on it since it will be kept updated for a while longer (how long Pat V. keeps Slackware-11 updated with bug fixes & patches only Pat knows) but i would tend to think the bare.i 2.4.xx kernel in Slack-11 wound do that old PC some justice...
|
Quote:
Slack 10.2, XFce |
It runs 10.2 right now..
Quote:
However, because I wanted PHP5 & MySQL 5.2 on this web-dev-server, I just wanted to go the easy way and reinstall Slack 12.0. I might as well download & install PHP & MySQL, but I think that might be more work, no? Especially PHP5, had some troubles with it a while back and I don't have the time for such problems :) I guess I have no choice though, solutions offered here are also time-consuming.. I'll see what I'll do.. Thanks for the input! |
All times are GMT -5. The time now is 12:10 AM. |