linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: ian reinhart geiser <geiseri@msoe.edu>
To: Simon Piette <spiette@generation.net>
Cc: LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: SANE
Date: Mon, 19 Jul 1999 11:15:24 -0500	[thread overview]
Message-ID: <37934F1C.3AC97178@msoe.edu> (raw)
In-Reply-To: 37934682.4119BEDF@generation.net


Simon Piette wrote:

> Hi,
>
> I've try to use SANE on R5. It compiles flawlessly, but I can get it to
> work. I discussed a lot with Oliver Rauch, a SANE developper (!), and we
> concluded that the problem was either with the scsi generic driver (sg),
> or with the scsi driver (53C94).
>
> I've found two other people unable to use SANE on R5, and I was
> wandering if I could find help in this group to make it work. I can
> provide you with a lot of details, and three testers!
>
> Thanks,
>
> Simon Piette

    i think the problem lies in the way the the scsi bus attaches and
reattaches
    i found that when ever i ran sane my scanner would get a few bytes and
then
    all of my scsi disks would just go into defib.  at this point i was forced
to reboot....

    -ian reinhart geiser


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-07-19 16:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-07-19 15:38 SANE Simon Piette
1999-07-19 16:15 ` ian reinhart geiser [this message]
1999-07-19 18:50 ` SANE Brad Midgley
     [not found] <199907200502.AAA26510@lists.linuxppc.org>
1999-07-20 17:08 ` SANE Brian C Burke
1999-07-21 12:39   ` SANE Simon Piette

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=37934F1C.3AC97178@msoe.edu \
    --to=geiseri@msoe.edu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=spiette@generation.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).