Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA7282 ; Mon, 18 Jan 93 10:51:06 EST Xref: sserve comp.org.eff.talk:11775 comp.unix.bsd:10202 comp.unix.wizards:28279 comp.org.usenix:3145 Newsgroups: comp.org.eff.talk,comp.unix.bsd,comp.unix.wizards,comp.org.usenix Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!yale.edu!qt.cs.utexas.edu!cs.utexas.edu!torn!watserv2.uwaterloo.ca!watserv1!swong From: swong@watserv1.uwaterloo.ca (Stanley Wong) Subject: Misc problems Message-ID: <C14zIy.2I5@watserv1.uwaterloo.ca> Organization: University of Waterloo References: <BZS.93Jan16205935@world.std.com> <1jdibnINN52u@usenet.pa.dec.com> <1993Jan19.224307.22194@prl.dec.com> Date: Wed, 20 Jan 1993 05:06:33 GMT Lines: 83 I have been using 386BSD for two months now, and I have some problems/questions that I would like to resolve. I am using 0.1 patch level 58 minus 47 (I think thats the one not recommended and various patches posted to the net). 1) I am having some problems with my ESDI disk. I have a Western Digital controller WD1007 and a Maxtor XT8380E 330 meg drive. My problems are with bad blocks. Firstly when I installed, I got a default partition setup for me that I don't really want, but I can live with it until the Future Domain SCSI driver is released. Anyways it got disklabeled without the sf param and I get a bunch of read errors at various points. Here is my disklabel: # /dev/rwd0d: type: ESDI disk: label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 16 sectors/cylinder: 1008 cylinders: 672 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 3 partitions: # size offset fstype [fsize bsize cpg] a: 665280 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 659) b: 10000 665868 swap # (Cyl. 660*- 670*) c: 676368 0 unused 0 0 # (Cyl. 0 - 670) By doing a bad144 wd0 I get this: bad block information at sector 677313 in /dev//rwd0d: cartridge serial number: 0(10) sn=0, cn=0, tn=0, sn=0 sn=20163, cn=20, tn=0, sn=3 sn=81360, cn=80, tn=11, sn=27 sn=81409, cn=80, tn=12, sn=13 sn=661856, cn=656, tn=9, sn=41 This information is on the 672nd cylinder, but doesn't seem addressable. When I put a badsect flag in, I reboot I get a hard read error at 677313 677315 677317 677319 and 677321. My question is, is cylinder 672 being used by the drive itself (not BSD) to hold bad blocks? So should the BSD bad block info be at cylinder 671? How can I get bad144 working for me so that I don't get anymore read errors? Furthermore does BSD require the d partition? 2) I have also been using the interuptless lpt driver thats been floating around. It works fine for plain text. I have a laserjet 3p. When I print TeX files, I get a page about every 2 mins. When, I use ghostscript, convert it to ljet3 and then print, I get a page every 4 mins. This seems long. Is this what everybody else is getting? My ljet3p has 3 megs ram. Also, I converted a postscript file to ljet3 and got a file that was 1.7 meg. I tried to lpr this, and it only sent out 1 meg, saying the file was too big. 1 meg was only 12 pages! How come? 3) Desparately seeking SCSI drivers for Future Domain TMC1680 controller. 4) I am using XBSD8514 server for XFree on a Ultra Plus 2 meg. Is anyone doing a mach32 driver? 5) What is the status with gcc2.3.3. I have been confused with all the patches posted to the net and the ones on ref. What patches are required so that the kernal et all can be recompiled with the bin package up on ref? 6) I still get blinking blue instead of highlight as mentioned in faq #50. Apparently about register 2 is setup correctly. I have an ATI Ultra Plus. There are no dips on this card. How can I get rid of this. When I boot up its ok, but once I dial out with tip to a sun, flashing blue comes instead of highlight. It then stays that way until I reboot. Xterm does not exhibit this. Any insight into these problems/questions appreciated. stan swong@watserv1.uwaterloo.ca