From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-dev/2013-March/023655.html | 76 +++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-March/023655.html (limited to 'zarb-ml/mageia-dev/2013-March/023655.html') diff --git a/zarb-ml/mageia-dev/2013-March/023655.html b/zarb-ml/mageia-dev/2013-March/023655.html new file mode 100644 index 000000000..0f29c0bbc --- /dev/null +++ b/zarb-ml/mageia-dev/2013-March/023655.html @@ -0,0 +1,76 @@ + + + + [Mageia-dev] USB Keyboard disabled in current stage1 + + + + + + + + + +

[Mageia-dev] USB Keyboard disabled in current stage1

+ Frank Griffin + ftg at roadrunner.com +
+ Wed Mar 20 17:50:06 CET 2013 +

+
+ +
On 03/20/2013 12:34 PM, Frank Griffin wrote:
+> I'm confused.
+>
+> I see your point: modules.dep and the actual driver module filenames 
+> in /lib/modules use dashes in the names, while usbtable uses 
+> underscores.  So why does lsmod show underscores instead of dashes ?
+>
+> Also, why do the two differ ?  If the kernel package, which one would 
+> think is definitive, uses dashes, why does ldetect-lst use underscores ?
+>
+Oh, one other thing.  On the working system, harddrake shows two 
+keyboard devices: a USB keyboard (PCI 0x1226/0x0034) and a LiteON USB 
+Keyboard (PCI 0x04ca/0x0022).  Neither of these appear in usbtable.  Or 
+is the problem with *any* USB device because of the ehci-*** modules 
+that are needed ?
+
+ + + + + + + + +
+

+ +
+More information about the Mageia-dev +mailing list
+ -- cgit v1.2.1