6.3-STABLE: keyboard not recognized
Hello, I have a strange problem with a PS/2 keyboard attached through USB adapter to USB port (machine doesn't have PS/2 ports). The keyboard behaves fine during POST and first boot stages (I'm not sure if that's the first stage, but I'm referring to the stage where I can select single-user mode). Then, after kernel is loaded, and enters single-user mode, and further on, if proceeded to multi-user mode, the keyboard input is not recognized. Strangely enough, when I load Xorg (I do that manually, not as a tty), the keyboard is recognized again, also in consoles. If I detach and attach the keyboard when it's input is not recognized, it finally gets recognized after several detach-attach cycles; on each, I get kernel messages about USB device being attached and detached. I would like to ask for advice, - if there's anything I can try? I can't grok the kernel sources related to the cause (I tried), so I need help about what else can I try - enable debug, put some hacks in kernel to see what's going on etc. Thank you! Here's exceprt from dmesg: FreeBSD 6.3-STABLE #0: Mon Jan 28 11:34:18 CET 2008 kbd1 at kbdmux0 uhci0: port 0xff20-0xff3f irq 16 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff00-0xff1f irq 17 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xdfdfbc00-0xdfdfbfff irq 22 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] usb2: waiting for BIOS to give up control usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered uhci2: port 0xff80-0xff9f irq 23 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] usb3: on uhci2 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered uhci3: port 0xff60-0xff7f irq 17 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] usb4: on uhci3 usb4: USB revision 1.0 uhub4: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub4: 2 ports with 2 removable, self powered uhci4: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] usb5: on uhci4 usb5: USB revision 1.0 uhub5: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub5: 2 ports with 2 removable, self powered ehci1: mem 0xff980800-0xff980bff irq 23 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub6: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub6: 6 ports with 6 removable, self powered ukbd0: vendor 0x0d3d USBPS2, rev 1.10/0.01, addr 2, iclass 3/1 kbd2 at ukbd0 ums1: vendor 0x0d3d USBPS2, rev 1.10/0.01, addr 2, iclass 3/1 ums1: 5 buttons and Z dir. usb1: host controller halted usb0: host controller halted And by this time the system is booted, but the keyboard is not recognized. So I take another wireless USB keyboard and plug it in, to login: uhub7: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.01, addr 2 uhub7: multiple transaction translators uhub7: 4 ports with 4 removable, self powered ukbd1: Logitech USB 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No kernel messages displayed during boot
Jeremy> Hmm, it looks as if the system doesn't have any indication of what Jeremy> the local console is. I would expect to see a "consolectl" listed Jeremy> under the "Configured:" section. See below for some of the output Jeremy> from our systems... Hi Jeremy, Thanks for your advice, I've started to dig deeper and deeper until I found that it was boot0 loader's fault. Strange as it sounds, it is the only plausible explanation I can think of, because of the all strange effects I've encountered. First, the problem went away when I've replaced /boot/loader with a freshly compiled one. But the interesting part was, that the change to the new loader caused a prompt for the location of /boot/loader on the next reboot (note, no -a in loader.conf!). Next reboots went just fine. The interesting stuff began when I reverted the loader back, and it worked - but again, first time it prompted the input, and worked afterwards. This pattern with flipping old and new loaders back and forth actually was reproducible, and most fun of it all, also under qemu, which I used to save time and used the same /dev/ad4 my system lives on, but in read-only mode. The fact that that action chain actually presisted between reboots in qemu on a read-only device -- I don't know, I simply have no explanation to this. As a last resort, I've re-run boot0cfg -B , and voila, everything started worked fine, and the loader prompt effect disappeared. I'm thinking that something corrupted my MBR in such a nasty way that some boot0's memory, possibly boot flags word (-a, -D etc boot_ flags found in loader.conf) , thought of having been initialized to zero, was not. I tried to look at the source of boot0, but couldn't figure out first if that's an issue here at all, and second, if that behavior would be desirable (after all, the code must be 512 bytes max). Nevertheless, that effect was really spooky - imagine a stray bit in MBR turns off whole console logging! And at last - the machine crashed when I tried to write on msdosfs mounted on /dev/md0. Apparently it wrote something it shouldn't in the MBR. And I tried to write on msdosfs while trying to figure out if my old msdosfs kernel PR #47628 is still actual under 6.2. If anyone's willing to try that, (the PR has perl script attached, http://www.freebsd.org/cgi/query-pr.cgi?pr=47628), you're very welcome. Just back up your MBR first :) -- 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]"
Re: No kernel messages displayed during boot
Hi AngryWolf! AngryWolf> Hi, I had the exact same problem after I upgraded to 7.0-BETA2, AngryWolf> and the problem seemed to be that I forgot to `make delete-old' AngryWolf> and `make delete-old-libs'. Thanks, I've run these, 'make delete-old' deleted some insignificant man pages 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/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: No kernel messages displayed during boot
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 disabled com port in BIOS (because the behavior looks like
>> booting on serial console) -- nothing, absolutely nothing changes it.
Jeremy> conscontrol(8) might help here ("conscontrol list"). Also worth
Jeremy> looking at is sysctl kern.console.
Hello Jeremy,
Thanks, at least this is a hint. That shows on my system:
$ conscontrol list
Configured:
Available:
Muting: off
and sysctl kern.console is / (not that I know what that means).
Then I try this:
$ conscontrol add /dev/console
conscontrol: could not add console as a console: Device not configured
$ conscontrol add /dev/consolectl
conscontrol: could not add consolectl as a console: Device not configured
Is that the expected behavior? What else I might 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]"
No kernel messages displayed during boot
Hello, My 6.2-STABLE crashed today, and when I rebooted it, a very strange effect appeared: from the second the kernel took over, immediately after loading all .ko files, no text was printed in the console. The system booted though, and the next text was printed to the console was the login prompt. The screen didn't went blank, just all kernel messages and output of /etc/rc* wasn't there -- all was printed on the screen was FreeBSD boot menu, and login prompt. 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 disabled com port in BIOS (because the behavior looks like booting on serial console) -- nothing, absolutely nothing changes it. When I tried to boot in single-user mode, the prompt was never displayed at all, which fact indeed makes me think alogn the path of the wrong boot console. I've removed /boot/loader.conf, and double-checked that /boot.config isn't present - didn't help. My question is therefore, what cause of this effect might be? Or, if noone would be able to answer this, how I would print 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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Sam> I've lost context about your problem but it appears you're having Sam> trouble associating with "trejago" sometimes. The failed scan shows Sam> that your rssi was only 6 when you were having problems which is a Sam> very marginal signal so I'm not at all surprised you're having Sam> trouble. You've got strong signal ap's on overlapping channels (5 Sam> and 7) which are likely drowning the signal on your ap. I don't see Sam> anything the driver could do differently; this seems more an issue of Sam> your environment being very busy. I vaguely recall you were Sam> comparing the operation of the freebsd to windows. If so then I also thought of the environment issue, but it seems to me that the problem might still be elsewhere. Initially I encountered problems when I set up AP to transmit at 12% of full power, so logically I assumed that this must be not enough, and turned the AP signal up to 25, 50, and finally to 100%. What's interesting is that even on 100%, SNR wasn't really different from when it was 12%, and again ath0 didn't associate. This is doubly strange because the neighbor APs are located behind 2-3 solid brick walls, and still their SNR is 5 times higher than from my AP which is just nearby. Even when distance to AP is <1m, SNR is still comparable. Of course, I cannot control their AP signal strength, but I'd be interested to measure the signal strength from my and their APs independently, I guess there should be some regulations about max signal power... 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 list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ath0 weak connectivity
Hi Sam! Sam> I do not understand what "bad connectivity" means. I'm not a native speaker so I've apparently used a wrong term, I apologize for the confusion. Instead I should've probably said "low signal strength". Sam> If you provide Sam> information like the mac+phy revs for the card, hal version, and Sam> statistics from programs like athstats then it might be possible to Sam> identify what's wrong. Otherwise look at turning on debugging at the Sam> net80211 layer with wlandebug. Both athstats and wlandebug are found Sam> in src/tools/tools (under net80211 and ath respectively). Here it is: dmesg: mem 0xa840-0xa840 irq 11 at device 2.0 on pci4 ath0: [GIANT-LOCKED] ath0: Ethernet address: 00:14:a4:80:f6:74 mac 5.9 phy 4.3 radio 3.6 sysctl -a | grep ath | grep hal: hw.ath.hal.version: 0.9.16.16 hw.ath.hal.dma_brt: 2 hw.ath.hal.sw_brt: 10 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 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ath0 weak connectivity
Hi,
Has anyone experienced problems with ath0 giving bad connectivity on
6.1-STABLE? My wireless card reported as Atheros 5212 rapidly loses
connectivity if I move it more than 2-3 meters away from the access
point, but the same notebook connects well from under windows.
I tried both kernel with both old device ath_rate_sample and ath_rate_onoe,
tried to play with AP's settings, changed transmit rate and beacon
interval, nothing helps. One interesting thing though is that "ifconfig ath0
scan" reports my station as configured to 119ms beacon interval, while
it is set to 100ms actually.
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
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 - Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-RELEASE #2: Sat Dec 28 11:51:07 CET 2002 root@ant:/usr/obj/usr/src/sys/ANT Timecounter "i8254" frequency 1193182 Hz CPU: AMD Athlon(tm) Processor (650.03-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x621 Stepping = 1 Features=0x183f9ff AMD Features=0xc040 real memory = 134135808 (130992K bytes) avail memory = 126533632 (123568K bytes) Preloaded elf kernel "kernel" at 0xc03b4000. Pentium Pro MTRR support enabled apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 10 at device 4.2 on pci0 uhci_run: setting run=0 uhci_run: done cmd=0x0 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 10 at device 4.3 on pci0 uhci_run: setting run=0 uhci_run: done cmd=0x0 sts=0x20 uhci_run: setting run=1 uhci_run: done cmd=0x81 sts=0x0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at 9.0 irq 10 pcm0: mem 0xe100-0xe1007fff irq 11 at device 10.0 on pci0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xa400-0xa43f irq 10 at device 13.0 on pci0 xl0: Ethernet address: 00:60:08:53:cc:50 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib1: on motherboard pci2: on pcib1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging disabled ad0: 39266MB [79780/16/63] at ata0-master UDMA66 acd0: CDROM at ata1-master using PIO3 Mounting root from ufs:/dev/ad0s3a ad0s1: raw partition size != slice size ad0s1: start 15566985, end 58589054, size 43022070 ad0s1c: start 15566985, end 31937219, size 16370235 /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized xl0: promiscuous mode enabled vmnet0: promiscuous mode enabled * attached * umass0: KONICA CORPORATION KD-500Z, rev 1.10/1.00, addr 2, SCSI over Bulk-Only umass0: Max Lun is 0 umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:-1: Attached to scbus0 as device 0 scbus0: scanning for umass0:0:0:-1 umass-sim:0:-1:-1:XPT_PATH_INQ:. umass0:0:0:0:XPT_PATH_INQ:. umass0:0:0:0:XPT_PATH_INQ:. umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/36b data/18b sense umass0: CBW 1: cmd = 6b (0x12002400), data = 36 bytes, dir = in umass-sim:0:1:0:func_code 0x0004: Invalid target (no wildcard) umass-sim:0:2:0:func_code 0x0004: Invalid target (no wildcard) umass0: Attach finished umass0: Handling BBB state 1 (BBB CBW), xfer=0xc0a8c900, NORMAL_COMPLETION umass0: Handling BBB state 2 (BBB Data), xfer=0xc0fd7580, NORMAL_COMPLETION umass0: 0x 00811f004b6f6e6963612020 buffer=0xc0fe9a84, buflen=36 umass0: 0x 4b442d3530305a202020202020202020 umass0: 0x 312e3030 umass0: Handling BBB state 4 (BBB CSW, 1st attempt), xfer=0xc0fd7400, NORMAL_COMPLETION umass0: CSW 1: sig = 0x53425355 (valid), tag = 1, res = 0, status = 0x00 (good) umass0:0:0:0:XPT_SCSI_IO: cmd: 0x12, flags: 0x40, 6b cmd/255b data/18b sense umass0: CBW 2: cmd = 6b (0x12018000ff00), data = 255 bytes, dir = in umass0: Handling BBB state 1 (BBB CBW), xfer=0xc0a8c900, NORMAL_COMPLETION umass0: Handling BBB state 2 (BBB Data), xfer=0xc0fd7580, NORMAL_COMPLETION umass0: 0x 0080 buffer=0xc0e53e00, buflen=255 umass0
Re: pcm0 problems on 4.7
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 card to a SB Live!. The more interesting thing is, that after the change the onboard card also functions o.k. It is not IRQ problem, at least on a motherboard level, since windows had no problem with the old card. If anyone is willing, I can give the old card away for the investigation. -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
perl paths corrupted
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 /usr/local/lib/perl5/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 .). BEGIN failed--compilation aborted. I am aware that the default @INC is stored in /usr/lib/libperl*, and tried to recompile perl with the correct path. Firstly, I was tangled in these; secondly, it didn't build successfully: Making B (dynamic) cc -o ../../lib/auto/B/B.so -Bshareable -L/usr/local/lib B.o B.o: In function `cc_opclass': B.o(.text+0x5e): undefined reference to `Perl_opargs' B.o(.text+0x1d1): undefined reference to `Perl_op_name' *** Error code 1 After lost of hacks, the perl was build, but was unusable, not at least because the default paths were wrong again. I am seeking help, on how would I either setup perl paths correctly, or compile perl without excessive hacking, with the default @INC correctly set? -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
sysinstall compile fails
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: `keymap_ua_koi8_u_shift_alt' undeclared here (not in a function) keymap.h:6084: initializer element is not constant keymap.h:6084: (near initialization for `keymapInfos[38].map') *** Error code 1 root@plab release/sysinstall# uname -a FreeBSD plab.ku.dk 4.3-STABLE FreeBSD 4.3-STABLE #0: Fri Nov 16 11:15:06 CET 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PUMA i386 -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Help needed - can't kill a process
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, Dmitry --- www.karasik.eu.org --- To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
