You are not logged in.

#1 2016-11-22 22:42

blim
Member
Registered: 2016-11-22
Posts: 4

Q4OS looks like this after a fresh install

IMG_20161123_095724.jpg
IMG_20161123_100634.jpg

Any fixes?

Offline

#2 2016-11-22 23:08

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,501
Website

Re: Q4OS looks like this after a fresh install

It's obviously graphics driver glitch. Please post here file '/var/log/Xorg.0.log' to analyze.

Offline

#3 2016-11-23 03:05

blim
Member
Registered: 2016-11-22
Posts: 4

Re: Q4OS looks like this after a fresh install

q4osteam wrote:

It's obviously graphics driver glitch. Please post here file '/var/log/Xorg.0.log' to analyze.

I'm not sure how I can realistically do that.

I tried 2.2.1 livecd and while it doesn't have the graphics problem, it was very slow and the installer won't run.

Offline

#4 2016-11-23 03:38

blim
Member
Registered: 2016-11-22
Posts: 4

Re: Q4OS looks like this after a fresh install

It took me a while but here's the log. https://pastebin.mozilla.org/8930709

Offline

#5 2016-11-23 08:26

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,501
Website

Re: Q4OS looks like this after a fresh install

Ok, we will analyze the log and let you know a result. You could also attach files directly into the forum posts - Post Reply -> Attachment -> Choose File ...

Offline

#6 2016-11-23 09:45

q4osteam
Q4OS Team
Registered: 2015-12-06
Posts: 4,501
Website

Re: Q4OS looks like this after a fresh install

You could try to create a specific configuration for your Savage graphics chipset. Create file '/etc/X11/xorg.conf.d/99-savage.conf' and paste following contents into it:

Section "Device"
        Identifier	"gfxcard"
        Driver		"savage"
# You will likely have to use NoAccel.  You can try EXA, but it's likely you will end up
# with a corrupted screen or a hard lockup.
        Option		"NoAccel" "True"
# Use ShadowFB instead of acceleration.  It's unlikely that acceleration will provide
# any benefits on this ancient chipset anyway.
        Option		"ShadowFB" "Enable"
# The following two options might or might not improve performance.  Remove the "#" to
# try using them:
#       Option		"NoPciBurst" "Enable"
#       Option		"FramebufferWC"
# If Xorg crashes on startup (hangs with black screen) you may try out the following 
# two lines (by removing the "#" before the line):
#       Option		"NoDDC"
# The 1024 in UseTiming is for a Notebook with a native resolution of 1024x768 pixel.
# If you have a native resolution of 800x600 pixel you should use "UseTiming800" instead.
#       Option		"UseTiming1024"
# EXA might or might not work.  It's likely that it will not, but if you want to try it,
# uncomment the following line and comment out the "NoAccel" option:
#       Option         "AccelMethod" "EXA"
EndSection
Section "Screen"
        Identifier	"Screen 0"
        Device		"gfxcard"
        Monitor		"Monitor 0"
# You can try setting DefaultDepth to 24, but many Savage cards only have 8MB of RAM
# and may not be able to achieve higher resolutions with 24-bit color.
        DefaultDepth	16
EndSection
Section "Monitor"
        Identifier	"Monitor 0"
        Option		"DPMS" "Disable"
EndSection

Reboot. You could fiddle with some commented options to get it work properly.

Offline

#7 2016-11-25 04:47

blim
Member
Registered: 2016-11-22
Posts: 4

Re: Q4OS looks like this after a fresh install

It worked! Everything seems to run fine now. Thank you.

Offline

Board footer

Powered by FluxBB