Installation Issues
Forum: Laptops
Topic: Installation Issues
started by: gungaden
Posted by gungaden on April 14 2005,16:07
I am trying an install of DSL 1.0 on a Winbook FX. At first I had problems with DSL recognizing the CDRom drive which interchanges with a floppy drive by removing one and inserting the other. I got around that by choosing the install option of making a ramdisk on the harddrive. Now my issue is that the install locks up at the "Checking fro myDSL apps..." line. I assume that it is looking for an internet connection at this point from which to access an applications site. If it is looking for an internet connection, the PCIA ethernet card apparently is not recognized because I cannot get a link light on the connection. The PCIA card and cables did get a link light when working with the old Windows 95 OS.Any ideas or suggestions?
Posted by cbagger01 on April 14 2005,16:48
Try booting with:dsl base
or with
dsl mydsl=hda1 (replace with the location of you hard drive files)
either of these boot commands should help.
Posted by gungaden on April 14 2005,19:10
| Quote (cbagger01 @ April 14 2005,12:48) |
Try booting with: dsl base - The process stops at "INIT: Entering runlevel: 5 or with dsl mydsl=hda1 (replace with the location of you hard drive files) - The process stops at "Automounter started for: floppy cdrom" |
Thank you for your quick response.
In summary, the install process makes it through setting up the ram disk (my Winbook FX only has 21532Kb of total memory), creating the directories and symlinks on the ramdisk, starting the init process, loading the kernel, and autoconfiguring the devices. Unfortunately, the process stops at the two points described in the above quote window. Is it possible that I am just not giving the process enough time to work? I have waited for about twenty minutes for the "hangups" to clear.
Posted by AwPhuch on April 14 2005,20:21
If your DSL hangs more than 30 seconds at any given time then something is up...Which version are you using..some of the older laptops you have to use syslinux on them..try that iso and the syslinux boot floppy and see if that works out for ya
Brian
AwPhuch
Posted by gungaden on April 14 2005,20:46
Thanks, Brian.I am downloading syslinux version now....will let you know how it turned out.
Posted by cbagger01 on April 14 2005,22:19
If you have limited memory, try:dsl base noicons
or even better:
fb800x600 base noicons
Posted by AwPhuch on April 14 2005,22:37
Well once he has both versions he can try both..im sure one of them will workBrian
AwPhuch
Posted by gungaden on April 15 2005,19:03
Ok, I got the same results with the syslinux iso... I have tried enabling/disabling PNP in the BIOS, every option for the boot sequence (failsafe, base, copy to HD, etc.). It continues to hang up at "Automounter for: floppy cdrom". Your idea about using a floppy installation might work, Brian, but I can't seem to find (or maybe I just do not know how to identify) the files to download for a floppy installation.Sorry, Cbagger, I did not see your response until a few moments ago. I tried the boot with the delimiter "fb800x600 base noicons" as you suggested. Although it, too, hung up, I notice that now, I get a period at the end of "Automounter started for: floppy cdrom" which was not there when booting under the other delimiting phrases. Another difference with using this delimiter, is that when it hangs at "Automounter started for: floppy cdrom", now the harddrive light stays on....
Posted by gungaden on April 16 2005,18:35
As an update.... I am still unable to obtain a sucessful installation. I have gotten the furthest by following the suggestions in < THIS > thread. But, alas, I only get a few steps further in the process. Also, I notice that right before Uncompressing LInux and bboting the kernel, a message appears stating "You passed an undefined mode number." Although having low RAM compounds the issue, the main problem seems to revolve around the fact that my Winbook FX has an interchangeable CDRom and diskette bay. You can have one installed at one time, but not both. The BIOS detects which of removable media device drives is installed when it boots up. Apparently, this somehow scrambles DSL's bootup sequence.....