Bug 2540 - Paralell port ZIP drive 100 dosen't work with 2.6.5
Summary: Paralell port ZIP drive 100 dosen't work with 2.6.5
Status: CLOSED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Parallel (show other bugs)
Hardware: i386 Linux
: P2 high
Assignee: drivers_parallel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-18 23:46 UTC by Peter
Modified: 2005-07-21 05:21 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.5
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
parport-probe-rewrite.patch (4.98 KB, patch)
2004-04-19 19:16 UTC, Adam Belay
Details | Diff
2.6.4 kernel dmesg (10.43 KB, text/plain)
2004-04-20 00:41 UTC, Peter
Details
2.6.5 kernel dmesg (9.93 KB, text/plain)
2004-04-20 00:41 UTC, Peter
Details
the kernel config file (27.82 KB, text/plain)
2004-04-20 00:45 UTC, Peter
Details
Dmesg after patch applied (10.26 KB, text/plain)
2004-04-20 23:05 UTC, Peter
Details
parport-pnp-revert.patch (5.50 KB, patch)
2004-04-23 10:44 UTC, Andrew Morton
Details | Diff
pnp-parport-detection-fix.patch (668 bytes, patch)
2004-04-25 19:00 UTC, Adam Belay
Details | Diff

Description Peter 2004-04-18 23:46:17 UTC
Distribution:Debian Woody 3.0 R1
Hardware Environment:i386; Duron 1100, MB QDI KinetiZ, Paralell port ZIPdrive
100 connected to LPT, printer EPSON LX-300 connected to ZIPdrive
Software Environment:
Problem Description:I compiled new kernel 2.6.5 for my machine and with the
2.6.5 kernel the paralell port ZIPdrive stopped working -it dosen't even mount
the drive, claims "not valid block device". With THE SAME kernel settings,
kernel 2.6.4 worked well, and if I boot the old kernel, it still works fine.
I suspect that some changes between 2.6.4 and 2.6.5 kernel has broken the
Paralell ZIPdrive functionality, or at least changed something that I need to
know to restore function of the ZIP.

Steps to reproduce:
1, compile the kernel 2.6.5 with paralell port support, IDE/ATAPI Floppy, SCSI
and related support
2, try to use paralell port ZIP drive
Comment 1 Andrew Morton 2004-04-18 23:50:33 UTC
Could you please send the dmesg output from 2.6.4 and from 2.6.5?

There were PNP-related parport changes in 2.6.5 and perhaps that
broke things.
Comment 2 Adam Belay 2004-04-19 19:16:46 UTC
Created attachment 2628 [details]
parport-probe-rewrite.patch

I've attached my parport changes made for 2.6.5.  Feel free to try reverting
them.  They only affect device detection but maybe its confusing the ECP
detection code.  If you haven't specifically tested 2.6.4, you may want to try
it also.  Several parport changes went in then too.

Finally could you attach your .config.	I'd like to see if PnP support is
enabled and also which specific parport options are selected.
Comment 3 Peter 2004-04-20 00:41:13 UTC
Created attachment 2632 [details]
2.6.4 kernel dmesg

Here's the 2.6.4 dmesg. Maybe You're right, there are some lines more related
to paralell port than in 2.6.5
Comment 4 Peter 2004-04-20 00:41:45 UTC
Created attachment 2633 [details]
2.6.5 kernel dmesg
Comment 5 Peter 2004-04-20 00:45:02 UTC
Created attachment 2634 [details]
the kernel config file

Here You are -the .config
Comment 6 Peter 2004-04-20 02:03:30 UTC
Guys, it's much worse than I expected -not only ZIP dosen't work -the WHOLE
PARALELL PORT is broken with 2.6.5. My mom has similar machine -QDI KinetiZ 7E
mb with KT133 chipset, VIA686 resp. VIA82C. She couldn't print with 2.6.5 while
with 2.6.2 no problem.

Just today I see, that father's print problems that I was not able to solve are
probably related to 2.6.5 too! Father has different machine, he has ABIT KG7 mb
I think, AFAIK AMD 751 or so northbridge, but I suspect he has VIA 686 resp. VIA
82C southbridge too!

So please, look at it. Since now I cannot state if the problem is related only
to VIA686 / VIA 82C or it affects more chipsets; if I'll test it on different
chipset, I'll let You know.

The severity might be normal, as far as I read the Severity gl, but
non-functional printing is enough for high, isn't it?
Comment 7 Andrew Morton 2004-04-20 02:05:21 UTC
Yours is the only report of this problem.

Please test the patch I sent.
Comment 8 Peter 2004-04-20 23:05:43 UTC
Created attachment 2638 [details]
Dmesg after patch applied

Yes, after applying the pnp-changes-removal patch, the paralell port works.
Here's dmesg.
Comment 9 dommi_s1 2004-04-23 06:29:54 UTC
I have exactely the same problem - complete parport stopped working with no
error messages at all. Any data sent to my printer just never arrives there.
Identical config with 2.6.4 gets the printer working again.

Please see also  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=244728

My system is an AMD-751 board with 550MHz Athlon
Comment 10 Andrew Morton 2004-04-23 10:44:13 UTC
Created attachment 2675 [details]
parport-pnp-revert.patch

Can you confirm that this patch fixes it up?
Comment 11 Adam Belay 2004-04-25 19:00:42 UTC
Created attachment 2706 [details]
pnp-parport-detection-fix.patch

This patch should solve the problem.  It prevents PnP detection if devices were
already detected by SuperIO.  Any testing would be appreciated.
Comment 12 Paul L. Rogers 2004-04-29 19:13:08 UTC
I have applied Adams's patch
(http://bugme.osdl.org/attachment.cgi?id=2706&action=view) to the 2.6.5
parport_pc.c as distributed by the Debian project.

The patch works for me (EPoX 8KTA3 (VIA KT133A)).
Comment 13 Adrian Bunk 2005-07-21 05:21:46 UTC
Looking at the bug logs, it seems this issue is fixed by the patch from Comment
11. I'm closing this bug since the patch is already included in recent 2.6 kernels.

Note You need to log in before you can comment on or make changes to this bug.