Re: Solution to printing problem (dumb mistake)

Luca Montecchiani (m.luca@iname.com)
Sun, 22 Aug 1999 23:21:05 +0200

> Turns out it wasn't a kernel problem. I had the io port and irq set wrong
> in conf.modules, and parport peacefully accepted the given options and
> sent data to the bit bucket.
>
> Question: is this proper behavior? It caused a system freeze on 2.3.13 and
> failed silently on 2.3.15-pre2. Is there any way for the parport module to
> say "you stupid (l)user, there isn't a parallel port there!"?

Oh well, today same problem here, I've just updated my
loadlin cmdline kernel 2.2.11 to parport=0x378,7 parport=0x278,5
before install a new lpt2 card :)

parport0: PC-style at 0x378, irq 7 [SPP,PS2,EPP]
parport0: no IEEE-1284 device present.
0x278: CTR: wrote 0x0c, read 0xff
0x278: DATA: wrote 0xaa, read 0xff
parport1: PC-style at 0x278, irq 5 [SPP,PS2]
parport1: no IEEE-1284 device present.

[root@home parport]# cat 0/* 1/*
MODEL:Unknown device;
MANUFACTURER:Unknown vendor;
lp
base: 0x378
irq: 7
dma: none
modes: SPP,PS2,EPP
7
MODEL:Unknown device;
MANUFACTURER:Unknown vendor;
lp
base: 0x278
irq: 5
dma: none
modes: SPP,PS2
5

[root@home parport]# insmod lp
lp0: using parport0 (interrupt-driven).
lp1: using parport1 (interrupt-driven).

As you see, parport came out with some messages (*), in this
situation we can show some bad warning and maybe don't
load parport1....

(*) 0x278: CTR: wrote 0x0c, read 0xff
0x278: DATA: wrote 0xaa, read 0xff

-- 
ciao, luca
------------------------------------------------------------------
E-mail......: Luca Montecchiani <m.luca@iname.com>
W.W.W.......: http://i.am/m.luca - http://luca.myip.org
Speakfreely.: sflwl -hlwl.fourmilab.ch luca@
I.C.Q.......: 17655604
-----------------------=(Linux since 1995)=-----------------------


Non esiste vento favorevole per il marinaio che non sa dove andare
                                                          Seneca


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/