Re: A20/keybord/no-keyboard
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 setting the appropriate hint in device.hints or > > >> loader.conf as documented in the sio(4) man page. For instance: > > >> > > >> hint.sio.0.flags="0x30" > > >> > > >> forces sio0 to become the system console regardless of the presence of > > >> a display adapter. > > >> > > >> You may also have to tell the boot code and loader to use the serial > > >> console; see their respective manual pages. > > > > > > 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. > > > > > > i'm using boot0sio, so the boot is also talking via the serial, but > > > the BTX > > > is still using the vga, compiling it to use the serial gave errors. > > > > BTX_SERIAL will not work with boot2 (hard drive boot blocks) due to > > space > > constraints. It does work for /boot/loader and pxeboot however. Note > > that > > it only outputs meaningful text if it crashes anyway, so I wouldn't > > worry > > about it. > > well, the host was not booting ... > > with BTX_SERIAL, btx does not compile, and for 'completness' it would be > nice to have all console output, anyways my problem was not btx related. > > danny Ah, I've fixed the btx compile. Seems some comment rototilling busted it. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.baldwin.cx/~john/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
(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, and complained, but i think that's taken care of. I solved it by adding hint.atkbdc.0.disabled="1". As I wrote before, 'it would be nice', if such fantom devices could be detected at boot time, so the same fs/root/kernel could work on 'similar' platforms out-of-the-box. with the kbd, i found where it was looping, in 'atkbdc.c: empty_both_buffers', but got lost trying to figure out how to get out of it (specialy since there is no kbd/buffer :-). danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
(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: -#ifdef SIO +#if defined(SIO) && COMSPEED != 0 /* * Initialize the serial port. bioscom preserves the driver number in DX. */ movw COMSPEED,%ax # defined by Makefile callw bioscom #endif /* SIO */ since this only works for speeds upto 9600, and breaks things for speeds above 9600. (i know, this probably should be a PR :-) danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
... > > 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. bioscom preserves the driver number in DX. */ movw COMSPEED,%ax # defined by Makefile callw bioscom #endif /* SIO */ since this only works for speeds upto 9600, and breaks things for speeds above 9600. (i know, this probably should be a PR :-) danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
> > 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 page. For instance: > >> > >> hint.sio.0.flags="0x30" > >> > >> forces sio0 to become the system console regardless of the presence of > >> a display adapter. > >> > >> You may also have to tell the boot code and loader to use the serial > >> console; see their respective manual pages. > >> > > > > 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. > > > > i'm using boot0sio, so the boot is also talking via the serial, but > > the BTX > > is still using the vga, compiling it to use the serial gave errors. > > BTX_SERIAL will not work with boot2 (hard drive boot blocks) due to > space > constraints. It does work for /boot/loader and pxeboot however. Note > that > it only outputs meaningful text if it crashes anyway, so I wouldn't > worry > about it. well, the host was not booting ... with BTX_SERIAL, btx does not compile, and for 'completness' it would be nice to have all console output, anyways my problem was not btx related. danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
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 page. For instance: hint.sio.0.flags="0x30" forces sio0 to become the system console regardless of the presence of a display adapter. You may also have to tell the boot code and loader to use the serial console; see their respective manual pages. 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. i'm using boot0sio, so the boot is also talking via the serial, but the BTX is still using the vga, compiling it to use the serial gave errors. BTX_SERIAL will not work with boot2 (hard drive boot blocks) due to space constraints. It does work for /boot/loader and pxeboot however. Note that it only outputs meaningful text if it crashes anyway, so I wouldn't worry about it. -- John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
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_FORCECONSOLE is ignored if COM_CONSOLE isn't set. > i'm using boot0sio, so the boot is also talking via the serial, but > the BTX is still using the vga, compiling it to use the serial gave > errors. There's no need to recompile anything; the third-stage loader will automatically use the serial console if the second-stage loader does (i.e. /boot.config contains -h). The reason why there are two versions of the first-stage loader is that space constraints preclude supporting both VGA and serial in the same code. The second- and third-stage loaders have no such constraints. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
> 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 hint.atkbdc.0.disabled="1". As I wrote before, 'it would be nice', if such fantom devices could be detected at boot time, so the same fs/root/kernel could work on 'similar' platforms out-of-the-box. with the kbd, i found where it was looping, in 'atkbdc.c: empty_both_buffers', but got lost trying to figure out how to get out of it (specialy since there is no kbd/buffer :-). > from an earlier message: > > > btw, this board doesn't have a vga either, and only after i removed > > it from the kernel config did i begin to see some output on the > > serial line. > > 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 page. For instance: > > hint.sio.0.flags="0x30" > > forces sio0 to become the system console regardless of the presence of > a display adapter. > > You may also have to tell the boot code and loader to use the serial > console; see their respective manual pages. > 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. i'm using boot0sio, so the boot is also talking via the serial, but the BTX is still using the vga, compiling it to use the serial gave errors. danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
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 message: > btw, this board doesn't have a vga either, and only after i removed > it from the kernel config did i begin to see some output on the > serial line. 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 page. For instance: hint.sio.0.flags="0x30" forces sio0 to become the system console regardless of the presence of a display adapter. You may also have to tell the boot code and loader to use the serial console; see their respective manual pages. DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
> 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 > dev/kbd/kbd.c optionalsc > dev/kbd/kbd.c optionalukbd > dev/kbd/kbd.c optionalvt > > Do you have any of these in in your kernel: atkbd, kdb, sc, ukbd, vt? > none of the above, but KBD_INSTALL_CDEV, which i don't know - yet - what it affects. btw, can the check for kbd be made aware of 'fantom' cases? i tried to follow the code but got entangled :-) danny > Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
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 dev/kbd/kbd.c optionalsc dev/kbd/kbd.c optionalukbd dev/kbd/kbd.c optionalvt Do you have any of these in in your kernel: atkbd, kdb, sc, ukbd, vt? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
> 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/src/sys/conf/newvers.sh WRAP cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/r+d/5.3/src/sys -I/r+d/5.3/src/sys/contrib/dev/acpica -I/r+d/5.3/src/sys/contrib/altq -I/r+d/5.3/src/sys/contrib/ipfilter -I/r+d/5.3/src/sys/contrib/pf -I/r+d/5.3/sr c/sys/contrib/dev/ath -I/r+d/5.3/src/sys/contrib/dev/ath/freebsd -I/r+d/5.3/src/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8000 --param inline- unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror vers.c linking kernel kbd.o(.text+0x308): In function `kbd_register': : undefined reference to `__start_set_kbddriver_set' kbd.o(.text+0x30e): In function `kbd_register': : undefined reference to `__stop_set_kbddriver_set' kbd.o(.text+0x334): In function `kbd_register': danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: A20/keybord/no-keyboard
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 http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
A20/keybord/no-keyboard
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 with a return ENXIO in atkbd_probe_unit got me going. so, Q1: is it possible to compile a 5.3 kernel without kbd, or, Q2: how can i tell the kernel that this board has not keyboard controller? btw, the SC11000 says it has atkbdc_probe_unit(): atkbdc0: at port 0x64,0x60 on isa0 but will hang in atkbd_probe_unit(). back in the days of the PDP11, Unix V6 would panic on boot if some harware was non-existant/miss-configured, Berkeley fixed this with autoconf, which was just brilliant. Now we have 'fantom' hardware which is, but is not realy there, making things a bit more complicated :-) btw, this board doesn't have a vga either, and only after i removed it from the kernel config did i begin to see some output on the serial line. danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: no keyboard
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, or there is no keyboard and mouse >hooked up, that the keyboard and mouse get "lost". Yes. This is one of the most annoying "features" I have ever seen, and with PC keyboards, I'm not even sure it makes sense - it's not as though there's much need for configuring. >I think the destructive probe is probably an artifact of the >pre-VM86() days, before we could ask the BIOS if there is a >PS/2 mouse port present. That would fit. I once wrote a patch to let you specify in the config file what kind of mouse you use, and if you did this, and the probe failed, it would just assume that's what you meant. I believe it worked fine with my 4-button trackball. I submitted the code and forgot about it; I don't have a copy anymore, and I can't swear it was very well tested. It was well enough tested that I could ignore the switch problem on my FreeBSD box. -s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
Ingo Flaschberger wrote: > > > > > 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 not > > hot-plug compatible > > i have never killed a keyboard with un / plugging. > at linux it works. I've cooked several. It's not nearly as likely these days; in the original AT days, the controller chip was on board the keyboard itself, and inadequately isolated. Using a KVM switch is roughly tantamount to doing the same thing, only without the static issue. 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, 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 from looking at the source to the Windows 98 mouse driver from the DDK CDROM from Microsoft, that the mouse driver periodically resynchronizes "just in case someone uses a KVM switch on me"). It's really, really annoying. At least one company has revised their KVM switch firmware for FreeBSD's peculiar tastes, but you still have to have the KVM switch plugged in at FreeBSD boot time, or it loses its mind. I rather suspect that the mouse issue could be dealt with in moused, with a tiny amount of kernel cooperation. For the keyboard itself, it's really a matter of getting FreeBSD's nose out of the keyboard controller at probe time (I actually think it's the LED code that causes the problem, but that's just my gut feeling on it), and letting the BIOS set it up however it wants it set up, and have FreeBSD adapt to that, instead. I think the destructive probe is probably an artifact of the pre-VM86() days, before we could ask the BIOS if there is a PS/2 mouse port present. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 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 hotswap again. It never disallowed it, it is simply a flag for the atkbd(4) driver. You can always tweak it by turning off flag 0x1 on the atkbd0 device via a custom kernel or using a userconfig script. However, by default keyboards are actually probed and not assumed present on 4.3, so hotplug of a keyboard if the keyboard was not plugged in in 4.3 will not work out of the box. Note that hotplug of USB will work. A real fix would be to have the atkbdc0 driver attach a atkbd0 device in the case that a keyboard interrupt comes in (i.e. on the first keypress after plugging in the keyboard). -- John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
> 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, it works, until your keyboard does actually break :) > > I've toasted lot of keyboards this way (Fujitsu POS no less). I have found > that IBM keyboards take the punishment quite well. At least I can count on > IBM engineering. As a result, that's the only type of kbd we keep in our > datacenters. While IBM keyboards are good (I've hot-plugged and otherwise abused a few in my day), IBM computers have had their share of faulty engineering. A high school I worked at once had quite a problem with some IBM PS/1 desktops, which exhibited the following traits: - hot-plugging a keyboard would either fry the keyboard or damage the MB (still usuable, just no KB support) - hot-plugging a keyboard into the PS/2 mouse port (no thanks to some badly oriented labels) would provide a few sparks, some smoke, and a toasted keyboard and MB. -- Matt Emmerton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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, it works, until your keyboard does actually break :) I've toasted lot of keyboards this way (Fujitsu POS no less). I have found that IBM keyboards take the punishment quite well. At least I can count on IBM engineering. As a result, that's the only type of kbd we keep in our datacenters. -gordon To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 machines... but it has happened more than once.) I'm in the same situation for my rack servers, and I solved using an USB keyboard :-) Enabling USB support in the kernel and in the BIOS of the machine is just what I need. When inserted you have only to do something like kbdcontrol -k /dev/kbd1 < /dev/console operating from a ssh/telnet/etc. session and voila, USB kbd is activated :-) When remove you do the same with /dev/kbd0. Probably if you disable the atkbd in the kernel you don't ever need such kbdcontrol magic. -- bye! Ale [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 then proceeds > to relocate itself across some contacts. Ahh yes... Be very careful plugging in those little PS/2 connectors. That's probably the cause of most burned hot-swapped keyboards. :) If you bend the pins by twisting, then get the wrong pin into the +5 ZZzap.. Later.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 hotswap again. Hehe... I've never burned a MB or keyboard in the > 1000 times I've done it, although I've had to reboot a few because the keyboard controller didn't wake up properly. :) I've had dead-ish keyboards that won't allow a machine to boot if plugged in when booting, but work fine if plugged in afterwards. (I've got a nice rackmount Netframe keyboard/trackball that does this. What a pain. I'd like to be able to use that keyboard!) It could be handy sometimes to have a widget to run that would totally re-initialize the keyboard controller. Most often I'd find this handy to 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 machines... but it has happened more than once.) Besides... It's not as bad as hot-swapping ISA cards. When I first got my Microsoft InPort Bus Mouse (with Windows 286) years and years ago, I used to often move it between my BBS machine and my development machine every few minutes when I was building some of the ANSI screens, etc. Occasionally I had to go to DOS and re-enable the mouse driver, but it actually worked because the card was so simple. :) Not recommended. Yes, I am crazy. Later.. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
* 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 > > > > > 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 :) > > > > It can actually fry the entire motherboard. I doubt linux can > > prevent that. > > > > it would blow the inline fuse before it fries the mother board. 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 then proceeds to relocate itself across some contacts. -- -Alfred Perlstein - [[EMAIL PROTECTED]] Daemon News Magazine in your snail-mail! http://magazine.daemonnews.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 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. > it would blow the inline fuse before it fries the mother board. > FreeBSD 4.3 allows hotswap again. > > -- > -Alfred Perlstein - [[EMAIL PROTECTED]] > http://www.egr.unlv.edu/~slumos/on-netbsd.html > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-hackers" in the body of the message -- Paul Halliday. http://dp.penix.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 that there IS a chance you will toast things. -- Andrew Hesford [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
* 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 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 hotswap again. -- -Alfred Perlstein - [[EMAIL PROTECTED]] http://www.egr.unlv.edu/~slumos/on-netbsd.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 :) -- Ceri Storey <[EMAIL PROTECTED]> http://pkl.net/~cez/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
> > > 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 not > hot-plug compatible i have never killed a keyboard with un / plugging. at linux it works. > > two better solutions : > - a KVM (keyboard video mouse) switch (for example, from Blackbox) cannt do that, to much boxes. > - a serial console (via console="comconsole" in /boot/loader.conf + the we already have serial console at the boxes, but u can't use it if u have no laptop with u. the keyboard an the monitor at the locations are always used at other boxes..( bye, Ingo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 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 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 not hot-plug compatible two better solutions : - a KVM (keyboard video mouse) switch (for example, from Blackbox) - a serial console (via console="comconsole" in /boot/loader.conf + the right conf in /etc/ttys -- Thierry Herbelot To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
> > 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 need access to this boxes (not > > remote access). > > is there a solution for this problem? > > > > See atkbd(4)... (remove 'flags 0x1' from the atkbd0 line) i don't have set the flags 0x1 at the kernel config. at the box the keyboard driver is installed at boot time: snip --- atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 --- snap --- but if i connect a keyboard later to the box, it doesn't work. bye, Ingo To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: no keyboard
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 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 need access to this boxes (not > remote access). > is there a solution for this problem? > See atkbd(4)... (remove 'flags 0x1' from the atkbd0 line) -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
no keyboard
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 recognized. at the colocations we often need access to this boxes (not remote access). is there a solution for this problem? bye, Ingo SILVER SERVER \\ \\ \ [EMAIL PROTECTED] www.sil.at Backbone Team [EMAIL PROTECTED]keep your backbone tidy To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
