On 11/4/07, Greg Thomas <[EMAIL PROTECTED]> wrote: > > On 11/4/07, Nick Holland <[EMAIL PROTECTED]> wrote: > > Greg Thomas wrote: > > > On 11/4/07, James <[EMAIL PROTECTED]> wrote: > > >> boot> > > >> booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70 > > >> entry point at 0x200120 > > >> > > >> > > >> booting hd0a:/bsd: 5665588+872060 [52+291168+272312]=0x6c5c70 > > >> entry point at 0x200120* > > >> > > >> > > >> Here's where I get slammed as the n00b I am. > > >> > > >> It looks to me like they're looking at two different but related > memory > > >> locations. Look at the entry points "0x200120" vs "0x200120*" > > >> > > >> Someone who understands what's going on better can comment on what > this > > >> means, but I'm almost willing to be there's a file somewhere you need > to > > >> recompile so it's looking at the correct location. > > >> > > > > > > Yep, so far the only thing I've thought to do is re-install the > > > bootblocks which I already did. > > > > > > I just can't figure out why there's a difference between letting it > > > boot automatically or interrupting the boot process to do the boot > > > hda0:/bsd. > > > > yeah, that is quite a puzzler. Along with why the contents of the > > panic come out on the CRT when you apparently have a serial console... > > > > I'm really grasping at straws here...but what's in your /etc/boot.conf? > > (and are you SURE?) > > What happens if you just delete(/rename/hide) it? > > > > I originally had "set tty com0" in it but renamed it to boot.conf.bak > since I didn't have my serial cable handy. > > > what happens if you just "boot" instead of "boot hd0a:/bsd"? > > > > Well, this thing is very flaky. It panicked using both "boot" and > "boot hd0a:/bsd" now. > > > ALSO...does anything different happen between a cold power-off/power-on > > and a reboot? > > Same behavior. > > This isn't the first time that I've had strange boot problems with > cheap PCs. I had a Pentium 133 at one time that I discussed with you > where OpenBSD wouldn't boot unless "boot" was in boot.conf, nor could > I interrupt the boot process with F8 and the like in Windows. My > workaround on that box was to put a simple "boot" in boot.conf. So... > > ...I did the same on this box and it boots with no problems. I'll > have to keep an alternative boot method, CD, whatever, in case I need > stop the boot process. > > Greg
What does appending boot do that isn't otherwise done? Inquiring minds must know...
