You know what they say about "assumptions." E.g.:
rick gen wrote:Lesson to learn is make a little research first before buying.
I read every
Q&A on the Amazon product page. The keyboard is all locally-configurable (incl. creating and saving macros). Didn't care about the media keys.
It would never have occurred to me in a million years the caps lock indicator would be b0rk3d.
Secondly: You'll note I referred to a bug. Please see caps lock led not working on Linux console
In short: As to the caps lock indicator: This is not a compatibility problem, but a bug. And the Corsair K55 is far from the only keyboard to fall victim to it.
phd21 wrote:Hi "JSeymour",
I just read your post and the good replies to it. Here are my thoughts on this as well.
That is a ridiculous and inflammatory statement in your post's subject, why don't you relax and change it to something that actually fits the issues you have, like "Having a problem with Corsair K55 keyboard."
Because I've been dealing with Linux systems since RH5 and this has been a recurring problem all along. This is far from the first time I've run into silly, unnecessarily broken functionality. I am relaxed. That OP didn't come close
to the rant I would liked to have spewed
It was not meant to be provocative or flame bait. It was meant to express a POV. I went back and re-read it a couple times. I re-read it again this morning. I stand by it.
+1 for the comments like Linux and specifically Linux Mint have certainly won the desktop wars for me and oh so many others.
It has, for me, too. (Well, up until recently.) But it has about half the desktop market share of Apple, which, in turn, has a tiny fraction of MS-Win. Not a particularly good showing considering the cost of and flaws in its competition. (I refer, of course, to Apple and Microsoft, respectively.)
I don't know how much time y'all spend on-line outside of Linux and other "tech geek" forums, but, aside from app availability, the nature of my complaint is the main reason I see non-tech users cite for trying, and discarding Linux.
It would help to know more about your system setup. If you run "inxi -Fxzd" and "lsusb" from the console terminal prompt, highlight the results, copy and paste them back here, that should provide enough information.
Code: Select all
$ inxi -Fxzd
System: Host: jimsun Kernel: 3.13.0-100-generic x86_64 (64 bit, gcc: 4.8.4) Desktop: N/A Distro: Linux Mint 17 Qiana
Machine: System: ASUS product: All Series
Mobo: ASUSTeK model: Z87-A version: Rev 1.xx Bios: American Megatrends version: 1707 date: 12/13/2013
CPU: Quad core Intel Core i5-4570S CPU (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 23202.7
Clock Speeds: 1: 800.00 MHz 2: 2901.00 MHz 3: 800.00 MHz 4: 800.00 MHz
Graphics: Card: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
X.Org: 1.15.1 drivers: intel (unloaded: fbdev,vesa) Resolution: email@example.com
GLX Renderer: Mesa DRI Intel Haswell Desktop GLX Version: 3.0 Mesa 10.1.3 Direct Rendering: Yes
Audio: Card-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0
Card-2: Intel 8 Series/C220 Series Chipset High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture ver: k3.13.0-100-generic
Network: Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 ver: 2.3LK-NAPI port: e000 bus-ID: 03:00.0
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 979.5GB (20.7% used) 1: id: /dev/sda model: INTEL_SSDSC2BW24 size: 240.1GB
2: id: /dev/sdb model: INTEL_SSDSC2BW24 size: 240.1GB 3: USB id: /dev/sdc model: My_Passport_070A size: 499.4GB
Optical: /dev/sr0 model: N/A rev: N/A dev-links: cdrom
Features: speed: 48x multisession: yes audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: N/A
Partition: ID: / size: 19G used: 5.9G (34%) fs: ext4 ID: /boot size: 453M used: 87M (21%) fs: ext4
ID: /home size: 158G used: 86G (58%) fs: ext4 ID: /var size: 9.1G used: 6.9G (81%) fs: ext4
ID: swap-1 size: 8.00GB used: 0.00GB (0%) fs: swap
RAID: Device-1: /dev/md1 - active components: sda1 sdb1
Info: raid: 1 report: 2/2 blocks: 234298176 chunk size: N/A bitmap: true
Sensors: System Temperatures: cpu: 28.0C mobo: 32.0C
Fan Speeds (in rpm): cpu: 438 fan-1: 789 fan-3: 755 fan-4: 0 fan-5: 0 fan-6: 0
Info: Processes: 250 Uptime: 24 min Memory: 2158.4/7669.6MB Runlevel: 2 Gcc sys: 4.8.4 Client: Shell inxi: 1.8.4
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 1058:070a Western Digital Technologies, Inc. My Passport Essential (WDBAAA), My Passport for Mac (WDBAAB), My Passport Essential SE (WDBABM), My Passport SE for Mac (WDBABW
Bus 003 Device 004: ID 1b1c:1b3d Corsair
Bus 003 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
First, you might resolve the issue simply by updating the Linux Kernel to the 4.11 series or higher using the Mint Update Manager or the Ubuntu Kernel PPA, or Ukuu, and reboot afterwards...
For a caps lock indicator? Yeah... I'm thinking not. This system is also the our home network's "everything server." It's mostly vanilla, but it is
running mdraid and hosting the Ubiquiti UniFi controller software. If it goes tango-uniform, we have nothing. 3.13.0-24 is the latest recommended kernel. I felt I was taking enough a chance on 3.13.0-100, but there were security issues (no longer recall what they were) that necessitated that.
Hope this helps ...
It does not, but I sincerely appreciate the attempt.
The caps lock indicator works correctly in the BIOS. Linux booting is breaking it.
The suggestion of putting "dumpkeys | sed s/CtrlL_Lock/Caps_Lock/ |loadkeys" into /etc/rc.local fixes the caps lock indicator, in console logins
, but breaks the num lock indicator. (It starts out lit, even though the keyboard is not in num lock.)
The suggestion of putting "keycode 58 = Caps_Lock" in /etc/console-setup/remap.inc does nothing, as does the suggestion of putting "dumpkeys |sed -e 's/keycode 58 = CtrlL_Lock/keycode 58 = Caps_Lock/' |loadkeys 2>&1 >/dev/null" into /etc/default/keyboard
All of the graphical interface suggestions have been dead ends.
I expect to eventually resolve the problem by moving this system into a server-only role (at which time I'll probably upgrade it to the latest Ubuntu LTS server release) and sticking it into a corner somewhere, then moving my wife and I over to Apple desktop systems. In the interim I'll simply disable the caps lock key. I retired after 30+ years in I.T. earlier this year. I've entirely lost my appetite for fiddling with contrary software.
Thanks for the reasoned responses, everybody, even if we do not agree.