Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


  cat lptest  /dev/lp0  where lptest is a small text file

and

  lp lptest

responds normally but nothing is printed and nothing is in the print que.

  cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


  cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is directed to lp0.


Where is the missing link?

Tom George



Netscape 6 Encryption Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
I downloaded and installed Netscape 6.  It works normally except when a 
transmission is to be encrypted.  Then it locks uo not only the Netscape 
window but all of Xwindows.  I can recover only by returning to the 
console and executing a Ctrl C to abort Xwindows.


I tried sending an email to Netscape support but this was automatically 
encrypted.


Any suggestions?

Tom George



Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
Thanks for the suggestion. I had not learned about
dmesg. Unfortunately it reported everything in order - i.e. parport0 using
0378 and irq 7. I must look elsewhere for the problem.

Tom George

ktb wrote:
On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:
  My printer was working perfectly.  I rebuilt the kernel allowing autoprobe.  Printer no longer responds even to   cat lptest  /dev/lp0  where lptest is a small text fileand   lp lptestresponds normally but nothing is printed and nothing is in the print que.   cat /proc/ioports  shows the correct value (0378-037f) for parport0   cat /proc/parport/0/irq  reports none (should be irq 7 but is this needed?)Documentation/parport indicates that a lilo command parport=0x378,7 should work but /sbin/lilo rejects this line placed anywhere in lilo.conf.  The documentation also implies that the irq value reported by cat/proc/parport/0/irq can be changed but I don't understand how.It seems to me that everything is working normally but the printer is not receiving the transmission.  The printcap file is unaltered and lp is !
directed to lp0.Where is the missing link?
What does dmesg say about parport?kent




Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
Thanks for the suggestion; I had not yet learned about dmesg.  
Unfortunately, dmesg reported all in order with parport - i.e. using 
0378 and irq 7.  I must look elsewhere for my problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest  /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is directed to lp0.


Where is the missing link?



What does dmesg say about parport?
kent





Re: Printer Problem

2001-02-02 Thread Thomas H. George,,,610-444-2626
I was surprised!  After running dmesg I found my printer working again.  
I don't understand why this is so but, as I had done nothing else (I 
send these messages from another computer), dmseg must have corrected 
the problem.


Thanks again for the help.

Tom George

Thomas H. George,,,610-444-2626 wrote:

Thanks for the suggestion.  I had not learned about dmesg.  
Unfortunately it reported everything in order - i.e. parport0 using 
0378 and irq 7.  I must look elsewhere for the problem.


Tom George

ktb wrote:


On Fri, Feb 02, 2001 at 11:01:26AM -0500, Thomas H. George,,,610-444-2626 wrote:

My printer was working perfectly.  I rebuilt the kernel allowing 
autoprobe.  Printer no longer responds even to


   cat lptest  /dev/lp0  where lptest is a small text file

and

   lp lptest

responds normally but nothing is printed and nothing is in the print que.

   cat /proc/ioports  shows the correct value (0378-037f) for 
parport0


   cat /proc/parport/0/irq  reports none (should be irq 7 but is 
this needed?)


Documentation/parport indicates that a lilo command parport=0x378,7 
should work but /sbin/lilo rejects this line placed anywhere in 
lilo.conf.  The documentation also implies that the irq value reported 
by cat/proc/parport/0/irq can be changed but I don't understand how.


It seems to me that everything is working normally but the printer is 
not receiving the transmission.  The printcap file is unaltered and lp 
is !

directed to lp0.

Where is the missing link?



What does dmesg say about parport?
kent







[Fwd: Down grade from gcc 2.95.2 to gcc 2.91.66]

2001-01-22 Thread Thomas H. George,,,610-444-2626



 Original Message 
Subject: Down grade from gcc 2.95.2 to gcc 2.91.66
Date: Mon, 22 Jan 2001 09:34:43 -0500
From: Thomas H. George,,,610-444-2626 [EMAIL PROTECTED]
To: [EMAIL PROTECTED]



I am running kernel 2.2.12 and downloaded release 2.4.  The accompanying 
instructions strongly recommends compiling the new kernel with 
gcc-2.91.66 (egcs-1.1.2).  I downloaded


  egcs-1.1.2-alpha.tar.bz2
  egcs-1.1.2-doc.tar.bz23
  egcs-1.1.2-glibc.x86.tar.bz2
  egcs-1.1.2-libc5.x86.tar.bz2

The instructions I found (somewhere) said put these in the root 
directory and unpack them.  I did.  Now dpkg -l still shows gcc-2.95 
installed and gcc --version reports cannot execute binary file.


Should I have purged gcc-2.95?  Is there any way to recover from what I 
have done?


Tom George