Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 13 Apr 2002 14:53:25 -0700
From:      "Drew Tomlinson" <drew@mykitchentable.net>
To:        "Matthew Emmerton" <matt@gsicomp.on.ca>, <questions@FreeBSD.ORG>
Subject:   Re: Boot Help - I've Gotten Myself Into Quite A Mess!
Message-ID:  <014601c1e335$a3484980$0301a8c0@bigdaddy>
References:  <00ca01c1e32f$213034e0$0301a8c0@bigdaddy> <001e01c1e331$d90d1360$1200a8c0@gsicomp.on.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
----- Original Message -----
From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: "Drew Tomlinson" <drew@mykitchentable.net>;
<questions@FreeBSD.ORG>
Sent: Saturday, April 13, 2002 2:26 PM
Subject: Re: Boot Help - I've Gotten Myself Into Quite A Mess!


Thank you for your reply.

> > I was recently given an old Pentium 133 and motherboard so I
decided
> > to replace my 486.  I shutdown, opened the case, replaced the
> > motherboard, and tried to reboot.  Well, DUH!  My kernel is
compiled
> > for a 486 and thus it panics because it finds the Pentium.  See
below:
>
> Heh.  I won't say how many times that's happened to me.
>
> > ok LOAD KERNEL.GENERIC
> > can't find 'KERNEL.GENERIC'
> >
> > Is the problem because everything is in all caps?  I have pressed
the
> > caps lock key but it makes no difference.  It's in all caps all
the
> > time.
>
> I think the boot loader will accept commands in both upper and lower
case,
> but filenames are case sensitive.
>
> Before giving you a workaround, have you tried using a different
keyboard?
> The only time I've seen a keyboard get stuck in all-caps is when
it's on its
> last legs.

I have things set to use COM1 for the console.  I have COM1 connected
to COM2 on another FBSD box and am accessing the console via tip.  Now
this used to work just fine with the 486 motherboard and the machine
booted.  I'm not sure if I ever had to do anything at the command
prompt before boot with the 486.  But in any event, I don't have a
keyboard problem.

> In the meantime, what you can do to get this thing to boot is use
the
> backdoor method of generating ASCII characters from your keyboard.
What you
> do is hold down ALT, and then punch in 0 and then the 3-digit
(decimal)
> ASCII code of your lowercase letters -- using the numeric keypad.
(It won't
> work with numbers along the top of the keyboard.)
>
> So in your case, type LOAD <space> ALT-0107 ALT-0101 ALT-0114
ALT-0110
> ALT-0101 ALT-0108 <dot> GENERIC <enter>  You should see "LOAD
> kernel.GENERIC" on your screen, and the loader should be able to
find it and
> boot from it.

OK, now it get's weird.  I tried this just as you described and the
characters are still displayed in CAPS.  So I suspect that it has
something to do with using the serial console via tip on another FBSD
machine.  Then add to it that I'm accessing that machine via SecureCRT
on a Windows 2000 platform.  I think I need to get things back to
"plain vanilla" and start from there.

So, any advice on how to get my console to display on a monitor?  I
attached a monitor and keyboard.  Once the boot loader takes over,
nothing more is displayed on the monitor.

Thanks for your help!

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?014601c1e335$a3484980$0301a8c0>