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-next>] [day] [month] [year] [list]
Date:	Thu, 18 Jun 2009 19:50:16 +0200
From:	Vegard Nossum <vegard.nossum@...il.com>
To:	Joseph Chan <JosephChan@....com.tw>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: CONFIG_FB_VIA made the screen go black

Hi,

It seems that I was unfortunate and managed to get CONFIG_FB_VIA=y in
my config. The result is that during boot, when via_fb loads, the
screen goes black. I put CONFIG_FB_VIA=n as the only change to my
config and the screen works again. Actually, just before going black,
a few lines (I mean pixel rows) would shortly flicker or move up and
down the screen.

Here's what changed in dmesg when making this config change:

 pci_hotplug: PCI Hot Plug PCI Core version: 0.5
 Platform driver 'da903x-backlight' needs updating - please use dev_pm_ops
-VIA Graphics Intergration Chipset framebuffer 2.4 initializing
-ioremap failed
 no IO addresses supplied
 Platform driver 'tmio-fb' needs updating - please use dev_pm_ops
 ACPI: SSDT 000000007fe7ac90 001EA (v01  PmRef  Cpu0Ist 00003000 INTL 20051117)

I don't actually have a VIA card:

01:00.0 VGA compatible controller: nVidia Corporation GeForce 8400M GS (rev a1)

The machine booted fine otherwise. This was post-2.6.30 kernel from a
few days ago. I attached the log of the failure case in case there is
anything useful in there.


Vegard

View attachment "log.txt" of type "text/plain" (19506 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ