On Wednesday 24 November 2004 09:29 am, Danny Braniss wrote:
> > On Nov 24, 2004, at 2:47 AM, Danny Braniss wrote:
> > >> If the VGA driver is present, the system will assume you want to use a
> > >> VGA console, unless you force one of the serial ports to become the
> > >> system console by settin
(sorry if this a resend, it seems there was a problem at hub.freebsd.org)
> The console driver (sc) currently requires you to have at least one
> keyboard driver compiled in. Since your board doesn't have a display
> adapter, you can simply remove 'device sc'.
>
the kbd.c was getting compiled in
(if this is a repeat, then sorry, there seems to be a problem at
hub.freebsd.org)
...
>
> Ah, I've fixed the btx compile. Seems some comment rototilling busted it.
that's what i saw.
btw, while we are at the bottom of the bleading edge, can this also be fixed:
in i386/boot/boot0/boot0.S:
-#ifd
...
>
> Ah, I've fixed the btx compile. Seems some comment rototilling busted it.
that's what i saw.
btw, while we are at the bottom of the bleading edge, can this also be fixed:
in i386/boot/boot0/boot0.S:
-#ifdef SIO
+#if defined(SIO) && COMSPEED != 0
/*
* Initialize the serial port. biosco
>
> On Nov 24, 2004, at 2:47 AM, Danny Braniss wrote:
>
> >> If the VGA driver is present, the system will assume you want to use a
> >> VGA console, unless you force one of the serial ports to become the
> >> system console by setting the appropriate hint in device.hints or
> >> loader.conf as d
On Nov 24, 2004, at 2:47 AM, Danny Braniss wrote:
If the VGA driver is present, the system will assume you want to use a
VGA console, unless you force one of the serial ports to become the
system console by setting the appropriate hint in device.hints or
loader.conf as documented in the sio(4) man
Danny Braniss <[EMAIL PROTECTED]> writes:
> im using hint.sio.0.flags="0x20", and still, only after i removed
> the vga from the config file did i get the console output on the
> serial line.
0x20 (COM_FORCECONSOLE) isn't enough, you have to use 0x30
(COM_FORCECONSOLE | COM_CONSOLE). COM_FORCECON
> The console driver (sc) currently requires you to have at least one
> keyboard driver compiled in. Since your board doesn't have a display
> adapter, you can simply remove 'device sc'.
>
the kbd.c was getting compiled in, and complained, but i think that's
taken care of.
I solved it by adding
Danny Braniss <[EMAIL PROTECTED]> writes:
> this is waht i get if i remove atkbd and atkbdc:
> ...
The console driver (sc) currently requires you to have at least one
keyboard driver compiled in. Since your board doesn't have a display
adapter, you can simply remove 'device sc'.
from an earlier
> In message: <[EMAIL PROTECTED]>
> Danny Braniss <[EMAIL PROTECTED]> writes:
> : kbd.o(.text+0x30e): In function `kbd_register':
> : : undefined reference to `__stop_set_kbddriver_set'
>
> dev/kbd/kbd.c optionalatkbd
> dev/kbd/kbd.c optional
In message: <[EMAIL PROTECTED]>
Danny Braniss <[EMAIL PROTECTED]> writes:
: kbd.o(.text+0x30e): In function `kbd_register':
: : undefined reference to `__stop_set_kbddriver_set'
dev/kbd/kbd.c optionalatkbd
dev/kbd/kbd.c optionalkbd
de
> In message: <[EMAIL PROTECTED]>
> Danny Braniss <[EMAIL PROTECTED]> writes:
> : so, Q1: is it possible to compile a 5.3 kernel without kbd,
>
> Doesn't removing atkbd and atkbdc from the kernel do the job?
>
this is waht i get if i remove atkbd and atkbdc:
...
MAKE=make sh /r+d/5.3/
In message: <[EMAIL PROTECTED]>
Danny Braniss <[EMAIL PROTECTED]> writes:
: so, Q1: is it possible to compile a 5.3 kernel without kbd,
Doesn't removing atkbd and atkbdc from the kernel do the job?
Warner
___
[EMAIL PROTECTED] mailing list
h
13 matches
Mail list logo
