documentation-packages team mailing list archive

[Jan Willem Nienhuys <1641120@xxxxxxxxxxxxxxxxxx>]

Hello,

I don't find that very satisfying.
When a user such as I meets a start loop, he doesn't know
at all what is the cause. As the computer won't start, there is
no way to find out (on internet) what's the matter.

Doug Smythies writes "It has been beat to death over years and years."
which I interpret to mean that the problem is very well known to insiders
who apparently don't give a damn about users who don't know
what kernels are, nor that old kernels are preserved rather than deleted.

JWN





2016-11-23 20:32 GMT+01:00 Gunnar Hjalmarsson <1641120@xxxxxxxxxxxxxxxxxx>:

> I'd say that help with how to remove redundant kernels is a support
> request, so @Jan: Please ask for help at e.g. <http://askubuntu.com>.
>
> Closing.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1641120
>
> Title:
>   too many kernels produce start loop
>
> Status in ubuntu-docs package in Ubuntu:
>   Invalid
>
> Bug description:
>   After performing the last update, I followed the advice to restart the
> computer. Then it got into
>   a loop. After typing the correct password, the screen went 'ploink' and
> presented again an
>   empty password field. No failsafe option was present.
>
>   Upon getting help from an expert, this expert discovered that there were
> many old
>   linux kernels, all the way back to 2.6.23 en 3.13. This took a lot of
> time too. Something to do with
>   NVIDIA-drivers needing gcc. On starting all the init-ramdisks had to be
> update for all those kernel versions. (Says my expert.)
>
>   I have had several computers, and each time I copied the entire hard
>   disk of one to the next one.
>
>   The remedy was to remove all old kernel versions.
>
>   I consider this a bug. Installing a new kernel without removing old ones
> causes
>   apparently serious problems. Ordinary users who have no idea about what
> is "under the hood"
>   are seriously handicapped and not all of them have easy access to an
> expert who can fix things
>   in a couple of hours.
>
>   I have Ubuntu 16.04.1 LTS
>
>   apt-cache policy pkgname  yields no information.
>
>   I am not sure that have too many outdated linux kernels
>   is something in a specific package.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+
> bug/1641120/+subscriptions
>


-- 
dr. J.W. Nienhuys
Dommelseweg 1A
5581 VA Waalre
Netherlands
tel. +31.40.2216791

-- 
You received this bug notification because you are a member of
Documentation Packages, which is subscribed to ubuntu-docs in Ubuntu.
https://bugs.launchpad.net/bugs/1641120

Title:
  too many kernels produce start loop

Status in ubuntu-docs package in Ubuntu:
  Invalid

Bug description:
  After performing the last update, I followed the advice to restart the computer. Then it got into
  a loop. After typing the correct password, the screen went 'ploink' and presented again an
  empty password field. No failsafe option was present.

  Upon getting help from an expert, this expert discovered that there were many old 
  linux kernels, all the way back to 2.6.23 en 3.13. This took a lot of time too. Something to do with
  NVIDIA-drivers needing gcc. On starting all the init-ramdisks had to be update for all those kernel versions. (Says my expert.)

  I have had several computers, and each time I copied the entire hard
  disk of one to the next one.

  The remedy was to remove all old kernel versions.

  I consider this a bug. Installing a new kernel without removing old ones causes 
  apparently serious problems. Ordinary users who have no idea about what is "under the hood" 
  are seriously handicapped and not all of them have easy access to an expert who can fix things 
  in a couple of hours. 
  	
  I have Ubuntu 16.04.1 LTS

  apt-cache policy pkgname  yields no information.

  I am not sure that have too many outdated linux kernels
  is something in a specific package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1641120/+subscriptions