2.6.31.19.32-generic killed my USB mouse

[Electric Bill]

This morning I noticed a new update available (2.6.31.19.32-generic) so I clicked on it.
I had just finished getting a new install of Karmic 64 dialed in on my HTPC - the Biostar in my sig below with an AMD 4670 video card.
When I rebooted my USB mouse was not working so I tried another one with the same results.
The only mouse that worked was an old PS/2 unit.

This is what was installed:
Commit Log for Fri Feb 5 11:23:47 2010


Upgraded the following packages:
linux-generic (2.6.31.17.30) to 2.6.31.19.32
linux-headers-generic (2.6.31.17.30) to 2.6.31.19.32
linux-image-generic (2.6.31.17.30) to 2.6.31.19.32

Installed the following packages:
linux-headers-2.6.31-19 (2.6.31-19.56)
linux-headers-2.6.31-19-generic (2.6.31-19.56)
linux-image-2.6.31-19-generic (2.6.31-19.56)

Commit Log for Fri Feb 5 11:22:32 2010


Upgraded the following packages:
linux-libc-dev (2.6.31-17.54) to 2.6.31-19.56

It was working with 2.6.31.17.30 but now the only kernel that works correctly is 2.6.31-14.

Anyone else have this problem or a solution?
Can I just uninstall 2.6.31-19.56 and reinstall 2.6.31-17.54 and if so where would I find it?

Bill

[poldie]

This morning I noticed a new update available (2.6.31.19.32-generic) so I clicked on it.
I had just finished getting a new install of Karmic 64 dialed in on my HTPC - the Biostar in my sig below with an AMD 4670 video card.
When I rebooted my USB mouse was not working so I tried another one with the same results.
The only mouse that worked was an old PS/2 unit.

This is what was installed:
Commit Log for Fri Feb 5 11:23:47 2010


Upgraded the following packages:
linux-generic (2.6.31.17.30) to 2.6.31.19.32
linux-headers-generic (2.6.31.17.30) to 2.6.31.19.32
linux-image-generic (2.6.31.17.30) to 2.6.31.19.32

Installed the following packages:
linux-headers-2.6.31-19 (2.6.31-19.56)
linux-headers-2.6.31-19-generic (2.6.31-19.56)
linux-image-2.6.31-19-generic (2.6.31-19.56)

Commit Log for Fri Feb 5 11:22:32 2010


Upgraded the following packages:
linux-libc-dev (2.6.31-17.54) to 2.6.31-19.56

It was working with 2.6.31.17.30 but now the only kernel that works correctly is 2.6.31-14.

Anyone else have this problem or a solution?
Can I just uninstall 2.6.31-19.56 and reinstall 2.6.31-17.54 and if so where would I find it?

Bill


I'm getting problems. I got an update, so I installed. It just hangs. I click on details and it's saying:

could not find /boot/grub.menu.lst. WOuld you like it generated for you? (y/n)

I don't know - you tell me! I don't want grub screwed up so my pc doesn't boot if that's what it's asking. At the same time this pops up, there's a `restart required` box. Well, hang on - I don't really want to restart while the install is half complete, do I?

Above the y/n choice I can see that this is about linux-image 2.6.31-19-generic (2.6.31-19.56). So perhaps this update wasn't tested properly.


I've just done all this and rebooted and then checked for updates again and I'm back where I started. It's all a bit microsoft, isn't it?

I'm on ubuntu 9.10 64 bit.

[Electric Bill]

Well it appears to be a video conflict with me.

This is on an HTPC so I'm using a Samsung 32" HDTV as a monitor.
I've had problems with this version (9.10 64 bit) right from the start and I have to momentarily turn the TV off & on right after the grub menu for Ubuntu to continue loading.
I filed a report on this back in November.

When the problem happened this morning after a fresh installation I finally got it to work by switching video cables from HDMI to VGA.
Then I ran into the USB problems.

This evening I tried the HDMI cable again and after doing the on/off trick I could hear hard drive activity so when it paused I hit enter and then typed in my password.
Then I switched to my gaming computer to see if I could see the HDMI computer on the network and sure enough it was accessible so I know that it did complete the boot.

If I boot in recovery mode the menu will appear for a few seconds and then I see the message "Could not access PID file for nmbd" and I have to Ctrl-Alt Del to restart.
This happens with the 2.6.31-19 and 2.6.31-17 images but as I mentioned earlier it will work with the 2.6.31-14 image.

I have this release on 3 machines right now but haven't updated the kernel on the other 2.
The gaming rig also uses the HDTV and has to be switched off and on to boot but the rig in the bedroom doesn't have that problem.
It's using a Samsung 22" widescreen monitor/TV.

I've also posted in another thread (http://ubuntuforums.org/showthread.php?p=8780415#post8780415) about issues with Hulu.
The early release had issues after a flash update which caused Hulu and in some cases any flash applications to not stream.

I found that the later versions of 9.10 have fixed this issue.

Bill

[yavoh]

This morning I noticed a new update available (2.6.31.19.32-generic) so I clicked on it.
I had just finished getting a new install of Karmic 64 dialed in on my HTPC - the Biostar in my sig below with an AMD 4670 video card.
When I rebooted my USB mouse was not working so I tried another one with the same results.
The only mouse that worked was an old PS/2 unit.

This is what was installed:
Commit Log for Fri Feb 5 11:23:47 2010


Upgraded the following packages:
linux-generic (2.6.31.17.30) to 2.6.31.19.32
linux-headers-generic (2.6.31.17.30) to 2.6.31.19.32
linux-image-generic (2.6.31.17.30) to 2.6.31.19.32

Installed the following packages:
linux-headers-2.6.31-19 (2.6.31-19.56)
linux-headers-2.6.31-19-generic (2.6.31-19.56)
linux-image-2.6.31-19-generic (2.6.31-19.56)

Commit Log for Fri Feb 5 11:22:32 2010


Upgraded the following packages:
linux-libc-dev (2.6.31-17.54) to 2.6.31-19.56

It was working with 2.6.31.17.30 but now the only kernel that works correctly is 2.6.31-14.

Anyone else have this problem or a solution?
Can I just uninstall 2.6.31-19.56 and reinstall 2.6.31-17.54 and if so where would I find it?

Bill

Same for me! I fixed it by booting back into the old 2.6.31-17. I don't know what caused it, nor can I find a launchpad bug.

[Electric Bill]

OK I just tried this in Synaptic:
Reinstalled the following packages:
linux-image-2.6.31-17-generic (2.6.31-17.54)

Now I can boot with 2.6.31-17 and 2.6.31-19 and USB devices are working normally.
Go figure.

I'm editing out the Vista comment I made earlier. :P

Bill