Bug#388309: (no subject)

2006-10-03 Thread Daniel B.
One more thing: CONFIG_PARPORT_PC_FIFO is marked "EXPERIMENTAL", at least in kernel 2.6.8, so it had no business being set to Y in Sarge's 2.6.8 in the first place. Daniel -- Daniel Barclay [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Troub

Bug#388309: (no subject)

2006-10-03 Thread Daniel B.
I just found this: http://cyberelk.net/tim/parport/archive/current/4542.html about getting extra bytes at the printer (consistent with the symptoms I'm getting (see http://lists.debian.org/debian-user/2006/10/msg00133.html)) and "DMA write timed out" and "parport0: FIFO is stuck" errors in code

Bug#388309: linux-image-2.6.17-2-686: "DMA write timed out" with "CONFIG_PARPORT_PC_FIFO=y

2006-10-03 Thread Daniel B.
Is the problem really that CONFIG_PARPORT_PC_FIFO wasn't set to N, or is it actually that there's a bug in the kernel that only shows up when CONFIG_PARPORT_PC_FIFO isn't set to Y (or possibly buggy hardware)? I have been unable to print without severe errors (http://lists.debian.org/debian-u