LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-01-2007, 02:30 PM   #16
Lenard
Senior Member
 
Registered: Dec 2005
Location: Indiana
Distribution: RHEL/CentOS/SL 5 i386 and x86_64 pata for IDE in use
Posts: 4,790

Rep: Reputation: 57

I provided you with the link for the updated k3b (SUSE rpms by the way) before(post #2 in this thread), once again the link is:

http://packman.links2linux.de/package/k3b

Just get the list of the currently installed rpm packages;
rpm -qa 'k3b*'
Download the updated versions and install; rpm -Uvh k3b*.rpm

I use the red Hat family, but do not limit myself to just the default packages. If I did then I would have; k3b-0.12.17-1.el5.x86_64 installed instead of;

$ rpm -qa k3b
k3b-1.0.4-1.el5.x86_64


I'm glad cdrdao can see the burners, so can everything else. SCSI devices is they way to go. Currently the new 2.6.22 and 23 kernels consider all [S]ATA{PI}, SCSI and USB devices as SCSI devices makes life easier in the short and long runs. My CD/DVD burner is really on an IDE(ATAPI) interface but as far as my current kernel is concerned it is a SCSI device (and I'm glad), see post # 4 of this thread.

The very last cdrecord command(just so you know for your own knowledge) : cdrecord dev=ATA -scanbus
This should output results similar to the cdrdao output.

Last edited by Lenard; 12-01-2007 at 02:31 PM.
 
Old 12-01-2007, 04:05 PM   #17
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
So, that rpm command from the command line should work out ok even though those rpms were made for the 10.2 or 10.3 systems even though I have 10.0?

I just found the src.rpm from that link you gave me so I guess I will try that one first.

Thank you for all the info!
 
Old 12-02-2007, 07:34 AM   #18
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: Slackware®
Posts: 13,610
Blog Entries: 34

Rep: Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793Reputation: 2793
Hi,

So when did your devices stop working? Can you roll back to the version that was working?

As for the installation of applications on Slackware. No problem. You select the application then download the source to compile then install. During the compile session you can create a package to be installed that can be shared. If you don't want to compile the application source then get a Slackware package from a repository if you are that lazy. Slackware is what linux should be! A OS that can be used without all the overhead or necessity to wait on someone to create an update to allow it to function.

Don't get the wrong idea as some have that Slackware is difficult. Sure you are required to know the system intrinsically but once setup the OS is rock solid yet adaptable. The best UNIX like OS in my opinion!

The SUSE, FC or whatever turnkey OS a user selects can be useful to them but when something goes wrong with that type system that same user will have loads of problems figuring out what to do. Someone that uses a OS like Slackware, BSD or the like will know how to figure out how to solve the problem. As they will be the maintainer of that system. Sure some Slackware users just install the OS and don't really tweak their system once it has been configured to their computer.

I'm biased because of the simplicity of Slackware. I don't need a chauffeur to take me anywhere. Be it with my car or my OS.

You might find this Linux Distro time line interesting.
 
Old 12-07-2007, 10:47 AM   #19
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
onebuck,
My devices did not stop working as far as I know. The Sony DVD burner never was able to write DVD's on Linux. I'm sure that it wrote DVD's when it was installed on Windows.

btw, I did not try that k3b .src.rpm file yet. I'm looking around for some info to see if anyone knows if it will work on any version of SuSE.
 
Old 12-12-2007, 02:40 AM   #20
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
Do it on the command line (console) with
Code:
yast -i /path/to/your/k3b.rpm
That will do the sanity checks (dependencies) and run all necessary programs and scripts to keep your installation clean.

Last edited by JZL240I-U; 12-12-2007 at 02:59 AM.
 
Old 12-12-2007, 11:25 AM   #21
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
I did yast -i /path/to/your/k3b.rpm as you said, and it seemed to check out ok.
I then installed the package with YaST but rather than putting version 1.0.4-2.1 on, it downgraded the version I had to 0.12.10-1.

The rpm I was trying was: k3b-1.0.4-2.1.src.rpm

I finally compiled it from a source tar. That worked and when I checked the version it said, 1.0.4. I also saved the configure, make, and install session files for future reference.

Anyway, after trying it out, my original problem remains.

It keeps giving me this error:
"Media is not formatted or unsupported. Write error."

I have tried every type of DVD I can get my hands on and 2 different brands as well (Sony and Memorex). I've even tried pre-formatted DVD's.

If k3b is supposed to format the DVD itself -- apparently k3b cannot/does not format them for me.

For the fun of it, I even tried making an .iso but it still would not burn it to the DVD.
 
Old 12-13-2007, 03:01 AM   #22
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
Weellll, it might be that K3b is not the culprit at all. Look here http://www.linuxquestions.org/questi...8/#post2989142
for the description of the wodim "problem". Suggestion: Either get the newest wodim or use cdrecord. Don't forget to straighten your sym-links.

Last edited by JZL240I-U; 01-03-2008 at 06:41 AM.
 
Old 12-22-2007, 12:45 PM   #23
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
Unhappy

My system does use cdrecord. I read that thread you gave but it didn't give much in the way of answers.

I looked in the "devices" section of k3b's tools and it lists my DVD recorder as "Writes DVD+R(W)...yes"

So, maybe there's something wrong with SuSE 10.0.
 
Old 01-03-2008, 06:44 AM   #24
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
Back again. Did you try to issue a direct cdrecord command at the command line and what looked the output like then?
 
Old 01-03-2008, 08:26 AM   #25
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
I don't know what command should be given. I don't do anything with the command line except for configuring/installing apps and starting them and getting any info that I've learned the commands to.

If you give me an example that I can try I'll do that.
 
Old 01-03-2008, 09:12 AM   #26
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
Code:
cdrecord -scanbus
cdrecord dev=x,y,z speed=x blank=all -v /path/and/file.name
The first command will show your writer and in one line its connction to the SCSI interface (bus, target, LUN) in the way of three comma separated numbers, here shown as "x,y,z". Insert those in the second command after "dev=" instead of x,y,z. Depending from your machine it might be necessary to amend that to "dev=ATA:x,y,z", just give it a try.

Speed "x" has to be replaced by a value your burner is capable of handling/achieving, AFAIR cdrecord falls back to the maximum speed in case of you overshooting.

See also

http://www.tldp.org/HOWTO/CD-Writing-HOWTO.html
http://www.troubleshooters.com/linux/coasterless.htm

Last edited by JZL240I-U; 01-03-2008 at 09:15 AM.
 
Old 01-03-2008, 12:03 PM   #27
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
Here's the result of "cdrecord -scanbus":

Code:
cdrecord -scanbus
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.
Linux sg driver version: 3.5.33
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c    1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus2:
        2,0,0   200) 'Generic ' 'USB SD Reader   ' '2.00' Removable Disk
        2,1,0   201) *
        2,2,0   202) *
        2,3,0   203) *
        2,4,0   204) *
        2,5,0   205) *
        2,6,0   206) *
        2,7,0   207) *
Contrast this with the output of "cdrecord dev=ATA -scanbus":

Code:
cdrecord dev=ATA -scanbus
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: 'ATA'
devname: 'ATA'
scsibus: -2 target: -2 lun: -2
Warning: Using badly designed ATAPI via /dev/hd* interface.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c    1.83 04/05/20 Copyright 1997 J. Schilling').
scsibus1:
        1,0,0   100) 'SONY    ' 'DVD+RW  DRU-120A' '1.51' Removable CD-ROM
        1,1,0   101) 'RICOH   ' 'CD-R/RW MP7040A ' '1.40' Removable CD-ROM
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *
I did the 2nd command after re-reading one of the posts above from Leonard. I also found this part interesting:
"Warning: Using badly designed ATAPI via /dev/hd* interface." I don't know if this has any importance.

Leonard had said,
Quote:
"The very last cdrecord command(just so you know for your own knowledge): cdrecord dev=ATA -scanbus This should output results similar to the cdrdao output."
Which is interesting because it was not the same output at all. Also, "cdrecord -scanbus" is just giving me the contents of scsibus2 but the "cdrecord dev=ATA -scanbus" command gives me what is on scsibus 1.

I'm still reading the pages on the links you gave me.
 
Old 01-04-2008, 01:50 AM   #28
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
"badly designed" is a long term jibe of Jörg Schilling (author of cdrecord, who has a feud with some kernel / debian maintainers). As long as it works ... I certainly can't change a thing here.

Why don't you just invest a CD and try the cdrecord command on the Sony burner with the information gathered from the "cdrecord dev=ATA -scanbus" command (seems to be more plausible to me, and most users do have ATAPI devices after all...).

Btw.: If you want to burn DVDs make sure that K3b had the necessary programs in its configuration tab.

Last edited by JZL240I-U; 01-04-2008 at 02:05 AM.
 
Old 01-04-2008, 10:09 AM   #29
gymnart
Member
 
Registered: Oct 2005
Distribution: SUSE 11.4
Posts: 331

Original Poster
Rep: Reputation: 30
I wanted to find out the capabilities of the DVD recorder to see what speed it is capable of because I don't know that, and after trying a few things to get that prcap command to give me the info I need, I finally got it to work this way:

Code:
cdrecord -prcap dev=/dev/hdc
Cdrecord-Clone 2.01 (i686-suse-linux) Copyright (C) 1995-2004 Jörg Schilling
Note: This version is an unofficial (modified) version
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://www.suse.de/feedback
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Warning: Open by 'devname' is unintentional and not supported.
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (okir@suse.de-scsi-linux-sg.c-1.83-resmgr-patch '@(#)scsi-linux-sg.c  1.83 04/05/20 Copyright 1997 J. Schilling').
Device type    : Removable CD-ROM
Version        : 0
Response Format: 2
Capabilities   :
Vendor_info    : 'SONY    '
Identifikation : 'DVD+RW  DRU-120A'
Revision       : '1.51'
Device seems to be: Generic mmc2 DVD-ROM.

Drive capabilities, per MMC-2 page 2A:

  Does read CD-R media
  Does write CD-R media
  Does read CD-RW media
  Does write CD-RW media
  Does read DVD-ROM media
  Does not read DVD-R media
  Does not write DVD-R media
  Does not read DVD-RAM media
  Does not write DVD-RAM media
  Does support test writing

  Does read Mode 2 Form 1 blocks
  Does read Mode 2 Form 2 blocks
  Does read digital audio blocks
  Does restart non-streamed digital audio reads accurately
  Does not support Buffer-Underrun-Free recording
  Does read multi-session CDs
  Does read fixed-packet CD media using Method 2
  Does not read CD bar code
  Does read R-W subcode information
  Does not return R-W subcode de-interleaved and error-corrected
  Does read raw P-W subcode data from lead in
  Does return CD media catalog number
  Does return CD ISRC information
  Does support C2 error pointers
  Does not deliver composite A/V data

  Does play audio CDs
  Number of volume control levels: 15
  Does support individual volume control setting for each channel
  Does support independent mute setting for each channel
  Does not support digital output on port 1
  Does support digital output on port 2
  Does not send digital data LSB-first
  Does not set LRCK high for left-channel data
  Does not have valid data on falling edge of clock
  Length of data in BCLKs: 16

  Loading mechanism type: tray
  Does support ejection of CD via START/STOP command
  Does not lock media on power up via prevent jumper
  Does allow media to be locked in the drive via PREVENT/ALLOW command
  Is not currently in a media-locked state
  Does not support changing side of disk
  Does not have load-empty-slot-in-changer feature
  Does not support Individual Disk Present feature

  Maximum read  speed:  5645 kB/s (CD  32x, DVD  4x)
  Current read  speed:  5645 kB/s (CD  32x, DVD  4x)
  Maximum write speed:  2117 kB/s (CD  12x, DVD  1x)
  Current write speed:  2117 kB/s (CD  12x, DVD  1x)
  Buffer size in KB: 2048
  Copy management revision supported: 1
So, it tells me, Maximum write speed: 2117 kB/s (CD 12x, DVD 1x) Current write speed: 2117 kB/s (CD 12x, DVD 1x)
So for the "speed=" part, would I put: "speed=1" (without the quotes of course)?

I looked in the programs tab in k3b and all listed programs have a green check mark so I assumed that everything needed was there.
This is what I have:
cdrdao 1.2.0
cdrecord 2.1
dvd+rw-format 7.0
eMovix 0.9.0
growisofs 7.0
mkisofs 2.1
normalize 0.7.7
readcd 2.1
sox 12.17.7
transcode 1.0.2
vcdxbuild 0.7.23
vcdxminfo 0.7.23
vcdxrip 0.7.23


This unrelated part is weird, I just did that prcap command for my other drive, a Ricoh CD-R/RW drive and it told me,
Maximum read speed: 3528 kB/s (CD 20x, DVD 2x)
Current read speed: 3528 kB/s (CD 20x, DVD 2x)

Which is funny because above that, prcap told me,
Does not read DVD-ROM media
Does not read DVD-R media
Does not write DVD-R media
Does not read DVD-RAM media
Does not write DVD-RAM media
 
Old 01-07-2008, 01:16 AM   #30
JZL240I-U
Senior Member
 
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 18.3+19.3, MX-18, Mandrake
Posts: 4,387

Rep: Reputation: Disabled
Well, congrats . AFAIK you should have found out by K3b via cdrecord. I usually chose maximum speed (for uncritical burns) and K3b (or rather cdrecord) tunes it down to the drive and medium capabilities and prints that out in the log window.

The last paragraphs I don't really understand. The problem was with you Sony drive and now you complain that the Ricoh is faster?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
reading / writing problems dvd's edvdrmark Linux - Hardware 0 07-02-2006 09:35 AM
Another how to play dvd's question bunnyknight13 Linux - Newbie 10 06-26-2005 07:33 PM
Writing DVD's in Linux with file size over 2 gb haoscar Linux - Software 64 05-03-2005 05:01 AM
Question about writing to windows partitions ludwig W Linux - Newbie 5 04-20-2005 03:25 AM
Writing Drivers-question turls Programming 5 01-08-2004 11:44 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:43 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration