bunda@cs.utexas.edu (John Bunda) (06/22/88)
I thought I finally had it. I changed the AUT O_BIOS in xt_wini.c, and put in the com_out replacement from the archives, made the kernel, and booted. "h" seemed to initialize things ok, though it did report bad superblock..., which I guess is expected. Anyhow, once up and running, the dd if=/dev/hd0.... test ran to completion, my hard disk merrily whirring away, dumping its 1000 blocks to /dev/null. I then backed up the disk, reformatted (low-level with the WD BIOS formatter using debug), and used DOS (3.3 by the way) FDISK to partition the drive. I created a DOS partition and another "extended DOS partition" for Minix. I formatted C:, restored my DOS system to its partition, and it works great (don't forget to activate the primary partition, or it won't boot). I then brs'd and booted Minix. fsck of either hard partition from the boot menu gives "bad superblock, fatal", again, I guess expected since mkfs hasn't been done yet. The light on the drive winks though, so I do know it's awake. Put in the root diskette and "=", the ram disk begins loading, meanwhile the hard drive begins what sounds like a major seek. The whole show then comes to a screeching halt with the message "kernel panic - can't read partition table on drive 0" I tried making the minix partition a virtual drive for DOS (D:), then high-level formatted. Waste of time, no effect whatsoever. Any coaching would be welcome.... thanks john -- ................................................................ John Bunda UT CS Dept. The proof is trivial, and bunda@cs.utexas.edu Austin, Texas left as an exercise.
jds@mimsy.UUCP (James da Silva) (06/23/88)
In article <2900@cs.utexas.edu> bunda@cs.utexas.edu (John Bunda) writes: | |I then backed up the disk, reformatted (low-level with the WD |BIOS formatter using debug), and used DOS (3.3 by the way) FDISK to ^^^ |partition the drive. I created a DOS partition and another |"extended DOS partition" for Minix. ^^^^^^^^^^^^^^^^^^^^^^^ ... | |Put in the root diskette and "=", the ram disk begins loading, meanwhile |the hard drive begins what sounds like a major seek. The whole show |then comes to a screeching halt with the message "kernel panic - can't |read partition table on drive 0" | Just a guess here, but I believe that DOS 3.3's "extended" partition hack puts some incompatible cruft in the partition table that Minix's disk driver doesn't understand. Try repartitioning the disk using something other than DOS 3.3. - Jaime ---------------------------------------------------------------------- usenet: uunet!mimsy!jds James da Silva internet: jds@mimsy.umd.edu "Stand on each other's shoulders, not on each other's toes."
bunda@ebirah.cs.utexas.edu (John Bunda) (06/28/88)
I'm finally running Minix on my Seagate-ST225/Western Digital WX-1. Thanks for the tip about DOS 3.3, which you cannot use to partition the disk. My procedure was as follows: fix that AUT O_BIOS typo in xt_wini.c, and use the fix from the archives as described in the information sheet. Rebuild the kernel, and build a boot diskette. Then, (after backup), I low-level formatted using the command g=c800:5 in debug. My kernel was patched by fixing the AUT O_BIOS typo and the fix described on the information sheet. I booted my patched kernel, then partitioned the disk using fdisk from /user/bin, which works great. Note to the unwary: DOS 3.3 FDISK will *not* work! I tried DOS 2.1 FDISK without results either. I also tried to use the edpart.exe from the archives, but I was not able to get one that would work, presumably due to local transmission problems. Anyway, the newly partitioned disk works fine with minix. Some words of warning if you want to let DOS 3.3 use the disk: When I booted 3.3 from the floppy, it wouldn't recognize the hard drive. Using FDISK munches the partition table, and you're back to square one. I booted DOS 2.1, which *did* recognize the drive, and did a high-level format, which worked (rebooting minix and doing checks of the hard disk partitions revealed no problems). after the 2.1 format, I booted 3.3, which now seemed to like the partition. I restored my DOS stuff, and everything works, at least for now... john