On Wed, 11 Jan 2017 11:52:30 -0500 Ric Moore sent:
> On 01/11/2017 03:02 AM, Thomas Schmitt wrote:
> > Hi,
> >
> > Charlie wrote:
> >> mount: /dev/sr0 is write-protected, mounting read-only
> >> mount: special device /dev/sr0 does not exist
> >
> > Does command dmesg report something about
On Wed, 11 Jan 2017 11:52:30 -0500 Ric Moore sent:
> Do you have a bios selection for the cdrom drive?? Last time this
> happened to me, replacement of the drive fixed the problem. Ric
After contemplation, my reply is:
Thanks Thomas and Ric,
Nothing in dmesg report and I will look at
On 01/11/2017 03:02 AM, Thomas Schmitt wrote:
Hi,
Charlie wrote:
mount: /dev/sr0 is write-protected, mounting read-only
mount: special device /dev/sr0 does not exist
Does command dmesg report something about "sr0" after this happened ?
Have a nice day :)
Do you have a bios selection for
Hi,
Charlie wrote:
> mount: /dev/sr0 is write-protected, mounting read-only
> mount: special device /dev/sr0 does not exist
Does command dmesg report something about "sr0" after this happened ?
Have a nice day :)
Thomas
On Wed, 11 Jan 2017 13:09:59 +1100 Charlie sent:
> Hello,
>
> Debian testing 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 (2016-07-18) x86_64
> GNU/Linux
>
> Suddenly have a CDROM problem:
> $ mount /media/cdrom
> mount: /dev/sr0 is write-protected, mounting read-only
> mount: special device
In gmane.linux.debian.user, you wrote:
lshw output in my case has no *cdrom entry at all. I rebooted, opened the
tray manually, inserted a Knoppix disk and set the BIOS to boot off the cdrom
drive. No luck - booted from the hard drive.
That sounds like a hardware problem with the cdrom
On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
No, it wasn't a hardware problem. After much travail with udev,
modprobe, interrupts, etc. and leariing more about dmesg output than I
care to know, I thought - well, no sr0? Then make one!
touch /dev/sr0
chown
On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
In gmane.linux.debian.user, you wrote:
lshw output in my case has no *cdrom entry at all. I rebooted, opened
the tray manually, inserted a Knoppix disk and set the BIOS to boot off
the cdrom drive. No luck - booted from the
On 2011-12-29 11:10:52 -0500, edj...@gmail.com wrote:
On Wednesday, December 28, 2011 11:37:15 PM Bill Marcum wrote:
In gmane.linux.debian.user, you wrote:
lshw output in my case has no *cdrom entry at all. I rebooted, opened
the tray manually, inserted a Knoppix disk and set the BIOS to
On Thu, 29 Dec 2011 13:01:54 -0500 edj...@gmail.com edj...@gmail.com
suggested this:
On Thursday, December 29, 2011 11:39:45 AM Vincent Lefevre wrote:
No, it wasn't a hardware problem. After much travail with udev,
modprobe, interrupts, etc. and leariing more about dmesg output
than I
On 2011-12-23 20:14:32 -0500, Ed Jabbour wrote:
On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:
Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
Why do I still get error msgs referring to scd0??
Perhaps because it is mentioned in /etc/fstab?
Running
On 12/23/2011 06:32 PM, Vincent Lefevre wrote:
On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:
On 12/23/2011 03:38 PM, Wayne Topa wrote:
On 12/23/2011 12:18 PM, Ed Jabbour wrote:
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use
On 2011-12-24 09:58:43 -0600, Hugo Vanwoerkom wrote:
On 12/23/2011 06:32 PM, Vincent Lefevre wrote:
Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
I believe that was after a udev update. It showed up in the changelog.
Indeed:
udev (175-1) unstable; urgency=low
[...]
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable to find or open device for: `cdrom'
On Fri, Dec 23, 2011 at 05:18:47PM GMT, Ed Jabbour wrote:
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block
On 12/23/2011 12:18 PM, Ed Jabbour wrote:
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block device
eject: tried to use `/dev/scd0' as device name but it is no block device
eject: unable
On 12/23/2011 03:38 PM, Wayne Topa wrote:
On 12/23/2011 12:18 PM, Ed Jabbour wrote:
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block
device
eject: tried to use `/dev/scd0' as device
On 2011-12-23 18:30:25 -0500, Wayne Topa wrote:
On 12/23/2011 03:38 PM, Wayne Topa wrote:
On 12/23/2011 12:18 PM, Ed Jabbour wrote:
CDROM tray will not respond to eject:
[Fri Dec 23] edj:~$ eject
eject: tried to use `/media/cdrom0' as device name but it is no block
On Friday, December 23, 2011 7:32:22 PM Vincent Lefevre wrote:
Yes, /dev/scd0 disappeared after a recent upgrade (after 2011-11-17).
Why do I still get error msgs referring to scd0??
Running lshw *as root* says which /dev files can be used.
In my case:
*-cdrom
Pessoal, Tenho uma máquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2.Aposmontar o CDROM pelo konqueror, este não desmonta, nem com umount -f, nem dando logout. Somente dando init 1 e posteriormente init 5 é que consegui desmontá-lo com umount. Alguém tem alguma idéia?
* Eduardo Braga ([EMAIL PROTECTED]) wrote:
Pessoal,
Tenho uma máquina com Debian (kernel 2.6.8) , placa mae M812, kde 3.2.
Apos montar o CDROM pelo konqueror, este não desmonta, nem com umount -f,
nem dando logout. Somente dando init 1 e posteriormente init 5 é que
Eduardo, aqui de vez em quando acontece isso, normalmente fao assim :
fuser -m /mnt/cdrom1
/mnt/cdrom 1234567x
kill -9 1234567x
Leve em considerao que aqui o meu cdrom o /mnt/cdrom1 e depois do
kill -9 voce coloca os numeros que reportou o uso do cdrom.
isso.
Eduardo Braga escreveu:
Eduardo,
Como outro colega falou, o problema é que o konqueror continua como que
usando o disco montado, e assim o umount dá a mensagem citada. Não é
mérito só do konqueror, já vi a mesma coisa com o nautilus. Você pode
dar um umount -l e vai resolver o problema, ele limpa as
referências ao
I am curious if anyone can clear up the following phenomena
for gnu tar on testing:
# tar --version
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU
Walter Tautz wrote:
I am curious if anyone can clear up the following phenomena
for gnu tar on testing:
# tar --version
tar (GNU tar) 1.13.25
Copyright (C) 2001 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it
Thus spake Eric Brooks ([EMAIL PROTECTED]):
I tried adding myself into the cdrom group but that did not solve the
problem.
Did you re-login after doing that?
--
Justin R. Miller [EMAIL PROTECTED]
View my website at http://codesorcery.net
Please encrypt email using key 0xC9C40C31
On Fri, Dec 14, 2001 at 12:47:10AM -0500, Justin R. Miller wrote:
Did you re-login after doing that?
No, I didn't. I'll try that. Thanks very much.
pgpPiRdSMV5Vy.pgp
Description: PGP signature
Eric Brooks wrote:
On Fri, Dec 14, 2001 at 12:47:10AM -0500, Justin R. Miller wrote:
Did you re-login after doing that?
No, I didn't. I'll try that. Thanks very much.
it's enough to do su - yourself (if you're using X and don't want to
restart it)
erik
Thus spake Erik Steffl ([EMAIL PROTECTED]):
it's enough to do su - yourself (if you're using X and don't want to
restart it)
That'll work for at least that console, but what about if you want to
start an app from the menu -- I don't think the new environment will be
picked up until you
Hi. I recently installed Alsa and I am working through getting sound
running. I can read data off my CDROM just fine. When I try to play
music off the CD I get the error:
Error accessing cdrom device. Please check to make sure cdrom drive
support is compiled into the kernel, and that you have
Hall Stevenson wrote:
okay, this.. is stupid question.. being completely spoilt
by Redhats simplicity.. i'm unaware of which device
/dev/cdrom was linked to. ..can someone, give me a hint?
Try
ls -l /dev/cdrom
How's that for simplicity ?? ;-)
You can even do it in completly
On Mon, 19 Feb 2001 03:29:37 +0100, William Leese
[EMAIL PROTECTED] wrote:
On Monday 19 February 2001 03:19, Hall Stevenson wrote:
okay, this.. is stupid question.. being completely spoilt
by Redhats simplicity.. i'm unaware of which device
/dev/cdrom was linked to. ..can someone, give me a
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
though not quite certain i think its master on the secondary channel. (makes
sense when using one HD and one CDROM-drive)
On Sun, Feb 18, 2001 at 03:23:50PM +0100, William Leese wrote:
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
Mines linked to hdc but yours may be different. Check -
$
On Tuesday 18 December 2001 07:20, ktb wrote:
On Sun, Feb 18, 2001 at 03:23:50PM +0100, William Leese wrote:
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
Mines linked
William Leese wrote:
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
William
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
William Leese wrote:
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
though not quite certain i think its master on the secondary channel. (makes
sense when using one HD
On Sun, Feb 18, 2001 at 03:05:16PM +, SamBozo Debian User wrote:
William Leese wrote:
okay, this.. is stupid question.. being completely spoilt by Redhats
simplicity.. i'm unaware of which device /dev/cdrom was linked to. ..can
someone, give me a hint?
At a terminal
MC
go to
Ah Cmd Line Magic ... I am continuly awestruck.
Now if I could just remember all this stuff.
But I go the next best thing
Linux in a Nutshell and Running Linux
race ya to see who's wares out 1st
Sam
ktb wrote:
On Sun, Feb 18, 2001 at 03:05:16PM +, SamBozo Debian User wrote:
William
okay, this.. is stupid question.. being completely spoilt
by Redhats simplicity.. i'm unaware of which device
/dev/cdrom was linked to. ..can someone, give me a hint?
Try
ls -l /dev/cdrom
How's that for simplicity ?? ;-)
Regards
Hall
On Monday 19 February 2001 03:19, Hall Stevenson wrote:
okay, this.. is stupid question.. being completely spoilt
by Redhats simplicity.. i'm unaware of which device
/dev/cdrom was linked to. ..can someone, give me a hint?
Try
ls -l /dev/cdrom
How's that for simplicity ?? ;-)
okay
After reinstalling my system (hamm) from scratch I have no /dev/cdrom
Is this obselete ? If yes then what is the name of the new device ?
I have tried ./MAKEDEV cdrom and got an error
Any ideas ?
George
/dev/cdrom is not a device, but a symbolic link to the cdrom device.
If you have
On Fri, Oct 16, 1998 at 11:08:17AM +0100,
G. Kapetanios wrote ...
After reinstalling my system (hamm) from scratch I have no /dev/cdrom
Is this obselete ? If yes then what is the name of the new device ?
/dev/cdrom is just a link to another device. Is your CDROM Drive
Atapi
Hallo Alan,
The same thing happened to me when I tried to unmount the cdrom while at
the same time my default directory is /cdrom or one of its subdirectories.
Make sure that you are in / when trying to unmount.
Johann.
This happens to me quite often: a floppy or a cd isn't being accessed,
but
44 matches
Mail list logo
