Re: LX Graphics: FATAL ERROR - InitDetectCPU Failed



I mean: init_detect_cpu function check for specific PCI devices to be sure
that it's running on a Geode LX.
If this function fails you have the 'LX Graphics: FATAL ERROR -
InitDetectCPU Failed' message and
the driver executes a 'hlt' instruction to halt the system

--

Luca Calligaris
l.calligaris.nospam@xxxxxxxxxxxxxxxxxx
www.eurotech.it

"Luca Calligaris" <l.calligaris.nospam@xxxxxxxxxxxxxxxxxx> ha scritto nel
messaggio news:ebXh161OJHA.1368@xxxxxxxxxxxxxxxxxxxxxxx
Which vendor /device ID does init_detect_cpu function find?

--

Luca Calligaris
l.calligaris.nospam@xxxxxxxxxxxxxxxxxx
www.eurotech.it

"dadalan" <u47302@uwe> ha scritto nel messaggio news:8c79cbc6c095a@xxxxxx
who can tell me how to solve this problem,it si make me crazy.

Debug Serial Init

SysInit: GDTBase=8103d0e8 IDTBase=8105e860 KData=81065800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:23:42
g_pPageDir = 81066000
RTC - Status Reg B - 0x02
X86Init done, OEMAddressTable = 80224ff8.
OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35
OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52
OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62
AES_AES_Init: context Drivers\Active\09
AES_AES_Init: returning 0x00000001
DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at
(Drivers\BuiltIn\AFD). Driver cannot be unloaded.

DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at
(Drivers\BuiltIn\PPP). Driver cannot be unloaded.

PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1 failed
LX Graphics: FATAL ERROR - InitDetectCPU Failed => Cpu: 0 Chipset:
0

Exception 00d Thread=83e63cf0 Proc=43e5d892 'gwes.exe'
AKY=00000009 PC=03083c0b(ddi_agx.dll+0x00003c0b) ESP=080af440 EA=00000000
Exception 00e Thread=83e63cf0 Proc=43e5d892 'gwes.exe'
AKY=00000009 PC=0003cda0(gwes.exe+0x0002cda0) ESP=080afb64 EA=00000008

--
Message posted via PocketPCJunkies.com
http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200810/1





.



Relevant Pages

  • Re: RTL 8139
    ... a KITL-over-Ethernet connection to your Platform Builder machine? ... driver; that won't work because you'll have both the kernel and the driver ... DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions ... Networking - Networking features - NDIS &Networking ...
    (microsoft.public.windowsce.platbuilder)
  • Re: RTL 8139
    ... no instrument no spam DOT com> wrote: ... driver; that won't work because you'll have both the kernel and the ... DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions ... Networking - Networking features - NDIS &Networking ...
    (microsoft.public.windowsce.platbuilder)
  • Re: "No .rel file found for module "
    ... Driver cannot be ... address in use by KITL. ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... required entry points for a stream interface driver. ... with KITL enabled, it loads. ... DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... KITL says that they are exported, but I double checked and they are ... remove the driver from the _FLATRELEASEDIR before ... "Dean Ramsier" wrote: ...
    (microsoft.public.windowsce.app.development)