Am 18.10.2013 05:54, schrieb Dale: > Walter Dnes wrote: >> On Thu, Oct 17, 2013 at 04:40:52PM -0500, Dale wrote >>> Well, this is interesting. I swapped out the mobo. First, it has the >>> UEFI BIOS thing. That was interesting for sure. I'm not complaining >>> but not used to it and wasn't expecting it either. Second, it works >>> except for the third part. Third thing is, no mouse worky. It works in >>> the BIOS but not in the OS. I have gpm set to start and it doesn't work >>> in a console or a GUI. I tried everything I can think of, no mouse. I >>> had to swap again. I'm back to my old mobo. Here is the kicker. I >>> plugged the USB mouse into the old mobo, it works just fine. It works >>> in KDE, console etc. It just works. The only kernel change I made was >>> for the chipset on the mobo. I left the USB stuff alone. >> I've run into this in the past. The USB 2.0 drivers are *SUPPOSED* to >> provide support for lowspeed USB 1.X devices, like mice and keyboards. >> But it doesn't always work that way. There is direct USB 1.X driver >> support in the kernel. In "make menuconfig", got to... >> >> Device Drivers ---> >> [*] USB support ---> >> < > OHCI HCD support >> < > UHCI HCD (most Intel and VIA) support >> >> I don't see any mention in your message whether the motherboard cpu is >> AMD or Intel. Generally, build UHCI for Intel+VIA, OHCI for AMD. Try >> it out and see what happens. >> > > Mine is AMD based. I have this right now but tried every other version > I could find too. > > <*> xHCI HCD (USB 3.0) support > <*> EHCI HCD (USB 2.0) support > <*> OHCI HCD support > [*] Generic OHCI driver for a platform device
there you go. platform driver. Take that one out. Make the rest modules. Amd board? kill uhci while you are at it. > <*> Generic EHCI driver for a platform device > <*> UHCI HCD (most Intel and VIA) support > > Under USB HID support, I have this enabled: > > <*> USB HID transport layer > [*] PID device support > [*] /dev/hiddev raw HID device support > > > This may help: > > root@fireball /usr/src/linux # cat .config | grep -i hid | grep =y > CONFIG_HID=y > CONFIG_HIDRAW=y > CONFIG_UHID=y > CONFIG_HID_GENERIC=y > CONFIG_HID_A4TECH=y > CONFIG_HID_APPLE=y > CONFIG_HID_BELKIN=y > CONFIG_HID_CHERRY=y > CONFIG_HID_CHICONY=y > CONFIG_HID_CYPRESS=y > CONFIG_HID_EZKEY=y > CONFIG_HID_KYE=y > CONFIG_HID_GYRATION=y > CONFIG_HID_KENSINGTON=y > CONFIG_HID_LOGITECH=y > CONFIG_HID_MICROSOFT=y > CONFIG_HID_MONTEREY=y > CONFIG_HID_NTRIG=y > CONFIG_HID_PANTHERLORD=y > CONFIG_HID_PETALYNX=y > CONFIG_HID_SAMSUNG=y > CONFIG_HID_SONY=y > CONFIG_HID_SUNPLUS=y > CONFIG_HID_TOPSEED=y > CONFIG_USB_HID=y > CONFIG_HID_PID=y > CONFIG_USB_HIDDEV=y > root@fireball /usr/src/linux # > > Right before I swapped back, I tried them all. ;-) Here is some more info: > > root@fireball /usr/src/linux # cat .config | grep -i hci > CONFIG_SATA_AHCI=y > # CONFIG_SATA_AHCI_PLATFORM is not set > # CONFIG_SATA_ACARD_AHCI is not set > # CONFIG_FIREWIRE_OHCI is not set > CONFIG_USB_ARCH_HAS_OHCI=y > CONFIG_USB_ARCH_HAS_EHCI=y > CONFIG_USB_ARCH_HAS_XHCI=y > CONFIG_USB_XHCI_HCD=y > # CONFIG_USB_XHCI_HCD_DEBUGGING is not set > CONFIG_USB_EHCI_HCD=y > CONFIG_USB_EHCI_ROOT_HUB_TT=y > CONFIG_USB_EHCI_TT_NEWSCHED=y > CONFIG_USB_EHCI_PCI=y > CONFIG_USB_OHCI_HCD=y > CONFIG_USB_OHCI_HCD_PLATFORM=y > CONFIG_USB_EHCI_HCD_PLATFORM=y > # 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=y > CONFIG_PROVIDE_OHCI1394_DMA_INIT=y > root@fireball /usr/src/linux # > > > My thinking, there is some driver that is different from my old mobo to > this new mobo and I'm missing it or just missing something really > simple. I went by the Debian HCL site but maybe something got changed. > If I could boot the Sysrescue stick then I could likely figure it out > from that. I'm going to update that stick before the next test. > > Keep in mind, for me to test anything, I have to swap mobos again. > Naturally I don't want to do that any more times than I have to. Each > times runs the risk of me messing up something. :/ > > Thanks much to all. > > Dale > > :-) :-) >
