[driverloader] kernel error with asus centrino

Reinout Smit reinout at xplo.net
Fri Feb 11 18:39:31 EST 2005


Hi,

It doesn't matter if i use WEP or not.
The error message with the hung part in it has come back after 2/3 hours
of using the interface.
My network is being setup with a ADSL modem connected to a Linksys 54G
AP/Router
I also noticed that when the modem is going down the connection between
the router and my laptop is also down.
Is it possible that this:
ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 4 (level, low) -> IRQ 4
is also a part of the problem?

Reinout

Op vr, 11-02-2005 te 09:58 -0500, schreef Linuxant support (Jonathan):
> Hi,
> 
> this error message means that a packet failed to be sent with the 
> wireless interface. If you are unable to use your wireless interface or 
> you experience significant slowdown, it is possible that it is the 
> source of the problem. It could also be generated when wrong WEP 
> settings are used.
> 
> Are you able to use your wireless interface? Is there a difference if 
> you use WEP or not? Did you started to obtain these error messages in 
> your 'dmesg' when you started using WEP?
> 
> Regards,
> 
> 
> Jonathan
> Technical specialist / Linuxant
> www.linuxant.com
> support at linuxant.com
> 
> 
> Reinout Smit wrote:
> > What does this error mean:
> > 
> > netndis_xmitcomplete_handler: err -5
> > netndis_xmitcomplete_handler: err -5
> > netndis_xmitcomplete_handler: err -5
> > netndis_xmitcomplete_handler: err -5
> > 
> > Reinout
> > Op do, 10-02-2005 te 13:12 -0500, schreef Linuxant support (Jonathan):
> > 
> >>Hi,
> >>
> >>you should use the network configuration tool of your Linux distribution 
> >>to setup your WEP key. For Fedora Core, this tool can be started with 
> >>the 'neat' command in a shell. This tool can also be launched from the 
> >>system menu.
> >>
> >>Regards,
> >>
> >>
> >>Jonathan
> >>Technical specialist / Linuxant
> >>www.linuxant.com
> >>support at linuxant.com
> >>
> >>
> >>Reinout Smit wrote:
> >>
> >>>Got it workend with a newer driver from intel
> >>>I already knew it was working because i've been using winxp for a few
> >>>month's on this laptop.
> >>>
> >>>Only got my wep at a 64 bits 10 hex digits code
> >>>What is the best way to add this to my eth1 configuration?
> >>>
> >>>I must admit that this driverloader is working great so far.
> >>>
> >>>Reinout
> >>>
> >>>Op do, 10-02-2005 te 11:43 -0500, schreef Linuxant support (Jonathan):
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>this is strange, it seems that the Windows XP driver detected an invalid 
> >>>>value from the hardware and at the end of the dump, you are unable to 
> >>>>send or receive packets with the wireless interface.
> >>>>
> >>>>Please try with different versions of the Windows XP driver to see if 
> >>>>there is a difference. You could also try to use this wireless card 
> >>>>under Windows XP just to make sure that this is not a hardware related 
> >>>>issue.
> >>>>
> >>>>Regards,
> >>>>
> >>>>
> >>>>Jonathan
> >>>>Technical specialist / Linuxant
> >>>>www.linuxant.com
> >>>>support at linuxant.com
> >>>>
> >>>>
> >>>>Reinout Smit wrote:
> >>>>
> >>>>
> >>>>>Hi,
> >>>>>
> >>>>>trying to use driverloader on a ASUS M6727NE centrino with a intel
> >>>>>2200BG on Fedora Core 3 with kernel 2.6.10-1.760_FC3.stk16
> >>>>>Can't get it to work,
> >>>>>underneath is a part of the dmesg output
> >>>>>
> >>>>>usbcore: deregistering driver driverloader
> >>>>>divert: freeing divert_blk for eth1
> >>>>>driverloader: stack=16384/64/0 REGPARM
> >>>>>usbcore: registered new driver driverloader
> >>>>>driverloader: w22n51.sys: 0xe0c1c000..0xe0dae080 entry = e0c1c300 (pbase = 0x10000)
> >>>>>ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 4 (level, low) -> IRQ 4
> >>>>>divert: allocating divert_blk for eth1
> >>>>>eth1: New link status: Disconnected (0002)
> >>>>>eth1: WPA, TKIP, WEP128, WEP64 supported
> >>>>>eth1: Intel(R) PRO/Wireless 2200 LAN Card Driver at 0000:02:02.0 (MAC address 00:0E:35:82:E0:20) ready
> >>>>>eth1: New link status: Connected (0001)
> >>>>>usbcore: deregistering driver driverloader
> >>>>>divert: freeing divert_blk for eth1
> >>>>>driverloader: stack=16384/64/0 REGPARM
> >>>>>usbcore: registered new driver driverloader
> >>>>>driverloader: w22n51.sys: 0xe0c1c000..0xe0dae080 entry = e0c1c300 (pbase = 0x10000)
> >>>>>ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 4 (level, low) -> IRQ 4
> >>>>>divert: allocating divert_blk for eth1
> >>>>>eth1: New link status: Disconnected (0002)
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorCode=0xc00013a7 NumberOfErrorValues=2
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorValue 0=0x4e4f4c41
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorValue 1=0x00000338
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorCode=INVALID_VALUE_FROM_ADAPTER NumberOfErrorValues=2
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorValue 0=0x4e4f4c41
> >>>>>driverloader: NdisWriteErrorLogEntry: ErrorValue 1=0x00000001
> >>>>>eth1: WPA, TKIP, WEP128, WEP64 supported
> >>>>>eth1: Intel(R) PRO/Wireless 2200 LAN Card Driver at 0000:02:02.0 (MAC address 00:0E:35:82:E0:20) ready
> >>>>>eth1: New link status: Connected (0001)
> >>>>>eth1: no IPv6 routers present
> >>>>>usbcore: deregistering driver driverloader
> >>>>>divert: freeing divert_blk for eth1
> >>>>>driverloader: stack=16384/64/0 REGPARM
> >>>>>usbcore: registered new driver driverloader
> >>>>>driverloader: w22n51.sys: 0xe0c1c000..0xe0dae080 entry = e0c1c300 (pbase = 0x10000)
> >>>>>ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 4 (level, low) -> IRQ 4
> >>>>>divert: allocating divert_blk for eth1
> >>>>>eth1: New link status: Disconnected (0002)
> >>>>>eth1: WPA, TKIP, WEP128, WEP64 supported
> >>>>>eth1: Intel(R) PRO/Wireless 2200 LAN Card Driver at 0000:02:02.0 (MAC address 00:0E:35:82:E0:20) ready
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>eth1: no IPv6 routers present
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>driverloader: ndisWrapCheckForHangTimerFunc_stk: PCI-0000:02:02.0-8086:4220-8086:2701 hung
> >>>>>
> >>>>>_______________________________________________
> >>>>>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
> _______________________________________________
> driverloader mailing list
> driverloader at lists.linuxant.com
> https://www.linuxant.com/mailman/listinfo/driverloader
> 
> 



More information about the driverloader mailing list