RE: Problems with 4.0 keyboard input!

1999-08-14 Thread Ron Klinkien
Hello Brian, I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is not that good ;) The messages comes from

Re: Problems with 4.0 keyboard input!

1999-08-14 Thread Mike Pritchard
In message 01bee5f0$c467c7c0$0264a8c0@.demon.nl "Ron Klinkien" writes: : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), : the keyboard is acting very strange, i cannot login, : i get only strange characters, and when I hit CTRL I get: : : load: 0.04 cmd:

Re: Problems with 4.0 keyboard input!

1999-08-14 Thread Poul-Henning Kamp
In message 000401bee65b$b6fd0440$0264a8c0@.demon.nl, "Ron Klinkien" writes: I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is

RE: Problems with 4.0 keyboard input!

1999-08-14 Thread Nick Hibma
I have looked in the source code, but what does usurping means? My English is not that good ;) 'opslorpen' in Dutch. Nick -- e-Mail: [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

RE: Problems with 4.0 keyboard input!

1999-08-14 Thread Ron Klinkien
In message 000401bee65b$b6fd0440$0264a8c0@.demon.nl, "Ron Klinkien" writes: I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I have looked in the source code, but what does usurping means? My English is

Re: Problems with 4.0 keyboard input!

1999-08-14 Thread Eric Hodel
Ron Klinkien wrote: Hello, After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), the keyboard is acting very strange, i cannot login, i get only strange characters, and when I hit CTRL I get: load: 0.04 cmd: login242 [ttyin] 0.01u 0.03s 0% 772K load: 0.04 cmd:

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Brian McGroarty
I get the bktr device usurping its own cdevsw[] as well - I was told it was "most likely" benign, so I've been waiting for others' comments. I also get the keyboard problem periodically, and I've been trying to isolate just what I do to cause it. Generally, if I reboot and don't hit a key before

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Warner Losh
In message 01bee5f0$c467c7c0$0264a8c0@.demon.nl "Ron Klinkien" writes: : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), : the keyboard is acting very strange, i cannot login, : i get only strange characters, and when I hit CTRL I get: : : load: 0.04 cmd: login242

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Kazutaka YOKOTA
[...] I also get the keyboard problem periodically, and I've been trying to isolate just what I do to cause it. Generally, if I reboot and don't hit a key before FreeBSD boots, it never happens. If I tap enter to abort the countdown, the keyboard scrambles perhaps one time in five. If you hit

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Mike Smith
In message 01bee5f0$c467c7c0$0264a8c0@.demon.nl "Ron Klinkien" writes: : After building a few succesfull 4.0 releases (last cvsupped on 13 aug 99), : the keyboard is acting very strange, i cannot login, : i get only strange characters, and when I hit CTRL I get: : : load: 0.04 cmd:

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Warner Losh
In message [EMAIL PROTECTED] Mike Smith writes: : It's not the boot blocks doing anything explicit; they just use the BIOS. I have noticed that boot[12] doesn't seem to have this problem. However, after /boot/loader has been loaded, I see this problem from time to time. I don't know what is

Re: Problems with 4.0 keyboard input!

1999-08-13 Thread Mike Smith
In message [EMAIL PROTECTED] Mike Smith writes: : It's not the boot blocks doing anything explicit; they just use the BIOS. I have noticed that boot[12] doesn't seem to have this problem. However, after /boot/loader has been loaded, I see this problem from time to time. I don't know what