Dale rdalek1...@gmail.com wrote:
Used versions
---
mkisofs: 2.1.1a77
growisofs: 7.1
growisofs command:
---
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=4gms
On Mon, Apr 19, 2010 at 8:44 PM, Dale rdalek1...@gmail.com wrote:
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0
This part jumps out at me.
Is /dev/hdd your new DVD burner? Is it really IDE and not SATA?
And isn't /dev/fd/0 a floppy device? Are you burning from a floppy to
an IDE drive?
Paul Hartman paul.hartman+gen...@gmail.com wrote:
On Mon, Apr 19, 2010 at 8:44 PM, Dale rdalek1...@gmail.com wrote:
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0
This part jumps out at me.
Is /dev/hdd your new DVD burner? Is it really IDE and not SATA?
And isn't /dev/fd/0 a floppy device? Are
On Tue, Apr 20, 2010 at 10:38 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Paul Hartman paul.hartman+gen...@gmail.com wrote:
On Mon, Apr 19, 2010 at 8:44 PM, Dale rdalek1...@gmail.com wrote:
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0
This part jumps out at me.
Is /dev/hdd
On 4/20/2010 11:01 AM, Paul Hartman wrote:
On Mon, Apr 19, 2010 at 8:44 PM, Dale rdalek1...@gmail.com wrote:
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0
And isn't /dev/fd/0 a floppy device? Are you burning from a floppy to
an IDE drive?
/dev/fd0 is a floppy. /dev/fd/0 is file descriptor 0 for
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
Used versions
---
mkisofs: 2.1.1a77
growisofs: 7.1
growisofs command:
---
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=4gms
Dale rdalek1...@gmail.com wrote:
---
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=4gms
-use-the-force-luke=tracksize:2295193 -speed=4
-use-the-force-luke=bufsize:32m
Well, if your problems
On Tue, Apr 20, 2010 at 10:45:27AM -0500, Paul Hartman wrote:
/dev/fd/0 is /dev/stdin
I learned something new, thanks :)
To complete your education :) fd stands for file descriptor.
fd/0 = stdin
fd/1 = stdout
fd/2 = stderr
You can create your own file descriptors and use them to
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
---
/usr/bin/growisofs -Z /dev/hdd=/dev/fd/0 -use-the-force-luke=notray
-use-the-force-luke=tty -use-the-force-luke=4gms
-use-the-force-luke=tracksize:2295193 -speed=4
-use-the-force-luke=bufsize:32m
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
Well whether k3b knows it or not, there is 320Gbs of space left. I did
some more testing and the drive really doesn't do anything now. Even
hdparm can't read all the info so I ordered a drive about 12 hours ago.
I have had this
Dale rdalek1...@gmail.com wrote:
It is a different prob;em than before. First time I got this error.
I'm going to install the version of cdrtools that was working and see if
it works. Will post the result later today. I got to drive a tractor
for a little while.
If I did understand
Dale rdalek1...@gmail.com wrote:
I tried a older version of k3b and different versions of cdrtools with
no change. Also tkdvd doesn't work either. Slightly different error but
still doesn't burn.
Posted on kde mailing list to see if this is some known issues with
k3b. Maybe hardware?
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
I tried a older version of k3b and different versions of cdrtools with
no change. Also tkdvd doesn't work either. Slightly different error but
still doesn't burn.
Posted on kde mailing list to see if this is some known issues with
Dale rdalek1...@gmail.com wrote:
Well whether k3b knows it or not, there is 320Gbs of space left. I did
some more testing and the drive really doesn't do anything now. Even
hdparm can't read all the info so I ordered a drive about 12 hours ago.
I have had this brand before so maybe it
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
Well whether k3b knows it or not, there is 320Gbs of space left. I did
some more testing and the drive really doesn't do anything now. Even
hdparm can't read all the info so I ordered a drive about 12 hours ago.
I have had this
Dale rdalek1...@gmail.com wrote:
On the screen that usually shows the progress, it says Fatal error at
startup: No space left on device. The main screen where I select files
shows there is space left. It shows about 1Mb or so left.
I also have a much smaller slice for the backup. When
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
On the screen that usually shows the progress, it says Fatal error at
startup: No space left on device. The main screen where I select files
shows there is space left. It shows about 1Mb or so left.
I also have a much smaller slice
Dale wrote:
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
On the screen that usually shows the progress, it says Fatal error at
startup: No space left on device. The main screen where I select
files
shows there is space left. It shows about 1Mb or so left.
I also have a much
On Sat, Apr 10, 2010 at 3:52 PM, Dale rdalek1...@gmail.com wrote:
On the screen that usually shows the progress, it says Fatal error at
startup: No space left on device. The main screen where I select files
shows there is space left. It shows about 1Mb or so left.
Do you have enough free
Paul Hartman wrote:
On Sat, Apr 10, 2010 at 3:52 PM, Dalerdalek1...@gmail.com wrote:
On the screen that usually shows the progress, it says Fatal error at
startup: No space left on device. The main screen where I select files
shows there is space left. It shows about 1Mb or so left.
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
All I know is that I downgraded cdrtools and it worked. I didn't even
eject the media. Since it works now , I don't guess there is any way to
test it. Next time I do a backup, I'll upgrade and see if it fails. If
it does, maybe
Paul Hartman paul.hartman+gen...@gmail.com wrote:
On Thu, Apr 1, 2010 at 10:02 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Your media was either accepted after several tries by the drive for unknown
reasons and is now usable in general again or you are observing a problem
Dale rdalek1...@gmail.com wrote:
He was talking about you mentioning hal. I think hal is running on this
thing but just not for xorg. It seems to work fine everywhere except
xorg. Then again, when I put a CD/DVD in, it doesn't mount it
automatically anymore. I think that is a KDE4
Dale rdalek1...@gmail.com wrote:
All I know is that I downgraded cdrtools and it worked. I didn't even
eject the media. Since it works now , I don't guess there is any way to
test it. Next time I do a backup, I'll upgrade and see if it fails. If
it does, maybe then we can figure it
On Tue, Apr 6, 2010 at 7:24 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Paul Hartman paul.hartman+gen...@gmail.com wrote:
On Thu, Apr 1, 2010 at 10:02 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Your media was either accepted after several tries by the
Paul Hartman paul.hartman+gen...@gmail.com wrote:
Would a HAL preprobe FDI like this prevent it from interfering with
burning?
Could you explain what this means?
I was just thinking if HAL is instructed to ignore the device maybe it
won't bother it any more (if that's even the cause
On Tue, Apr 6, 2010 at 10:54 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Paul Hartman paul.hartman+gen...@gmail.com wrote:
Would a HAL preprobe FDI like this prevent it from interfering with
burning?
Could you explain what this means?
I was just thinking if HAL is
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
All I know is that I downgraded cdrtools and it worked. I didn't even
eject the media. Since it works now , I don't guess there is any way to
test it. Next time I do a backup, I'll upgrade and see if it fails. If
it does, maybe
On Thu, 01 Apr 2010 16:12:30 -0500, Dale wrote:
Then again, when I put a CD/DVD in, it doesn't mount it
automatically anymore. I think that is a KDE4 thing. I may not have
turned something on. I just haven't looked into it yet.
That's a settings thing, turned off by default
System
Neil Bothwick wrote:
On Thu, 01 Apr 2010 16:12:30 -0500, Dale wrote:
Then again, when I put a CD/DVD in, it doesn't mount it
automatically anymore. I think that is a KDE4 thing. I may not have
turned something on. I just haven't looked into it yet.
That's a settings thing, turned
On 4/1/2010 4:38 PM, Paul Hartman wrote:
On Thu, Apr 1, 2010 at 10:02 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Your media was either accepted after several tries by the drive for unknown
reasons and is now usable in general again or you are observing a problem
caused by
Neil Bothwick wrote:
On Thu, 01 Apr 2010 16:12:30 -0500, Dale wrote:
Then again, when I put a CD/DVD in, it doesn't mount it
automatically anymore. I think that is a KDE4 thing. I may not have
turned something on. I just haven't looked into it yet.
That's a settings thing, turned
On Fri, Apr 2, 2010 at 12:21 PM, Dale rdalek1...@gmail.com wrote:
Neil Bothwick wrote:
On Thu, 01 Apr 2010 16:12:30 -0500, Dale wrote:
Then again, when I put a CD/DVD in, it doesn't mount it
automatically anymore. I think that is a KDE4 thing. I may not have
turned something on. I just
Bad enough you mentioned HAL in a conversation with Dale. Now there's
XML involved. This thread is officially never going to end.
This list really lightens up a day. LOL
--
If we can but prevent the government from wasting the labours of the
people, under the pretence of taking care of
On Fri, 02 Apr 2010 10:20:24 -0500, Dale wrote:
It is mounting it now. I can see it when I type in mount. I figured
it was turned off somewhere. Now to get me a little icon on the
desktop so I can open it. lol
Try adding the Device Notifier plasmoid to the task bar, I ind that much
more
On Fri, 02 Apr 2010 11:21:04 -0500, Dale wrote:
Am I supposed to have anything in fstab for KDE4 and the DVD? I don't
have currently and didn't for KDE3 either. I read somewhere that KDE4
did this differently tho.
No, KDE determines the mount point from the volume name.
--
Neil
Neil Bothwick wrote:
On Fri, 02 Apr 2010 10:20:24 -0500, Dale wrote:
It is mounting it now. I can see it when I type in mount. I figured
it was turned off somewhere. Now to get me a little icon on the
desktop so I can open it. lol
Try adding the Device Notifier plasmoid to the
Neil Bothwick wrote:
On Fri, 02 Apr 2010 11:21:04 -0500, Dale wrote:
Am I supposed to have anything in fstab for KDE4 and the DVD? I don't
have currently and didn't for KDE3 either. I read somewhere that KDE4
did this differently tho.
No, KDE determines the mount point from the
On Fri, Apr 02, 2010 at 03:27:39PM -0400, stosss wrote:
Bad enough you mentioned HAL in a conversation with Dale. Now there's
XML involved. This thread is officially never going to end.
This list really lightens up a day. LOL
--
If we can but prevent the government from wasting the
Dale rdalek1...@gmail.com wrote:
mkisofs
---
2097493
/usr/bin/mkisofs: Warning: Cannot add inode hints with -no-cache-inodes.
I strongly recommend not to use the option -no-cache-inodes.
This option causes mkisofs not to check for hard links. As a rersult,
the
Dale rdalek1...@gmail.com wrote:
growisofs -dvd-compat -Z /dev/dvd=/path/to/file.iso
At least you'll have a better idea where the problem lies.
Could I just get rid of one of the programs or are they all part of the
same package? I suspect a mismatch of package versions which
Dale rdalek1...@gmail.com wrote:
Used versions
---
cdrecord: 2.1.1a77
cdrecord
---
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version:
Dale rdalek1...@gmail.com wrote:
This is hopefully the last update. I have now burned several DVDs,
including the ones that failed earlier, with no errors at all. I guess
the newer version of cdrtools has some issues which may be why it is not
in stable yet. ;-)
There are no known
Mike Edenfield kut...@kutulu.org wrote:
On 3/30/2010 1:00 PM, Dale wrote:
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags:
Dale rdalek1...@gmail.com wrote:
I see your points but it just finished burning about 6 more very full
DVDs with not one single error. They burned with no prompts other than
the usual things it does to confirm what I am doing, such as overwriting
a DVD with data on it. Since it was
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
Used versions
---
cdrecord: 2.1.1a77
cdrecord
---
scsidev: '/dev/hdd'
devname: '/dev/hdd'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
I see your points but it just finished burning about 6 more very full
DVDs with not one single error. They burned with no prompts other than
the usual things it does to confirm what I am doing, such as overwriting
a DVD with data on
Dale rdalek1...@gmail.com wrote:
After downgrading to a stable cdrtools, I don't have any failing media.
I have been using the same drive and media for quite a while tho. I
There is a difference between after downgrading and _from_ downgrading.
It you really mean _after_ downgrading, there
Dale rdalek1...@gmail.com wrote:
OK. I thought I would try some different versions of software and see
what happens. With the info Neil provided about what does what, I
thought I would try a different version of cdrtools. I went to a older
version and it worked fine on the first try
Joerg Schilling wrote:
Dalerdalek1...@gmail.com wrote:
OK. I thought I would try some different versions of software and see
what happens. With the info Neil provided about what does what, I
thought I would try a different version of cdrtools. I went to a older
version and it worked
On Thu, 01 Apr 2010 17:02:20 +0200, Joerg Schilling wrote:
Your media was either accepted after several tries by the drive for
unknown reasons and is now usable in general again or you are observing
a problem caused by hald.
OMG Jörg! Do you have any idea what you've done?
--
Neil Bothwick
On Thu, Apr 1, 2010 at 10:02 AM, Joerg Schilling
joerg.schill...@fokus.fraunhofer.de wrote:
Your media was either accepted after several tries by the drive for unknown
reasons and is now usable in general again or you are observing a problem
caused by hald. Note that hald does not care about
Neil Bothwick n...@digimed.co.uk wrote:
On Thu, 01 Apr 2010 17:02:20 +0200, Joerg Schilling wrote:
Your media was either accepted after several tries by the drive for
unknown reasons and is now usable in general again or you are observing
a problem caused by hald.
OMG Jörg! Do you have
Joerg Schilling wrote:
Neil Bothwickn...@digimed.co.uk wrote:
On Thu, 01 Apr 2010 17:02:20 +0200, Joerg Schilling wrote:
Your media was either accepted after several tries by the drive for
unknown reasons and is now usable in general again or you are observing
a problem caused by
Am Tue, 30 Mar 2010 15:06:46 -0500
schrieb Dale rdalek1...@gmail.com:
Dale wrote:
[...]
I hope the DVD guru saw this and the error just in case he sees what
needs fixing. Maybe he is on vacation or something. :-)
Heh, I was wondering where Jörg Schilling (I guess that's who you mean) is,
Marc Joliet wrote:
Am Tue, 30 Mar 2010 15:06:46 -0500
schrieb Dalerdalek1...@gmail.com:
Dale wrote:
[...]
I hope the DVD guru saw this and the error just in case he sees what
needs fixing. Maybe he is on vacation or something. :-)
Heh, I was wondering where Jörg
On Wed, 31 Mar 2010 17:46:47 -0500, Dale wrote:
I don't always get involved in a hal thread.
And bears don't always shit in the woods...
;-)
--
Neil Bothwick
He who asks a question is a fool for a minute,
He who doesn't ask is a fool for a lifetime.
signature.asc
Description: PGP
On Mon, 29 Mar 2010 20:19:02 -0500, Dale wrote:
I also tried to burn this with tkdvd but it failed too. I don't think
the media is bad. It doesn't appear to be k3b since the other program
fails too. I also updated to the latest testing but no
difference that I can see. It does sometimes
On Tue, Mar 30, 2010 at 3:39 AM, Neil Bothwick n...@digimed.co.uk wrote:
On Mon, 29 Mar 2010 20:19:02 -0500, Dale wrote:
I also tried to burn this with tkdvd but it failed too. I don't think
the media is bad. It doesn't appear to be k3b since the other program
fails too. I also updated to
stosss wrote:
On Tue, Mar 30, 2010 at 3:39 AM, Neil Bothwickn...@digimed.co.uk wrote:
On Mon, 29 Mar 2010 20:19:02 -0500, Dale wrote:
I also tried to burn this with tkdvd but it failed too. I don't think
the media is bad. It doesn't appear to be k3b since the other program
fails
Neil Bothwick wrote:
On Mon, 29 Mar 2010 20:19:02 -0500, Dale wrote:
I also tried to burn this with tkdvd but it failed too. I don't think
the media is bad. It doesn't appear to be k3b since the other program
fails too. I also updated to the latest testing but no
difference that I can
On Tue, Mar 30, 2010 at 11:00 AM, Dale rdalek1...@gmail.com wrote:
Neil Bothwick wrote:
On Mon, 29 Mar 2010 20:19:02 -0500, Dale wrote:
I also tried to burn this with tkdvd but it failed too. I don't think
the media is bad. It doesn't appear to be k3b since the other program
fails too.
On Tue, 30 Mar 2010 11:00:06 -0500, Dale wrote:
K3b is running mkisofs and growisofs at the same time, hence the
mixed up debug output making it hard to see where the error is coming
from. Take the media, drive and growisofs out of the equation by
getting K3b to create an ISO image
Neil Bothwick wrote:
On Tue, 30 Mar 2010 11:00:06 -0500, Dale wrote:
K3b is running mkisofs and growisofs at the same time, hence the
mixed up debug output making it hard to see where the error is coming
from. Take the media, drive and growisofs out of the equation by
getting K3b to create
Dale wrote:
OK. I went back to k3b and tried to burn a Gentoo install disc which
is a iso image. This is what it gives when I do that.
SNIP
This appears to be using cdrecord. Any ideas? Should I shoot it? lol
Dale
:-) :-)
OK. I thought I would try some different versions of
Dale wrote:
Dale wrote:
OK. I went back to k3b and tried to burn a Gentoo install disc which
is a iso image. This is what it gives when I do that.
SNIP
This appears to be using cdrecord. Any ideas? Should I shoot it? lol
Dale
:-) :-)
OK. I thought I would try some different
On 3/30/2010 1:00 PM, Dale wrote:
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
This part is claiming that
Mike Edenfield wrote:
On 3/30/2010 1:00 PM, Dale wrote:
status: 0x2 (CHECK CONDITION)
Sense Bytes: 70 00 03 00 00 00 00 0A 00 00 00 00 73 03 00 00
Sense Key: 0x3 Medium Error, Segment 0
Sense Code: 0x73 Qual 0x03 (power calibration area error) Fru 0x0
Sense flags: Blk 0 (not valid)
68 matches
Mail list logo