headers
Nate | 1 Apr 2002 18:57

Re: [PARPORT] problem with DCC

What kind of Cable are you using?

Some cables are wired differently so that input lines go to output lines and
viceversa.
It is the same theory as Null Modem Cable.

If you have a straight through printer type cable it will not work.  You
have to have the right kind of cable, like a lap-link style cable.

Nate

----- Original Message -----
From: "vinod m. vanjeri" <vinodvanjeri <at> rediffmail.com>
To: <linux-parport <at> torque.net>
Sent: Sunday, March 31, 2002 6:20 AM
Subject: [PARPORT] problem with DCC

> hi,
>    I tried to connect the two windows 98 systems by means of
> Direct Cable Connection. I have installed all the software
> necessory for it & all the settings are proper
> & my 25 pin D-sub connector cable also has no problem but still
> the computers are not connecting giving the errors.
>
> error on the geust computer is
> "can't find the host computer make sure you have run DCC on the
> host computer & connect your cable to both computer"
>
> error on the host computer is
> "is the geust computer running"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Luc Pardon | 2 Apr 2002 21:06
Picon
Favicon

[PARPORT] Where are my interrupts ?

Hello list,

  I'm writing a driver for a custom-made piece of hardware (basically an
interface card) attached to the parallel port. 

  It works fine, i.e. the driver compiles, loads, .. and I can read and
write and make the lights on the card go on and off. Cool.

  Now I try to enable interrupts, but no go. I just want the base SPP
acknowledge, no fancy EPP/ECP handshakes. But no matter how much I
switch pin 10 on the parallel port up and down (between 0 and +5V), no
interrupts. 

  This is on RedHat Linux 7.2, uname -r -> 2.4.7-10

  What I'm getting thus far:

  * the cable is OK, it does deliver pin 10 into the PC's serial port

  * the parallel port is configured in the BIOS as 0x378, irq 7, SPP
mode (tried EPP etc, no change) on an oldish PC.

  * parport_pc loads with options from /etc/modules.conf, and uses irq 7

  * /proc/interrupts shows irq 7 in use by parport0, but counter at 0

  * "dmesg | grep parport" says (with BIOS in ECP/EPP mode):

  parport0: PC-Style at 0x378 (0x778), irq 7 (PCSPP, TRISTATE, COMPAT,
EPP, ECP)
(Continue reading)

Permalink | Reply | 1 comment |
headers
Stefan Riha | 3 Apr 2002 23:26
Picon
Picon

[PARPORT] IO errors

Ich möchte meinen Freecom portable CD-RW Brenner (2x2x24) auch unter Linux
benutzen. Der Brenner ist mit einen Freecom parallel port cable an den Rechner
angeschlossen.
An diesen Computer ist nur der Brenner angeschlossen.
Zu Testzwecken habe ich auf diesen Rechner RedHat 6.2 Standart installiert.
Nun wollte ich den Brenner wie auf ihrer webseite beschrieben ist zum laufen
bringen.
Aber ich erhalte immer wieder den selben fehler.

Nun eine genaue ablauf beschreibung:

#lsmod
Module        Size    Used    by
lockd         31912    1      (autoclean)
sunrpc        53604    1      (autoclean) [locked]
rtl8139       12132    1      (autoclean)

#modprobe paride
paride: version 1.04 installed

#modprobe friq
paride: friq registered as protocol 0

#modprobe pcd
pcd: pcd version 1.07, major 46, nice 0
pcd0: Sharing parport0 at 0x378
pcd0: friq 1.01, Freecom IQ ASCI-2 adapter at 0x378, mode 4 (EPP-32), delay
1
pcd0: Master R/RW 2x2x24
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tim Waugh | 2 Apr 2002 21:58
Picon
Favicon
Gravatar

Re: [PARPORT] Where are my interrupts ?

On Tue, Apr 02, 2002 at 09:06:05PM +0200, Luc Pardon wrote:

>   * the cable is OK, it does deliver pin 10 into the PC's serial port

Serial port? ;-)

You have to set the IntEn bit in the parallel port control register.
It's 0x10 I think (1 for enable).

Tim.
*/
Permalink | Reply | 0 comments |
headers
Igor Bujna | 4 Apr 2002 18:57
Picon

[PARPORT] Max.paralel ports

Hi,
i have kernel version 2.2.19 or 2.4.x and want you ask how much of 
paralel conections i can have on my linux box.
Thank you

--  To unsubscribe, send mail to: linux-parport-request <at> torque.net --
--  with the single word "unsubscribe" in the body of the message. --
Permalink | Reply | 0 comments |
headers
Filipe Freire | 5 Apr 2002 19:36
Picon

[PARPORT] ppSCSI-0.91.patch in newer kernels

Hallo!

I have slackware 8 running a 2.4.17 kernel and which to install
the HP 5200C scanner.  I found a patch with the necessary drives
for this scanner

ftp://ftp.torque.net/pub/ppSCSI-0.91.patch

which applies to a 2.2.10 kernel.

When I try to apply the patch to 2.2.19 or 2.4.17 I get two rejections: 
 	drivers/scsi/Makefile and include/linux/proc_fs.h

It applies well to 2.2.10 but I can not compile a working kernel in my
system.

Ideally I would like the patch to work with my running version of the kernel.

Any help/ideas on how to modify the patch to get it to work in a 2.4.17 will 
be very welcome.

	Filipe

--  To unsubscribe, send mail to: linux-parport-request <at> torque.net --
--  with the single word "unsubscribe" in the body of the message. --
Permalink | Reply | 2 comments |
headers
Stefan Riha | 5 Apr 2002 21:58
Picon
Picon

[PARPORT] IO errors

I want to use my Freecom portable CD-RW writer (2x2x24) under Linux.
The writer is with a Freecom parallel port cable connected to my computer.
For testing i have connected the writer on a 486 computer.
Now i have installed RedHat 6.2 and when i want to mount a data CD i get the
following errors.
Now i have Installed Suse 7.2 and i get the same errors when i want to mount
the data CD.

Now an concrete description of what i have done under RedHat 6.2

#lsmod
Module        Size    Used    by
lockd         31912    1      (autoclean)
sunrpc        53604    1      (autoclean) [locked]
rtl8139       12132    1      (autoclean)

#modprobe paride
paride: version 1.04 installed

#modprobe friq
paride: friq registered as protocol 0

#modprobe pcd
pcd: pcd version 1.07, major 46, nice 0
pcd0: Sharing parport0 at 0x378
pcd0: friq 1.01, Freecom IQ ASCI-2 adapter at 0x378, mode 4 (EPP-32), delay
1
pcd0: Master R/RW 2x2x24

#lsmod
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jon Miner | 6 Apr 2002 01:07
Picon
Favicon

Re: [PARPORT] ppSCSI-0.91.patch in newer kernels

We went over this a while back on the list.  For the
2.4.x kernel, you should start with the patches from:

http://http.us.debian.org/debian/pool/main/k/kernel-patch-ppscsi-2.4/

I integrated them into the RedHat 2.4.9-31 kernel,
hopefully they'll work for you too!

--- Filipe Freire <freire <at> schroedinger.stp.dias.ie>
wrote:
> Hallo!
> 
> I have slackware 8 running a 2.4.17 kernel...
> I found a patch....
>
> ftp://ftp.torque.net/pub/ppSCSI-0.91.patch
> 
> which applies to a 2.2.10 kernel.
> 

=====
Jon Miner
http://www.ConcordNH.com/Trains  - Concord Model RR Club
http://bmrrhs.come.to - B&M RR Historical Society

__________________________________________________
Do You Yahoo!?
Yahoo! Tax Center - online filing with TurboTax
http://taxes.yahoo.com/
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jerry Mulchin | 6 Apr 2002 07:14
Favicon

[PARPORT] SIIG Dual Parallel Port card under RH 6.2

Hi,

I have installed a SIIG Dual PCI parallel port card into my RH 6.2 system.
The PCI ports are seen OK by the BIOS and appear to be seen OK by
RedHat because the ports appear under /dev/pci/devices, and other places.

But I don't want to use the ports for printers. Rather I want to just use them
for control of some hardware I'm designing. When I installed the RH 6.2,
I did not install any parallel port support. Fortunately interrupts are not a
requirement, so I don't need to program for that. I also understand Linux
6.2 doesn't support parallel port interrupts anyway.

So, my questions are;

1.) Can I leave them at the ports the end up at when the system boots up?
They appear at 0xE800, 0XE400, 0xE000, and 0xDC00 and are defaulted
to EPP mode I believe. Or should I program the base addr registers to change
them to lower port address?

2.) Can I just program them for use in "user space" and use some of the
libraries out there that control paralle ports. One that I plan to use is a
library called "parapin". Parapin does support "ioperm", but I added "iopl" to
the library for the higher I/O addresses.

3.) I assume that the ports have to be setup just like any PCI card would
be programmed. Clearing the Status register, setting the control port for
I/O instead of Memory, setting them for SPP mode, etc...

Thanks in advance for the help
(Continue reading)

Permalink | Reply | 5 comments |
headers
Dr. Muhammad Masroor Ali | 6 Apr 2002 18:25

[PARPORT] "Operation not permitted" message when installing kernel modules

Hi All,
It is not that my drive (HP 7200) is bad. I have been using
it for more than a year under Mandrake 7.1, recently I
switched to RedHat and this mysterious problems starte
occurring. In Mandrake, I used the following sequrnce of
commands to install the modules,

/sbin/modprobe paride
/sbin/modprobe epat
/sbin/modprobe pg
/sbin/modprobe pcd

And it worked like a charm. Now under RH, the last command
generates the following message,

/lib/modules/2.4.2-2/kernel/drivers/block/paride/pg.o:
init_module: Operation not permitted
Hint: insmod errors can be caused by incorrect module
parameters, including invalid IO or IRQ parameters
/lib/modules/2.4.2-2/kernel/drivers/block/paride/pg.o:
insmod /lib/modules/2.4.2-2/kernel/drivers/block/paride/pg.o
failed
/lib/modules/2.4.2-2/kernel/drivers/block/paride/pg.o:
insmod pg failed

I have tried switching the sequence of the last two
commands, with messages in the same line. I feel really
frustated. Could any kind soul please tell me what is wrong.

Output from dmesg follows:
(Continue reading)

Permalink | Reply | 1 comment |

Gmane