As mentioned in a previous reply, I have only the kernel headers for
this new kernel. No generic kernel or modules for it. I also have two
Karmic partitions and just safe-upgraded and dist-upgraded both Karmic
partitions yet no -16 kernel or modules on either. One partition uses
the archives.ubuntu.com mirror and the other uses the 76.73.4.58 karmic
mirror. Anyone have any idea why only the header files are available on
two different mirror but not the kernel or modules. I usually just use
safe-upgrade and so far have gotten the -15 and all previous kernel,
modules, etc starting with the beta Karmic install. Appreciate any
help/suggestions as this is driving me crazy hoping the newa kernel will
solve some of m X window issue.
Thanks for any help/suggestions.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

> As mentioned in a previous reply, I have only the kernel headers for
> this new kernel. No generic kernel or modules for it. I also have two
> Karmic partitions and just safe-upgraded and dist-upgraded both Karmic
> partitions yet no -16 kernel or modules on either. *One partition uses
> the archives.ubuntu.com mirror and the other uses the 76.73.4.58 karmic
> mirror. *Anyone have any idea why only the header files are available on
> two different mirror but not the kernel or modules. I usually just use
> safe-upgrade and so far have gotten the -15 and all previous kernel,
> modules, etc starting with the beta Karmic install. *Appreciate any
> help/suggestions as this is driving me crazy hoping the newa kernel will
> solve some of m X window issue.

http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
has
linux-386_2.6.31.16.29_i386.deb
linux-generic-pae_2.6.31.16.29_i386.deb
linux-generic_2.6.31.16.29_amd64.deb
linux-generic_2.6.31.16.29_i386.deb
linux-image-386_2.6.31.16.29_i386.deb
linux-image-generic-pae_2.6.31.16.29_i386.deb
linux-image-generic_2.6.31.16.29_amd64.deb
linux-image-generic_2.6.31.16.29_i386.deb
linux-image-server_2.6.31.16.29_amd64.deb
linux-image-server_2.6.31.16.29_i386.deb
linux-image-virtual_2.6.31.16.29_amd64.deb
linux-image-virtual_2.6.31.16.29_i386.deb
linux-image_2.6.31.16.29_amd64.deb
linux-image_2.6.31.16.29_i386.deb
linux-server_2.6.31.16.29_amd64.deb
linux-server_2.6.31.16.29_i386.deb
linux-virtual_2.6.31.16.29_amd64.deb
linux-virtual_2.6.31.16.29_i386.deb
linux_2.6.31.16.29_amd64.deb
linux_2.6.31.16.29_i386.deb

I cannot access archives.ubuntu.com through either hostname or ip
(67.215.65.132). whether through http or ftp...

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

Tom H wrote:

As mentioned in a previous reply, I have only the kernel headers for
this new kernel. No generic kernel or modules for it. I also have two
Karmic partitions and just safe-upgraded and dist-upgraded both Karmic
partitions yet no -16 kernel or modules on either. One partition uses
the archives.ubuntu.com mirror and the other uses the 76.73.4.58 karmic
mirror. Anyone have any idea why only the header files are available on
two different mirror but not the kernel or modules. I usually just use
safe-upgrade and so far have gotten the -15 and all previous kernel,
modules, etc starting with the beta Karmic install. Appreciate any
help/suggestions as this is driving me crazy hoping the newa kernel will
solve some of m X window issue.


http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
has
linux-386_2.6.31.16.29_i386.deb
linux-generic-pae_2.6.31.16.29_i386.deb
linux-generic_2.6.31.16.29_amd64.deb
linux-generic_2.6.31.16.29_i386.deb
linux-image-386_2.6.31.16.29_i386.deb
linux-image-generic-pae_2.6.31.16.29_i386.deb
linux-image-generic_2.6.31.16.29_amd64.deb
linux-image-generic_2.6.31.16.29_i386.deb
linux-image-server_2.6.31.16.29_amd64.deb
linux-image-server_2.6.31.16.29_i386.deb
linux-image-virtual_2.6.31.16.29_amd64.deb
linux-image-virtual_2.6.31.16.29_i386.deb
linux-image_2.6.31.16.29_amd64.deb
linux-image_2.6.31.16.29_i386.deb
linux-server_2.6.31.16.29_amd64.deb
linux-server_2.6.31.16.29_i386.deb
linux-virtual_2.6.31.16.29_amd64.deb
linux-virtual_2.6.31.16.29_i386.deb
linux_2.6.31.16.29_amd64.deb
linux_2.6.31.16.29_i386.deb

I cannot access archives.ubuntu.com through either hostname or ip
(67.215.65.132). whether through http or ftp...


Thanks Tom, the archives.ubuntu.com wasn't the full sources.list entry
just the domain

I copied from it and it does work for me today. It is http in my list.
I do have main and all the rest in my list but nothing about
linux-meta. Not even sure what

it means or how to set up in sources.list. I suppose the puting:
deb http://76.73.4.58/ubuntu/pool/main/l/linux-meta/ in my sources.list
file would get me to
the latest kernels. I also noticed that there is a 2.6.32.6.6-generic
kernel image listed. Just
wondering why the usual mirrors don't have the kernel or modules but
have the headers.
Also concerned just what the significance, consequences of using the
linux-meta mirror
has. Could use some more elaboration on using the linux-meta mirror and
the newer kernels

on my Karmic 64 bit machine. Anybody?

Leonard
lenc5570@sbcglobal.net
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

>> http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
>> has
>> linux-386_2.6.31.16.29_i386.deb
>> linux-generic-pae_2.6.31.16.29_i386.deb
>> linux-generic_2.6.31.16.29_amd64.deb
>> linux-generic_2.6.31.16.29_i386.deb
>> linux-image-386_2.6.31.16.29_i386.deb
>> linux-image-generic-pae_2.6.31.16.29_i386.deb
>> linux-image-generic_2.6.31.16.29_amd64.deb
>> linux-image-generic_2.6.31.16.29_i386.deb
>> linux-image-server_2.6.31.16.29_amd64.deb
>> linux-image-server_2.6.31.16.29_i386.deb
>> linux-image-virtual_2.6.31.16.29_amd64.deb
>> linux-image-virtual_2.6.31.16.29_i386.deb
>> linux-image_2.6.31.16.29_amd64.deb
>> linux-image_2.6.31.16.29_i386.deb
>> linux-server_2.6.31.16.29_amd64.deb
>> linux-server_2.6.31.16.29_i386.deb
>> linux-virtual_2.6.31.16.29_amd64.deb
>> linux-virtual_2.6.31.16.29_i386.deb
>> linux_2.6.31.16.29_amd64.deb
>> linux_2.6.31.16.29_i386.deb

> Thanks Tom, the archives.ubuntu.com wasn't the full sources.list entry just
> the domain
> I copied from it and it does work for me today. It is http in my list.
> I do have main and all the rest in my list but nothing about linux-meta.
> *Not even sure what
> it means or how to set up in sources.list. *I suppose the puting:
> deb http://76.73.4.58/ubuntu/pool/main/l/linux-meta/ in my sources.list file
> would get me to
> the latest kernels. I also noticed that there is a 2.6.32.6.6-generic kernel
> image listed. *Just
> wondering why the usual mirrors don't have the kernel or modules but have
> the headers.
> Also concerned just what the significance, consequences of using the
> linux-meta mirror
> has. *Could use some more elaboration on using the linux-meta mirror and the
> newer kernels
> on my Karmic 64 bit machine. *Anybody?

Sorry, I wasn't suggesting that you add that long URL to your
"sources.list", only that you should try to install the kernel
appropriate to your hardware/setup by name.

The long URL is where the kernel sits on the repository server, which
you can find with
apt-cache show linux-image
or
apt-cache show linux-image-generic
or
apt-cache show linux-image-2.6.31-16.generic

There must be some naming problem. I did not think of comparing the
kernels in the repository that I use
us.archive.ubuntu.com
with the one above from 76.73.4.58

The 2.6.32.6... is for Lucid.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

>>> http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
>>> has
>>> linux-386_2.6.31.16.29_i386.deb
>>> linux-generic-pae_2.6.31.16.29_i386.deb
>>> linux-generic_2.6.31.16.29_amd64.deb
>>> linux-generic_2.6.31.16.29_i386.deb
>>> linux-image-386_2.6.31.16.29_i386.deb
>>> linux-image-generic-pae_2.6.31.16.29_i386.deb
>>> linux-image-generic_2.6.31.16.29_amd64.deb
>>> linux-image-generic_2.6.31.16.29_i386.deb
>>> linux-image-server_2.6.31.16.29_amd64.deb
>>> linux-image-server_2.6.31.16.29_i386.deb
>>> linux-image-virtual_2.6.31.16.29_amd64.deb
>>> linux-image-virtual_2.6.31.16.29_i386.deb
>>> linux-image_2.6.31.16.29_amd64.deb
>>> linux-image_2.6.31.16.29_i386.deb
>>> linux-server_2.6.31.16.29_amd64.deb
>>> linux-server_2.6.31.16.29_i386.deb
>>> linux-virtual_2.6.31.16.29_amd64.deb
>>> linux-virtual_2.6.31.16.29_i386.deb
>>> linux_2.6.31.16.29_amd64.deb
>>> linux_2.6.31.16.29_i386.deb
>
>> Thanks Tom, the archives.ubuntu.com wasn't the full sources.list entry just
>> the domain
>> I copied from it and it does work for me today. It is http in my list.
>> I do have main and all the rest in my list but nothing about linux-meta.
>> *Not even sure what
>> it means or how to set up in sources.list. *I suppose the puting:
>> deb http://76.73.4.58/ubuntu/pool/main/l/linux-meta/ in my sources.list file
>> would get me to
>> the latest kernels. I also noticed that there is a 2.6.32.6.6-generic kernel
>> image listed. *Just
>> wondering why the usual mirrors don't have the kernel or modules but have
>> the headers.
>> Also concerned just what the significance, consequences of using the
>> linux-meta mirror
>> has. *Could use some more elaboration on using the linux-meta mirror and the
>> newer kernels
>> on my Karmic 64 bit machine. *Anybody?
>
> Sorry, I wasn't suggesting that you add that long URL to your
> "sources.list", only that you should try to install the kernel
> appropriate to your hardware/setup by name.
>
> The long URL is where the kernel sits on the repository server, which
> you can find with
> apt-cache show linux-image
> or
> apt-cache show linux-image-generic
> or
> apt-cache show linux-image-2.6.31-16.generic
>
> There must be some naming problem. I did not think of comparing the
> kernels in the repository that I use
> us.archive.ubuntu.com
> with the one above from 76.73.4.58

The actual kernels are in
http://76.73.4.58/ubuntu/pool/main/l/linux/

The files in
http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
are virtual/meta packages but they are the ones that are installed and
they are the same as the
http://us.archive.ubuntu.com/pool/main/l/linux-meta/
ones.

Can you install linux-image or linux-image-generic (without any version number)?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--- On Sun, 12/6/09, Tom H <tomh0665@gmail.com> wrote:

snipped

> > Thanks Tom, the archives.ubuntu.com wasn't the full
> sources.list entry just
> > the domain
> > I copied from it and it does work for me today. It is
> http in my list.
> > I do have main and all the rest in my list but nothing
> about linux-meta.
> > *Not even sure what
> > it means or how to set up in sources.list. *I suppose
> the puting:
> > deb http://76.73.4.58/ubuntu/pool/main/l/linux-meta/ in my
> sources.list file
> > would get me to
> > the latest kernels. I also noticed that there is a
> 2.6.32.6.6-generic kernel
> > image listed. *Just
> > wondering why the usual mirrors don't have the kernel
> or modules but have
> > the headers.
> > Also concerned just what the significance,
> consequences of using the
> > linux-meta mirror
> > has. *Could use some more elaboration on using the
> linux-meta mirror and the
> > newer kernels
> > on my Karmic 64 bit machine. *Anybody?
>
> Sorry, I wasn't suggesting that you add that long URL to
> your
> "sources.list", only that you should try to install the
> kernel
> appropriate to your hardware/setup by name.
>
> The long URL is where the kernel sits on the repository
> server, which
> you can find with
> apt-cache show linux-image
> or
> apt-cache show linux-image-generic
> or
> apt-cache show linux-image-2.6.31-16.generic
>
> There must be some naming problem. I did not think of
> comparing the
> kernels in the repository that I use
> us.archive.ubuntu.com
> with the one above from 76.73.4.58
>
> The 2.6.32.6... is for Lucid.
>
Ahhh, I see said the blind man. It seems that linux-image and linux-image-generic were rmed somehow, probably when I purged and reinstalled
the -15 generic kernel and nvidia drivers trying to resolve the notorious Karmic low res graphics issue. I reinstalled the two and it also picked up the -16 generic kernel. Now am happy again.
Thanks for the help as it never occurred to me to reinstall them.

Leonard Chatagnier
lenc5570@sbcglobal.net



--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

--- On Sun, 12/6/09, Tom H <tomh0665@gmail.com> wrote:

> From: Tom H <tomh0665@gmail.com>
> Subject: Re: No New 2.6.31-16-generic Kernel-Why?
> To: ubuntu-users@lists.ubuntu.com
> Date: Sunday, December 6, 2009, 2:05 PM
> >>> http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
> >>> has
> >>> linux-386_2.6.31.16.29_i386.deb
> >>> linux-generic-pae_2.6.31.16.29_i386.deb
> >>> linux-generic_2.6.31.16.29_amd64.deb
> >>> linux-generic_2.6.31.16.29_i386.deb
> >>> linux-image-386_2.6.31.16.29_i386.deb
> >>> linux-image-generic-pae_2.6.31.16.29_i386.deb
> >>> linux-image-generic_2.6.31.16.29_amd64.deb
> >>> linux-image-generic_2.6.31.16.29_i386.deb
> >>> linux-image-server_2.6.31.16.29_amd64.deb
> >>> linux-image-server_2.6.31.16.29_i386.deb
> >>> linux-image-virtual_2.6.31.16.29_amd64.deb
> >>> linux-image-virtual_2.6.31.16.29_i386.deb
> >>> linux-image_2.6.31.16.29_amd64.deb
> >>> linux-image_2.6.31.16.29_i386.deb
> >>> linux-server_2.6.31.16.29_amd64.deb
> >>> linux-server_2.6.31.16.29_i386.deb
> >>> linux-virtual_2.6.31.16.29_amd64.deb
> >>> linux-virtual_2.6.31.16.29_i386.deb
> >>> linux_2.6.31.16.29_amd64.deb
> >>> linux_2.6.31.16.29_i386.deb
> >
> >> Thanks Tom, the archives.ubuntu.com wasn't the
> full sources.list entry just
> >> the domain
> >> I copied from it and it does work for me today. It
> is http in my list.
> >> I do have main and all the rest in my list but
> nothing about linux-meta.
> >> *Not even sure what
> >> it means or how to set up in sources.list. *I
> suppose the puting:
> >> deb http://76.73.4.58/ubuntu/pool/main/l/linux-meta/ in my
> sources.list file
> >> would get me to
> >> the latest kernels. I also noticed that there is a
> 2.6.32.6.6-generic kernel
> >> image listed. *Just
> >> wondering why the usual mirrors don't have the
> kernel or modules but have
> >> the headers.
> >> Also concerned just what the significance,
> consequences of using the
> >> linux-meta mirror
> >> has. *Could use some more elaboration on using
> the linux-meta mirror and the
> >> newer kernels
> >> on my Karmic 64 bit machine. *Anybody?
> >
> > Sorry, I wasn't suggesting that you add that long URL
> to your
> > "sources.list", only that you should try to install
> the kernel
> > appropriate to your hardware/setup by name.
> >
> > The long URL is where the kernel sits on the
> repository server, which
> > you can find with
> > apt-cache show linux-image
> > or
> > apt-cache show linux-image-generic
> > or
> > apt-cache show linux-image-2.6.31-16.generic
> >
> > There must be some naming problem. I did not think of
> comparing the
> > kernels in the repository that I use
> > us.archive.ubuntu.com
> > with the one above from 76.73.4.58
>
> The actual kernels are in
> http://76.73.4.58/ubuntu/pool/main/l/linux/
>
> The files in
> http://76.73.4.58/ubuntu/pool/main/l/linux-meta/
> are virtual/meta packages but they are the ones that are
> installed and
> they are the same as the
> http://us.archive.ubuntu.com/pool/main/l/linux-meta/
> ones.
>
> Can you install linux-image or linux-image-generic (without
> any version number)?
>

Already done as per my previous reply. I'm good.
Leonard Chatagnier
lenc5570@sbcglobal.net


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

> It seems that linux-image and linux-image-generic were rmed somehow,
> probably when I purged and reinstalled the -15 generic kernel and nvidia
> drivers trying to resolve the notorious Karmic low res graphics issue. I
> reinstalled the two and it also picked up the -16 generic kernel.*Now am
> happy again. Thanks for the help as it never occurred to me to reinstall
> them.

You're welcome.

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

On 12/06/2009 09:29 AM, Leonard Chatagnier wrote:
> As mentioned in a previous reply, I have only the kernel headers for
> this new kernel. No generic kernel or modules for it. I also have two
> Karmic partitions and just safe-upgraded and dist-upgraded both Karmic
> partitions yet no -16 kernel or modules on either. One partition uses
> the archives.ubuntu.com mirror and the other uses the 76.73.4.58 karmic
> mirror. Anyone have any idea why only the header files are available on
> two different mirror but not the kernel or modules. I usually just use
> safe-upgrade and so far have gotten the -15 and all previous kernel,
> modules, etc starting with the beta Karmic install. Appreciate any
> help/suggestions as this is driving me crazy hoping the newa kernel will
> solve some of m X window issue.
> Thanks for any help/suggestions.
>

Via Synaptic set your repository for "Main server" and try to update
(just standard Reload) and then System|Administration|Update...). I had
an issue on one machine (32bit of course) where the -16 didn't get
properly upgraded. The history shows:
Commit Log for Sat Dec 5 09:05:25 2009
Upgraded the following packages:
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
linux-libc-dev (2.6.31-15.50) to 2.6.31-16.52
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

Whereas a system that properly upgraded to -16 shows:
Commit Log for Sat Dec 5 13:09:39 2009
Upgraded the following packages:
linux-generic (2.6.31.15.28) to 2.6.31.16.29
linux-headers-386 (2.6.31.15.28) to 2.6.31.16.29
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-386 (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-386 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-386 (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

Even taking out the -386, I should have gotten:
Upgraded the following packages:
linux-generic (2.6.31.15.28) to 2.6.31.16.29
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

so linux-generic (2.6.31.15.28) to 2.6.31.16.29 didn't get upgraded.

I ended up having to reinstall the -16's.


--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

NoOp wrote:

On 12/06/2009 09:29 AM, Leonard Chatagnier wrote:


As mentioned in a previous reply, I have only the kernel headers for
this new kernel. No generic kernel or modules for it. I also have two
Karmic partitions and just safe-upgraded and dist-upgraded both Karmic
partitions yet no -16 kernel or modules on either. One partition uses
the archives.ubuntu.com mirror and the other uses the 76.73.4.58 karmic
mirror. Anyone have any idea why only the header files are available on
two different mirror but not the kernel or modules. I usually just use
safe-upgrade and so far have gotten the -15 and all previous kernel,
modules, etc starting with the beta Karmic install. Appreciate any
help/suggestions as this is driving me crazy hoping the newa kernel will
solve some of m X window issue.
Thanks for any help/suggestions.



Via Synaptic set your repository for "Main server" and try to update
(just standard Reload) and then System|Administration|Update...). I had
an issue on one machine (32bit of course) where the -16 didn't get
properly upgraded. The history shows:
Commit Log for Sat Dec 5 09:05:25 2009
Upgraded the following packages:
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
linux-libc-dev (2.6.31-15.50) to 2.6.31-16.52
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

Whereas a system that properly upgraded to -16 shows:
Commit Log for Sat Dec 5 13:09:39 2009
Upgraded the following packages:
linux-generic (2.6.31.15.28) to 2.6.31.16.29
linux-headers-386 (2.6.31.15.28) to 2.6.31.16.29
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-386 (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-386 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-386 (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

Even taking out the -386, I should have gotten:
Upgraded the following packages:
linux-generic (2.6.31.15.28) to 2.6.31.16.29
linux-headers-generic (2.6.31.15.28) to 2.6.31.16.29
linux-image-generic (2.6.31.15.28) to 2.6.31.16.29
Installed the following packages:
linux-headers-2.6.31-16 (2.6.31-16.52)
linux-headers-2.6.31-16-generic (2.6.31-16.52)
linux-image-2.6.31-16-generic (2.6.31-16.52)

so linux-generic (2.6.31.15.28) to 2.6.31.16.29 didn't get upgraded.

I ended up having to reinstall the -16's.



Ok, did the synaptic bit and update manager bit. Neither one showed any
new packages
or upgrades to install. Also, aptitude search shows I have everthing
installed and have
rebooted a couple of times. No issues except, of course, the Karmic low
res issue. I still
get the start up message but accept the startup in low res mode just
this one time and
wait a bit and up comes the kdm login screen. I sure wish Ubuntu or
Nvidia or Hal or

dkms would fix this issue. -((

--
Leonard
lenc5570@sbcglobal.net
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users