Re: Problem with /dev/scd[0-9] permissions
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 ripping my cds to convert them to mp3 or > burning purposes (KAudioCreator or K3b) I get an error: > > Access denied. > > This error accures only in this circumstances. Here my Configuration > > Debian Sarge > kernel 2.6.8.1-686-smp > I think there was a problem with kernel 2.6.8.* Check that possibility, I'm not sure. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with /dev/scd[0-9] permissions
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 get an error:
Access denied.
This error accures only in this circumstances. Here my Configuration
Debian Sarge
kernel 2.6.8.1-686-smp
Devices
Host: scsi1 Channel: 00 Id: 02 Lun: 00
Vendor: PIONEER Model: DVD-ROM DVD-305 Rev: 1.03
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi2 Channel: 00 Id: 02 Lun: 00
Vendor: PLEXTOR Model: CD-R PX-W1210S Rev: 1.06
Type: CD-ROM ANSI SCSI revision: 02
Host: scsi3 Channel: 00 Id: 00 Lun: 00
Vendor: PLEXTOR Model: DVDR PX-708A Rev: 1.08
Type: CD-ROM ANSI SCSI revision: 02
Permissions to these devices:
Permissions are set by /etc/init.d/udev by executing /etc/udev/udev.rules.
# permissions for SCSI CD devices
BUS="scsi", KERNEL="sr[0-9]*", SYSFS{type}="5", NAME="scd%n", MODE="0776",
GROUP
="cdrom", SYMLINK="sr%n"
BUS="scsi", KERNEL="sg[0-9]*", SYSFS{type}="5", NAME="%k", MODE="0776",
GROUP="c
drom"
Permissions are set correctly.
Anyone any ideas?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with /dev
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 > > /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 my system, > cdrom support is built as a module (ide-cd). The > modules was automatically > loaded when needed, but because it wasn't loaded > when udev started, udev > didn't know to create the links. After I ran (as > root): > > echo "ide-cd" >> /etc/modules > > and restarted udev, everything worked fine. See if > that works for you. > > Adam > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with /dev
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 my system, cdrom support is built as a module (ide-cd). The modules was automatically loaded when needed, but because it wasn't loaded when udev started, udev didn't know to create the links. After I ran (as root): echo "ide-cd" >> /etc/modules and restarted udev, everything worked fine. See if that works for you. Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with /dev
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, CDWMRW. # Other words are accepted but ignored. #OUTPUT="CD CDRW DVD DVDRW DVDRAM" # Whether to output numbered links. # 1 = output 'cdrom1', 'dvd1' etc. for other devices # 0 = don't output 'cdrom1', 'dvd1' etc. # We always output 'cdrom', 'dvd' etc. for the best-match devices. #NUMBERED_LINKS=1 --- any help on this would be appreciated! Thanks Manu --- Manu <[EMAIL PROTECTED]> wrote: > 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 > > > > __ > Do you Yahoo!? > Yahoo! Mail - Find what you need with new enhanced > search. > http://info.mail.yahoo.com/mail_250 > > > -- > To UNSUBSCRIBE, email to > [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact > [EMAIL PROTECTED] > > __ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
problem with /dev
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 __ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Problem with /dev and /dev/cdrom
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 being assigned to HDC and HDD but there is nothing in /dev I use Kernel 2.6.6 and gnome 2.6 Thanks Emmanuel __ Do you Yahoo!? Vote for the stars of Yahoo!'s next ad campaign! http://advision.webevents.yahoo.com/yahoo/votelifeengine/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with /dev/cdrom --) /dev/cdrom0 [solved]
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 spot where the problem was. You expert people always impress me... Saluti, Mauro. -- On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED. GnuPG key ID: 28A61681 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: problem with /dev/cdrom --) /dev/cdrom0
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 > lrwxrwxrwx1 root root9 Mar 18 2004 /dev/cdrom0 -> > /dev/scd0 > I tried to get rid of /dev/cdrom0 doing the following: > ifi:/home/mario# rm /dev/cdrom0 > ifi:/home/mario# rm /dev/cdrom > ifi:/home/mario# ln -s /dev/scd0 /dev/cdrom > ifi:/home/mario# ls -l /dev/cdrom > lrwxrwxrwx1 root root9 Mar 18 16:36 /dev/cdrom -> > /dev/scd0 > but after reboot I get the previous situation: > ifi:/home/mario# ls -l /dev/cdrom > lrwxrwxrwx1 root root 11 Mar 18 2004 /dev/cdrom -> > /dev/cdrom0 > How can I get rid of /dev/cdrom0 ?? > Saluti, Mauro. Ciao Mauro, IIRC this may have something to do with the DISCOVER package. IIRC it makes links during the boot process. -Kev signature.asc Description: Digital signature
problem with /dev/cdrom --) /dev/cdrom0
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 I tried to get rid of /dev/cdrom0 doing the following: ifi:/home/mario# rm /dev/cdrom0 ifi:/home/mario# rm /dev/cdrom ifi:/home/mario# ln -s /dev/scd0 /dev/cdrom ifi:/home/mario# ls -l /dev/cdrom lrwxrwxrwx1 root root9 Mar 18 16:36 /dev/cdrom -> /dev/scd0 but after reboot I get the previous situation: ifi:/home/mario# ls -l /dev/cdrom lrwxrwxrwx1 root root 11 Mar 18 2004 /dev/cdrom -> /dev/cdrom0 How can I get rid of /dev/cdrom0 ?? Saluti, Mauro. -- On this laptop no Windows system survives and LINUX POWER reigns UNLIMITED. GnuPG key ID: 28A61681 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Problem with /dev/dsp
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 loaded or if it's not correctly configured, you'll get this error. It only means you won't get sound :) -- ,---. > Name: Alson van der Meulen < > Personal: [EMAIL PROTECTED] < > School: [EMAIL PROTECTED]< `---' Sorry, we deleted that package last week... -
Problem with /dev/dsp
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
quake: problem with /dev/dsp
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)= -1 ENOSYS (Function not implemented)
open("/dev/dsp", O_RDWR)= -1 ENOSYS (Function not implemented)
open("/dev/dsp", O_RDWR)= -1 ENOSYS (Function not implemented)
open("/dev/dsp", O_RDWR)= -1 ENOSYS (Function not implemented)
open("/dev/dsp", O_RDWR)= -1 ENODEV (No such device)
write(2, "/dev/dsp: No such device\n", 25/dev/dsp: No such device
write(1, "Could not open /dev/dsp\n", 24) = 24
--
I have the following devices:
--
lrwxrwxrwx1 root root9 AUG 11 16:27 /dev/dsp -> /dev/dsp0
crw-rw1 root audio 14, 3 AUG 11 16:27 /dev/dsp0
crw-rw1 root audio 14, 19 AUG 11 16:27 /dev/dsp1
crw-rw1 root audio 14, 35 AUG 11 16:27 /dev/dsp2
crw-rw1 root audio 14, 51 AUG 11 16:27 /dev/dsp3
--
Thanks for any help
Attila
Sound card: SBLive
--
--
- Mail: [EMAIL PROTECTED]; Debian 2.2 Linux / 2.2.13 / exim-
- Get my PGP key: gpg --keyserver keys.pgp.com --recv-key 0x2cc33acb -
Problem with /dev/ttyp? devices
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 chowned to the user who logs in under them? Mine aren't. The permissions on all are as follows: crw-rw-rw-1 root tty3, 2 Jan 7 23:36 /dev/ttyp2 According to strace, both biff and mesg fail in chmod calls, thus increasing the likelihood of my problems being caused by the lack of chowning. Can anyone possibly point me in the right direction? This problem confuses me. Also, please CC me with any replies; I'm not subscribed to the list. Thanks.
Re: problem with /dev/lp0
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 configured > sos:~# tunelp /dev/lp2 > /dev/lp2: Device not configured OK, got your drift now. What does the kernel say when you modprobe lp? I think the problem may be your giving modprobe an argument. If you give ANY arguments, you must start at port 0, i.e. you'd need to put something like io=0x3bc,0x378 to get 378 to apply to port 1. Now you're using all the normal defaults, just try modprobing it without any extra info and see if it says lp1 at 0x378. _ > sos:~# cat /proc/ioports > ... > 0378-037f : lp Yes, that's ok but it registers any/all ports as lp, not lpN. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: problem with /dev/lp0
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://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- On Thu, 7 Oct 1999, Debian Mail wrote: > > 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 static as i > > can since it so rarely changes..only stuff like vmware, lm_sensors etc get > > to be modules. > > But parport and parport_pc only come with kernels > 2.1 and I am using > 2.0.26... > > Stef > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: problem with /dev/lp0
> > 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 sos:~# cat /proc/ioports ... 0378-037f : lp ... Stef
Re: problem with /dev/lp0
> 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 static as i > can since it so rarely changes..only stuff like vmware, lm_sensors etc get > to be modules. But parport and parport_pc only come with kernels > 2.1 and I am using 2.0.26... Stef
Re: problem with /dev/lp0
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 Linux, Live Free or . __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
problem with /dev/lp0
>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 bidirectional parallel cable. >Since printing trough >magicfilter does not work, I tried to generate a file >using gslj and >send that directly to /dev/lp0: >cat file.lj > /dev/lp0 >This takes about 4 seconds and produces no error. But >nothing is >printed and there is no error message on the printer. >tunelp /dev/lp0 -s gives the following: >/dev/lp0 status is 240, out of paper, on-line, error >but the printer is not out of paper and displays no >error. Also >printing works if the printer is connected to a >Windows NT machine. >tunelp /dev/lp0 tells me that lp0 is using polling. >lp1 and lp2 are >not configured. cat /proc/interrupts gives: > 0:8290233 timer > 1: 35309 keyboard > 2: 0 cascade > 3:188 + serial > 4: 73807 + serial > 8: 2 + rtc > 9: 116284 NE2000 >13: 1 math error >14:4628478 + ide0 >Why does printing not work? >From what I remember linux assignes the printer at 0x3f8 to lp0, 0x378 to lp1 and 0x278 to lp2. This would mean that your printer is actually on lp2! It may be possible to override this. Windows and dos assign lp0 to the first printer port address found, so the actual address of lp0 under windows and dos depends on how many printer ports you have and at which addresss. Linux by default just assigns them by a hard coded address. If you have two printer ports and you use the lp=0xnnn command in lilo or when assigning modules this prevents linux from using any other lp port (as a printer). Maybe you had a cd rom connected to a parallel port, you would need this command to reserve the extra port for that (by NOT specifing it as a lp). In short, if your LP is at 0x278, try changing to lp2 and see what happens. Any comments welcome! = Amateur Radio, when all else fails! http://www.qsl.net/wa2mze Debian Gnu Linux, Live Free or . __ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com
Re: problem with /dev/lp0
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 since it so rarely changes..only stuff like vmware, lm_sensors etc get to be modules. nate [mailto:[EMAIL PROTECTED] ]-- Linux System Administrator http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- On Wed, 6 Oct 1999, Debian Mail wrote: > 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 bidirectional parallel cable. Since printing trough > magicfilter does not work, I tried to generate a file using gslj and > send that directly to /dev/lp0: > cat file.lj > /dev/lp0 > This takes about 4 seconds and produces no error. But nothing is > printed and there is no error message on the printer. > tunelp /dev/lp0 -s gives the following: > /dev/lp0 status is 240, out of paper, on-line, error > but the printer is not out of paper and displays no error. Also > printing works if the printer is connected to a Windows NT machine. > tunelp /dev/lp0 tells me that lp0 is using polling. lp1 and lp2 are > not configured. cat /proc/interrupts gives: > > 0:8290233 timer > 1: 35309 keyboard > 2: 0 cascade > 3:188 + serial > 4: 73807 + serial > 8: 2 + rtc > 9: 116284 NE2000 > 13: 1 math error > 14:4628478 + ide0 > > Why does printing not work? > > Any comments welcome! > > Stef > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
Re: problem with /dev/lp0
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 still /dev/lp0. lp1 and lp2 are still not configured, I read these words, but I don't understand what you mean by them. If you're running a 2.0.x kernel, 0x378 means minor number 1. You can only change it by editing drivers/char/lp.c which I assume you haven't. Minor number 0 goes to 0x3bc and I'm guessing you really don't want that. > and tunelp still gives the same output. So I guess it does not matter > whether 0x278 or 0x378 is used. Unfortunately. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: problem with /dev/lp0
> 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 tunelp still gives the same output. So I guess it does not matter whether 0x278 or 0x378 is used. Unfortunately. Stef
Re: problem with /dev/lp0
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. 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). OTOH my machines running 2.2.10 all print on /dev/lp0 (but that's still LPT1 and 0x378). This is similar to many other people who have reported their configurations when surprised by the change from /dev/lp1 to /dev/lp0 caused by migration to 2.2.x kernels. Cheers, -- Email: [EMAIL PROTECTED] Tel: +44 1908 653 739 Fax: +44 1908 655 151 Snail: David Wright, Earth Science Dept., Milton Keynes, England, MK7 6AA Disclaimer: These addresses are only for reaching me, and do not signify official stationery. Views expressed here are either my own or plagiarised.
Re: problem with /dev/lp0
> 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
RE: problem with /dev/lp0
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 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 bidirectional parallel cable. Since printing trough magicfilter does not work, I tried to generate a file using gslj and send that directly to /dev/lp0: cat file.lj > /dev/lp0 This takes about 4 seconds and produces no error. But nothing is printed and there is no error message on the printer. tunelp /dev/lp0 -s gives the following: /dev/lp0 status is 240, out of paper, on-line, error but the printer is not out of paper and displays no error. Also printing works if the printer is connected to a Windows NT machine. tunelp /dev/lp0 tells me that lp0 is using polling. lp1 and lp2 are not configured. cat /proc/interrupts gives: 0:8290233 timer 1: 35309 keyboard 2: 0 cascade 3:188 + serial 4: 73807 + serial 8: 2 + rtc 9: 116284 NE2000 13: 1 math error 14:4628478 + ide0 Why does printing not work? Any comments welcome! Stef -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
problem with /dev/lp0
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 bidirectional parallel cable. Since printing trough magicfilter does not work, I tried to generate a file using gslj and send that directly to /dev/lp0: cat file.lj > /dev/lp0 This takes about 4 seconds and produces no error. But nothing is printed and there is no error message on the printer. tunelp /dev/lp0 -s gives the following: /dev/lp0 status is 240, out of paper, on-line, error but the printer is not out of paper and displays no error. Also printing works if the printer is connected to a Windows NT machine. tunelp /dev/lp0 tells me that lp0 is using polling. lp1 and lp2 are not configured. cat /proc/interrupts gives: 0:8290233 timer 1: 35309 keyboard 2: 0 cascade 3:188 + serial 4: 73807 + serial 8: 2 + rtc 9: 116284 NE2000 13: 1 math error 14:4628478 + ide0 Why does printing not work? Any comments welcome! Stef
