Uploaded image for project: 'Core ReactOS'
  1. Core ReactOS
  2. CORE-20267

MSI PC60G PCI WiFi adapter fails to find external firmware.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • Networking

    Description

      I'm testing the following build of ReactOS on real hardware.

      https://iso.reactos.org/bootcd/reactos-bootcd-0.4.16-dev-1475-g410db43-x86-gcc-lin-dbg.7z

      with a MSI PC60G Wireless 11g Turbo G PCI Adapter and the following windows xp driver:

      https://web.archive.org/web/20130131052144if_/http://download2.msi.com/files/downloads/dvr_exe/RT61V1.2.8.0.zip

      It gives the following error and locks up when installing the driver:

      (sdk/lib/rtl/heap.c:2323) HEAP: Trying to free an invalid address 0022E710!
      (ntoskrnl/mm/ARM3/sysldr.c:170) Loading: \SystemRoot\System32\drivers\RT61.sys at F65C1000 with 7b pages
      (ntoskrnl/mm/ARM3/sysldr.c:2592) ImageBase 0xF65C1000 ImageSize 0x7a180 Section 6 VA 0x78400 Raw 0x1d80 virt 0x1d46
      (ntoskrnl/io/pnpmgr/pnpres.c:648) Resource conflict: IRQ (0x5 0x5 vs. 0x5 0x5)
      (ntoskrnl/io/pnpmgr/pnpres.c:648) Resource conflict: IRQ (0x5 0x5 vs. 0x5 0x5)
      (/srv/buildbot/worker_data/Build_GCCLin_x86/build/drivers/network/ndis/ndis/misc.c:291)(NdisOpenFile) ZwCreateFile failed (c0000034) Name rt2561s.bin
      NDIS_STATUS_MEDIA_DISCONNECT
      (ntoskrnl/kdbg/kdb_symbols.c:231) Trying \SystemRoot\System32\drivers\RT61.sys
      NDIS_STATUS_MEDIA_DISCONNECT 

      the strange thing about this is the driver contains a internal Wifi firmware. I know this because A. the driver works on windows XP with the driver listed here and it does not contain a external firmware to load.

      B. I searched for the the drivers on the chip-set manufacturer site and it has a firmware for this chip-set so i searched for the firmware header and found it in the driver:

      https://web.archive.org/web/20070124180604if_/http://www.ralinktech.com:80/ralink/data/RT61_Firmware_V1.2.zip

      using this firmware or extracting the embedded firmware will let ReactOS run a bit longer but eventually will lockup.

      Substituting windows 2003 ndis.sys will allow the driver to start without ReactOS locking up but can't be fully tested due to unimplemented functions in ntoskrnl.

      Attachments

        Activity

          People

            Unassigned Unassigned
            Zombiedeth Zombiedeth
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: