Re: Errors in dmesg output

Hi,

the 'export not found' error message is generated because DriverLoader 
doesn't yet support the Windows driver you have uploaded to the Web 
Configurator. As a workaround, trying with another version of the 
Windows XP driver, preferably an older version might solve the problem. 
These could be available on the CD/DVD that came with the wireless 
device or on the web site of the vendor of the device.

Copying the 'ntoskrnl.exe' and the 'hal.dll' files from a Windows 
installation will not solve the problem and it is the most likely cause 
of the crash.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
[email protected]



Alfred Krohmer wrote:
> Based on the output of lspci -v I'm using a `AR5006EG` WLAN card in a ASUS X51R notebook. After adding the driver from the archive I downloaded form the ASUS website the webinterface told me, that "It seems that your device is either not present or not supported by the installed driver(s)".
> The output of `dmesg` tells me that the driver tries to load `ntoskrnl.exe`, `hal.dll` and other Windows-DLLs:
> [ 1597.252000] driverloader: stack=8192/64/0 REGPARM SMP
> [ 1597.256000] usbcore: registered new interface driver driverloader
> [ 1597.428000] driverloader: ar5211.sys: 0xf97a8000..0xf98293c0 entry = f97dd2a0 (pbase = 0x10000)
> [ 1597.428000] driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
> [ 1597.428000] driverloader: ar5211.sys: export not found: ZwDeleteKey (ntoskrnl.exe)
> [ 1597.428000] driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
> [ 1597.428000] driverloader: ar5211.sys: export not found: ZwCreateKey (ntoskrnl.exe)
> [ 1597.428000] driverloader: /var/lib/driverloader/ntoskrnl.exe: unable to open (err=-2)
> [ 1597.428000] driverloader: ar5211.sys: export not found: IoOpenDeviceRegistryKey (ntoskrnl.exe)
> [ 1597.428000] driverloader: unable to load "ar5211.sys" (-6)
> 
> I tried to copy these files from my Windows XP installation to `/var/lib/driverloader` and reloading the driver by `rmmod driverloader` and `modprobe driverloader`. Afterwards my system freezed and the next reboot stopped with a "Kernel panic" error. Removing the driverloader-modules by `dldrconfig --remove` in a rescue system made the system booting again.
> 
> I'd like to know whether it is necessary to use these Windows system files or if this is a bug.