linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Woody Suwalski <terraluna977@gmail.com>
To: Martin Kepplinger <martink@posteo.de>, Zhang Rui <rui.zhang@intel.com>
Cc: "rjw@rjwysocki.net" <rjw@rjwysocki.net>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-media@vger.kernel.org
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading
Date: Thu, 24 Jul 2014 18:26:44 -0400	[thread overview]
Message-ID: <53D18824.9000907@gmail.com> (raw)
In-Reply-To: <53D131E7.2090304@posteo.de>

Martin Kepplinger wrote:
> Am 2014-06-30 12:39, schrieb Martin Kepplinger:
>> back to aaeb2554337217dfa4eac2fcc90da7be540b9a73 as the first bad
>> commit. why is this not revertable exactly? how can I show a complete
>> list of commits this merge introduces?
>>
> It seems that _nobody_ is running a simple 32 bit i915 (acer) laptop.
> rc6 is still unusable. Black screen directly after kernel-loading. no
> change since rc1.
>
> Seems like I won't be able to use 3.16. I'm happy to test patches and am
> happy for any advice what to do, when time permits.
>
>                               martin
>
Martin, I am running happily a 32-bit kernel 3.16-rc*all on i915 (Asus 
EeePC)
However: from your postings I still have no idea what Intel video 
chipset is in your Acer.
Try to add "nomodeset=y" to your kernel's cmdline to verify that it can 
boot. You have many kobject messages which are hiding what is 
happening... And please submit at least full dmesg output and "lspci 
-nn" ;-)

Woody

  reply	other threads:[~2014-07-24 22:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-22 14:24 [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution Martin Kepplinger
2014-06-23  1:10 ` Zhang, Rui
2014-06-23 12:22   ` Martin Kepplinger
2014-06-23 13:14     ` Zhang Rui
2014-06-23 14:46       ` Martin Kepplinger
2014-06-23 20:04         ` [BUG] black screens (was: rc1 and rc2...screen black ...) Felix Miata
2014-06-27 15:14         ` [BUG] rc1 and rc2: Laptop unusable: on boot,screen black instead of native resolution Zhang Rui
2014-06-27 18:09           ` Martin Kepplinger
2014-06-27 19:51             ` Martin Kepplinger
2014-06-27 22:14               ` Martin Kepplinger
2014-06-30  7:52                 ` [BUG] rc3 Oops: unable to handle kernel NULL pointer dereference at 0000074c Martin Kepplinger
2014-06-30  8:18                   ` Zhang Rui
2014-06-30  8:20                     ` Zhang Rui
2014-06-30  9:00                       ` Martin Kepplinger
2014-06-30 10:39                         ` [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading Martin Kepplinger
2014-07-24 16:18                           ` Martin Kepplinger
2014-07-24 22:26                             ` Woody Suwalski [this message]
2014-07-24 23:20                             ` Hugh Dickins
2014-07-25 10:15                               ` Martin Kepplinger
2014-07-26 23:19                                 ` Hugh Dickins

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=53D18824.9000907@gmail.com \
    --to=terraluna977@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=martink@posteo.de \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).