Genius SlimStar PRO usb keyboard refuses to work properly

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the output of 'dmesg' after pressing numlock and removing and then reconnecting your keyboard? Thanks in advance.

OK here it is. I hope it's enough. Im'n not a very experienced user. Just tell me if you need more informations.

[ 15.448000] kjournald starting. Commit interval 5 seconds
[ 15.448000] EXT3-fs: mounted filesystem with ordered data mode.
[ 16.040000] usb 2-2: new low speed USB device using ohci_hcd and address 2
[ 16.248000] usb 2-2: configuration #1 chosen from 1 choice
[ 16.488000] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00012920000456bc]
[ 16.556000] usb 2-5: new full speed USB device using ohci_hcd and address 3
[ 16.764000] usb 2-5: configuration #1 chosen from 1 choice
[ 16.764000] hub 2-5:1.0: USB hub found
[ 16.768000] hub 2-5:1.0: 3 ports detected
[ 17.124000] usb 2-5.1: new full speed USB device using ohci_hcd and address 4
[ 17.248000] usb 2-5.1: configuration #1 chosen from 1 choice
[ 22.080000] eth2: no link during initialization.
[ 22.112000] skge eth1: enabling interface
[ 22.820000] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 22.820000] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 22.872000] i2c_adapter i2c-0: nForce2 SMBus adapter at 0x1c00
[ 22.872000] i2c_adapter i2c-1: nForce2 SMBus adapter at 0x1c40
[ 22.968000] input: PC Speaker as /class/input/input1
[ 23.052000] usbcore: registered new interface driver hiddev
[ 23.116000] input: Logitech USB-PS/2 Optical Mouse as /class/input/input2
[ 23.116000] input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:02.0-2
[ 23.180000] irda_init()
[ 23.180000] NET: Registered protocol family 23
[ 23.252000] input: ABBHOME USB Keyboard as /class/input/input3
[ 23.252000] input: USB HID v1.10 Keyboard [ABBHOME USB Keyboard] on usb-0000:00:02.0-5.1
[ 23.260000] input: ABBHOME USB Keyboard as /class/input/input4
[ 23.260000] input: USB HID v1.10 Mouse [ABBHOME USB Keyboard] on usb-0000:00:02.0-5.1
[ 23.260000] usbcore: registered new interface driver usbhid
[ 23.260000] drivers/usb/input/hid-core.c: v2.6:USB HID core driver
[ 23.320000] Linux agpgart interface v0.101 (c) Dave Jones
[ 23.636000] nvidia: module license 'NVIDIA' taints kernel.
[ 23.908000] NET: Registered protocol family 17
[ 23.920000] ACPI: PCI Interrupt 0000:05:00.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 17
[ 23.920000] PCI: Setting latency timer of device 0000:05:00.0 to 64
[ 23.920000] NVRM: loading NVIDIA UNIX x86 Kernel Module 1.0-9755 Mon Feb 26 23:21:15 PST 2007
[ 23.996000] ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 22
[ 23.996000] ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [APCJ] -> GSI 22 (level, low) -> IRQ 18
[ 23.996000] PCI: Setting latency timer of device 0000:00:04.0 to 64
[ 24.320000] intel8x0_measure_ac97_clock: measured 58795 usecs
[ 24.320000] intel8x0: clocking to 47036
[ 24.444000] fuse init (API version 7.8)
[ 24.484000] lp: driver loaded but no devices found
[ 24.520000] Adding 996020k swap on /dev/disk/by-uuid/ef6b94a0-9c7a-415e-913a-b757c7e3bf6a. Priority:-1 extents:1 across:996020k
[ 24.640000] EXT3 FS on sda2, internal journal
[ 24.804000] kjournald starting. Commit interval 5 seconds
[ 24.804000] EXT3 FS on sdb5, internal journal
[ 2...

Now that the final version of Feisty Fawn is available we were wondering if this issue still exists. Thanks in advance.

Hello,

it seems to be fixed. Just installed Feisty yesterday and no problem so
far. Good work :)

Am Mittwoch, den 25.04.2007, 18:08 +0000 schrieb Brian Murray:
> Now that the final version of Feisty Fawn is available we were wondering
> if this issue still exists. Thanks in advance.
>

I've got Genius SlimStar PRO usb keyboard (with hub), nforce 4 chipset and I'm encountering exactly same problem. I have downloaded Feisty Fawn 7.04 i386 and amd64 builds, same problem. I'll try to post dmesg after reboot into linux. Thanks!

My dmesg output:

[ 0.000000] Linux version 2.6.20-15-generic (root@yellow) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 06:17:24 UTC 2007 (Ubuntu 2.6.20-15.27-generic)
[ 0.000000] Command line: root=UUID=5840460c-8b00-4977-a58e-725a2ded6e0c ro quiet splash
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
[ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 000000007fee0000 (usable)
[ 0.000000] BIOS-e820: 000000007fee0000 - 000000007fee3000 (ACPI NVS)
[ 0.000000] BIOS-e820: 000000007fee3000 - 000000007fef0000 (ACPI data)
[ 0.000000] BIOS-e820: 000000007fef0000 - 000000007ff00000 (reserved)
[ 0.000000] BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
[ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
[ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 3200 used
[ 0.000000] Entering add_active_range(0, 256, 524000) 1 entries of 3200 used
[ 0.000000] end_pfn_map = 1048576
[ 0.000000] DMI 2.2 present.
[ 0.000000] ACPI: RSDP (v000 Nvidia ) @ 0x00000000000f7f80
[ 0.000000] ACPI: RSDT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000007fee3040
[ 0.000000] ACPI: FADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000007fee30c0
[ 0.000000] ACPI: MCFG (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000007fee94c0
[ 0.000000] ACPI: MADT (v001 Nvidia AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x000000007fee9400
[ 0.000000] ACPI: DSDT (v001 NVIDIA AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x0000000000000000
[ 0.000000] Scanning NUMA topology in Northbridge 24
[ 0.000000] Number of nodes 1
[ 0.000000] Node 0 MemBase 0000000000000000 Limit 000000007fee0000
[ 0.000000] Entering add_active_range(0, 0, 159) 0 entries of 3200 used
[ 0.000000] Entering add_active_range(0, 256, 524000) 1 entries of 3200 used
[ 0.000000] NUMA: Using 63 for the hash shift.
[ 0.000000] Using node hash shift of 63
[ 0.000000] Bootmem setup node 0 0000000000000000-000000007fee0000
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0 -> 4096
[ 0.000000] DMA32 4096 -> 1048576
[ 0.000000] Normal 1048576 -> 1048576
[ 0.000000] early_node_map[2] active PFN ranges
[ 0.000000] 0: 0 -> 159
[ 0.000000] 0: 256 -> 524000
[ 0.000000] On node 0 totalpages: 523903
[ 0.000000] DMA zone: 56 pages used for memmap
[ 0.000000] DMA zone: 1101 pages reserved
[ 0.000000] DMA zone: 2842 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 7108 pages used for memmap
[ 0.000000] DMA32 zone: 512796 pages, LIFO batch:31
[ 0.000000] Normal zone: 0 pages used for memmap
[ 0.000000] Nvidia board detected. Ignoring ACPI timer override.
[ 0.000000] If you got timer trouble try acpi_use_timer_override
[ 0.000000] ACPI: PM-Timer IO Port: 0x4008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPI...

HueponiK, could you test the keyboard without using the usb hub and see if the problem still occurs? Thanks in advance.

The keyboard IS hub itself. It has 2 usb ports. nothing plugged into them though....

http://www.genius-kye.com/detaprodtw.asp?idsubcate=30428&idcate=30413&idprod=30471&name=over

I misunderstood, I thought you meant that it was connected via a hub not that it was hub. Sorry about that.

HueponiK,
For this bug to be accepted by the kernel team please provide the minimal information as described here: https://wiki.ubuntu.com/KernelTeamBugPolicies.

HueponiK,
Is this still a problem with Ubuntu 7.10 (Gutsy)?
If so please provide the information described here: https://wiki.ubuntu.com/DebuggingKeyboardDetection.

Yes, the problem is still there. I'm just acquired PS/2 keyboard so soon I will be able to provide further information.

OK. I'm plugged in PS/2 Keyboard.

I'll try to go through https://wiki.ubuntu.com/DebuggingKeyboardDetection guide.

Keyboard - Genius SlimStar pro, usb wired connection, have built-in passive 2-port usb hub.

Right now, my USB keyboard now behaves different way (from what was on feisty) - it does not work at all. just Numlock led is on. Prevously, it stopped responding after pressing shift (i dont remember which key exactly).
When I'm pressing NumLock at my PS/2 keyboard, nothing happens at usb one - NumLock led still on.

Unplugget usb keyboard, then plugged it back in. same situation - not working but NumLock on

P.S. sorry for my bad english

Thank you for the information provided, assigning to the kernel usb team.
I don't notice anything special in your logs, this problem probably needs some further debugging guided by a knowledged developer.
A similar bug has been reported in Debian, see upstream bug watch.

I've also tried it in gentoo with custom kernel 2.6.23. No luck, absolutely same behavior...

I've installed Ubuntu 8.04 beta. Seems like the bug is gone!

Kernel is 2.6.24-16-generic

Oh.. I forgot to mantion. I also changed my motherboard, (was DFI NFORCE4-SLI, now Abit IP35 pro)

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Same problem in Intrepid Ibex 8.10 Alpha5 2.6.27-3

Perhaps the problem of motherboards NForce4, as with other works without problems, as well as keyboard works through the USB HUB.

Hi tp-hans,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux-image-`uname -r` 94837

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

.We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!