Re:parport disabled?

[castet . matthieu]

Hi,


> Whenever I "modprobe parport_pc", I get this message:
> 
> Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b activated.
> Jan 27 10:55:47 hummus kernel: parport: PnPBIOS parport detected.
> Jan 27 10:55:47 hummus kernel: pnp: Device 00:0b disabled.
> 
> and the parallel port is unusable ever after.
> This is with Kernel 2.6.10-ac10 and 2.6.10-ac11
> 
> How can I make my parallel port usable again?
Try disabling acpi.

If it works, with acpi enabled send a "for i in /sys/bus/pnp/devices/*; do cat
$i/*; done"

I could be related to http://bugzilla.kernel.org/show_bug.cgi?id=3912
and [1]

regards,

Matthieu


Adam Belay wrote:

> On Mon, Nov 29, 2004 at 10:30:29PM +0100, matthieu castet wrote:
>
>> matthieu castet wrote:
>>
>>> Hello,
>>>
>>> acpi need that the order of the resources are the same as the
>>> possible resources. It could be the same for pnpbios.
>>>
>>> I most of case, it works quite well, but if the independent options
>>> are after dependent, it doesn't work :
>>> in pnp manager, pnp_assign_resources first uses independent_options
>>> and then dependent ones. So we break the order, and it doesn't work.
>>>
>>> What the rules for independent options in pnpbios ?
>>>
>>> If it works like pnpacpi, it is allowed to define them only before
>>> or after dependent option.
>>>
>>> So a solution could be to have a second independent option, and use
>>> it after dependent options in pnp_assign_resources.
>>>
>>> What do you think of that ?
>>>
>>> Matthieu CASTET
>>>
>>
>> I forgot to say that it is probably the bug of meelis roos.
>>
>
>
> Hmm, I agree this is a problem, and it will be interesting to see if
> it
> resolves Meelis's issue.  I don't think a second independent option
> would be a
> clean solution.  I think the a slight redesign is in order, with a
> focus on
> ensuring resources are assigned in the order they are advertised in
> all cases.
> I'm hacking something together now. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/