Back to Website

ReactOS on eBox and embedded systems

Ask your support questions in here

Moderator: Moderator Team

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Tue Sep 27, 2011 2:59 am

Thanks for all of the suggestions. I'm just a beginner at this but at least I seem to be slowly making some progress with the good help. :)

I keep trying several things over and over...

I again tried booting the 53799 debug live cd with everything configured the same as when the release live cd works. Now I got a good capture of the log (more complete than what I posted on 23-Sep thinking I had a serial problem):
Code: Select all
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\serial.sys at F99FE000 with 12 pages
(ntoskrnl/io/pnpmgr/pnproot.c:1137) IRP_MJ_PNP / Unknown minor function 0x14
(ntoskrnl/io/pnpmgr/pnpmgr.c:3666) IRP_MN_QUERY_PNP_DEVICE_STATE failed with status 0xc00000bb
(base/services/umpnpmgr/umpnpmgr.c:2965) Device arrival: Root\*PNP0501\0001
(base/services/umpnpmgr/umpnpmgr.c:2733) Success? 1
(base/services/umpnpmgr/umpnpmgr.c:2627) Installing: Root\*PNP0501\0002
WARNING:  RtlSetUnhandledExceptionFilter at lib/rtl/exception.c:186 is UNIMPLEMENTED!
(lib/rtl/path.c:923) don't keep the directory handle open on removable media
(dll/ntdll/ldr/ldrutils.c:1138) LDR: LdrpMapDll Relocating Image Name gdi32.dll (77FF0000 -> 00730000)
(dll/ntdll/ldr/ldrutils.c:1177) Overlapping DLL: C:\reactos\system32\dnsapi.dll
(ntoskrnl/ps/query.c:1268) Unsupported or unimplemented: 22
fixme:(dll/win32/shell32/shellpath.cpp:1052) (32,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 0
fixme:(dll/win32/shell32/shellpath.cpp:1052) (34,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 1
fixme:(dll/win32/shell32/shellpath.cpp:1052) (33,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 2
err:(dll/win32/setupapi/queue.c:1659) copy error 5 L"C:\\reactos\\inf\\serial.sys" -> L"C:\\reactos\\system32\\drivers\\serial.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 2 L"C:\\reactos\\inf\\serial.sys" -> L"C:\\reactos\\system32\\drivers\\serial.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 5 L"C:\\reactos\\inf\\serenum.sys" -> L"C:\\reactos\\system32\\drivers\\serenum.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 2 L"C:\\reactos\\inf\\serenum.sys" -> L"C:\\reactos\\system32\\drivers\\serenum.sys"
(ntoskrnl/io/pnpmgr/pnpres.c:416) Resource conflict: IRQ (0x4 0x4 vs. 0x4 0x4)
(ntoskrnl/io/pnpmgr/pnpres.c:903) Using conflicting boot resources because no requirements were supplied!
(hal/halx86/legacy/bus/sysbus.c:160) Vector 34 is ALREADY IN USE!
(hal/halx86/legacy/bussupp.c:1433) Returning IRQL 17, Vector 0 for Level/Vector: 4/4
(hal/halx86/legacy/bussupp.c:1436) Old HAL would've returned IRQL 17 and Vector 34
(ntoskrnl/io/pnpmgr/pnpres.c:800) Failed to translate interrupt resource (Vector: 0x4 | Level: 0x4)
(ntoskrnl/io/pnpmgr/pnpres.c:931) Failed to translate resources for Root\*PNP0501\0002
(base/services/umpnpmgr/umpnpmgr.c:2733) Success? 1
(base/services/umpnpmgr/umpnpmgr.c:2627) Installing: Root\*PNP0501\0003
WARNING:  RtlSetUnhandledExceptionFilter at lib/rtl/exception.c:186 is UNIMPLEMENTED!
(lib/rtl/path.c:923) don't keep the directory handle open on removable media
(dll/ntdll/ldr/ldrutils.c:1138) LDR: LdrpMapDll Relocating Image Name gdi32.dll (77FF0000 -> 00730000)
(dll/ntdll/ldr/ldrutils.c:1177) Overlapping DLL: C:\reactos\system32\dnsapi.dll
(ntoskrnl/ps/query.c:1268) Unsupported or unimplemented: 22
fixme:(dll/win32/shell32/shellpath.cpp:1052) (32,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 0
fixme:(dll/win32/shell32/shellpath.cpp:1052) (34,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 1
fixme:(dll/win32/shell32/shellpath.cpp:1052) (33,L""), LoadString failed, missing translation?
err:(dll/win32/wininet/urlcache.c:549) Couldn't get path for default container 2
err:(dll/win32/setupapi/queue.c:1659) copy error 5 L"C:\\reactos\\inf\\serial.sys" -> L"C:\\reactos\\system32\\drivers\\serial.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 2 L"C:\\reactos\\inf\\serial.sys" -> L"C:\\reactos\\system32\\drivers\\serial.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 5 L"C:\\reactos\\inf\\serenum.sys" -> L"C:\\reactos\\system32\\drivers\\serenum.sys"
err:(dll/win32/setupapi/queue.c:1659) copy error 2 L"C:\\reactos\\inf\\serenum.sys" -> L"C:\\reactos\\system32\\drivers\\serenum.sys"
Assertion 'Dispatch.Interrupt->Mode != Latched' failed at ntoskrnl/ke/i386/irqobj.c line 456
Entered debugger on embedded INT3 at 0x0008:0x80903c4e.
kdb:

I'll file a bug report with this info. It would seem good to get the debug live cd working under the same conditions where the release live cd works. Then the next step might be to use the debug live cd to figure out why things break when I change the cd from being the IDE master to the slave?
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am


Postby hto » Tue Sep 27, 2011 9:33 am

Assertion 'Dispatch.Interrupt->Mode != Latched' failed at ntoskrnl/ke/i386/irqobj.c line 456
Entered debugger on embedded INT3 at 0x0008:0x80903c4e.
kdb:

Can you obtain a backtrace (type bt and «Enter ↵»)?
hto
Developer
 
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Tue Sep 27, 2011 5:01 pm

I tried to get a backtrace but it didn't seem to work. I'll try again and let you know the result.
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Tue Sep 27, 2011 11:40 pm

Got a debug log with a backtrace and added it to the bug listing. Please let me know what else I can do to help.
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Fri Sep 30, 2011 6:40 am

Thanks! Now I'm able to boot the live cd dbg r53891 when the cd drive is master. If I try to run the boot cd dbg with the same setup it fails with a prompt that says no HD is present (but it is there as the slave device).

I tried the r53891 boot cd dbg with the HD as master and the CD as slave but that stops. I've added the debug log here: bug 6413.
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Postby SomeGuy » Fri Sep 30, 2011 2:42 pm

Try copying in the UniATA file from a build prior to 51735 and/or one of the older versions from here: http://alter.org.ua/en/soft/win/uni_ata/ and see if that makes a difference.
SomeGuy
 
Posts: 586
Joined: Mon Nov 29, 2004 9:48 am
Location: Marietta, GA

Re: ReactOS on eBox and embedded systems

Postby Haos » Fri Sep 30, 2011 3:07 pm

Try setting up hdd as master and cd as slave.
Haos
Test Team
 
Posts: 2954
Joined: Thu Mar 22, 2007 5:42 am

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Fri Sep 30, 2011 9:11 pm

Try copying in the UniATA file from a build prior to 51735 and/or one of the older versions from here: http://alter.org.ua/en/soft/win/uni_ata/ and see if that makes a difference.


Yes, using the older UniATA I was able to get the r53891 build cd to install onto my CF HD. Now I'm able to boot from the CF (HD) and get further. No problem reading the registry as when I tried installing via VMware.

It now loads drivers (on the blue ReactOS screen) with AFD.sys being the last one. Then it pauses for several seconds on that screen. Then the screen goes black and the last two lines of this debug log are written.
Code: Select all
(ntoskrnl/kd/kdio.c:321) -----------------------------------------------------
(ntoskrnl/kd/kdio.c:322) ReactOS 0.4-SVN (Build 20110929-r53891)
(ntoskrnl/kd/kdio.c:324) 1 System Processor [0 MB Memory]
(ntoskrnl/kd/kdio.c:325) Command Line: /DEBUG /DEBUGPORT=COM1 /BAUDRATE=115200 /SOS /KDSERIAL
(ntoskrnl/kd/kdio.c:329) ARC Paths: multi(0)disk(0)rdisk(0)partition(1) \ multi(0)disk(0)rdisk(0)partition(1) \ReactOS\
(ntoskrnl/ke/i386/cpu.c:251) Vortex86 SoC CPU support not fully tested!
(ntoskrnl/ke/i386/cpu.c:494) Supported CPU features :  KF_RDTSC      KF_CMPXCHG8B  KF_WORKING_PTE           
(ntoskrnl/ke/i386/cpu.c:251) Vortex86 SoC CPU support not fully tested!
(ntoskrnl/ke/i386/cpu.c:801) Prefetch Cache: 32 bytes   L2 Cache: 0 bytes   L2 Cache Line: 64 bytes   L2 Cache Associativity: 0
(ntoskrnl/ke/i386/cpu.c:1088) No support for SYSENTER detected.
(ntoskrnl/mm/mminit.c:243)           0x80000000 - 0x80C00000   Boot Loaded Image
(ntoskrnl/mm/mminit.c:247)           0xB0000000 - 0xB0181000   PFN Database
(ntoskrnl/mm/mminit.c:251)           0xB0181000 - 0xB0949000   ARM³ Non Paged Pool
(ntoskrnl/mm/mminit.c:255)           0xBC000000 - 0xBD000000   System View Space
(ntoskrnl/mm/mminit.c:259)           0xBD000000 - 0xC0000000   Session Space
(ntoskrnl/mm/mminit.c:262)           0xC0000000 - 0xC0300000   Page Tables
(ntoskrnl/mm/mminit.c:265)           0xC0300000 - 0xC0400000   Page Directories
(ntoskrnl/mm/mminit.c:268)           0xC0400000 - 0xC0800000   Hyperspace
(ntoskrnl/mm/mminit.c:272)           0xE1000000 - 0xED400000   ARM³ Paged Pool
(ntoskrnl/mm/mminit.c:275)           0xF4C00000 - 0xFA305000   System PTE Space
(ntoskrnl/mm/mminit.c:278)           0xFA305000 - 0xFFBE0000   Non Paged Pool Expansion PTE Space
(hal/halx86/legacy/bussupp.c:620) Found parent bus (indicating PCI Bridge). PCI devices may fail!

====== PCI BUS HARDWARE DETECTION =======

00:00.0 Host bridge [0600]: RDC Semiconductor, Inc. R6021 Host Bridge [17f3:6021] (rev 01)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 0

00:03.0  [0300]: XGI Technology Inc. (eXtreme Gra Z7/Z9 (XG20 core) [18ca:0020] (rev 00)
   Subsystem: Unknown [18ca:0020]
   Flags: 66MHz, medium devsel, latency 0
   Memory at f8000000 (32-bit, prefetchable) [size=128M]
   Memory at fefc0000 (32-bit, non-prefetchable) [size=256K]
   I/O ports at df80 [size=128]

00:07.0 ISA bridge [0601]: RDC Semiconductor, Inc. R6031 ISA Bridge [17f3:6031] (rev 01)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, latency 0

00:08.0 Ethernet controller [0200]: RDC Semiconductor, Inc. R6040 MAC Controller [17f3:6040] (rev 00)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 128, IRQ 09
   I/O ports at de00 [size=512]
   Memory at fefbb400 (32-bit, non-prefetchable) [size=1K]
   Device is using IRQ 9! ISA Cards using that IRQ may fail!

00:0a.0 USB Controller [0c03]: RDC Semiconductor, Inc. R6060 USB 1.1 Controller [17f3:6060] (rev 11)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 128, IRQ 06
   Memory at 000e2000 (32-bit, non-prefetchable) [size=8K]
   Device is using IRQ 6! ISA Cards using that IRQ may fail!
   Device is an OHCI (USB) PCI Expansion Card. Turn off Legacy USB in your BIOS!

00:0a.1 USB Controller [0c03]: RDC Semiconductor, Inc. R6061 USB 2.0 Controller [17f3:6061] (rev 02)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 128, IRQ 05
   Memory at 000e3000 (32-bit, non-prefetchable) [size=4K]
   Device is using IRQ 5! ISA Cards using that IRQ may fail!

00:0b.0 USB Controller [0c03]: RDC Semiconductor, Inc. R6060 USB 1.1 Controller [17f3:6060] (rev 11)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 128, IRQ 15
   Memory at 000e0000 (32-bit, non-prefetchable) [size=128K]
   Device is using IRQ 15! ISA Cards using that IRQ may fail!
   Device is an OHCI (USB) PCI Expansion Card. Turn off Legacy USB in your BIOS!

00:0b.1 USB Controller [0c03]: RDC Semiconductor, Inc. R6061 USB 2.0 Controller [17f3:6061] (rev 02)
   Subsystem: GLoria L [0000:0000]
   Flags: bus master, medium devsel, latency 128, IRQ 09
   Memory at 000e1000 (32-bit, non-prefetchable) [size=4K]
   Device is using IRQ 9! ISA Cards using that IRQ may fail!

00:0c.0 Mass storage controller [0180]: RDC Semiconductor, Inc. R1010 IDE Controller [17f3:1010] (rev 13)
   Subsystem: Unknown [17f3:1010]
   Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 14
   I/O ports at 01f0 [size=16]
   I/O ports at 03f4 [size=4]
   I/O ports at 0170 [size=16]
   I/O ports at 0374 [size=4]
   I/O ports at fff0 [size=16]
   Device is using IRQ 14! ISA Cards using that IRQ may fail!

====== PCI BUS DETECTION COMPLETE =======

PC Compatible Eisa/Isa HAL Detected
(ntoskrnl/io/pnpmgr/pnpmgr.c:2822) Firmware mapper is enabled
(ntoskrnl/io/pnpmgr/pnpreport.c:346) Reported device: DETECTEDInternal\PCI_HAL (Root\PCI_HAL\0)
(ntoskrnl/io/iomgr/iorsrce.c:882) IoReportResourceUsage is halfplemented!
(ntoskrnl/io/iomgr/driver.c:1557) '\Driver\BUSLOGIC' initialization failed, status (0xc00000c0)
(ntoskrnl/io/iomgr/iorsrce.c:725) Failed opening given symbolic link!
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\floppy.sys at FA137000 with 19 pages
(ntoskrnl/io/iomgr/driver.c:1557) '\Driver\FLOPPY' initialization failed, status (0xc000000e)
(ntoskrnl/mm/ARM3/sysldr.c:929) Leaking driver: floppy.sys
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\cdrom.sys at FA118000 with 1b pages
(ntoskrnl/io/iomgr/driver.c:1557) '\Driver\CDROM' initialization failed, status (0xc000000e)
(ntoskrnl/mm/ARM3/sysldr.c:929) Leaking driver: cdrom.sys
(ntoskrnl/mm/ARM3/sysldr.c:405) class2.sys <class2.sys>
(ntoskrnl/mm/ARM3/sysldr.c:405) multi(0)disk(0)rdisk(0)partition(1)\ReactOS\system32\drivers\scsiport.sys <scsiport.sys>
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\fs_rec.sys at FA10C000 with c pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\null.sys at FA104000 with 8 pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\beep.sys at FA0FB000 with 9 pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\mouclass.sys at FA0E7000 with 14 pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\kbdclass.sys at FA0D3000 with 14 pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\blue.sys at FA0C8000 with b pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\vbemp.sys at FA0BC000 with c pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\videoprt.sys at FA09E000 with 1e pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\npfs.sys at FA08A000 with 14 pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\msfs.sys at FA080000 with a pages
(ntoskrnl/mm/ARM3/sysldr.c:168) Loading: \SystemRoot\system32\drivers\afd.sys at FA056000 with 2a pages
(ntoskrnl/io/iomgr/file.c:421) Using IopParseDevice() hack. Requested invalid attributes: 1
(ntoskrnl/ex/init.c:1930) Free non-cache pages: e8d5
WARNING:  RtlSetUnhandledExceptionFilter at lib/rtl/exception.c:186 is UNIMPLEMENTED!
(ntoskrnl/ps/query.c:1268) Unsupported or unimplemented: 22
WARNING:  RtlSetUnhandledExceptionFilter at lib/rtl/exception.c:186 is UNIMPLEMENTED!
(ntoskrnl/ps/query.c:1268) Unsupported or unimplemented: 22

(ntoskrnl/ex/init.c:1972) Free non-cache pages: e8a5
(ntoskrnl/mm/ARM3/zeropage.c:40) Free non-cache pages: e8a5

I don't see any crash error in that log. What can I try next? At least now I'm able to edit and change some files on the CF if that is needed.

I did try changing the UniATA driver on the CF back to the r53891 version but that didn't make any difference (since now I'm booting from the CF which is the master drive).
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Postby hto » Sat Oct 01, 2011 6:49 pm

I don't see any crash error in that log. What can I try next? At least now I'm able to edit and change some files on the CF if that is needed.

Can you build reactos from sources? If not, maybe I will compile more ‘noisy’ kernel.
hto
Developer
 
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Sun Oct 02, 2011 12:57 am

Can you build reactos from sources? If not, maybe I will compile more ‘noisy’ kernel.


I'd like to be able to do that but I'm not there yet. So if you could compile a kernel with more logging that would be very helpful.
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Postby Lone_Rifle » Mon Oct 03, 2011 10:27 am

Could you describe the eBox-3300MX variant you're using? If you're looking to get a sample of other models http://www.robosavvy.com might be able to help you. I'm particularly keen on the eBox-3310MX that they have in stock, since it uses a Vortex86MX+ , which has twice the performance thanks to improvements in the memory controller and branch predictor. Amount of RAM supported has also gone up to 1GB.
Lone_Rifle
Test Team
 
Posts: 802
Joined: Thu Apr 03, 2008 2:17 pm

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Mon Oct 03, 2011 2:46 pm

I'm presently using this ISA card for my tests (VDX-6324D 800MHz):
http://www.icop.com.tw/pddetail.aspx?id=117&pid=4

That is just a DX version and that is what I'd prefer to get working with ReactOS. If all I need is a console program with one or two serial ports my goal is to use the DX versions of the eBox or the least expensive board I can find.

I'm aware of the MX and I anticipate using it as well but in many control projects the extra power isn't needed.
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Postby hto » Mon Oct 03, 2011 11:29 pm

Ok, it's here. It generates a lot of output, so do not paste logs on the forum. :)
hto
Developer
 
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Re: ReactOS on eBox and embedded systems

Postby pbreneman » Tue Oct 04, 2011 1:12 am

Here is the long debug log:
http://www.turbocontrol.com/CAP50.zip
pbreneman
 
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

PreviousNext

Return to Support

Who is online

Users browsing this forum: No registered users and 4 guests