Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On Tuesday 03 April 2012 05:35:24 Opera wrote:
Hlo,
The reason for putting this on top is that I have data that are
showing that I can not blame the Shuttle.
Here is the brief infos-
When using a USB keyboard [native USB or with an adaptor for ps2]
the keypad Del key works perfectly but when NumLock is on that key
does not change its output to Dot when working with any version
of OpenBSD that I have tried. Turning NumLock off and using the
shift key does not work either.
There are no other keys affected.
The problem exists on every computer that I try.
Windows 7 or XP and NetBSD both work perfectly.
There is now some tension in the evidence.
(I) It would seem that there is a little bug in OpenBSD that will
affect any box running with USB keyboard.
(II) I can't believe that this can not have been noticed before if
clause (I) is true.
Well maybe that no OBSD person uses USB keyboard? Or doesn't use
that Dot key on the keypad?
I ust tried it on two machines with (only) a USB keyboard. One i tried with
the latetst snapshot from 2 april. Both show the same problem.
The del function on that same key also don't behave like the normal del key.
gr
Renzo
On 31/03/2012 04:07, Steffen Daode Nurpmeso wrote:
Opera wrote [2012-03-30 12:58+0200]:
Using the same keyboard where I first saw the bug but connected to a
plain old PC.
I use hexdump like this:
# hexdump -C
tap the problem key, then hit return and then Cntrol-D
With numlock off I see:
^[[3~
1b 5b 33 7e 0a
0005
With numlock on:
.
2e 0a
0002
Using the same keyboard with a ps2-USB adaptor I see the same
result as the numlock off test above whether numlock is on or off.
This is what I see on the Shuttle also but it has no ps2 sockets
so on it I'm stuck with no working dot key on the numpad and
of course old habits die hard so I mess up lots of ip addresses.
Is there something in wsconsctl or such that would let me patch
it? I've been hunting through various related man pages but I
have not hit on a hint so far.
Hey, b-by!
Just recently i've posted a patch to tech@ that let's you examine
the scancode of a key via wsconsctl!!!
Then you can use basic wsconsctl features to set the key to
whatever you want, now that you can identify it!!
By the way - Marco Peereboom has posted a great ksh(1) to tech@ on
2011-09-06 that let you do graceful multi-character-sequence key
binding, which may also be of interest to you.
Was for me.
And YOU ARE THE FIRST Windows NT user i know of who cares about
keyboard scancodes!
This is just a FANTASTIC EXPERIENCE for me.
THANK YOU
(P.S.: there is a X program which gives you even more info, so
that you can adjust your .xmodmaprc or so.)
--steffen
Forza Figa!
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On 3/04/2012 15:35, Richard Toohey wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. There are no other keys affected. The problem exists on every computer that I try. Windows 7 or XP and NetBSD both work perfectly. There is now some tension in the evidence. (I) It would seem that there is a little bug in OpenBSD that will affect any box running with USB keyboard. (II) I can't believe that this can not have been noticed before if clause (I) is true. IIRC then yes, I have noticed this (or something very similar.) Trying to run an emulator program on OpenBSD. Worked fine on my laptop, but using a USB keyboard failed - it was returning a different value for the same key. This was a couple of months ago, so my memory might be playing tricks on me. Thanks for the report. When you say same key, do you mean the numpad Del/. key?
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On 3/04/2012 15:54, patrick keshishian wrote: On Mon, Apr 2, 2012 at 8:35 PM, Operaop...@witworx.com wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. Just tried with both my netbook (running week old snapshot) with a USB keyboard attached to and also an older desktop (running older OBSD release) with SUN USB keyboard. Both work fine. The period (.) on the numeric-pad (with Num Lock on) acts as a period (tested with xcal and in vi). HTH, --patrick Oh.. that blows me out. After trying 2 models of Mitsubishi Diamond Digital (ps2), a recent Samsung ps2 and a Gigabyte USB on machines as old as 2000 and as new as a Thinkpad e320 and the Shuttle and having all of them fail, I didn't really expect to see any report to the contrary. Desparate question - I use US layout. Do you? Tnx
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On 3/04/2012 21:07, Renzo Fabriek wrote: (I) It would seem that there is a little bug in OpenBSD that will affect any box running with USB keyboard. (II) I can't believe that this can not have been noticed before if clause (I) is true. Well maybe that no OBSD person uses USB keyboard? Or doesn't use that Dot key on the keypad? I ust tried it on two machines with (only) a USB keyboard. One i tried with the latetst snapshot from 2 april. Both show the same problem. The del function on that same key also don't behave like the normal del key. I am sorry that you have the bug too but I'm glad I'm not alone. I wonder if anybody reading the list can tell us why the USB keyboard has just one key that does not honor the NumLock modifier that does work for all the other keys on the keypad? Mind you that the shift key does not get a dot by tapping the Del/. key either Tnx.
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On Tuesday 03 April 2012 14:02:20 Opera wrote: On 3/04/2012 15:54, patrick keshishian wrote: On Mon, Apr 2, 2012 at 8:35 PM, Operaop...@witworx.com wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. Just tried with both my netbook (running week old snapshot) with a USB keyboard attached to and also an older desktop (running older OBSD release) with SUN USB keyboard. Both work fine. The period (.) on the numeric-pad (with Num Lock on) acts as a period (tested with xcal and in vi). HTH, --patrick Oh.. that blows me out. After trying 2 models of Mitsubishi Diamond Digital (ps2), a recent Samsung ps2 and a Gigabyte USB on machines as old as 2000 and as new as a Thinkpad e320 and the Shuttle and having all of them fail, I didn't really expect to see any report to the contrary. Desparate question - I use US layout. Do you? Tnx One thing I forgot to check. Last time I only tried it at the console. I now tried it within X. The dot works, but the del function still doesn't do the same as the other del key.
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On Tue, Apr 3, 2012 at 5:02 AM, Opera op...@witworx.com wrote: On 3/04/2012 15:54, patrick keshishian wrote: On Mon, Apr 2, 2012 at 8:35 PM, Operaop...@witworx.com wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. Just tried with both my netbook (running week old snapshot) with a USB keyboard attached to and also an older desktop (running older OBSD release) with SUN USB keyboard. Both work fine. The period (.) on the numeric-pad (with Num Lock on) acts as a period (tested with xcal and in vi). HTH, --patrick Oh.. that blows me out. After trying 2 models of Mitsubishi Diamond Digital (ps2), a recent Samsung ps2 and a Gigabyte USB on machines as old as 2000 and as new as a Thinkpad e320 and the Shuttle and having all of them fail, I didn't really expect to see any report to the contrary. Desparate question - I use US layout. Do you? Yes. US layout here as well. But, as Renzo Fabriek points out in a later post, this does seem to be a problem in console. Not in X. I'm sorry, I don't know if this was explicitly mentioned in your posts, but I didn't find a reference to it being a console issue. I can confirm the issue in console mode. --patrick
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
Yes. US layout here as well. But, as Renzo Fabriek points out in a later post, this does seem to be a problem in console. Not in X. I'm sorry, I don't know if this was explicitly mentioned in your posts, but I didn't find a reference to it being a console issue. I can confirm the issue in console mode. So can I. I'll fix it in a couple seconds; in the meantime you can use: # wsconsctl keyboardN.map+=keycode 99 = KP_Delete KP_Decimal to fix this (N being the wskbd device number of the USB keyboard).
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On 4/04/2012 04:17, Miod Vallat wrote: Yes. US layout here as well. But, as Renzo Fabriek points out in a later post, this does seem to be a problem in console. Not in X. I'm sorry, I don't know if this was explicitly mentioned in your posts, but I didn't find a reference to it being a console issue. I can confirm the issue in console mode. So can I. I'll fix it in a couple seconds; in the meantime you can use: # wsconsctl keyboardN.map+=keycode 99 = KP_Delete KP_Decimal to fix this (N being the wskbd device number of the USB keyboard). OR, where you have an older system and can't update yet, put the arguments in the above command into /etc/wsconsctl.conf i.e. # Fix for USB keyboard keypad Del/. key keyboardN.map+=keycode 99 = KP_Delete KP_Decimal Thank you heaps for the quick fix, Miod. Vous jtes l'homme! Thanks to Richard, Renzo, Patrick as well. Without their help I might still be wondering if I wasn't losing the plot. In any case I am amazed that the bug has been around for years and nobody used the keypad . on a USB keyboard. Oppy.
Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. There are no other keys affected. The problem exists on every computer that I try. Windows 7 or XP and NetBSD both work perfectly. There is now some tension in the evidence. (I) It would seem that there is a little bug in OpenBSD that will affect any box running with USB keyboard. (II) I can't believe that this can not have been noticed before if clause (I) is true. Well maybe that no OBSD person uses USB keyboard? Or doesn't use that Dot key on the keypad? On 31/03/2012 04:07, Steffen Daode Nurpmeso wrote: Opera wrote [2012-03-30 12:58+0200]: Using the same keyboard where I first saw the bug but connected to a plain old PC. I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 1b 5b 33 7e 0a 0005 With numlock on: . 2e 0a 0002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. Hey, b-by! Just recently i've posted a patch to tech@ that let's you examine the scancode of a key via wsconsctl!!! Then you can use basic wsconsctl features to set the key to whatever you want, now that you can identify it!! By the way - Marco Peereboom has posted a great ksh(1) to tech@ on 2011-09-06 that let you do graceful multi-character-sequence key binding, which may also be of interest to you. Was for me. And YOU ARE THE FIRST Windows NT user i know of who cares about keyboard scancodes! This is just a FANTASTIC EXPERIENCE for me. THANK YOU (P.S.: there is a X program which gives you even more info, so that you can adjust your .xmodmaprc or so.) --steffen Forza Figa!
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On 3/04/2012, at 3:35 PM, Opera wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. There are no other keys affected. The problem exists on every computer that I try. Windows 7 or XP and NetBSD both work perfectly. There is now some tension in the evidence. (I) It would seem that there is a little bug in OpenBSD that will affect any box running with USB keyboard. (II) I can't believe that this can not have been noticed before if clause (I) is true. IIRC then yes, I have noticed this (or something very similar.) Trying to run an emulator program on OpenBSD. Worked fine on my laptop, but using a USB keyboard failed - it was returning a different value for the same key. This was a couple of months ago, so my memory might be playing tricks on me. Well maybe that no OBSD person uses USB keyboard? Or doesn't use that Dot key on the keypad? On 31/03/2012 04:07, Steffen Daode Nurpmeso wrote: Opera wrote [2012-03-30 12:58+0200]: Using the same keyboard where I first saw the bug but connected to a plain old PC. I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 1b 5b 33 7e 0a 0005 With numlock on: . 2e 0a 0002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. Hey, b-by! Just recently i've posted a patch to tech@ that let's you examine the scancode of a key via wsconsctl!!! Then you can use basic wsconsctl features to set the key to whatever you want, now that you can identify it!! By the way - Marco Peereboom has posted a great ksh(1) to tech@ on 2011-09-06 that let you do graceful multi-character-sequence key binding, which may also be of interest to you. Was for me. And YOU ARE THE FIRST Windows NT user i know of who cares about keyboard scancodes! This is just a FANTASTIC EXPERIENCE for me. THANK YOU (P.S.: there is a X program which gives you even more info, so that you can adjust your .xmodmaprc or so.) --steffen Forza Figa!
Re: Does your USB keyboard Dot key on keypad fail? Was Re: Shuttle XS35 v2 - One key going loco
On Mon, Apr 2, 2012 at 8:35 PM, Opera op...@witworx.com wrote: Hlo, The reason for putting this on top is that I have data that are showing that I can not blame the Shuttle. Here is the brief infos- When using a USB keyboard [native USB or with an adaptor for ps2] the keypad Del key works perfectly but when NumLock is on that key does not change its output to Dot when working with any version of OpenBSD that I have tried. Turning NumLock off and using the shift key does not work either. Just tried with both my netbook (running week old snapshot) with a USB keyboard attached to and also an older desktop (running older OBSD release) with SUN USB keyboard. Both work fine. The period (.) on the numeric-pad (with Num Lock on) acts as a period (tested with xcal and in vi). HTH, --patrick There are no other keys affected. The problem exists on every computer that I try. Windows 7 or XP and NetBSD both work perfectly. There is now some tension in the evidence. (I) It would seem that there is a little bug in OpenBSD that will affect any box running with USB keyboard. (II) I can't believe that this can not have been noticed before if clause (I) is true. Well maybe that no OBSD person uses USB keyboard? Or doesn't use that Dot key on the keypad? On 31/03/2012 04:07, Steffen Daode Nurpmeso wrote: Opera wrote [2012-03-30 12:58+0200]: Using the same keyboard where I first saw the bug but connected to a plain old PC. I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 1b 5b 33 7e 0a 0005 With numlock on: . 2e 0a 0002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. Hey, b-by! Just recently i've posted a patch to tech@ that let's you examine the scancode of a key via wsconsctl!!! Then you can use basic wsconsctl features to set the key to whatever you want, now that you can identify it!! By the way - Marco Peereboom has posted a great ksh(1) to tech@ on 2011-09-06 that let you do graceful multi-character-sequence key binding, which may also be of interest to you. Was for me. And YOU ARE THE FIRST Windows NT user i know of who cares about keyboard scancodes! This is just a FANTASTIC EXPERIENCE for me. THANK YOU (P.S.: there is a X program which gives you even more info, so that you can adjust your .xmodmaprc or so.) --steffen Forza Figa!
Re: Shuttle XS35 v2 - One key going loco
Some progress in research. I remembered how to catch key output using hexdump so I could examine and compare various configurations. Using the same keyboard where I first saw the bug but connected to a plain old PC. I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 1b 5b 33 7e 0a 0005 With numlock on: . 2e 0a 0002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. TIA, oppy On 30/03/2012 11:46, Opera wrote: dmesg below. This little unit is cool and nearly everything important works on the important OS. I don't care about the funny multi-card thingy as I only use USB sticks. The one bug is very annoying. The numpad key that is . when numlock is on and Del otherwise is really tricky. When booting, at the boot prompt if the numlock is on, the key produces dots as expected. Once BSD.RD or BSD is running that is not the case. BSD shows all the bugs and I shall skip BSD.RD as it is a subset. At a login: prompt it appears that no chars are being sent BUT if you hit the key 8 times it acts like you hit Enter except the Password: prompt becomes assword: Hit an Enter there and you get a Login failed and a new login: prompt. (of course!) At this point hitting the crazy key results in ^[[3~ appearing every time the key is pressed. (until the max length (8 hits) is exceeded.)
Re: Shuttle XS35 v2 - One key going loco
Opera wrote [2012-03-30 12:58+0200]: Using the same keyboard where I first saw the bug but connected to a plain old PC. I use hexdump like this: # hexdump -C tap the problem key, then hit return and then Cntrol-D With numlock off I see: ^[[3~ 1b 5b 33 7e 0a 0005 With numlock on: . 2e 0a 0002 Using the same keyboard with a ps2-USB adaptor I see the same result as the numlock off test above whether numlock is on or off. This is what I see on the Shuttle also but it has no ps2 sockets so on it I'm stuck with no working dot key on the numpad and of course old habits die hard so I mess up lots of ip addresses. Is there something in wsconsctl or such that would let me patch it? I've been hunting through various related man pages but I have not hit on a hint so far. Hey, b-by! Just recently i've posted a patch to tech@ that let's you examine the scancode of a key via wsconsctl!!! Then you can use basic wsconsctl features to set the key to whatever you want, now that you can identify it!! By the way - Marco Peereboom has posted a great ksh(1) to tech@ on 2011-09-06 that let you do graceful multi-character-sequence key binding, which may also be of interest to you. Was for me. And YOU ARE THE FIRST Windows NT user i know of who cares about keyboard scancodes! This is just a FANTASTIC EXPERIENCE for me. THANK YOU (P.S.: there is a X program which gives you even more info, so that you can adjust your .xmodmaprc or so.) --steffen Forza Figa!
Shuttle XS35 v2 - One key going loco
dmesg below. This little unit is cool and nearly everything important works on the important OS. I don't care about the funny multi-card thingy as I only use USB sticks. The one bug is very annoying. The numpad key that is . when numlock is on and Del otherwise is really tricky. When booting, at the boot prompt if the numlock is on, the key produces dots as expected. Once BSD.RD or BSD is running that is not the case. BSD shows all the bugs and I shall skip BSD.RD as it is a subset. At a login: prompt it appears that no chars are being sent BUT if you hit the key 8 times it acts like you hit Enter except the Password: prompt becomes assword: Hit an Enter there and you get a Login failed and a new login: prompt. (of course!) At this point hitting the crazy key results in ^[[3~ appearing every time the key is pressed. (until the max length (8 hits) is exceeded.) Logging in normally is fine but now the errant key simply echoes a tilde for each keypress whether numlock is on or off. The problem happens when using Mitsubishi Diamond Digital or Samsung SDL1500 keyboards. FWIW it doesn't happen using win things. XP or 7. It does happen under older OpenBSD releases. TIA, Oppy. Dmesg: OpenBSD 5.1-current (GENERIC.MP) #214: Sun Mar 25 15:09:18 MDT 2012 dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP cpu0: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF real mem = 2137255936 (2038MB) avail mem = 2091499520 (1994MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 06/23/11, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev. 2.6 @ 0xfc8b0 (23 entries) bios0: vendor American Megatrends Inc. version 080015 date 06/23/2011 bios0: Standard XS35 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC MCFG SLIC OEMB HPET GSCI acpi0: wakeup devices P0P1(S4) AZAL(S3) P0P4(S4) P0P5(S4) JLAN(S3) P0P6(S4) P0P7(S4) P0P8(S4) P0P9(S4) USB0(S3) USB1(S3) USB2(S3) USB3(S3) EUSB(S3) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: apic clock running at 199MHz cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu1: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu2: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Atom(TM) CPU D525 @ 1.80GHz (GenuineIntel 686-class) 1.80 GHz cpu3: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,NXE,LONG,SSE3,MWAIT,DS-CPL,TM2,SSSE3,CX16,xTPR,PDCM,MOVBE,LAHF ioapic0 at mainbus0: apid 4 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 3, remapped to apid 4 acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 3 (P0P1) acpiprt2 at acpi0: bus 1 (P0P4) acpiprt3 at acpi0: bus 2 (P0P5) acpiprt4 at acpi0: bus -1 (P0P6) acpiprt5 at acpi0: bus -1 (P0P7) acpiprt6 at acpi0: bus -1 (P0P8) acpiprt7 at acpi0: bus -1 (P0P9) acpiec0 at acpi0 acpicpu0 at acpi0 acpicpu1 at acpi0 acpicpu2 at acpi0 acpicpu3 at acpi0 acpitz0 at acpi0: critical temperature is 104 degC acpibtn0 at acpi0: SLPB acpibtn1 at acpi0: PWRB acpivideo0 at acpi0: GFX0 acpivout0 at acpivideo0: LCD_ bios0: ROM list: 0xc/0xda00! 0xce000/0x1800! 0xcf800/0x1000 pci0 at mainbus0 bus 0: configuration mode 1 (bios) mem address conflict 0xfc00/0x400 pchb0 at pci0 dev 0 function 0 Intel Pineview DMI rev 0x02 vga1 at pci0 dev 2 function 0 Intel Pineview Video rev 0x02 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) intagp0 at vga1 agp0 at intagp0: aperture at 0xd000, size 0x1000 inteldrm0 at vga1: apic 4 int 16 drm0 at inteldrm0 Intel Pineview Video rev 0x02 at pci0 dev 2 function 1 not configured azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: msi azalia0: codecs: IDT 92HD81B1X audio0 at azalia0 ppb0 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 4 int 16 pci1 at ppb0 bus 1 ppb1 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 4 int 17 pci2 at ppb1 bus 2 JMicron SD/MMC rev 0x80 at pci2 dev 0 function 0 not configured sdhc0 at pci2 dev 0 function 2 JMicron SD Host
Re: Shuttle XS35 v2 - One key going loco
On 29/03/2012 17:47, Opera wrote: dmesg below. This little unit is cool and nearly everything important works on the important OS. I don't care about the funny multi-card thingy as I only use USB sticks. The one bug is very annoying. The numpad key that is . when numlock is on and Del otherwise is really tricky. When booting, at the boot prompt if the numlock is on, the key produces dots as expected. Once BSD.RD or BSD is running that is not the case. BSD shows all the bugs and I shall skip BSD.RD as it is a subset. At a login: prompt it appears that no chars are being sent BUT if you hit the key 8 times it acts like you hit Enter except the Password: prompt becomes assword: Hit an Enter there and you get a Login failed and a new login: prompt. (of course!) At this point hitting the crazy key results in ^[[3~ appearing every time the key is pressed. (until the max length (8 hits) is exceeded.) Logging in normally is fine but now the errant key simply echoes a tilde for each keypress whether numlock is on or off. The problem happens when using Mitsubishi Diamond Digital or Samsung SDL1500 keyboards. FWIW it doesn't happen using win things. XP or 7. It does happen under older OpenBSD releases. TIA, No ideas? Anyone?
