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/023667.html | 87 +++++++++++++++++++++++++++++++ 1 file changed, 87 insertions(+) create mode 100644 zarb-ml/mageia-dev/2013-March/023667.html (limited to 'zarb-ml/mageia-dev/2013-March/023667.html') diff --git a/zarb-ml/mageia-dev/2013-March/023667.html b/zarb-ml/mageia-dev/2013-March/023667.html new file mode 100644 index 000000000..312b27c80 --- /dev/null +++ b/zarb-ml/mageia-dev/2013-March/023667.html @@ -0,0 +1,87 @@ + + + + [Mageia-dev] USB Keyboard disabled in current stage1 + + + + + + + + + +

[Mageia-dev] USB Keyboard disabled in current stage1

+ Thierry Vignaud + thierry.vignaud at gmail.com +
+ Wed Mar 20 21:21:35 CET 2013 +

+
+ +
On 20 March 2013 20:47, AL13N <alien at rmail.be> wrote:
+>> > 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 ?
+>
+> 1. since ages already, modprobe accepts with - or with _ it makes no
+> difference,
+
+You know we don't use modprobe in stage1, do you?
+
+ + + + + + + + + + + + + + + + +
+

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