From: Takanori Watanabe <takawata-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
To: Matthew Wilcox <matthew-Ztpu424NOJ8@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: PNPACPI breaks my asus k6-2 parallel port
Date: Tue, 07 Dec 2004 13:14:31 +0900 [thread overview]
Message-ID: <200412070414.NAA01833@axe-inc.co.jp> (raw)
In-Reply-To: Your message of "Tue, 07 Dec 2004 02:21:33 GMT." <20041207022133.GB22171-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
In message <20041207022133.GB22171-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>, Matthew
Wilcox wrote:
>
>Turning on PNPACPI changes this in my dmesg:
>
>-parport0: PC-style at 0x378 [PCSPP(,...)]
>-lp0: using parport0 (polling).
>+ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
>+ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
>+parport: PnPBIOS parport detected.
>+parport0: PC-style at 0x378, irq 7 [PCSPP(,...)]
>+lp0: using parport0 (interrupt-driven).
>+pnp: Device 00:08 activated.
>+parport: PnPBIOS parport detected.
>+parport1: PC-style at 0x278, irq 5 [PCSPP(,...)]
>+lp1: using parport1 (interrupt-driven).
>
>As a result, my parallel port stops working. Any more information I can
>provide?
I don't know little about Linux specific, but generally,
a Printer port device will appear several times as ACPI devices.
If you forget to check device status (_STA),
confliction will occur as you got.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-07 4:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 2:21 PNPACPI breaks my asus k6-2 parallel port Matthew Wilcox
[not found] ` <20041207022133.GB22171-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-12-07 2:37 ` Li Shaohua
2004-12-07 4:14 ` Takanori Watanabe [this message]
[not found] ` <200412070414.NAA01833-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
2004-12-07 15:40 ` Nate Lawson
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 1:08 Li, Shaohua
[not found] ` <16A54BF5D6E14E4D916CE26C9AD30575BB93FB-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-12-08 2:17 ` Takanori Watanabe
[not found] ` <200412080217.LAA15383-yzSWc4HAx5xL9jVzuh4AOg@public.gmane.org>
2004-12-08 2:23 ` Li Shaohua
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200412070414.NAA01833@axe-inc.co.jp \
--to=takawata-yzswc4hax5xl9jvzuh4aog@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=matthew-Ztpu424NOJ8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox