home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!morrow.stanford.edu!morrow!aoki
- From: aoki@risk.stanford.edu (ikuro aoki)
- Newsgroups: comp.unix.bsd
- Subject: Re: 386bsd installation problem for an EISA machine. (continue)
- Date: 26 Dec 92 02:51:54
- Organization: Stanford University, Stanford, CA, USA.
- Lines: 89
- Distribution: comp
- Message-ID: <AOKI.92Dec26025154@risk.Stanford.EDU>
- References: <AOKI.92Dec24024946@risk.Stanford.EDU>
- <AOKI.92Dec24193843@risk.Stanford.EDU>
- NNTP-Posting-Host: risk.stanford.edu
- In-reply-to: aoki@risk.stanford.edu's message of 24 Dec 92 19:38:43
-
- Hello net,
-
- I've just got my Adaptec 1742A controller + SCSI HDD worked.
- For other 1742 users, I report what I did.
-
- As I reported the official boot binary doesn't work for Adaptec
- 1742A SCSI controller even it is in the aha1542 compatible mode
- (Standard mode.) This EISA adapter needs another boot binary.
-
- I got them from ref.tfs.com [140.145.254.251] /usr/bootdisks.
- Because the binaries in this machine/directory are not officially
- released, there is no documents for them in the directory.
-
- I ftp'ed the following items,
- 1)-rw-rw-r-- 1 root 1228800 Nov 22 15:09 dist.fs.aha1742-only
- 2)-rw-r--r-- 1 root 1225728 Dec 3 16:33 fixit.1742a.fs
- 3)-rw-rw-r-- 1 root 1228800 Nov 22 14:36 fixit.fs.aha1742-only
-
- Only 2) could work for my 1742A board (BIOS version 1.34).
-
- Because the fixit binary doesn't have some information which is
- needed for an installation, I used 1) and 3) binary.
-
- I made a tiny 386bsd floppy from 1) and fixit floppy from 2).
- Boot from the fixit, and disklabel'ed a hard disk,
-
- disklabel -r -w as0 mk156 scsi /usr/mdec/sdboot /usr/mdec/bootsd
-
- The mk156 disktype was NOT suitable for my hard disk (Micropolice
- 2112-15 1.05Gbyte). However, if tried to edit /etc/disktab file, the
- system easily panic'ed. I also newfs'ed and fsck'ed the disk,
-
- newfs /dev/ras0a
- fsck /dev/ras0a
-
- After making a file system, I mounted the filesystem under the fixit,
-
- mount /dev/as0a /mnt
-
- made each directories, copied all files in the fixit to the new disk.
- Owing to the 'cp' command doesn't understand, I had to copy all the
- file one by one, like 'cp /usr/distbin/cat /mnt/usr/distbin/cat'.
-
- And I made an empty directory /work under /mnt, then attached the
- dist.fs, copied the contents to appropriate directories
- (one by one manually, again).
-
- Because the 'cp' doesn't have '-p' option, all copied file became
- 644 mode(depending on umask). For this reason, I had to extract
- 'chmod' from the dist.fs:/etc/distutil.cpio.Z.
-
- The fixit floppy doesn't have cpio and uncompress, and the copied
- binaries which are in the HD also don't work bicause of the mode 666.
- By using /mnt/work/usr/bin/coio and /mnt/work/usr/bin/uncompress,
- I extracted /etc/baseutils.cpio.Z under /mnt (=HD's root) directory.
-
- cp /mnt/etc/baseutils.cpio.Z /mnt/baseutils.cpio.Z
- uncompress /mnt/baseutils.cpio.Z
- cd /mnt
- cpio -idv < baseutils.cpio
-
- Note: 'zcat baseutils.cpio.Z | cpio -id' crashed my system.
-
- After getting 'chmod', I changed the mode of all executable binaries
- as it should be. /sbin/init must be executable.
-
- Sync
- /mnt/usr/distbin/umount /mnt/work
- /mnt/usr/distbin/umount /mnt
- shutdown
-
- remove both floppy disks, and, it booted from the HD.
-
- After this work,
- I mounted the fixit floppy again,
- edit /etc/disktab of the fixit,
- copy 'chmod' to the fixit,
- boot form the new fixit,
- did over the above work.
-
- Now my system is working fine with an Adaptek 1742A controller.
- I appreciate all who gave me information. Any comments will be
- welcome.
- --
- Ikuro Aoki
- aoki@risk.Stanford.EDU
-
-
-
-