Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!hp9000.csc.cuhk.hk!uakari.primate.wisc.edu!ames!elroy.jpl.nasa.gov!usc!sol.ctr.columbia.edu!ira.uka.de!math.fu-berlin.de!zrz.tu-berlin.de!cs.tu-berlin.de!engel From: engel@opal.cs.tu-berlin.de (Christian Engel) Newsgroups: comp.unix.bsd Subject: 386BSD 0.1 success and tape problem Summary: error reading tapes, resid: 10240 Keywords: 386BSD, SCSI-Tape Message-ID: <1992Jul31.150311.3229@cs.tu-berlin.de> Date: 31 Jul 92 15:03:11 GMT Sender: news@cs.tu-berlin.de Organization: Techn. University of Berlin, Germany Lines: 62 Hi out there, I got the 386BSD0.1 working on my system. I have two problems. Here is the system configuration : 486/33MHz - 256KB Cache 16 MB RAM ET4000/1MB VGA card AT-IO ADAPTEC 1542B SCSI Drive 0 : 330 MB Wren SCSI Drive 1 : 660 MB Wren SCSI Tape 2 : Wangtek 5150 ES I had no problems installing the system on my harddisk(s). I built a new kernel with the lp.c driver for the printer which was contributed to the 386BSD-0.0. I attached a terminal to com1 and everything worked fine up until this point. I installed the previously posted kmem-patch (problem occurred). I can write tapes without any problems. I am even able to read these tapes. By the way there are no speed problems, writing to and reading from tape works with reasonable speed. But I run into trouble trying to read tapes from a SUN (gnu-tar) and from another 486 machine with ISC-UNIX (SysV-ISC tar). 386BSD-0.1 shows the following behaviours: 1) SUN tape: (command: tar -xvf /dev/ras2a) - tape begins to run but does not read any input. After a while the system stops with resid: 10240 error 2) ISC tape: (same command as above) - system reads about 40 MBytes from the tape. Then it stops with an error message and resid: 10240 error Has anyone out there any ideas ? Unfortunately I have no manuals for the Adaptec controller so I cannot try to fix it by myself. ::::::::::: 2nd Problem ::::::::::: When I built a new kernel, I normally try to copy it to the root directory using a name, that doesn't exist in the root directory. Sometimes the system just stops execution while copying. No message is printed. After a restart and the file system repair, you can see that a file was created but that its length is zero. Any ideas or similar problems ? -- ------------------------------------------------------------------------ Christian Engel, TU-Berlin mail: engel@cs.tu-berlin.de TFS, dept of theoretical computer science, formal specifications address: TU-Berlin, FR6-1, Franklinstr. 28/29, 1000 Berlin 10, Germany