On Sun, 30 Jul 2000, Kenneth Wayne Culver wrote:
> My problems are with a previous build of late last week. And my problem
> isn't with X. My problem only happens when you start "tail" on some file,
> then try to exit. It locks the console solid... neither the mouse nor the
> keyboard work.
Sorr
To resolve the problem with tail, rebuild your kernel with revision 1.11 of
sys/kern/kern_event.c. 1.12 which was designed to make the kevent system
restartable seems to keep the process from ever receiving the interrupt. I
don't have a solution which solves both problems yet.
Jim Bloom
[EMAIL
My problems are with a previous build of late last week. And my problem
isn't with X. My problem only happens when you start "tail" on some file,
then try to exit. It locks the console solid... neither the mouse nor the
keyboard work.
=
(Originally didnt response back to mailing list...)
The keyboard works fine when I dont start X, single user mode
or just at the console. I can crash the machine whenever I switch
virtual consoles which is most not fun. Not sure if its
strictly an X problem on not.
My previous -current was bef
On Sun, 30 Jul 2000 [EMAIL PROTECTED] wrote:
> The problem I am seeing is that the keyboard isnt even seen.
> Its useable up until about midway through the boot process,
> then it goes dead/locks up. The boot continues fine and the machine
> is up. The mouse is usable in X but not the keyboard.
Hrmm, that's even worse than my problem.
=
| Kenneth Culver | FreeBSD: The best NT upgrade|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: muythaibxr
The problem I am seeing is that the keyboard isnt even seen.
Its useable up until about midway through the boot process,
then it goes dead/locks up. The boot continues fine and the machine
is up. The mouse is usable in X but not the keyboard. Cant even switch
virtual consoles.
steve
> I have
I have, like when I'm running tail on something, and then I try to ctrl-c
out of it, the whole console locks solid, and I have to reboot. (although
if I was connected to an ethernet, I think I could probably ssh in and
reboot.) Also, as an unrelated problem in -CURRENT, I'm experiencing the
lockmg
Hi,
I updated my source tree yesterday (and kernel) and am having some problems
with my keyboard under X. Has anyone else noticed anything
strange.
steve
--
Steve Heistand
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the
