6.3-STABLE: keyboard not recognized

2008-02-13 Thread Dmitry Karasik
Receiver, rev 1.10/38.10, addr 3, iclass 3/1 kbd3 at ukbd1 ums2: Logitech USB Receiver, rev 1.10/38.10, addr 3, iclass 3/1 ums2: 8 buttons and Z dir. The first keyboard is still not recognized; but by the time xorg is loaded it is, without any extra kernel messages. -- Sincerely, Dmitry Karasik

Re: No kernel messages displayed during boot

2007-11-19 Thread Dmitry Karasik
Jeremy On Sun, Nov 18, 2007 at 08:01:59PM +0100, Dmitry Karasik wrote: I've re-run 'make installworld' and 'make installkernel' (as I had leftovers from recent buildworld), - didn't help. I've tried to power down the machine (suspecied video card trouble), I've resetted BIOS, I've even

Re: No kernel messages displayed during boot

2007-11-19 Thread Dmitry Karasik
and 'make delete-old-libs' deleted nothing. And the behavior didn't change . Did you notice, btw, what libs your 'make delete-old-libs' did remove? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org

Re: No kernel messages displayed during boot

2007-11-19 Thread Dmitry Karasik
:) -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

No kernel messages displayed during boot

2007-11-18 Thread Dmitry Karasik
messages from kernel (I'd recompile it for that purpose) to identify which device it picked up for console IO -- and especially, how I print that either to a file, or directly to /dev/console? -- Sincerely, Dmitry Karasik ___ freebsd-stable

Re: ath0 weak connectivity

2006-09-24 Thread Dmitry Karasik
... Also, I tried another channel, switching to channel 13 - did not help at all. Sam freebsd does not support XR mode. Are there plans for implementing XR mode for ath? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing

Re: ath0 weak connectivity

2006-09-23 Thread Dmitry Karasik
hw.ath.hal.swba_backoff: 0 Output after wlandebug +debug scan is too large to be quoted on the list, so please take a look here: http://www.karasik.eu.org/misc/ath0.html , probably you can find anything suspicious? -- Sincerely, Dmitry Karasik

ath0 weak connectivity

2006-09-18 Thread Dmitry Karasik
. Anything else I can try? -- Sincerely, Dmitry Karasik ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

USB camera problems

2002-12-28 Thread Dmitry Karasik
Hello, I've problems with accessing a camera via USB. I'm not aware if the problem is fixed in 4.7 or 5.0, the machine is better not be upgraded anyway, so I'm looking for a patch and/or an advice. Below is debug printouts. Thanks, Dmitry -

Re: pcm0 problems on 4.7

2002-12-23 Thread Dmitry Karasik
Hi Ulrich! On 18 Dec 02 at 17:40, Ulrich (Ulrich Spoerlein) wrote: Ulrich like: cat kernel /dev/dsp0 and cat kernel /dev/dsp1 Ulrich - use 'mixer' to change the volume levels to 100% - try to free up Ulrich some IRQs man! :) Whatever was the trouble, it was gone after I changed the

perl paths corrupted

2002-02-05 Thread Dmitry Karasik
After cvsupping from 4.3-STABLE to 4.5-STABLE, successfull make buildworld, installworld, etc etc, the following glitch with perl installaltion paths was found: $ perl -Mstrict -e 1 Can't locate strict.pm in @INC (@INC contains: /usr/local/lib/perl5/5.00503/i386-freebsd

sysinstall compile fails

2001-11-26 Thread Dmitry Karasik
What can possibly be done to resolve this ( except for 'make installworld' ) ? root@plab release/sysinstall# make ... cc -O -pipe -Wall -I/usr/src/release/sysinstall/../../gnu/lib/libdialog -I/usr/src/release/sysinstall -c keymap.c In file included from keymap.c:40: keymap.h:6084:

Help needed - can't kill a process

2000-12-29 Thread Dmitry Karasik
Hi! There's a process, that is unkillable by 'kill -9'. Could live with that unless it wouldn't block /dev/cuaa1. Any ideas? ps says: 72234 p4- IE 0:00.01 cu -s 9600 -l /dev/cuaa1 uname says: FreeBSD 4.1-STABLE #0 Or, maybe there's a way to reset the com port device? -- Sincerely,