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 outp
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
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
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
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 cd
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
[..
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 `/me
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?
> > Runni
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
>
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
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 na
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 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 blo
13 matches
Mail list logo
