Dietmar

@reboot12 works, nice, just installs devices, USB works on the Biostar z690A Valkyrie Dietmar PS: But result is the same. I cant install any driver because of "The parameter is not correct" So, no unsigned driver possible via 9560.inf . Tomorrow I make a try to add them by hand to registry and to system32\drivers .

@reboot12 Today I am too tired, because with the 9560 driver I work until 5 in this morning. I make a try with the Fat32 USB stick and your nice XP SP2 bit 64 and then I go to bed Dietmar

@reboot12 Can I use Firadisk or only real CD Dietmar

@reboot12 It is an *.iso. How to install it, via Rufus or real CD Dietmar

@reboot12 Can you send me the link to your XP SP2 bit 64 +.iso with key? And do you have different USB drivers for it? Still I think, that there is a switch in politicies or something like this, for to enable to install own drivers. But on the other hand I know, that nlite can destroy an original CD Dietmar

@reboot12 This is install via an original Corporate XP SP2 bit64 CD. Nothing modded. Oh no, I use one time nlite for the Kai Sata driver. This is very much important, because I notice, that when 1 Bit is wrong, the Intel firmware 77 will fall 100.000 packets later Dietmar

@reboot12 Vermutlich hat das was mit signierten Treibern oder irgendwelchen Policities zu tun. Auf jeden Fall kann ich keinen einzigen selbstgebauten Treiber unter XP SP2 bit64 installieren und das liegt nicht am Treiber Dietmar

@reboot12 What the hell is wrong in this??? XP bit64 Parameter wrong ??? https://www.upload.ee/files/19338992/139x64.zip.html

@reboot12 Something is wrong with all the drivers for XP bit 64. I am just looking, what it is Dietmar

@reboot12 It seems, as ChatGPT translates C-Code wrong from XP SP3 ==> XP SP2 bit 64. Already the driver entry is a mismatch, and so even no entry in registry or the driver itself in System32\drivers Dietmar

@reboot12 I set up Windbg session on the Biostar board with XP SP2 bit64. But I cant install the Wlan 9560 driver, get message „The parameter is incorrect“ brrr.. I like XP SP3 Dietmar

@reboot12 No, you get endless waiting at Setup, because Bsod of USB on the Biostar board. I wrote somewhere about this Bsod C0000004 (as I remember) Dietmar

@reboot12 On the Biostar z690A Valkyrie most USB driver do not work. So I use serial Bus mouse. But now install is ready, crazy journey through Bsods.. Because still no USB, I put all needed files on the harddisk, which I can easy change Dietmar

@reboot12 I just fight with install of XP SP2 bit 64 on the Biostar board. Bsod everywhere, no USB install, but I will succeed Dietmar

@reboot12 do you have the antenna connected? Because I remember Code 10 without antenna at the 9560 Wlan Dietmar

@reboot12 I am just installing XP SP2 bit 64. On first place is diagnosis. Via Putty I make a complete scan (trace) of all the register, variables, adresses etc. on the Biostar board and on the N100 for OpenBSD vers. 79 for to understand, how the 9560 is initialized in bit 64 and started Dietmar

@reboot12 Yes, to enlarge firmware loading timeout is a nice idea. I just build new driver. Then I think, which board would be the best for me for testing. On the Asrock N100DC-ITX and Biostar z690A Valyrie the 9560 Wlan driver works for XP SP3. But for crazy debug sessions the Wyse 5070 does not work until now, because missing Lan-Windbg from @Mov AX, 0xDEAD . So I need to think. Maybe, I install XP bit 64 on the Biostar board first Dietmar EDIT: Please send me the whole Debug log, because at other places I can see also, what is going on. 9560m139_x64_bootwait.zip https://www.upload.ee/files/19338020/9560m139_x64_bootwait.zip.html

@reboot12 The driver comes very near to work. The Firmware 77 does not boot on the Dell Wyse 5070. This you can see at alive=0 . For me, this was the biggest hurdle in the beginning. I think, the only chance is, that I install XP bit 64 also on my 5070. But I make a try: This new driver sets IRQ, MSI-X and Poll for alive Dietmar https://www.upload.ee/files/19337772/9560m138_x64_alive_poll.zip.html

@reboot12 Here it is 9560m137_x64_startdiag driver for XP SP3 and XP bit64 , good luck Dietmar https://www.upload.ee/files/19337542/9560m137_x64_startdiag.zip.html

@reboot12 1. Get DebugView Important: Do NOT use the current DebugView 5.x if it does not run on Windows XP x64. For Windows XP x64, use an older Sysinternals DebugView 4.x version, preferably 4.81 or 4.90. Microsoft Sysinternals DebugView page: https://learn.microsoft.com/sysinternals/downloads/debugview If the Microsoft download only provides the newer 5.x version, search for an older Sysinternals release. Suggested search terms: DebugView 4.81 Sysinternals DebugView 4.90 Sysinternals DbgView.exe 4.81 DbgView.exe 4.90 After extraction, the executable will usually be named: Dbgview.exe or, if included: Dbgview64.exe On Windows XP x64, first try Dbgview.exe. If it does not start and Dbgview64.exe is present, try Dbgview64.exe. 2. Prepare the Dell Wyse 5070 with Windows XP x64 Create these folders: C:\DBGVIEW C:\9560LOG Copy DebugView into: C:\DBGVIEW Install the diagnostic x64 driver package: 9560m137_x64_startdiag Important: Do not use the nodebug version for this test. We need DbgPrint output from the driver. If possible, do not enable the Intel 9560 device in Device Manager before DebugView is already running. 3. Start DebugView Start DebugView as Administrator: For this you need your password from installation of XP. I installed XP SP3 without password, and crazy DebugView does not work. C:\DBGVIEW\Dbgview.exe If it does not start and Dbgview64.exe is available, try: C:\DBGVIEW\Dbgview64.exe 4. Enable DebugView capture options In DebugView, open the menu: Capture Enable these options: Capture Win32 Capture Kernel Enable Verbose Kernel Output Optional but useful: Options -> Clock Time Options -> Show Milliseconds Then clear the current output: Edit -> Clear Display DebugView should now be empty and waiting for new output. 5. Set the filter Open: Edit -> Filter/Highlight Use this Include filter first: 9560 If too little is captured, use: 9560;NDIS;Miniport;Wifi Leave the Exclude field empty. Press OK. 6. Enable logging to file Open: File -> Log to File Use this filename: C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG If DebugView asks whether to append or overwrite, choose Overwrite. 7. Reproduce the Code 10 problem Open Device Manager: devmgmt.msc Then use one of these methods: Method A: Right-click the Intel 9560 device. Choose Disable. Then right-click it again. Choose Enable. Method B: Right-click the Intel 9560 device. Choose Update Driver. Choose manual installation. Choose Have Disk. Select the 9560.inf from the m137_x64_startdiag package. Method C: If the device already shows Code 10: Uninstall the device. Then choose Scan for hardware changes. Install the driver again using the 9560.inf file. Keep DebugView open during the whole process. 8. Important lines in the DebugView log We need the startup sequence of the 9560 driver. Look for lines like: 9560nn56: NdisMInitializeScatterGatherDma 9560nn56: query resources pass0 9560nn56: query resources pass1 9560nn56: resources count 9560nn56: resource[0] 9560nn56: resource[1] 9560nn56: resource[2] 9560nn56: mapped resources mmio 9560nn56: NdisMRegisterInterrupt 9560nn56: embedded fw hdr ver 9560nn56: alive wait end 9560nn56: bootstrap status 9560m8c: WifiInitialize success If Code 10 appears, the last 9560 line before the failure is usually the most important one. 9. Save the log After Code 10 appears: File -> Save As Save as: C:\9560LOG\DBGVIEW_9560_X64_CODE10_FINAL.LOG Also keep this file if Log to File was enabled: C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG 10. What to send back Please zip and send to me these files: C:\9560LOG\DBGVIEW_9560_X64_CODE10.LOG C:\9560LOG\DBGVIEW_9560_X64_CODE10_FINAL.LOG 11. If DebugView shows nothing Try these steps: A: Run DebugView as Administrator. B: Disable and re-enable: Capture -> Capture Kernel C: Make sure this is enabled: Capture -> Enable Verbose Kernel Output D: Remove the filter completely. Leave the Include field empty. E: Start DebugView before installing or enabling the driver. F: Try a different DebugView 4.x version. For example: try 4.81 instead of 4.90, or 4.90 instead of 4.81. G: If there is still no output, we need a special 9560 x64 diagnostic build that writes the init status into the registry instead of using DbgPrint. 12. How to interpret the result If the log stops around: query resources mapped resources Possible cause: PCI / UEFI / ACPI resource problem, BAR/MMIO mapping problem. If it stops around: NdisMRegisterInterrupt Possible cause: IRQ / INTx / UEFI / ACPI interrupt routing problem. If it reaches: embedded fw hdr The driver reached firmware loading. If it shows: alive wait end alive=0 Possible cause: Firmware did not start, awake/reset/boot/power problem. If it shows: bootstrap status alive=1 Firmware started successfully; the failure is later in the init path. If it shows: WifiInitialize success The driver initialization itself succeeded. Then Code 10 is probably caused by a later NDIS status, wrong return value, binding issue, or another post-init failure.

@reboot12 Code 10 means, that this driver is acceptet but just can not start. With Windbg it would be easy to solve. So, from my side, next step would be to bring the @Mov AX, 0xDEAD Lan-Windbg to XP bit 64 Dietmar

@reboot12 I have the same Dell Wyse 5070 as you, same Wlan 9560, same cpu, same M.2 Sata, same ram and same cpu. But I have no idea, how to install XP 64 there Dietmar

@reboot12 Here is the 9560 Wlan driver for XP SP3 and XP bit 64. Free and Checked version each and Source Code. I notice crazy things: The most most stable run of this driver is on an original XP SP3 from 2008, 4GB. I got millions of packages without crash, MyPal 13.7 via DSL Speed test. 64 bit XP I have not tested. Tomorrow I make a try to compile the 77 firmware for to understand it much better. NO(!!!) 32 GB or something else, those "patches" make whole XP SP3 instable. Until now no WPA2 only unencrypted, open Wlan, Channel 6 at 2.4 GHZ Good luck, Dietmar https://www.upload.ee/files/19336803/9560m136_m120_nodebug_x64.zip.html

@reboot12 I was one step away from to give up with the Wlan 9560 driver. I use old firmware, which is not supported officially for this card. To come to live for this card is from Ubuntu, Scan is from OpenBSD, the RX Ring is first part from OpenBSD and updated with a nice idea from Ubuntu, wifi path is from XP SP1. But the most most crazy things were 1,) The CNVi firmware always kills my card with power switch off between 11.000 and 700.000 packages. For to overcome this I modd my Bios like crazy, to really force any power on. Later I come to the idea, to look, how OpenBSD and Ubuntu solve this. Win10, win11 have problems with this too, but I succeed with a simple OpenBSD hack. 2.) The CNVi firmware looks for MSI-X. This is something, that XP does not like. Crazy, this I noticed only today. So I rewrite my driver from IRQ ==> Polling just now. And voila, see this result, It is much better than my lan result via DSL Speedtest from Computerbild and any Wlan card that I know Dietmar PS: The 9560 card I tested on the Asrock N100DC-ITX and just now on the Biostar z690A Valkyrie.

@reboot12 I am writing this to you from the 9560 Wlan driver on XP SP3, niccceeeeeee Dietmar PS: About 500h work and I build about 2000 not working drivers..