I have mine linked to the kernel. At least I believe that's
the effect of
CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PRINTER=y
> > Bug #2: Something isn't right in the 2.1.xx lp initialization
> >
> > My machine under 2.1.120 cannot print. Attempts to cat to /dev/lp0
> > or /dev/lp1 yield "Operation not supported by device".
>
> Hmm. Works for me.. ;-)
>
> Again, I've got lp as a module. I'll use your config options and take a
> look though.
>
> If you could send the output of "dmesg", that would help out a lot.
Looks like this is the critical bit...
Checking 386/387 coupling... OK, FPU using exception 16 error reporting.
Checking 'hlt' instruction... OK.
Swansea University Computer Society NET3.039 for Linux 2.1
NET3: Unix domain sockets 0.16 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: ICMP, UDP, TCP
PCI: PCI BIOS revision 2.10 entry at 0xfdb81
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: Enabling I/O for device 00:3a
Starting kswapd v 1.5
parport0: PC-style at 0x378 [SPP]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Serial driver version 4.26 with no serial options enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS01 at 0x02f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
PS/2 auxiliary pointing device detected -- driver installed.
APM disabled: APM is not SMP safe.
Sound initialization started
<Sound Blaster 16 (4.16)> at 0x220 irq 5 dma 1,5
<Sound Blaster 16> at 0x330 irq 5 dma 0
Sound initialization complete
Floppy drive(s): fd0 is 1.44M
FDC 0 is a National Semiconductor PC87306
> > I suspect this has something to do with the facts that (a) the port
> > address configured for the port is 378, which would normally be lp1,
> > (b) /proc/parport contains only the entry `0', and (c) the 2.1.xx
> > driver, unlike the 2.0.xx driver, tries to map port addresses
> > to devices dynamically.
> > Frobbing lp boot time options has yielded no good result.
>
> If you only have one parallel port, which I think is what you've
> described, then you can expect /dev/lp0 to be the right device. To make
> sure, you could try booting with:
>
> parport=0x378 lp=parport0
>
> on the kernel command line. (Or something like that - check
> Documentation/parport.txt and drivers/char/lp.c.)
I'll try this.
-- <a href="http://www.tuxedo.org/~esr">Eric S. Raymond</a>The following is a Python RSA implementation. According to the US Government these three lines are "munitions" and posting them makes me an international arms trafficker! Join me in civil disobedience; add these lines of code to your .sig block to help get this stupid and unconstitutional law changed. ============================================================================ from sys import*;from string import*;a=argv;[s,p,q]=filter(lambda x:x[:1]!= '-',a);d='-d'in a;e,n=atol(p,16),atol(q,16);l=(len(q)+1)/2;o,inb=l-d,l-1+d while s:s=stdin.read(inb);s and map(stdout.write,map(lambda i,b=pow(reduce( lambda x,y:(x<<8L)+y,map(ord,s)),e,n):chr(b>>8*i&255),range(o-1,-1,-1)))
Every election is a sort of advance auction sale of stolen goods. -- H.L. Mencken
- 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/faq.html