I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write. The program doesn't even recognise that there is a blank disk in the burner. This applies to both the CD and the DVD burner. # ls -l /dev/sr* brw-rw----+ 1 root cdrom 11, 0 Dec 23 15:53 /dev/sr0 brw-rw----+ 1 root cdrom 11, 1 Dec 23 08:59 /dev/sr1 # lsattr /dev/sr* lsattr: Operation not supported While reading flags on /dev/sr0 lsattr: Operation not supported While reading flags on /dev/sr1 I've tried various devices and currently have # lsscsi [0:0:0:0] disk ATA WDC WD10EALS-00Z 1D05 /dev/sda [0:0:1:0] cd/dvd LG DVD-ROM DRD8160B 1.01 /dev/sr0 [1:0:0:0] cd/dvd PBDS CD-ROM DH-48N1S BD11 /dev/sr1 Yes, I am in group cdrom. Dmesg reports this and nothing else about them [ 11.524687] sr 0:0:1:0: [sr0] scsi3-mmc drive: 0x/48x cd/rw xa/form2 cdda tray [ 11.524692] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 11.524934] sr 0:0:1:0: Attached scsi CD-ROM sr0 [ 11.536505] sr 1:0:0:0: [sr1] scsi3-mmc drive: 0x/48x cd/rw xa/form2 cdda tray [ 11.536800] sr 1:0:0:0: Attached scsi CD-ROM sr1 I see nothing in the BIOS that would prevent these devices being accessed in write mode # uname -a Linux Mainbox 3.18.1-1.g5f2f35e-desktop #1 SMP PREEMPT Wed Dec 17 18:20:30 UTC 2014 (5f2f35e) x86_64 x86_64 x86_64 GNU/Linux # cat /etc/os-release NAME=openSUSE VERSION="13.1 (Bottle)" VERSION_ID="13.1" PRETTY_NAME="openSUSE 13.1 (Bottle) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:13.1" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://opensuse.org/" ID_LIKE="suse" # lsmod | grep rom cdrom 60734 2 sr_mod,pktcdvd Dell Optiplex 755 I'm wondering if there is some PolicyKit feature that is blocking access? It still blocks accesses when I run K3B as root. I have no problem reading CDs or DVDs. I've googled and not found anything that seems specific to this case. Lots of stuff about access and missing programs, none of which applies here. As far as I can tell the burners -- and yes I'm sure they are burners, I've swapped around as part of the problem determination and these work in other machines -- Let me repeat: the drive is not recognising the blank. If I put a music cd or a an old backup DVD in I get the KDE notifier popup offering me the various choices. When I put a blank in I expect a popup offering to start k3b. That isn't happening. So, "hardware" you say. Well I've swapped that hardware and know it works elsewhere. I know the reader functions work Ok and the notifier works OK. I've run out of ideas. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/24/2014 10:03 AM, Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write.
Let me repeat: the drive is not recognising the blank.
If I put a music cd or a an old backup DVD in I get the KDE notifier popup offering me the various choices.
When I put a blank in I expect a popup offering to start k3b. That isn't happening.
So, "hardware" you say. Well I've swapped that hardware and know it works elsewhere. I know the reader functions work Ok and the notifier works OK.
I've run out of ideas.
Then there's this, which seems to hold even as I swap in and out different burners # cat /proc/sys/dev/cdrom/info CD-ROM information, Id: cdrom.c 3.20 2003/12/17 drive name: sr1 sr0 drive speed: 48 48 drive # of slots: 1 1 Can close tray: 1 1 Can open tray: 1 1 Can lock tray: 1 1 Can change speed: 1 1 Can select disk: 0 0 Can read multisession: 1 1 Can read MCN: 1 1 Reports media changed: 1 1 Can play audio: 1 1 Can write CD-R: 0 0 <==== Can write CD-RW: 0 0 <==== Can read DVD: 0 1 Can write DVD-R: 0 0 <==== Can write DVD-RAM: 0 0 <==== Can read MRW: 1 1 Can write MRW: 1 1 Can write RAM: 1 1 Again, beyond my expertise, but could the udisk rules be doing something to account for this? -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/12/2014 16:14, Anton Aylward a écrit :
Again, beyond my expertise, but could the udisk rules be doing something to account for this?
I guess they worked before? try a live dvd to see if the result is the same I also suppose you tried as root? what opensuse version? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/24/2014 10:24 AM, jdd wrote:
Le 24/12/2014 16:14, Anton Aylward a écrit :
Again, beyond my expertise, but could the udisk rules be doing something to account for this?
I guess they worked before?
Yes. That's part of ths issue.
try a live dvd to see if the result is the same
There is no problem booting from or reading from a DVD. I'll see what LiveCDs I have ..
I also suppose you tried as root?
what opensuse version?
Yes, all in my oringal post. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-24 16:27, Anton Aylward wrote:
On 12/24/2014 10:24 AM, jdd wrote:
Le 24/12/2014 16:14, Anton Aylward a écrit :
I guess they worked before?
Yes. That's part of ths issue.
Try boot with a previous kernel. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 12/24/2014 10:29 AM, Carlos E. R. wrote:
Try boot with a previous kernel.
Good idea! I went back to 3.11.10 ... But /proc/sys/dev/cdrom/info reports the same It might still be a udisk or some other privilege issue. I'll try jdd's idea of live boots, but its getting to look like a h/w or bios issue and since there don't seem to be any bios settings... And as i say, the h/w works elsewhere. Oh, yes, wiggle the cables etc etc. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-24 16:48, Anton Aylward wrote:
On 12/24/2014 10:29 AM, Carlos E. R. wrote:
Try boot with a previous kernel.
Good idea!
I went back to 3.11.10 ... But /proc/sys/dev/cdrom/info reports the same It might still be a udisk or some other privilege issue.
I don't think so... /proc is "written" by the kernel. Or so I believe.
Oh, yes, wiggle the cables etc etc.
Plug a different cable, plug it into a different connector, hopefully on a different "chip". Some boards have more than one sata chip. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On December 24, 2014 3:10:08 PM EST, "Carlos E. R."
On 2014-12-24 16:48, Anton Aylward wrote:
On 12/24/2014 10:29 AM, Carlos E. R. wrote:
Try boot with a previous kernel.
Good idea!
I went back to 3.11.10 ... But /proc/sys/dev/cdrom/info reports the same It might still be a udisk or some other privilege issue.
I don't think so... /proc is "written" by the kernel. Or so I believe.
I think "populated by the kernel" might be a better way to express it. /proc is a view into key kernel data structures themselves as I understand it. Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-25 15:12, Greg Freemyer wrote:
On December 24, 2014 3:10:08 PM EST, "Carlos E. R." <> wrote:
I don't think so... /proc is "written" by the kernel. Or so I believe.
I think "populated by the kernel" might be a better way to express it. /proc is a view into key kernel data structures themselves as I understand it.
Yes, that's a more appropriate wording. I know what /proc is, but I couldn't find the correct word. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 12/24/2014 10:24 AM, jdd wrote:
I guess they worked before?
try a live dvd to see if the result is the same
I tried some suseLive back to 11.3 and a couple of FedoraLive, 15 and 17 Same results. So it has to be hardware or BIOS. I can't see anything in the BIOS specific to CD/DVD. If its for the whole disk/scsi controller then why isn't it affecting the hard drive? -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/12/2014 18:47, Anton Aylward a écrit :
I tried some suseLive back to 11.3 and a couple of FedoraLive, 15 and 17
Same results.
So it has to be hardware or BIOS.
I can't see anything in the BIOS specific to CD/DVD. If its for the whole disk/scsi controller then why isn't it affecting the hard drive?
I'm stuck, as the disk is :-( do you have any other spare writer, to try? usb one? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/24/2014 01:03 PM, jdd wrote:
Le 24/12/2014 18:47, Anton Aylward a écrit :
I tried some suseLive back to 11.3 and a couple of FedoraLive, 15 and 17
Same results.
So it has to be hardware or BIOS.
I can't see anything in the BIOS specific to CD/DVD. If its for the whole disk/scsi controller then why isn't it affecting the hard drive?
I'm stuck, as the disk is :-(
do you have any other spare writer, to try? usb one?
I've tried a couple of other DVD burners with the same result. I can't see anything in the BIOS pertaining to the burners that might apply. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 24/12/2014 19:10, Anton Aylward a écrit :
On 12/24/2014 01:03 PM, jdd wrote:
do you have any other spare writer, to try? usb one?
I've tried a couple of other DVD burners with the same result.
so not a dvd hardware problem, so cable or mobo well... sata or IDE? if sata you may be able to test on a different plug (there are usually 4) - try also different cable any jumper on the mobo? just guesses :-( jdd and happy Christmas anyway :-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 02:03 AM, Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write.
The program doesn't even recognise that there is a blank disk in the burner.
This applies to both the CD and the DVD burner.
[pruned]
When I put a blank in I expect a popup offering to start k3b. That isn't happening.
So, "hardware" you say. Well I've swapped that hardware and know it works elsewhere. I know the reader functions work Ok and the notifier works OK.
I've run out of ideas.
This has happened to me several times in the past. Always caused by one of 3 things: (a) putting in a blank CD/DVD which is bad; (b) putting in the wrong sized disc for what is required; eg when k3b 'knows' that it is to burn 1.0GB of data but a 700MB CD is inserted; (c) an earlier attempt to burn to a disc failed but some data has been written to the directory sectors and you then try and reuse the disc thinking that it is still a "clean" disc. BTW, after you have inserted such a disc did you look in DEVICE>MEDIA INFO? BC -- Using openSUSE 13.1, KDE 4.14.3 & kernel 3.18.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/24/2014 09:07 PM, Basil Chupin wrote:
On 12/25/2014 02:03 AM, Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write.
Please see my later posts about the contents of /proc/sys/dev/cdrom/info
I've run out of ideas.
This has happened to me several times in the past. Always caused by one of 3 things:
(a) putting in a blank CD/DVD which is bad;
I had previously tried a couple more with the same result. I now know it has nothing to do with the media.
(b) putting in the wrong sized disc for what is required; eg when k3b 'knows' that it is to burn 1.0GB of data but a 700MB CD is inserted;
I have both a CDROM and DVD burner and tried in both.
(c) an earlier attempt to burn to a disc failed but some data has been written to the directory sectors and you then try and reuse the disc thinking that it is still a "clean" disc.
Nope. I worked though a pile of 'unused' from the spindle I purchased.
BTW, after you have inserted such a disc did you look in DEVICE>MEDIA INFO?
K3B refused to even acknowledge there was a blank disk there. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 04:29 PM, Anton Aylward wrote:
On 12/24/2014 09:07 PM, Basil Chupin wrote:
On 12/25/2014 02:03 AM, Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write. Please see my later posts about the contents of /proc/sys/dev/cdrom/info
I've run out of ideas. This has happened to me several times in the past. Always caused by one of 3 things:
(a) putting in a blank CD/DVD which is bad; I had previously tried a couple more with the same result. I now know it has nothing to do with the media.
(b) putting in the wrong sized disc for what is required; eg when k3b 'knows' that it is to burn 1.0GB of data but a 700MB CD is inserted; I have both a CDROM and DVD burner and tried in both.
(c) an earlier attempt to burn to a disc failed but some data has been written to the directory sectors and you then try and reuse the disc thinking that it is still a "clean" disc. Nope. I worked though a pile of 'unused' from the spindle I purchased.
BTW, after you have inserted such a disc did you look in DEVICE>MEDIA INFO? K3B refused to even acknowledge there was a blank disk there.
OK. I've just read over your original post. Firstly, what happens if you start k3b FIRST and then try and insert a blank disc? Secondly, you have a "CD burner" [sr0] and a "DVD burner" [sr1]. As far a I know - which has always been the case with me and I only have the one burner, DVDRW - the DVD burner will also burn CDs so why do you have a burner for CDs and another for DVDs? k3b confused? BC -- Using openSUSE 13.1, KDE 4.14.3 & kernel 3.18.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 12:47 AM, Basil Chupin wrote:
OK. I've just read over your original post.
Always a good start.
Firstly, what happens if you start k3b FIRST and then try and insert a blank disc?
I get the popup notice about there not being a writer as soon as k3b starts whether there is a disk in either of the burners or not. Since the contents of /proc/sys/dev/cdrom/info says that neither can write, and I'm told that is generated by the kernel, this makes sense.
Secondly, you have a "CD burner" [sr0] and a "DVD burner" [sr1].
As far as I can tell its the other way round.
As far a I know - which has always been the case with me and I only have the one burner, DVDRW - the DVD burner will also burn CDs so why do you have a burner for CDs and another for DVDs? k3b confused?
That's how the box came. My next test is going to be conect only one at a time. I don't know if its useful but starting k3b from the CLI results in this
k3b Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath) k3b(9252)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! anton@Mainbox:/proc/sys/dev> QCoreApplication::postEvent: Unexpected null receiver k3b(9252) KDirWatch::removeDir: doesn't know ""
-- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-12-25 03:07, Basil Chupin wrote:
On 12/25/2014 02:03 AM, Anton Aylward wrote:
This has happened to me several times in the past. Always caused by one of 3 things:
(a) putting in a blank CD/DVD which is bad;
Not in this case. He gets: # cat /proc/sys/dev/cdrom/info Can write CD-R: 0 0 <==== Can write CD-RW: 0 0 <==== Can write DVD-R: 0 0 <==== Can write DVD-RAM: 0 0 <==== Me, with an already burned disk, I get: Can write CD-R: 1 Can write CD-RW: 1 Can write DVD-R: 1 Can write DVD-RAM: 1 Can write MRW: 1 Can write RAM: 1 This output is not influenced by the disk. It is his kernel which says the unit can not write. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse. Is there a fix for this, or maybe a kernel module problem? All else is A.OK Touchpad Driver (Elan, Synaptics) for 64-bit Windows exe *64.5 MB* Windows 8.1 (64-bit) Synaptics_18.0.7.87 Elan_11.4.49.1_WHQL 12/10/2014 Supported Systems - Lenovo G40-80, G50-80 Supported Operating Systems - Windows 8.1 (64-bit) Manufacturer - Elan, Synaptics http://support.lenovo.com/us/en/products/laptops-and-netbooks/lenovo-g-serie... -- don't use google mail. It sucks ~ -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 25/12/2014 18:28, Ruben Safir a écrit :
We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
All else is A.OK
did you configure in kde system config? jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 12:37 PM, jdd wrote:
Le 25/12/2014 18:28, Ruben Safir a écrit :
We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
All else is A.OK
did you configure in kde system config?
jdd
not yet. Idon't see where is can be configured. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 12:43 PM, Ruben.Safir wrote:
On 12/25/2014 12:37 PM, jdd wrote:
Le 25/12/2014 18:28, Ruben Safir a écrit :
We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
All else is A.OK
did you configure in kde system config?
jdd
not yet. Idon't see where is can be configured.
I think it is a modules problem -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Dec 25, 2014 at 10:28 AM, Ruben Safir
We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
Can you please post the output of "cat /proc/bus/input/devices"? Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Brandon Vincent
On Thu, Dec 25, 2014 at 10:28 AM, Ruben Safir
wrote: We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
Can you please post the output of "cat /proc/bus/input/devices"?
Can we please break this off and start a new thread rather than confusing and garbling the "original" thread "K3b won't write". -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Dec 25, 2014 at 11:32:55AM -0700, Brandon Vincent wrote:
On Thu, Dec 25, 2014 at 10:28 AM, Ruben Safir
wrote: We picked up several new Lenovo Laptop G50-80 and it works just dandy, however, the touchpads left mouse button seems to fail under opensuse.
Is there a fix for this, or maybe a kernel module problem?
Can you please post the output of "cat /proc/bus/input/devices"?
Actually, there are a few problems with this system, more than I thought. I hate this. I had a young man who wanted a laptop for STEAM and I found these on sale and they are pretty cheap, with A6, 6gigs or ram and a terabyte drive for $350 dollars. I arrainged for them but when I installed opensuse 13.2, there are just too many problems and the kid won't use it. Actually, looking at it, I don't blame him. kwallet won't get out of the damn way. That is a design that is totlally broken. You are going to force everyone to use this thing? The graphics aren't working right. The redrawn is black, so for example if you use wmaker the menus show up all black without fonts until you pass over them, and then they light up, and when you move objects across the screen, it makes a back streaking shodow that erases the screen. Obviously something about the video card is not right. KDE is slow as hell with a huge amount of ram and very fast quad cpu. Steam installs but just freezes on the screen. I wish he didn't want like a freshly minted laptop... but he wanted to play games on it. Then there is the touch screen problem. It will likely take months to shake it out, and he has no patience, but honestly, even I get fustrated with it. I installed opensuse with systemd because it usually has the best desktop and laptop configutation on the market.... but this is bust. Meanwhile, I go the $200 asus laptop working full tilt at this point. Ruben
Brandon Vincent -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and and extermination camps, but incompatible with living as a free human being. -RI Safir 2013 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 24 Dec 2014 10:03:59 -0500 Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write.
8< snipped >8
I've tried various devices and currently have # lsscsi [0:0:0:0] disk ATA WDC WD10EALS-00Z 1D05 /dev/sda [0:0:1:0] cd/dvd LG DVD-ROM DRD8160B 1.01 /dev/sr0 [1:0:0:0] cd/dvd PBDS CD-ROM DH-48N1S BD11 /dev/sr1
Hi Anton and Merry Christmas! If the device is, in fact, an LG DRD-8160B, according to the owner's manual* it's just a reader, circa 2001, not a writer. hth & regards, Carl http://www.manualslib.com/manual/699130/Lg-Drd-8160b.html#manual -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 12/25/2014 09:05 AM, Carl Hartung wrote:
On Wed, 24 Dec 2014 10:03:59 -0500 Anton Aylward wrote:
I don't think the problem is with K3b, but it reports the CDROM and DVD drives as not being able to write.
8< snipped >8
I've tried various devices and currently have # lsscsi [0:0:0:0] disk ATA WDC WD10EALS-00Z 1D05 /dev/sda [0:0:1:0] cd/dvd LG DVD-ROM DRD8160B 1.01 /dev/sr0 [1:0:0:0] cd/dvd PBDS CD-ROM DH-48N1S BD11 /dev/sr1
Hi Anton and Merry Christmas!
If the device is, in fact, an LG DRD-8160B, according to the owner's manual* it's just a reader, circa 2001, not a writer.
hth & regards,
Carl
http://www.manualslib.com/manual/699130/Lg-Drd-8160b.html#manual
${EXPLETIVE} !! Thank you. Stupid of me for just accepting what I was given without checking! "Trust, but verify" -- and I didn't. Now I've verified that DH-48N1S isn't a burner either! Not much I can do today; next week someone is going to lambasted and I'm going shopping. Merry Happy's to you and family :-) -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (11)
-
Anton Aylward
-
Basil Chupin
-
Brandon Vincent
-
Carl Hartung
-
Carlos E. R.
-
Greg Freemyer
-
jdd
-
Patrick Shanahan
-
ruben
-
Ruben Safir
-
Ruben.Safir