ubuntu-x-swat team mailing list archive

[Felix Kuehling <felix.kuehling@xxxxxxx>]

The steps you take to recover your system (dpkg-reconfigure -phigh
xserver-xorg; aticonfig --initial -f) do much more than changing
xorg.conf. I have two possible suspicions.

1: Due to the age of the system I suspect that it's an AGP board,
correct? Maybe the sequence or timing of loading fglrx and the AGP
drivers is causing problems. When in recovery mode, instead of your
steps above try "rmmod fglrx; modprobe fglrx" and resume booting. Does
that help?

2: Instead of the steps above, try this in recovery mode before you
resume booting: rm /etc/ati/amdpcsdb. Do NOT delete
/etc/ati/amdpcsdb.default, though.

/etc/ati/amdpcsdb is where the driver remembers settings in between X
sessions. It's possible that a combination of remembered settings in
amdpcsdb and the cold reboot (which reinitializes the hardware) triggers
the problem on your hardware. When you reboot from Windows, it doesn't
completely reinitialize the hardware. Some register values, clocks, even
parts of the framebuffer are preserved from how the Windows driver
initialized the hardware.

-- 
[Kubuntu] xorg.conf needs to be reconfigured at each reboot
https://bugs.launchpad.net/bugs/429419
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to fglrx-installer in ubuntu.