Installation attempt, slinky-0.5.02 [Was Re: [RULE] slinky-0.5.02 for Fedora Core 4 FC4]

[Franz Zahaurek]

Hi C David,

Thank you very much for your exact test-report.  Thou I cannot
actually reproduce your testcase here, I hope I could find the error
due to your very precice report.
This is an advice how you can fix it yourself very easy. I hope it will work.

C David Rigby  cdrigby 9online fr  writes:

> Results of my installtion attempt are shown below. Any help
> appreciated.  CDR
> [...]

> _Installing FC4 on numberfive using slinky-0.5.02_
>
> Numberfive is a Compaq Presario 1625 portable (AMD K6-233, 64MB RAM)
> which lacks such things as a working CD-ROM drive and battery. This
> makes it a good candidate for a RULE rescue. Possibly it is usable as
> a light-duty server.
>
> 1. I created the slinky-0.5.02-disk1.img and created another diskette
> with an ext2 filesystem to hold selected modules from
> [...]

If you can manage to do this, that's half the way.

>
> 2. I booted from the slinky-0.5.02-disk1 disk.
>
> 3. Once I got the "Welcome to 'Slinky' the RULE low memory installer"
> splash screen, I switched to the second console (CTL-ALT-F2) and
> issued the following commands to access the external SCSI CD-ROM drive:

If you use another keyboard than us, you could select this first.

>
> A. After placing my second floppy in the drive, I issued the command
> "mount /dev/fd0 /mnt/floppy"

If you mount the floppy at /lib/modules you don't need to cd and
module dependencies should be resolved automatically.

>
> B. I changed to the directory where the pcmcia drivers are stored and
> issued "insmod rsrc_nonstatic.ko"
>
> C. Then I issued "insmod yenta_socket.ko." I got messages indicating
> that the card socket was detected by the driver.
>
> D. Then I changed to the directory where the pcmcia scsi drivers are
> located and entered "insmod aha152x_cs.ko"
>
> E. This was followed by "insmod sd_mod.ko," "insmod sr_mod.ko" and for
> good measure "insmod sg.ko" (I really doubt I need that last one).
>
> F. I then changed directory to /sbin and ran "cardmgr." I received
> messages indicating that the CD-ROM drive was found and correctly
> identified.
>
> G. To test, I issued the command "mount /dev/scd0 /mnt/cdrom" which
> appraently tried all possible file system types (since I didn't
> specify one) until it hit on iso and mounted the CD. I confirmed this
> by issuing "ls /mnt/cdrom" and I could see the top level directory of
> the CD.

That shows, that you successfully loaded all necessary modules.

>
> H. I issued the command "umount /mnt/cdrom" to free the mount point.
>
> I. I created a symlink between /dev/scd0 and /dev/cdrom by issuing the
> command "ln -s /dev/scd0 /dev/cdrom."
>
> J. I returned to the slinky session on the first console.
>
> 4. I worked through the messages, and I went back to the second
> console to umount my modules floppy when I saw the "you can remove
> your boot floppy..." message.

May be you should first get to here and afterwards load the modules. But
I think that's not important.

>
> 5. I skipped the keyboard configuration on the next screen, then
> tabbed down to item #2: Select_the_distribution_to_install and pressed
> ENTER.
>
> 6. On the next screen I chose Item #1: FC4.
>
> 7. I got the message confirming the selection and advising that the
> first FC4 CD would be necessary.

For minimal installation only the lilo-rpm is not located on the first disk.
But that's not the only reason to use GRUB.

>
> 8. Returned to the selection screen and Item #3:
> Select_your_installation_method was the default, so I pressed ENTER.
>
> 9. On the Choose Installation method screen, Item #1: cdrom was
> highlighted, so I just pressed ENTER.
>
> 10. I got the message "I wasn't able to locate your cdrom drive..." 

That's because it is no ATAPI-CD (/dev/hdc for example).

> Per that message, which indicates that I should only use the "cdrom"
> entry if I have a link that points from /dev/cdrom to my CD-drive's
> actual device, I typed in "cdrom" and pressed ENTER.

See the script: "/scripts/select_method.sh" where this is performed.
You find it when you switch to the second virtual console.

>
> 11. I got a message that said, in full, "I will try to use <cdrom> as
> your cd drive. You will have the opportunity to change this later in
> the install, if need be. "OK" is highlighted at the bottom of the
> message window.
>
> 12. I pressed ENTER (repeatedly) but the installer never left that window.

It seems to be exactly what you describe: an endless loop - sorry.
Look at line 478 of select_method.sh, it reads as:

    echo CDROM_DEV=$CDROM_DEV >> $install_log
    ;;

Add the following line:

    echo CDROM_DEV=$CDROM_DEV >> $install_log
    have_device=1                     <<<<==== add this line
    ;;

Store the file and now the script should continue - I hope.

But you could skip this step at all (use cursor down to select the
next step) as you were able to mount the installation cdrom yourself.
(Don't unmount it when you got it working.)

>
> Any suggestions?

I hope you get further with these hints.

- Franz
-- 
Franz Zahaurek                        fzk at fzk.at
Gymnasiumstr. 26/7                    http://www.fzk.at
1180 Wien

_______________________________________________
Rule Project HOME PAGE:  http://www.rule-project.org/en/
Rule-list at rule-project.org
http://mail.rule-project.org/mailman/listinfo/rule-list_rule-project.org