Re: Printer fiascos.
> "Nicolas" == Nicolas Souchu <[EMAIL PROTECTED]> writes: Nicolas> On Sun, Jan 30, 2000 at 02:42:39PM -0500, Brian Dean wrote: >> >> >> For what its worth, I am able to reproduce this problem on my >> system. Nicolas> Would you mind trying this patch before I send it to Jordan? I certainly don't get any "hangs" any more, but I'm still experiencing "pauses" --- short half-a-second mouse unresponsiveness when someone prints. I'm currently seeing the following on boot: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
This patch fixes the problem for me. Thanks!!!
-Brian
> On Sun, Jan 30, 2000 at 02:42:39PM -0500, Brian Dean wrote:
> >
> >
> >For what its worth, I am able to reproduce this problem on my system.
>
> Would you mind trying this patch before I send it to Jordan?
>
> Index: lpt.c
> ===
> RCS file: /home/ncvs/src/sys/dev/ppbus/lpt.c,v
> retrieving revision 1.13
> diff -u -r1.13 lpt.c
> --- lpt.c 2000/01/25 22:23:47 1.13
> +++ lpt.c 2000/02/02 23:10:36
> @@ -865,12 +865,12 @@
>
> /*
> * No more data waiting for printer.
> -* Wakeup is not done if write call was interrupted.
> +* Wakeup is not done if write call was not interrupted.
> */
> sc->sc_state &= ~OBUSY;
>
> if(!(sc->sc_state & INTERRUPTED))
> - wakeup((caddr_t)sc);
> + wakeup((caddr_t)lptdev);
> lprintf(("w "));
> return;
> } else { /* check for error */
>
> --
> [EMAIL PROTECTED] / [EMAIL PROTECTED]
> FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, Jan 30, 2000 at 02:42:39PM -0500, Brian Dean wrote:
>
>
>For what its worth, I am able to reproduce this problem on my system.
Would you mind trying this patch before I send it to Jordan?
Index: lpt.c
===
RCS file: /home/ncvs/src/sys/dev/ppbus/lpt.c,v
retrieving revision 1.13
diff -u -r1.13 lpt.c
--- lpt.c 2000/01/25 22:23:47 1.13
+++ lpt.c 2000/02/02 23:10:36
@@ -865,12 +865,12 @@
/*
* No more data waiting for printer.
-* Wakeup is not done if write call was interrupted.
+* Wakeup is not done if write call was not interrupted.
*/
sc->sc_state &= ~OBUSY;
if(!(sc->sc_state & INTERRUPTED))
- wakeup((caddr_t)sc);
+ wakeup((caddr_t)lptdev);
lprintf(("w "));
return;
} else { /* check for error */
--
[EMAIL PROTECTED] / [EMAIL PROTECTED]
FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, Jan 30, 2000 at 10:38:57PM -0500, David Gilbert wrote: > >> "Michael" == Michael Remski <[EMAIL PROTECTED]> writes: > >Michael> ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset >Michael> (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with >Michael> 16/16/7 bytes threshold lpt0: on ppbus 0 >Michael> lpt0: Interrupt-driven port > >I don't get the FIFO portion of the probe. With ECP mode available? You should. > >Dave. > >-- > >|David Gilbert, Velocet Communications. | Two things can only be | >|Mail: [EMAIL PROTECTED] | equal if and only if they | >|http://www.velocet.net/~dgilbert | are precisely opposite. | >=GLO > > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
> "Michael" == Michael Remski <[EMAIL PROTECTED]> writes: Michael> ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset Michael> (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with Michael> 16/16/7 bytes threshold lpt0: on ppbus 0 Michael> lpt0: Interrupt-driven port I don't get the FIFO portion of the probe. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos
> For what its worth, I am able to reproduce this problem on my system. > Simply submit something to lpr, wait for the printer light to blink, > and pull the paper tray. The system hangs hard as described and does > not return to normal until the paper tray is put back in. I haven't > been able to make it do anything while the printer has the system > hung, so I haven't been able to track it down, yet. However, I > haven't had much time to spend on this problem, but thought I'd chime > in a "me too" when I saw someone had the (apparently) same problem. > > I have an HP LaserJet 4 connected to the parallel port. > > I am running -current, and a buildworld as of about a week ago. > > -Brian > -- > Brian Dean [EMAIL PROTECTED] I will confirm this problem with the lpt driver. Even worse, on my LaserJet IIIsi printer... Not only did it hang the system, but I went as far as turning the printer off, then back on. THE SYSTEM REBOOTED. There was no panic or other context to share. I suspect it MAY have been related to the about of time it takes the LJ III to cycle on a power-up. Regardless, this is wholly unacceptable for a RELEASE. FWIW, my dmesg follows to show the port-type, etc. ppp0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pps0: on ppbus0 Cheers, -skots -- Scott G. Akmentins-Taylor InterNet: [EMAIL PROTECTED] MRY Systems [EMAIL PROTECTED] (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") - Labak miris neka sarkans - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
This is on 3.4 Stable, Another "me too", BUT, with a "data point". NEC SuperScript 870, ASUS MB. Had the same problem when the BIOS was set to ECP+EPP on the parallel port. Sinces it only a printer, I set the BIOS to Normal and deliberately tried to introduce the problem (pull paper tray, etc). Didn't have the problem. Two things had happened, the BIOS change and I removed the "flags 0x40" from the config file. Relevant piece of dmesg: ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER PrintGear,PCL,PJL lpt0: on ppbus 0 lpt0: Interrupt-driven port dmesg prior to the change: ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port Notice it used to say SMC-like chipset? Just a data point. m On Sun, 30 Jan 2000, Brian Dean wrote: > > For what its worth, I am able to reproduce this problem on my system. > Simply submit something to lpr, wait for the printer light to blink, > and pull the paper tray. The system hangs hard as described and does > not return to normal until the paper tray is put back in. I haven't > been able to make it do anything while the printer has the system > hung, so I haven't been able to track it down, yet. However, I > haven't had much time to spend on this problem, but thought I'd chime > in a "me too" when I saw someone had the (apparently) same problem. > > I have an HP LaserJet 4 connected to the parallel port. > > I am running -current, and a buildworld as of about a week ago. > > -Brian > -- > Brian Dean[EMAIL PROTECTED] > > > Here's my dmesg: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Sun Jan 23 09:10:33 EST 2000 > [EMAIL PROTECTED]:/usr/src/sys/compile/VGER > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 300682757 Hz > CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > >Features=0x183f9ff > real memory = 201326592 (196608K bytes) > avail memory = 192131072 (187628K bytes) > Preloaded elf kernel "kernel" at 0xc02f3000. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq >11 > chip1: port 0x5000-0x500f at device 7.3 >on pci0 > vga-pci0: mem >0xe500-0xe5ff,0xe400-0xe4ff irq 10 at device 9.0 on pci0 > xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc400-0xc43f irq 5 at device 10.0 on >pci0 > xl0: Ethernet address: 00:60:08:17:67:f9 > miibus0: on xl0 > nsphy0: on miibus0 > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ahc0: port 0xc800-0xc8ff mem 0xe900-0xe9000fff >irq 9 at device 11.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 11 > pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ata-isa0: already registered as ata0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding disabled, >unlimited logging > Waiting 15 seconds for SCSI devices to settle > acd0: CDROM drive at ata0 as master > acd0: 128KB buffer, PIO4 > acd0: Reads: CD-R, CD-RW, CD-DA stream, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > Mounting root from ufs:/dev/da0a > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device
Re: Printer fiascos.
For what its worth, I am able to reproduce this problem on my system. Simply submit something to lpr, wait for the printer light to blink, and pull the paper tray. The system hangs hard as described and does not return to normal until the paper tray is put back in. I haven't been able to make it do anything while the printer has the system hung, so I haven't been able to track it down, yet. However, I haven't had much time to spend on this problem, but thought I'd chime in a "me too" when I saw someone had the (apparently) same problem. I have an HP LaserJet 4 connected to the parallel port. I am running -current, and a buildworld as of about a week ago. -Brian -- Brian Dean [EMAIL PROTECTED] Here's my dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 23 09:10:33 EST 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/VGER Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300682757 Hz CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 192131072 (187628K bytes) Preloaded elf kernel "kernel" at 0xc02f3000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: port 0x5000-0x500f at device 7.3 on pci0 vga-pci0: mem 0xe500-0xe5ff,0xe400-0xe4ff irq 10 at device 9.0 on pci0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc400-0xc43f irq 5 at device 10.0 on pci0 xl0: Ethernet address: 00:60:08:17:67:f9 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xc800-0xc8ff mem 0xe900-0xe9000fff irq 9 at device 11.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 11 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging Waiting 15 seconds for SCSI devices to settle acd0: CDROM drive at ata0 as master acd0: 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/da0a da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da4 at ahc0 bus 0 target 6 lun 0 da4: Removable Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15) da4: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da3: 8683MB (17783204 512 byte sectors: 255H 63S/T 1106C) pid 52635 (communicator-4.6), uid 1000: exited on signal 10 (core dumped) Dan Sobral wrote: > Chuck Robey wrote: > > > > Sheesh. This is a FreeBSD-questions type thing, not current. > > I disagree. It is obvious that something is getting locked inside the > kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his > machine locked whenever the printer went out of paper, and *stayed* > locked, I'd be willing to believe the problem was caused by hardwar
Re: Printer fiascos.
On Sat, Jan 29, 2000 at 08:21:33PM -0800, Matthew Dillon wrote: > >When the new parallel port stuff was put several months ago, my >machine stopped working. I had to set flags to 0x40 to make it >work again. Flags of 0x40 force the driver to use the most >basic probes possible. It was put in because a number of people's >machines stopped working. > >It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC >on Jan 14. Specific chipset detection is now disabled by default since most of the chipsets detected on new MB are not recognised by ppc. A MACHINE option shall be set to activate chipset detection. See http://www.freebsd.org/~nsouch/ppbus.html for more info. [...] > >David, try putting flags 0x40 back in and see if that fixes your >problem. 0x40 has the same effect only if chipset specific detection is activated at compile time by the correct option. Otherwise the action is null. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sat, Jan 29, 2000 at 10:59:15PM -0500, David Gilbert wrote: > >> "Chris" == Chris Costello <[EMAIL PROTECTED]> writes: > >Chris> On Saturday, January 29, 2000, David Gilbert wrote: >>> When this happens, the entire machine freezes until someone feeds >>> the printer --- the momment it starts printing again, the computer >>> unfreezes. > >Chris>Could it be a printer-specific (or printer-compatibility) >Chris> problem? My HP DeskJet 880C does not have that problem at all: > >To my mind, the printer shouldn't be able to hang the comptuer ... no >matter what it does. My biggest problem is that it hangs the system. Even if rapid interrupts are sent to the computer? A priority issue among various interrupt sources maybe. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sat, Jan 29, 2000 at 09:49:40PM -0600, Chris Costello wrote: > >On Saturday, January 29, 2000, David Gilbert wrote: >> When this happens, the entire machine freezes until someone feeds the >> printer --- the momment it starts printing again, the computer >> unfreezes. > > Could it be a printer-specific (or printer-compatibility) >problem? My HP DeskJet 880C does not have that problem at all: > >ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 >ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode >ppb0: IEEE1284 device found /NIBBLE/ECP >Probing for PnP devices on ppbus0: >ppbus0: MLC,PCL,PML >plip0: on ppbus 0 >lpt0: on ppbus 0 >lpt0: Interrupt-driven port >ppi0: on ppbus 0 Note that you're using an older ppbus/lpt drivers. -- [EMAIL PROTECTED] / [EMAIL PROTECTED] FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
Matthew Dillon wrote:
> When the new parallel port stuff was put several months ago, my
> machine stopped working. I had to set flags to 0x40 to make it
> work again. Flags of 0x40 force the driver to use the most
> basic probes possible. It was put in because a number of people's
> machines stopped working.
>
> It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC
> on Jan 14.
>
> At the time I had an argument with the author who insisted that
> the correct way to force 'basic' probing of the printer was to
> set the flags field in GENERIC rather then make the default a basic
> probe.
>
> * Peter, the comment in your log message makes no mention of the reason
> * for removing the flags. If you did this by accident could you please
> * set the flags back to 0x40?
The reason I did that was because flags 0x40 only does something if you
activate the PPC_PROBE_CHIPSET option. By default you get flags 0x40
type behavior and the intrusive probes are simply not even compiled into
the driver. If you activate the option, then you can also specify
flags 0x40 to disable the code you compiled in. In other words, GENERIC
does not require the flag any more as it doesn't have the option active.
#ifdef PPC_PROBE_CHIPSET
/* we have to differenciate available chipset modes,
* chipset running modes and IEEE-1284 operating modes
*
* after detection, the port must support running in compatible mode
*/
if (ppc->ppc_flags & 0x40) {
if (bootverbose)
printf("ppc: chipset forced to generic\n");
#endif
> Now, a huge number of changes have been made since the original problem
> was reported, so I could be puffing smoke here. I didn't see anything
> in the CVS logs, though, so I am assuming that the removal of the
> flags field was a mistake.
>
> David, try putting flags 0x40 back in and see if that fixes your
> problem.
>
> -Matt
> Matthew Dillon
> <[EMAIL PROTECTED]>
>
> :Why is it that a properly functioning printer is such a moving target
> :in FreeBSD?
> :
> :I don't mean to be argumentative, but under 3.x, the magic cookie to
> :make printers work (it appeared to be a flow control problem) was to
> :change
> :
> :device ppc0at isa? port? flags 0x40 net irq 7
> :
> :to
> :
> :device ppc0at isa? port? flags 0x40 tty irq 7
> :
> :Now... I've upgraded to -CURRENT, and it has a much more serious
> :problem. The line now reads
> :
> :device ppc0at isa? port? irq 7
> :
> :... so I havn't tried putting net or tty in it, but I have a printer
> :with a particular problem --- it will often fail to pick up a sheet of
> :paper. I suspect that this sets the paper out sense line of the
> :parallel port (?).
> :
> :When this happens, the entire machine freezes until someone feeds the
> :printer --- the momment it starts printing again, the computer
> :unfreezes.
> :
> :Printer-port related things probe as:
> :
> :ppc0: at port 0x378-0x37f irq 7 on isa0
> :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode
> :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP
> :Probing for PnP devices on ppbus0:
> :ppbus0: PCL,MLC,PML
> :lpt0: on ppbus0
> :lpt0: Interrupt-driven port
> :plip0: on ppbus0
> :ppi0: on ppbus0
> :
> :(I have tried putting the BIOS in different parallel port modes.)
> :
> :Dave.
> :
> :--
> :
> :|David Gilbert, Velocet Communications. | Two things can only be |
> :|Mail: [EMAIL PROTECTED] | equal if and only if they |
> :|http://www.velocet.net/~dgilbert | are precisely opposite. |
> :=GLO
>
>
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
Chuck Robey wrote: > > Sheesh. This is a FreeBSD-questions type thing, not current. I disagree. It is obvious that something is getting locked inside the kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his machine locked whenever the printer went out of paper, and *stayed* locked, I'd be willing to believe the problem was caused by hardware. That's not what was reported. What was reported is rather (better) explained by some kernel code waiting indefinitely for an event, while preventing anything else from executing. -- Daniel C. Sobral(8-DCS) [EMAIL PROTECTED] [EMAIL PROTECTED] "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Sun, 30 Jan 2000, David Gilbert wrote: > > "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: > > Sean> On 2000 Jan 29, David Gilbert opined: > >> > "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: > >> > Sean> lptcontrol -p > >> I will try this. It still seems that there's a misfeature that it > >> just doesn't work by default. > > Sean> Yep. It is odd that it completely locks your box waiting for > Sean> paper. I have seen other printers which end up printing garbage > Sean> after this but never a locked box. And notice it's not for everyone. I don't know why yours locks up and mine doesn't, but my printer, in the last month, has begun to occaisonally fail to pick up a sheet of paper. It stops the print, but nothing worse than that. I haven't really investigated it, and for me, since I don't see your problem, the fix is a couple of suitably applied alcohol wipes, probably. What I'm saying is, don't start trying to over-generalize your problem. It'll make it harder for you to find, and give FreeBSD an unnecessarily bad rep over that. BTW, that lptcontrol -p means you have something wrong with your parallel interface, because it's not responding to interrupts. This often means you have some IO card you forgot (like a sound card) sitting unbeknownst to you on IRQ 7, messing up the printer. The -p means it just polls the printer to pass in new characters, instead of reacting by interrupt. If the -p thing works for you, I would go looking at hardware, myself. Sheesh. This is a FreeBSD-questions type thing, not current. > > That's a different problem... That problem has something to do with > flow control... and I've had that happen, too. > > Dave. > > Chuck Robey| Interests include C & Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
> "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: Sean> On 2000 Jan 29, David Gilbert opined: >> > "Sean" == Sean O'Connell <[EMAIL PROTECTED]> writes: >> Sean> lptcontrol -p >> I will try this. It still seems that there's a misfeature that it >> just doesn't work by default. Sean> Yep. It is odd that it completely locks your box waiting for Sean> paper. I have seen other printers which end up printing garbage Sean> after this but never a locked box. That's a different problem... That problem has something to do with flow control... and I've had that happen, too. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
When the new parallel port stuff was put several months ago, my machine stopped working. I had to set flags to 0x40 to make it work again. Flags of 0x40 force the driver to use the most basic probes possible. It was put in because a number of people's machines stopped working. It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC on Jan 14. At the time I had an argument with the author who insisted that the correct way to force 'basic' probing of the printer was to set the flags field in GENERIC rather then make the default a basic probe. * Peter, the comment in your log message makes no mention of the reason * for removing the flags. If you did this by accident could you please * set the flags back to 0x40? Now, a huge number of changes have been made since the original problem was reported, so I could be puffing smoke here. I didn't see anything in the CVS logs, though, so I am assuming that the removal of the flags field was a mistake. David, try putting flags 0x40 back in and see if that fixes your problem. -Matt Matthew Dillon <[EMAIL PROTECTED]> :Why is it that a properly functioning printer is such a moving target :in FreeBSD? : :I don't mean to be argumentative, but under 3.x, the magic cookie to :make printers work (it appeared to be a flow control problem) was to :change : :device ppc0at isa? port? flags 0x40 net irq 7 : :to : :device ppc0at isa? port? flags 0x40 tty irq 7 : :Now... I've upgraded to -CURRENT, and it has a much more serious :problem. The line now reads : :device ppc0at isa? port? irq 7 : :... so I havn't tried putting net or tty in it, but I have a printer :with a particular problem --- it will often fail to pick up a sheet of :paper. I suspect that this sets the paper out sense line of the :parallel port (?). : :When this happens, the entire machine freezes until someone feeds the :printer --- the momment it starts printing again, the computer :unfreezes. : :Printer-port related things probe as: : :ppc0: at port 0x378-0x37f irq 7 on isa0 :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP :Probing for PnP devices on ppbus0: :ppbus0: PCL,MLC,PML :lpt0: on ppbus0 :lpt0: Interrupt-driven port :plip0: on ppbus0 :ppi0: on ppbus0 : :(I have tried putting the BIOS in different parallel port modes.) : :Dave. : :-- : :|David Gilbert, Velocet Communications. | Two things can only be | :|Mail: [EMAIL PROTECTED] | equal if and only if they | :|http://www.velocet.net/~dgilbert | are precisely opposite. | :=GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
> "Chris" == Chris Costello <[EMAIL PROTECTED]> writes: Chris> On Saturday, January 29, 2000, David Gilbert wrote: >> When this happens, the entire machine freezes until someone feeds >> the printer --- the momment it starts printing again, the computer >> unfreezes. Chris>Could it be a printer-specific (or printer-compatibility) Chris> problem? My HP DeskJet 880C does not have that problem at all: To my mind, the printer shouldn't be able to hang the comptuer ... no matter what it does. My biggest problem is that it hangs the system. To your lack of problem, all I can say is that you might not have the conditions to notice it. To see the problem, you need the printer to fail to pick up paper (or to run out of paper) while the job is still being fed by the computer (does not count if the job is entirely within the printer when it runs out of paper). Now... I'm running LPRng, and it appears that only things printed by Samba clients (as opposed to local jobs which go through a gs filter first) hang the printer --- but this may be a red herring (that is all jobs might have the possibility to hang the printer, it's simply in our experience that lpr-submitted jobs havn't ... but then the sample of lpr jobs is very small compared to the sample of samba jobs). Regardless... the fact that the printer is hard to get working is a minor problem. The fact that it hangs the whole system is a MAJOR problem. (This is a real hard hang. Durning the hang no mouse/X response and no network (not even ping) response) When the printer is given paper, this problem disappears. Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Printer fiascos.
On Saturday, January 29, 2000, David Gilbert wrote: > When this happens, the entire machine freezes until someone feeds the > printer --- the momment it starts printing again, the computer > unfreezes. Could it be a printer-specific (or printer-compatibility) problem? My HP DeskJet 880C does not have that problem at all: ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 -- |Chris Costello <[EMAIL PROTECTED]> |Earn cash in your spare time -- blackmail friends. `-- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Printer fiascos.
Why is it that a properly functioning printer is such a moving target in FreeBSD? I don't mean to be argumentative, but under 3.x, the magic cookie to make printers work (it appeared to be a flow control problem) was to change device ppc0at isa? port? flags 0x40 net irq 7 to device ppc0at isa? port? flags 0x40 tty irq 7 Now... I've upgraded to -CURRENT, and it has a much more serious problem. The line now reads device ppc0at isa? port? irq 7 ... so I havn't tried putting net or tty in it, but I have a printer with a particular problem --- it will often fail to pick up a sheet of paper. I suspect that this sets the paper out sense line of the parallel port (?). When this happens, the entire machine freezes until someone feeds the printer --- the momment it starts printing again, the computer unfreezes. Printer-port related things probe as: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 (I have tried putting the BIOS in different parallel port modes.) Dave. -- |David Gilbert, Velocet Communications. | Two things can only be | |Mail: [EMAIL PROTECTED] | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =GLO To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
