Wireless keyboard and USB Knoppix

Hello,
I'm Gary. I've been lurking about attempting to find a solution to a problem. I like Knoppix. It's the most impessive OS I've played with lately. The CD was delivered and put to a stick that boots fine on my old POS laptop. I've tweaked the bios on this new POS to allow legacy booting. The disc works fine on this Win 8.1 Acer T3-600, but the stick does not. I seem to have a keyboard right up until the password and then no glory. No KB response. It just waits for a password. Hard boot. Start over.

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>

00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915

00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) (prog-if 30 [XHCI])
Subsystem: Acer Incorporated [ALI] Device 8030
Flags: bus master, medium devsel, latency 0, IRQ 42
Memory at f7d20000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd

00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, fast devsel, latency 0, IRQ 11
Memory at f7d3c000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>

00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
Subsystem: Acer Incorporated [ALI] Device 8000
Flags: bus master, fast devsel, latency 0, IRQ 44
Memory at f7d00000 (32-bit, non-prefetchable) [size=128K]
Memory at f7d39000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f080 [size=32]
Capabilities: <access denied>
Kernel driver in use: e1000e

00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f7d38000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci

00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04)
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, fast devsel, latency 0, IRQ 43
Memory at f7d30000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev c4) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: f7c00000-f7cfffff
Capabilities: <access denied>
Kernel driver in use: pcieport

00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) (prog-if 20 [EHCI])
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f7d37000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=04, subordinate=04, sec-latency=32
Capabilities: <access denied>

00:1f.0 ISA bridge: Intel Corporation B75 Express Chipset LPC Controller (rev 04)
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich

00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) (prog-if 01 [AHCI 1.0])
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 41
I/O ports at f0d0 [size=8]
I/O ports at f0c0 [size=4]
I/O ports at f0b0 [size=8]
I/O ports at f0a0 [size=4]
I/O ports at f060 [size=32]
Memory at f7d36000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci

00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04)
Subsystem: Acer Incorporated [ALI] Device 063d
Flags: medium devsel, IRQ 18
Memory at f7d35000 (64-bit, non-prefetchable) [size=256]
I/O ports at f040 [size=32]

03:00.0 Network controller: Atheros Communications Inc. AR9462 Wireless Network Adapter (rev 01)
Subsystem: Lite-On Communications Inc Device 6621
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at f7c00000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at f7c80000 [disabled] [size=64K]
Capabilities: <access denied>
Kernel driver in use: ath9k

It's a PNY 32 stick and a new fangled, 50 dollar, solar powered logitech keyboard. This is being written while accessing the forum through Ice Weasel(cute), operating on the aforementioned kb, on the Acer, from the Knoppix disc. The stick works fine on the old Dell Laptop. I'm thinking USB conflict? Any clues?

I'm studying for my A+, am on the Chancellor's list, and have 40 years computer experience. Why do I still feel stupid?
Don't answer that.

I did see some others with the issue but not any tangible solutions. Sorry if it's been covered back in the dark ages.

Thanks,
gpearman

Hello Gary,

I suppose the solar powered logitech keyboard needs a kernel module which is not included in the Linux kernel. You can verify this by booting from the disc and issuing the command

Code:

---

lsmod

---

This will show the additional kernel modules.

Danke Klaus,

Will try.

Gary

Klaus,

Thanks for your interest.

Module Size Used by
parport_pc 23972 0
ppdev 4167 0
lp 6185 0
parport 21928 3 lp,ppdev,parport_pc
i915 430125 3
drm_kms_helper 20665 1 i915
ipv6 212138 14
rfcomm 23249 10
bnep 7279 2
ath3k 4538 0
btusb 8785 0
bluetooth 143972 25 bnep,ath3k,btusb,rfcomm
hid_logitech_dj 7966 0
coretemp 4518 0
kvm_intel 109899 0
kvm 275162 1 kvm_intel
wmi 6035 0
crc32_pclmul 2177 0
serio_raw 3206 0
arc4 1463 2
ath9k 63510 0
ath9k_common 1456 1 ath9k
ath9k_hw 330565 2 ath9k_common,ath9k
ath 10993 3 ath9k_common,ath9k,ath9k_hw
mac80211 347664 1 ath9k
cfg80211 319430 3 ath,ath9k,mac80211
e1000e 121204 0
snd_hda_codec_hdmi 22332 1
snd_hda_codec_realtek 22017 1
ptp 5855 1 e1000e
lpc_ich 10929 0
pps_core 4891 1 ptp
snd_hda_intel 24570 1
snd_hda_codec 90020 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_i ntel
joydev 6659 0
i2c_i801 11125 0

I don't know. What's your opinion. My flight controls are Saitek and the mouse is a wireless logitech (its partner KB died). Just not sure if the logitech entry is the KB or Mouse or relevent.
I do like the system. I'm supposed to know this stuff.

Thanks, Gary

Update and after action report,

Klaus,

Here's the strange bit. I'm now inputting thru the solar KB, Logitech K750.
It wouldn't work for the password.
Used it until then.
Changed to wired KB.
Entered password.
System boots
Changed back to K750.
Works like we got along fine all along. It's trying to drive me crazy.
Is this one of them there bugs folks talk about?
Why just at the password prompt?
Wierd.
Let me know what you think. I'll play around a bit.

Thanks,
Gary

.
Greetings Gary & Klaus2008.

I use a Logitech M305 wireless mouse with Knoppix 7.2.

Code:

---

less Xorg.0.log | grep -i Logitech

---

gives a lot of info on how Knoppix handles it.

HTH

Utu,

I'm honored that both you and Klaus have taken an interest. Thanks for the Xorg lesson. The output seems to be, but am not certain, post boot. What is strange is that the K750 wireless kb works fine up until the password prompt, then a change to a USB wired kb is required for input. After entering the password on the wired kb, the unifier can be re-inserted and the wired USB kb unplugged. I wouldn't know what to change, where in the bootstrap to smooth out the glitch.

Have a look. I can't tell where the kb swap occurred. You can see when I switched back to the wireless mouse. I was thinking the system might have been looking for the wireless mouse's dead partner (they once shared a dongle). Made no difference at the password prompt.

root@Microknoppix:/# less /var/log/Xorg.0.log | grep -i Logitech
[ 111.787] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[ 111.787] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 111.787] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 111.787] (**) Logitech USB Receiver: always reports core events
[ 111.787] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event2"
[ 111.788] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc505
[ 111.788] (--) evdev: Logitech USB Receiver: Found keys
[ 111.788] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 111.788] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[ 111.788] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[ 111.788] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 111.788] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 111.788] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 111.788] (**) Logitech USB Receiver: always reports core events
[ 111.788] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event3"
[ 111.788] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc505
[ 111.788] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[ 111.789] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 111.789] (--) evdev: Logitech USB Receiver: Found relative axes
[ 111.789] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 111.789] (--) evdev: Logitech USB Receiver: Found keys
[ 111.789] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 111.789] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 111.789] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 111.789] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 111.789] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 111.789] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 10)
[ 111.789] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 111.789] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 111.789] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 111.789] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 111.789] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 111.790] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 111.792] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4002 (/dev/input/event6)
[ 111.792] (**) Logitech Unifying Device. Wireless PID:4002: Applying InputClass "evdev keyboard catchall"
[ 111.792] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4002'
[ 111.792] (**) Logitech Unifying Device. Wireless PID:4002: always reports core events
[ 111.792] (**) evdev: Logitech Unifying Device. Wireless PID:4002: Device: "/dev/input/event6"
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Vendor 0x46d Product 0xc52b
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found 1 mouse buttons
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found scroll wheel(s)
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found relative axes
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Forcing relative x/y axes to exist.
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found absolute axes
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Forcing absolute x/y axes to exist.
[ 111.792] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found keys
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Configuring as mouse
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Configuring as keyboard
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Adding scrollwheel support
[ 111.792] (**) evdev: Logitech Unifying Device. Wireless PID:4002: YAxisMapping: buttons 4 and 5
[ 111.792] (**) evdev: Logitech Unifying Device. Wireless PID:4002: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 111.792] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4002" (type: KEYBOARD, id 13)
[ 111.792] (II) evdev: Logitech Unifying Device. Wireless PID:4002: initialized for relative axes.
[ 111.792] (WW) evdev: Logitech Unifying Device. Wireless PID:4002: ignoring absolute axes.
[ 111.793] (**) Logitech Unifying Device. Wireless PID:4002: (accel) keeping acceleration scheme 1
[ 111.793] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration profile 0
[ 111.793] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration factor: 2.000
[ 111.793] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration threshold: 4


Probably cuz we greped "Logitech". I would be interesting to understand what occurs at the password prompt as to require the swap.
Little things that make us go "huh?" By now we're past the "WTF" point.

I'll log the entire process somehow. You guys are busy enough.
Spater!

Thanks,
Gary

I think it could be helpful to see the output of the command

Code:

---

lsusb

---

Here ya go,Sir,

Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) 64MB QDI U2 DISK
Bus 003 Device 003: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 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 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp.
Bus 001 Device 006: ID 04ca:3006 Lite-On Technology Corp.
Bus 002 Device 003: ID 0461:4dcb Primax Electronics, Ltd

Both of the Logitech wireless devices are plugged in now + the wired keyboard (USB), no game controllers. The point in the process that requires the wired Kb is when the system request the passphrase that guards the encrypted persistent partitition. Both keyboards respond except at the passphrase prompt. then just the wired kb. Bizarre, to the uninitiated. The creators may understand what is different at that point in the process. I'm still looking for a logging process. Debug hung - had to kick it -hard boot. No sound card found either. Probably something Acer has done. This is my newest machine. It was part of the emachine class action suit. That old 533 still has ACAD 2000 (legal) on it and it won't miigrate well without extensive tweaking. What I need is a good KVM switch. Throw some crap out. Pardon me. Recycle some stuff.

I'm easily distracted by shiny objects. I can't seem to let this go. It 'bugs' me. I should be doing a practice exam. None of this is on it. My head has bruises.

Thanks,
Gary

Hello Gary,

ID 046d:c52b Logitech, Inc. Unifying Receiver needs the kernel module hid-logitech-dj.ko which has to be loaded before you can use the solar powered Logitech keyboard.

If you have booted from the USB stick you could extract the /mnt-system/boot/syslinux/minirt.gz in a new directory /home/knoppix/minirtdir and copy the kernel module in the subdirectory /home/knoppix/minirtdir/modules. Then the old minirt.gz has to be replaced by a new one containing the kernel module. I would issue the following commands in an LXTerminal.

Code:

---

mkdir -p /home/knoppix/minirtdir
su -
cd /home/knoppix/minirtdir
cp /mnt-system/boot/syslinux/minirt.gz /mnt-system/boot/syslinux/minirt0.gz
zcat /mnt-system/boot/syslinux/minirt.gz | cpio -imd --no-absolute-filenames
cp /lib/modules/`uname -r`/kernel/drivers/hid/hid-logitech-dj.ko /home/knoppix/minirtdir/modules/
find . | cpio -oH newc | gzip -9 > /mnt-system/boot/syslinux/minirt.gz
exit

---

Reboot and try it out.

Thanks Klaus,

So, evdev is a catch all that won't work for authenticating an encrypted partition? I've rerun the OS to the USB stick w/o the encryption and now there's no requirement for the other KB. Just the same, I running the above to clear up any problem. We'll check back.

Thanks again,
Gary

OK Klaus,
[ 21.717] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[ 21.717] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 21.717] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 21.717] (**) Logitech USB Receiver: always reports core events
[ 21.717] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event2"
[ 21.717] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc505
[ 21.717] (--) evdev: Logitech USB Receiver: Found keys
[ 21.717] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 21.717] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 9)
[ 21.718] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event3)
[ 21.718] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
[ 21.718] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
[ 21.718] (II) Using input driver 'evdev' for 'Logitech USB Receiver'
[ 21.718] (**) Logitech USB Receiver: always reports core events
[ 21.718] (**) evdev: Logitech USB Receiver: Device: "/dev/input/event3"
[ 21.718] (--) evdev: Logitech USB Receiver: Vendor 0x46d Product 0xc505
[ 21.718] (--) evdev: Logitech USB Receiver: Found 20 mouse buttons
[ 21.718] (--) evdev: Logitech USB Receiver: Found scroll wheel(s)
[ 21.718] (--) evdev: Logitech USB Receiver: Found relative axes
[ 21.718] (--) evdev: Logitech USB Receiver: Found x and y relative axes
[ 21.718] (--) evdev: Logitech USB Receiver: Found keys
[ 21.718] (II) evdev: Logitech USB Receiver: Configuring as mouse
[ 21.718] (II) evdev: Logitech USB Receiver: Configuring as keyboard
[ 21.718] (II) evdev: Logitech USB Receiver: Adding scrollwheel support
[ 21.718] (**) evdev: Logitech USB Receiver: YAxisMapping: buttons 4 and 5
[ 21.718] (**) evdev: Logitech USB Receiver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 21.718] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: KEYBOARD, id 10)
[ 21.718] (II) evdev: Logitech USB Receiver: initialized for relative axes.
[ 21.719] (**) Logitech USB Receiver: (accel) keeping acceleration scheme 1
[ 21.719] (**) Logitech USB Receiver: (accel) acceleration profile 0
[ 21.719] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
[ 21.719] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
[ 21.719] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
[ 21.720] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:4002 (/dev/input/event4)
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: Applying InputClass "evdev keyboard catchall"
[ 21.720] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:4002'
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: always reports core events
[ 21.720] (**) evdev: Logitech Unifying Device. Wireless PID:4002: Device: "/dev/input/event4"
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Vendor 0x46d Product 0xc52b
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found 1 mouse buttons
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found scroll wheel(s)
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found relative axes
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Forcing relative x/y axes to exist.
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found absolute axes
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Forcing absolute x/y axes to exist.
[ 21.720] (--) evdev: Logitech Unifying Device. Wireless PID:4002: Found keys
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Configuring as mouse
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Configuring as keyboard
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: Adding scrollwheel support
[ 21.720] (**) evdev: Logitech Unifying Device. Wireless PID:4002: YAxisMapping: buttons 4 and 5
[ 21.720] (**) evdev: Logitech Unifying Device. Wireless PID:4002: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 21.720] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:4002" (type: KEYBOARD, id 11)
[ 21.720] (II) evdev: Logitech Unifying Device. Wireless PID:4002: initialized for relative axes.
[ 21.720] (WW) evdev: Logitech Unifying Device. Wireless PID:4002: ignoring absolute axes.
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: (accel) keeping acceleration scheme 1
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration profile 0
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration factor: 2.000
[ 21.720] (**) Logitech Unifying Device. Wireless PID:4002: (accel) acceleration threshold: 4

Thanks,
Gary

This is the new output, piping less thru grep on Logitech:

And then there's the new lsmod:

Module Size Used by
parport_pc 23972 0
ppdev 4167 0
lp 6185 0
parport 21928 3 lp,ppdev,parport_pc
ipv6 212138 16
i915 430125 3
drm_kms_helper 20665 1 i915
bnep 7279 2
rfcomm 23249 10
ath3k 4538 0
btusb 8785 0
bluetooth 143972 25 bnep,ath3k,btusb,rfcomm
coretemp 4518 0
kvm_intel 109899 0
kvm 275162 1 kvm_intel
wmi 6035 0
crc32_pclmul 2177 0
serio_raw 3206 0
arc4 1463 2
ath9k 63510 0
ath9k_common 1456 1 ath9k
ath9k_hw 330565 2 ath9k_common,ath9k
ath 10993 3 ath9k_common,ath9k,ath9k_hw
mac80211 347664 1 ath9k
cfg80211 319430 3 ath,ath9k,mac80211
snd_hda_codec_hdmi 22332 1
e1000e 121204 0
snd_hda_codec_realtek 22017 1
joydev 6659 0
snd_hda_intel 24570 4
snd_hda_codec 90020 3 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_i ntel
lpc_ich 10929 0
ptp 5855 1 e1000e
pps_core 4891 1 ptp
i2c_i801 11125 0
hid_logitech_dj 7966 0

I'm not sure if the code changes much. As an IT student, I'd be interested in your opinions. I mean I can tell that the wired Kb is unplugged and Santana's playing on the disc drive. Well, not by name.
The new directory is there and the renamed file. Copied and pasted to a root terminal.
Still, wonder why the encrpted persistent partition made any difference in the Kb?
Gotta go study Windows (barf), A+ scheduled - 15July, 801 @9:30, 802 @ 1300.
I aced a college level UNIX Shell scripting course, way back when. Ran SunOs and early Solaris for years. It's coming back to me slowly.

Thanks for all your help and tuition,
Gary

If you do not use an encrypted overlay you do not need the modified minirt.gz.