Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!spool.mu.edu!hri.com!ukma!risner From: risner@ms.uky.edu (James Risner) Newsgroups: comp.unix.bsd Subject: Unable to get 0.1 to boot on machine running 0.0, any clues? Keywords: 0.1 Unable help Message-ID: <1992Jul20.161040.29819@ms.uky.edu> Date: 20 Jul 92 20:10:40 GMT Article-I.D.: ms.1992Jul20.161040.29819 Organization: University Of Kentucky, Dept. of Math Sciences Lines: 149 I have been unable to get 0.1 running on the HD after two days of trying. A list of problems and how I overcame the problems is below. The final problem for which I can not come up with a method of overcoming is also listed. I anyone has any clues or wishes me to try anything to determine the reasons I am game... Setup: 486-33 AMI kb bios and main bios. All caching and shadowing truned on. 32 meg of ram (60 ns) CGA card with printer interface (378) With or without a 2 serial port card (com1 = normal, com2 = fifo) One 1.44 floppy drive. 2 IDE HDs. Conner 170mb IDE (903c,8h,46s) Seagate (Slave) IDE (1001c, 15h, 17s) Original Setup: Conner partitions = 1 meg dos, 1 meg OS/2 Boot Manager, 160 meg 386bsd Seagate = 74 meg FAT, 50 meg HPFS (OS/2 disk) 0.0 Works on this machine. 0.1 Boot messages: 386NSD Release 0.1 by William and Lynne Jolitz. [0.1.24 07/14/92 19:07] .... .... .... pc0<color> at 0x60 irq 1 on isa wd0 <Conner Peripherals 170MB - CP30174E> at 0x1f0 irq 14 on isa fd0 drives 0: 1.44M at 0x3f0 irq6 drq 2 on isa npx0 at 0xf0 irq 13 on isa changing root device to fd0a ... ... ... # (prompt) Now originally when running install with: 1) 1 meg OS/2 boot manage, 1 meg dos, NO OTHER partitions assigned 160free 2) 1 meg OS/2 boot manage, 1 meg dos, 160 meg EXTENDED DOS partition # install It appears that 386BSD has already been installed. Reinstall? no response issues # prompt. Yes = "install on ENTIRE disk message" no to ENTIRE disk issues a # prompt again. Yes = warning... At this point I did not really want to lose my boot manager since I would need to reinstall Os/2 to get one again... but I decided to delete the entire DISK by repartitioning it as one large DOS partition and running nortons Speedisk to "clear unused space", then ran OS/2 install to put back the 1 meg dos and 1 meg boot manager partitions. Now this time it did not say it reconized 386bsd on the disk but skipped the first question and went on to the next with the same responses as above. Ie the only way to get anywhere is to say YES to the ENTIRE disk question. I wanted to avoid this so I ran fdisk and made a 160 meg EXTENDED dos partition and ran diskedit to changed the partition type from 05 (ext DOS) to A5 for 386bsd partition. Now I WAS GETTING SOMEWHERE... It reconized the 386bsd partititon and said "install on 386bsd partition?" Yes! Went on to install... Messages: High Level formatting of 386bsd partition(?) /dev/rwd0a: x sectors in x cyc of 8 tracks 46 sectors 162.x MB in 5x cyl groups ( x c/g, x/g x i/g) super-block backups: 32, 5968... 53072... 106112... 159152... 212192... 265232... 318272, Mounting 386BSD filesystem. Installing files from installation floppy. HANG no error messages no nada... All disk access hangs (ctrl - z work correctly) Ctrl-c issues pages of the messages just before the first prompt is printed until it finally calms down and gives you a prompt which you can use Everything about is from memory but I am sure it only differs, from what I am getting now using the ENTIRE disk option, only by the numbers listed. Using ENTIRE DISK: High Level formatting of disk storage: /dev/rwd0a: 873 cylinders of 8 tracks, 46 sectors 164.5 MB in 55 cyl groups ( 16 c/g, 3.01MB/g, 704 i/g) super-block backups: 32, 5968... 53072... 106112... 159152... 212192... 265232... 318272, Mounting 386BSD filesystem. Installing files from installation floppy. One thing as a side note, the drive had 903 cylcs so why would it say 873? Are 874-903 used as swap? Anyway... I try doing it by had: Boot tiny 386bsd newfs /dev/rwd0a (similar if not same info as above) mount /dev/wd0a /mnt cp files into /mnt no problems, then try mkdir /mnt/bin mkdir either 1) hangs forevery with no ctrl-z,\,c to stop or 2) works perfectly. When mkdir hangs its all over = reboot when mkdir works then next file copied to /mnt panics machine. With: mode=0100664, inum=4, fs=/mnt panic: ialloc: duip alloc Updating disks... "Saving RAM to device 1, offset 0" ... "area improper"... instant reboot Something about prompting for input but it never waits for prompting just reboots. Anyway if you try the install exec method it hangs with the cpio of basefiles.Z when it gets done with all the files in / on tiny386bsd. Ie when It gets to a dir it hangs. Now if you leave install running in the bg and it hangs, then if YOU at the prompt type ls /mnt or ANYTHING to do with /mnt you HANG with no escape by ctrl-z,c,\ My final problem comes down to mkdir it does not seem to work on my hardware. I am unsure if it is a kernel problem or mkdir problem since I can not load 386bsd to look around. Any help suggestions or tips would be greatly appeciated, and a case of beer shipped to the man who comes up with the solution... Shipping anywhere in the USA... Risner