No usb detect after kernel update

English Hardware
1

Sorry for my english, just in case.

I’m using openSUSE 11.2 in my desktop pc (mb asus m4a78-em), and is the second time I deal with this problem. The first time, I simply did a format, I installed fedora and then I reinstalled opensuse (because the usb neither is detect in the installation process, in opensuse).

Now, I don’t want to do that again.

I just did a clean install and then I updated all packages, among them was the kernel. (Note, I SUPOSE the kernel update is the problem, but quietly can be the kde update, I don’t know).

The problem itself is opensuse can’t detect any usb device, among then are my wireless usb kit (mouse, keyboard). Currently I only have this input device (also a usb mouse, so I can’t do anything in opensuse), but I think I will have borrow a ps2 keyboard, at least.

The actual kernel is 2.6.31.12-0.2. In the grub, the usb works. When the first loading screen appears, all leds are turned off.

I know it is little information, but it’s this I can give for now. Let me know if I should give more.
Any ideas? How I could solve the problem from a LiveCD?

2

You say that the system does not detect any USB devices. How do you know? Did you run

lsusb

and when yes, show us the output, and when no please do so and show us the output.

3

Also post output of:


lsmod | grep usb
lsmod | grep hci
4

On some PCs it is necessary to go into the BIOS and change the USB setting to “legacy mode”.

5

Well, I think I’ve a weird problem. I discovered the usb is detected, but ~3 minutes after the system is initialized (desktop is displayed). So I have to wait until the wireless reciever turn on the leds, to write anything in the console. (remember, I only have this usb wireless kit…). This happens from the last update, before never happened.

lsusb: (it took a while to display the answer)


Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 045e:00f1 Microsoft Corp.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

the

lsmod | grep usb
lsmod | grep hci

It gave me no answer. It seems the system ignore these comand.

And the legacy usb support from bios, didn’t change anything.

6

If you are confident you can correlate this to a specific update, then write a bug report on openSUSE. Guidance is here: Submitting Bug Reports - openSUSE … this will bring the problem to the attention of the kernel ?? packagers for SuSE-GmbH who may know what caused this to happen.

7

It is strange indeed. The system sees only the 7 USB buses, but except on bus 4 (where it sees some unspecified Microsoft Corp. device) it sees nothing.

You say that all starts working after a few minutes. Does the lsusb give more information then. And the same for the lsmod ones?

And as oldcpu sys, it seems that it is very important to find out what that last update was about. Was is from the Applet, or something different? Was a kernel update included? You see, a lot of questions, but the earlier we ask, the beter you may still remember what you did.

8

It’s easy to remember what I did before the problem, because I did only a few things. After the last clean installation, I enabled some community repos (vlc, packman, ooo, mozilla, kde community and backports, ati), I installed all necesary, and then I did and update. Kde was updated to 4.3.5, firefox to 3.5.9, and I think a lot of libraries were up to date too. All I did, I did it with yast.
When all was installed, I had to do a reboot, because the display drivers needed it. Then, when I was in the desktop again, I did realize the problem was here (again!).

Today, I did some light tests. I plugged a usb mouse (wired) and the system took the same 2-3 minutes, to enable it. Then, I plugged a WD passport, and the system recognized it inmediately. So, I don’t understand what’s the matter here.

I think the lsusb it’s fine, because I only have one usb port used, with the ms wireless 2000.

For me the key is the kernel update, I can’t believe kde or multimedia libraries can do this with the usb. Obviously, it’s a personal thought, I can be wrong.

Finally, sorry if I seem too rude or crude, but English isn’t my natural language, I’m doing the best I can.

9

To begin with your english is quite adaquate and your description is very clear to me.

I agree that this can not be multimedia or KDE updates. It is kernel or very near to it. You could go back to the kernel on the DVD I suppose. And when that one functions properly a bug report would be justified (as oldcpu allready suggested).

BTW, did you try to see with dmesg what happens in those three minutes you are waiting?

10

I uploaded dmseg to a google doc, is too long to post it here.

dmseg

I had never used this command, but it has an understandable output. You can see, when


[28.553560] wlan0: authenticate with AP

I think I’m already in desktop. To the


[165.752735] generic-usb 0003:045E:00F1.0002: input,hidraw1: USB HID v1.11 Mouse [Microsft Microsoft Wireless Desktop Receiver 3.1A] on usb-0000:00:12.1-1/input1

there are 1’ 30’’ (well, not so much as I thought). Then I plugged an usb mouse, it took a bit more than a minute to be useful.

If I can come back to old kernel, i’ll try to put the system in the same conditions than now, to replicate the problem. You see, I can’t sure the problem is the new kernel.

11

Dah… obviously, 1’ 30’’ =/= 130 sec, little mistake.
:eek:

12

I see a lot of

   46.805021] usb 2-1: device descriptor read/64, error -110

also for 5-1. To me it looks as if the communication times out and retries, but that is only a guess. It is a bit (maybe even far) beyond my understanding.

You could try to install the kernel from the install DVD.
In YaST > Software > Repositories enable the cd:/// one and then YaST > software > Software Management. Search for kernel and use the >Verions tab below to see what provides what. When you install the one from the DVD (choose the same type as you have), it is possible that it is installed without removing the other (newer) one. When that is the case, yoy will have more entriees in your GRUB menu and can then boot with boot kernels at your liking. That would be nice of course.

When in doubt during this installation, please first ask here.

And do not forget to disable the DVD repos after the install, else the DVD is asked for at every software management task.

13

Well, well, well… Now, by the moment at least, I can say the problem is gone. Against my will, I had to reinstall the system again. But now I’ve been very carefull with enable the community repos I needed, because I had the “hunch” that the fglrx driver was causing the problem.

As I said, before enabling all the needed repos, I did a general update (kde, multimedia, firefox, amarok, kernel…) and I installed some more applications (fglrx, libraries…). All, at the same time. And I think it’s clear that this caused the problem.

I can’t explain technically, but it seems the fglrx driver compiles (it may not be “compile” the exact word, but it serves) to a determinate kernel version, when you are installing it. So, when I installed the fglrx drivers, it did over the old kernel. And then, at the same session (or not!), the kernel version was updated. When I rebooted, the system failed. The problem wasn’t solved with reinstalling the fglrx over the new kernel, I tried it. When the process not done in the correct order, I think the damage can be fixed, only, by reinstalling the system.

I think that was the root of the trouble. How was the usb affected? Well, I don’t know. But at least this thread will be a record for that.

So, the right form to do a clean install, is update the kernel, reboot, and then enable to the ati repo, and install the fglrx. So easy like that (but you must know before the headaches…)

Thanks to all people interested in help, i’m very grateful with them.

Regards

14

You arer welcome.

And thanks for sharing your solution with us.