> Sorry to see that you're having this problem. I'm stymied as to why it might
> happen with a VM. I had assumed that the new kernel had stopped supporting
> some piece of hardware in my rather unusual little notebook computer.
> The same day the kernel was updated on my system, pc-grub was
On 11/03/2016 03:26 PM, Mike Conde wrote:
Have you checked your boot partition - does it have enough free space?
I don't have a separate boot partition, just one main partition that
is 40GB in capacity and 40% full.
Sorry to see that you're having this problem. I'm stymied as to why it
> Have you checked your boot partition - does it have enough free space?
I don't have a separate boot partition, just one main partition that
is 40GB in capacity and 40% full.
Mike Conde wrote:
> I am having exactly the same problem as Jape Person's post from Oct 22
> 2016, except my hardware environment is completely different.
>
> I am running Debian testing/Stretch 64-bit on a virtual machine under
> virtualbox. The host OS is Windows 7 64-bit.
>
> I don't know
I am having exactly the same problem as Jape Person's post from Oct 22
2016, except my hardware environment is completely different.
I am running Debian testing/Stretch 64-bit on a virtual machine under
virtualbox. The host OS is Windows 7 64-bit.
I don't know exactly which kernel update was
On 10/23/2016 05:26 PM, Frank wrote:
Op 23-10-16 om 22:47 schreef Felix Miata:
I don't remember having any Stretch installations with fewer than two
installed kernels. The currently booted one, originally installed 51
weeks ago, has 6 installed. I've yet to discover any doc suggesting
anything
Op 23-10-16 om 22:47 schreef Felix Miata:
I don't remember having any Stretch installations with fewer than two
installed kernels. The currently booted one, originally installed 51
weeks ago, has 6 installed. I've yet to discover any doc suggesting
anything about any possibility of automatic
On 10/23/2016 04:47 PM, Felix Miata wrote:
Jape Person composed on 2016-10-23 14:33 (UTC-0400):
Felix Miata wrote:
Does the same thing happen booting the previous kernel
(4.6?)?
Nope. The problem occurred on the first reboot after the
upgrade from 4.7.6-1 to 4.7.8-1. The upgrade process
Jape Person composed on 2016-10-23 14:33 (UTC-0400):
Felix Miata wrote:
Does the same thing happen booting the previous kernel (4.6?)?
Nope. The problem occurred on the first reboot after the upgrade
from 4.7.6-1 to 4.7.8-1. The upgrade process didn't leave
4.7.6-1 in place so I could
On 10/23/2016 01:33 PM, Felix Miata wrote:
James P. Wallen composed on 2016-10-23 12:14 (UTC-0400):
On 10/22/2016 18:10 (UTC-0400), Jape Person wrote:
It's confusing to see a response from a different person writing as if he was
responding to himself.
The confusion is caused by my idiotic
On 10/23/2016 01:21 PM, Børge Holen wrote:
I have to use the nomodeset from time to time where the f*** gfx card has
unresolved issues with itself. Atleast it lets me boot to a prompt. Now
thinking of it, I have no blinking cursor, I just get a black screen... So
different issue all together and
On 10/23/2016 01:03 PM, Michael Lange wrote:
On Sun, 23 Oct 2016 12:14:39 -0400
"James P. Wallen" wrote:
Double checked to see if I was right about the video subsystem.
It is not ATI, it is Intel integrated. No docs on this thing. It
was never officially sold in U.S.,
James P. Wallen composed on 2016-10-23 12:14 (UTC-0400):
On 10/22/2016 18:10 (UTC-0400), Jape Person wrote:
It's confusing to see a response from a different person writing as if he was
responding to himself.
Be that as it may, have either of you tried intercepting Grub and unquieting
the
Heck I even remember a one-floppy live distribution that I had for just
this purpose.
On Sun, Oct 23, 2016 at 7:26 PM, Børge Holen wrote:
> Have you tried booting off a live distribution and inserted the old kernel
> and symlinked the libraries so you can rerun grub
Have you tried booting off a live distribution and inserted the old kernel
and symlinked the libraries so you can rerun grub update? I remember we had
to do that with lilo whenever I tried new kernels and forgot all about
lilo. Cannot even remember the last time I did it, since I found the rescue
I have to use the nomodeset from time to time where the f*** gfx card has
unresolved issues with itself. Atleast it lets me boot to a prompt. Now
thinking of it, I have no blinking cursor, I just get a black screen... So
different issue all together and I am just rambling on
On Sun, Oct 23, 2016
On Sun, 23 Oct 2016 12:14:39 -0400
"James P. Wallen" wrote:
> Double checked to see if I was right about the video subsystem.
> It is not ATI, it is Intel integrated. No docs on this thing. It
> was never officially sold in U.S., where I live currently. Since
> I can't
Double checked to see if I was right about the video subsystem.
It is not ATI, it is Intel integrated. No docs on this thing. It
was never officially sold in U.S., where I live currently. Since
I can't boot it to usable state, I can't (easily) find out
exactly which video it uses.
It's
I've got a little Panasonic CF-R3 mini-laptop which has been
kept fully up-to-date in testing every day since Etch was
released. (I think the original installation is that old.)
I've been using the linux-image-686-pae kernel on the system.
The updates today included an update to
19 matches
Mail list logo