On Sat, Nov 1, 2008 at 1:48 PM, Karl Larsen <firstname.lastname@example.org> wrote:
> My Intrepid first boot with a GeForce6100 got those exact results. I
> fear your in the same boat with me. We will just have to wait in Hardy
> until someone has time to fix the kernel and Intrepid.
I didn't have that problem, fortunately. I had other problems -
including having to run dpkg -configure -a after rebooting the box in
the middle of a distribution upgrade to intrepid earlier today. Seems
that for some reason first kded went down (doing the adept_updater in
kde4.1 on hardy) and then my screen went down while it was configuring
packages. I heard the drive going on and off but there was no other
confirmation that there was active things being done.
And then I had to run aptitude update and aptitude upgrade a few times
to get all the packages installed for the distrbution upgrade. I had
troubles with amarok (fixed now) but it removed a lot of kde in the
. I lost ksirc (no candidate for install) and replaced that
task with konversation. I also had to reload amarok and a few other
things. This will probably get sorted out in the process over the next
But the nvidia was a breeze, once all the packages got downloaded and
everything was configured. It got 177 right off and installed it.
It does fix two nagging problems that I had reported earlier on this
list - first, I don't have to do that extra step of insmod'ing the
driver manually, since the machine no longer boots in low-resolution
mode (although the resolution is a bit lower than I would like).
I also noticed that early on kde would not come up on the ubuntu
splash/login screen. Currently I am in gnome as a fallback position. I
will have to check to see if kde will start up - it probably did not
because not all of the updates were in place.
ubuntu-users mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users