DOCBoot doesn't compile

DOCBoot doesn't compile

[Brian O'Dell]

I get the following error when compiling DOCBoot :

doc_bootstub.o(.text+0x131): In function `doc_cmd':
: undefined reference to `BX_CDSN_IO'

I have googled and grepped for BX_CDSN_IO with no results.  Any 
thoughts?  Has anyone successfully compiled the most recent docboot?

Thanks,
Brian

Re: DOCBoot doesn't compile

[Dan Brown]

Brian O'Dell wrote:
> I get the following error when compiling DOCBoot :
> 
> doc_bootstub.o(.text+0x131): In function `doc_cmd':
> : undefined reference to `BX_CDSN_IO'
> 
> I have googled and grepped for BX_CDSN_IO with no results.  Any 
> thoughts?  Has anyone successfully compiled the most recent docboot?

Ack! My fault.  I somehow forgot to check in doc_bootstub.h

Checked in now.  Please let me know if that fixes the problem.  Or if it 
doesn't.

	-Dan

Re: DOCBoot doesn't compile

[Brian O'Dell]

Dan Brown wrote:

> Ack! My fault.  I somehow forgot to check in doc_bootstub.h
>
> Checked in now.  Please let me know if that fixes the problem.  Or if 
> it doesn't.
>
>     -Dan


Thank you for the quick response Dan.  DOCBoot does compile now, but it 
freezes prior to any indication that it is trying to load the kernel.  
Here is what I get with DEBUG_BUILD defined: 

Installing DOCBoot.
doc_seg = 0xE000           setup_seg = 0x2400
int15/e801 returns 0x0F00    initrd_start = 0x0FFF0000
top of low mem = 0x0279k    handler seg = 0x9E00
 -- Press any key --

Prior to pressing any key, numlock and capslock respond normally.  I can 
also reboot via ctrl-alt-del.  I press enter, then the system freezes 
hard.  No numlock or capslock response, ctrl-alt-del does not work.  Any 
thoughts or ideas are much appreciated.

Thanks,
Brian  

Re: DOCBoot doesn't compile

[Dan Brown]

Brian O'Dell wrote:

> Thank you for the quick response Dan.  DOCBoot does compile now, but 
> it freezes prior to any indication that it is trying to load the 
> kernel.  Here is what I get with DEBUG_BUILD defined:
> Installing DOCBoot.
> doc_seg = 0xE000           setup_seg = 0x2400
> int15/e801 returns 0x0F00    initrd_start = 0x0FFF0000
> top of low mem = 0x0279k    handler seg = 0x9E00
> -- Press any key --
>
> Prior to pressing any key, numlock and capslock respond normally.  I 
> can also reboot via ctrl-alt-del.  I press enter, then the system 
> freezes hard.  No numlock or capslock response, ctrl-alt-del does not 
> work.  Any thoughts or ideas are much appreciated.


Hmm.  Well, nothing appears odd in the debug messages.  Your DOC is at 
E000, you have 256Mbytes of RAM, you have 633k free low memory, etc.  
Let me get some more info from you:

- what type/size of DOC you're using
- size of your kernel and initrd
- what options you use when building DOCBoot (which interrupt, for 
instance).
- what other devices are in the system (video, harddrives, etc)

Hopefully you're able to boot your system normally (DOCBoot install will 
be skipped if you hold down shift, alt, or control at the appropriate 
phase of BIOS boot).

    -Dan

Re: DOCBoot doesn't compile

[Brian O'Dell]

Dan Brown wrote:

> Brian O'Dell wrote:
>
>> Thank you for the quick response Dan.  DOCBoot does compile now, but 
>> it freezes prior to any indication that it is trying to load the 
>> kernel.  Here is what I get with DEBUG_BUILD defined:
>> Installing DOCBoot.
>> doc_seg = 0xE000           setup_seg = 0x2400
>> int15/e801 returns 0x0F00    initrd_start = 0x0FFF0000
>> top of low mem = 0x0279k    handler seg = 0x9E00
>> -- Press any key --
>>
>> Prior to pressing any key, numlock and capslock respond normally.  I 
>> can also reboot via ctrl-alt-del.  I press enter, then the system 
>> freezes hard.  No numlock or capslock response, ctrl-alt-del does not 
>> work.  Any thoughts or ideas are much appreciated.
>
>
>
> Hmm.  Well, nothing appears odd in the debug messages.  Your DOC is at 
> E000, you have 256Mbytes of RAM, you have 633k free low memory, etc.  
> Let me get some more info from you:
>
> - what type/size of DOC you're using
> - size of your kernel and initrd
> - what options you use when building DOCBoot (which interrupt, for 
> instance).
> - what other devices are in the system (video, harddrives, etc)
>
> Hopefully you're able to boot your system normally (DOCBoot install 
> will be skipped if you hold down shift, alt, or control at the 
> appropriate phase of BIOS boot).
>
>    -Dan


I'm using a 128M DOC2000, model number:  md2202-D128.  It is one of the 
newer INFTL devices.  The kernel is a hefty 1.9 Megabytes.  I would like 
to use initrd in the future, but for now I am leaving it out.  I haven't 
used any options when compiling.  I left doc_bootstub.h alone, except to 
turn on the debugging messages.   DOC_BIOS_HOOK is defined to 0x18.  
Though in my system it behaves more like the description for Int 19h.   
It completely ignores the hard drive on boot even though it is there.  I 
don't care really, just mentioning it in case some BIOS weirdness could 
be causing the trouble.   The BIOS is from General Software.  The 
mainboard is a SBC from Versalogic, VSBC-8.  It has the BX chipset and a 
ATI Rage Mobility video chip.  I have a ultra ata hard drive also.  I 
can boot fine.  The shift bypass works very well.

Thanks
-Brian

Re: DOCBoot doesn't compile

[Brian O'Dell]

Brian O'Dell wrote:

> Dan Brown wrote:
>
>> Brian O'Dell wrote:
>>
>>> Thank you for the quick response Dan.  DOCBoot does compile now, but 
>>> it freezes prior to any indication that it is trying to load the 
>>> kernel.  Here is what I get with DEBUG_BUILD defined:
>>> Installing DOCBoot.
>>> doc_seg = 0xE000           setup_seg = 0x2400
>>> int15/e801 returns 0x0F00    initrd_start = 0x0FFF0000
>>> top of low mem = 0x0279k    handler seg = 0x9E00
>>> -- Press any key --
>>>
>>> Prior to pressing any key, numlock and capslock respond normally.  I 
>>> can also reboot via ctrl-alt-del.  I press enter, then the system 
>>> freezes hard.  No numlock or capslock response, ctrl-alt-del does 
>>> not work.  Any thoughts or ideas are much appreciated.
>>
>>
>>
>>
>> Hmm.  Well, nothing appears odd in the debug messages.  Your DOC is 
>> at E000, you have 256Mbytes of RAM, you have 633k free low memory, 
>> etc.  Let me get some more info from you:
>>
>> - what type/size of DOC you're using
>> - size of your kernel and initrd
>> - what options you use when building DOCBoot (which interrupt, for 
>> instance).
>> - what other devices are in the system (video, harddrives, etc)
>>
>> Hopefully you're able to boot your system normally (DOCBoot install 
>> will be skipped if you hold down shift, alt, or control at the 
>> appropriate phase of BIOS boot).
>>
>>    -Dan
>
>
>
> I'm using a 128M DOC2000, model number:  md2202-D128.  It is one of 
> the newer INFTL devices.  The kernel is a hefty 1.9 Megabytes.  I 
> would like to use initrd in the future, but for now I am leaving it 
> out.  I haven't used any options when compiling.  I left 
> doc_bootstub.h alone, except to turn on the debugging messages.   
> DOC_BIOS_HOOK is defined to 0x18.  Though in my system it behaves more 
> like the description for Int 19h.   It completely ignores the hard 
> drive on boot even though it is there.  I don't care really, just 
> mentioning it in case some BIOS weirdness could be causing the 
> trouble.   The BIOS is from General Software.  The mainboard is a SBC 
> from Versalogic, VSBC-8.  It has the BX chipset and a ATI Rage 
> Mobility video chip.  I have a ultra ata hard drive also.  I can boot 
> fine.  The shift bypass works very well.
>
> Thanks
> -Brian
>

After reading through the doc_bootstub.S a bit, it looks like my system 
isn't even getting to the interrupt handler.  I've installed to 18h and 
19h.  Both with the same result:  The system locks hard right after it 
exits from the SPL.  Could docboot be clobbering something important 
when it loads the interrupt handler?  I'm assuming that it isn't getting 
to the interrupt handler because I don't get the "Kernel Loading..." 
message.  Is my theory plausible or likely?

-Brian

Re: DOCBoot doesn't compile

[Dan Brown]

Brian O'Dell wrote:
> After reading through the doc_bootstub.S a bit, it looks like my system 
> isn't even getting to the interrupt handler.  I've installed to 18h and 
> 19h.  Both with the same result:  The system locks hard right after it 
> exits from the SPL.  Could docboot be clobbering something important 
> when it loads the interrupt handler?  I'm assuming that it isn't getting 
> to the interrupt handler because I don't get the "Kernel Loading..." 
> message.  Is my theory plausible or likely?

It's been a while since I've actually run DOCBoot (I've been working on 
other stuff), so I just built and installed it on my device from the 
latest CVS as a sanity check.  I get the same hard lockup as you do.

I'll let you know when I've found the problem.  Needless to say, I'm a 
bit embarassed to have checked in code this broken and let it sit that 
way in the repository for several months :(

	-Dan

Re: DOCBoot doesn't compile

[Dan Brown]

Dan Brown wrote:
> It's been a while since I've actually run DOCBoot (I've been working on 
> other stuff), so I just built and installed it on my device from the 
> latest CVS as a sanity check.  I get the same hard lockup as you do.
> 
> I'll let you know when I've found the problem.  Needless to say, I'm a 
> bit embarassed to have checked in code this broken and let it sit that 
> way in the repository for several months :(


OK, I found the issue; I was clobbering a register I shouldn't have.  I 
guess I must have made this change right before I committed the latest 
version and not properly tested it.

I'd appreciate feedback from anyone interested in using DOCBoot... does 
the latest CVS now work for you?

	-Dan

Re: DOCBoot doesn't compile

[Brian O'Dell]

Dan Brown wrote:

> Dan Brown wrote:
>
>> It's been a while since I've actually run DOCBoot (I've been working 
>> on other stuff), so I just built and installed it on my device from 
>> the latest CVS as a sanity check.  I get the same hard lockup as you do.
>>
>> I'll let you know when I've found the problem.  Needless to say, I'm 
>> a bit embarassed to have checked in code this broken and let it sit 
>> that way in the repository for several months :(
>
>
>
> OK, I found the issue; I was clobbering a register I shouldn't have.  
> I guess I must have made this change right before I committed the 
> latest version and not properly tested it.
>
> I'd appreciate feedback from anyone interested in using DOCBoot... 
> does the latest CVS now work for you?
>
>     -Dan
>
>
It works great.  You are my new hero man.  Thank you!  Thanks to dwmw2 
and the entire mtd team for putting all of this together for us to use.  
You guys are doing good work. 

bto