*SOLVED, see Bug 22781* K3b CD to CD copy problem

Message

Master_Of_Disaster · Post by **Master_Of_Disaster** » Thu Jun 05, 2003 6:36 pm

Hi guys,
in my machine there is an IDE Burner and an IDE DVD-ROM. I have set up K3B correctly for burning, and it works perfectly, but theres one PITA: I'm unable to use my DVD-ROM as a Reader in CD 2 CD Copies, although K3B tells me that it has been detected correctly. Have I missed a setting? Or is it impossible to use an IDE Device as a reader (I hope not!)?

jetblack · Post by **jetblack** » Thu Jun 05, 2003 6:56 pm

I had that problem, too. It turned out that I had to explicitly tell it to use the "generic-mmc" driver for the reader in the settings. Unfortunately, I'm not home now, so I don't recall exactly where it is. Somewhere in the settings, though, there's a list that tells you all the properties of your devices. It looks like everything is read-only, but you can actually set the driver from there. In my case, it said "Auto" or something. Clicking on the driver gave me a drop down, from which I selected "generic-mmc". After that, everything was fine.

How's that for a vague, wordy answer?

Master_Of_Disaster · Post by **Master_Of_Disaster** » Thu Jun 05, 2003 7:08 pm

Sorry but that did not help, there is no such option.
Here
http://fuero.homeftp.net/tiki/tiki-brow ... imageId=29
you can see what K3B sees...

jetblack · Post by **jetblack** » Thu Jun 05, 2003 7:21 pm

Oh, I'm sorry. I misunderstood. I am using scsi emulation for both my dvd-rom and my cd burner. That's why I had that option. I'm not sure how to do it without SCSI emulation. I did a forum search for "k3b ATAPI", but didn't see anything too promising. Maybe something would jump out at you, though.

Master_Of_Disaster · Post by **Master_Of_Disaster** » Thu Jun 05, 2003 7:57 pm

You were right, Google popped out the answer:

From the K3B FAQ:

Q: I cannot select my IDE CDROM as reading device in the cd copy dialog.
A: K3b currently does only support SCSI devices for cd copy. To use your IDE CDROM for
reading please enable SCSI emulation.

Darn it!

Master_Of_Disaster · Post by **Master_Of_Disaster** » Thu Jun 05, 2003 8:16 pm

hm, I appended "hdb=ide-scsi" to my Kernelparameters, which are now: "root=/dev/hda3 hdc=ide-scsi hdb=ide-scsi video=vesa:ywrap,mtrr vga=0x31A"
K3B thinks now it's ok to use my DVD drive, but keeps telling me now that the inserted disc is empty...

[edit]
also checked the driver setting for the DVD-ROM as you suggested, it neither works with generic-mmc nor with auto.
[/edit]

Eliad · Post by **Eliad** » Thu Jun 05, 2003 11:40 pm

Did you modify your fstab correctly(replace /dev/hdb with /dev/scd0 etc etc)? did you run the k3b setup again?

Another thing to be careful about is that when you run k3b setup it saves the driver settings for the ROOT user... you have to also set the driver under the configuration option under the menu when you run k3b as normal user...

hope that helps

Master_Of_Disaster · Post by **Master_Of_Disaster** » Fri Jun 06, 2003 5:51 am

From fstab:

/dev/scsi/host0/bus0/target0/lun0/cd /mnt/cdrom auto ro,noauto,user,exec 0 0
/dev/scsi/host0/bus0/target1/lun0/cd /mnt/brenner auto ro,noauto,user,exec 0 0

K3B Setup has been executed as root, in the K3B Settings I changed then driver afterwards.
Still not working

hoppy · Post by **hoppy** » Fri Jun 13, 2003 3:43 am

I had a similar problem that drove me absolutely NUTS!! I had both drives enabled in SCSI ATAPI mode and it would see the reader, but then tell me that there was no data on the source drive. I updated CDRECORD (I think thats the package name) to v2.x and it worked straight away. CDrecord doesnt seem to be a package in the world update file as I often do an "emerge --update world"... but this needed a manual upgrade.

Master_Of_Disaster · Post by **Master_Of_Disaster** » Fri Jun 13, 2003 8:59 am

Package is app-cdr/cdrtools, on my System there is 2.01_alpha14 installed, but i have still the same problem that hoppy had. BTW: it was recorded in my world file.

ugly_orc · Post by **ugly_orc** » Fri Jun 13, 2003 10:27 am

I had the same problem with cdrtools 2.01_alpha14. Looking at this thread, I decided to try downgrading cdrtools to 2.01_alpha08 and it fixed it! Now k3b works like it used to, and finds the contents of the cd you give it.
That's good because it was starting to really annoy me

I hope this "fix" will work for others. BTW, should we post a bug report ? There was none about this yesterday...

Master_Of_Disaster · Post by **Master_Of_Disaster** » Fri Jun 13, 2003 8:13 pm

Hm i will try that. If this does the trick, i'll handle the bug report. BTW: How can you tell portage not to try to update a particular package?

Master_Of_Disaster · Post by **Master_Of_Disaster** » Fri Jun 13, 2003 8:28 pm

Ha finally! Thanks for your help, it works now. I created a bugreport, see Bug 22781.

ugly_orc · Post by **ugly_orc** » Sat Jun 14, 2003 9:09 am

BTW: How can you tell portage not to try to update a particular package?

I just did an "emerge inject app-cdr/cdrtools-2.01_alpha14".

Master_Of_Disaster · Post by **Master_Of_Disaster** » Mon Jun 16, 2003 10:48 am

See bug update: I found out the problem can also be solved by updating K3B to 0.9pre1.

deepthought · Post by **deepthought** » Mon Jun 16, 2003 12:54 pm

ugly_orc wrote:
BTW: How can you tell portage not to try to update a particular package?
I just did an "emerge inject app-cdr/cdrtools-2.01_alpha14".

"Pinning" a package to a certain version (to prevent it from being up-/downgraded by emerge" by using

Code: Select all

emerge inject foo-<yourversion>

is a really bad idea, as it tricks portage into thinking that a certain package with a certain version is installed, but actually it isn't.

Now think of a package depending (or using) foo-<yourversion>. Portage will think that foo is available and tell the other package to use it. Unfortunately, the "configure" run during package building doesn't know about package injection and will -- remember that the package isn't really there -- fail.

This failure is not mandatory. emerge may fail during configure, make or whereever else. In the worst case, you will have problems after successfully emerging the package depending on foo during runtime.

A far better solution for "pinning" a package to a certain version is to specify this in the world file. Do

Code: Select all

nano -w /var/cache/edb/world

as root and find the line with the package to "pin". If it isn't there, add it (like sys-foo/bar).

Now change the entry as follows:

Code: Select all

=sys-foo/bar-<theversionyouwant>

Note that wildcards and "greater/lighter than" statements are allowed. For example I have the following line in my world file:

Code: Select all

>=app-emulation/vmware-workstation-4.*

Portage never bothers downgrading this package, although it's still unstable (~x86) and I don't use ACCEPT_KEYWORDS="~x86".

This is the recommended way to lock a package to a certain (or a set of ) version(s) -- don't mimic this "inject" madness.

Regards,
Alexander

ugly_orc · Post by **ugly_orc** » Tue Jun 17, 2003 10:08 am

"Pinning" a package to a certain version (to prevent it from being up-/downgraded by emerge" by using
Code: Select all
emerge inject foo-<yourversion>
is a really bad idea, as it tricks portage into thinking that a certain package with a certain version is installed, but actually it isn't.
...
A far better solution for "pinning" a package to a certain version is to specify this in the world file.

Oh, ok. Thanks for the tip. I'm not too clear on the inner workings of portage, so I thought inject would do just that, insert the package into the world file... But I'll take your word on it and do it your way from now on. Thanks!

hoppy · Post by **hoppy** » Wed Jun 18, 2003 10:52 am

Just as a further update to this. I went to do a CD Copy this evening and its not working again. A quick check shows that cdrtools is now at 2.01_alpha14

Portage must have updated it sometime between when I last used it and reading this thread

How do you downgrade a package??

Master_Of_Disaster · Post by **Master_Of_Disaster** » Wed Jun 18, 2003 2:33 pm

emerge -C package
emerge /usr/portage/appgroup/appname/version_you_want_to_emerge.ebuild

But try K3B 0.9pre1, you can find the ebuild by searching the forum.

hoppy · Post by **hoppy** » Thu Jun 19, 2003 12:22 am

K3b-0.9-pre2 is in ~X86. Ive just emerged it and all is working fine again

Master_Of_Disaster · Post by **Master_Of_Disaster** » Thu Jun 19, 2003 1:20 pm

same for me, already posted test results to bug, should be resolved now.

crimson · Post by **crimson** » Fri Sep 05, 2003 7:06 am

After both upgrading to newest k3b: 0.9, AND downgrading to the older cdrtools(alpha08), I STILL can't copy cd to cd. Atleast now k3b detects that there actually are tracks on the cd, but this doesn't make a bit of difference since it won't burn them

.

ch_bock · Post by **ch_bock** » Fri Sep 05, 2003 1:10 pm

I didn't read everything, but when I had problems copying cd to cd (which is done by cdrdao) I edited the cdrdao/drivers file that it matched. If your drive is not listed it won't work
Its more or less self explaining, but I'm at a windows machine atm so I cant tell where the file is.

an cdrecord --scanbus should give the detailed name of your burner

have fun

crimson · Post by **crimson** » Fri Sep 05, 2003 8:22 pm

well, I know my cd recorder works... But neither it or my cd-rom drive are in the /usr/share/cdrdao/drivers file.

However the line for a cdrom drive:
R|E-IDE|CD-ROM 52X/AKH|generic-mmc
only differs from mine in the speed, mine is 56X.

I *have been trying to use the generic-mmc and generic-mmc-raw drivers for this drive, to no avail. I know my cdrw works, how can I test cd-->cd copy without the k3b interface, just using cdrdao?

Squinky86 · Post by **Squinky86** » Sun Sep 14, 2003 5:38 pm

I'm a bit confused- I disabled scsi emulation when I found out cdrtools could do ATAPI burning. It seems that if cdrtools can burn in ATAPI mode, it should also be able to read in that mode, or is that currently being worked on? Oh well, now to recompile my kernel (again).
Oh, and thanks for the thread- I was getting rather frustrated and this helped me out.

SOLVED, see Bug 22781 K3b CD to CD copy problem

SOLVED, see Bug 22781 K3b CD to CD copy problem

wow