On Thursday 12 May 2005 19:07, c m wrote:
> if you forgot to change your bootloader (LILO) config
> for using the new kernel image then it still loads the
> old kernel.
> Even if you reinstall LILO after the compile.
He's on an Alpha platform, so his bootloader is something other than LILO and
g
On Thursday 12 May 2005 18:34, Marc Jackson wrote:
> I downloaded the software 2.4.20 to build a new kernel on an alpha machine.
>
> It compiled and I have a working kernel.
>
> Oddly enough, after booting on the new kernel ... uname -a returned 2.2.20.
>
> Can anyone think of why this would happen
>
> Oddly enough, after booting on the new kernel ...
> uname -a returned 2.2.20.
>
> Can anyone think of why this would happen?
>
One idea of a possibility.
if you forgot to change your bootloader (LILO) config
for using the new kernel image then it still loads the
old kernel.
Even if you r
On Thu, Jun 24, 2004 at 12:30:23PM +1000, Rob Weir wrote:
> On Wed, Jun 23, 2004 at 03:08:51PM +0100, David Goodenough said
> > Just recently the Alt+ shortcut to get to KDE menu entries
> > stopped working. I commented on this on the debian-kde list and got the
> > reply that someone had cured it
On Wed, Jun 23, 2004 at 03:08:51PM +0100, David Goodenough said
> Just recently the Alt+ shortcut to get to KDE menu entries
> stopped working. I commented on this on the debian-kde list and got the
> reply that someone had cured it by backout from 4.3.0dfsg.1-5_all to
> 4.3.0-7_all. I am unsure
5 matches
Mail list logo
