Red Hat Bugzilla – Bug 837255
Siliconmotion hardware gives Not enough video memory for the configured screen size (1024x1024) and color depth.
Last modified: 2013-08-01 09:39:26 EDT
Created attachment 595927 [details]
Xorg.0.log shows screen size set too large
Description of problem:
With xorg-x11-drv-siliconmotion-1.7.6-1.fc17.i686.rpm installed,
I see the Fedora lightbulb display. Then, the screen goes dark,
with disk activity every few seconds.
Version-Release number of selected component (if applicable):
Fairy fresh FC17 with additional driver as above.
Every time, on a Panasonic CF28. Searching the Internet shows this to be a common problem in different distros
Steps to Reproduce:
1. Boot system
Slacko 5.3.3, a version of Puppy Linux, has an xorgwizard that allows trying various display configurations. However, it did not detect the hardware.
Rosa LXDE shows its logo, but also goes to a dark screen.
Attaching Xorg.0.log . My /etc/xorg.conf seems to have only a Keyboard section.
Created attachment 600522 [details]
Xorg file after trying Xorg -configure in single-user mode
Tried Xorg -configure in single-user. Will attach Xorg.0.log, conf.new, and console output
Created attachment 600524 [details]
xorg.conf.new form Xorg -configure
Created attachment 600525 [details]
console output from Xorg -configure
Created attachment 649907 [details]
After applying latest updates, recovered /var/log/messages as follows:
Booted with PAE kernel. Saw lightbulb and blue f, then dark screen, with occasional disk activity. After trying CTRL-ALT-Fn, CTRL-ALT-BKSP CTRL-ALT-DEL with no visible effect, flicked power switch and got a power down.
Booted with nonn-PAE kernel, same results.
Also tried setting nomodeset in GRUB, with same results.
Booted to single-user mode, and was able to recover /var/log/messages and log files, which I am posting.
Created attachment 649908 [details]
Created attachment 649909 [details]
lxdm.log, just in case
Re-assigning to correct component.
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.