PNPACPI breaks my asus k6-2 parallel port

PNPACPI breaks my asus k6-2 parallel port

[Matthew Wilcox]

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?

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain


-------------------------------------------------------
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/

Re: PNPACPI breaks my asus k6-2 parallel port

[Li Shaohua]

On Tue, 2004-12-07 at 10:21, 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?
Looks like one parport is disabled before but re-assign resources by
PNP. Could you please send me the 'acpidmp' output?

Thanks,
Shaohua



-------------------------------------------------------
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/

Re: PNPACPI breaks my asus k6-2 parallel port

[Takanori Watanabe]

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/

Re: PNPACPI breaks my asus k6-2 parallel port

[Nate Lawson]

Takanori Watanabe wrote:
> 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.

You are right Watanabe-san.  It appears linux just parses all resource 
sets in _PRS as separate devices instead of parsing the DPFs and 
treating them as separate sets for a single device.

-- 
Nate



-------------------------------------------------------
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/

RE: PNPACPI breaks my asus k6-2 parallel port

[Li, Shaohua]

>>>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.
>
>You are right Watanabe-san.  It appears linux just parses all resource
>sets in _PRS as separate devices instead of parsing the DPFs and
>treating them as separate sets for a single device.
Hi Nate,
Could you please clarify it? Linux did check _STA, and only assigned
dependent resources (that is one set of resources) from _PRS to a
device.
In Wilcox's case, LPT (PNP0400) has resources of 0x378, irq 7. PNPACPI
can only assign 0x278, irq 5 to ECP (PNP0401) the resources are listed
in ECP's _PRS. ECP possibly isn't a parport (Dunno why it said a parport
detected), it can use DMA per the _PRS.

Thanks,
Shaohua 


-------------------------------------------------------
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/

Re: PNPACPI breaks my asus k6-2 parallel port

[Takanori Watanabe]

In message <16A54BF5D6E14E4D916CE26C9AD30575BB93FB-4yWAQGcml66iAffOGbnezLfspsVTdybXVpNB7YpNyf8@public.gmane.org
>, "Li, Shaohua" 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 =3D 4) is a 16550A
>>>>+ttyS1 at I/O 0x2f8 (irq =3D 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.
>>
>>You are right Watanabe-san.  It appears linux just parses all resource
>>sets in _PRS as separate devices instead of parsing the DPFs and
>>treating them as separate sets for a single device.
>Hi Nate,
>Could you please clarify it? Linux did check _STA, and only assigned
>dependent resources (that is one set of resources) from _PRS to a
>device.
>In Wilcox's case, LPT (PNP0400) has resources of 0x378, irq 7. PNPACPI
>can only assign 0x278, irq 5 to ECP (PNP0401) the resources are listed
>in ECP's _PRS. ECP possibly isn't a parport (Dunno why it said a parport
>detected), it can use DMA per the _PRS.

In many case, single Parallel port is appeared as multiple device,
like ECP port, simple parport,etc ...  in ACPI name space 
with only one of them activated. And if you try to wake up all resources,
only the last activated one will make available, I think.


-------------------------------------------------------
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/

Re: PNPACPI breaks my asus k6-2 parallel port

[Li Shaohua]

On Wed, 2004-12-08 at 10:17, Takanori Watanabe wrote:
> >Could you please clarify it? Linux did check _STA, and only assigned
> >dependent resources (that is one set of resources) from _PRS to a
> >device.
> >In Wilcox's case, LPT (PNP0400) has resources of 0x378, irq 7. PNPACPI
> >can only assign 0x278, irq 5 to ECP (PNP0401) the resources are listed
> >in ECP's _PRS. ECP possibly isn't a parport (Dunno why it said a parport
> >detected), it can use DMA per the _PRS.
> 
> In many case, single Parallel port is appeared as multiple device,
> like ECP port, simple parport,etc ...  in ACPI name space 
> with only one of them activated. And if you try to wake up all resources,
> only the last activated one will make available, I think.
Thanks Watanabe-san. Wilcox's case possibly is like what you said. If
so, the fix isn't straightforward. PNP layer always automatically
actives disabled devices. Possibly the BIOS (_STA) should tell us the
device is absent.

Thanks,
Shaohua



-------------------------------------------------------
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/