[driverloader] Unable to connect to AP

Linuxant support (Jonathan) support at linuxant.com
Tue Jan 24 11:27:30 EST 2006


we can see the following error message generated a few times in your 

OsAllocateFlags(200344, 0x0): failed, OsIrql=2
driverloader: NdisAllocateMemoryWithTag: OsAllocate(Length=200336) failed

It seems that the kernel is unable to allocate the memory required by 
the Windows XP driver ans this could be the source of the problem. 
Please try with different versions of the Windows XP driver to see if 
there is a difference. Different Linux kernels might also improve this 
situation, for example, please try to upgrade the kernel to test latest 
one available for Fedora Core 4.

According to this message in your 'dmesg':

ACPI: PCI Interrupt 0000:00:13.0[A] -> Link [LNKA] -> GSI 11 (level, 
low) -> IRQ 11

your wireless device was assigned IRQ 11 by the kernel. If you use the 
'lspci' to see the information about PCI hardware, please make sure that 
you run this command as root as some of this information is only 
available to this user.


Technical specialist / Linuxant
support at linuxant.com

Jeff Jackson wrote:
> To: DriverLoader Support Team
> Re: unable to access AP
> 	Let me start with apologizing, I'm a Linux Newbie, who has spoken as
> a Windows Sysadmin for the last 15 years. I just started learning Linux this
> month and have come up against a brick wall getting my computer on my home
> network. 
> 	I am using the Fedora Core 4 distribution and a Belkin F5D7000
> version: 5000 wireless NIC.  The NIC shows up in my network configuration.
> Also as a precaution I have completely disabled WEP on my router, the only
> security I have is MAC address restrictions, and the MAC address is in my
> router. When I try to activate the NIC it reports that "Determining IP
> information for eth0.failed."  When I look under hardware and network
> configuration the IRQ reports "unknown" and the MEM, IO, IO1, IO2, DMA0, and
> DMA1 are all blank.  I believe that this is the problem, but I am not sure
> of the settings to plug into it to make it work.  
>            I have included every log mentioned in the FAQ that I could find
> that might allow you to help me reach a resolution. Thank you in advance for
> all your help.  I'm sure that once I get this work driverloader will be an
> incredible tool and I look forward to further development on this software. 
> Sincerely,
> 	Jeff
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader

More information about the driverloader mailing list