On Sun, Dec 19, 2004 at 05:56:45PM +0100, [EMAIL PROTECTED] wrote:
> Hi all,
> I have a problem with permissions to my cdrom devices. If I try to access
> them as an user just to playback audio-cds or mounting data-contents there
> is no problem at all.
>
> Even when I try to use them for rippin
Hi all,
I have a problem with permissions to my cdrom devices. If I try to access
them as an user just to playback audio-cds or mounting data-contents there
is no problem at all.
Even when I try to use them for ripping my cds to convert them to mp3 or
burning purposes (KAudioCreator or K3b) I g
Hi Adam
Thanks for your help! it worked!. From reading a bit
around , udev does do any loading like devfs did. But
it is actually much better I think.
Thanks for you help
Manu
--- Adam Aube <[EMAIL PROTECTED]> wrote:
> Manu wrote:
>
> > I upgraded to kernel 2.6.9 but in /dev I do not
> see
>
Manu wrote:
> I upgraded to kernel 2.6.9 but in /dev I do not see
> /dev/cdrom (/dev/hdd) and /dev/hdc (CD-WRITER)
>
> first one should map CD-ROM/CD et and the other one
> was mapping my CDRW.. how can I get these devices
> back?
I had this problem as well when I first started running udev. On
Also forgot to mention that I use udev.. could it be
because of configuration problem of udev?
I look at the configuration file cdsymlinks.conf
and here is what I see
---
# Output links for these types of devices.
# Allowed keywords are CD, CDR, CDRW, DVD, DVDRW,
DVDRAM, CDMRW
Hi
I upgraded to kernel 2.6.9 but in /dev I do not see
/dev/cdrom (/dev/hdd) and /dev/hdc (CD-WRITER)
first one should map CD-ROM/CD et and the other one
was mapping my CDRW.. how can I get these devices
back?
I cannot see them in /dev/ and so cannot mount them!
Thanks
Manu
Hi
I have a problem
following an update today, I do not have access to my
CDROM in nautilus as well as my burner in Eroaster
I looked in /dev
and I cannot see either my /dev/hdc (CDRW) and
/dev/hdd (DVD) or /dev/cdrom
is this a problem with the Kernel? What should I do?
I see them at the startup
On Mon, 22 Mar 2004 at 03:43:36 +, Kevin Mark wrote:
> Ciao Mauro,
> IIRC this may have something to do with the DISCOVER package. IIRC it
> makes links during the boot process.
> -Kev
Thank you _so_ much!
apt-get --purge remove discover
solved the problem. I think it was rather difficult to sp
On Fri, Mar 19, 2004 at 09:19:46AM +0100, Mauro Darida wrote:
> Recently I have discovered on my woody system this weird situation:
> ifi:/home/mario# ls -l /dev/cdrom
> lrwxrwxrwx1 root root 11 Mar 18 2004 /dev/cdrom ->
> /dev/cdrom0
> ifi:/home/mario# ls -l /dev/cdrom0
> lrwxrw
Recently I have discovered on my woody system this weird situation:
ifi:/home/mario# ls -l /dev/cdrom
lrwxrwxrwx1 root root 11 Mar 18 2004 /dev/cdrom ->
/dev/cdrom0
ifi:/home/mario# ls -l /dev/cdrom0
lrwxrwxrwx1 root root9 Mar 18 2004 /dev/cdrom0 ->
/dev/scd0
On Thu, Mar 22, 2001 at 12:49:49PM +0100, Alberto Garc?a wrote:
> I try to launch Netscape Communicator from GNOME and displays this error
> message:
> /dev/dsp not found.
> What?s that device used for? How can I "mount" it?
> Thanks in Advance. Yope
It's the sound device. If no sound driver is lo
I try to launch Netscape Communicator from GNOME
and displays this error message:
/dev/dsp not found.
What´s that device used for? How can I "mount"
it?
Thanks in Advance. Yope
Hi,
I try to run qw-client-svga as 'root' but I've no sound. I use ALSA on my linux
box: wave output works.
qw-client-svga is the QuakeWorld program from the latest quakeforge project.
I got the following error messages (using the strace program)
---
open("/dev/dsp", O_RDWR)=
I've recently encountered the following problem on my potato system. I
decided to try to run biff and see what it was like. When attempting
to run it, though, I receive:
ethereal:~> biff y
/dev/ttyp2: Operation not permitted
Exit 1
As I understand it, the /dev/ttyp devices are supposed to be chow
Quoting Debian Mail ([EMAIL PROTECTED]):
> > > The device is still /dev/lp0. lp1 and lp2 are still not configured,
> >
> > I read these words, but I don't understand what you mean by them.
>
> sos:~# tunelp /dev/lp0
> /dev/lp0 using polling
> sos:~# tunelp /dev/lp1
> /dev/lp1: Device not configur
odd, i pulled that module info from the help of kernel 2.0.36 :/
ohwell..maybe the docs on it are screwed.
[mailto:[EMAIL PROTECTED] ]--
Linux System Administrator http://www.firetrail.com/
Firetrail Internet Services Limited http://w
> > The device is still /dev/lp0. lp1 and lp2 are still not configured,
>
> I read these words, but I don't understand what you mean by them.
sos:~# tunelp /dev/lp0
/dev/lp0 using polling
sos:~# tunelp /dev/lp1
/dev/lp1: Device not configured
sos:~# tunelp /dev/lp2
/dev/lp2: Device not configured
> which module is loaded for the parallel port? i prefer static kernels but
lp
> from what i can see you would need parport_pc loaded and not parport. and
> for 2.2.x you gotta tell it to support parallel printers in character
> device section of config, again i always do my kernels as much stat
I assume you have only one printer port. LEAVE OUT
the lp=0xnnn and let the kernel probe for the printer.
Then look at what the kernel spits out, it will tell
you where the printer is. Try "dmesg | less" to see it.
=
Amateur Radio, when all else fails!
http://www.qsl.net/wa2mze
Debian Gnu
>I use Debian with kernel 2.0.36. All information I
>can get from the
>BIOS of my Intel PC about the parallel port ist, that
>io is 0x278 and
>that the mode is normal (other possible modes: ECP,
>EPP 1.9 and EPP
>1.7). So I say modprobe lp io=0x278. The printer is a
>HP LaserJet 4P
>connected troug
which module is loaded for the parallel port? i prefer static kernels but
from what i can see you would need parport_pc loaded and not parport. and
for 2.2.x you gotta tell it to support parallel printers in character
device section of config, again i always do my kernels as much static as i
can s
Quoting Debian Mail ([EMAIL PROTECTED]):
> > Should it? My machines running 2.0.36 are all printing on /dev/lp1
> > and that's to LPT1 and 0x378. I'm not sure why you're using 0x278
> > in the BIOS (conventionally LPT2).
>
> I changed it to 0x378 and said modprobe lp io=0x378
> The device is sti
> Should it? My machines running 2.0.36 are all printing on /dev/lp1
> and that's to LPT1 and 0x378. I'm not sure why you're using 0x278
> in the BIOS (conventionally LPT2).
I changed it to 0x378 and said modprobe lp io=0x378
The device is still /dev/lp0. lp1 and lp2 are still not configured,
and
Quoting Debian Mail ([EMAIL PROTECTED]):
> > I believe it is /dev/lp1=lpt1:. Are you sure you are using the correct
> > device ?
>
> Yes, /dev/lp0 should be the correct device. Also I can see the printer
> in a way, since tunelp /dev/lp0 only gives specific output if the
> printer is connected.
> I believe it is /dev/lp1=lpt1:. Are you sure you are using the correct
> device ?
Yes, /dev/lp0 should be the correct device. Also I can see the printer
in a way, since tunelp /dev/lp0 only gives specific output if the
printer is connected.
Stef
I believe it is /dev/lp1=lpt1:. Are you sure you are using the correct
device ?
-Original Message-
From: Debian Mail [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 06, 1999 10:11 AM
To: debian-user@lists.debian.org
Subject: problem with /dev/lp0
I use Debian with kernel 2.0.36. All
I use Debian with kernel 2.0.36. All information I can get from the
BIOS of my Intel PC about the parallel port ist, that io is 0x278 and
that the mode is normal (other possible modes: ECP, EPP 1.9 and EPP
1.7). So I say modprobe lp io=0x278. The printer is a HP LaserJet 4P
connected trough a bidir
27 matches
Mail list logo
