kopia lustrzana https://gitlab.com/sane-project/website
112 wiersze
5.4 KiB
HTML
112 wiersze
5.4 KiB
HTML
<!-- received="Tue Jun 22 17:24:37 1999 PDT" -->
|
|
<!-- sent="Wed, 23 Jun 1999 02:22:26 GMT" -->
|
|
<!-- name="Meino Christian Cramer" -->
|
|
<!-- email="root@solfire.ludwigsburg.netsurf.de" -->
|
|
<!-- subject="Re: SCSI-bus confusing with AVISION AV630CS/TEKRAM DC390F" -->
|
|
<!-- id="19990623022226Z.root@solfire.ludwigsburg.netsurf.de" -->
|
|
<!-- inreplyto="Pine.LNX.4.10.9906222124040.16312-100000@chef.ecs.soton.ac.uk" -->
|
|
<title>sane-devel: Re: SCSI-bus confusing with AVISION AV630CS/TEKRAM DC390F</title>
|
|
<h1>Re: SCSI-bus confusing with AVISION AV630CS/TEKRAM DC390F</h1>
|
|
<b>Meino Christian Cramer</b> (<a href="mailto:root@solfire.ludwigsburg.netsurf.de"><i>root@solfire.ludwigsburg.netsurf.de</i></a>)<br>
|
|
<i>Wed, 23 Jun 1999 02:22:26 GMT</i>
|
|
<p>
|
|
<ul>
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#149">[ date ]</a><a href="index.html#149">[ thread ]</a><a href="subject.html#149">[ subject ]</a><a href="author.html#149">[ author ]</a>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0150.html">Simon Piette: "Re: Umax 1200S on LinuxPPC R5"</a>
|
|
<li> <b>Previous message:</b> <a href="0148.html">Nick Lamb: "Re: Umax 1200S on LinuxPPC R5"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|
|
<!-- body="start" -->
|
|
From: Nick Lamb <<a href="mailto:njl98r@ecs.soton.ac.uk">njl98r@ecs.soton.ac.uk</a>><br>
|
|
Subject: Re: SCSI-bus confusing with AVISION AV630CS/TEKRAM DC390F<br>
|
|
Date: Tue, 22 Jun 1999 21:29:18 +0100 (GMT)<br>
|
|
Message-ID: <<a href="mailto:Pine.LNX.4.10.9906222124040.16312-100000@chef.ecs.soton.ac.uk">Pine.LNX.4.10.9906222124040.16312-100000@chef.ecs.soton.ac.uk</a>><br>
|
|
<p>
|
|
Hi Nick!<br>
|
|
<p>
|
|
Thank you for your fast reply ! :-)<br>
|
|
<p>
|
|
<i>> On Tue, 22 Jun 1999, Meino Christian Cramer wrote:</i><br>
|
|
<i>> </i><br>
|
|
<i>> > Does anyone out there knows about some things I could try</i><br>
|
|
<i>> > to avoid those dead-scans?</i><br>
|
|
<i>> </i><br>
|
|
<i>> Well, to at least avoid killing the Linux box you should check out</i><br>
|
|
<i>> </i><br>
|
|
<i>> (1) SCSI may become happy again if you turn off the scanner when it hangs</i><br>
|
|
<br>
|
|
Unfortunately it does not. I unplugged the scanner ... nothing.<br>
|
|
I tried to leave X ... the screen blanks (the X-server end) but<br>
|
|
I received a black screen, cause any access to the disk was blocked. <br>
|
|
I tried to shutdown the "official" way ... no chance: the "shutdown"-<br>
|
|
programm could not be loaded: disk blcoked. SySREQs also does not work.<br>
|
|
Hardreset recalls the box ittself -- but the disk remains blocked so<br>
|
|
the BIOS reports "disk access failure". Only after physically cycle power,<br>
|
|
the block was ended -- sigh.<br>
|
|
<br>
|
|
<p>
|
|
<i>> You will see a lot of screaming from the kernel "Where did that go????"</i><br>
|
|
<i>> but then it should settle down and you can reboot safely</i><br>
|
|
<i>> </i><br>
|
|
<i>> (2) Magic SysRq is your friend, in 2.2.x at least you can configure the</i><br>
|
|
<i>> Alt+SysRq sequence on and have a keypress which syncs and reboots to</i><br>
|
|
<i>> avoid file corruption. Check out the appropriate kernel files.</i><br>
|
|
<p>
|
|
Yes, it is activated since -- I don't know. But it was inaccessible after<br>
|
|
the scsi-block. See above.<br>
|
|
<p>
|
|
<i>> </i><br>
|
|
<i>> AFAIK the SCSI mid-layer of Linux is unhelpful about reporting errors</i><br>
|
|
<i>> such as "You sent too much/ not enough/ wrong kind of data" to upper</i><br>
|
|
<i>> layers such as SCSI generic. Tinkering with mid-layer endangers SCSI</i><br>
|
|
<i>> disks, tape backups etc. and only benefits SCSI generic users. So it</i><br>
|
|
<i>> won't happen for a while yet.</i><br>
|
|
<p>
|
|
Do you have any hint,or trick, what I have to chance in the backend?<br>
|
|
What do I have done wrong there? In short: I done a INQUIRY, then<br>
|
|
SET-WINDOW, START-SCAN and a READ-loop, which does not loop, cause<br>
|
|
the block happens then.....<br>
|
|
<p>
|
|
<p>
|
|
<i>> Nick.</i><br>
|
|
<i>> </i><br>
|
|
<i>> </i><br>
|
|
<i>> --</i><br>
|
|
<i>> Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a></i><br>
|
|
<i>> To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a></i><br>
|
|
<i>> </i><br>
|
|
<p>
|
|
Thank you very much in advance!<br>
|
|
<p>
|
|
KEEP HACKING!<br>
|
|
Meino<br>
|
|
<p>
|
|
<p>
|
|
---------------------------------------------<br>
|
|
*** YOU CAN STILL GET OUT OF THE MATRIX! ***<br>
|
|
*** USE LINUX! ***<br>
|
|
---------------------------------------------<br>
|
|
<p>
|
|
--------------------------------------------------------------------------<br>
|
|
Anyone sending unwanted advertising e-mail to this address will be charged<br>
|
|
$25 for network traffic and computing time. By extracting my address from<br>
|
|
this message or its header, you agree to these terms.<br>
|
|
--------------------------------------------------------------------------<br>
|
|
<p>
|
|
<pre>
|
|
--
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|
</pre>
|
|
<!-- body="end" -->
|
|
<p>
|
|
<ul>
|
|
<!-- next="start" -->
|
|
<li> <b>Next message:</b> <a href="0150.html">Simon Piette: "Re: Umax 1200S on LinuxPPC R5"</a>
|
|
<li> <b>Previous message:</b> <a href="0148.html">Nick Lamb: "Re: Umax 1200S on LinuxPPC R5"</a>
|
|
<!-- nextthread="start" -->
|
|
<!-- reply="end" -->
|
|
</ul>
|