mju@mudos.ann-arbor.mi.us (Marc Unangst) (08/16/90)
I recently upgraded from MINIX 1.2 to 1.5.10, and I'm really impressed with the difference. Screen scrolling is MUCH faster; I used to use 'cat' to look at files and just use ^S and ^Q, but now I have to use 'more' because the stuff scrolls past too fast to react! Unfortunately, I'm having a few small problems with 1.5.10. I'm running on a Zenith Z-148 with 640K, a V20 processor, and the COM1 8250 replaced with a NS16550AN. There are two hard disks and two hard disk controllers on the system -- a 20MB MFM ST-225 with a WD XT-GEN controller, and a 60MB RLL M3675 with a WD 1004-27X controller. The 20MB disk is drive 0, with the controller BIOS at C8000 and IRQ 2. The 60MB disk is drive 1, with the controller BIOS at CA000 and IRQ 5. Here are the problems: 1. The MINIX xt_wini.c driver doesn't like the fact that I have two controllers. If I link the kernel with max-drives (I forget what the real name is) set to 2, neither drive works -- I can read and write to/from /dev/hd0, but hd[1-10] don't work at all. Even though I have valid MINIX partitions on /dev/hd2 and /dev/hd3, mount(1) fails with an "invalid filesystem" message. By changing max-drives to 1, I can get things to work okay, but naturally, /dev/hd[5-10] don't work. The 60MB drive is all MS-DOS, so it's not a big problem, but it would be nice to be able to dosread(1) from it instead of having to transfer stuff from floppies. (Note: bios_wini.c doesn't work at all; when I boot up, I get an "unexpected interrupt or trap >17" message and have to reboot.) 2. On a related note, fdisk(1) doesn't work. Even when I set max-drives to 1, when it comes up it tells me that the size info for partitions 2 and 3 is incorrect, and to try again with -h6 and -s17. I *know* this is wrong, because the ST-225 has 4 heads. However, the M3675 has 6 heads...It looks like fdisk(1) is getting its info from the wrong place. 3. I can't get the serial port driver to work. I have a terminal hardwired to /dev/tty1, with DCD and DTR forced high all the time. My /etc/ttys reads like this: 200 2f1 Although a getty is spawned for /dev/tty1, it never presents a login: prompt or anything. I then tried editing /etc/ttys: change the "2" to a "0" for that line, 'kill -1 1', 'kill -9 <getty-proc>', and then tried running kermit on that line. It connects to the line okay, and things I type at the console appear on the terminal, but anything I type at the terminal never shows up on the computer screen. I've hooked a breakout box into the line and the signals ARE getting sent over the serial line; thus, I'd guess it's a problem with MINIX. I've tried both the assembler serial port handlers and the C serial port handles; neither one works. 4. Again, a related problem: modem(1) doesn't work properly. If I do 'modem -o tty1' with a getty running for that line, the getty is never killed, init is never told anything, and nothing gets sent to /dev/tty1. If I do 'modem -i 1 tty1' without a getty running for that line, the same thing happens (getty is never spawned, init is never told about this, and nothing is sent over the serial line). Is there something really simple that I'm missing here? Everybody else seems to have this working properly... -- Marc Unangst | mju@mudos.ann-arbor.mi.us | Angular momentum makes the world go 'round. ...!umich!leebai!mudos!mju |
RX80266%INDYLLY.BITNET@uicvm.uic.edu (08/21/90)
HI, COULD YOU KIND ENOUGH TO PROVIDE ME INFORMATION ON HOW TO UPGRADE FROM 1.2 TO 1.5 PLEASE. THANKS MUCH. From: CHAN GING (MCVAX0::RX80266) To: FOREIGN TRANSPORT ADDRESSEE (MCDEV1::IN%"INFO-MINIX%UDEL.EDU@VM1.NoDak.E DU")