Marcus Berglund (mabs@jaycom.net.au)
Fri, 19 Jun 1998 05:16:44 +1000 (EST)
On 18-Jun-98 grant@torque.net wrote:
> It's hard to say too much without some data. Please load pf with
> the "verbose=1" flag and let me see what it says.
Here:
4:50:54 mabs:/usr/src/paride-0.94# insmod pf verbose=1
pf0: epat: port 0x3bc, mode 0, ccr ff, test=(255,255,510)
pf0: epat: port 0x3bc, mode 1, ccr ff, test=(255,255,510)
pf0: epat: port 0x3bc, mode 2, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 0, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 1, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 2, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 3, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 4, ccr ff, test=(255,255,510)
pf0: epat: port 0x378, mode 5, ccr ff, test=(255,255,510)
pf0: epat: port 0x278, mode 0, ccr 0, test=(0,256,0)
pf0: epat: port 0x278, mode 1, ccr 40, test=(187,256,297)
pf0: epat: port 0x278, mode 2, ccr 0, test=(0,256,0)
pf0: epat: port 0x278, mode 3, ccr 0, test=(0,256,0)
pf0: epat: port 0x278, mode 4, ccr 0, test=(0,256,0)
pf0: epat: port 0x278, mode 5, ccr 0, test=(0,256,0)
pf0: epat 0.94, Shuttle EPAT chip c6 at 0x278, using mode 5 (EPP-32)
pf0: Reset (1) signature = 1 1 1 14 eb
pf0: MATSHITA LS-120 COSM 04, master LUN 0, type 0, removable, 246528 blocks
04:51:05 mabs:/usr/src/paride-0.94#
I also don't seem to get any timeouts...
> Well, one thing is to load the driver with the "nice=1" flag. That
> should address some of your concerns.
Doesn't seem to make a difference, an example is the mouse being very jumpy, in
X or at a console (gpm).
> Again, without seeing the error messages from pf, I can't really comment.
> Certain errors will result in long timeouts. If you are getting those,
> there is something wrong with your setup (either the hardware or the
> driver configuration).
Those messages, if I am right, probably kernel messages, complaining about a
read error, and it locked the computer to the point that the keyboard input
stopped working.
The same happens in 2.1 or 2.0 kernels, I am using 2.0 right now. It looked
like an IRQ was slowing the machine, so in 2.1 I didn't specify an IRQ, but it
still persisted.
I am using kernel 2.0.34 w/paride 0.94 & 2.1.103 with built in paride support.
My motherboard is a Giga-Byte 586-ATM/P (430FX) the parallel port is at
0x278/IRQ5 it still happens if I specify another pp address/IRQ.
The difference between genius and stupidity
is that genius has it's limits.
- - - - - - - - - - - - - - - - - - - - - - -
Marcus Berglund, VK3TST.
Linux / Unix System Consultant / Administrator
Bendigo, Victoria, Australia.
E-mail: mabs@jaycom.net.au
Web: http://mabs.home.ml.org/
Phone: +61 3 5441 6318
ICQ: 7402444
- - - - - - - - - - - - - - - - - - - - - - -
-- To unsubscribe, send mail to: linux-parport-request@torque.net --
-- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:17:52 EST