From owner-freebsd-stable  Sat Sep 20 10:26:29 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA16955
          for stable-outgoing; Sat, 20 Sep 1997 10:26:29 -0700 (PDT)
Received: from cabri.obs-besancon.fr (cabri.obs-besancon.fr [193.52.184.3])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA16950
          for <freebsd-stable@freebsd.org>; Sat, 20 Sep 1997 10:26:22 -0700 (PDT)
Received: by cabri.obs-besancon.fr (5.57/Ultrix3.0-C)
	id AA21491; Sat, 20 Sep 97 19:27:19 +0100
Date: Sat, 20 Sep 97 19:27:19 +0100
Message-Id: <9709201827.AA21491@cabri.obs-besancon.fr>
From: Jean-Marc Zucconi <jmz@cabri.obs-besancon.fr>
To: cracauer@cons.org
Cc: joerg_wunsch@uriah.heep.sax.de, cracauer@cons.org,
        freebsd-stable@freebsd.org
In-Reply-To: <19970920163121.26878@cons.org> (message from Martin Cracauer on
	Sat, 20 Sep 1997 16:31:21 +0200)
Subject: Re: 2.2-stable problems
X-Mailer: Emacs
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>>>>> Martin Cracauer writes:

 > In <19970920132312.OX18440@uriah.heep.sax.de>, J Wunsch wrote: 
 >> As Martin Cracauer wrote:
 >> 
 >> > Folks, [CC: to Joerg as wormcontrol meister]
 >> > 
 >> > updating a 2.2.2 machine to 2.2-stable last week, I have two problems:
 >> > 
 >> > 1) 'wormcontrol fixate' always fails with
 >> >   wormcontrol: ioctl(WORMIOFIXATION): Invalid argument
 >> > 
 >> > The burner (Plasmon RF4100 1.26) worked without problems under 2.2.2.
 >> 
 >> I've also noticed this last week after an upgrade.  I've already told
 >> Jean-Marc about it, but didn't investigate yet.
 >> 
 >> Manual fixation worked around the problem for me...

 > Manual?

 > I thought the ioctl(fd, WORMIOCFIXATION, &f) (used in wormcontrol.c) is
 > the only interface we have to the burner and that apparently got out
 > of sync with the kernel. 

Try	scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0"

if this does not work, then try
	scsi -f /dev/rworm0.ctl -s 3600 -c "35 0 0 0 0 0 0 0 0 0"
followed by
	scsi -f /dev/rworm0.ctl -s 3600 -c "e9 0 0 0 0 0 0 0 1 0"

 > What other way to go? I think a friend of mine has some old
 > Roentgenlaser, built after a famous old german book. Which track do I
 > need to shoot at? I think that beast can burn holes in steel, should
 > be sufficient :-]

 > BTW, as expected booting a 2.2.2-kernel on a 2.2-stable world made
 > wormcontrol work again.

So this means that the the bug is in wormcontrol rather than in the
driver ??

Jean-Marc
 _____________________________________________________________________________
 Jean-Marc Zucconi       Observatoire de Besancon       F 25010 Besancon cedex
                   PGP Key: finger jmz@cabri.obs-besancon.fr