Dietmar

@reboot12 Can you give me the drivers and also the XP SP3 bit 32 version for eMMC boot? I still work on the 9560 for the gemini chipset here with j4105 but until now no success to overcome RX only 2 packages Dietmar

@reboot12 Here is first try of translating the Source Code for ME from OpenBSD 79 to XP Dietmar 1. Früher poll184_14-Startpfad bleibt erhalten -> kein poll184_19-Code-10-APM-Ersatz 2. OpenBSD-POLLING-WIDX-Logik: nach jedem Poll: widx = (closed == 0 ? Wifi_MAX_RX - 1 : closed - 1) & ~7 RFH_Q0_FRBDCB_WIDX_TRG wird auch bei count == 0 geschrieben 3. OpenBSD-artiger late nic_lock: MAC_ACCESS_REQ setzen auf MAC_ACCESS_EN warten GOING_TO_SLEEP prüfen 4. OpenBSD-artiger late ME/Wake/Ownership-Touch: HAP_WAKE WAKE_ME WAKE_ME_PCIE_OWNER_EN PCI_OWN_SET OS_ALIVE INIT_DONE RFKILL_WAKE_L1A_EN L1A_NO_L0S_RX HPET 0xffff0000 Link Power Management disabled 5. 0x3b wird nicht gefälscht closed bleibt echt nur RFH/MAC/ME wird wie OpenBSD nachgetriggert

@reboot12 I found this link https://codebrowser.dev/linux/linux/drivers/net/wireless/intel/iwlwifi/mei/main.c.html What it means is very easy. ME kills the 9560 on the gemini chip platform, so for our j4105. And on the Asrock j4105-ITX I cant disable ME, the name in Bios for ME there is TXE but when I disable it, the Wlan 9560 is gone. I can see ME at work: The 2 RX packages I read above are data for arp and DHCP. After this, crazy ME brings the firmware to write 3b, so the RX ring is blocked. I also found in the original OpenBSD 79 Source Code, which I modd for POLLING for the 9560, has an own C-block, how to handle this ME. So, fun is not over but I have to build this all with the help of ChatGPT, like translation from OpenBSD C-Code to XPC-Code. Then, XP is "allowed" under ME. I also tried a dirty hack, just to jump over this 3b code. But then the 9560 driver does not install any longer Dietmar 1. iwm_nic_lock() MAC_ACCESS_REQ setzen auf MAC_ACCESS_EN warten GOING_TO_SLEEP beachten 2. iwm_apm_init() HAP_WAKE_L1A setzen INIT_DONE setzen MAC_CLOCK_READY warten DMA clock / L1_ACT_DIS setzen 3. iwm_prepare_card_hw() HW_IF_CONFIG PREPARE / NIC_READY / ME_OWN / WAKE_ME prüfen 4. iwm_nic_rx_mq_init() RFH_RXF_DMA_CFG RFH_GEN_CFG DMA_SNOOP RFH_RXF_RXQ_ACTIVE WIDX_TRG 5. iwm_power_update_device() POWER_TABLE_CMD 6. iwm_power_mac_update_mode() MAC_PM_POWER_TABLE 7. iwm_ltr_config() LTR_CONFIG

@reboot12 I need to make some more tests. Until now only 2 RX packages, because I force one ring for this. But because it is a pure POLLING driver and DHCP works already, I think already today I send to you Dietmar

Yessssssssssssaaaaaaaaaaaaaahhhh after about next 500h of work and about 1000 not working drivers, I get the driver for the Wlan 9560 on the gemini chipset with j4105 cpu to run. It is a pure polling driver, based on OpenBSD 79. The step for to bring the firmware to alive=1 I managed only with Ubuntu. Crazy, 10 different rings for TX and RX and management data. Again I was one step away from to give up Dietmar

@UsefulAGKHelper No, he disappeared suddently in November 2024, dont know why Dietmar

@reboot12 For a try it may work. The problem in this is, that the way, the Bios treated DSDT is not static. Suddently you will get Bsod. This makes me like crazy, until @Mov AX, 0xDEAD tells me, that this was the exact reason why he build his DSDT patcher at boottime Dietmar

@reboot12 For one of my AMD boards I bought a changeable case on motherboard for the Bios chip. The original chip I solder out and can put it in and out of this case as often as I want, like in former times. After this, I can modd DSDT for this board while during flashing whole bios also in minutes Dietmar

@reboot12 Yes, I did this with success with the DSDT Patcher at boot time from @Mov AX, 0xDEAD . This is a really nice tool and with it I change DSDT a lot of times in minutes. But only for XP bit 32 I think. asl does not work, because it patches only the static DSDT in registry and gives Bsod on reboot. You can ask @Damnation he succeed with grub4dos I think, but dont know if this also works with XP bit 64 Dietmar

@reboot12 This is the problem from those acpi.sys hacks. So, this way does not work until now. I remember from past, that this happens, when an acpi.sys hack also destroyed necessary answers to other devices. This takes a long run with Windbg and Ida Pro to fix this Dietmar

@reboot12

@reboot12 May be, that from other place also a jump goes direct to this bsod A5 0x02 This will with this acpi13.sys not happen any longer Dietmar https://www.upload.ee/files/19415611/acpi13.sys.html

@reboot12 Here is acpi12.sys good luck Dietmar https://www.upload.ee/files/19415565/acpi12.sys.html

@reboot12 I just notice, that there are at least 5 places for this Bsod A5 0x02, so here is acpi11.sys Dietmar https://www.upload.ee/files/19415521/acpi11.sys.html

@reboot12 Here is acpi10.sys for this Bsod, hihi Dietmar https://www.upload.ee/files/19415497/acpi10.sys.html