Gene Heskett writes:
> Point being Lisi, that its without a doubt of
> Chinese manufacture and the price on your store
> shelf should be comparable +- shipping and of course
> any resttrictive tarrifs your government may have in
> place one way or the other. Some call it a customs
> tax, but the
On Monday 25 January 2016 05:13:23 Lisi Reisz wrote:
> On Monday 25 January 2016 00:45:58 Gene Heskett wrote:
> > I bought the last burner I have, about 3 or 4 years ago at wallmart,
> > everything but Blue Ray, for about a $25 dollar bill. Internal, sata
> > interface.
>
> Don't gloat, Gene. ;-)*
On Monday 25 January 2016 00:45:58 Gene Heskett wrote:
> I bought the last burner I have, about 3 or 4 years ago at wallmart,
> everything but Blue Ray, for about a $25 dollar bill. Internal, sata
> interface.
Don't gloat, Gene. ;-)*
Lisi
*Tech prices in the USA are very low compared with many of
Hi,
Emanuel Berg wrote:
> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0
That's another member of the family of medium-not-present messages:
2 3A 00 MEDIUM NOT PRESENT
2 3A 01 MEDIUM NOT PRESENT TRAY CLOSED
2 3A 02 MEDIUM NOT PRESENT TRAY OPEN
2 3A 03 MEDIUM NOT PRESENT LO
On Sunday 24 January 2016 18:50:25 Emanuel Berg wrote:
> "Thomas Schmitt" writes:
> > wodim -v dev=/dev/sr0 -toc
> >
> > If i run this on an empty drive, i get
> >
> > ... Current: 0x (Reserved/Unknown) ... Sense
> > Code: 0x3A Qual 0x01 (medium not present - tray
> > closed) Fru 0x0 ...
"Thomas Schmitt" writes:
> wodim -v dev=/dev/sr0 -toc
>
> If i run this on an empty drive, i get
>
> ... Current: 0x (Reserved/Unknown) ... Sense
> Code: 0x3A Qual 0x01 (medium not present - tray
> closed) Fru 0x0 ... wodim: No disk / Wrong disk!
I get the same, only:
Sense Code: 0x
Hi,
> I have suspected a hardware error as well. Is there
> any way to confirm this?
You could try whether it can recognize any kind of other medium:
wodim -v dev=/dev/sr0 -toc
If i run this on an empty drive, i get
...
Current: 0x (Reserved/Unknown)
...
Sense Code: 0x3A Qual 0x0
"Thomas Schmitt" writes:
> Bad news is that you will probably have to get
> a new burner.
I have suspected a hardware error as well. Is there
any way to confirm this?
Strange thing tho I recently burned an ISO DVD movie
to a DVD with no problem. I'm used to things in the
computer world either w
Hi,
Emanuel Berg wrote:
> http://user.it.uu.se/~embe8573/wodim_log
where i read
> Executing 'test unit ready' command on Bus 1 Target 0, Lun 0 timeout 200s
> CDB: 00 00 00 00 00 00
> Errno: 5 (Input/output error), test unit ready scsi sendcmd: no error
> CDB: 00 00 00 00 00 00
> status: 0x2 (C
Emanuel Berg writes:
> The disc is a CD-R
I have tried two CD-Rs brand new from the (same) box -
same thing.
--
underground experts united
http://user.it.uu.se/~embe8573
"Thomas Schmitt" writes:
> wodim -V ...your.wodim.options... 2>&1 | tee -i
> /tmp/wodim_log
http://user.it.uu.se/~embe8573/wodim_log
> What wodim options did you use, exactly ?
zsh: http://user.it.uu.se/~embe8573/conf/.zsh/dvd
burn-iso-to-cd () {
local iso=$1
wodim -v
Hi,
Emanuel Berg wrote:
> > $ wodim --devices
> > I get "Cannot open SCSI driver!"
strace reveils that this confusing message comes from the total
lack of /dev/scd* and /dev/hd* device files or links.
I can fix it on my Jessie by
for i in 0 1 2 3 4 5
do
test -
uot;Cannot open SCSI driver!"
This i can reproduce on Jessie.
wodim: No such file or directory.
Cannot open SCSI driver!
For possible targets try 'wodim --devices' or 'wodim -scanbus'.
wodim -scanbus does not work either.
(How can it be that unchanged softwar
When I try to burn with wodim, it says
Errno: 5 (Input/output error), test unit ready
scsi sendcmd: no error
and
$ wodim --devices
I get "Cannot open SCSI driver!"
Ideas?
--
underground experts united
http://user.it.uu.se/~embe8573
> Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
> cdrecord: No such file or directory. Cannot open SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
>
> Well, maybe my kernel isn't configured
On Thu, 12 Jun 2003 20:02:01 +0200
Jon Haugsand <[EMAIL PROTECTED]> wrote:
>
> There is a slight problem, though. Nothing happened after a reboot, I
> had to perform a 'modprobe ide-scsi' manually. Thus, I guess I need
> this to be performed at each boot, but where to put it?
man -k modules
man
* Chris Metzler
> This document, aimed at Debian users, should help you:
>
> http://newbiedoc.sourceforge.net/peripherals/cdrw.html
Thanks, it did. I only needed to insert an
append="hdd=ide-scsi max_scsi_luns=1"
line in lilo.conf. I haven't tested it, but it is responding to
'cdrecord -sca
ord: No such file or directory. Cannot open SCSI driver.
> cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you
> are root.
>
> Well, maybe my kernel isn't configured for my cd writer, but how do I
> do just that?
The first few entries on a Google search
Trying to get my cd writer to run. After installing cdrecord, I
tried:
cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Mak
e/chiappa# cdrecord -scanbus
> Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 J?rg Schilling
> cdrecord: No such file or directory. Cannot open SCSI driver.
>
>
> Now, after surfed google a little, I am wonder if I have a problem with
> the /dev/sg0 device. The MAKEDE
tray
sr1: scsi3-mmc drive: 24x/32x writer cd/rw xa/form2 cdda tray
remember that my problem is this message:
nostromo:/home/chiappa# cdrecord -scanbus
Cdrecord 1.10 (i686-pc-linux-gnu) Copyright (C) 1995-2001 Jörg Schilling
cdrecord: No such file or directory. Cannot open SCSI driver.
Now, after
e-
From: Marcelo Chiapparini [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 22, 2003 9:06 AM
To: debian user
Subject: Cannot open SCSI driver
Hello!
I am running woody and I have a cdrom and a cdwriter. I want to write
cds using the cdwriter reading from the cdrom. Both are ATAPI devices
google is your friend!
http://www.google.com/search?q=Cannot+open+SCSI+driver&sourceid=mozilla-search&start=0&start=0
a couple of interesting threads described similar problems. from what i
gather from a quick peek, it's a symlink issue.
this is what my setup looks like:
ge
d: No such file or directory. Cannot open SCSI driver.
thus, cdrecord cannot find the SCSI driver (scsi0?). But the scsi drive
is readed during the boot process, as can be seen from the dmesg output
above.
What is going wrong? Any help will be very appreciated!
Marcelo
--
Marcelo Chiapparini
D
24 matches
Mail list logo
