From: "Felipe Alfaro Solana" <felipe_alfaro@msn.com>
To: dgilbert@interlog.com
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: cdrecord, IDE-SCSI and 2.5.39
Date: Mon, 30 Sep 2002 17:55:55 +0200 [thread overview]
Message-ID: <F758Ts6DdVjkfQWswop000122ba@hotmail.com> (raw)
Hello,
I have found that cdrecord 1.11a34 has stopped working on linux kernel
2.5.38+. I have a SONY CRX185E3 ATAPI burner and it works fine on 2.4.19
using "hdd=ide-scsi" kernel parameter, but with kernel 2.5.38+, cdrecord
fails when trying to access the "/dev/pg*" device files. When I run cdrecord
-scanbus, it complains with:
cdrecord: No such file or directory. Cannot open '/dev/pg*'. Cannot open
SCSI driver.
I'm logged on as root. SCSI support is enabled as loadable modules (both the
IDE-SCSI and SCSI generic support), as well as IDE CD-ROM. The "sg.o",
"ide-scsi.o" and "scsi_mod.o" modules are loaded and I have used the
"hdd=ide-scsi" kernel parameter. Also, on /var/log/messages, an entry
reports problem locating char-major-97. I have a QDI Platinix P4 Motherboard
with Intel 845 chipset.
Is this a known issue? Also, when running 2.5.38+, why is my computer's box
IDE led activity continuously lit? On 2.4.19, it only lits when there is
disk/CD-ROM activity, but on 2.5.38+ it's kept always lit...
Sincerely,
Felipe Alfaro
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com
next reply other threads:[~2002-09-30 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 15:55 Felipe Alfaro Solana [this message]
2002-09-30 19:45 ` cdrecord, IDE-SCSI and 2.5.39 Thomas Molina
2002-09-30 20:13 ` Bongani
2002-10-01 2:41 ` Thomas Molina
2002-09-30 20:43 Felipe Alfaro Solana
2002-09-30 20:45 Felipe Alfaro Solana
2002-10-01 2:46 ` Thomas Molina
2002-10-01 8:16 bonganilinux
2002-10-01 11:26 Felipe Alfaro Solana
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=F758Ts6DdVjkfQWswop000122ba@hotmail.com \
--to=felipe_alfaro@msn.com \
--cc=dgilbert@interlog.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 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).