[driverloader] Driverloader causes system crash
Linuxant support (Jonathan)
support at linuxant.com
Thu Nov 30 11:45:30 EST 2006
Hi,
Windows XP driver are often in a self-extractable EXE files. It is
possible that you can use the 'unzip' command on them under Linux to
obtain the driver. CAB files, which can also hold the driver, can
generally be extracted under Linux using one the following tools:
cabextract: http://www.kyz.uklinux.net/cabextract.php
unshield: http://synce.sourceforge.net/synce/unshield.php
It some cases, it is important that you use the Windows XP driver
provided by the vendor as they might the only ones which is able to
enable the RF signal of the wireless device. It is a possible reason why
the Windows driver I gave the link to in my last post does not work with
your wireless device.
Regards,
Jonathan
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com
JT wrote:
> Is there an easy way to locate the correct driver on my WXP recovery
> disks? I cannot locate a bcmwl5.inf file within the i386 directory. Any
> ideas? THANKS. None of the drivers ive tried are working. Only the one
> originally from HP causes the wifi indicator to light (as my machine
> freezes)!
>
>
> ----- Original Message ----
> From: Linuxant support (Jonathan) <support at linuxant.com>
> To: JT <jtreister at yahoo.com>
> Cc: driverloader at lists.linuxant.com
> Sent: Wednesday, November 29, 2006 4:16:53 PM
> Subject: Re: [driverloader] Driverloader causes system crash
>
> Hi,
>
> you can manually delete the Windows driver with the following command in
> a root shell:
>
> ---
> rm -fr /var/lib/driverloader/*
> ---
>
> It is possible that, depending on the PCI ID of your wireless device,
> that the following driver will be compatible:
>
> http://ftp.us.dell.com/network/R74092us.EXE
>
> Under Linux, you can use the 'unzip' command on the .EXE file to extract
> the Windows driver. The required .INF file will be named
> 'AR/bcmwl5a.inf' inside the .EXE file.
>
> Alternatively, it is possible that an older version of the driver might
> be available on the web site of the vendor of the wireless device or on
> the CD/DVD that came with it.
>
> Regards,
>
>
> Jonathan
> Technical specialist / Linuxant
> www.linuxant.com <http://www.linuxant.com>
> support at linuxant.com
>
>
>
> JT wrote:
> > The driver package I downloaded from HP is 'sp33008.exe'. The inf file
> > (bcmwl5.inf): DriverVer=03/23/2006, 4.40.19.0
> >
> > It seems I had to load each of these via the driverloader web client:
> >
> > bcmwl5.inf
> >
> > bcmwl5.sys
> >
> > bcmwl564.sys
> >
> >
> >
> > How do I remove the problem driver (which of the (3) files)? I cannot
> > start the driverloader daemon without crashing my system (it is
> > currently disabled).
> >
> >
> >
> > My hardware is Broadcom 4311 (Rev 1). Where can I find previous versions
> > of the driver?
> >
> >
> >
> > THANKS!
> >
> > ----- Original Message ----
> > From: Linuxant support (Jonathan) support at linuxant.com
> > <mailto:support at linuxant.com>
> > Cc: driverloader at lists.linuxant.com
> > Sent: Wednesday, November 29, 2006 10:05:19 AM
> > Subject: Re: [driverloader] Driverloader causes system crash
> >
> > Hi,
> >
> > please try with different versions of the Windows XP driver to see if
> > there is a difference. If you require more assistance, please send to
> > support at linuxant.com the output of 'dumpdiag'. Type the following in a
> > root shell:
> >
> > ---
> > dldrconfig --dumpdiag
> > ---
> >
> > If the previous command crashes your machine, pl,ease tyr this one
> instead:
> >
> > ---
> > dldrconfig --noprobe --dumpdiag
> > ---
> >
> > Just send us the generated file located in /tmp
> > ('driverloaderdiag.txt'). It'll help us solve the problem.
> >
> > The default DHCP client shipped with SuSE 10.0 should work fine with
> > DriverLoader and you do not need to use ndiswrapper at all.
> >
> > Regards,
> >
> >
> > Jonathan
> > Technical specialist / Linuxant
> > www.linuxant.com <http://www.linuxant.com> <http://www.linuxant.com/>
> > support at linuxant.com
> >
> >
> >
> > Jeremy Treister wrote:
> > > Just installed. Seemed to be going well.
> > > I got web interface. I registered then applied license key. Once I
> > > applied key, system crashed. I can boot up only by disabling
> > > driverloader. If I manually start in runlevel editor, same problem.
> > > Which dhcp clients and ndiswrapper packages do I need? Suse 10.0
> > >
> > >
> > >
> ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > driverloader mailing list
> > > driverloader at lists.linuxant.com
> > > https://www.linuxant.com/mailman/listinfo/driverloader
> > _______________________________________________
> > driverloader mailing list
> > driverloader at lists.linuxant.com
> > https://www.linuxant.com/mailman/listinfo/driverloader
> >
> >
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > driverloader mailing list
> > driverloader at lists.linuxant.com
> > https://www.linuxant.com/mailman/listinfo/driverloader
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader
More information about the driverloader
mailing list