LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 08-09-2019, 02:10 PM   #1
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,637

Rep: Reputation: 130Reputation: 130
KDE K3b not detecting blank drive


There are a bunch of (confusing) threads on this all over the Internet. I want to burn an ISO to a blank DVD. I put the blank DVD in the drive and KDE pops up with: Available Devices > Blank DVD-R > Create file project with K3b. I click on that and it launches K3b. I navigate to the ISO image, select it and click on "Burn Image Directly". That gives me the details on the ISO image and K3b loads it into memory (progress bar).

Now the problem. Under "Burn Medium" it says, "Please insert an empty DVD or Blu-ray medium". The 'Start' is grayed out.

Why?

Do I need to belong to some group? I've ejected and re-inserted the disk several times, made no difference. Clearly, the system detects the blank DVD and prompts me to launch K3b.

Image is 4.6G. Running Slackware64 14.2
 
Old 08-09-2019, 02:16 PM   #2
termayto
LQ Newbie
 
Registered: Jan 2019
Distribution: Slackware64 14.2
Posts: 12

Rep: Reputation: 10
Run k3bsetup and select a burning group (i recommend 'cdrom')and click apply to allow it to fix permissions for the various related executables, it will prompt you for your root password to do this. Also of course make sure your user is in what ever group you choose. Remember that when ever you change your users groups changes only take effect on your next login.
 
Old 08-09-2019, 03:22 PM   #3
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 126

Rep: Reputation: 71
Did you try different disk? Sometimes poor quality disks became broken even before write.
 
Old 08-09-2019, 03:23 PM   #4
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,637

Original Poster
Rep: Reputation: 130Reputation: 130
Ran k3bsetup. Added me to group cdrom, rebooted. Start button still grayed out.

Yes, I've tried different disks.

Last edited by mfoley; 08-09-2019 at 03:24 PM.
 
Old 08-09-2019, 03:52 PM   #5
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 126

Rep: Reputation: 71
1. make sure you have "sg" module loaded
Code:
modprobe sg
2. check if cdrecord see disk
Code:
cdrecord -v -minfo
 
Old 08-09-2019, 04:07 PM   #6
termayto
LQ Newbie
 
Registered: Jan 2019
Distribution: Slackware64 14.2
Posts: 12

Rep: Reputation: 10
This is kind of a shot in the dark, but is this one of those cheap off-brand portable burners? If so, in k3b go to 'Settings' -> 'Configure K3b...', then in the 'Devices' section check the 'Write Capabilities' of your device . I bought one a while back that was branded as a dvd burner, it could read dvds but would actually only burn cds (brand name was Rioddas). That had me scratching my head for several days before I figured out I'd been scammed.
 
Old 08-10-2019, 12:23 AM   #7
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 752

Rep: Reputation: 162Reputation: 162
i never liked k3b, have used cli to copy/burn

try growisofs To burn an .iso file to a DVD
 
Old 08-10-2019, 01:33 AM   #8
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 156

Rep: Reputation: 106Reputation: 106
Tried another program for burning, e.g. brasero or simpleburn (both have SBo buildscripts for 14.2)?

Also, starting from terminal might give you some information on what's causing the issue.
 
Old 08-11-2019, 11:15 AM   #9
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,637

Original Poster
Rep: Reputation: 130Reputation: 130
Quote:
Originally Posted by Labinnah View Post
1. make sure you have "sg" module loaded
Code:
modprobe sg
2. check if cdrecord see disk
Code:
cdrecord -v -minfo
(I thought I already posted this ... guess I didn't) I ran 'modprobe sg', then 'cdrecord' as root:
Code:
# cdrecord -v -minfo
Cdrecord-ProDVD-ProBD-Clone 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling
TOC Type: 1 = CD-ROM
Linux sg driver version: 3.5.36
Using libscg version 'schily-0.9'.
SCSI buffer size: 32768
No target specified, trying to find one...
Using dev=1,0,0.
atapi: 1
Device type    : Removable CD-ROM
Version        : 5
Response Format: 2
Capabilities   : 
Vendor_info    : 'TSSTcorp'
Identifikation : 'CD/DVDW TS-H653L'
Revision       : '0414'
Device seems to be: Generic mmc2 DVD-R/DVD-RW/DVD-RAM.
Current: DVD-R sequential recording
Profile: DVD-R/DL sequential recording 
Profile: DVD-R/DL layer jump recording 
Profile: DVD+R/DL 
Profile: DVD+R 
Profile: DVD+RW 
Profile: DVD-RW sequential recording 
Profile: DVD-RW restricted overwrite 
Profile: DVD-RAM 
Profile: DVD-R sequential recording (current)
Profile: DVD-ROM 
Profile: CD-RW 
Profile: CD-R 
Profile: CD-ROM 
Profile: Removable Disk 
Using generic SCSI-3/mmc-2 DVD-R/DVD-RW/DVD-RAM driver (mmc_dvd).
Driver flags   : NO-CD DVD MMC-3 SWABAUDIO BURNFREE 
Supported modes: PACKET SAO LAYER_JUMP
Drive buf size : 1048576 = 1024 KB
cdrecord: Warning: Cannot read drive buffer.
cdrecord: Warning: The DMA speed test has been skipped.
Current Secsize: 2048
book type:       DVD-R, Version 2.0x -> 2.1 (2.5)
disc size:       120mm (0)
maximum rate:    Not specified (15)
number of layers:1
track path:      Parallel Track Path (0)
layer type:      Rewritable Area (2)
linear density:  0.267 �m/bit (0)
track density:   0.74 �m/track (0)
phys start:      196608 (0x30000) 
phys end:        0
end layer 0:     0
bca:             0
phys size:...    -196607
copyr prot type: 0
region mgt info: 0
last rma sector: 0
application code:64
physical code:   193
last rec address:16621272
part v./ext code:5/2
ind wr. power:   135
wavelength code: 13
write str. code: 13 87 88 90
Manufacturer:   'RITEKF1'
rzone size:         40
rzone number:       1
border number:      1
ljrs:               0
track mode:         4 copy: 0
damage:             0
reserved track:     0 blank: 1 incremental: 1 fp: 0
data mode:          1
lra valid:          0
nwa valid:          1
rzone start:        0
next wr addr:       0
free blocks:        2297888
blocking factor:    16
rzone size:         2297888
last recorded addr: 0
read compat lba:    0

    Capacity  Blklen/Sparesz.  Format-type  Type
     2297888             2048         0x00  Unformated or Blank Media
Mounted media class:      DVD
Mounted media type:       DVD-R sequential recording
Disk Is not erasable
data type:                standard
disk status:              empty
session status:           empty
BG format status:         none
first track:              1
number of sessions:       1
first track in last sess: 1
last track in last sess:  1
Disk Is unrestricted
Disk type: DVD, HD-DVD or BD

Track  Sess Type   Start Addr End Addr   Size
==============================================
    1     1 Blank  0          2298495    2298496         -1

Next writable address:              0
Remaining writable size:            2298496
Code:
# lsmod | grep sg
sg                     28250  0
Running cdrecord as user trying to burn:
Code:
$ cdrecord -v -minfo
Cdrecord-ProDVD-ProBD-Clone 3.01 (x86_64-unknown-linux-gnu) Copyright (C) 1995-2015 Joerg Schilling
TOC Type: 1 = CD-ROM
cdrecord: Operation not permitted. Warning: Cannot raise RLIMIT_MEMLOCK limits.
cdrecord: Cannot allocate memory. WARNING: Cannot do mlockall(2).
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Operation not permitted. WARNING: Cannot set RR-scheduler.
cdrecord: Permission denied. WARNING: Cannot set priority using setpriority().
cdrecord: WARNING: This causes a high risk for buffer underruns.
cdrecord: Insufficient 'file read' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'file write' privileges. You will not be able to open all needed devices.
cdrecord: Insufficient 'device' privileges. You may not be able to send all needed SCSI commands, this my cause various unexplainable problems.
cdrecord: Insufficient 'memlock' privileges. You may get buffer underruns.
cdrecord: Insufficient 'priocntl' privileges. You may get buffer underruns.
cdrecord: Insufficient 'network' privileges. You will not be able to do remote SCSI.
cdrecord: Permission denied. Cannot open '/dev/sg0'. Cannot open or use SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.
cdrecord: For possible transport specifiers try 'cdrecord dev=help'.
termayto: Not a portable burner. Don't know the manufacturer off-hand.

glorsplitz/kgha: Yes, I may have to try a different burner. I'll give K3b a last shot if the above gives some clues.
 
Old 08-11-2019, 04:34 PM   #10
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, Manjaro (for gaming)
Posts: 106

Rep: Reputation: 94
People jump through hoops to avoid setting cdrecord SUID.

-rwsr-xr-x 1 root root 484256 Apr 13 2018 /usr/bin/cdrecord*

chmod 4755 cdrecord will solve a lot of your problems. If it's your personal computer, you can make personal choices. I may get admonished for telling you that, but I'm not putting up with that bollocks on my systems (which are very personal... if anyone else touched them I'd have to kill them).

P.S. For some reason, I don't like growisofs. It seems to happily burn DVDs with i/o errors, often files can't be read even on the same drive that burned it. It must have poor error detection or something. This isn't just on one box or one burner, we're talking years for me. Recently, I thought I'd try it again thinking maybe by now it would have improved, and I had the same thing happening again too coincidentally. Not "coasters" and not every time, but unreadable areas whether it's a backup of files, or DVD movie playback. I use cdrecord for burning DVD images as well, moreover, modern K3B will just use cdrecord if growisofs isn't installed (unfortunately, my K3B from Trinity Desktop, KDE3, will not for DVD images).

Another burning program I liked was xfburn, which uses libburnia libraries. It worked well for me when I had it but I don't use XFCE anymore so it would be pointless dependencies. That works properly as a normal user without any BS.

Last edited by TheRealGrogan; 08-11-2019 at 05:09 PM.
 
Old 08-11-2019, 10:33 PM   #11
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,637

Original Poster
Rep: Reputation: 130Reputation: 130
TheRealGrogan: Tried the SUID thing on cdrecord. Start button still grayed out. Even before doing that I tried logging on as root and running k3b. Still no go.

Here's the interesting bit. I tried a different ISO file and my start button was active! The difference? The ISO I'm trying to burn is a Windows 10 iso. It is 4.6G. The one I just tried that gives a good start button was 2.6G. Perhaps the 4.6G is too big?

If so, k3b developers, how about a message to that effect instead of users having to spin their wheels uselessly!

Is it possible to burn a 4.6G iso image? According to my research, a DVD has a capacity of 4.7G. So what's the problem?
 
Old 08-11-2019, 11:38 PM   #12
mrapathy
Member
 
Registered: Nov 2005
Distribution: slackware
Posts: 238

Rep: Reputation: 48
official microsoft windows 10 iso from microsoft is not to big to burn. I had no problems burning it with k3b on current from March 2019
 
Old 08-12-2019, 01:14 AM   #13
Labinnah
Member
 
Registered: May 2014
Location: Łódź, Poland
Distribution: Slackware-current
Posts: 126

Rep: Reputation: 71
Quote:
Originally Posted by mfoley View Post
Perhaps the 4.6G is too big?
This is possible - empty DVD may vary in size little bit and Win image is lttle greater than your disk size. Try check in k3b advanced settings "allow overburn" or try double layer disk.


Alternatively you may check exacltly size of iso image and empty DVD:
Code:
   Capacity  Blklen/Sparesz.  Format-type  Type
     2297888             2048         0x00  Unformated or Blank Media
Your DVD has capacity 4706074624 bytes.
 
Old 08-12-2019, 01:30 PM   #14
TheRealGrogan
Member
 
Registered: Oct 2010
Location: Ontario, Canada
Distribution: Slackware, Manjaro (for gaming)
Posts: 106

Rep: Reputation: 94
Ahh, I have found that the "official Windows 10 DVD ISO" is too big to burn to a standard DVD. At least the last build was (don't know if there's a newer one or re-roll). I wish I'd have recognized your plight, I had the same thing happen. I tried it on two boxes with burners and different software, the image really was a hair bigger than a standard 4.7 Gb DVD-R. I needed it for a job right away, so I sacrificed an expensive double layer disk.

It took me by surprise when they did that, because I didn't think even Microsoft was that stupid (arrogant, really) to let that happen.

P.S. It was build 1809. (still have it)

Last edited by TheRealGrogan; 08-12-2019 at 01:40 PM.
 
1 members found this post helpful.
Old 08-12-2019, 05:23 PM   #15
mfoley
Senior Member
 
Registered: Oct 2008
Location: Columbus, Ohio USA
Distribution: Slackware
Posts: 1,637

Original Poster
Rep: Reputation: 130Reputation: 130
Quote:
Originally Posted by mrapathy View Post
official microsoft windows 10 iso from microsoft is not to big to burn. I had no problems burning it with k3b on current from March 2019
Doesn't help much.
Quote:
Originally Posted by TheRealGrogan View Post
Ahh, I have found that the "official Windows 10 DVD ISO" is too big to burn to a standard DVD. At least the last build was (don't know if there's a newer one or re-roll). I wish I'd have recognized your plight, I had the same thing happen. I tried it on two boxes with burners and different software, the image really was a hair bigger than a standard 4.7 Gb DVD-R. I needed it for a job right away, so I sacrificed an expensive double layer disk.

It took me by surprise when they did that, because I didn't think even Microsoft was that stupid (arrogant, really) to let that happen.

P.S. It was build 1809. (still have it)
Yes, it turns out that Microsoft is that stupid/arrogant. And why not? They have NO competition in the Office Workstation market, so what do they care (I've been trying to convert our office for two years, first to Linux, then to Mac. Can't be done). After posting this issue on a Microsoft website I got the response:
Quote:
Make sure you are using discs and software that can burn DVD-9 since the size of the files requires it.

The size exceeded the DVD-5 which is limited to 4.38 GB or roughly 4,700,00 bytes, since the ISO is larger you need to use the a disc that supports a larger format
And part of my response was:
Quote:
I think it's a bit irritating of Microsoft not to advise about the ISO size issue and say as part of the download instructions exactly what you said in your message about DVD-9, etc. Had that information been stated up-front I would have spent some time locating a DVD-9 burner program and not spinning my wheels trying different computers and different burners that didn't/couldn't work.
So, I solved the problem by returning the purchased ISO to Microsoft and bought a DVD at my local computer store (for $50 cheaper!).
Grrr!

Last edited by mfoley; 08-12-2019 at 05:25 PM.
 
2 members found this post helpful.
  


Reply

Tags
k3b


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
Feb17 - Slackware64 (14.2) Current - K3B not detecting blank disks arfon Slackware 13 03-26-2017 05:44 PM
[SOLVED] K3b recognises blank DVD, but 'Burn Image' dialog says 'Please insert blank media' Doug Hutcheson Linux - Software 5 03-03-2014 10:06 PM
USB devices stop detecting (or un-detecting). Mleahy Linux - Desktop 1 07-31-2011 02:08 AM
RedHat 9 is not detecting the LAN card, but Win'98 is detecting the LAN card SKYNAT Linux - Newbie 4 12-28-2007 10:25 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:56 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration