lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 24 Jul 2014 18:26:44 -0400
From:	Woody Suwalski <terraluna977@...il.com>
To:	Martin Kepplinger <martink@...teo.de>,
	Zhang Rui <rui.zhang@...el.com>
CC:	"rjw@...ysocki.net" <rjw@...ysocki.net>,
	"lenb@...nel.org" <lenb@...nel.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	linux-media@...r.kernel.org
Subject: Re: [BUG] rc1 rc2 rc3 not bootable - black screen after kernel loading

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ