public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.33.2 does not boot on Atom?
Date: Mon, 12 Apr 2010 13:14:33 +0200	[thread overview]
Message-ID: <20100412111433.GA6631@linux-m68k.org> (raw)
In-Reply-To: <20100412061604.GB31112@kroah.com>

On Sun, Apr 11, 2010 at 11:16:05PM -0700, Greg KH wrote:
> On Tue, Apr 06, 2010 at 10:55:09PM +0200, Richard Zidlicky wrote:
> > Hi,
> > 
> > I have been compiling my own kernels since ages and switched from 2.6.32.8 to 
> > 2.6.33.2 now.
> > Same procedure like allways - copied .config to new buildtree, make menuconfig
> > (almost nothing changed in config), installed the new kernel on 2 machines.
> 
> Oops, that's the problem, you need to do 'make oldconfig' to ensure you
> didn't miss anything, and to adjust any new defaults.

did not tried that yet. Although it is possible to miss something with menuconfig
I did diff the .config files without noticing anything obvious.

Meanwhile I have tried a few recent Fedora-12 kernels and none of them worked on 
this particular Atom Netbook with which I have never had problems before.
With the Fedora kernels the issue appears to be Intel graphics and it seems the boot
continued when I blindly typed the dm password.. so I will investigate further.
Last Fedora kernel that worked was 2.6.31 based, the 2.6.32.* I tried so far will
display a black screen.

Richard

  reply	other threads:[~2010-04-12 11:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 20:55 2.6.33.2 does not boot on Atom? Richard Zidlicky
2010-04-12  6:16 ` Greg KH
2010-04-12 11:14   ` Richard Zidlicky [this message]
2010-04-13  9:09   ` Richard Zidlicky
2010-04-13 13:28     ` Greg KH
2010-04-13 18:22       ` Richard Zidlicky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100412111433.GA6631@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox