K1/M1 Driver Development - Page 3

Arrakiv · 02-09-2010, 10:47 AM

Silvers: I understand that. But they are still beta drivers. They're not fully released yet and they don't work correctly. You may be downloading this as a fix - and for many people, it may actually be one - but they are beta drivers with everything that is attached to what that is. It isn't a fix - the fix will be out soon.

We're also collecting an awful lot of feedback from you all to make certain that I can link to drivers that will do just that.

ironleg · 02-09-2010, 05:46 PM

I just had an RMA om my killer nic. I am using the 4.0.0.6 drivers because the beta drivers just caused problems. and this is a new replacement card.I am thinking very seriously of buying a xeno but have doubts because of some issues I have heard here. I like the Ideas of the PCI_E. and that it has FNA APPS that the k1/m1 will never have.when i had it using XP i loved it. I don't want to get caught in a design flaw or driver issue flaws that make it unusable and money not well spent. I can use the extra 100.00 on Ram, CPU or other components. I explained to support the issues I was having and they said they were going to RMA it I asked if they could just RMA it with the cheaper XENO card and support said they could not.I know we paid 200-250.00 for the card and we all want it just to work and they are working on it, so I ask this ; should I buy a xeno card and what mobo should i avoid. (yes I saw a brief list here).I believe killer will get it right and we will all be eating crow in the future.

Any advice good or bad is welcome.
thank you

Arrakiv · 02-10-2010, 10:32 AM

Is the card actually dead, or was it an issue with the drivers?

If it is the latter, please try out the latest stable build that just came out, and hopefully that will clear up any issues for you.

As much as I'd love to tell you to go, run out, and buy a Xeno... I'd be happier seeing your current card working well. :-)

d2thez · 02-10-2010, 02:56 PM

So have the "Stable Release" drivers been changed even a little bit from the beta release? The versions numbers are exactly the same which would make me think not.

ironleg · 02-10-2010, 05:52 PM

I get a failed pipe error now with the visual basic error at C\...
If the card was the issue I wanted to see if they would trade me with a Xeno to see if it would fix the problem.I have tried it with a clean install after writing zeros to a 1 tb drive;(that took some time..) and I have tried different windows 7 x 64 versions. I know the xeno is priced less than what I paid for the killer nic i have. I don't wish to sound cheap but want a resolution to this issue. I still think Bigfoot is the best card and the right software/hardware is just almost there.I told my brothers friend who just opened a computer shop about Bigfoot gaming cards and they never heard of them. I am hoping to get him to include them in his inventory.

Whity · 02-11-2010, 05:44 PM

well installed new release of k1 drivers and seems i get firmware ip tables not installed is this normal or what

LLR-64 (Version=4.1.0.37) Configuration request
KillerNIC K1 LLR Mode is currently set to GAME Mode
LLR Version Number = 4.1.0.14
Proxy Version Number = 4.1.0.15
Firmware Version Number = 4.1.0.10
Card SubSystemID = 0x201 (indicates a K1)
Number of Raw NIC SGLs = 1
Number of LLR SGLs = 1
Current LLR Ping Control= 0
Current LED CONTROL = Blinking
LLR Game Priority = Boosted
Boot Partition = Side B
Boot Status Value = 0
Boot Running Status = KillerNic Boot Successful
Boot Strap Version = 0x000003e8
KillerNIC Secondary IP Address=172.31.254.2 Mask=255.255.255.0
KillerNIC Tx Poll Timer Setting = 1000us
KillerNIC Rx Poll Timer Setting = 1000us
KillerNIC Firmware IP_TABLES is NOT Loaded
KillerNIC K1 FNA support= Enabled
LinkSpeed = 100Mps Mode=Full Duplex
<==SetUdpConfig

Winsock 32-bit Catalog:
=======================
1271 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1272 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1273 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1274 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1112 - MSAFD Pgm (RDM)
1113 - MSAFD Pgm (Stream)
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1270 - BfLLR

Winsock 64-bit Catalog:
=======================
1271 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1272 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1273 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1274 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1112 - MSAFD Pgm (RDM)
1113 - MSAFD Pgm (Stream)
1007 - RSVP TCPv6 Service Provider
1008 - RSVP TCP Service Provider
1009 - RSVP UDPv6 Service Provider
1010 - RSVP UDP Service Provider
1270 - BfLLR

Killer Suite Version: 4.1.0.144

Tekgun · 02-11-2010, 07:08 PM

I think that just means your Killer firewall is turned off. Turn it on and the configuration request should show the IP Tables loaded.

d2thez · 02-11-2010, 08:27 PM

Ok, installed the final release on my K1 in Win7 x64. The previous release drivers 4.1.0.37 beta worked without fault in everything. I did a total purge of those before installing the new final drivers.

Problem is Modern Warfare 2 refuses to connect to IWNET while in Game Mode. It only works in App Compat Mode. That is the only issue I have seen. Unfortunately, this game is huge! ! How can a bug like this make it past testing, especially when it worked fine with the previous driver? This is the game of the moment folks!! I need my UDP offloading!!!!!!!!!!

Here is my config:

LLR-64 (Version=4.1.0.37) Configuration request
KillerNIC K1 LLR Mode is currently set to GAME Mode
LLR Version Number = 4.1.0.14
Proxy Version Number = 4.1.0.15
Firmware Version Number = 4.1.0.10
Card SubSystemID = 0x201 (indicates a K1)
Number of Raw NIC SGLs = 1
Number of LLR SGLs = 1
Current LLR Ping Control= 0
Current LED CONTROL = Blinking
LLR Game Priority = Boosted
Boot Partition = Side B
Boot Status Value = 0
Boot Running Status = KillerNic Boot Successful
Boot Strap Version = 0x000003e8
KillerNIC Secondary IP Address=192.168.254.2 Mask=255.255.0.0
KillerNIC Tx Poll Timer Setting = 1000us
KillerNIC Rx Poll Timer Setting = 1000us
KillerNIC Firmware IP_TABLES is NOT Loaded
KillerNIC K1 FNA support= Enabled
LinkSpeed = 100Mps Mode=Full Duplex
<==SetUdpConfig
Winsock 32-bit Catalog:
=======================
1017 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1018 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1016 - BfLLR
Winsock 64-bit Catalog:
=======================
1017 - BfLLR over [MSAFD Tcpip [TCP/IP]]
1018 - BfLLR over [MSAFD Tcpip [UDP/IP]]
1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]]
1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]]
1001 - MSAFD Tcpip [TCP/IP]
1002 - MSAFD Tcpip [UDP/IP]
1003 - MSAFD Tcpip [RAW/IP]
1004 - MSAFD Tcpip [TCP/IPv6]
1005 - MSAFD Tcpip [UDP/IPv6]
1006 - MSAFD Tcpip [RAW/IPv6]
1016 - BfLLR

Killer Suite Version: 4.1.0.144

02-09-2010, 10:47 AM	#21
Arrakiv Community Manager Killer Performance Join Date: Jul 2009 Location: Austin, Texas Posts: 501	Re: K1/M1 Driver Development Silvers: I understand that. But they are still beta drivers. They're not fully released yet and they don't work correctly. You may be downloading this as a fix - and for many people, it may actually be one - but they are beta drivers with everything that is attached to what that is. It isn't a fix - the fix will be out soon. We're also collecting an awful lot of feedback from you all to make certain that I can link to drivers that will do just that. __________________ Sean Bulger Community Manager Bigfoot Networks Facebook \| Twitter \| Steam \| Blog

02-09-2010, 05:46 PM	#22
ironleg High Ping Join Date: Aug 2007 Posts: 62	Re: K1/M1 Driver Development I just had an RMA om my killer nic. I am using the 4.0.0.6 drivers because the beta drivers just caused problems. and this is a new replacement card.I am thinking very seriously of buying a xeno but have doubts because of some issues I have heard here. I like the Ideas of the PCI_E. and that it has FNA APPS that the k1/m1 will never have.when i had it using XP i loved it. I don't want to get caught in a design flaw or driver issue flaws that make it unusable and money not well spent. I can use the extra 100.00 on Ram, CPU or other components. I explained to support the issues I was having and they said they were going to RMA it I asked if they could just RMA it with the cheaper XENO card and support said they could not.I know we paid 200-250.00 for the card and we all want it just to work and they are working on it, so I ask this ; should I buy a xeno card and what mobo should i avoid. (yes I saw a brief list here).I believe killer will get it right and we will all be eating crow in the future. Any advice good or bad is welcome. thank you

02-10-2010, 10:32 AM	#23
Arrakiv Community Manager Killer Performance Join Date: Jul 2009 Location: Austin, Texas Posts: 501	Re: K1/M1 Driver Development Is the card actually dead, or was it an issue with the drivers? If it is the latter, please try out the latest stable build that just came out, and hopefully that will clear up any issues for you. As much as I'd love to tell you to go, run out, and buy a Xeno... I'd be happier seeing your current card working well. :-) __________________ Sean Bulger Community Manager Bigfoot Networks Facebook \| Twitter \| Steam \| Blog

02-10-2010, 02:56 PM	#24
d2thez High Ping Join Date: Jul 2009 Posts: 58	Re: K1/M1 Driver Development So have the "Stable Release" drivers been changed even a little bit from the beta release? The versions numbers are exactly the same which would make me think not.

02-10-2010, 05:52 PM	#25
ironleg High Ping Join Date: Aug 2007 Posts: 62	Re: K1/M1 Driver Development I get a failed pipe error now with the visual basic error at C\... If the card was the issue I wanted to see if they would trade me with a Xeno to see if it would fix the problem.I have tried it with a clean install after writing zeros to a 1 tb drive;(that took some time..) and I have tried different windows 7 x 64 versions. I know the xeno is priced less than what I paid for the killer nic i have. I don't wish to sound cheap but want a resolution to this issue. I still think Bigfoot is the best card and the right software/hardware is just almost there.I told my brothers friend who just opened a computer shop about Bigfoot gaming cards and they never heard of them. I am hoping to get him to include them in his inventory.

02-11-2010, 05:44 PM	#26
Whity High Ping Join Date: Nov 2009 Posts: 59	Re: K1/M1 Driver Development well installed new release of k1 drivers and seems i get firmware ip tables not installed is this normal or what LLR-64 (Version=4.1.0.37) Configuration request KillerNIC K1 LLR Mode is currently set to GAME Mode LLR Version Number = 4.1.0.14 Proxy Version Number = 4.1.0.15 Firmware Version Number = 4.1.0.10 Card SubSystemID = 0x201 (indicates a K1) Number of Raw NIC SGLs = 1 Number of LLR SGLs = 1 Current LLR Ping Control= 0 Current LED CONTROL = Blinking LLR Game Priority = Boosted Boot Partition = Side B Boot Status Value = 0 Boot Running Status = KillerNic Boot Successful Boot Strap Version = 0x000003e8 KillerNIC Secondary IP Address=172.31.254.2 Mask=255.255.255.0 KillerNIC Tx Poll Timer Setting = 1000us KillerNIC Rx Poll Timer Setting = 1000us KillerNIC Firmware IP_TABLES is NOT Loaded KillerNIC K1 FNA support= Enabled LinkSpeed = 100Mps Mode=Full Duplex <==SetUdpConfig Winsock 32-bit Catalog: ======================= 1271 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1272 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1273 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1274 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1112 - MSAFD Pgm (RDM) 1113 - MSAFD Pgm (Stream) 1007 - RSVP TCPv6 Service Provider 1008 - RSVP TCP Service Provider 1009 - RSVP UDPv6 Service Provider 1010 - RSVP UDP Service Provider 1270 - BfLLR Winsock 64-bit Catalog: ======================= 1271 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1272 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1273 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1274 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1112 - MSAFD Pgm (RDM) 1113 - MSAFD Pgm (Stream) 1007 - RSVP TCPv6 Service Provider 1008 - RSVP TCP Service Provider 1009 - RSVP UDPv6 Service Provider 1010 - RSVP UDP Service Provider 1270 - BfLLR Killer Suite Version: 4.1.0.144

02-11-2010, 07:08 PM	#27
Tekgun Lagged Join Date: Feb 2009 Location: England Posts: 15	Re: K1/M1 Driver Development I think that just means your Killer firewall is turned off. Turn it on and the configuration request should show the IP Tables loaded.

02-11-2010, 08:27 PM	#28
d2thez High Ping Join Date: Jul 2009 Posts: 58	Re: K1/M1 Driver Development Ok, installed the final release on my K1 in Win7 x64. The previous release drivers 4.1.0.37 beta worked without fault in everything. I did a total purge of those before installing the new final drivers. Problem is Modern Warfare 2 refuses to connect to IWNET while in Game Mode. It only works in App Compat Mode. That is the only issue I have seen. Unfortunately, this game is huge! ! How can a bug like this make it past testing, especially when it worked fine with the previous driver? This is the game of the moment folks!! I need my UDP offloading!!!!!!!!!! Here is my config: LLR-64 (Version=4.1.0.37) Configuration request KillerNIC K1 LLR Mode is currently set to GAME Mode LLR Version Number = 4.1.0.14 Proxy Version Number = 4.1.0.15 Firmware Version Number = 4.1.0.10 Card SubSystemID = 0x201 (indicates a K1) Number of Raw NIC SGLs = 1 Number of LLR SGLs = 1 Current LLR Ping Control= 0 Current LED CONTROL = Blinking LLR Game Priority = Boosted Boot Partition = Side B Boot Status Value = 0 Boot Running Status = KillerNic Boot Successful Boot Strap Version = 0x000003e8 KillerNIC Secondary IP Address=192.168.254.2 Mask=255.255.0.0 KillerNIC Tx Poll Timer Setting = 1000us KillerNIC Rx Poll Timer Setting = 1000us KillerNIC Firmware IP_TABLES is NOT Loaded KillerNIC K1 FNA support= Enabled LinkSpeed = 100Mps Mode=Full Duplex <==SetUdpConfig Winsock 32-bit Catalog: ======================= 1017 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1018 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1016 - BfLLR Winsock 64-bit Catalog: ======================= 1017 - BfLLR over [MSAFD Tcpip [TCP/IP]] 1018 - BfLLR over [MSAFD Tcpip [UDP/IP]] 1019 - BfLLR over [MSAFD Tcpip [TCP/IPv6]] 1020 - BfLLR over [MSAFD Tcpip [UDP/IPv6]] 1001 - MSAFD Tcpip [TCP/IP] 1002 - MSAFD Tcpip [UDP/IP] 1003 - MSAFD Tcpip [RAW/IP] 1004 - MSAFD Tcpip [TCP/IPv6] 1005 - MSAFD Tcpip [UDP/IPv6] 1006 - MSAFD Tcpip [RAW/IPv6] 1016 - BfLLR Killer Suite Version: 4.1.0.144 Last edited by d2thez; 02-11-2010 at 08:56 PM.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode