FreeBSD 9.2-RELEASE doesn't correctly detect USB mouse/keyboard
I am running vanilla 9.2-RELEASE on an HP Z230. Strangely, my USB keyboard and mouse don't work. When I attach, here is what shows: Oct 11 12:36:39 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:39 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:39 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:48 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:48 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:48 waridi kernel: uhub_reattach_port: could not allocate new device Oct 11 12:36:55 waridi kernel: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) Oct 11 12:36:55 waridi kernel: ugen0.2: Unknown at usbus0 (disconnected) Oct 11 12:36:55 waridi kernel: uhub_reattach_port: could not allocate new device $ uname -a FreeBSD waridi.kihingovillage.com 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 r...@bake.isc.freebsd.org:/usr/obj /usr/src/sys/GENERIC amd64 I am wondering if there is something obvious I am missing? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 I can't hear you -- I'm using the scrambler. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
detecting keyboard layout during boot
Hello, I have in /etc/rc.conf a line keymap=german.iso to set the keyboard to German; as the system in question is on an USB key for boot and sometimes used in other laptops with QWERTY layout, I would like to have it adapt itself to the actual layout without changing anything before booting in rc.conf and without asking the user to press a key ... is there some way to detect the actual keyboard layout automagically? Thanks matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: detecting keyboard layout during boot
On Wed, 2013-05-15 at 09:35 +0200, Matthias Apitz wrote: is there some way to detect the actual keyboard layout automagically? I suspect it's impossible to request what keyboard is used, since some Linux installers ask the user to type some keys, after that auto-detection does work. Perhaps you only can start a session with a script, that does ask the user to type and then set up the needed keyboard map. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: detecting keyboard layout during boot
On Wed, 15 May 2013 09:35:54 +0200, Matthias Apitz wrote: Hello, I have in /etc/rc.conf a line keymap=german.iso to set the keyboard to German; as the system in question is on an USB key for boot and sometimes used in other laptops with QWERTY layout, I would like to have it adapt itself to the actual layout without changing anything before booting in rc.conf and without asking the user to press a key ... is there some way to detect the actual keyboard layout automagically? Basically, it's impossible, but it can be made possible by the power of FreeBSD. :-) Allow me to explain: Depending on where the keyboard is attached, some connections (AT 5 pin plug, PS/2 6 pin mini-plug) do not offer any means to detect what keyboard is connected (or even _if_ a keyboard is connected). This case usually applies to keyboards built into laptops. You can see that in dmesg | grep kbd. Example: % dmesg | grep kbd kbd1 at kbdmux0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ukbd0: vendor 0x0430 Sun USB Keyboard, class 0/0, rev 2.00/1.05, addr 5 on usbus1 kbd2 at ukbd0 You see: The AT keyboard controller is detected, kbd0 is available. But there is no actual keyboard connected to that PS/2 port. Instead, a Sun USB Type 7 keyboard (german layout) is being used here, as kbd2. But as you're asking about USB, there is a way. But this way depends on how the manufacturer cooperates. Let's discuss that. As you know, every USB device is characterized by two specific USB numbers: vendor ID and product ID. In some cases, the product ID is different regarding the language layout, but you need to test that individually, no standard seems to exist. Then, you can use the devd.conf file to select per this ID and load the correct keyboard layout. This is done in the rc.conf stage. Prior to this stage, the kernel stage, you can hardcode layouts in the kernel config. Last time I checked this stopped working, I have been told that the use of kbdmux is the reason for this observation. Example: options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP=german.iso options UKBD_DFLT_KEYMAP makeoptions UKBD_DFLT_KEYMAP=german.iso Those options would enable a german keyboard layout even in SUM. Even adding a font for proper display has been possible: options SC_DFLT_FONT makeoptions SC_DFLT_FONT=iso Not sure if this is still supported. Using Umlauts and Eszett is discouraged in filenames, and the blind knowledge of the US keyboard layout is quite standard among sysadmins. :-) As a summery: No soup for you! ;-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: detecting keyboard layout during boot
El día Wednesday, May 15, 2013 a las 03:27:24PM +0200, Polytropon escribió: On Wed, 15 May 2013 09:35:54 +0200, Matthias Apitz wrote: Hello, I have in /etc/rc.conf a line keymap=german.iso to set the keyboard to German; as the system in question is on an USB key for boot and sometimes used in other laptops with QWERTY layout, I would like to have it adapt itself to the actual layout without changing anything before booting in rc.conf and without asking the user to press a key ... is there some way to detect the actual keyboard layout automagically? Basically, it's impossible, but it can be made possible by the power of FreeBSD. :-) Allow me to explain: Depending on where the keyboard is attached, some connections (AT 5 pin plug, PS/2 6 pin mini-plug) do not offer any means to detect what keyboard is connected (or even _if_ a keyboard is connected). This case usually applies to keyboards built into laptops. You can see that in dmesg | grep kbd. Example: % dmesg | grep kbd kbd1 at kbdmux0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ukbd0: vendor 0x0430 Sun USB Keyboard, class 0/0, rev 2.00/1.05, addr 5 on usbus1 kbd2 at ukbd0 You see: The AT keyboard controller is detected, kbd0 is available. But there is no actual keyboard connected to that PS/2 port. Instead, a Sun USB Type 7 keyboard (german layout) is being used here, as kbd2. Hello, Here on an laptop/netbook EeePC 900 with English keyboard it says: # dmesg | fgrep kbd kbd1 at kbdmux0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 how do I know that the kb layout is English? But as you're asking about USB, there is a way. But this way depends on how the manufacturer cooperates. Let's discuss that. USB was only meant as the boot device. matthias -- Sent from my FreeBSD netbook Matthias Apitz | - No system with backdoors like Apple/Android E-mail: g...@unixarea.de | - Never being an iSlave WWW: http://www.unixarea.de/ | - No proprietary attachments, no HTML/RTF in E-mail phone: +49-170-4527211 | - Respect for open standards ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: detecting keyboard layout during boot
On Wed, 15 May 2013 15:53:08 +0200, Matthias Apitz wrote: Hello, Here on an laptop/netbook EeePC 900 with English keyboard it says: # dmesg | fgrep kbd kbd1 at kbdmux0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 how do I know that the kb layout is English? By looking at it. ONLY by looking at it. :-) Even if you would remove the built-in keyboard (disconnect the flex), you would see that entry. It's not about the keyboard per se, it's about the keyboard controller. This interface usually is in parallel with a PS/2 connector (if present). There is no language information in it. But as you're asking about USB, there is a way. But this way depends on how the manufacturer cooperates. Let's discuss that. USB was only meant as the boot device. Okay, then I misread it. English is not my native language. :-) The logical conclusion: You have no way to find out what keyboard is physically installed (or attached via PS/2). This _might_ be not entirely true: If you can obtain some hardware identification of the eeePC you're using, maybe some kind of ACPI string or other vendor and product ID from some component, you could guess what localization the device has, and then assume what keyboard is installed. But that's just a wild guess from my side. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: detecting keyboard layout during boot
On Wed, May 15, 2013, at 07:45 AM, Polytropon wrote: On Wed, 15 May 2013 15:53:08 +0200, Matthias Apitz wrote: Hello, Here on an laptop/netbook EeePC 900 with English keyboard it says: # dmesg | fgrep kbd kbd1 at kbdmux0 atkbdc0: Keyboard controller (i8042) port 0x60,0x64 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 how do I know that the kb layout is English? By looking at it. ONLY by looking at it. :-) Even if you would remove the built-in keyboard (disconnect the flex), you would see that entry. It's not about the keyboard per se, it's about the keyboard controller. This interface usually is in parallel with a PS/2 connector (if present). There is no language information in it. But as you're asking about USB, there is a way. But this way depends on how the manufacturer cooperates. Let's discuss that. USB was only meant as the boot device. Okay, then I misread it. English is not my native language. :-) The logical conclusion: You have no way to find out what keyboard is physically installed (or attached via PS/2). This _might_ be not entirely true: If you can obtain some hardware identification of the eeePC you're using, maybe some kind of ACPI string or other vendor and product ID from some component, you could guess what localization the device has, and then assume what keyboard is installed. But that's just a wild guess from my side. Have you tried dmidecode? Handle 0x000E, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Keyboard External Connector Type: PS/2 Port Type: Keyboard Port Handle 0x000F, DMI type 8, 9 bytes Port Connector Information Internal Reference Designator: J1A1 Internal Connector Type: None External Reference Designator: Mouse External Connector Type: PS/2 Port Type: Mouse Port -- Signore Citizen signoreciti...@myopera.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Keyboard weirdness
All of a sudden today Im having a very weird issue with my keyboards. 1. Pressing the ctrl key nets a single quotation mark 2. Pressing s nets s. (s followed by a period). Pressing period nets that same s. combination 3. Pressing the quotation key does nothing. Thats just what Ive come across so far. You can imagine how much Ive had to edit this mes.s.age with all the periods and letter s Ive typed... Anyone have an idea of why this might be happening? I didnt change anything, and it seems to happen even on the console. -- Using Opera's mail client: http://www.opera.com/mail/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard weirdness
On Sat, 12 Jan 2013 14:48:01 -0500, Andre Goree an...@drenet.info wrote: All of a sudden today Im having a very weird issue with my keyboards. 1. Pressing the ctrl key nets a single quotation mark 2. Pressing s nets s. (s followed by a period). Pressing period nets that same s. combination 3. Pressing the quotation key does nothing. Thats just what Ive come across so far. You can imagine how much Ive had to edit this mes.s.age with all the periods and letter s Ive typed... Anyone have an idea of why this might be happening? I didnt change anything, and it seems to happen even on the console. Turns out this is a hardware problem with they keyboard itself, I have the same issue when plugging the keyboard into another system. -- Using Opera's mail client: http://www.opera.com/mail/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: keyboard and mouse problem
Jack Mc Lauren jack.mclau...@yahoo.com writes: I have a freeBSD 8.2 amd64 on my system and I'm using gnome environment. But after a few seconds my USB keyboard and PS/2 mouse hang up !!! What should I do ? Are you still able to switch to other virtual terminals? Are you still able to ssh in to the system and see whether the console mouse and keyboard are generating interrupts? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: keyboard and mouse problem
Hi, On Tue, 8 Jan 2013 23:53:04 -0800 (PST) Jack Mc Lauren jack.mclau...@yahoo.com wrote: I have a freeBSD 8.2 amd64 on my system and I'm using gnome environment. But after a few seconds my USB keyboard and PS/2 mouse hang up !!! when did you setup the system? Did this happen after an update? What should I do ? Can you test without mouse? To be honest, I was not able to get a system up with a PS/2 mouse or keyboard since years. I blamed it on the old hardware and got me a new keyboard and a new mouse with USB. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
keyboard and mouse problem
Hi guys I have a freeBSD 8.2 amd64 on my system and I'm using gnome environment. But after a few seconds my USB keyboard and PS/2 mouse hang up !!! What should I do ? Thanks in advance ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Apple Aluminium Keyboard (w/ numpad) woe
Hi all, has anyone got any pointers for why my Apple (A1243) wired USB keyboard (with numpad, gb/uk model) doesn't want to report F13 (and some other keys). This is on 9.0, though it was the same on 8, 7, and IIRC, 6. It's clear that the ukbd driver sees the key presses (see below), but I can't seem to get them to be recognised by syscons. (Even with a syscons keymap where all the NUL's have become '*') With ukbd debug via the sysctl I see the following, so clearly ukbd gets the keys (this output is from pressing, Return, F13, F14, F15) ... but why doesn't syscons get the keys ? Aug 9 23:41:09 tv kernel: ukbd_put_key: 0x28 (40) pressed Aug 9 23:41:09 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:09 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:09 tv kernel: ukbd_put_key: 0x428 (1064) released Aug 9 23:41:10 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:10 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:10 tv kernel: ukbd_intr_callback: [0] = 0x28 Aug 9 23:41:10 tv kernel: ukbd_put_key: 0x28 (40) pressed Aug 9 23:41:11 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:11 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:11 tv kernel: ukbd_put_key: 0x428 (1064) released Aug 9 23:41:12 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:12 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:12 tv kernel: ukbd_intr_callback: [0] = 0x68 Aug 9 23:41:12 tv kernel: ukbd_put_key: 0x68 (104) pressed Aug 9 23:41:12 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:12 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:12 tv kernel: ukbd_put_key: 0x468 (1128) released Aug 9 23:41:13 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:13 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:13 tv kernel: ukbd_intr_callback: [0] = 0x69 Aug 9 23:41:13 tv kernel: ukbd_put_key: 0x69 (105) pressed Aug 9 23:41:13 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:13 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:13 tv kernel: ukbd_put_key: 0x469 (1129) released Aug 9 23:41:14 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:14 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:14 tv kernel: ukbd_intr_callback: [0] = 0x6a Aug 9 23:41:14 tv kernel: ukbd_put_key: 0x6a (106) pressed Aug 9 23:41:14 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:14 tv kernel: ukbd_intr_callback: modifiers = 0x Aug 9 23:41:14 tv kernel: ukbd_put_key: 0x46a (1130) released Aug 9 23:41:14 tv kernel: ukbd_intr_callback: actlen=8 bytes Aug 9 23:41:14 tv kernel: ukbd_intr_callback: modifiers = 0x0001 Aug 9 23:41:14 tv kernel: ukbd_put_key: 0xe0 (224) pressed Thanks very much, and apologies if there's a known answer, it's not something I've managed to find yet if it is. Steve Roome P.S. I'm hoping for an obvious hint or flag somewhere to set, but I'm open to doing a bit of code if that's the only way. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Apple Aluminium Keyboard (w/ numpad) woe
On Fri, 10 Aug 2012 00:10:46 +0100, Steve Roome wrote: Hi all, has anyone got any pointers for why my Apple (A1243) wired USB keyboard (with numpad, gb/uk model) doesn't want to report F13 (and some other keys). Seems to be related not only to this model. I have the old version here (white plastic, german layout), and F13-F16 and the four keys on the top right don't seem to generate anything. I've checked both text mode and xev (in X) - and made almost the same observations as you did. I don't have that kind of strange behaviour with other multifunctional keyboards (Sun type 6 and 7, german layout). Thanks very much, and apologies if there's a known answer, it's not something I've managed to find yet if it is. Sorry, no solution here, only confirmation... :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: keyboard latency from time to time
El día Monday, April 09, 2012 a las 07:06:59PM +0200, Matthias Apitz escribió: Months later, in some other issue, I learned about the feature of KDE slow keys and what I have described is exactly the same behaviour and I can now even reproduce this with just pressing and holding down the Shift-key for around 8 secs; when it happens one must go to the KDE Control Center and activate 'slow keys' (yes, they are not shown as activated in this moment) and deactivate 'slow keys' again, and all is fine. I was curious and digged deeper into this... slow keys is part of the X11 XKB-protocol (details in XKBproto.pdf or XkbGetSlowKeysDelay(3) man page; in the ports there is ports/x11/xkbset utility and with this one can set the Slowkeys acceptance delay (time in ms the X server awaits a key is hold down before sending out the keypress event) or to switch it off again: $ xkbset slowkeys 500 # to switch in on and set 500ms delay $ xkbset -slowkeys # to switch it off again HIH matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Was..... Lots of lagging after upgrade of xorg. Now keyboard layout is lost
On Tue, 24 Apr 2012 07:13:20 +0200, Leslie Jensen wrote: 2012-04-23 19:56, Leslie Jensen skrev: 2012-04-23 18:29, Warren Block skrev: On Mon, 23 Apr 2012, Leslie Jensen wrote: Use Option AutoAddDevices Off to disable HAL input device detection. ___ http://www.wonkity.com/~wblock/docs/html/aei.html After adding the above Option I lost the Swedish layout of my keyboard. Following the instructions and editing the /usr/local/etc/hal/fdi/policy/x11-input.fdi I already have the file in place with the following setup: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp /merge merge key=input.x11_options.XkbModel type=stringlatitude/merge merge key=input.x11_options.XkbLayout type=stringse/merge /match /device /deviceinfo Where else can I control the setting for Swedish? You could use the default method: /etc/X11/xorg.conf which is designed to _centralize_ X-related settings. Keyboard settings can also be put there. For example, this is what I use to define a german keyboard layout (and which applies everywhere in X, as intended): Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout de Option XkbOptionsterminate:ctrl_alt_bksp EndSection You can employ this approach, changing it to swedish language. Note that I'm using the X setup without HAL and DBUS here. Additionally, there's the method of using xmodmap with a custom ~/.xmodmaprc file which can be used to make keyboard language settings work _independently_ from both xorg.conf and XML files scattered across the local/ subtree. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Was..... Lots of lagging after upgrade of xorg. Now keyboard layout is lost
On Tue, 24 Apr 2012, Leslie Jensen wrote: 2012-04-23 19:56, Leslie Jensen skrev: 2012-04-23 18:29, Warren Block skrev: On Mon, 23 Apr 2012, Leslie Jensen wrote: Use Option AutoAddDevices Off to disable HAL input device detection. ___ http://www.wonkity.com/~wblock/docs/html/aei.html After adding the above Option I lost the Swedish layout of my keyboard. It's not required to disable HAL, but that's usually what people are trying to do when they turn off AEI. To leave HAL enabled, remove the AutoAddDevices option. Keyboard layout will come from the HAL fdi file. Keyboard layout can also be set with setxkbmap in .xinitrc or .xsession, or in the keyboard InputDevice section as Polytropon shows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Was..... Lots of lagging after upgrade of xorg. Now keyboard layout is lost
2012-04-24 16:01, Warren Block skrev: On Tue, 24 Apr 2012, Leslie Jensen wrote: 2012-04-23 19:56, Leslie Jensen skrev: 2012-04-23 18:29, Warren Block skrev: On Mon, 23 Apr 2012, Leslie Jensen wrote: Use Option AutoAddDevices Off to disable HAL input device detection. ___ http://www.wonkity.com/~wblock/docs/html/aei.html After adding the above Option I lost the Swedish layout of my keyboard. It's not required to disable HAL, but that's usually what people are trying to do when they turn off AEI. To leave HAL enabled, remove the AutoAddDevices option. Keyboard layout will come from the HAL fdi file. Keyboard layout can also be set with setxkbmap in .xinitrc or .xsession, or in the keyboard InputDevice section as Polytropon shows. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Yes, thank you. Polytropon solution works for me :-) /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Was..... Lots of lagging after upgrade of xorg. Now keyboard layout is lost
2012-04-23 19:56, Leslie Jensen skrev: 2012-04-23 18:29, Warren Block skrev: On Mon, 23 Apr 2012, Leslie Jensen wrote: Use Option AutoAddDevices Off to disable HAL input device detection. ___ http://www.wonkity.com/~wblock/docs/html/aei.html After adding the above Option I lost the Swedish layout of my keyboard. Following the instructions and editing the /usr/local/etc/hal/fdi/policy/x11-input.fdi I already have the file in place with the following setup: ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp /merge merge key=input.x11_options.XkbModel type=stringlatitude/merge merge key=input.x11_options.XkbLayout type=stringse/merge /match /device /deviceinfo Where else can I control the setting for Swedish? I can see in /usr/local/share/X11/xkb/rules/base.lst that there is the ! variant parameters. Any hints appreciated. Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Dual monitors ok, but no mouse and keyboard action on the slave screen
I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 separate desktops. I plan to have stuff like wireshark etc on the smallest. But I have a problem, I can get no work done since I have no mouse or keyboard working on the 17... Anyone have somewhere with a solution to point me towards ? Blessed be.. Kenneth Hatteland ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual monitors ok, but no mouse and keyboard action on the slave screen
On Sun, 22 Apr 2012 13:43:31 +0200, Kenneth Hatteland wrote: I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 separate desktops. I plan to have stuff like wireshark etc on the smallest. But I have a problem, I can get no work done since I have no mouse or keyboard working on the 17... Anyone have somewhere with a solution to point me towards ? There are basically two kind of two-monitor settings: One is to have the WM manage them, the other one is to concatenate them to one logical screen. I've been using the concatenated screen with two 21 CRTs, each running at 1400x1050, so the result was a 2800x1050 ultra extended extraordinary super hyper big wide screen. :-) You can configure this in your /etc/X11/xorg.conf (which you can have X auto-generate). For example, ServerLayout could contain Screen 0 Screen0 0 0 Screen 1 Screen1 LeftOf Screen0 Option Xinerama on Then add the two Monitor sections according to the screen parameters (in my case, identical data). In the final Screen section, you can then experiment with Option TwinView Option TwinViewOrientation LeftOf Option ConnectedMonitor CRT, CRT depending on your actual connection setup. You can find more inspiration here: Dual head issues, non-xinerama setup possible? http://forums.freebsd.org/showthread.php?t=11567 Dual monitor setup http://lists.freebsd.org/pipermail/freebsd-mobile/2005-January/005613.html Dual monitors xorg.conf http://lists.freebsd.org/pipermail/freebsd-questions/2005-May/087929.html Using two monitors with X.org http://www.freebsddiary.org/xorg-two-screens.php Many things to consider depend on your actual setting (which hardware you have, what WM you use and which behaviour you want). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dual monitors ok, but no mouse and keyboard action on the slave screen
On Mon, 23 Apr 2012, Polytropon wrote: On Sun, 22 Apr 2012 13:43:31 +0200, Kenneth Hatteland wrote: I`ve gotten a 17 inch monitor in addition to my 22 inch working with 2 separate desktops. I plan to have stuff like wireshark etc on the smallest. But I have a problem, I can get no work done since I have no mouse or keyboard working on the 17... Anyone have somewhere with a solution to point me towards ? There are basically two kind of two-monitor settings: One is to have the WM manage them, the other one is to concatenate them to one logical screen. I've been using the concatenated screen with two 21 CRTs, each running at 1400x1050, so the result was a 2800x1050 ultra extended extraordinary super hyper big wide screen. :-) You can configure this in your /etc/X11/xorg.conf (which you can have X auto-generate). For example, ServerLayout could contain Screen 0 Screen0 0 0 Screen 1 Screen1 LeftOf Screen0 Option Xinerama on The newer way to do this is with a Virtual entry in the Screen section: Section Monitor Identifier Monitor0 VendorName HWP ModelName2615 Option PreferredMode 1920x1200 Option Position 1280 0 EndSection Section Monitor Identifier Monitor1 VendorName SAM ModelName215 Option PreferredMode 1280x1024 Option Position 0 0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 SubSection Display Virtual 3200 1200 EndSubSection EndSection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Keyboard Input Vanishes Seconds After Loading GNOME
I am experiencing a most peculiar problem upon loading the GNOME desktop on a brand new install of FreeBSD v9.0 RELEASE. So far, I have Installed the FreeBSD v9.0 RELEASE operating system for the x86-64 platform Installed xorg Installed gnome2 In order to enable both the loading of xorg and gnome(2), I have edited my /etc/rc.conf file. Here is what cat reports: #cat /etc/rc.conf hostname= Mephisto ifconfig_re0=DHCP sshd_enable=YES moused_enable=YES #Set dumpdev to AUTO to enable crash dumps, NO to disable dumpdev=NO hald_enable=YES dbus_enable=YES gnome_enable=YES gdm_enable=YES After entering in my password at the GNOME GDM login, I am able to get to my desktop and have access to my programs. However, if I were to open say Gedit and type for any period of time, my keyboard input will disappear and I will either be unable to type anything or it will infinitely type the last character I typed (e.g. the letter k). Has anyone else faced this situation and if so, how do I go about solving this? Thank you very much for taking the time to read my request. Sincerely, Timothy ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: keyboard latency from time to time
El día Monday, July 25, 2011 a las 05:10:47PM +0200, Matthias Apitz escribió: Hello, I run a 9-CURRENT from end of October on an Acer D250 laptop; which in general runs very fine; from time to time (say once a month) I encounter the following situation within KDE3 or X11: from a moment to another (can't say what action triggers this) the keyboard stops working; there are just no keyevents delivered on short press to any window; I've checked it with xev(1); mouse is working fine and I can close the windows or the whole session of KDE, of course loosing my connections or the content of files I'm editing in that moment; the keyevent is only delivered when you press the key for around half second, or so, and after this also the normal key re-iteration is produced; its even hard to catch only one keyevent and not twice or more; this is true for all keys, including Ctrl and Backspace, ... after restarting X11 and KDE it is fine again; Hello, Months later, in some other issue, I learned about the feature of KDE slow keys and what I have described is exactly the same behaviour and I can now even reproduce this with just pressing and holding down the Shift-key for around 8 secs; when it happens one must go to the KDE Control Center and activate 'slow keys' (yes, they are not shown as activated in this moment) and deactivate 'slow keys' again, and all is fine. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: XFCE keyboard layout tab missing
On Fri, 27 Jan 2012 02:12:09 + Neil Munro neilmu...@gmail.com wrote: Hi all, first I apologise if this is a known issue, I have been searching but can't seem to find an answer. I am looking to switch to FreeBSD full time and this is the only thing holding me back I want to run XFCE and I know the 4.8 release has some issues with mounting devices which used to use HAL but doesn't now, from what I understand of the issue it's not a deal breaker for me, what I am struggling with is that I cannot set the keyboard in XFCE to dvorak, as the layout tab is missing and the keyboard icon in the settings window has no icon. I imagined this was at first just requiring the correct language pack but having installed the GB language pack the missing tab does not appear. Additionally I recompiled xfce4-settings with all options enabled to no avail. Does anyone know what may be causing this issue? Many thanks, Neil Hi Neil, I think you need to install the port /usr/ports/deskutils/xfce4-xkb-plugin (or package if you prefer). Tony ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
XFCE keyboard layout tab missing
Hi all, first I apologise if this is a known issue, I have been searching but can't seem to find an answer. I am looking to switch to FreeBSD full time and this is the only thing holding me back I want to run XFCE and I know the 4.8 release has some issues with mounting devices which used to use HAL but doesn't now, from what I understand of the issue it's not a deal breaker for me, what I am struggling with is that I cannot set the keyboard in XFCE to dvorak, as the layout tab is missing and the keyboard icon in the settings window has no icon. I imagined this was at first just requiring the correct language pack but having installed the GB language pack the missing tab does not appear. Additionally I recompiled xfce4-settings with all options enabled to no avail. Does anyone know what may be causing this issue? Many thanks, Neil ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Problems with keyboard on the loader menu
-Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd- questi...@freebsd.org] On Behalf Of Airton Arantes Sent: Wednesday, December 07, 2011 5:46 PM To: freebsd-questions@freebsd.org Subject: Problems with keyboard on the loader menu I'm having troubles with my keyboard when the bootstrapping reach the loader menu. My Keyboard simply doesn't works, but before and after the loader menu my keyboard works very well. I have seen BIOS settings like USB keyboard and nothing is helping. I didn't no one kernel tuning, I'm using GENERIC. The Server is a HP Proliant DL120 G6. Does anyone here can help me? -- Airton Arantes Coelho Filho I have found that I have to do the following on some of our Proliant G5's - # cd / # echo -P boot.conf Also, are you using the VGA or the serial console? We enable both (our serial consoles are connected to terminal servers for remote access and VGA is used for the physical access). Our keyboards are USB. This is with FreeBSD 8.0 AMD64 Patrick Patrick Mahan Lead Technical Kernel Engineer Adara Networks Disclaimer: The opinions expressed here are solely the responsibility of the author and are not to be construed as an official opinion of Adara Networks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
X11 - keyboard driver unloaded, how to load it again
Hi, I've an USB Mouse - Microsoft Wireless Mouse 1000, which is recognized also as a keyboard: ugen1.3: vendor 0x192f at usbus1 (disconnected) ums0: at uhub2, port 2, addr 3 (disconnected) ugen0.5: Microsoft at usbus0 ukbd0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 kbd2 at ukbd0 ums0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 ums0: 5 buttons and [XYZT] coordinates ID=26 ums0: 0 buttons and [T] coordinates ID=0 uhid0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 After disconnecting this mouse kbd module was unloaded by X: [ 40002.703] (**) Microsoft 2.4GHz Transceiver v8.0: always reports core events [ 40002.703] (**) Microsoft 2.4GHz Transceiver v8.0: always reports core events [ 40002.704] (**) Option Protocol standard [ 40002.704] (**) Option XkbRules base [ 40002.704] (**) Option XkbModel pc105 [ 40002.704] (**) Option XkbLayout pl [ 40002.704] (**) Option XkbOptions terminate:ctrl_alt_bksp [ 40002.709] (**) Option config_info hal:/org/freedesktop/Hal/devices/usb_device_45e_745_noserial_if0 [ 40002.709] (II) XINPUT: Adding extended input device Microsoft 2.4GHz Transceiver v8.0 (type: KEYBOARD) [ 47161.229] (II) 3rd Button detected: disabling emulate3Button [ 49888.691] (II) config/hal: removing device Microsoft 2.4GHz Transceiver v8.0 [ 49888.696] (II) UnloadModule: kbd [ 49888.696] (II) Unloading kbd Question is: how to prevent this behavior in X and how to reload module 'kbd' under working X session (I can connect through ssh to this machine). best regards, -- Sebastian Chmielewski ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X11 - keyboard driver unloaded, how to load it again
On Wed, 7 Dec 2011 08:48:20 +0100 Sebastian Chmielewski chmi...@o2.pl wrote: Hi, I've an USB Mouse - Microsoft Wireless Mouse 1000, which is recognized also as a keyboard: ugen1.3: vendor 0x192f at usbus1 (disconnected) ums0: at uhub2, port 2, addr 3 (disconnected) ugen0.5: Microsoft at usbus0 ukbd0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 kbd2 at ukbd0 ums0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 ums0: 5 buttons and [XYZT] coordinates ID=26 ums0: 0 buttons and [T] coordinates ID=0 uhid0: Microsoft Microsoft 2.4GHz Transceiver v8.0, class 0/0, rev 2.00/6.56, addr 5 on usbus0 After disconnecting this mouse kbd module was unloaded by X: [ 40002.703] (**) Microsoft 2.4GHz Transceiver v8.0: always reports core events [ 40002.703] (**) Microsoft 2.4GHz Transceiver v8.0: always reports core events [ 40002.704] (**) Option Protocol standard [ 40002.704] (**) Option XkbRules base [ 40002.704] (**) Option XkbModel pc105 [ 40002.704] (**) Option XkbLayout pl [ 40002.704] (**) Option XkbOptions terminate:ctrl_alt_bksp [ 40002.709] (**) Option config_info hal:/org/freedesktop/Hal/devices/usb_device_45e_745_noserial_if0 [ 40002.709] (II) XINPUT: Adding extended input device Microsoft 2.4GHz Transceiver v8.0 (type: KEYBOARD) [ 47161.229] (II) 3rd Button detected: disabling emulate3Button [ 49888.691] (II) config/hal: removing device Microsoft 2.4GHz Transceiver v8.0 [ 49888.696] (II) UnloadModule: kbd [ 49888.696] (II) Unloading kbd Question is: how to prevent this behavior in X and how to reload module 'kbd' under working X session (I can connect through ssh to this machine). I would suggest just disabling HAL support for x11-server/xorg-server and just statically configuring the file. The only thing you may possibly want to do after that is make sure moused is started if you are have any non-USB mice on that system as well. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Problems with keyboard on the loader menu
I'm having troubles with my keyboard when the bootstrapping reach the loader menu. My Keyboard simply doesn't works, but before and after the loader menu my keyboard works very well. I have seen BIOS settings like USB keyboard and nothing is helping. I didn't no one kernel tuning, I'm using GENERIC. The Server is a HP Proliant DL120 G6. Does anyone here can help me? -- Airton Arantes Coelho Filho ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No usb keyboard in single user mode
On 11/11/2011 12:02, Polytropon wrote: On Fri, 11 Nov 2011 10:41:56 +0100, David Demelier wrote: When prompted Enter full pathname of shell or RETURN for /bin/sh:uhub3: 6 ports with 6 removable, self powered uhub7: 8 ports with 8 removable, self powered ugen0.2:BTC at usbus0 ukbd0:BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.20, addr 2 on usbus0 kbd1 at ukbd0 uhid0:BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.20, addr 2 on usbus0 ugen1.2:vendor 0x0a12 at usbus1 ubt0:vendor 0x0a12 EDRClassone, class 224/1, rev 2.00/19.58, addr 2 on usbus1 ugen0.3:Logitech at usbus0 So here nothing possible to do, only shutdown by power button. After the keyboard has been detected, you should be able to enter full pathname of shell or RETURN for /bin/sh. Possible obstacle if you do NOT have device kbdmux in your kernel configuration! I have heard a long time ago that legacy USB must be enabled in the BIOS and it is in mine. I also had a similar experience in v7 with my old system. After waiting for the kernel to identify ukbd0, it could be used as intended for local logins. I remember why I added kbdmux as module. If not this option will not be honored: makeoptions UKBD_DFLT_KEYMAP=uk.iso And then I don't have my uk.iso keymap on single user mode ! -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No usb keyboard in single user mode
Hello, This question may have been asked a lot of time but I have the same problem, my USB keyboard works well with the loader, when the system has successfully booted but not in the single user mode. I don't know if this matters but when the request When prompted Enter full pathname of shell or RETURN for /bin/sh: comes, my keyboard didn't already show up in the kernel message, and the kernel still probe and attach devices after this message so the following output is printed : When prompted Enter full pathname of shell or RETURN for /bin/sh:uhub3: 6 ports with 6 removable, self powered uhub7: 8 ports with 8 removable, self powered ugen0.2: BTC at usbus0 ukbd0: BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.20, addr 2 on usbus0 kbd1 at ukbd0 uhid0: BTC USB Multimedia Keyboard, class 0/0, rev 1.10/1.20, addr 2 on usbus0 ugen1.2: vendor 0x0a12 at usbus1 ubt0: vendor 0x0a12 EDRClassone, class 224/1, rev 2.00/19.58, addr 2 on usbus1 ugen0.3: Logitech at usbus0 So here nothing possible to do, only shutdown by power button. I have heard a long time ago that legacy USB must be enabled in the BIOS and it is in mine. This is reproducible all the time on 8.2-RELEASE Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Dvorak keyboard (Spanish)
Can add Dvorak spanish variant for syscons? http://es.wikipedia.org/wiki/Archivo:Teclado_Dvorak_Español.png Cheers! -- netSys-- http://www.byteandbit.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Dvorak keyboard (Spanish)
Alvaro Castillo gobl...@gmail.com, 2011-08-25 02:25 (+0200): Can add Dvorak spanish variant for syscons? http://es.wikipedia.org/wiki/Archivo:Teclado_Dvorak_Español.png Copy /usr/share/syscons/keymaps/us.dvorak.kbd to your home directory. Start the editor of your choice and edit the file to add the keys you need for a Spanish keyboard. If you're uncertain what keycode a certain key generates, use the misc/kbdscan port [1] to find out. When you're done editing load the new keyboard with kbdcontrol -l your-spanish-dvorak.kbd When you're satisfied you can copy the file to /usr/share/syscons/keymaps/ and edit rc.conf and add keymap=your-spanish-dvorak If everything works out right you can think about using send-pr(1) or http://www.freebsd.org/send-pr.html and send the new keyboard layout to be included in FreeBSD. [1] I wrote the program but I didn't submit it to ports. I would have gone for the sysutils category, I think. Happy hacking, MC. -- http://hack.org/mc/ Use plain text e-mail, please. HTML messages silently dropped. OpenPGP welcome, 0xE4C92FA5. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
keyboard latency from time to time
Hello, I run a 9-CURRENT from end of October on an Acer D250 laptop; which in general runs very fine; from time to time (say once a month) I encounter the following situation within KDE3 or X11: from a moment to another (can't say what action triggers this) the keyboard stops working; there are just no keyevents delivered on short press to any window; I've checked it with xev(1); mouse is working fine and I can close the windows or the whole session of KDE, of course loosing my connections or the content of files I'm editing in that moment; the keyevent is only delivered when you press the key for around half second, or so, and after this also the normal key re-iteration is produced; its even hard to catch only one keyevent and not twice or more; this is true for all keys, including Ctrl and Backspace, ... after restarting X11 and KDE it is fine again; What could this causing? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xpdf does not accept input from keyboard
FreeBSD 8.2 amd64 xpdf version 3.02 whines: Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: ManagerParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfBeginLine Warning: ... found while parsing ':KeyosfBeginLine: ManagerGadgetTraverseHome()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfHelp Warning: ... found while parsing ':KeyosfHelp: ManagerGadgetHelp()' Warning: String to TranslationTable conversion encountered errors Warning: Cannot allocate colormap entry for default background. Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfHelp Warning: ... found while parsing ':KeyosfHelp: Help()' ... Warning: translation table syntax error: Unknown keysym name: osfCancel Warning: ... found while parsing 'KeyosfCancel: MenuEscape()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfSelect Warning: ... found while parsing ':KeyosfSelect: ArmAndActivate()' Warning: String to TranslationTable conversion encountered errors Warning: Cannot convert string -*-times-bold-i-normal--20-*-*-*-*-*-iso8859-1 to type FontStruct Warning: Cannot convert string -*-times-medium-r-normal--14-*-*-*-*-*-iso8859-1 to type FontStruct Warning: Color name LightYellow is not defined And then seems to mostly work, except that it does not notice any input from the keyboard. Clicking on buttons with the mouse works as expected, but attempting to paste text into the find text box does not work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
xpdf does not accept input from keyboard
FreeBSD 8.2 amd64 xpdf version 3.02 whines: Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: ManagerParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfBeginLine Warning: ... found while parsing ':KeyosfBeginLine: ManagerGadgetTraverseHome()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfHelp Warning: ... found while parsing ':KeyosfHelp: ManagerGadgetHelp()' Warning: String to TranslationTable conversion encountered errors Warning: Cannot allocate colormap entry for default background. Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfHelp Warning: ... found while parsing ':KeyosfHelp: Help()' ... Warning: translation table syntax error: Unknown keysym name: osfCancel Warning: ... found while parsing 'KeyosfCancel: MenuEscape()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfActivate Warning: ... found while parsing ':KeyosfActivate: PrimitiveParentActivate()' Warning: String to TranslationTable conversion encountered errors Warning: translation table syntax error: Unknown keysym name: osfSelect Warning: ... found while parsing ':KeyosfSelect: ArmAndActivate()' Warning: String to TranslationTable conversion encountered errors Warning: Cannot convert string -*-times-bold-i-normal--20-*-*-*-*-*-iso8859-1 to type FontStruct Warning: Cannot convert string -*-times-medium-r-normal--14-*-*-*-*-*-iso8859-1 to type FontStruct Warning: Color name LightYellow is not defined And then seems to mostly work, except that it does not notice any input from the keyboard. Clicking on buttons with the mouse works as expected, but attempting to paste text into the find text box does not work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, May 16, 2011 at 05:13:48PM -0700, Chip Camden wrote: Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. When I'm creating something from scratch that some people would consider an ideal task for a spreadsheet, I tend to just start practicing my complex data structure skills in Ruby. I guess I'm weird, but I loathe spreadsheets in general. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpBTfKXmAdCy.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, 16 May 2011 17:13:48 -0700, Chip Camden sterl...@camdensoftware.com wrote: I don't use dia very often (it's for diagrams). So maybe gnuplot is an alternative (if we have the same kind of diagrams in mind)? Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. Use openoffice.org-3.0.0-scalc - it's not monolithic, it's a simple single program! :-) I'm not sure in how far the KDE office applications are monolithic or not, maybe if you already have KDE-based programs on your system (or even use KDE as a desktop environment), a look at them may be useful. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Tue, 17 May 2011 01:27:50 -0600, Chad Perrin per...@apotheon.com wrote: On Mon, May 16, 2011 at 05:13:48PM -0700, Chip Camden wrote: Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. When I'm creating something from scratch that some people would consider an ideal task for a spreadsheet, I tend to just start practicing my complex data structure skills in Ruby. I guess I'm weird, but I loathe spreadsheets in general. I've done something similarly insane for a documentation project: Here, the main document was made in LaTeX, and there were CSV (comma seperated values) files with numerical data and text. Those were then processed by awk scripts that did the calculation part; their result were LaTeX includes that were then sourced by \input. Another file was made with definitions of macros that hold intermediate or result values for use inside the text. Additionally, output was given in gnuplot form and then processed by that utility, the result was eps or png graphics also for inclusion in the document. The whole play was controlled by a quite simple Makefile that caused a make call to process the files that had changed. Just imagine: Change a value in a table, run make, and have all the results (tables, figures, mentionings in text) change automatically. The result was a PDF file for sending and for printing. Of course, it is totally insane to do so. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Warren Block on Monday, 16 May 2011: On Mon, 16 May 2011, Chip Camden wrote: Looks like cinepaint doesn't have any GNOME dependencies, and also no HAL dependency. Now if I can just learn how to do everything I know how to do in GIMP, I'll be set for that piece. I don't use dia very often (it's for diagrams). Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. I just submitted ports/157096 with a patch to build gvfs without HAL support: http://www.freebsd.org/cgi/query-pr.cgi?pr=157096 Very lightly tested, but no problems so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Awesome! I'll test it out. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgp7yPJQhKx84.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Warren Block on Monday, 16 May 2011: On Mon, 16 May 2011, Chip Camden wrote: Looks like cinepaint doesn't have any GNOME dependencies, and also no HAL dependency. Now if I can just learn how to do everything I know how to do in GIMP, I'll be set for that piece. I don't use dia very often (it's for diagrams). Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. I just submitted ports/157096 with a patch to build gvfs without HAL support: http://www.freebsd.org/cgi/query-pr.cgi?pr=157096 Very lightly tested, but no problems so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Works for me! So long, HAL! Thanks! -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpXfP8AvbMJo.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
--As of May 16, 2011 10:00:38 AM +0200, Polytropon is alleged to have said: On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. --As for the rest, it is mine. Sure it is: cd /usr/ports/sysutils/hal make deinstall It will list what ports require it. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, 16 May 2011, Daniel Staal wrote: --As of May 16, 2011 10:00:38 AM +0200, Polytropon is alleged to have said: On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. --As for the rest, it is mine. Sure it is: cd /usr/ports/sysutils/hal make deinstall It will list what ports require it. ;) pkg_info -R hal\* will show the same list without actually deinstalling it. But some or most of those don't directly depend on hal, they depend on something else that depends on hal. It would be nice to easily find the root few. xorg-server can be set to not use hal. Then rebuild the keyboard, mouse, and video drivers. One problem with getting rid of hal entirely is libgnomeui, which depends on gvfs, which depends on gnome-mount, which depends on hal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Daniel Staal on Monday, 16 May 2011: --As of May 16, 2011 10:00:38 AM +0200, Polytropon is alleged to have said: On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. --As for the rest, it is mine. Sure it is: cd /usr/ports/sysutils/hal make deinstall It will list what ports require it. ;) Daniel T. Staal A less destructive way to get the same info is pkg_info -R hal-0.5.14_13 and 'portversion -v hal' can be used to get the specific version installed. After some more investigation, it appears that gnome-mount is the culprit. I'm looking into how to exclude that from the consumer apps. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpf42G1aPwb2.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, May 16, 2011 at 4:00 AM, Polytropon free...@edvax.de wrote: On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. Also see ports-mgmt/pkg_tree pkg_tree -v is quite useful. -- Eitan Adler ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Warren Block on Monday, 16 May 2011: On Mon, 16 May 2011, Daniel Staal wrote: --As of May 16, 2011 10:00:38 AM +0200, Polytropon is alleged to have said: On Sun, 15 May 2011 12:18:28 -0700, Chip Camden sterl...@camdensoftware.com wrote: I wish I could figure out what dependency wanted HAL to be installed so I could remove it. I would assume that the HAL dependency may be required by some deeper-inside Gnome part that is used by Gimp, maybe a part of the Gtk+ library... I'm not sure it's trivial to find out which one it is. --As for the rest, it is mine. Sure it is: cd /usr/ports/sysutils/hal make deinstall It will list what ports require it. ;) pkg_info -R hal\* will show the same list without actually deinstalling it. But some or most of those don't directly depend on hal, they depend on something else that depends on hal. It would be nice to easily find the root few. xorg-server can be set to not use hal. Then rebuild the keyboard, mouse, and video drivers. One problem with getting rid of hal entirely is libgnomeui, which depends on gvfs, which depends on gnome-mount, which depends on hal. Yes, that seems to be the sticking point. The only option appears to be doing without gimp, gnumeric, and dia, which all depend upon libgnomeui. Any Gnome-free alternatives out there? -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgp4tuGXDKNgZ.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, 16 May 2011 11:14:49 -0700, Chip Camden sterl...@camdensoftware.com wrote: Quoth Warren Block on Monday, 16 May 2011: One problem with getting rid of hal entirely is libgnomeui, which depends on gvfs, which depends on gnome-mount, which depends on hal. That's what I did assume. Yes, that seems to be the sticking point. The only option appears to be doing without gimp, gnumeric, and dia, which all depend upon libgnomeui. Any Gnome-free alternatives out there? Let's see: Gimp - Krita (KDE) or InkScape? Gnumeric - KOffice (if you're already on KDE), OpenOffice, LibreOffice, StarOffice (or add any other possible *Office to the mix). And dia... I have to admit that I don't know what this is. :-) Maybe, just MAYBE, the gnome-mount dependency can be installed without requiring HAL. I don't know much about the details, but HAL has been said to be the means for automounting local media, and maybe is in conjuction with Samba. If you can disable such functionality via make config for the gnome-mount port, MAYBE there is a chance to avoid HAL in this specific case. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, 16 May 2011, Polytropon wrote: Maybe, just MAYBE, the gnome-mount dependency can be installed without requiring HAL. I don't know much about the details, but HAL has been said to be the means for automounting local media, and maybe is in conjuction with Samba. If you can disable such functionality via make config for the gnome-mount port, MAYBE there is a chance to avoid HAL in this specific case. gnome-mount is specifically for hal. OTOH, the Linux guys have been working on removing hal, and gvfs has a promising --disable-hal option I'm testing now. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, May 16, 2011 at 11:14:49AM -0700, Chip Camden wrote: Yes, that seems to be the sticking point. The only option appears to be doing without gimp, gnumeric, and dia, which all depend upon libgnomeui. Any Gnome-free alternatives out there? I don't use anything like gnumeric or dia, generally, but an alternative to GIMP is Cinepaint. I don't *think* it requires libgnomeui. It has some, err, quirks, but they're trade-offs rather than pure negatives, because Cinepaint does a number of things better than the GIMP. Among the things it does better are start and operate quickly; where the GIMP often takes an interminably long time to do simple things (like open an image), Cinepaint is pretty snappy by comparison. The interface is occasionally a bit glitchy, though. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpB61va1wts8.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Chad Perrin on Monday, 16 May 2011: On Mon, May 16, 2011 at 11:14:49AM -0700, Chip Camden wrote: Yes, that seems to be the sticking point. The only option appears to be doing without gimp, gnumeric, and dia, which all depend upon libgnomeui. Any Gnome-free alternatives out there? I don't use anything like gnumeric or dia, generally, but an alternative to GIMP is Cinepaint. I don't *think* it requires libgnomeui. It has some, err, quirks, but they're trade-offs rather than pure negatives, because Cinepaint does a number of things better than the GIMP. Among the things it does better are start and operate quickly; where the GIMP often takes an interminably long time to do simple things (like open an image), Cinepaint is pretty snappy by comparison. The interface is occasionally a bit glitchy, though. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Thanks, I'll take a look at it! -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpm495pJxv5U.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Chad Perrin on Monday, 16 May 2011: On Mon, May 16, 2011 at 11:14:49AM -0700, Chip Camden wrote: Yes, that seems to be the sticking point. The only option appears to be doing without gimp, gnumeric, and dia, which all depend upon libgnomeui. Any Gnome-free alternatives out there? I don't use anything like gnumeric or dia, generally, but an alternative to GIMP is Cinepaint. I don't *think* it requires libgnomeui. It has some, err, quirks, but they're trade-offs rather than pure negatives, because Cinepaint does a number of things better than the GIMP. Among the things it does better are start and operate quickly; where the GIMP often takes an interminably long time to do simple things (like open an image), Cinepaint is pretty snappy by comparison. The interface is occasionally a bit glitchy, though. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] Looks like cinepaint doesn't have any GNOME dependencies, and also no HAL dependency. Now if I can just learn how to do everything I know how to do in GIMP, I'll be set for that piece. I don't use dia very often (it's for diagrams). Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. Thanks to everyone who has responded so far. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgphgMl5hh0ad.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Mon, 16 May 2011, Chip Camden wrote: Looks like cinepaint doesn't have any GNOME dependencies, and also no HAL dependency. Now if I can just learn how to do everything I know how to do in GIMP, I'll be set for that piece. I don't use dia very often (it's for diagrams). Gnumeric I use more frequently (for spreadsheets). I hate having to start up that monolithic libreoffice just to do a spreadsheet, but that would be a HAL-free alternative. I just submitted ports/157096 with a patch to build gvfs without HAL support: http://www.freebsd.org/cgi/query-pr.cgi?pr=157096 Very lightly tested, but no problems so far. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Please allow me a technical sidenote: On Sat, 14 May 2011 20:53:27 -0700 (PDT), Rob Clark rpcl...@ymail.com wrote: Trying the obvious first, I unplugged the keyboard and plugged it back in the ps2 port, and keyboard worked immediately -- this was repeatable. Do _NOT_ hotplug the PS/2 port! It's not capable of that! I've seen myself in the past that trying so caused a mainboard to fly into the garbage can - as hotplugging the keyboard seemed to have damaged the PS/2 port (it didn't work anymore, with no keyboard). However, you actually CAN do this with USB. And I've done hotplugging with an old AT (big 5 pin keyboard connector) and HIL connect/disconnect at the keyboard (!) without any problem (IBM model M, the famous one). Some digging around revealed that I had the following line in /etc/rc.conf twice: moused_enable=YES This doesn't matter: /etc/rc.conf is a shell script included in system scripts that does just contain variables that are set. Compare the following: x = 3; x = 3; What does happen? Or even this: x = 3; x = 4; You can have the same line 100 times in this file, with the result that the _last_ setting will be used. See man rc.conf for details. I removed one of these (which I guess was the culprit) and left one as it should have been, then all was well. So _that_ is very strange, if one has the functionality of /etc/rc, rc.conf, and the rc.d/ scripts in mind... having a line twice in the config file does _not_ imply a service is started twice. I have no idea why I had moused_enable=YES in there twice, whether it was from an old or recent rc.conf edit, but it clearly seems to have been causing the issue. Coincidence, covariation, correlation...? :-) Other (maybe valuable) info: I am running hald in /etc/rc.conf as follows: dbus_enable=YES hald_enable=YES ...and these were there prior to the ports update. I figured this issue may be of some value since I did not do any src updates. While moused is part of the base system (updated per source or freebsd-update), dbus and hal are ports (job for portmaster). -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
On Sat, 14 May 2011, Rob Clark wrote: After restarting X, prior to any reboot, I lost the mouse in X. So I figured a reboot was in order. This is almost certainly HAL. If you do not know you need HAL for something, mark the hal and hal-info ports FORBIDDEN (set FORBIDDEN to any value in the Makefiles) whenever you update your ports tree. Grep /var/db/ports for hal and then remove the with hal option in the affected ports using make config. Force reinstall the affected ports. Try to pkg_delete hal, to check for dependencies you haven't resolved. When all the dependencies are removed, then remove hal. Some digging around revealed that I had the following line in /etc/rc.conf twice: moused_enable=YES I removed one of these (which I guess was the culprit) and left one as it should have been, then all was well. Keyboard found at reboot, no further issues -- mouse was available in X too. I have no idea why I had moused_enable=YES in there twice, whether it was from an old or recent rc.conf edit, but it clearly seems to have been causing the issue. This cannot be. Once or a million times should have exactly the same effect. Commonly ports, people, and sysinstall just add stuff to the end of this file. They add everything they know they need because only the last of similar entries has effect. rc.conf can become unwieldly over time because of this. It is safe to delete duplicate entries, but that should not affect the result. When the same value is assigned differing values only the last is effective. The defaults are in /etc/defaults/rc.conf which should never be edited. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Quoth Lars Eighner on Sunday, 15 May 2011: On Sat, 14 May 2011, Rob Clark wrote: After restarting X, prior to any reboot, I lost the mouse in X. So I figured a reboot was in order. This is almost certainly HAL. If you do not know you need HAL for something, mark the hal and hal-info ports FORBIDDEN (set FORBIDDEN to any value in the Makefiles) whenever you update your ports tree. Grep /var/db/ports for hal and then remove the with hal option in the affected ports using make config. Force reinstall the affected ports. Try to pkg_delete hal, to check for dependencies you haven't resolved. When all the dependencies are removed, then remove hal. That's some good advice. I was able to remove hal using this approach, but only after removing firefox, gimp, gnumeric, dia and several others. When I reinstalled firefox, it didn't need HAL -- but when I reinstalled gimp the first thing it did was build HAL. I didn't find HAL in any of gimp's options, and I have WITHOUT_HAL=YES in /etc/make.conf. The HAL daemon hald isn't running, and gimp seems to work. I wish I could figure out what dependency wanted HAL to be installed so I could remove it. -- .O. | Sterling (Chip) Camden | http://camdensoftware.com ..O | sterl...@camdensoftware.com | http://chipsquips.com OOO | 2048R/D6DBAF91 | http://chipstips.com pgpxOEZd2EVGz.pgp Description: PGP signature
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Polytropon free...@edvax.de wrote: Do _NOT_ hotplug the PS/2 port! It's not capable of that! I've seen myself in the past that trying so caused a mainboard to fly into the garbage can - as hotplugging the keyboard seemed to have damaged the PS/2 port (it didn't work anymore, with no keyboard). This is conventional wisdom, and I believed it until I came across, as an enclosure with a Belkin F8E206c PS/2 keyboard that had 3 extra keys*, specific instructions to unplug the keyboard, wait 5 seconds, and replug it to get past a BIOS incompatibility on some Intel boards using the SE440BX-2 chipset. (The next step was to upgrade the BIOS, but the hotplug exercise was necessary to get to the point of being _able_ to upgrade the BIOS.) * Power, Sleep, WakeUp; presumably intended for ACPI or APM. However, you actually CAN do this with USB. Yes, USB was designed to be hot-pluggable. And I've done hotplugging with an old AT (big 5 pin keyboard connector) and HIL connect/disconnect at the keyboard (!) without any problem (IBM model M, the famous one). The AT and PS/2 keyboard interfaces are electrically identical -- only the physical connector is different. (I have seen, and used, adapters to connect either type of keyboard to the other type of system. Such adapters have no active components, just the two connectors wired together.) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
--As of May 15, 2011 8:03:29 PM -0700, per...@pluto.rain.com is alleged to have said: The AT and PS/2 keyboard interfaces are electrically identical -- only the physical connector is different. (I have seen, and used, adapters to connect either type of keyboard to the other type of system. Such adapters have no active components, just the two connectors wired together.) --As for the rest, it is mine. The physical connector is all that actually needs to be different: Hot-swap interfaces make a point of connecting ground before power, usually be longer ground pins. Although I don't think it matters in this case. I could check, but I'd have to unplug my keyboard from the computer I'm on. ;) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: No keyboard after ports update, 2x moused_enable=YES culprit
Daniel Staal dst...@usa.net wrote: --As of May 15, 2011 8:03:29 PM -0700, per...@pluto.rain.com is alleged to have said: The AT and PS/2 keyboard interfaces are electrically identical -- only the physical connector is different. --As for the rest, it is mine. The physical connector is all that actually needs to be different: Hot-swap interfaces make a point of connecting ground before power, usually be longer ground pins. The PS/2 should qualify on this point, provided it is wired _correctly_ (with the connector shell grounded both on the motherboard and in the cable). I'm less sure about the AT, which used a 5-pin DIN plug that may not even have had a shell-ground on the motherboard -- we were less concerned about generating RFI in those days. IIRC all 5 pins were the same length. It's possible this particular Belkin keyboard used longer pins for power and ground than for signal, so as to be safely hot-pluggable even if the motherboard didn't ground the connector shell. However, I've since gotten by with hot-plugging a PS/2 trackball on the same machine a couple of times, to clear lockups. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
No keyboard after ports update, 2x moused_enable=YES culprit
System Info: 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Tue Aug 10 11:43:36 EDT 2010, and xorg-server-1.7.7_1,1 X.Org X server and related programs Not having updated my ports in nearly 1 year, I did a sledgehammer approach with portmaster as follows: portmaster -D -R -f -m BATCH=yes -a This took a few rounds. I did this as I started having all sorts of issues after running down various port problems when going through a rather long /usr/ports/UPDATING. Maybe not the best method, but I think everything is finally done. After restarting X, prior to any reboot, I lost the mouse in X. So I figured a reboot was in order. Issue: After a reboot I found I had no keyboard -- not even in console mode. Trying the obvious first, I unplugged the keyboard and plugged it back in the ps2 port, and keyboard worked immediately -- this was repeatable. Reboot, same thing, no keyboard. Some digging around revealed that I had the following line in /etc/rc.conf twice: moused_enable=YES I removed one of these (which I guess was the culprit) and left one as it should have been, then all was well. Keyboard found at reboot, no further issues -- mouse was available in X too. I have no idea why I had moused_enable=YES in there twice, whether it was from an old or recent rc.conf edit, but it clearly seems to have been causing the issue. Other (maybe valuable) info: I am running hald in /etc/rc.conf as follows: dbus_enable=YES hald_enable=YES ...and these were there prior to the ports update. I figured this issue may be of some value since I did not do any src updates. I'll be glad to try to help or test this further, but keep in mind I'm not a coder. Thanks, Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On 11-04-09 17:17, Warren Block wrote: On Fri, 8 Apr 2011, Sascha Vieweg wrote: As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on the normal (startup) console: (1) use my apple keyboard, especially, scroll through console output man syscons | less -p'Back Scrolling' ... Says: press the `slock' key (with some PC keyboard description). However, I have got a MB Pro where no such key is available. Thus, I may repeat my question: How can I get console scolling working on my MacBook Pro 13''? (2) have a screen resolution of at least 800x600. vidcontrol(1) can set different modes, potentially including VESA_800x600. What's available depends on the video card BIOS and you'll probably have to build a kernel with SC_PIXEL_MODE. Both things seem to be no particular problem in X11, however, I cannot find advices for the normal console. Unless you're trying to emulate a machine without X11 for a particular purpose, xterms are more versatile than consoles. It's probably possible to get a console-like stack of fullscreen xterms with one of the mouseless window managers. Thanks, the vidcontrol tip helped a lot. *S* -- Sascha Vieweg, saschav...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On Apr 18, 2011, at 11:35 AM, Sascha Vieweg wrote: man syscons | less -p'Back Scrolling' ... Says: press the `slock' key (with some PC keyboard description). However, I have got a MB Pro where no such key is available. Thus, I may repeat my question: How can I get console scolling working on my MacBook Pro 13''? slock is the key above the home key; on an Apple A1048 USB keyboard, that is labelled F15. I don't think the 13 Macbook Pro has that key available, so you might have to attach an external USB keyboard. Try dmesg | less instead, or using SSH from a handy terminal emulator with scrolling windows (like Terminal.app from the base MacOS X) is likely to be easier... Regards, -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On Apr 18, 2011, at 2:45 PM, Chuck Swiger wrote: On Apr 18, 2011, at 11:35 AM, Sascha Vieweg wrote: man syscons | less -p'Back Scrolling' ... Says: press the `slock' key (with some PC keyboard description). However, I have got a MB Pro where no such key is available. Thus, I may repeat my question: How can I get console scolling working on my MacBook Pro 13''? slock is the key above the home key; on an Apple A1048 USB keyboard, that is labelled F15. I don't think the 13 Macbook Pro has that key available, so you might have to attach an external USB keyboard. fn-shift-f12 should be scroll lock. At least, it is when the hardware runs windows___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On Fri, 8 Apr 2011, Sascha Vieweg wrote: As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on the normal (startup) console: (1) use my apple keyboard, especially, scroll through console output man syscons | less -p'Back Scrolling' (2) have a screen resolution of at least 800x600. vidcontrol(1) can set different modes, potentially including VESA_800x600. What's available depends on the video card BIOS and you'll probably have to build a kernel with SC_PIXEL_MODE. Both things seem to be no particular problem in X11, however, I cannot find advices for the normal console. Unless you're trying to emulate a machine without X11 for a particular purpose, xterms are more versatile than consoles. It's probably possible to get a console-like stack of fullscreen xterms with one of the mouseless window managers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD VMWare Mac screen resulution and keyboard map
As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on the normal (startup) console: (1) use my apple keyboard, especially, scroll through console output (2) have a screen resolution of at least 800x600. Both things seem to be no particular problem in X11, however, I cannot find advices for the normal console. And: does anybody know what vertical and horizontal refresh rates my VMWare display have? According to the user handbook I need to specify this information in the X11 config file -- the current X11 display does not look very sharp. Thanks for help *S* -- Sascha Vieweg, saschav...@gmail.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On Apr 8, 2011, at 12:22 PM, Sascha Vieweg wrote: As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on the normal (startup) console: (1) use my apple keyboard, especially, scroll through console output (2) have a screen resolution of at least 800x600. Both things seem to be no particular problem in X11, however, I cannot find advices for the normal console. And: does anybody know what vertical and horizontal refresh rates my VMWare display have? According to the user handbook I need to specify this information in the X11 config file -- the current X11 display does not look very sharp. Thanks for help *S* You should be able find the screen dimensions for that MacBook Pro somewhere on the net. If my memory is correct and it's like my 13 acrylic MacBook then it will be something either 1280x800 or, less likely, 1280x720. I'm really old so I use an config file in the standard location: /etc/X11/xorg.conf configuration file to control X. If I understand correctly this is not longer strictly necessary. You can generate a base config by running: # X -configure That will write a file: xorg.conf.new into the current directory. For monitor setting I've never found anything on VMware Fusion, or the MacBook line that gives those numbers. I've been using: Section Monitor Identifier Apple MacBook Pro A1286 Display VendorName Apple HorizSync 27.0-86.0 VertRefresh 50.0-72.0 Modeline 1440x900 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync Modeline 1280x800 83.46 1280 1344 1480 1680 800 801 804 828 EndSection I'm using the Vesa Driver rather than the native vmware one so I'm pretty sure that the MacBook is actually handling the display settings. Again, there are instructions on the net for hacking xorg.conf specifically for VMWare Fusion and or Parallels to get a crisp display on a FreeBSD VM on a Mac. - I haven't found a way to map a key to Scroll Lock. I would imagine that the syscons driver is the place to look. -- Chris There will be an answer, Let it be. e: chris -at- vindaloo -dot- com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD VMWare Mac screen resulution and keyboard map
On Apr 8, 2011, at 12:22 PM, Sascha Vieweg wrote: As a curious beginner I am running FreeBSD on VMWare Fusion 3.1.2 on a MacBook Pro 13'' i5, and I want to do two things on the normal (startup) console: (1) use my apple keyboard, especially, scroll through console output The Apple Keyboard should just work. The FreeBSD console has a special mode where you can scroll back and forth in console output after hitting Scroll Lock. I'm just not sure what key on the Apple Keyboard VMware maps to Scroll Lock. (2) have a screen resolution of at least 800x600. To start, the X log file: /var/log/Xorg.0.log file is a good source of information about what X is doing if you are trying to tune things. Getting a good screen resolution should just be a matter of setting the refresh rates to match your monitor. You may be able to put any values you like in there since your screen and video adapter are virtual. All of this gets configured in /etc/X11/xorg.conf. I believe it's considered gauche to hand configure this anymore but since many modern displays, the Apple laptops included, don't conform to the VESA standard modes it's helpful to be able to tune things by hand. The problem is compounded by the fact that again, in VMware you probably aren't talking to the real hardware. Any modern hardware should just tell the X server what it's Sync and Refresh rates are. One final tip: Check the amount of VideoRam that VMware assigned to the virtual machine. I noticed that it was a little skint at 2Mb or something and I bumped it up to something larger than 8Mbso I could have a 1920x1080x24bpp display. Here's my xorg.conf file which I started on an Acrylic MacBook running Parallels and them moved to and retuned for a unibody 15 MacBook Pro. I'm following up my first post since I revisited this file this afternoon to fix a couple of issues that I had worked around. My box is FreeBSD 8.2-STABLE built from sources on 4/6/2011. I'm running xorg-7.5.1 from ports Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files ModulePath /usr/local/lib/xorg/modules FontPath /usr/local/lib/X11/fonts/misc/ FontPath /usr/local/lib/X11/fonts/TTF/ FontPath /usr/local/lib/X11/fonts/OTF FontPath /usr/local/lib/X11/fonts/Type1/ FontPath /usr/local/lib/X11/fonts/100dpi/ FontPath /usr/local/lib/X11/fonts/75dpi/ EndSection Section Module Load extmod Load record Load dbe Load glx Load dri Load dri2 Load vmmouse EndSection Section InputDevice Identifier Keyboard0 Driver kbd EndSection Section InputDevice Identifier Mouse0 Driver vmmouse Option Protocol auto Option Device /dev/sysmouse Option ZAxisMapping 4 5 6 7 EndSection Section Monitor Identifier Apple MacBook Pro A1286 Display VendorName Apple HorizSync 27.0-86.0 ## These shouldn't matter VertRefresh 50.0-72.0 ## ## 15 MacBook Pro Modeline 1440x900 106.47 1440 1520 1672 1904 900 901 904 932 -HSync +Vsync ## 13 MacBook and possibly 13 MacBook Pro Modeline 1280x800 83.46 1280 1344 1480 1680 800 801 804 828 EndSection Section Device Identifier VMware Legacy Emulated SVGA II Adapter Driver vmwlegacy VendorName VMware BoardName Legacy Emulated SVGA II Adapter BusID PCI:0:15:0 EndSection Section Screen Identifier Screen0 Device VMware Legacy Emulated SVGA II Adapter MonitorApple MacBook Pro A1286 Display ## Purge the display modes that I don't need from here. SubSection Display Viewport0 0 Depth 24 Modes 1440x900 ## 15 MacBook Pro Modes 1280x800 ## 13 MacBook/MacBook Pro EndSubSection EndSection -- Chris -- __o Chris Hilton _`\,_e: chris /at/ vindaloo /dot/ com __(*)/_(*) All I was doing was trying to get home from work. -Rosa Parks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
keyboard click driver:: User-side.
Guys, I have been interested in having a FreeBSD version of the SunOS click utility for decades. --I first discovered that my Sun 3/80 let the keys sound a brief click sound, much softer than ye-olden IBM Selectrics, around 1988-9. I do need the audio feedback. The folks in the wizard sector at Ubuntu turned me onto a python script of about 30 pages of code called keymon.py written by a Scott Kirkwood. The present keymon displays certain graphics when certain keys are hit. Scott does think that his script can include the click sound that I have. My program is in C, it opens the /dev/dsp and output a click via click.h. I am learning python and find it pretty straightforward. I think using Scott's keyboard program with mine can allow me to do just what I want. On the user-side, have clicky keys where necessary. This feedback would help folks using the severely cheep keyboards that are on the notebook class as well as even cheaper laptops for children whose keyboards are nothing put cardboard wrapped in plastic. Typing on a _real_ keyboard can be satisfactory. But when you try it on one of these crappy types, forget it. Just doing several random tests, my fingers do not connect with more than 60-65% of the keys on my EEE-900A. bEcause my shoulder is partly out of socket i can only type so much, so the more people who can check out keymon.py and let me know if it is worth porting to FBSD, the better. Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 7.98a release of Jottings: http://jottings.thought.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
terminal emulators with secure keyboard capability
For those who aren't aware, XTerm offers a pretty nifty security feature, particular for cases of entering passwords. If you hold down the Ctrl key and the left left mouse button, a menu appears; the second item down is Secure Keyboard. From the XTerm manpage: The Secure Keyboard mode is helpful when typing in passwords or other sensitive data in an unsecure environment; see SECURITY below (but read the limitations carefully). I recommend anyone interested in this feature read the SECURITY section of the xterm(1) manpage, of course. I won't copy all the relevant text here. Let it suffice to say, in summary, that Secure Keyboard mode in XTerm attempts to ensure that all keyboard input is directed only to xterm (using the GrabKeyboard protocol request). I have yet to notice any other terminal emulator with a similar keyboard input protection mode. Does anyone here know of any such terminal emulators, aside from XTerm, that do something like this? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] pgpgOnCBREKKX.pgp Description: PGP signature
Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/19/11 09:35, Jan Henrik Sylvester wrote: On 01/-10/-28163 20:59, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers? Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! I have 8.1-RELEASE running on an Optiplex 980 with no keyboard problems, but not with a Dell keyboard as we ordered Cherry keyboards with our Dells (the person evaluating the Dells thought the keyboard was way too light and fragile). Since I usually have the keyboard plugged into the hub in the display, I just tried it directly in the (rear) usb ports with no difference. Trying the Fujitsu and Sun keyboards from the other machines in my office does not immediately lead to problems, either. (Or how much would I have to type to reproduce the problem?) Maybe it is just the keyboards? Or a bios setting? (I cannot currently reboot to check if there are any keyboard related bios settings I changed.) Based on this post, I switched my keyboard so that it runs through the hub in my monitor. It seems to have fixed the problem, as I haven't seen the keyboard repeat in almost a day. I'm still curious as to what the actual problem is. Maybe the fact that running it through a hub first will help to narrow down the issue. Thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/19/11 08:48, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! I forgot to attach my dmesg - here it is! Copyright (c) 1992-2011 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.2-RC2 #1: Mon Jan 17 12:10:53 EST 2011 root@galvatron:/usr/obj/usr/src/sys/GENERIC amd64 Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2660.02-MHz K8-class CPU) Origin = GenuineIntel Id = 0x106e5 Family = 6 Model = 1e Stepping = 5 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x98e3fdSSE3,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 4082315264 (3893 MB) ACPI APIC Table: DELL B11K FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0: Changing APIC ID to 8 ioapic0 Version 2.0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger kbd1 at kbdmux0 acpi0: DELL B11Kon motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 acpi_button0: Power Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: PCI-PCI bridge irq 16 at device 3.0 on pci0 pci1: PCI bus on pcib1 vgapci0: VGA-compatible display port 0xdc80-0xdcff mem 0xf600-0xf6ff,0xe000-0xefff,0xf000-0xf1ff irq 16 at device 0.0 on pci1 nvidia0: GeForce GT 330 on vgapci0 vgapci0: child nvidia0 requested pci_enable_busmaster vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io nvidia0: [ITHREAD] hdac0: NVidia (Unknown) High Definition Audio Controller mem 0xf7dfc000-0xf7df irq 17 at device 0.1 on pci1 hdac0: HDA Driver Revision: 20100226_0142 hdac0: [ITHREAD] pci0: base peripheral at device 8.0 (no driver attached) pci0: base peripheral at device 8.1 (no driver attached) pci0: base peripheral at device 8.2 (no driver attached) pci0: base peripheral at device 16.0 (no driver attached) pci0
Re: Keyboard repeat issues with Dell Optiplex 980s
On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/-10/-28163 20:59, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers? Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! I have 8.1-RELEASE running on an Optiplex 980 with no keyboard problems, but not with a Dell keyboard as we ordered Cherry keyboards with our Dells (the person evaluating the Dells thought the keyboard was way too light and fragile). Since I usually have the keyboard plugged into the hub in the display, I just tried it directly in the (rear) usb ports with no difference. Trying the Fujitsu and Sun keyboards from the other machines in my office does not immediately lead to problems, either. (Or how much would I have to type to reproduce the problem?) Maybe it is just the keyboards? Or a bios setting? (I cannot currently reboot to check if there are any keyboard related bios settings I changed.) Cheers, Jan Henrik ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/19/11 09:35, Jan Henrik Sylvester wrote: On 01/-10/-28163 20:59, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers? Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! I have 8.1-RELEASE running on an Optiplex 980 with no keyboard problems, but not with a Dell keyboard as we ordered Cherry keyboards with our Dells (the person evaluating the Dells thought the keyboard was way too light and fragile). Since I usually have the keyboard plugged into the hub in the display, I just tried it directly in the (rear) usb ports with no difference. Trying the Fujitsu and Sun keyboards from the other machines in my office does not immediately lead to problems, either. (Or how much would I have to type to reproduce the problem?) Maybe it is just the keyboards? Or a bios setting? (I cannot currently reboot to check if there are any keyboard related bios settings I changed.) We have the keyboards plugged into the rear ports, and not via a USB hub. The problem is not immediate or constant, but if you spend about two hours with the keyboard hooked up to the rear, you will certainly run into the problem (assuming its not related to these Dell keyboards...). As for a BIOS setting, there is nothing relevant in the BIOS with regards to the keyboard or USB emulation that I can remember. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard repeat issues with Dell Optiplex 980s
On 01/19/11 08:48, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! The problem still exists with the kbdmux.0.disabled hint. It definitely took effect, as there is no longer a /dev/kbdmux0, and dmesg lists the refusal to register the kbdmux module. Any other ideas? We've tried playing with the hw.usb.ehci.lostinrbug and hw.usb.ehci.no_hs sysctls, but they don't make a difference either. Looking at the ehci(4) man page, this sticks out at me: BUGS The driver is not finished and is quite buggy. There is currently no support for isochronous transfers. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard repeat issues with Dell Optiplex 980s
On Wednesday 19 January 2011 15:51:41 Steve Polyack wrote: On 01/19/11 08:48, Steve Polyack wrote: On 1/18/2011 5:56 PM, Jeremy Chadwick wrote: On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. The keyboard is also a Dell model - model KB1421, or listed as Dell QuiteKey Keyboard under dmesg. The same keyboard does not exhibit the strange behavior when used with the older model of tower (Optiplex 960). I'll reboot today with the loader.conf hint you provided. I'll let you guys know if it helps. Thanks! The problem still exists with the kbdmux.0.disabled hint. It definitely took effect, as there is no longer a /dev/kbdmux0, and dmesg lists the refusal to register the kbdmux module. Any other ideas? We've tried playing with the hw.usb.ehci.lostinrbug and hw.usb.ehci.no_hs sysctls, but they don't make a difference either. Looking at the ehci(4) man page, this sticks out at me: BUGS The driver is not finished and is quite buggy. There is currently no support for isochronous transfers. For FreeBSD 8+ this is not true. Probably the manpage has not been updated. Hence you are seeing a different number of UHCI controllers, this looks like an ACPI problem. USB keyboards usually require a UHCI to enumerate. The EHCI can only enumerate High Speed devices. --HPS ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Keyboard repeat issues with Dell Optiplex 980s
We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Thanks, Steve Polyack ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Keyboard repeat issues with Dell Optiplex 980s
On Tue, Jan 18, 2011 at 04:40:13PM -0500, Steve Polyack wrote: We've recently upgraded a few desktop workstations from Dell Optiplex 960s to Optiplex 980s. We were running FreeBSD 8.1-RELEASE. The migration was performed by simply swapping the drives into the new systems. Immediately after switching people over, they all began to report bizarre keyboard issues - things like infinite key repeats (letters, numbers, enter) for keys they did not hold down. The key repeats continue indefinitely until another key is pressed. Occasionally, even mouse input will trigger similar infinite keyboard input repetition. In addition to the repeat issue, sometimes physical key-presses are not registered by FreeBSD, leading to typos and angry developers. We've tried doing fresh installs of FreeBSD 8.2-RC2 on two of these systems, and the issue persists. Because of the observed behavior, I'm thinking that this is due to new hardware in the 980s which isn't timing or handling interrupts correctly under the FreeBSD kernel. Looking at a 'pciconf -lvb' from each system, I noticed that the 980 has two USB controllers which probe under ehci(4), while the 960 (which does not exhibit this problem), enumerates six uhci(4) controllers and two ehci(4) controllers. To cut to the chase here, the 960 users' keyboards probe under a USB1.0 uhci(4), while the 980s only have ehci(4) devices to attach to. So, I guess what I'm asking is - has anyone else seen any keyboard repeat or other USB craziness with ehci(4) ports or otherwise Intel PCH controllers?Any fellow Optiplex 980 users? I'd be more than happy to provide pciconf or other output if requested. Try adding the following to /boot/loader.conf then reboot and see if the excessive repeat behaviour changes: hint.kbdmux.0.disabled=1 It would also help if you would state exactly what brand/model of keyboard is used. Yes, believe it or not, it matters. dmesg output would be helpful in this case. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
How to fix the keyboard dead question ?
Sometimes after booting freebsd and reaching the slim login screen, i cannot input anything: the keyboard seems to be dead. Then i have to reboot freebsd and the problem disappear ! uname -a FreeBSD mybsd.zsoft.com 8.1-RELEASE FreeBSD 8.1-RELEASE #1: Wed Sep 8 09:07:54 CST 2010 r...@mybsd.zsoft.com:/media/G/usr/obj/media/G/usr/src/sys/MYKERNEL i386 dmesg -a | grep -i fail acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3fde (3) failed dmesg -a | grep -i warn ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x 0 0/0x1 (20100331/tbfadt-655) Sincerely! - e^(π⋅i) + 1 = 0 -- View this message in context: http://old.nabble.com/How-to-fix-the-%22keyboard-dead%22-question---tp29734114p29734114.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to fix the keyboard dead question ?
On Thu, 16 Sep 2010 16:51:31 -0700 (PDT), zaxis z_a...@163.com wrote: Sometimes after booting freebsd and reaching the slim login screen, i cannot input anything: the keyboard seems to be dead. Then i have to reboot freebsd and the problem disappear ! Is this an AT or USB keyboard? If it is a USB keyboard: I have similar problems on FreeBSD 7 (didn't have them before on 5) where the activation of the USB keyboard sometimes takes up to 2 minutes after system boot is complete. Detaching and re-attaching the USB plug sometimes helps. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to fix the keyboard dead question ?
I've had similar results on my USB to PS/2 keyboard adapter. If I reconnect the bridge device (not necc. have the KB attached to it) it will work. On Sep 16, 2010, at 8:08 PM, Polytropon wrote: On Thu, 16 Sep 2010 16:51:31 -0700 (PDT), zaxis z_a...@163.com wrote: Sometimes after booting freebsd and reaching the slim login screen, i cannot input anything: the keyboard seems to be dead. Then i have to reboot freebsd and the problem disappear ! Is this an AT or USB keyboard? If it is a USB keyboard: I have similar problems on FreeBSD 7 (didn't have them before on 5) where the activation of the USB keyboard sometimes takes up to 2 minutes after system boot is complete. Detaching and re-attaching the USB plug sometimes helps. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
On 2010-08-30 21:02, Bernt Hansson wrote: Put this in your .xinitrc setxkbmap se Thanks for the suggestion! I wonder, is this metod the correct way. According to the handbook one should use the /usr/local/etc/hal/fdi/policy/x11-input.fdi file. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
2010-08-31 10:29, Leslie Jensen skrev: On 2010-08-30 21:02, Bernt Hansson wrote: Put this in your .xinitrc setxkbmap se Thanks for the suggestion! I wonder, is this metod the correct way. I think so, as long X is concerned. According to the handbook one should use the /usr/local/etc/hal/fdi/policy/x11-input.fdi file. There are no *.fdi files on this machine, and I don't feel like fiddling with hal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
On Tue, 31 Aug 2010 12:38:57 +0200 Bernt Hansson be...@bah.homeip.net articulated: 2010-08-31 10:29, Leslie Jensen skrev: On 2010-08-30 21:02, Bernt Hansson wrote: Put this in your .xinitrc setxkbmap se Thanks for the suggestion! I wonder, is this metod the correct way. I think so, as long X is concerned. According to the handbook one should use the /usr/local/etc/hal/fdi/policy/x11-input.fdi file. There are no *.fdi files on this machine, and I don't feel like fiddling with hal. No one in their right mind likes messing with hal. HAL is now (at least on other OSs) deprecated, since it has become a large monolithic unmaintainable mess, and also duplicates a lot of functionality which are nowadays provided by udev and the kernel itself. Hopefully, FreeBSD will soon free itself from its clutches. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Take Care of the Molehills, and the Mountains Will Take Care of Themselves. Motto of the Federal Civil Service ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
On 2010-08-31 12:38, Bernt Hansson wrote: 2010-08-31 10:29, Leslie Jensen skrev: On 2010-08-30 21:02, Bernt Hansson wrote: Put this in your .xinitrc setxkbmap se Thanks for the suggestion! I wonder, is this metod the correct way. I think so, as long X is concerned. According to the handbook one should use the /usr/local/etc/hal/fdi/policy/x11-input.fdi file. There are no *.fdi files on this machine, and I don't feel like fiddling with hal. OK, thank you. /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
Hello After upgrading to xorg-7.5 on 8.1-RELEASE I've got a problem with X not reading my /usr/local/etc/hal/fdi/policy/x11-input.fdi --- ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp /merge merge key=input.x11_options.XkbModel type=stringlogiitc/merge merge key=input.x11_options.XkbLayout type=stringse/merge /match /device /deviceinfo So I get a US keyboard layout instead of SE. My /var/log/Xorg.0.log (II) config/hal: Adding input device AT Keyboard (II) LoadModule: kbd (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so (II) Module kbd: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) AT Keyboard: always reports core events (**) Option Protocol standard (**) AT Keyboard: Protocol: standard (**) Option XkbRules base (**) AT Keyboard: XkbRules: base (**) Option XkbModel pc105 (**) AT Keyboard: XkbModel: pc105 (**) Option XkbLayout us (**) AT Keyboard: XkbLayout: us (**) Option CustomKeycodes off (**) AT Keyboard: CustomKeycodes disabled (II) XINPUT: Adding extended input device AT Keyboard (type: KEYBOARD) (II) 3rd Button detected: disabling emulate3Button I've checked permissions and file content from a machine running 8.0-RELEASE with xorg-7.4_3 and they are the same. Any suggestions on how to fix this? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Cleaned out /usr/local when reinstalling ports, now keyboard in X is not localized
Put this in your .xinitrc setxkbmap se 2010-08-30 15:06, Leslie Jensen skrev: Hello After upgrading to xorg-7.5 on 8.1-RELEASE I've got a problem with X not reading my /usr/local/etc/hal/fdi/policy/x11-input.fdi --- ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.capabilities contains=input.keyboard merge key=input.x11_options.XkbOptions type=stringterminate:ctrl_alt_bksp /merge merge key=input.x11_options.XkbModel type=stringlogiitc/merge merge key=input.x11_options.XkbLayout type=stringse/merge /match /device /deviceinfo So I get a US keyboard layout instead of SE. My /var/log/Xorg.0.log (II) config/hal: Adding input device AT Keyboard (II) LoadModule: kbd (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so (II) Module kbd: vendor=X.Org Foundation compiled for 1.7.5, module version = 1.4.0 Module class: X.Org XInput Driver ABI class: X.Org XInput driver, version 7.0 (**) AT Keyboard: always reports core events (**) Option Protocol standard (**) AT Keyboard: Protocol: standard (**) Option XkbRules base (**) AT Keyboard: XkbRules: base (**) Option XkbModel pc105 (**) AT Keyboard: XkbModel: pc105 (**) Option XkbLayout us (**) AT Keyboard: XkbLayout: us (**) Option CustomKeycodes off (**) AT Keyboard: CustomKeycodes disabled (II) XINPUT: Adding extended input device AT Keyboard (type: KEYBOARD) (II) 3rd Button detected: disabling emulate3Button I've checked permissions and file content from a machine running 8.0-RELEASE with xorg-7.4_3 and they are the same. Any suggestions on how to fix this? Thanks /Leslie ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD/amd: boot/loader ignores usb-keyboard
Hello, when i switched to an usb-keyboard some month ago, i realized, that boot/loader ignores input from this device. The bootmanager accepts input, loader not. Is there any configuration-parameter to fix this? Andreas ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Spanish keyboard in X
Hi, This is working for me correctly. In gnome select Sistema/Preferencias/Teclado (System/preferences/Keyboard) and select the appropriate layout. Also on my .bash_profile I've included a: export LANG=es_ES.ISO8859-15 Cheers, Antonio On 18/07/2010 18:49, Leonardo M. Ramé wrote: Hi,I'm trying to configure spanish keyboard in FreeBsd 8.1-RC2 with no luck, I've read many documents on the web, but they seem to be rather old, or assume that the user has Gnome or KDE installed, I use Awesome WM. Any hint? Leonardo M. Ramé http://leonardorame.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Spanish keyboard in X
El día Sunday, July 18, 2010 a las 11:32:05AM -0700, Leonardo M. Ramé escribió: Yes,I have modified xorg.conf the same way as you mentioned. Anyway, now the problem is solved by adding setxkbmap es to my .xsession Thanks. Leonardo M. Ramé http://leonardorame.blogspot.com A bit related to the question: If you need Spanish Tilde chars but you have only an English or German keyboard (like I have), you can make use of the so called WindowsKey in X11 and define the keys like shown below. After this, for example, the combination WindowsKey+a gives á (a-tilde). # $Id: xmod.sh,v 1.1 2008/08/25 10:04:41 guru Exp $ # # para español: # xmodmap -e keycode 0x73 = Mode_switch xmodmap -e keycode 0x39 = n N ntilde Ntilde xmodmap -e keycode 0x1a = e E eacute Eacute xmodmap -e keycode 0x26 = a A aacute Aacute xmodmap -e keycode 0x1f = i I iacute Iacute xmodmap -e keycode 0x1e = u U uacute Uacute xmodmap -e keycode 0x20 = o O oacute Oacute xmodmap -e keycode 0x14 = questiondown question backslash ssharp xmodmap -e keycode 0x0a = 1 exclam exclamdown onesuperior # xmodmap -e keycode 94 = less greater guillemotleft guillemotright bar brokenbar Espero que te ayude. Saludos matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Spanish keyboard in X
On Mon, 19 Jul 2010 10:09:00 +0200, Matthias Apitz g...@unixarea.de wrote: El día Sunday, July 18, 2010 a las 11:32:05AM -0700, Leonardo M. Ramé escribió: Yes,I have modified xorg.conf the same way as you mentioned. Anyway, now the problem is solved by adding setxkbmap es to my .xsession Thanks. Leonardo M. Ramé http://leonardorame.blogspot.com A bit related to the question: If you need Spanish Tilde chars but you have only an English or German keyboard (like I have), you can make use of the so called WindowsKey in X11 and define the keys like shown below. Just for completeness, there is another option I'd like to add: You define a key to be the multi key, usually labelled Compose, at least on the Sun keyboard I use; in ~/.xmodmaprc: add mod4 = Multi_key keycode 117 = Multi_key Then you can compose any characters you need that aren't even part of your localized keymap, e. g. Compose char1 char2 (as a sequence, not a combination) will give you the combination of both characters, at least if there's a symbol matching in the character table. Examples: Compose a a - å (svedish a-circle) Compose s s - ß (Eszett) Compose o / - ø (danish o-stroke) Compose U - Ü (german U Umlaut, capital) Compose L / - Ł (polish L-stroke, capital) Compose k k - ĸ (greek kappa, not sure if it really is) Compose n ' - ń (n with accent grave) This can also be used to generate tilde characters, as well as the weirdest use of accents. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Spanish keyboard in X
Hi,I'm trying to configure spanish keyboard in FreeBsd 8.1-RC2 with no luck, I've read many documents on the web, but they seem to be rather old, or assume that the user has Gnome or KDE installed, I use Awesome WM. Any hint? Leonardo M. Ramé http://leonardorame.blogspot.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Spanish keyboard in X
On Sun, 18 Jul 2010 09:49:16 -0700 (PDT), Leonardo M. Ramé martinr...@yahoo.com wrote: Hi,I'm trying to configure spanish keyboard in FreeBsd 8.1-RC2 with no luck, I've read many documents on the web, but they seem to be rather old, or assume that the user has Gnome or KDE installed, I use Awesome WM. Any hint? What's wrong about the old-fashioned way of using xorg.conf as a central means of X configuration? :-) Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout de Option AutoRepeat250 30 EndSection Of course, you have to set the correct codes for spanish layout (setting XkbLayout), it should be es. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Spanish keyboard in X
Yes,I have modified xorg.conf the same way as you mentioned. Anyway, now the problem is solved by adding setxkbmap es to my .xsession Thanks. Leonardo M. Ramé http://leonardorame.blogspot.com --- On Sun, 7/18/10, Polytropon free...@edvax.de wrote: From: Polytropon free...@edvax.de Subject: Re: Spanish keyboard in X To: Leonardo M. Ramé martinr...@yahoo.com Cc: freebsd-questions@freebsd.org Date: Sunday, July 18, 2010, 2:36 PM On Sun, 18 Jul 2010 09:49:16 -0700 (PDT), Leonardo M. Ramé martinr...@yahoo.com wrote: Hi,I'm trying to configure spanish keyboard in FreeBsd 8.1-RC2 with no luck, I've read many documents on the web, but they seem to be rather old, or assume that the user has Gnome or KDE installed, I use Awesome WM. Any hint? What's wrong about the old-fashioned way of using xorg.conf as a central means of X configuration? :-) Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout de Option AutoRepeat 250 30 EndSection Of course, you have to set the correct codes for spanish layout (setting XkbLayout), it should be es. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB keyboard: mode switch / numlock freezes
On 04/27/10 07:06, Polytropon wrote: On Mon, 26 Apr 2010 00:33:28 +0200, Anselm Strauss amsiba...@gmail.com wrote: Could it be a numlock issue? Any idea how to address this? A good tool for diagnostics always is the xev program. See if something like KeyPress event, serial 24, synthetic NO, window 0x1c1, root 0x73, subw 0x0, time 1034406899, (-570,493), root:(12,632), state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x1c1, root 0x73, subw 0x0, time 1034406949, (-570,493), root:(12,632), state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False comes out when pressing the Num key. You can always remap the Num Lock functionality onto another key that doesn't fail after the 4th use - see xmodmap. I tried xev, but there is no event when I press the mode switch. I mapped numlock to scrolllcok for testing. I then see the numlock event but the mode on the keyboard block does not change. So it doesn't seem to be implemented over the numlock functionality. Is there another way to debug the USB device directly? Anselm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: USB keyboard: mode switch / numlock freezes
On Mon, 26 Apr 2010 00:33:28 +0200, Anselm Strauss amsiba...@gmail.com wrote: Could it be a numlock issue? Any idea how to address this? A good tool for diagnostics always is the xev program. See if something like KeyPress event, serial 24, synthetic NO, window 0x1c1, root 0x73, subw 0x0, time 1034406899, (-570,493), root:(12,632), state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 27, synthetic NO, window 0x1c1, root 0x73, subw 0x0, time 1034406949, (-570,493), root:(12,632), state 0x10, keycode 77 (keysym 0xff7f, Num_Lock), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False comes out when pressing the Num key. You can always remap the Num Lock functionality onto another key that doesn't fail after the 4th use - see xmodmap. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
USB keyboard: mode switch / numlock freezes
Hi, I have a Roccat Arvo keyboard that has a number block with integrated positioning keys (arrows, del, end, ...), but no extra keys for them. There is a mode switch button that switches between the two layouts, like the numlock key, but I'm not sure if this really is numlock. For some reason the switch stops to work after exactly 4 presses. This only happens during boot, or when the FreeBSD kernel is loaded. It does not happen when I boot into Windows or Linux. I also tried other computers, getting the same result. Could it be a numlock issue? Any idea how to address this? Thanks, Anselm ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Configure X: multiple keyboard layouts ?
Hi, I'd like to configure X for multiple keyboard layouts, e. g.: - french - swiss french - german On my Linux box (running CentOS 5.4 and a dated version of X.org), the configuration for this looks like this : Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout fr,ch,de Option XkbVariant ,fr, Option XkbOptions grp:alt_shift_toggle EndSection This stanza enables me to toggle between different keyboard layouts, using the [Alt]+[RightShift] key combination. You might wonder about the XkbVariant option: the swiss keyboard layout has two variants: fr and de. This is to indicate the swiss roman layout. Now is there any way I could achieve a similar thing with the more recent X.org shipping with FreeBSD 8.0 ? Any suggestions ? Niki Kovacs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Configure X: multiple keyboard layouts ?
On Sun, Mar 07, 2010 at 11:09:16AM +0100, Niki Kovacs wrote: Hi, I'd like to configure X for multiple keyboard layouts, e. g.: - french - swiss french - german On my Linux box (running CentOS 5.4 and a dated version of X.org), the configuration for this looks like this : Section InputDevice Identifier Keyboard0 Driver kbd Option XkbModel pc105 Option XkbLayout fr,ch,de Option XkbVariant ,fr, Option XkbOptions grp:alt_shift_toggle EndSection This stanza enables me to toggle between different keyboard layouts, using the [Alt]+[RightShift] key combination. You might wonder about the XkbVariant option: the swiss keyboard layout has two variants: fr and de. This is to indicate the swiss roman layout. Now is there any way I could achieve a similar thing with the more recent X.org shipping with FreeBSD 8.0 ? Any suggestions ? Hi Niki, Welcome to FreeBSD! There is a way to achieve similar results with recent X.org. X nowadays can get by without an xorg.conf and by default it uses hald and dbus to configure keyboard, mouse etc. It's documented how you can create an xorg.conf and use that for device config rather than hald: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/x-config.html You basically create an xorg.conf and then add: Option AutoAddDevices false to the ServerLayout section and then your keyboard config placed in your xorg.conf will be picked up. You will also need a section for the mouse along the lines of: Section InputDevice Identifier Mouse0 Driver mouse Option CorePointer Option Protocol auto Option Device /dev/sysmouse # Option Emulate3Buttons false Option ZAxisMapping 4 5 6 7# For scroll wheel EndSection It's parameters are dependent on your type of mouse. With that and xorg.conf placed under /etc/X11/ you should be good to go. But I'm quite sure you know that xorg.conf can be a fiddle ;) If you get stuck, post your xorg.conf BTW, if you haven't read it already the manpage for moused(8) is quite a revelation. The FreeBSD mouse driver puts the Linux mouse driver to shame! Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
