*** This bug is a duplicate of bug 148586 ***
https://bugs.launchpad.net/bugs/148586
I'm marking it as duplicate of bug 148586, which appears to be the same
problem.
** Changed in: linux-restricted-modules-2.6.22 (Ubuntu)
Importance: Undecided = Medium
Status: New = Invalid
**
This happened to me too - it seemed that I lost a processor during the
upgrade to Gutsy, when in fact I just had to rearrange the new menu.lst
to default to generic instead of 386. I didn't notice the problem
until one of my applications (Java) reported it to me.
--
nvidia-glx-new installs 386
mewt:
I believe this comes about when linux-restricted-modules has been pulled up (by
default it will be installed). I'm searching around to see if I can find the
bug report that mentioned this...
--
nvidia-glx-new installs 386 kernel
https://bugs.launchpad.net/bugs/137758
You received this
might have been i had it uninstalled..but then again i think such a prob
should be fixed by having the appropriate linux-restricted modules
installed, not get a new one according to the kernel getting installed
--
nvidia-glx-new installs 386 kernel
https://bugs.launchpad.net/bugs/137758
You
mewt:
I've had a look but I can't find the bug (if there ever was one) where this was
mentioned in detail (Martin PItt briefly mentions the issue in
https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.20/+bug/99122/comments/5
). Basically because there is more than one
