Hello all,
I have been using linux-2.6.16.24 for development.
However, when I boot a sustem that uses a Dell USB
keyboard with a hub built into a Dell monitor, there
are continuous keyboard disconnect messages until
I exercise ^S/^Q. Then, everything is fine. I
thought maybe there was a bug that had been fixed
in later versions so I built and installed Linux-2.6.22.1.
The required usbhid.ko doesn't build, even though it
is enabled in ".config."
CONFIG_USB_DABUSB=m
# USB devices
CONFIG_SND_USB_AUDIO=m
CONFIG_SND_USB_USX2Y=m
# CONFIG_SND_USB_CAIAQ is not set
# USB Input Devices
CONFIG_USB_HID=m
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
CONFIG_USB_HIDDEV=y
# USB HID Boot Protocol drivers
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
# USB support
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
# Miscellaneous USB options
CONFIG_USB_DEVICEFS=y
CONFIG_USB_DEVICE_CLASS=y
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_SUSPEND is not set
# CONFIG_USB_OTG is not set
# USB Host Controller Drivers
CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_SPLIT_ISO=y
CONFIG_USB_EHCI_ROOT_HUB_TT=y
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_EHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_ISP116X_HCD=m
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=m
CONFIG_USB_SL811_HCD=m
CONFIG_USB_SL811_CS=m
# USB Device Class drivers
CONFIG_USB_ACM=m
CONFIG_USB_PRINTER=m
Also, the following errors occur when building the kernel:
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/linux/compile.h
MODPOST vmlinux
WARNING: arch/i386/kernel/built-in.o(.text+0xfca1): Section mismatch: reference to .init.data:trampoline_end (between 'setup_trampoline' and 'cpu_coregroup_map')
WARNING: arch/i386/kernel/built-in.o(.text+0xfca9): Section mismatch: reference to .init.data:trampoline_data (between 'setup_trampoline' and 'cpu_coregroup_map')
WARNING: arch/i386/kernel/built-in.o(.text+0xfcb3): Section mismatch: reference to .init.data:trampoline_data (between 'setup_trampoline' and 'cpu_coregroup_map')
WARNING: arch/i386/kernel/built-in.o(.exit.text+0x26): Section mismatch: reference to .init.text: (between 'cache_remove_dev' and 'ffh_cstate_exit')
WARNING: arch/i386/kernel/built-in.o(.data+0xe20): Section mismatch: reference to .init.text: (between 'thermal_throttle_cpu_notifier' and 'mtrr_mutex')
WARNING: kernel/built-in.o(.text+0x1b582): Section mismatch: reference to .init.text: (between 'kthreadd' and 'init_waitqueue_head')
Kernel: arch/i386/boot/bzImage is ready (#1)
Building modules, stage 2.
MODPOST 1258 modules
WARNING: drivers/net/sis900.o(.text+0x4b8): Section mismatch: reference to .init.text:sis900_mii_probe (between 'sis900_probe' and 'sis900_default_phy')
WARNING: drivers/net/sunhme.o(.text+0x2f49): Section mismatch: reference to .init.text: (between 'happy_meal_pci_probe' and 'happy_meal_pci_remove')
Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips).
My book : http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
On Wed, 15 Aug 2007, linux-os (Dick Johnson) wrote:
> I thought maybe there was a bug that had been fixed in later versions so
> I built and installed Linux-2.6.22.1. The required usbhid.ko doesn't
> build, even though it is enabled in ".config."
Could you plase send me your full .config? The usbhid module builds just
fine, please doble check on your side.
Thanks,
--
Jiri Kosina
On Thu, 16 Aug 2007, Jiri Kosina wrote:
> On Wed, 15 Aug 2007, linux-os (Dick Johnson) wrote:
>
>> I thought maybe there was a bug that had been fixed in later versions so
>> I built and installed Linux-2.6.22.1. The required usbhid.ko doesn't
>> build, even though it is enabled in ".config."
>
> Could you plase send me your full .config? The usbhid module builds just
> fine, please doble check on your side.
>
> Thanks,
>
> --
> Jiri Kosina
>
Okay. I found what was different. It does actually build, but it
is now put into a completely different directory,
/lib/modules/2.6.22.1/kernel/drivers/hid/usbhid, and requires
/lib/modules/2.6.22.1/kernel/drivers/input/ff-memless.ko
to be installed before it can be. None of this is documented
and it makes upgrading extremely difficult, expecially when a
keyboard won't work anymore.
BYW, it did fix the problem with the old driver.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.22.1 on an i686 machine (5588.29 BogoMips).
My book : http://www.AbominableFirebug.com/
_
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
On Thu, 16 Aug 2007, linux-os (Dick Johnson) wrote:
> Okay. I found what was different. It does actually build, but it is now
> put into a completely different directory,
> /lib/modules/2.6.22.1/kernel/drivers/hid/usbhid, and requires
> /lib/modules/2.6.22.1/kernel/drivers/input/ff-memless.ko to be installed
> before it can be.
Only if you enabled force feedback for HID devices in your menuconfig. And
if you did so, it perfectly makes sense that the force-feedback input
module must be loaded.
> None of this is documented and it makes upgrading extremely difficult,
> expecially when a keyboard won't work anymore.
1) what strange distro/environment do you use that the usbhid driver is
not loaded automatically when you plug the keyboard in?
2) even if your module autoloading is that much broken, you can always ssh
to the box or attach PS/2 keyboard and modprobe usbhid ... that works
no matter which directory keeps the driver
There is nothing to be documented there, we don't document which directory
holds which driver.
> BYW, it did fix the problem with the old driver.
Good to hear, thanks.
--
Jiri Kosina