From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: IDE-SCSI oops in 2.6.0-test11
Date: 2 Dec 2003 21:39:15 GMT [thread overview]
Message-ID: <bqj0q3$dge$1@gatekeeper.tmr.com> (raw)
In-Reply-To: 3FCC9307.8050409@wmich.edu
In article <3FCC9307.8050409@wmich.edu>,
Ed Sweetman <ed.sweetman@wmich.edu> wrote:
| ross.alexander@uk.neceur.com wrote:
| > CPU: Athlon-XP 2700+
| > MB: ASUS A7N8X Deluxe
| > Memory: 3 x 512MB
| > Notes: UP kernel, standard EIDE driver, boot paramters acpi=off
| > nolapic,noapic
| > Libc: glibc-2.3.2 with linuxthreads.
| >
| > This error occurs while trying to write a DVD+RW to an NEC-1300A DVD
| > writer
| > using cdrecord-dvdpro executable (no source available). This works fine
| > on linux-2.4.23.
| >
|
|
|
| First off, acpi should be working just fine now...should have been for
| the last couple versions of 2.6.0-test.
Is that "should have been working" as in "I believe it to be working" or
"dammit they said it was working?"
| Second, you probably shouldn't be using ide-scsi. ATAPI works just fine
| using straight ide for CDR's so it probably works fine for DVD-R+R+RW
| whatever stupid acronymn they're using today.
ATAPI works fine for programs which know about it and are
Linux-specific. Programs expecting SCSI devices, which work on Linux
2.4, Solaris, SCO, and even Windows (I'm told) want SCSI.
| Third, you didn't post the actual oops so how is anyone supposed t osay
| anything about this problem?
Your mail was truncated, I believe.
| Fourth, you are using a binary you didn't compile that's probably
| compiled against headers for api's found in 2.4.x which is seriously
| different from the kernel you're running it on. Compile your own
| cdrecord and see how it goes.
You missed the "binary only" in his post. That software is no more
available in source than Windows.
I think the real point is not that it doesn't work, but that it oops's
the system. I would regard anything which a user can do which causes an
oops as a critical problem.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
next prev parent reply other threads:[~2003-12-02 21:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 12:40 IDE-SCSI oops in 2.6.0-test11 ross.alexander
2003-12-02 13:26 ` Ed Sweetman
2003-12-02 14:08 ` ross.alexander
2003-12-02 16:53 ` Len Brown
2003-12-02 18:37 ` Linus Torvalds
2003-12-03 9:06 ` Jens Axboe
2003-12-03 12:25 ` ross.alexander
2003-12-03 16:07 ` bill davidsen
2003-12-02 21:39 ` bill davidsen [this message]
2003-12-02 21:53 ` Craig Bradney
2003-12-02 23:10 ` bill davidsen
[not found] ` <200312022310.SAA14384@gatekeeper.tmr.com>
2003-12-02 23:30 ` Craig Bradney
2003-12-02 23:33 ` bill davidsen
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='bqj0q3$dge$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--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 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).