From owner-freebsd-hackers Thu May 29 13:24:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA07170 for hackers-outgoing; Thu, 29 May 1997 13:24:48 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA07165 for ; Thu, 29 May 1997 13:24:41 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA16596; Thu, 29 May 1997 22:24:33 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA05089; Thu, 29 May 1997 22:16:35 +0200 (MET DST) Message-ID: <19970529221635.NB25349@uriah.heep.sax.de> Date: Thu, 29 May 1997 22:16:35 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: hackers@FreeBSD.ORG Cc: tom@tomqnx.com (Tom Torrance at home) Subject: Re: HP 6020 Problems References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Tom Torrance at home on May 29, 1997 03:05:24 -0400 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Tom Torrance at home wrote: > Jordon's original announcement for Release 2.2.1 stated that the HP 6020 > was supported, so I went and bought one. Hmm, the 6020i actually -- i didn't even know there's a difference. > THis is a REALLY crude hack, but it works well enough to allow me to > fulfill my objective. I offer it here only so that someone who really > knows what they are doing can use the information I have gathered to > implement the necessary support properly. Driver code is far beyond me. I wonder what the second hack is for? > Note that when running the 'burncd' script, the dd command fails at the > end of the copy, How? What? Which? Any SCSI messages? What errno? > Although I got 'burncd' to function for me, more or less, attempting to > execute 'cd-write 1.2' to master a CD locks up the entire systemi, > after the initializing disk info message. cd-write is a totally different beast. It only uses the driver as a loophole in order to do the complete SCSI handling of its own. As such, it offers the ability for a lot more new bugs :). I think that's something where you should contact Jean-Marc directly in order to find and fix the bug. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)