[driverloader] tel 2100 on D800 - linux crash

[Emmanuel Khamissian]

Hi,

I have upgraded the driverloader version to 1.38 : Exactly the same
problem ! Linux crash !

i have tried 2.6.0test6  and 2.6.0test9, 1.37 and 1.38. No diff,
samething.

Do you expect a solution for this trouble ?

Regards,


On lun, 2003-11-10 at 18:09, Emmanuel Khamissian wrote:
> Hello,
> 
> I have found another trouble with v 1.37:
> the init(1) process take more than 60% of CPU time ! (often 99%).
> Even if i remove the driverloader module, the problem persists.
> 
> Thanks.
> 
> 
> On lun, 2003-11-10 at 16:22, MartinG at gmx.ch wrote:
> > > 
> > > Hi,
> > > 
> > Hi
> > 
> > > I am testing driverloader on my host, it's a D800 from DELL with a
> > > Centrino and 2100 3B MiniPCI Adapter. I have linux 2.6.0test9 on it.
> > > 
> > > When i try to configure via webconf and i add .sys the system crash and
> > > i need to reboot it.
> > > I haven't any log.
> > > 
> > > This is my driverloaderdiag.txt :
> > ...
> > 
> > > driverloader: module license 'see LICENSE file; Copyright (c)2003
> > > Linuxant inc.' taints kernel.
> > > driverloader: probe of 0000:00:01.0 failed with error -5
> > > driverloader: probe of 0000:00:1e.0 failed with error -5
> > > driverloader: probe of 0000:00:1f.0 failed with error -5
> > > driverloader: probe of 0000:00:1f.6 failed with error -5
> > > driverloader: probe of 0000:01:00.0 failed with error -5
> > > driverloader: probe of 0000:02:01.3 failed with error -5
> > > driverloader: unable to load "/var/lib/driverloader/w70n51.sys" (-5)
> > > driverloader: probe of 0000:02:03.0 failed with error -5
> > > 
> > >
> > ...
> > > 
> > > Does somebody have any idea, and can help me ? 
> > 
> > I'd really like to be able to help you as I've exactly the same problem. The
> > same adapter, same kernel version and the same errors. But I'm running
> > Debian SID on a ASUS M2400N. However, I've already sent my dumpdiag-output to
> > support at linuxant.org but haven't got any response yet. Maybe they can it figure
> > it out now, as they have two different systems with the same error. 
> > At least, I hope so...;-)
> > 
> > PS: Have you tried another kernel version? With 2.4.23 everything worked
> > fine for me...
> > > 
> > > Regards,
> > > 
> > > -- 
> > > 
> > > Emmanuel Khamissian
-- 
Emmanuel Khamissian <ekhamissian at highnet.org>