Messages in this thread | | | From | CD323 <> | Subject | Re: kmod freezes | Date | Sat, 4 Apr 1998 15:16:38 -0800 (PST) |
| |
> > On Sat, 4 Apr 1998, Tim Waugh wrote: > > >I don't believe that preventing that configuration in the first place is > >an answer, because maybe one day we'll have the printer driver trying to > >set itself up with a lowlevel parport driver each time an open() is done > >on an lp device if it failed at initialisation time. > > I agree with you, kmod must be fixed to handle that.
hello -
i believe that what you're referring to is a problem that early versions of kmod had with modules loading other modules during their own init_module() phase - we are currently testing and debugging a patch which solves this problem, and which is available by searching linux-kernel archives (patch was submitted by Greg Zornetzer). as i have said before, and will say again, kirk and i have always intended to support these behaviors. if, after applying greg's patch, you are still having difficulty with your parallel port driver loading its various bits and pieces, please let me know.
> BTW, there is another annoying bug: if I don' t add this line: > > post-install parport modprobe -k parport_lowlevel > > to /etc/conf.modules, parport_pc is not loaded at it should be. This > workaround change also the time when parport_pc is loaded and don' t work > in a configuration of CONFIG_PARPORT=y CONFIG_PARPORT_PC=m and > CONFIG_PRINTER=m.
this is not a kmod issue. please take this up with the parallel port driver maintainers. it looks to me like parport_pc is at no time requested by any of the other parallel port driver components, and so needs to be "manually" loaded from /etc/modules.conf. thanks.
-cyrus durgin. cider@speakeasy.org.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |