On Tuesday 17 July 2007 22:02, Peter Alfredsen wrote:
> On Tuesday 17 July 2007, Mick wrote:
> > On Tuesday 17 July 2007 15:46, Neil Bothwick wrote:
> > > On Tue, 17 Jul 2007 15:00:05 +0100, Mick wrote:
> > > > It's not as if it starts to load the kernel and then fails. It just
> > > > stops befor
On Tuesday 17 July 2007, Mick wrote:
> On Tuesday 17 July 2007 15:46, Neil Bothwick wrote:
> > On Tue, 17 Jul 2007 15:00:05 +0100, Mick wrote:
> > > It's not as if it starts to load the kernel and then fails. It just
> > > stops before then. Shall I wait for a future version? Am I the only
> > >
Albert Hopkins wrote:
> On Tue, 2007-07-17 at 15:19 +0200, Alan McKinnon wrote:
>
>> On Tuesday 17 July 2007, Mick wrote:
>>
>>> On Tuesday 17 July 2007 13:20, Billy McCann wrote:
>>>
Hi Mick. From what I understand, using oldconfig for major
version changes (.20 -> .21)
On Tuesday 17 July 2007 15:46, Neil Bothwick wrote:
> On Tue, 17 Jul 2007 15:00:05 +0100, Mick wrote:
> > It's not as if it starts to load the kernel and then fails. It just
> > stops before then. Shall I wait for a future version? Am I the only
> > one here with running a PIII that won't boot t
On Tue, 17 Jul 2007 15:00:05 +0100, Mick wrote:
> It's not as if it starts to load the kernel and then fails. It just
> stops before then. Shall I wait for a future version? Am I the only
> one here with running a PIII that won't boot this kernel?
Is it possible that your kernel image is corru
On Tue, 2007-07-17 at 15:19 +0200, Alan McKinnon wrote:
> On Tuesday 17 July 2007, Mick wrote:
> > On Tuesday 17 July 2007 13:20, Billy McCann wrote:
> > > Hi Mick. From what I understand, using oldconfig for major
> > > version changes (.20 -> .21) is a bad idea. Here's what I did. It
> > > ma
On Tuesday 17 July 2007 14:30, Neil Bothwick wrote:
> On Tue, 17 Jul 2007 07:20:06 -0500, Billy McCann wrote:
> > Hi Mick. From what I understand, using oldconfig for major version
> > changes (.20 -> .21) is a bad idea. Here's what I did. It may be slow
> > and stupid but it worked like a char
On Tue, 17 Jul 2007 07:20:06 -0500, Billy McCann wrote:
> Hi Mick. From what I understand, using oldconfig for major version
> changes (.20 -> .21) is a bad idea. Here's what I did. It may be slow
> and stupid but it worked like a charm.
2.6.20 to 2.6.21 is not a major version change, it's a
Hi Billy,
Tuesday, July 17, 2007, 3:20:06 PM, you wrote:
> Hi Mick. From what I understand, using oldconfig for major
> version changes (.20 -> .21) is a bad idea. Here's what I did. It
> may be slow and stupid but it worked like a charm.
> Open two root terminals and navigate one to /usr/s
On Tuesday 17 July 2007, Mick wrote:
> On Tuesday 17 July 2007 13:20, Billy McCann wrote:
> > Hi Mick. From what I understand, using oldconfig for major
> > version changes (.20 -> .21) is a bad idea. Here's what I did. It
> > may be slow and stupid but it worked like a charm.
>
> Sure, but I h
On Tuesday 17 July 2007 13:20, Billy McCann wrote:
> Hi Mick. From what I understand, using oldconfig for major version
> changes (.20 -> .21) is a bad idea. Here's what I did. It may be slow and
> stupid but it worked like a charm.
Sure, but I have been using oldconfig for previous major cha
On 7/17/07, Mick <[EMAIL PROTECTED]> wrote:
Hi All,
This must have been the first time in many years that I cannot boot a
kernel.
I mean I cannot boot it at all! It just spins the disk at Booting
kernel . . .
Since I built this from a 2.6.20-gentoo-r8 .config file using make
oldconfig,
so I a
Hi All,
This must have been the first time in many years that I cannot boot a kernel.
I mean I cannot boot it at all! It just spins the disk at Booting
kernel . . .
Since I built this from a 2.6.20-gentoo-r8 .config file using make oldconfig,
so I am not sure what's gone wrong. The only re
13 matches
Mail list logo
