[driverloader] Re: Broadcom 14e4:4320, it's a bit better now with dldr 1.34...

Marc Boucher marc at linuxant.com
Sun Nov 9 14:39:34 EST 2003


Hi Jan,

I'm glad it works on your system with 2.4. Good that we're finally
narrowing on the issue, which seems specific to your 2.6 kernels.

let me look into a few things and recontact you for further tests,
and perhaps to review your kernel configuration since the problem
doesn't happen on our 2.6 kernels here.

Marc

On Sun, Nov 09, 2003 at 08:04:06PM +0100, Jan Slupski wrote:
> On Sun, 9 Nov 2003, Marc Boucher wrote:
> 
> > how about 2.4?
> 
> Just tried.
> It is an old 2.4.22-rc1 (last I had ready, before switching to 2.6)
> I don't remeber if any patches was applied.
> 
> Anyway:
> 
> It seems to be all right, here. (do this answer make you happy or
> opposite?)
> 
> No suspicious init activity, processor cool, associaite with AP.
> 
> Is it time to move to 2.4? ;)
> 
> Jan
> 
> >
> > Marc
> >
> > On Sun, Nov 09, 2003 at 07:43:40PM +0100, Jan Slupski wrote:
> > > On Sun, 9 Nov 2003, Marc Boucher wrote:
> > >
> > > > Hi Jan,
> > > >
> > > > We haven't yet been able to reproduce the problem you are describing
> > > > with 'init' using 100% of CPU.
> > > >
> > > > Perhaps it is due to the custom 2.6.0-test9-bk13 prerelease kernel
> > > > snapshot with the 'extra' patches (like swsusp) that have been applied
> > > > to your system.
> > >
> > > Unfortunatelly at vanilia -test9 it is exactly the same.
> > > I tried with ACPI, USB, and both  ACPI & USB turned off.
> > >
> > > Haven't tried 1.37 yet, but ChangeLog do not give me much hope.
> > >
> > > >
> > > > Even if we cannot officially support non-standard kernels, I'll try
> > > > to build a 2.6.0-test9-bk13 to test (already tried 2.6.0-test9 and
> > > > it seems to work fine) and let you know the result..
> > > >
> > > > Has anybody else encountered the problem which Jan describes below?
> > > >
> > > > Regards
> > > > Marc
> > > >
> > > > On Sun, Nov 09, 2003 at 03:26:29PM +0100, Jan Slupski wrote:
> > > > >
> > > > > Version v1.35 helped much. There are no more hangs on startup,
> > > > > I can associate with AP every time (probably because of no restricted
> > > > > option ;)
> > > > >
> > > > > But now just after loading the module the 'init' process uses 100% of
> > > > > CPU, so temerature of processoer rises dramatically, etc, etc.
> > > > >
> > > > > It remains even if I rmmod the driverloader.
> > > > > The processor (or sth else) is so busy, that I cannot even shutdown.
> > > > > I got:
> > > > >  Broadcast message from root (tty4) (Sun Nov  9 15:20:56 2003):
> > > > >  The system is going down for reboot NOW!
> > > > >  init: timeout opening/writing control channel /dev/initctl
> > > > >
> > > > >
> > > > > The same problems with v1.36.
> > > > >
> > > > >
> > > > > Jan
> > > > >
> > > > > PS
> > > > > I also downloaded the newest drivers from HP site, the sys file is exactly
> > > > > the same as Belkin one, the inf file differs a bit (eg, has proper PCI ids
> > > > > for Broadcom)
> > > > >
> > > > >    _  _  _  _  _____________________________________________
> > > > >    | |_| |\ |  S L U P S K I              jslupski at email.com
> > > > >  |_| | | | \|                          http://www.juljas.net
> > > >
> > > > _______________________________________________
> > > > driverloader mailing list
> > > > driverloader at lists.linuxant.com
> > > > https://www.linuxant.com/mailman/listinfo/driverloader
> > > >
> > >
> > >    _  _  _  _  _____________________________________________
> > >    | |_| |\ |  S L U P S K I              jslupski at email.com
> > >  |_| | | | \|                          http://www.juljas.net
> > >
> >
> 
>    _  _  _  _  _____________________________________________
>    | |_| |\ |  S L U P S K I              jslupski at email.com
>  |_| | | | \|                          http://www.juljas.net
> 


More information about the driverloader mailing list