SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I recently put together a system using the asus m4n68t-m v2 board, i'm currently running SW 13.37, i'm using a wireless usb keyboard and mouse, and whenever i start up Slackware i find that i have to unplug and then plug back in again the wireless receiver to get the keyboard and mouse to work, anyone know why that is?
In dmesg its saying that is it unable to enumerate device, and I also see a message that goes something like this "unable to register device on port 3".USb
I've had this problem with several USB devices and a couple of motherboards. I've come to the conclusion that it's something between the device, the kernel and the USB chipset/ports/BIOS. Does not happen with all motherboards/devices/chipsets. Usually you can get around this by not mixing USB 1.x and USB 2.0 devices on the same bus. Or force loading ehci-hcd before uhci-hcd (IIRC Slackware has done this for a while now), or disable ehci_hcd for faulty USB 2.0 ports.
Or's are because it depends on the USB peripheral, and the USB chipset.
It'll be a trial and error to narrow down the non cooperating bus/device. I'd start with just the keyboard mouse plugged in, and see which (if any) ports are having fits.
I've had this problem with several USB devices and a couple of motherboards. I've come to the conclusion that it's something between the device, the kernel and the USB chipset/ports/BIOS. Does not happen with all motherboards/devices/chipsets. Usually you can get around this by not mixing USB 1.x and USB 2.0 devices on the same bus. Or force loading ehci-hcd before uhci-hcd (IIRC Slackware has done this for a while now), or disable ehci_hcd for faulty USB 2.0 ports.
Or's are because it depends on the USB peripheral, and the USB chipset.
It'll be a trial and error to narrow down the non cooperating bus/device. I'd start with just the keyboard mouse plugged in, and see which (if any) ports are having fits.
Thanks for the advice, hopefully your suggestions will help.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.