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
hi,
this board (WRAP) has no keyboard, and there is a fix in boot1.S
to take into account such case, but i can't compile a -current a kernel
without kbd (4.x is ok without kbd*), i solved the problem
with a quick hack, just to see if im on the correct track, and a return
wi
In message <[EMAIL PROTECTED]>, Terry Lambert writes:
>FreeBSD has an extremely annnoying habit of taking a keyboard
>that has been successfully configured by the BIOS, and then
>reconfiguring it "destructively" during probe, such that, if
>there is no KVM hooked up,
by the BIOS, and then
reconfiguring it "destructively" during probe, such that, if
there is no KVM hooked up, or there is no keyboard and mouse
hooked up, that the keyboard and mouse get "lost".
Linux doesn't have this problem, and neither does Windows (I
believe f
On 05-May-01 Alfred Perlstein wrote:
> * Ceri Storey <[EMAIL PROTECTED]> [010505 11:59] wrote:
>> On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
>> > > Note : this is a way to kill your keyboard : an AT keyboard is not
>> > > hot-plug compatible
>> >
>> > i have never killed
> On Sat, 5 May 2001, Ceri Storey wrote:
>
> > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > > > Note : this is a way to kill your keyboard : an AT keyboard is not
> > > > hot-plug compatible
> > >
> > > i have never killed a keyboard with un / plugging.
> > > at linux it
On Sat, 5 May 2001, Ceri Storey wrote:
> On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > > Note : this is a way to kill your keyboard : an AT keyboard is not
> > > hot-plug compatible
> >
> > i have never killed a keyboard with un / plugging.
> > at linux it works.
> Well,
On Sat, May 05, 2001 at 06:08:05PM -0600, Doug Russell wrote:
> re-enable a PS/2 mouse after inadvertantly disconnecting it. I hate to
> reboot server machines that have been up for hundreds of days because I
> can't use the KB or mouse. (Not that I often use a KB or mouse on any
> server machi
On Sat, 5 May 2001, Alfred Perlstein wrote:
> Anything is possible, and I have heard of it happening at least
> once. One of the other fun things about hot swapping keyboards
> is that you can actually damage the connector which can cause a
> short on the motherboard if the poor thing detaches
On Sat, 5 May 2001, Alfred Perlstein wrote:
> > > i have never killed a keyboard with un / plugging.
> > > at linux it works.
> > Well, it works, until your keyboard does actually break :)
>
> It can actually fry the entire motherboard. I doubt linux can
> prevent that.
>
> FreeBSD 4.3 allows
* Paul Halliday <[EMAIL PROTECTED]> [010505 13:41] wrote:
> Alfred Perlstein wrote:
> >
> > * Ceri Storey <[EMAIL PROTECTED]> [010505 11:59] wrote:
> > > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > > > > Note : this is a way to kill your keyboard : an AT keyboard is not
Alfred Perlstein wrote:
>
> * Ceri Storey <[EMAIL PROTECTED]> [010505 11:59] wrote:
> > On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > > > Note : this is a way to kill your keyboard : an AT keyboard is not
> > > > hot-plug compatible
> > >
> > > i have never killed a keybo
On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> i have never killed a keyboard with un / plugging.
> at linux it works.
Of course it works with linux. It has nothing to do with the operating
system. I hotswap my stuff keyboard and mouse all the time; you just
have to remember
* Ceri Storey <[EMAIL PROTECTED]> [010505 11:59] wrote:
> On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > > Note : this is a way to kill your keyboard : an AT keyboard is not
> > > hot-plug compatible
> >
> > i have never killed a keyboard with un / plugging.
> > at linux i
On Sat, May 05, 2001 at 08:54:18PM +0200, Ingo Flaschberger wrote:
> > Note : this is a way to kill your keyboard : an AT keyboard is not
> > hot-plug compatible
>
> i have never killed a keyboard with un / plugging.
> at linux it works.
Well, it works, until your keyboard does actually break :)
> > > the problem is, when i connect after the boot a keyboard at the box, it is
> > > not recognized. at the colocations we often need access to this boxes (not
> > > remote access).
> > > is there a solution for this problem?
>
> Note : this is a way to kill your keyboard : an AT keyboard is n
Chris Faulhaber wrote:
>
> On Sat, May 05, 2001 at 07:36:07PM +0200, Ingo Flaschberger wrote:
> > Hi
> >
> > i'm not sure if that is the right list, but i hope u could help me.
> >
> > i'm working at an iap, and we are using freebsd (4.2) boxes as r
> > i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
> > normally no keyboard or monitor is attached to the box.
> > the problem is, when i connect after the boot a keyboard at the box, it is
> > not recognized. at the colocations we often n
On Sat, May 05, 2001 at 07:36:07PM +0200, Ingo Flaschberger wrote:
> Hi
>
> i'm not sure if that is the right list, but i hope u could help me.
>
> i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
> normally no keyboard or monitor is attached
Hi
i'm not sure if that is the right list, but i hope u could help me.
i'm working at an iap, and we are using freebsd (4.2) boxes as routers.
normally no keyboard or monitor is attached to the box.
the problem is, when i connect after the boot a keyboard at the box, it is
not reco
32 matches
Mail list logo
