From: Douglas Gilbert <dougg@torque.net>
To: Christian Thalinger <e9625286@student.tuwien.ac.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.19-pre9 and sym53c8xx problem
Date: Sat, 01 Jun 2002 20:34:12 -0400 [thread overview]
Message-ID: <3CF96804.D25F623B@torque.net> (raw)
Christian Thalinger wrote:
> Since 2.4.19-pre8 cdrecord does not work anymore. It worked with -pre6,
> -pre7 i've missed, don't know about this one. Maybe i'll try it after
> this mail.
>
> [root@sector17:/proc/scsi]# uname -a
> Linux sector17.home.at 2.4.19-pre9 #2 SMP Sat Jun 1 19:31:25 CEST 2002
> i686 unknown
> [root@sector17:/proc/scsi]# cdrecord -scanbus
> Cdrecord 1.11a08 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
> cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open
> SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are
> root.
Christian,
What does the output of "cat /proc/scsi/sg/*" look like?
Cdrecord should see your plextor writer both as /dev/scd0
and /dev/sg0 (assuming you don't have any other scsi devices).
Cdrecord goes on to scan the parallel generic devices (i.e. /dev/pg*)
if it doesn't find anything suitable on its /dev/sg* scan.
Your post doesn't supply any information that would link
this problem with the sym53c8xxx driver. If there is some
problem then there will be some "noise" in the /var/log/messages
file [typically showing multiple scsi bus resets].
BTW The "-vv" switch (and/or "-VV") on cdrecord will yield more
debug information. strace may also be useful.
Doug Gilbert
next reply other threads:[~2002-06-02 0:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-02 0:34 Douglas Gilbert [this message]
2002-06-02 14:21 ` linux-2.4.19-pre9 and sym53c8xx problem Christian Thalinger
-- strict thread matches above, loose matches on Subject: below --
2002-06-01 18:14 Christian Thalinger
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=3CF96804.D25F623B@torque.net \
--to=dougg@torque.net \
--cc=e9625286@student.tuwien.ac.at \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.